60
edits
Changes
Transport Canada (TC) Infrastructure Modernization - Cloud / DR / Workload Migration (view source)
Revision as of 16:02, 13 December 2019
, 16:02, 13 December 2019Update for the 13th of December
== Project Status ==
== Project Status ==
This project will use where possible the Agile methodology, following the TC Project Management Office Framework.
This project will use where possible the Agile methodology, following the TC Project Management Office Framework 4 Gate model.
{| class="wikitable"
TC Azure Cloud foundation build activities and planning for the migration of applications into the Cloud are on track; overall the project is behind schedule due to the issue of the delay of secure network connectivity (a Protected B "Cloud to Ground" connection) and authentication services (Active Directory - AD). This issue is also causing delays to operationalizing the TC Cloud Foundational Environments and other projects (GC-Docs, ZEV). The Protected B Cloud environment (Azure) has been granted a Protected B "Authority to Operate" (ATO) for applications not requiring "Cloud to Ground" connectivity and AD. In order to progress and to validate the migration process, a list of unclassified applications for migration to the Cloud has been created, that do not require "Cloud to Ground" connectivity and AD to an SSC Enterprise Data Centre. Phase 3 of the project (define the migration process and migrate first set of applications) has contract approval and is now commencing. The project has been reviewed and approved by TBS via the GC-EARB review process.
{| class="wikitable mw-collapsible"
|'''Milestones'''
|'''Milestones'''
|'''Initial Target Date'''
|'''Initial Target Date'''
|2019-10-18
|2019-10-18
|2019-10-18
|2019-10-18
|Complete: This is the Cloud Working environment for TC applications
|Complete (minus "Cloud to Ground" "SCED" networking infrastructure): This is the Cloud Working environment for TC applications
|-
|-
|Protected B Application in Pilot
| colspan="5" |
|2019-10-18
|-
|-
|Gate 2 – Business Case approval
| colspan="5" |
|2019-09-30
|-
|-
|Gate 2 Phase 3 – Project Execution approval
|Gate 2 Phase 3 – Project Execution approval
* Deployed 1 Protected B application in pilot – MISS (Major Investigations Specialists Software)
* Deployed 1 Protected B application in pilot – MISS (Major Investigations Specialists Software)
* 40 application workloads currently in pre-production (development, testing, pilot) in Cloud
* 40 application workloads currently in pre-production (development, testing, pilot) in Cloud
* Completed implementation of security controls required for Protected-B Cloud environment
* 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
* 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
* Contracted industry Cloud expertise to assist to create, configure, and train TC FTE staff
=== Risks: ===
=== Risks: ===
* There is a risk that dependencies from Enterprise Architecture (Target State Cloud Architecture), Data Management (Data Strategy; updated data management policies), IT Security (Updated Risk Management approach), and Solutions Centre (Cloud-Native development framework) will delay aspects of the project – Impact: Low – Probability: Medium
* Resourcing is a high risk, since there is a potential of a lack of resources 1) for application developers due to other projects and schedules colliding with major deliverables; 2) in obtaining support resources for the Cloud due to this skill set being in high demand at this time. – Impact: Medium – Probability: High
'''Mitigation'''- Work with the appropriate groups to expedite deliverables. Cyber Security has approved an updated IT Security Risk Management approach using a Security Assessment & Authority (SA&A).
'''Mitigation''' - The team will strive to mitigate this risk through high-level program management and close coordination with Managers and Directors. Support from senior management across various projects will be needed to ensure that initiatives, inter-dependencies and resource conflicts are highlighted. Senior management will also need to get involved to prioritize and resolve conflicts as required.
* Transport Canada has dependencies in the Cloud environment to provide Disaster Recovery services for critical business applications. There is a risk that this will not materialize due to delays in the delivery of Cloud Protected B services – Impact: Medium – Probability: High
* Cloud technology is a new paradigm for TC developers, and as well is a fast changing technology environment for support staff, creating a steep learning curve. - Impact: Medium – Probability: Medium
'''Mitigation''' - Work with and the Cloud service providers to expedite the delivery and to prioritize critical applications once the cloud environment is available. Availability of the Cloud environment is continuing to be impacted by the delayed delivery of connectivity from "Cloud to Ground" (now scheduled for April, 2020).
'''Mitigation''' - TC management must include Cloud based training for staff in the training plans, as well, staff needs to take advantage of the vendor workshops, demos, and other venues that the Cloud support team has organized.
* Schedule is a low impact risk as there are mitigation plans in place for the currently listed risks (connectivity, resourcing). - Impact: Low – Probability: High
'''Mitigation''' - The Project Manager will mitigate the risk by conducting weekly meetings and focus on which deliverables to manage, while at the same time keeping the project end date on track. Mitigation plans are in place for schedule delays due to the current risks. Scheduling challenges are immediately communicated to senior management.
=== Issues: ===
=== Issues: ===