510
edits
Changes
Transport Canada (TC) Infrastructure Modernization - Cloud / DR / Workload Migration (view source)
Revision as of 14:50, 29 October 2020
, 14:50, 29 October 2020no edit summary
|-
|-
|'''RISK'''
|'''RISK'''
|If the SCED pilot for PGS and eBIDA takes longer than expected, then SCED implementation for 370+ other applications/platforms by March 2023 may be delayed. This would cause a delay to the overall project schedule, which means that not all applications/platforms would be migrated to the Cloud by the time MacDonald Cartier Data Centre (MCDC) closes in March 2023.
|If the SCED pilot for PGS and eBIDA takes longer than expected, then SCED implementation for 370+ other applications/platforms by March 2023 may be delayed.
|-
|-
|'''Impact'''
|'''Impact'''
|-
|-
|'''Mitigation'''
|'''Mitigation'''
|Ongoing assessment of project schedule as SCED implementation develops, and continue to migrate non-SCED dependent apps. If the overall project schedule is delayed, some applications/platforms may not be accessible for a certain amount of time and/or an on-premise interim solution will need to be built for them, until they can move to the Cloud.
|Ongoing assessment of project schedule as SCED implementation develops, and continue to migrate non-SCED dependent apps.
|}
|}
|-
|-
|'''RISK'''
|'''RISK'''
|If the overall project schedule is delayed due to SCED, then delivery of the 27 capital projects that have a dependency on this project for Cloud foundation infrastructure, workload migration, and SCED, may be delayed as well. This would mean that TC will not be able to meet service, regulatory, policy, and legal requirements for the respective projects, which will impact the safety and security of the Canadian public.
|If net new applications/platforms are added to project scope, then work on other priority applications/platforms must stop, negatively impacting the project schedule.
|-
|-
|'''Impact'''
|'''Impact'''
|High
|Medium
|-
|-
|'''Probability'''
|'''Probability'''
|High
|Medium
|-
|-
|'''Mitigation'''
|'''Mitigation'''
|Create on-premise implementations for the 27 capital projects that can be easily migrated to the Cloud when SCED becomes available. If the overall project schedule is delayed, we will work with the capital project teams to produce mitigation plans.
|Assess and prioritize new applications and adjust project schedule accordingly. Submit change request if end date of project needs to move.
|}
|}
|-
|-
|'''RISK'''
|'''RISK'''
|Future years' funding not confirmed: If TC does not receive the required funding from the TBS App Modernization program, then the migration activities will be negatively impacted, leading to schedule pressure, and TC's inability to proceed with the GC Cloud-first strategy.
|If application/platform teams do not have enough capacity, then workload migration to the Cloud stalls, delaying the project schedule.
|-
|-
|'''Impact'''
|'''Impact'''
|Medium
|Medium
|-
|-
|'''Escalation'''
|'''Mitigation'''
|Migration of workloads to the Cloud results in cost savings for the GC and SSC in particular. Negotiations with SSC will need to be held to fund the operation of workloads that are migrated to the Cloud.
|Engage each application/platform team early in the process and escalate accordingly if there is not enough capacity.
|}
|}
|-
|-
|'''ISSUE'''
|'''ISSUE'''
|Lack of resources and a constrained schedule may cause the project to extend past the current timeframe, which would require more funding and may impact the GC strategy to shut down the MacDonald Cartier Data Centre (MCDC) by March 2023.
|Ongoing application assessments show that teams with applications/systems dependent on SCED/Oracle DBs are choosing not to prepare for migration at this time, causing significant delays to the migration schedule.
|-
|-
|'''Impact'''
|'''Impact'''
|Medium
|High
|-
|-
|'''Resolution Plan'''
|'''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.
|Acquire OCI to provide Oracle solutions in the Cloud, and continue to use the Application Prioritization Framework to assess readiness for migration.
|}
|}
|-
|-
|'''ISSUE'''
|'''ISSUE'''
|Limited Cloud expertise in the areas of network infrastructure, security, and server configuration. TC is having to build Cloud operations teams to support workloads in the Cloud, and SSC teams manage the on-premise infrastructure, so there is an opportunity to leverage their expertise.
|Given the current project constraints, such as SCED, Oracle, stakeholder, and resource availability, we will not be able to meet our forecast milestone dates.
|-
|-
|'''Impact'''
|'''Impact'''
|-
|-
|'''Resolution Plan'''
|'''Resolution Plan'''
|The adoption of DevSecOps is expected to alleviate this issue 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.
|Create and implement stakeholder engagement plan.
|}
|}
|-
|-
|'''ISSUE'''
|'''ISSUE'''
|There are currently two funding issues:
|Create approach to engage Enterprise Architects (EAs) in identifying migration vs modernization candidates for moving applications/platforms to the Cloud.
|-
|-
|'''Impact'''
|'''Impact'''
|High
|Medium
|-
|-
|'''Resolution Plan'''
|'''Resolution Plan'''
|A funding strategy will be created and planned work will be adjusted according to the level of funding and/or additional funding will be sought from within TC.
|EAs are currently being engaged to address this issue.
|}
|}