Difference between revisions of "Transport Canada (TC) Infrastructure Modernization - Cloud / DR / Workload Migration"

From wiki
Jump to: navigation, search
 
(13 intermediate revisions by the same user not shown)
Line 255: Line 255:
 
This project is following an iterative Agile process to migrate applications to the Cloud.
 
This project is following an iterative Agile process to migrate applications to the Cloud.
  
'''The following applications have already been migrated to the Cloud: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, and NWAR-ESS.'''
+
'''The following applications have already been migrated to the Cloud: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, iServer, and NWAR-ESS.'''
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 290: Line 290:
 
|ASD
 
|ASD
 
|NPRD
 
|NPRD
|Dev is working on authentication, data conversion, and a new data model to fit TC’s current modeling standards.
+
|Confirming if ATO has been received and if the application can move to PROD.
 
|-
 
|-
 
|eBIDA
 
|eBIDA
 
|NPRD
 
|NPRD
|Related to COVID-19 response. Part of SCED pilot. Planning work in progress, intake form and infrastructure summary received. Databricks expert resource is needed. Meeting with Microsoft to discuss.
+
|Related to COVID-19 response. Part of SCED pilot. ATO received. Taking a phased release approach. Phase 1 moving to PROD.
 
|-
 
|-
 
|CARTES
 
|CARTES
Line 302: Line 302:
 
|CCM
 
|CCM
 
|Planning
 
|Planning
|
+
|Initial planning underway.
 
|-
 
|-
 
|ECATS
 
|ECATS
Line 311: Line 311:
 
|Planning
 
|Planning
 
|Initial planning underway.
 
|Initial planning underway.
|-
 
|iServer
 
|PROD
 
|Ongoing support to fix technical issues.
 
 
|-
 
|-
 
|MISS
 
|MISS
 
|Planning
 
|Planning
|
+
|Initial planning underway.
 
|-
 
|-
 
|MMERS
 
|MMERS
 
|Planning
 
|Planning
|Kickoff meeting being scheduled.
+
|Migration plan in progress.
 
|-
 
|-
 
|PGS
 
|PGS
Line 330: Line 326:
 
|RPA CoE
 
|RPA CoE
 
|Planning
 
|Planning
|Related to COVID-19 response. Initial interview conducted, data gathering in progress.
+
|Related to COVID-19 response. Migration plan in progress.
 
|-
 
|-
 
|SAP-BI
 
|SAP-BI
Line 338: Line 334:
 
|SRF
 
|SRF
 
|Planning
 
|Planning
|Intake form and questionnaire received. Assessment and planning document created based on questionnaire and first interview.
+
|Migration plan created.
 
|-
 
|-
 
|Tachyon and ActiveEfficiency
 
|Tachyon and ActiveEfficiency
 
|Planning
 
|Planning
|
+
|Initial planning underway.
 
|-
 
|-
 
|TCLR API
 
|TCLR API
 
|Planning
 
|Planning
|
+
|Initial planning underway.
 
|-
 
|-
 
|TCOMS
 
|TCOMS
 
|Planning
 
|Planning
|Related to COVID-19 response. Initial interview complete, data gathering in progress.
+
|Related to COVID-19 response. Migration plan in progress.
 
|-
 
|-
 
|TEAMMATE
 
|TEAMMATE
|Doing
+
|NPRD
 
|Performance testing in progress.
 
|Performance testing in progress.
 
|-
 
|-
 
|Vessel Registry
 
|Vessel Registry
 
|Planning
 
|Planning
|
+
|Initial planning underway.
 
|-
 
|-
 
|ZAMMAD
 
|ZAMMAD
 
|Planning
 
|Planning
|
+
|Migration plan in progress.
 +
|}
 +
 
 +
{| class="wikitable"
 +
|'''Blocked Apps/Platforms'''
 +
|'''Current State'''
 +
|'''Notes'''
 
|-
 
|-
 
|LDPS
 
|LDPS
Line 642: Line 644:
 
== Défis: Risques et enjeux ==
 
== Défis: Risques et enjeux ==
  
'''RISQUE:''' Le pilote ADNS a commencé avec deux applications: PGS et eBIDA, mais il y a plus de 370 autres applications à migrer vers le nuage, de sorte que le calendrier global du projet peut encore être retardé. Quand le pilote ADNS est terminé, la durée de mise en œuvre de SCED sera plus claire pour les autres applications. '''Répercussion:''' élevée. '''Probabilité:''' moyenne. '''Atténuation:''' évaluation continue du calendrier du projet au fur et à mesure du développement de la mise en œuvre de SCED et poursuite de la migration des applications non dépendantes de ADNS.   
+
'''RISQUE:''' Le pilote ADNS a commencé avec deux applications: PGS et eBIDA, mais il y a plus de 370 autres applications à migrer vers le nuage, de sorte que le calendrier global du projet peut encore être retardé. Quand le pilote ADNS est terminé, la durée de mise en œuvre de ADNS sera plus claire pour les autres applications. '''Répercussion:''' élevée. '''Probabilité:''' moyenne. '''Atténuation:''' évaluation continue du calendrier du projet au fur et à mesure du développement de la mise en œuvre de ADNS et poursuite de la migration des applications non dépendantes de ADNS.   
  
 
'''RISQUE:''' 27 projets d'investissement dépendent de ce projet pour l'infrastructure de la fondation de nuager, la migration de la charge de travail et ADNS. La livraison de ces 27 projets d'immobilisations pourrait être retardée en raison du retard dans l'obtention du ADNS. '''Répercussion:''' élevée.  '''Probabilité:''' élevée. '''Atténuation:''' créez des implémentations sur site pour les 27 projets d'immobilisations qui peuvent être facilement migrés vers le nuage lorsque ADNS devient disponible.
 
'''RISQUE:''' 27 projets d'investissement dépendent de ce projet pour l'infrastructure de la fondation de nuager, la migration de la charge de travail et ADNS. La livraison de ces 27 projets d'immobilisations pourrait être retardée en raison du retard dans l'obtention du ADNS. '''Répercussion:''' élevée.  '''Probabilité:''' élevée. '''Atténuation:''' créez des implémentations sur site pour les 27 projets d'immobilisations qui peuvent être facilement migrés vers le nuage lorsque ADNS devient disponible.
Line 710: Line 712:
 
Ce projet suit un processus Agile itératif et le premier ensemble d'applications est en cours de migration vers le nuage.
 
Ce projet suit un processus Agile itératif et le premier ensemble d'applications est en cours de migration vers le nuage.
  
'''Les applications suivantes ont déjà été migrées vers le nuage: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, et NWAR-ESS.'''
+
'''Les applications suivantes ont déjà été migrées vers le nuage: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, iServer et NWAR-ESS.'''
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 745: Line 747:
 
|ASD
 
|ASD
 
|Non-production
 
|Non-production
|L’équipe responsable de la conception travaille à l’authentification, à la conversion des données et à l’élaboration d’un nouveau modèle de données afin de respecter les normes actuelles de TC en matière de modélisation des données.
+
|Confirmer si ADF a été reçu et si l'application peut passer à un environnement de production.
 
|-
 
|-
 
|eBIDA
 
|eBIDA
 
|Non-production
 
|Non-production
|En lien avec l’intervention à la COVID-19. Fait partie du projet pilote d’ADNS. Planification en cours; le formulaire d’accueil et le sommaire de l’infrastructure ont été reçus. L’aide d’un expert de Databricks est nécessaire. Une réunion avec Microsoft aura lieu afin d’en discuter.
+
|En lien avec l’intervention à la COVID-19. Fait partie du projet pilote d’ADNS. ADF a reçu. Adopter une approche de la version logicielle de phase. La première phase est le passage à un environnement de production.  
 
|-
 
|-
 
|CARTES
 
|CARTES
Line 757: Line 759:
 
|CCM
 
|CCM
 
|Planification
 
|Planification
|
+
|Planification initiale en cours.
 
|-
 
|-
 
|CESTA
 
|CESTA
Line 766: Line 768:
 
|Planification
 
|Planification
 
|Planification initiale en cours.
 
|Planification initiale en cours.
|-
 
|iServer
 
|Production
 
|Un soutien continu est sollicité afin de régler les problèmes techniques.
 
 
|-
 
|-
 
|LSEE
 
|LSEE
 
|Planification
 
|Planification
|
+
|Planification initiale en cours.
 
|-
 
|-
 
|SRMAL
 
|SRMAL
 
|Non-Production
 
|Non-Production
|Une réunion de lancement est prévue.
+
|Plan de migration en cours.
 
|-
 
|-
 
|PGS
 
|PGS
Line 785: Line 783:
 
|CE APR
 
|CE APR
 
|Planification
 
|Planification
|En lien avec l’intervention à la COVID-19. L’entrevue initiale a été effectuée; la collecte de données est en cours.
+
|En lien avec l’intervention à la COVID-19. Plan de migration en cours.
 
|-
 
|-
 
|RA-SAP
 
|RA-SAP
Line 793: Line 791:
 
|Registre des navires
 
|Registre des navires
 
|Planification
 
|Planification
|
+
|Planification initiale en cours.
 
|-
 
|-
 
|SRF
 
|SRF
 
|Planification
 
|Planification
|Le formulaire d’accueil et le questionnaire ont été reçus. Un document d’évaluation et de planification a été créé en fonction du questionnaire et de la première entrevue.
+
|Plan de migration créé.
 
|-
 
|-
 
|SGOTC
 
|SGOTC
 
|Planification
 
|Planification
|En lien avec l’intervention à la COVID-19. L’entrevue initiale a été effectuée; la collecte de données est en cours.
+
|En lien avec l’intervention à la COVID-19. Plan de migration en cours.
 
|-
 
|-
 
|Tachyon and ActiveEfficiency
 
|Tachyon and ActiveEfficiency
 
|Planification
 
|Planification
|
+
|Planification initiale en cours.
 
|-
 
|-
 
|TCLR API
 
|TCLR API
 
|Planification
 
|Planification
|
+
|Planification initiale en cours.
 
|-
 
|-
 
|TEAMMATE
 
|TEAMMATE
|En cours
+
|Non-production
 
|Essais de rendement en cours.  
 
|Essais de rendement en cours.  
 
|-
 
|-
 
|ZAMMAD
 
|ZAMMAD
 
|Planification
 
|Planification
|
+
|Plan de migration en cours.
 +
|}
 +
 
 +
{| class="wikitable"
 +
|'''Application ou plateforme bloquée'''
 +
|'''État actuel'''
 +
|'''Notes'''
 
|-
 
|-
 
|PAP
 
|PAP

Latest revision as of 13:20, 31 July 2020

Transport Canada (TC) Infrastructure Modernization - Cloud / DR / Workload Migration[edit | edit source]


Transport Canada (TC) IT Infrastructure Modernization[edit | edit source]

The goal of this project is to deliver a complete modern infrastructure environment for TC applications in the Cloud. This requires building a foundational Cloud environment, planning and executing a workload migration plan, as well as creating and implementing a Disaster Recovery Management Program. In conjunction with SSC, a secure network to Cloud and authentication services will be established.

The Cloud will provide TC with a modern, scalable, and resilient infrastructure which offers disaster recovery and rapid time to market to support the promotion of a safe and secure, efficient and environmentally responsible transportation system in Canada.

This project is meant to address the business needs and opportunities of:

  • Providing recovery services for IT in the event of a disaster. This will ensure that the delivery of critical services affecting the safety, security, and economic viability of Canadian citizens continues in a normal operations mode in the event of a disaster;
  • Responding to the Cloud First principle and direction from TBS for delivery of Digital Services;
  • Responding to demands for increased IT capabilities and increased IT capacity to support department’s programs;
  • Adoption of DevSecOps and modern development methodologies that are enhanced by Cloud services – working in Agile, Open, Collaboration; and,
  • Implementing a Disaster Recovery Management program in response to the TBS Policy on Government Security to provide IT service continuity in a timely and efficient manner.

The key deliverables are:

  • Modernized TC IT environment using Cloud solutions;
  • A migration of all applications/systems within the Workload Migration (WLM) initiative to the Cloud;
  • Application development and support model modernization to enable Cloud solutions providing efficiencies in delivery time and cost; and,
  • A validated and maintained Disaster Recovery Management framework in place.

Secure Cloud Enablement and Defence (SCED)[edit | edit source]

As workloads are migrated to the Cloud, the GC perimeter shifts outside of the on-premise environment, and measures must be put in place to monitor and protect these Cloud-based environments, and respond to cyber threats quickly. The establishment of private, dedicated connections to GC approved Cloud Service Providers (CSP) will enable a hybrid IT environment, and ensure that the GC can continue to have secure access to information systems and solutions hosted in the Cloud.

Secure connectivity from Cloud to Ground is being implemented for applications and platforms that handle Protected B data. This connectivity is Secure Cloud Enablement and Defence (SCED), also called Express Route. SCED was delivered to TC by SSC in June 2020 as a pilot project for two applications: Enterprise BI and Data Analytics (eBIDA) and Policy on Government Security (PGS). SCED is currently being implemented for these two applications.

Cloud Service Operation Model (CSOM)[edit | edit source]

The Cloud Service Operation Model (CSOM) is a framework used to assess current levels of organizational maturity in the operation, management, and governance of Cloud services. The CSOM framework and methodology is iterative and can be used for existing and new Cloud services. Microsoft is leading the CSOM effort for TC and will deliver the Maturity Roadmap and Assessment Report in August 2020.

Project Status[edit | edit source]

This project is using Agile methodology and is in Phase 3, Launch/Execution & Control, of the TC Project Management Framework 4 Gate Model. TC's Azure Cloud Foundational Environment has been granted Authority to Operate (ATO) up to Protected-B for applications not requiring secure network connectivity.

Overall, the project was impacted by the delayed SSC delivery of SCED (Secure Cloud Enablement & Defence), required for applications that need secure connectivity, but is now moving forward with a SCED pilot for two COVID-19 related applications: PGS and eBIDA. Applications related to the COVID-19 response have been given top priority for migration, so more resources will be put on these, and other activities may be impacted. For PGS and eBIDA, resources from Solutions Centre and Microsoft have been secured for Cloud migration work.

Disaster Recovery (DR) plans are implemented for each application that moves to the Cloud, if required. The full DR program is expected to be set up and operational by the end of the calendar year 2022. All applications are expected to be in the Cloud, with DR plans if required, by March 2023.

Milestones Initial Target Date Forecast Date Completion Date Comments
Project Start Date 2017-10-26 2017-10-26
Discovery & Analysis for Disaster Recovery (DR) 2018-10-05 2018-10-05 2018-10-05 Complete: Initial research for establishing a Disaster Recovery Program for TC
Gate 0 Phase 1: Discovery and Initial Cloud Foundation 2019-04-29 2019-04-01 2019-04-01 Complete: Task awarded to Microsoft to collect information for Cloud environment, assess the TC landscape, and create the initial working environment for TC applications.
Gate 1 Phase 2: Application Target State Assessment 2019-09-20 2019-09-20 2019-09-20 Complete: All business systems assessed and assigned a Cloud target state.
GC EARB Prioritization for Secure Cloud Enablement Defence (SCED) 2018-07-16 2020-06-30 TC requested a target date of July 2018 for SCED but delivery was delayed. Until SCED is available, TC cannot put into production any Cloud applications that require secure connectivity.
Cloud Foundation Build 2019-04-01 2019-10-18 2019-10-18 Complete (except for SCED secure connectivity). This is the Cloud working environment for TC applications.
Sprint #1 Migration of Applications to Cloud 2020-01-31 2020-01-31 2020-01-31 Sprint #1 complete. The following apps were worked on: CUMULUS, SAP-BI, TSCA. CUMULUS progressed into a Non-Production environment.
Gate 2 Project Execution Approval (under the PMF 4 Gate Model) 2020-03-01 2020-03-01 2020-01-30
Sprint #2 Migration of Applications to Cloud 2020-02-28 2020-02-28 2020-02-28 Sprint #2 complete. The following apps were worked on: CUMULUS, SAP-BI, TSCA, LDPS, TeamMate Suite, TC WWW, ASD.
Sprint #3 Migration of Applications to Cloud 2020-03-15 2020-04-30 2020-04-30 Sprint #3 complete. The EGIS app was worked on.
Sprint #4 Migration of Applications to Cloud 2020-05-04 2020-05-20 Sprint #4 in progress. The following apps are being worked on: MEDV, SRF, iServer.
Migration of Business Systems to the Cloud 2023-03-31 2023-03-31 Remainder of systems migrated to the Cloud.
Disaster Recovery Plans for all applications completed 2023-03-31 2023-03-31
DR initial Exercise 2022-03-30 2022-03-30 First full scale exercise
Gate 3 Phase 4 - Project Completion Date - Approval for Project close 2023-03-31 2023-03-31 TC signoff of delivery of all services
Gate 4 - Project Close 2023-04-15 2023-04-15

Key Accomplishments[edit | edit source]

  • The following applications have been migrated to the Cloud: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, and NWAR-ESS.
  • TC-SSC ADM Cloud Steering Committee created to address issues and risks associated with this project.
  • SCED pilot in progress for two applications: PGS and eBIDA.
  • Applications related to COVID-19 response were prioritized and work is underway.
  • Identified and prioritized next 8 non-COVID-19 applications for migration to the Cloud.
  • Upgraded the Microsoft Multi-Factor Authentication (MFA) and Self-Service Password Reset (SSPR) features to use a centralized portal.
  • Created a Cloud Migration Checklist for teams to use for migrating their apps to the Cloud.
  • Created a Cloud Workload Prioritization framework to establish a priority order for applications moving to the Cloud.
  • Created an Application Gateway script that dramatically reduces the amount of time required to create and configure subdomains on the network. As a manual process, creating and configuring subdomains takes about 30 minutes for each one, but with the new script it takes only 2 minutes. The script contains all the accurate settings for the subdomains, which removes any chance of configuration errors, and therefore saves the team potential troubleshooting time. The script is shared in the GCAccelerators github.
  • Launched an Education Initiative as a way to create and distribute content to educate other teams in TC about Cloud migration and operations. As one of the first steps in this initiative, an onboarding checklist was created to help teams understand the steps involved in their journey to the Cloud.
  • Created an Assessment Scorecard as a way to assess the criticality of moving applications to the Cloud and create a priority order. This scorecard will assist ARB with a technical understanding of the applications in the migration pipeline so they can make a decision about the migration priority order.
  • All active TC employees (7,079) have been on-boarded to MS Teams.
  • Active Directory Federation Services (ADFS) is now available for Cloud-based applications at TC. ADFS provides users with single sign-on capabilities by establishing a link between TC’s Azure Active Directory and the on-premise Active Directory. This reduces the amount of usernames and passwords required to log on to Cloud-based applications.
  • TC has received the Memorandum of Understanding (MoU) from TBS for $1.27M for Cloud Migration activities, and it has been signed by Philippe Johnston (Director General, Digital Services Directorate).
  • Completed implementation of security controls required for Protected-B Cloud environment.
  • Completed assessment of TC's applications for readiness to be migrated to the Cloud.
  • Contracted industry Cloud expertise to assist to create, configure, and train TC FTE staff.
  • Established the foundational Cloud environment, Hybrid Cloud Management (HCM), to start accepting workloads.
  • As part of Culture change to adopt Cloud, 37 (formal and informal) Training sessions, 11 Technical Talks, 33 Awareness building roadshows, and four TC-wide Cloud engagement sessions have been completed.
  • TC is sharing with other GC Agencies and Departments the Azure Network Template Generator via the GitHub repository.
  • Adoption of DevSecOps and modern development methodologies that are enhanced by Cloud services – Working in Agile, Open, Collaboration.
  • Dedicated TC Cloud Centre of Excellence (#TC3OE) has been established.          

Overview of Transport Canada’s Cloud Centre of Excellence (#TC3OE)[edit | edit source]

TC3OE is Transport Canada’s Cloud Centre of Excellence. The TC3oE team is enabling the delivery of modern digital solutions by leveraging the Agility, Flexibility, Elasticity, and Disaster Recovery features of Cloud technologies. The team supports and maintains the Cloud foundational infrastructure, and aids designers in the planning, procurement, configuration and integration of Cloud services, so that TC clients can quickly address their rapidly changing business needs.

#TC3OE can be contacted via email at: TC.Cloud-Infonuagique.TC@tc.gc.ca

Here is a photo of our outstanding team!

TC3OE team 18dec2019.jpg

Challenges: Risks and Issues[edit | edit source]

RISK: SCED pilot has begun with two applications: PGS and eBIDA, but there are 370+ other applications to migrate to the Cloud, so the overall project schedule may still be delayed. After the SCED pilot is complete, it will be clearer how long SCED implementation will take for the other applications. Impact: High. Probability: Medium. Mitigation: Ongoing assessment of project schedule as SCED implementation develops, and continue to migrate non-SCED dependent apps.                  

RISK: There are 27 capital projects that have a dependency on this project for Cloud foundation infrastructure, workload migration, and SCED. Delivery of these 27 capital projects may be delayed, due to the delay in getting SCED. Impact: High. Probability: High. Mitigation: Create on-premise implementations for the 27 capital projects that can be easily migrated to the Cloud when SCED becomes available.

ISSUE: Resource availability and schedule constraints. Impact: Medium. Resolution Plan: The 67H3 project manager is actively prioritizing the workload, working with strategic partners to ensure the availability of skilled people, and the TC3oE team is taking on some of the workload from the teams that are moving their apps to the Cloud.

ISSUE: Cloud technology is new and is rapidly evolving, creating a steep learning curve for TC developers, cyber security experts, and operations teams which is impacting the project schedule. Impact: Medium. Resolution Plan: The adoption of DevSecOps is expected to alleviate this problem because expertise from SSC and the rest of TC can be leveraged. Digital Services management is equipping the team with the necessary tools, and ensuring the team is trained in Cloud technology, including Q&A sessions and training with the vendor.

ISSUE: GC EARB approved partial funding for 20/21 fiscal year ($2.7M out of $7.7M) and the amount is insufficient for the planned work. Impact: Medium. Resolution Plan: Planned work will be adjusted according to the level of funding and/or additional funding will be sought from within TC.      

Guidance and Documentation[edit | edit source]

Workload Migration Categorizations (Business Applications in Scope)[edit | edit source]

Data was sourced from the previous Microsoft Assessment.

Security Classification No Active Directory Dependency No Connectivity Requires Active Directory Requires Connectivity with EDC SQL Database Total
Unclassified 84 21 40 103 7 124
Protected A 87 9 60 138 5 147
Protected B 46 8 9 47 4 55
Total 217 38 109 288 16 326

Application Workload Migration via Agile Sprints[edit | edit source]

This project is following an iterative Agile process to migrate applications to the Cloud.

The following applications have already been migrated to the Cloud: Open Data, Alexa Recalls, TC Search, Navigable Waters Act Registry, eGIS, TC WWW, MEDV, iServer, and NWAR-ESS.

App/Platform State Description
Not Started Work has not yet started on migrating the app/platform to Cloud.
Planning Initial planning underway to determine timeframe for migrating app/platform to Cloud.
Doing Tasks actively in progress with no blockers.
NPRD Non-Production. App is ready for review in the NPRD environment prior to moving to PROD.
PROD Production. App is in the PROD environment and ready for review, testing/cut over.
Blocked Blocking issue is impeding further progress.
Done App is in PROD and functioning as expected.
Apps/Platforms In Progress Current State Notes
ASD NPRD Confirming if ATO has been received and if the application can move to PROD.
eBIDA NPRD Related to COVID-19 response. Part of SCED pilot. ATO received. Taking a phased release approach. Phase 1 moving to PROD.
CARTES Doing Database created in Azure. Initial report export to SSRS files, further review/development required. Working on migrating Access Queries to SQL Azure.
CCM Planning Initial planning underway.
ECATS Planning Related to COVID-19 response. Workload Intake Form and architecture diagrams received, currently being reviewed by TC3oE team.
GC Docs Planning Initial planning underway.
MISS Planning Initial planning underway.
MMERS Planning Migration plan in progress.
PGS Planning Related to COVID-19 response. Part of SCED pilot. Initial interview conducted, data gathering in progress.
RPA CoE Planning Related to COVID-19 response. Migration plan in progress.
SAP-BI NPRD Certificate installed and connection tested. Requesting DNS creation from SSC.
SRF Planning Migration plan created.
Tachyon and ActiveEfficiency Planning Initial planning underway.
TCLR API Planning Initial planning underway.
TCOMS Planning Related to COVID-19 response. Migration plan in progress.
TEAMMATE NPRD Performance testing in progress.
Vessel Registry Planning Initial planning underway.
ZAMMAD Planning Migration plan in progress.
Blocked Apps/Platforms Current State Notes
LDPS Blocked Lowest priority for business unit.
myTC Blocked Dev resources required elsewhere.
CUMULUS Blocked Looking for a replacement, plan to use CUMULUS until this is found. Decision needed on effort and value to complete Cloud migration.
Upcoming Apps/Platforms Current State Notes
BALLAST INTERVENTIONS Not Started
BASE NAVIRES Not Started
CVSA Not Started
Digital Signatures Not Started Related to COVID-19 response. SaaS app (DocuSign), will not migrate.
FORMATION Not Started
FORMATION_WEB Not Started
INC_POLL 2014 Not Started
MTCO-SMTC Not Started
PRET Not Started
PROFIL-FORMNAX Not Started
PROJETCERTI Not Started
PWS (BC) Not Started
QAIMS Not Started
SIVP-VISP Not Started
TO_LAND Not Started
TRAVERSES Not Started
TSCM Not Started Related to COVID-19 response.


Business Drivers and Timeline for TC's Journey to the Cloud[edit | edit source]

Journey-to-Cloud-June2020-v2.jpg

BusinessDriversForModernization-June2020.jpg