Difference between revisions of "Application Modernization"

From wiki
Jump to navigation Jump to search
m
 
(127 intermediate revisions by 3 users not shown)
Line 2: Line 2:
 
@en|
 
@en|
  
−
'''''Note: We are continuously improving this site. As the initiative attracts more attention, we are trying to publish the information we have as we have it. A French version will follow shortly.'''''
+
'''''Note:''''' We are continuously improving this site and information is published as we receive it. Templates and discussions related to Application Modernization can be found in the [[gccollab:file/group/1432343/all#1727776|GCCollab Core Technologies group]]. It is recommended you join that group to watch for updates. '''''Check out [https://wiki.gccollab.ca/Application_Modernization#References_.26_What.27s_New What's New] and the Discussion tab above for the latest updates !'''''
  
−
'''''Templates and discussions related to Application Modernization can be found in the [[gccollab:file/group/1432343/all#1727776|GCCollab Core Technologies group]]. It is strongly recommended you join that group to watch for updates.'''''
+
{| class="wikitable"
 +
|-
 +
! Year 1 – 2018-19
 +
! Year 2 – 2019-20
 +
! Year 3 – 2020-21
 +
! Year 4 – 2021-22
 +
! Year 5 – 2022-23
 +
|-
 +
| $4,000,000
 +
(disbursed)
 +
| $20,000,000
 +
(disbursed)
 +
| $40,000,000
 +
(disbursed)
 +
| $35,000,000
 +
(disbursed)
 +
| $11,000,000
 +
($ 9,124,586 in process)
 +
|-
 +
|}
 +
 
 +
<!-- BACKGROUND -->
 +
== Background ==
 +
From [https://www.budget.gc.ca/2018/docs/plan/chap-04-en.html#Enabling-Digital-Services-to-Canadians Budget 2018:]
 +
 
 +
''"$110 million over six years, starting in 2018–19, to be accessed by Shared Services Canada’s partner departments and agencies to help them migrate their applications from older data centres into more secure modern data centres or cloud solutions."''
 +
 
 +
Application Modernization is one of four pillars of the Workload Migration & Cloud Enablement (WLM&CE) initiative.
 +
<!-- END OF BACKGROUND -->
  
 
<!-- OVERVIEW -->
 
<!-- OVERVIEW -->
 
== '''Overview''' ==
 
== '''Overview''' ==
−
This handbook is meant to help departments navigate the Application Modernization Investment Framework; the process for:
+
This handbook is meant to help departments navigate the Application Modernization Investment Framework; and other topic of interest:
 
* Prioritizing at-risk technologies
 
* Prioritizing at-risk technologies
−
* Engaging with partner departments
+
* Engaging with [https://www.canada.ca/en/shared-services/corporate/partner-organizations.html partner departments]
 
* Performing an analysis of departmental application portfolios
 
* Performing an analysis of departmental application portfolios
 
* Planning for addressing the at-risk technologies through modernization
 
* Planning for addressing the at-risk technologies through modernization
 
* Governance gating for endorsing modernization/migration plan and making the associated funds available
 
* Governance gating for endorsing modernization/migration plan and making the associated funds available
 
* Ongoing monitoring of status
 
* Ongoing monitoring of status
−
This handbook focuses on the decisions departments must make and how they are captured. It is not meant to provide a deep analysis of different technical decisions or architectural strategies a department can use to modernize, save for those captured in policy instruments.
+
 
  
 
The Investment Frame work consists of two gates:
 
The Investment Frame work consists of two gates:
Line 21: Line 49:
 
'''Gate 1''': a scope of at-risk technologies has been identified and approved by governance for modernization or decommissioning  
 
'''Gate 1''': a scope of at-risk technologies has been identified and approved by governance for modernization or decommissioning  
  
−
'''Gate 2''': a department's plan for modernization is ready to be endorsed by GC EARB thus authorizing the release of Application Modernization funds.
+
'''Gate 2''': a department's plan for modernization is ready to be endorsed by governance thus authorizing the release of Application Modernization funds.
 +
 
  
 
The Investment Framework also consists of four phases:
 
The Investment Framework also consists of four phases:
Line 27: Line 56:
 
'''Prioritization''': priorities for modernizing at-risk technologies are selected and endorsed by governance.
 
'''Prioritization''': priorities for modernizing at-risk technologies are selected and endorsed by governance.
  
−
<strong>Engagement</strong>: notify impacted departments, distribute templates to capture technical details, modernization/migration strategies, costing details and reporting dashboard.
+
<strong>Engagement</strong>: notify impacted departments, distribute templates to capture technical details, modernization/migration strategies, and costing details.
  
 
'''Discovery''': departments analyze their application portfolios to determine their strategies for modernizing at-risk technologies including a plan and cost estimates.
 
'''Discovery''': departments analyze their application portfolios to determine their strategies for modernizing at-risk technologies including a plan and cost estimates.
Line 33: Line 62:
 
'''Execution''': departments work with their partners to execute the modernization strategies identified during the discovery phase.
 
'''Execution''': departments work with their partners to execute the modernization strategies identified during the discovery phase.
  
−
The image below provides a pictorial view of a department's journey through the Investment Framework, or can also be found [[gccollab:file/view/1957351/enoverview-of-the-customer-journeyfr|here]] in downloadable document form.
+
A department's journey through the Investment Framework, or can also be found [[gccollab:file/view/1957351/enoverview-of-the-customer-journeyfr|here]] in downloadable document form.
 
<!-- APPLICATION MODERNIZATION IMAGE -->
 
<!-- APPLICATION MODERNIZATION IMAGE -->
 
[[File:DepartmentalJourney.png|alt=Application Modernization Investment Framework|center|frame|Application Modernization Investment Framework - Departmental Journey]]
 
[[File:DepartmentalJourney.png|alt=Application Modernization Investment Framework|center|frame|Application Modernization Investment Framework - Departmental Journey]]
 +
Please review the brief Frequently Asked Questions [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ].
 
<!-- END OF OVERVIEW -->
 
<!-- END OF OVERVIEW -->
−
 
−
<!-- BACKGROUND -->
 
−
=== Background ===
 
−
Application Modernization is one of four pillars of the Workload Migration & Cloud Enablement (WLM&CE) initiative. A brief Frequently Asked Questions [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ] document can be found here.
 
−
 
−
From [https://www.budget.gc.ca/2018/docs/plan/chap-04-en.html#Enabling-Digital-Services-to-Canadians Budget 2018:]
 
−
 
−
''"$110 million over six years, starting in 2018–19, to be accessed by Shared Services Canada’s partner departments and agencies to help them migrate their applications from older data centres into more secure modern data centres or cloud solutions."''
 
−
<!-- END OF BACKGROUND -->
 
  
 
<!-- PRIORITIZATION -->
 
<!-- PRIORITIZATION -->
 
== '''Prioritization''' ==
 
== '''Prioritization''' ==
  
−
Priorities for investment from the Application Modernization and Workload Migration funds are based upon identifying high business value applications that are impacted by at-risk technologies. These at risk technologies can include, amongst other things, end of life software, end of life infrastructure, outdated architectures, to be decommissioned facilities such as data centres, etc…  
+
Priorities for investment from the Application Modernization and Workload Migration funds are based upon identifying high business value applications that are impacted by at-risk technologies. These at risk technologies can include, end of life software, end of life infrastructure, outdated architectures, to be decommissioned facilities such as data centres, etc…  
  
−
1) To stabilize the IT landscape and ensure continuity of services to Canadians, TBS and SSC are working in collaboration with GC departments that demonstrate a readiness to modernize applications and migrate them to end state hosting platforms (cloud or enterprise data centres).
+
1) TBS and SSC are working in collaboration with GC departments that demonstrate a readiness to modernize applications and migrate them to end state hosting platforms ([https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] or enterprise data centres).
  
−
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment. If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program.
+
2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment.  
  
−
To facilitate the prioritization process, [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template] has been provided for departments to complete. This template, once completed, can be brought forward to your Departmental Architecture Review Board before being brought forward to request endorsement by governance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group], [[GC EARB]], ADM CEPP, and DM CEPP). The request for endorsement is a department’s opportunity to make a strong business case for investment to address at-risk technologies.
+
If endorsed by [https://wiki.gccollab.ca/Application_Modernization#Governance governance], those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program. Departments are required to complete the '''[https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr a GCEARB Gate1 (Prioritization) template]''' and engage your Departmental Architecture Review Board before being brought forward to request endorsement by governance:
 +
* [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group]
 +
* [[GC EARB]]
 +
* ADM SEP
 +
* DM CEPP
  
−
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework (described on this page), and the strategy that will be used to modernize (rehost, replatform, refactor, replace and to which hosting platform; data centre or cloud services)
+
The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework, and the modernization strategy that will be used (rehost, replatform, refactor, replace and to which hosting platform; data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services)
  
−
In 2018, the following data centre facilities were identified as at-risk technologies to be decommissioned and the applications to be migrated or modernized to a new data centre or cloud services.
+
In 2018, the following data centre facilities were identified as at-risk technologies to be decommissioned and the applications to be migrated or modernized to a new enterprise data centre or [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services. The first wave of workload migration projects began in 2018 and the second wave began in 2019:
−
 
+
{| class="wikitable"
−
The first wave of workload migration projects began in 2018:
+
|-
−
* Tunney’ Pasture DC (Statistics Canada)
+
! Wave
−
* Dorval DC (Environment and Climate Change Canada)
+
! Department
−
* Aviation Parkway DC (22 partner department tenants)
+
! Discovery
−
* St. Laurent DC (Canada Revenue Agency and Canada Border Services Agency)
+
! Execution
−
* Booth Street DC (Natural Resources Canada)
+
|-
−
* Goldenrod DC (Department of National Defence)
+
| 1
−
''(insert approved wave 2 list of priorities Oct. 10)''
+
| Statistics Canada <sup>1</sup>
 +
|
 +
| X
 +
|-
 +
| 1
 +
| Treasury Board of Canada Secretariat <sup>1</sup>
 +
|
 +
| X
 +
|-
 +
| 1
 +
| Canada Border Services Agency
 +
| X
 +
| X
 +
|-
 +
| 1
 +
| Canada Revenue Agency
 +
| X
 +
| X
 +
|-
 +
| 1
 +
| Department of National Defense
 +
| X
 +
|
 +
|-
 +
| 1
 +
| Environment and Climate Change Canada
 +
| X
 +
|
 +
|-
 +
| 1
 +
| Natural Resources Canada
 +
| X
 +
| X
 +
|-
 +
| 1
 +
| Royal Canadian Mounted Police
 +
| X
 +
|
 +
|-
 +
| 2
 +
| Canadian Food Inspection Agency
 +
|
 +
| X
 +
|-
 +
| 2
 +
| Correctional Services Canada
 +
| X
 +
| X
 +
|-
 +
| 2
 +
| Employment and Social Development Canada
 +
| X
 +
|
 +
|-
 +
| 2
 +
| Global Affairs Canada
 +
| X
 +
| X
 +
|-
 +
| 2
 +
| Health Canada
 +
| X
 +
|
 +
|-
 +
| 2
 +
| Innovation, Science and Economic Development
 +
| X
 +
| X
 +
|-
 +
| 2
 +
| Privy Council Office
 +
| X
 +
| X
 +
|-
 +
| 2
 +
| Public Health Agency Canada
 +
| X
 +
|
 +
|-
 +
| 2
 +
| Public Services and Procurement Canada
 +
| X
 +
|
 +
|-
 +
| 2
 +
| Transport Canada
 +
|
 +
| X
 +
|}
 +
<sub>1</sub>Pathfinder
 
<!-- END OF PRIORITIZATION -->
 
<!-- END OF PRIORITIZATION -->
−
 
−
<!-- GOVERNANCE -->
 
−
== '''Governance''' ==
 
−
[[Image:WLM Governance.png]]
 
−
<!-- END OF GOVERNANCE -->
 
  
 
<!-- ENGAGEMENT -->
 
<!-- ENGAGEMENT -->
 
== '''Engagement''' ==
 
== '''Engagement''' ==
  
−
Once priorities are reached and the impacted partner departments are notified, the Application Modernization starter kit package, along with application modernization handbook and [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ] documents are provided. This package contains [https://gccollab.ca/file/view/2650400/engeneric-wlm-app-mod-gcearb-gate1-prioritizationfr| GC EARB Gate 1 (Prioritization) template], [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|App Mod Cost estimates template]] (used to identify funding requirements), Departmental & Data Centre View dashboard, Application Risk Review dashboard, and [https://gccollab.ca/file/view/3088763/engeneric-wlm-app-mod-business-casefr| Business case template].  Partner departments are provided guidance/assistance throughout the engagement journey.
+
Once priorities are reached and departments are notified, the TBS-OCIO project manager will provide guidance and tools to start the department's journey.
 +
 
 +
* [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ]
 +
* [https://gccollab.ca/file/view/2649702/engeneric-wlm-app-mod-gcearb-gate1-discoveryfr| GC EARB Gate 1 (Discovery) template]
 +
* [https://wiki.gccollab.ca/images/0/0e/SamplePortfolioAnalysis.png Departmental & Data Centre View dashboard]
 +
* [https://gccollab.ca/file/view/3088763/engeneric-wlm-app-mod-business-casefr| Business case template].   
 +
 
 +
[https://www.canada.ca/en/shared-services/corporate/partner-organizations.html partner departments] are provided guidance/assistance to provide an accurate list of applications by updating the APM and to prepare for the [https://wiki.gccollab.ca/Application_Modernization#Governance governance] endorsement. 
 +
* [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group]
 +
* [[GC EARB]]
 +
* ADM SEP
 +
* DM CEPP)
  
−
Partner Departments are endorsed by governance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail WLM Working group], [[GC EARB]], ADM CEPP, and DM CEPP) and funding becomes available to initiate the discovery phase. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr| Memorandum of Understanding] between the Government of Canada’s Chief Information Officer (GC CIO) and the Deputy Head of a department will be agreed upon by both parties to secure the funding.
+
Once endorsed, the Chief Information Officer of Canada (GC CIO) and the Deputy Head of a department signs the  '''[https://gccollab.ca/file/view/9003565/engeneric-wlm-app-mod-mou-fund-disbursement-enfr| Memorandum of Understanding]'''.
 
<!-- END OF ENGAGEMENT -->
 
<!-- END OF ENGAGEMENT -->
 +
 +
[[Image:Discovery Swimlanes.png]]
  
 
<!-- DISCOVERY -->
 
<!-- DISCOVERY -->
Line 92: Line 214:
  
 
==== <big>Determine Modernization Vision for the Organization</big> ====
 
==== <big>Determine Modernization Vision for the Organization</big> ====
−
By the end of this step, you should have discussed with leadership how far you want to take your modernization journey. This will be the vision for your organization. Those who will be performing the subsequent portfolio analysis steps should understand that vision.
+
This is an opportunity to determine the direction for the organization and ensure those performing the subsequent portfolio analysis steps understand the vision to modernize and be more transformative! Perhaps your organization has already begun a modernization journey. In today's IT environment [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary:      
−
 
+
* Deliver IT faster
−
This is an opportunity to determine the direction for the organization; is it to largely sustain current operations and culture, or does the organization desire to modernize and be more transformative. Perhaps your organization has already begun a modernization journey. In today's IT environment cloud technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary     
 
−
* deliver IT faster
 
−
 
 
 
* Increase reliability
 
* Increase reliability
 
* Increase security
 
* Increase security
 
* Increase quality  
 
* Increase quality  
−
This guide does not instruct an organization how to undertake its modernization journey, but instead is meant to be a catalyst for establishing the vision. These changes can be wide sweeping impacting roles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement.  
+
These changes can be wide sweeping impacting roles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement. While some organizations have started this journey years ago and are ready to go "all in" on [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] and the workforce are DevOps practitioners, others have not begun the journey.  
−
 
 
−
While some organizations have started this journey years ago and are ready to go "all in" on cloud and the workforce are DevOps practitioners, others have not begun the journey.  
 
  
−
For those who have not yet begun a modernization journey the choice may be take this opportunity to start that journey. For others, they may decide to simply sustain operations as-is.
+
Here is a simple visual for plotting your [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] adoption .
  
 
[[Image:Cloud maturity map .png]]
 
[[Image:Cloud maturity map .png]]
  
−
A simple visual for plotting you cloud adoption maturity can be found here. Most organizations start small with a few low risk applications. A team of willing and keen developers from within your existing workforce would lead an initative to migrate those low risk workloads to the cloud. From these experiences they would use their learnings to train others to do the same. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. An organization should review the [insert roles and reap document here] to ensure your organization is ready to undertake the required roles to support cloud services.
+
Start small with a few low risk applications. A team of developers from within your existing workforce would lead an initiative to migrate those low risk workloads to the [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud]. The build from these experiences and transfer these skills to train others. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. Review the [https://gccollab.ca/file/view/3691530/engc-cloud-rr-matrixfr GC Cloud R&R Matrix] to ensure your organization is ready to undertake the required roles to support [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] services.
−
 
 
−
A [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple scorecard]] has been devised to assess low risk workloads for cloud migration. This scorecard is meant to provide you a short list from which to further decide where to start. Any application can be migrated to the cloud with enough time and effort. The scorecard is meant to identify low risk and low effort migrations.
 
  
−
For organizations that desire to forego modernization opportunities, the decision to rehost the entire application portfolio to a new data centre provides that opportunity.
+
See the [[gccollab:file/view/1994079/encloud-fitness-scorecardfr|simple cloud fitness scorecard]] to assess low risk workloads for cloud migration. It provides a short list to help with the decision as to where to start and to identify low risk and low effort migrations. Any application can be migrated to the [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud] with enough time and effort.  
  
 
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
 
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
Line 123: Line 238:
  
 
===== <u>Obsolete Applications</u> =====
 
===== <u>Obsolete Applications</u> =====
−
Your application portfolio rates the business value of applications. Review low business value applications. Assess whether these applications remain needed:
+
Your application portfolio rates the business value of applications. Review low business value applications. Assess whether these applications are still needed:
 
* Use access/update logs to identify applications that have received few updates in the past two years.
 
* Use access/update logs to identify applications that have received few updates in the past two years.
 
* Identify the most recent users and inquire as to the business value of the application. 
 
* Identify the most recent users and inquire as to the business value of the application. 
  
 
==== <big>Document Migration Strategy and Targets</big> ====
 
==== <big>Document Migration Strategy and Targets</big> ====
−
By the end of this step you will have analyzed your portfolio of applications, updated key data in APM, chose the migrations strategy for each application ( one of the 5 Rs ), and the target for each application ( cloud or EDC ).
+
By the end of this step you will have analyzed your portfolio of applications, updated key data in APM, chose the [https://gccollab.ca/file/group/1432343/all#5335607 migration strategy] for each application (one of the 5 Rs), and the target for each application (cloud or EDC).
−
 
 
−
During the Determine Modernization Vision for the Organization step you would have determine how far your organization wants to take its modernization journey. Part of that step was the Cloud Fit Scorecard. You should have already narrowed the target options for each application.  
 
  
 
===== '''<u>Choose the Appropriate Migration Strategy</u>''' =====
 
===== '''<u>Choose the Appropriate Migration Strategy</u>''' =====
Line 143: Line 256:
 
|-
 
|-
 
| Retire
 
| Retire
−
| Decomission
+
| Decommission
 
| Retire, decommission, sunset application. Eliminate it from the portfolio.
 
| Retire, decommission, sunset application. Eliminate it from the portfolio.
 
|  
 
|  
Line 168: Line 281:
 
| Replace
 
| Replace
 
| Repurchase
 
| Repurchase
−
| Replace application's functionality by a new solution acquired or developed by department (medium to large investment of resources). The application will be decommissioned once replaced.
+
| Replace application's functionality with a new solution acquired or developed by department (medium to large investment of resources). The application will be decommissioned once replaced.
 
|  
 
|  
 
|X
 
|X
Line 177: Line 290:
 
With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.  
 
With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.  
  
−
For workloads migrating to cloud, it is strongly advised that, at the very least, the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.  
+
For workloads migrating to [https://wiki.gccollab.ca/GC_Cloud_Infocentre cloud], it is strongly advised that the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.  
  
 
====== '''Replatform (lift, shift, and tinker)''' ======
 
====== '''Replatform (lift, shift, and tinker)''' ======
 
With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:
 
With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:
  
−
Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/policy-implementation-notices.html ITPINs]
+
* Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology/policy-implementation-notices.html ITPINs]
−
 
+
* Moving to Platform-as-a-Service (PaaS) for commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture.  
−
Move to Platform-as-a-Service (PaaS). For commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture. A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT Lifecycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.
+
A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT Lifecycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.
  
 
Containers is an increasingly popular method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.
 
Containers is an increasingly popular method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.
Line 198: Line 311:
  
 
====== '''Replace (Repurchase)''' ======
 
====== '''Replace (Repurchase)''' ======
−
This is an opportunity to determine if Software-as-a-Service solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.
+
This is an opportunity to determine if Software-as-a-Service (SaaS) solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.
  
 
===== '''<u>Choose Your Migration Target</u>''' =====
 
===== '''<u>Choose Your Migration Target</u>''' =====
Line 205: Line 318:
 
''Enterprise Data Centre (EDC):'' a new data centre with low technical risks
 
''Enterprise Data Centre (EDC):'' a new data centre with low technical risks
  
−
''Cloud:'' a public cloud service provider available from the SSC Cloud Broker
+
''Cloud:'' a public cloud service provider available from the [https://cloud-broker.canada.ca/s/?language=en_CA SSC GC Cloud Brokering Service]
  
 
===== '''<u>Identify Data Centre</u>''' =====
 
===== '''<u>Identify Data Centre</u>''' =====
Line 217: Line 330:
  
 
===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====
 
===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====
−
Request that TBS generate a dashboard of your application portfolio. This will ensure your decisions have been correctly reflected. A sample of the dashboard that is generated is found here:
+
Request that TBS generate a dashboard of your application portfolio. This will ensure your decisions have been correctly reflected. A sample of the dashboard that is generated is found here:  
  
 
[[File:SamplePortfolioAnalysis.png|1000x1000px|center|alt=Sample Application Portfolio Analysis]]
 
[[File:SamplePortfolioAnalysis.png|1000x1000px|center|alt=Sample Application Portfolio Analysis]]
Line 228: Line 341:
 
[[File:SampleRoadmapAnalysis.png||alt=Sample Roadmap for Modernization]]
 
[[File:SampleRoadmapAnalysis.png||alt=Sample Roadmap for Modernization]]
  
−
=== ''Document Cost Estimates'' ===
 
−
An [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|App Mod Cost estimates template]] has been devised to identify cost estimates. A Memorandum of Understanding between the GC CIO and the Deputy Head of a department will be agreed upon by both parties to secure the funding for execution phase. The MoU generic template can be found here (insert template).
 
  
 
=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===
 
=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===
−
At this point the discovery phase is completed. The analysis and planning undertaken as part of discovery will be presented to GC EARB as part of requesting endorsement for releasing funds for the execution phase.
 
  
−
The [https://gccollab.ca/file/view/2649702/engeneric-wlm-app-mod-gcearb-gate1-discoveryfr generic template] for the presenting your discovery analysis and funding approval to move to execution.
+
=== '''NEW! Application Modernization Technical Assessment report=== '''
  
−
As part of the GC EARB a CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy requirement (requirement 6.4.2) and meeting requirement 6.1.1 of the Directive..
+
The Application Modernization Technical Assessment provides the rationale used in identifying application complexities and associated strategies for each application, both of which are key components in determining funding allocations. The Technical Assessment is an excel spreadsheet with a list of applications sent to departments to respond to the Application Complexity and Proposed Strategy for each application as well as a short list of [https://gccollab.ca/file/view/9592990/entechnical-assessment-questionsfr questions].  Once reviewed by the TBS project manager, the department is requested to present to the  [https://gccollab.ca/file/group/1896301/all#9322590 Enterprise Architecture Community of Practice] to solicit their input.
 +
The goal is to provide guidance and support to partner departments in:
 +
* Prioritizing the GC’s Cloud First approach
 +
* Aligning with IT horizontal solutions
 +
* Supporting the decommissioning of at-risk technologies
 +
* Supporting modernization strategies that are technically sound and innovative
 +
The analysis and planning undertaken as part of discovery will be presented to the [https://wiki.gccollab.ca/Application_Modernization#Governance governance] structure as part of requesting endorsement for releasing funds for the execution phase. The '''[https://gccollab.ca/file/view/2650673/engeneric-wlm-app-mod-gcearb-gate2-executionfr generic template]''' is to be completed to present the discovery analysis and funding approval to move to the execution phase.
  
−
If and when endorsement is provided by GC EARB, approval will be requested from the GC CIO. A [https://gccollab.ca/file/view/3089069/enmou-generic-fund-disbursement-v3docxfr Memorandum of Understanding] between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.
+
The department's CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy (Cloud First 4.4.1.9 / Data Residency 4.4.1.10 / Non-Public Cloud GC EARB Assessments 4.1.1.2.4) of the [https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601  Directive on Service and Digital]. If and when endorsement is provided, approval will be requested from the GC CIO. A '''[https://gccollab.ca/file/view/9003565/engeneric-wlm-app-mod-mou-fund-disbursement-enfr Memorandum of Understanding]''' between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.
  
 
=== ''Reporting Requirements'' ===
 
=== ''Reporting Requirements'' ===
−
As per section 3: Reporting Requirements of the signed MOU between your department and TBS, the executive project dashboard is due at the end of  each quarter. Please find the [https://intranet.canada.ca/wg-tg/go-sg/docs/epd-tbdp.xls Executive project dashboard tool] to be used to report the status of your modernization strategies to the TBS Oversight Team. This is a standard template that is used to monitor projects with further [https://intranet.canada.ca/wg-tg/go-sg/dwnld-eng.asp instructions]if required can be found here:  .
+
As per section 3: Reporting Requirements of the signed MOU between your department and TBS, the executive project dashboard is due at the end of  each quarter. Please find the '''[https://gccollab.ca/file/view/6712988/enwlm-appmod-quarterly-reporting-dashboardfr Quarterly Reporting Dashboard tool]''' to be used to report the status of your modernization strategies to the TBS Oversight Team. This is a standard template that is used to monitor projects with [https://intranet.canada.ca/wg-tg/go-sg/dwnld-eng.asp instructions].
 
<!-- END OF DISCOVERY -->
 
<!-- END OF DISCOVERY -->
  
Line 247: Line 363:
 
== '''Execution''' ==
 
== '''Execution''' ==
  
−
Once priorities are reached the impacted partner departments are notified, and Application Modernization starter kit package, along with application modernization handbook and FAQ documents are provided. This package contains GC EARB template, App Mod Cost estimates template (used to identify funding requirements), Departmental & Data Centre View dashboard, Application Risk Review dashboard, and Business case template.   
+
With the execution funds now received, the analysis and planning undertaken as part of discovery will be now be executed in order to close the legacy data centre. Departments are still required to submit quarterly reporting dashboards based on the funding received and to provide input into the status of their application modernization/migration journey by breaking down how the funds are spent, documenting milestones, risks and issues.  Feedback and guidance will be received from the TBS project manager as required. The information is also collected to form part of the status report on the WLM program to the WLM governance structure.
 +
 
 +
[[Image:Execution Swimlanes v1.png]]
  
−
Partner departments are provided guidance/assistance throughout the engagement journey.
 
−
Partner Departments are endorsed by governance (WLM Working group, GC EARB, ADM CEPP, and DM CEPP) and funding becomes available to initiate the discovery phase. A Memorandum of Understanding between the Government of Canada’s Chief Information Officer (GC CIO) and the Deputy Head of a department will be agreed upon by both parties to secure the funding.
 
 
<!-- END OF EXECUTION -->
 
<!-- END OF EXECUTION -->
  
−
<!-- LESSONS LEARNED -->
+
<!-- CLOSE OUT -->
−
== '''Lessons Learned''' ==
+
== '''Close Out''' ==
 +
 
 +
=== '''Lessons Learned''' ===
  
 
<b>Change is hard.</b> Cloud requires a major culture shift in the organization, especially in IT as it means radical transformation to some roles. Do not underestimate the fear that people will have. Organizational change management must be at the forefront.
 
<b>Change is hard.</b> Cloud requires a major culture shift in the organization, especially in IT as it means radical transformation to some roles. Do not underestimate the fear that people will have. Organizational change management must be at the forefront.
Line 272: Line 390:
  
 
<b>Be like water</b> You have to work with a singular vision and purpose, but you have to be like water otherwise.  The landscape in the cloud is ever changing - gone are the days of set it and forget it.  Also, politically, there are always changes too - so you must be prepared to pivot when needed.  eg. Pathfinder, APDC Closure, desktop, etc...
 
<b>Be like water</b> You have to work with a singular vision and purpose, but you have to be like water otherwise.  The landscape in the cloud is ever changing - gone are the days of set it and forget it.  Also, politically, there are always changes too - so you must be prepared to pivot when needed.  eg. Pathfinder, APDC Closure, desktop, etc...
−
<!-- END OF LESSONS LEARNED -->
 
  
−
<!-- REFERENCES -->
+
=== '''Benefits realization''' ===
−
== '''References''' ==
+
 
 +
Technology transformation projects with benefits realization management aligns strategic goals with project lifecycles. This helps contribute to a more efficient core business processes. Listed below are some of the benefits have been realized after TBS’s migration from a legacy data centre to cloud.
 +
 
 +
* Completely eliminated technical debt
 +
* Modernized our whole environment (PaaS, SaaS)
 +
* Adopted DevOps and automation
 +
* Gained end to end visibility and monitoring capabilities
 +
* Stronger Security posture
 +
* Resilience and fault tolerance
 +
 
 +
What benefits do you foresee to be realized?  See [https://www.canada.ca/en/treasury-board-secretariat/services/information-technology-project-management/project-management/outcome-management-guide-tools.html Outcome Management Guide and Tools].
 +
 
 +
<!-- END OF CLOSE OUT -->
 +
 
 +
<!-- REFERENCES & WHAT'S NEW -->
 +
== '''References & What's New''' ==
 +
====== '''WHAT'S NEW''' ======
 +
[https://gccollab.ca/file/view/9635053/enrenewed-cloud-adoption-strategy-vision-measures-principlesfr?utm_source=notification&utm_medium=email Renewed Cloud Adoption Strategy Vision, Measures, Principles]
 +
 
 +
[https://gccollab.ca/file/group/1432343/all#5335607 DEPARTMENTAL CLOUD STRATEGIES]
 +
 
 +
[https://wiki.gccollab.ca/GC_Cloud_Infocentre Cloud Infocentre]
 +
 
 +
[https://www.gcpedia.gc.ca/wiki/OCIO_Application_Portfolio_Management/Aging_IT_Application_Assessment OCIO Application Portfolio Management/Aging IT Application Assessment]
 +
 
 +
[https://gccollab.ca/file/group/2731824/all#5536103 Enterprise IT Service Standards] - Standard on; IT Profile, IT Entitlements, IT Service Common Configurations, Enterprise IT Service Usage Restrictions and more!
 +
 
 +
TBS [https://wiki.gccollab.ca/GC_Enterprise_Architecture/Enterprise_Solutions#Security_Architecture_and_Privacy GC Enterprise Architecture/Enterprise Solutions]
 +
 
 +
[https://gccollab.ca/file/view/6331829/en complianceweek-accelerating-protected-workloads-sept-2020fr Accelerating Protected Workloads (Sept 2020)]
 +
 
 +
[https://api.canada.ca/en/homepage API Store] [https://gccollab.ca/groups/profile/1466411/enapi-storefrmagasin-api API GC Collab]
 +
 
 +
[https://www.gcpedia.gc.ca/gcwiki/images/c/c5/GC_Zero_Trust_Security_Concept.pdf Zero Trust Security Concept PDF (Aug-2020)]
 +
 
 +
[https://www.gcpedia.gc.ca/wiki/Zero_Trust_Security Zero Trust Security (Jul-2020)]
 +
 
 +
 
 +
[https://wiki.gccollab.ca/Workload_Migration_(WLM)_Program Workload Migration SSC WLM Program]
 +
 
 +
[https://ssc-clouddocs.canada.ca/ SSC Cloud document portal]
 +
 
 +
SSC [https://gccollab.ca/groups/profile/4209321/enssc-cpmsd-cloud-adoption-playbooksfrgroupe-de-ru00e9vision-des-documents-dadoption-de-linformatique-en-nuage-pru00e9paru00e9-par-la-dsgpi Cloud Adoption Playbooks]
 +
 
 +
(Jan-2021) Visit the [https://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gcpedia.gc.ca%2Fwiki%2FM365-playbook%2Fhome&data=04%7C01%7Cnicole.koch%40tbs-sct.gc.ca%7C2e5e1b863a354b3bf49708d8bc8d7a3b%7C6397df10459540479c4f03311282152b%7C0%7C0%7C637466663110726935%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aVRNmcoUkdFO7xIuqyT7qKXuWbMlluBrCKssZNQcDJA%3D&reserved=0 M365 Playbook on GCpedia]
 +
 
 +
PSPC [https://www.gcpedia.gc.ca/wiki/En/GCPS EA and GC Programs and Solutions]
 +
 
 +
The Canada School of Public Service (CSPS) Digital Academy is offering a virtual  learning program: [https://learn-apprendre.csps-efpc.gc.ca/application/en/content/getting-started-cloud-computing-i621-0 Getting Started with Cloud Computing]
 +
 
 +
[https://gccollab.ca/discussion/view/5344264/enstratosphere-2020fr Stratosphere Cloud Event]
 +
 
 +
[https://youtu.be/GzyNlkiCbeE FWDThinking Episode 5.2: Showing What’s Possible—an extended interview with Minister Murray]
 +
 
 +
[https://gccollab.ca/file/view/3671533/enworkload-placement-in-hybrid-it-gartnerfr Gartner: Workload Placement in Hybrid IT]
 +
 
 +
[https://youtu.be/OJeoNYvsoT4 DPI - Charting a path to success for Workload Migration: Approaches and Best Practices]
 +
 
 
====== '''TB Policies & Standards''' ======
 
====== '''TB Policies & Standards''' ======
−
[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=12755&section=html Policy on Management of Information Technology]
+
[https://www.canada.ca/en/government/system/digital-government/government-canada-digital-operations-strategic-plans/digital-operations-strategic-plan-2021-2024.html Digital Operations Strategic Plan: 2021-2024]
 +
 
 +
[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=32601  Directive on Service and Digital]
  
 
[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=16578 Policy on Government Security]
 
[https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=16578 Policy on Government Security]
  
−
[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/direction-electronic-data-residency.html Direction for Electronic Data Residency, ITPIN No: 2017-02]
+
[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/direction-secure-use-commercial-cloud-services-spin.html Direction on the Secure Use of Commercial Cloud Services: Security Policy Implementation Notice (SPIN)]
 +
 
 +
====== '''Guidance''' ======
  
−
[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/direction-secure-use-commercial-cloud-services-spin.html Direction of the Secure Use of Commercial Cloud Services: Security Policy Implementation Notice (SPIN)]
+
[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/government-canada-cloud-adoption-strategy.html Government of Canada Cloud Adoption Strategy]
  
−
====== '''Guidance''' ======
+
[https://canada-ca.github.io/digital-playbook-guide-numerique/en/overview.html Government of Canada Digital Playbook]
  
−
[https://canada-ca.github.io/digital-playbook-guide-numerique/en/overview.html Government of Canada Digital Playbook (draft)]
+
[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/security-playbook-information-system-solutions-cloud.html Security Playbook for Information System Solutions]
  
−
[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/cloud-services/government-canada-security-control-profile-cloud-based-it-services.html Government of Canada Security Control Profile for Cloud-Based GC IT Services]
+
[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/government-canada-security-control-profile-cloud-based-it-services.html Government of Canada Security Control Profile for Cloud-Based GC IT Services]
  
−
[https://www.canada.ca/en/government/system/digital-government/modern-emerging-technologies/cloud-services/cloud-security-risk-management-approach-procedures.html Government of Canada Cloud Security Risk Management Approach and Procedures]
+
[https://www.canada.ca/en/government/system/digital-government/digital-government-innovations/cloud-services/cloud-security-risk-management-approach-procedures.html Government of Canada Cloud Security Risk Management Approach and Procedures]
  
 
[https://cyber.gc.ca/en/guidance/baseline-security-requirements-network-security-zones-government-canada-itsg-22 CSE ITSG-22 Baseline Security Requirements for Network Security Zones in the Government of Canada]
 
[https://cyber.gc.ca/en/guidance/baseline-security-requirements-network-security-zones-government-canada-itsg-22 CSE ITSG-22 Baseline Security Requirements for Network Security Zones in the Government of Canada]
Line 315: Line 493:
  
 
[https://medium.com/core-technologies/5-4-3-2-1-cloud-a904f99d56cd 5–4–3–2–1 — Cloud!]
 
[https://medium.com/core-technologies/5-4-3-2-1-cloud-a904f99d56cd 5–4–3–2–1 — Cloud!]
−
<!-- END OF REFERENCES -->
+
<!-- END OF REFERENCES & WHAT'S NEW -->
 +
 
 +
<!-- GOVERNANCE -->
 +
== '''Governance''' ==
 +
 
 +
'''[https://gccollab.ca/file/view/7293070/enprioritization-endorsement-timelinefr Prioritization/Endorsement critical path]'''
 +
 
 +
[[Image:WLM Governance.png]]
 +
<!-- END OF GOVERNANCE -->
  
 
@fr|
 
@fr|
Line 360: Line 546:
 
=== Contexte ===
 
=== Contexte ===
  
−
La modernisation des applications constitue l’un des quatre piliers de l’initiative Migration de la charge de travail et habilitation en nuage (MCT et HN). Un court document de foire aux questions est accessible ici [https://www.budget.gc.ca/2018/docs/plan/chap-04-fr.html#Enabling-Digital-Services-to-Canadians Budget de 2018:].
+
La modernisation des applications constitue l’un des quatre piliers de l’initiative Migration de la charge de travail et habilitation en nuage (MCT et HN). Un court document de foire aux questions est accessible ici: [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ].
−
Extrait du Budget de 2018 :
+
 
 +
Extrait [https://www.budget.gc.ca/2018/docs/plan/chap-04-fr.html#Enabling-Digital-Services-to-Canadians Budget de 2018:]
  
 
'''« 110 millions de dollars sur six ans, à compter de 2018-2019, auquel les ministères et organismes partenaires de Services partagés Canada accéderont pour les aider à faire la migration de leurs applications de vieux centres de données vers des centres de données plus sécurisés ou vers des solutions infonuagiques ».'''
 
'''« 110 millions de dollars sur six ans, à compter de 2018-2019, auquel les ministères et organismes partenaires de Services partagés Canada accéderont pour les aider à faire la migration de leurs applications de vieux centres de données vers des centres de données plus sécurisés ou vers des solutions infonuagiques ».'''
Line 375: Line 562:
 
2) Les ministères peuvent relever comme investissements prioritaires les applications à valeur organisationnelle élevée qui sont touchées par différentes technologies à risque. Une fois approuvées par la gouvernance, ces priorités pourront bénéficier du fonds de modernisation des applications et des mesures de soutien prévues par le programme de migration de la charge de travail.  
 
2) Les ministères peuvent relever comme investissements prioritaires les applications à valeur organisationnelle élevée qui sont touchées par différentes technologies à risque. Une fois approuvées par la gouvernance, ces priorités pourront bénéficier du fonds de modernisation des applications et des mesures de soutien prévues par le programme de migration de la charge de travail.  
  
−
Pour faciliter le processus d’établissement de l’ordre des priorités, [https://gccollab.ca/file/view/3399063/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-priorisationpptx un modèle pour le point de contrôle 1 du CEAI GC (établissement de l’ordre des priorités)] a été fourni aux ministères afin d’être rempli. Après l’avoir rempli, les ministères pourront présenter ce modèle à leur conseil d’examen de l’architecture avant de le présenter à la gouvernance [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail groupe de travail sur la MCT] [[groupe de travail sur la MCT]], Comité des sous-ministres adjoints sur les priorités et la planification intégrées (SMA CPPI) et Comité des sous-ministres sur les priorités et la planification intégrées (SM CPPI)) aux fins d’approbation. La demande d’approbation permet au ministère de présenter une rigoureuse analyse de rentabilisation pour les investissements afin d’aborder les technologies à risque.  
+
Pour faciliter le processus d’établissement de l’ordre des priorités, [https://gccollab.ca/file/view/3399063/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-priorisationpptx un modèle pour le point de contrôle 1 du CEAI GC (établissement de l’ordre des priorités)] a été fourni aux ministères afin d’être rempli. Après l’avoir rempli, les ministères pourront présenter ce modèle à leur conseil d’examen de l’architecture avant de le présenter à la gouvernance [https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail groupe de travail sur la MCT] [https://wiki.gccollab.ca/GC_EARB CEAI GC], Comité des sous-ministres adjoints sur les priorités et la planification intégrées (SMA CPPI) et Comité des sous-ministres sur les priorités et la planification intégrées (SM CPPI)) aux fins d’approbation. La demande d’approbation permet au ministère de présenter une rigoureuse analyse de rentabilisation pour les investissements afin d’aborder les technologies à risque.  
 
   
 
   
 
L’approbation des technologies à risque doit être appuyée par les données de la gestion du portefeuille des applications (GPA), par l’état de préparation pour aller de l’avant avec le cadre de modernisation des applications (décrit dans la présente) et par la stratégie de modernisation (réhéberger, remonter, réusiner, remplacer en indiquant par quelle la plateforme d’hébergement, quel centre de données ou quel service d’informatique en nuage).  
 
L’approbation des technologies à risque doit être appuyée par les données de la gestion du portefeuille des applications (GPA), par l’état de préparation pour aller de l’avant avec le cadre de modernisation des applications (décrit dans la présente) et par la stratégie de modernisation (réhéberger, remonter, réusiner, remplacer en indiquant par quelle la plateforme d’hébergement, quel centre de données ou quel service d’informatique en nuage).  
Line 381: Line 568:
 
En 2018, les installations de centres de données qui suivent ont été assimilées à des technologies à risque devant être mises hors service, alors que les applications ont été désignées comme devant être modernisées ou transférées vers un nouveau centre de données ou de nouveaux services d’informatique en nuage.   
 
En 2018, les installations de centres de données qui suivent ont été assimilées à des technologies à risque devant être mises hors service, alors que les applications ont été désignées comme devant être modernisées ou transférées vers un nouveau centre de données ou de nouveaux services d’informatique en nuage.   
 
La première vague de projets de migration de la charge de travail a été lancée en 2018 :  
 
La première vague de projets de migration de la charge de travail a été lancée en 2018 :  
−
• Centre de données du pré Tunney (Statistique Canada)
+
* Statistique Canada
 +
* Environnement et Changement climatique Canada
 +
* Agence du revenu du Canada, Agence des services frontaliers du Canada.
 +
* Ressources naturelles Canada
 +
* ministère de la Défense nationale
  
−
• Centre de données de Dorval (Environnement et Changement climatique Canada)
+
La 2ièm vague de projets de migration de la charge de travail a été lancée en 2019:
−
• Centre de données de la promenade de l’Aéroport (22 locataires des ministères partenaires)
+
* Transports Canada                              
−
• Centre de données Saint-Laurent (Agence du revenu du Canada, Agence des services frontaliers du Canada.)
+
* Agence canadienne d'inspection des aliments
−
• Centre de données de la rue Booth (Ressources naturelles Canada)
+
* Innovation, Sciences et Développement économique Canada
−
• Centre de données de Goldenrod (ministère de la Défense nationale)
+
* Emploi et Développement social Canada (Montréal et Moncton)
−
(Insérez la liste de priorités approuvée de la vague 2 du 10 octobre.)  
+
* Bureau du Conseil privé                           
 +
* Affaires mondiales Canada                       
 +
* Services publics et Approvisionnement Canada (PdP III)      
  
 
<!-- Gouvernance -->
 
<!-- Gouvernance -->
Line 397: Line 590:
 
<!-- Mobilisation -->
 
<!-- Mobilisation -->
 
== '''Mobilisation''' ==
 
== '''Mobilisation''' ==
−
Une fois que l’on a atteint les priorités et avisé les ministères partenaires touchés, on fournit la trousse de départ sur la modernisation des applications, de même que le guide de modernisation des applications et les documents de [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ]. Cette trousse comporte le [https://gccollab.ca/file/view/3399063/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-priorisationpptx modèle pour le point de contrôle 1 du CEAI GC (établissement des priorités)], le modèle d’estimation des coûts liés à la modification des applications (utilisé pour relever les exigences en matière de financement), le tableau de bord Vue du ministère et centre de données, le tableau de bord sur l’examen des risques liés aux applications et le [https://gccollab.ca/file/view/3423530/enfrmodu00e8le-du2019analyse-de-rentabilisationdoc| modèle d’analyse de rentabilisation]. Les ministères partenaires reçoivent de l’aide et du soutien tout au long de la mobilisation.
+
Une fois que l’on a atteint les priorités et avisé les ministères partenaires touchés, on fournit la trousse de départ sur la modernisation des applications, de même que le guide de modernisation des applications et les documents de [https://gccollab.ca/file/view/1760164/enfaq-wlm-app-mod-enfrfaq-wlm-app-mod-en| FAQ]. Cette trousse comporte le [https://gccollab.ca/file/view/3399890/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-1-du00e9couvertepptx| Générique Mod app et MCT- Point de contrôle 1 (découverte)], le tableau de bord Vue du ministère et centre de données, et le [https://gccollab.ca/file/view/3423530/enfrmodu00e8le-du2019analyse-de-rentabilisationdoc| modèle d’analyse de rentabilisation]. Les ministères partenaires reçoivent de l’aide et du soutien tout au long de la mobilisation. Un nouveau modèle de calcul du financement est en cours d'élaboration et sera prêt à être utilisé d'ici fin juin 2020.
  
−
Les ministères partenaires reçoivent l’approbation de la gouvernance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail groupe de travail sur la MCT] [[groupe de travail sur la MCT]], SMA CPPI et le SM CPPI), qui rend accessible le financement pour lancer l’étape de la découverte. Un protocole d’entente est conclu entre le dirigeant principal de l’information du gouvernement du Canada et l’administrateur général d’un ministère en vue de l’obtention du financement.  
+
Les ministères partenaires reçoivent l’approbation de la gouvernance ([https://gccollab.ca/groups/profile/2006418/enworkload-migration-working-groupfrgroupe-de-travail-sur-la-migration-des-charges-de-travail groupe de travail sur la MCT],  [https://wiki.gccollab.ca/GC_EARB CEAI GC], SMA CPPI et le SM CPPI), qui rend accessible le financement pour lancer l’étape de la découverte. Un protocole d’entente est conclu entre le dirigeant principal de l’information du gouvernement du Canada et l’administrateur général d’un ministère en vue de l’obtention du financement.  
  
 
<!-- END OF Mobilisation -->
 
<!-- END OF Mobilisation -->
Line 538: Line 731:
  
 
[[File:SampleRoadmapAnalysis.png||alt=
 
[[File:SampleRoadmapAnalysis.png||alt=
−
 
−
Un [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|modèle pour les estimations des coûts associés à la modernisation des applications]] a été élaboré afin de relever les estimations de coûts. Un protocole d’entente (PE) sera conclu entre le dirigeant principal de l’information (DPI) du GC et l’administrateur général du ministère afin d’assurer le financement de l’étape de la mise en œuvre. Le modèle générique de ce PE est accessible ici (insérez le modèle).
 
  
 
=== ''Point de contrôle 2 : Approbation du CEAI GC et PE visant à libérer les fonds'' ===
 
=== ''Point de contrôle 2 : Approbation du CEAI GC et PE visant à libérer les fonds'' ===
Line 545: Line 736:
 
L’étape de la découverte est terminée à ce stade-ci. L’analyse et la planification réalisées à cette étape seront présentées au CEAI GC dans le cadre de la demande d’approbation de la libération de fonds pour la mise en œuvre.  
 
L’étape de la découverte est terminée à ce stade-ci. L’analyse et la planification réalisées à cette étape seront présentées au CEAI GC dans le cadre de la demande d’approbation de la libération de fonds pour la mise en œuvre.  
  
−
Le modèle générique permettant la présentation de votre analyse des découvertes et de votre approbation de financement pour la mise en œuvre est accessible [[gccollab.ca/file/view/3399890/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-1-du00e9couvertepptx|ici]].
+
Le modèle générique permettant la présentation de votre analyse des découvertes et de votre approbation de financement pour la mise en œuvre est accessible [[https://gccollab.ca/file/view/4672976/enfrgu00e9nu00e9rique-mod-app-et-mct-point-de-contru00f4le-2-exu00e9cution]].
  
 
Dans le cadre du CEAI GC, un dirigeant principal de l’information (DPI) expliquera la stratégie de migration et les choix ciblés. Il expliquera, entre autres, dans quelle mesure ces choix respectent l’exigence de la politique de l’informatique en nuage d’abord (exigence 6.4.2) et l’exigence 6.1.1 de la Directive.  
 
Dans le cadre du CEAI GC, un dirigeant principal de l’information (DPI) expliquera la stratégie de migration et les choix ciblés. Il expliquera, entre autres, dans quelle mesure ces choix respectent l’exigence de la politique de l’informatique en nuage d’abord (exigence 6.4.2) et l’exigence 6.1.1 de la Directive.  
Line 552: Line 743:
 
<!-- END OF DISCOVERY -->
 
<!-- END OF DISCOVERY -->
 
<!-- EXECUTION -->
 
<!-- EXECUTION -->
−
=== ''Mise en œuvre'' ===
+
=== '''Mise en œuvre''' ===
−
 
+
Une fois que l’on a atteint les priorités, on en avise les ministères partenaires et on fournit la trousse de départ sur la modernisation des applications, le guide sur la modernisation des applications et le document de FAQ. Cette trousse comporte le modèle du CEAI GC, le tableau de bord Vue du ministère et centre de données, le tableau de bord sur l’examen des risques liés aux applications et le modèle d’analyse de rentabilisation.
−
Une fois que l’on a atteint les priorités, on en avise les ministères partenaires et on fournit la trousse de départ sur la modernisation des applications, le guide sur la modernisation des applications et le document de FAQ. Cette trousse comporte le modèle du CEAI GC, le modèle d’estimation des coûts associés à la modernisation des applications (utilisé pour relever les exigences en matière de financement), le tableau de bord Vue du ministère et centre de données, le tableau de bord sur l’examen des risques liés aux applications et le modèle d’analyse de rentabilisation.
 
  
 
Les ministères partenaires reçoivent de l’aide et du soutien tout au long de la mobilisation. Les ministères partenaires sont appuyés par la gouvernance (groupe de travail sur la MCT, CEAI GC, SMA CPPI et SM CPPI), qui rend accessible le financement pour lancer l’étape des découvertes. Un protocole d’entente sera conclu entre le dirigeant principal de l’information (DPI) du gouvernement du Canada (GC) et l’administrateur général du ministère afin d’assurer le financement.  
 
Les ministères partenaires reçoivent de l’aide et du soutien tout au long de la mobilisation. Les ministères partenaires sont appuyés par la gouvernance (groupe de travail sur la MCT, CEAI GC, SMA CPPI et SM CPPI), qui rend accessible le financement pour lancer l’étape des découvertes. Un protocole d’entente sera conclu entre le dirigeant principal de l’information (DPI) du gouvernement du Canada (GC) et l’administrateur général du ministère afin d’assurer le financement.  
Line 579: Line 769:
 
<!-- Références -->
 
<!-- Références -->
 
== '''Références''' ==
 
== '''Références''' ==
 +
Consultez le Guide sur [://can01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.gcpedia.gc.ca%2Fwiki%2FM365-playbook%2Fhome&data=04%7C01%7Cnicole.koch%40tbs-sct.gc.ca%7C2e5e1b863a354b3bf49708d8bc8d7a3b%7C6397df10459540479c4f03311282152b%7C0%7C0%7C637466663110726935%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aVRNmcoUkdFO7xIuqyT7qKXuWbMlluBrCKssZNQcDJA%3D&reserved=0 M365 sur GCpédia]
 +
 
====== '''Politiques et normes du Conseil du Trésor''' ======
 
====== '''Politiques et normes du Conseil du Trésor''' ======
 
[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=12755&section=html Politique sur la gestion de la technologie de l’information]
 
[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=12755&section=html Politique sur la gestion de la technologie de l’information]
  
 
[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=16578 Politique sur la sécurité du gouvernement]
 
[https://www.tbs-sct.gc.ca/pol/doc-fra.aspx?id=16578 Politique sur la sécurité du gouvernement]
−
 
−
[https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/technologiques-modernes-nouveaux/orientation-relative-residence-donnees-electroniques.html Orientation relative à la résidence des données électroniques, AMPTI no : 2017-02]
 
−
 
−
[https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/technologiques-modernes-nouveaux/orientation-utilisation-securisee-services-commerciaux-informatique-nuage-amops.html Orientation sur l’utilisation sécurisée des services commerciaux d’informatique en nuage : Avis de mise en œuvre de la Politique sur la sécurité (AMOPS)]
 
  
 
====== '''Orientation''' ======
 
====== '''Orientation''' ======
  
 
[https://canada-ca.github.io/digital-playbook-guide-numerique/fr/apercu.html Guide numérique du gouvernement du Canada (ébauche)]
 
[https://canada-ca.github.io/digital-playbook-guide-numerique/fr/apercu.html Guide numérique du gouvernement du Canada (ébauche)]
−
 
−
[https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/technologiques-modernes-nouveaux/services-informatique-nuage/profil-controle-securite-services-ti-fondes-information-nuage.html Profil des mesures de sécurité pour les services du GC fondés sur l’informatique en nuage]
 
−
 
−
[https://www.canada.ca/fr/gouvernement/systeme/gouvernement-numerique/technologiques-modernes-nouveaux/services-informatique-nuage/approche-procedures-gestion-risques-securite-informatique-nuage.html Gouvernement du Canada Approche et procédures de gestion des risques à la sécurité de l’informatique en nuage]
 
  
 
[https://cyber.gc.ca/fr/orientation/exigences-de-base-en-matiere-de-securite-pour-les-zones-de-securite-de-reseau-au-sein Exigences de base en matière de sécurité pour les zones de sécurité de réseau au sein du gouvernement du Canada (ITSG-22)]
 
[https://cyber.gc.ca/fr/orientation/exigences-de-base-en-matiere-de-securite-pour-les-zones-de-securite-de-reseau-au-sein Exigences de base en matière de sécurité pour les zones de sécurité de réseau au sein du gouvernement du Canada (ITSG-22)]

Latest revision as of 12:16, 26 May 2022


Note: We are continuously improving this site and information is published as we receive it. Templates and discussions related to Application Modernization can be found in the GCCollab Core Technologies group. It is recommended you join that group to watch for updates. Check out What's New and the Discussion tab above for the latest updates !

Year 1 – 2018-19 Year 2 – 2019-20 Year 3 – 2020-21 Year 4 – 2021-22 Year 5 – 2022-23
$4,000,000

(disbursed)

$20,000,000

(disbursed)

$40,000,000

(disbursed)

$35,000,000

(disbursed)

$11,000,000

($ 9,124,586 in process)

Background[edit | edit source]

From Budget 2018:

"$110 million over six years, starting in 2018–19, to be accessed by Shared Services Canada’s partner departments and agencies to help them migrate their applications from older data centres into more secure modern data centres or cloud solutions."

Application Modernization is one of four pillars of the Workload Migration & Cloud Enablement (WLM&CE) initiative.

Overview[edit | edit source]

This handbook is meant to help departments navigate the Application Modernization Investment Framework; and other topic of interest:

  • Prioritizing at-risk technologies
  • Engaging with partner departments
  • Performing an analysis of departmental application portfolios
  • Planning for addressing the at-risk technologies through modernization
  • Governance gating for endorsing modernization/migration plan and making the associated funds available
  • Ongoing monitoring of status


The Investment Frame work consists of two gates:

Gate 1: a scope of at-risk technologies has been identified and approved by governance for modernization or decommissioning

Gate 2: a department's plan for modernization is ready to be endorsed by governance thus authorizing the release of Application Modernization funds.


The Investment Framework also consists of four phases:

Prioritization: priorities for modernizing at-risk technologies are selected and endorsed by governance.

Engagement: notify impacted departments, distribute templates to capture technical details, modernization/migration strategies, and costing details.

Discovery: departments analyze their application portfolios to determine their strategies for modernizing at-risk technologies including a plan and cost estimates.

Execution: departments work with their partners to execute the modernization strategies identified during the discovery phase.

A department's journey through the Investment Framework, or can also be found here in downloadable document form.

Application Modernization Investment Framework
Application Modernization Investment Framework - Departmental Journey

Please review the brief Frequently Asked Questions FAQ.

Prioritization[edit | edit source]

Priorities for investment from the Application Modernization and Workload Migration funds are based upon identifying high business value applications that are impacted by at-risk technologies. These at risk technologies can include, end of life software, end of life infrastructure, outdated architectures, to be decommissioned facilities such as data centres, etc…

1) TBS and SSC are working in collaboration with GC departments that demonstrate a readiness to modernize applications and migrate them to end state hosting platforms (cloud or enterprise data centres).

2) Departments may identify applications of high business value that are impacted by technology risks as a priority investment.

If endorsed by governance, those priorities will be eligible for access to Application Modernization funds and support from the Workload Migration program. Departments are required to complete the a GCEARB Gate1 (Prioritization) template and engage your Departmental Architecture Review Board before being brought forward to request endorsement by governance:

The endorsement of priority at-risk technologies must be supported by the departments’ Application Portfolio Management (APM) data, readiness to proceed with the application modernization framework, and the modernization strategy that will be used (rehost, replatform, refactor, replace and to which hosting platform; data centre or cloud services)

In 2018, the following data centre facilities were identified as at-risk technologies to be decommissioned and the applications to be migrated or modernized to a new enterprise data centre or cloud services. The first wave of workload migration projects began in 2018 and the second wave began in 2019:

Wave Department Discovery Execution
1 Statistics Canada 1 X
1 Treasury Board of Canada Secretariat 1 X
1 Canada Border Services Agency X X
1 Canada Revenue Agency X X
1 Department of National Defense X
1 Environment and Climate Change Canada X
1 Natural Resources Canada X X
1 Royal Canadian Mounted Police X
2 Canadian Food Inspection Agency X
2 Correctional Services Canada X X
2 Employment and Social Development Canada X
2 Global Affairs Canada X X
2 Health Canada X
2 Innovation, Science and Economic Development X X
2 Privy Council Office X X
2 Public Health Agency Canada X
2 Public Services and Procurement Canada X
2 Transport Canada X 
1Pathfinder

Engagement[edit | edit source]

Once priorities are reached and departments are notified, the TBS-OCIO project manager will provide guidance and tools to start the department's journey.

partner departments are provided guidance/assistance to provide an accurate list of applications by updating the APM and to prepare for the governance endorsement.

Once endorsed, the Chief Information Officer of Canada (GC CIO) and the Deputy Head of a department signs the Memorandum of Understanding.

Discovery Swimlanes.png

Discovery[edit | edit source]

Application Portfolio Analysis[edit | edit source]

The next three steps are an opportunity for your departments to assess its portfolio of applications and document your decisions as to how you will reduce, sustain, and modernize that portfolio.

Determine Modernization Vision for the Organization[edit | edit source]

This is an opportunity to determine the direction for the organization and ensure those performing the subsequent portfolio analysis steps understand the vision to modernize and be more transformative! Perhaps your organization has already begun a modernization journey. In today's IT environment cloud technologies combined with DevOps methods are having a large impact on how IT is delivered. Amongst the goals of these technologies and methods is to decrease lead time and time to market; in summary:

  • Deliver IT faster
  • Increase reliability
  • Increase security
  • Increase quality

These changes can be wide sweeping impacting roles, responsibilities, and culture. They are not undertaken in a year, but instead must be seen as a journey of maturity and continuous improvement. While some organizations have started this journey years ago and are ready to go "all in" on cloud and the workforce are DevOps practitioners, others have not begun the journey.

Here is a simple visual for plotting your cloud adoption .

Cloud maturity map .png

Start small with a few low risk applications. A team of developers from within your existing workforce would lead an initiative to migrate those low risk workloads to the cloud. The build from these experiences and transfer these skills to train others. As the number of workloads grow, the need for more sophisticated methods such as automation and DevOps will need to be applied. This will facilitate scaling without impacting agility. Existing governance and roles will also need to evolve. Review the GC Cloud R&R Matrix to ensure your organization is ready to undertake the required roles to support cloud services.

See the simple cloud fitness scorecard to assess low risk workloads for cloud migration. It provides a short list to help with the decision as to where to start and to identify low risk and low effort migrations. Any application can be migrated to the cloud with enough time and effort.

Determine Rationalization and Retirement Opportunities[edit | edit source]

By the end of this step you will have assessed your portfolio and infrastructure for rationalization and retirement opportunities.

Obsolete Repositories[edit | edit source]

There are GC applications – content management systems / web-database systems -  that are no longer actively used but maintained because they may contain information that might be required in the future e.g. to respond to an ATIP request.

  • Departments should have an active Information Management (IM) function that can verify the actual data retention requirements applicable to a specific application.
  • Departments should recognize the cost of unnecessary data retention and actively dispose of data that has been deemed unnecessary. Unnecessary data is both a cost and a liability.
Obsolete Applications[edit | edit source]

Your application portfolio rates the business value of applications. Review low business value applications. Assess whether these applications are still needed:

  • Use access/update logs to identify applications that have received few updates in the past two years.
  • Identify the most recent users and inquire as to the business value of the application. 

Document Migration Strategy and Targets[edit | edit source]

By the end of this step you will have analyzed your portfolio of applications, updated key data in APM, chose the migration strategy for each application (one of the 5 Rs), and the target for each application (cloud or EDC).

Choose the Appropriate Migration Strategy[edit | edit source]

For each application you need to determine you migration strategy (aka the 5Rs).

Strategy Alternative Name Full Description Data Centre Cloud
Retire Decommission Retire, decommission, sunset application. Eliminate it from the portfolio.
Rehost Lift and shift Redeploy applications to a different hardware environment and change the application’s infrastructure configuration. Also called Lift-and-shift. Move the solution as is, or with minor changes, to a new hosting environment (small investment of resources). X X
Replatform Lift, shift, and tinker Change OS / Middleware. Requiring some level of application change (medium investment of resources to change). X1 X
Refactor Re-architect Application will be redesigned. Sections of the application will be re-written for improvement/optimization purposes (medium to large investment of resources to change). X
Replace Repurchase Replace application's functionality with a new solution acquired or developed by department (medium to large investment of resources). The application will be decommissioned once replaced. X 
1Appropriate when addressing end of life OSes
Rehost (lift and shift)[edit | edit source]

With a rehost migration strategy, the application undergoes no changes and is migrated as-is to a new data centre or cloud. This is the simplest and least effort migration strategy.

For workloads migrating to cloud, it is strongly advised that the resources (network, compute, storage) be optimized and reduced to the smallest size possible. Additionally using reserved instances for production workloads and turning off unused servers during off-hours will help ensure a lower monthly bill from your cloud provider.

Replatform (lift, shift, and tinker)[edit | edit source]

With a replatform strategy, the application undergoes minor changes as it is migrated to a new data centre or cloud. Replatforming strategies may include, but as not limited to:

  • Addressing end of life (EOL) software such as those deprecated by IT Policy Implementation Notice ITPINs
  • Moving to Platform-as-a-Service (PaaS) for commoditized services such as databases, web servers, file servers, container orchestration, moving to a PaaS allows for a serverless architecture.

A serverless architecture negates the need to manage and patch operating systems, middleware and manage server instances. This also reduces an organization's IT Lifecycle Management burden. Users sometimes worry that using PaaS will cause vendor lock-in. By using PaaS that have alternatives elsewhere in the market will avoid lock-in. Being able to extract your business data and business rules from a PaaS is key to avoiding lock-in. Most cloud providers offer database, web server, and file server platforms. While migrating from one to another may not be completely painless, migration tools and APIs exist to allow for this possibility.

Containers is an increasingly popular method to deploy applications. If your application is stateless, moving it to a container will not only help portability, but also help with your organization's adoption of DevOps practices.

Refactor (Re-Architect)[edit | edit source]

Refactoring is the most costly and time consuming of all strategies. This is an opportunity to take full advantage of cloud-native architectures by introducing elastic scaling of resources.

Adding disaster recover capabilities is other option for refactoring.

Migrating away from less common OSes such AIX, UNIX, or Solaris may require extensive changes to the application.

Due to the high cost of refactoring, this strategy should only be applied to high business value applications.

Replace (Repurchase)[edit | edit source]

This is an opportunity to determine if Software-as-a-Service (SaaS) solutions for some of the COTS or custom built application you may have running today. Migrating to SaaS is an opportunity to access the latest version of that service and to lower lifecycle management burden. For example, if you operate a legacy email application, you may want to take the opportunity to replace it with Office 365.

Choose Your Migration Target[edit | edit source]

Choose the target, or where the application will be migrated to, for each application.

Enterprise Data Centre (EDC): a new data centre with low technical risks

Cloud: a public cloud service provider available from the SSC GC Cloud Brokering Service

Identify Data Centre[edit | edit source]

Ensure applications are correctly allocated to its current legacy data centre. The data centre is an essential reporting dimension when TBS tracks your portfolio's progress.

Identify Mission Critical Applications[edit | edit source]

Ensure mission critical applications are correctly identified.

Identify Operating Systems[edit | edit source]

Ensure the operating systems for each application are correctly identified. This will be used to ensure all operating systems beyond end-of-life are addressed through a replatform.

Generate Portfolio Analysis Dashboard[edit | edit source]

Request that TBS generate a dashboard of your application portfolio. This will ensure your decisions have been correctly reflected. A sample of the dashboard that is generated is found here:

Sample Application Portfolio Analysis

Engage SSC Project Manager and WLM Factory[edit | edit source]

It is likely you have already been working with your SSC Project Manager. If not, talk to your Service Delivery Manager. At this point it would be prudent to work with a supplier qualified on the WLM Factory to help with planning and cost estimates.

Document Project Milestones (Roadmap)[edit | edit source]

Sample Roadmap for Modernization


Gate2: GC EARB Endorsement and MoU to Release Funds[edit | edit source]

=== NEW! Application Modernization Technical Assessment report===

The Application Modernization Technical Assessment provides the rationale used in identifying application complexities and associated strategies for each application, both of which are key components in determining funding allocations. The Technical Assessment is an excel spreadsheet with a list of applications sent to departments to respond to the Application Complexity and Proposed Strategy for each application as well as a short list of questions. Once reviewed by the TBS project manager, the department is requested to present to the Enterprise Architecture Community of Practice to solicit their input.

The goal is to provide guidance and support to partner departments in:

  • Prioritizing the GC’s Cloud First approach
  • Aligning with IT horizontal solutions
  • Supporting the decommissioning of at-risk technologies
  • Supporting modernization strategies that are technically sound and innovative

The analysis and planning undertaken as part of discovery will be presented to the governance structure as part of requesting endorsement for releasing funds for the execution phase. The generic template is to be completed to present the discovery analysis and funding approval to move to the execution phase.

The department's CIO will explain their migration strategy and target choices. This includes how those choices align to the Cloud First policy (Cloud First 4.4.1.9 / Data Residency 4.4.1.10 / Non-Public Cloud GC EARB Assessments 4.1.1.2.4) of the Directive on Service and Digital. If and when endorsement is provided, approval will be requested from the GC CIO. A Memorandum of Understanding between the GC CIO and the deputy head of the requesting department will be agreed to by both parties.

Reporting Requirements[edit | edit source]

As per section 3: Reporting Requirements of the signed MOU between your department and TBS, the executive project dashboard is due at the end of each quarter. Please find the Quarterly Reporting Dashboard tool to be used to report the status of your modernization strategies to the TBS Oversight Team. This is a standard template that is used to monitor projects with instructions.

Execution[edit | edit source]

With the execution funds now received, the analysis and planning undertaken as part of discovery will be now be executed in order to close the legacy data centre. Departments are still required to submit quarterly reporting dashboards based on the funding received and to provide input into the status of their application modernization/migration journey by breaking down how the funds are spent, documenting milestones, risks and issues. Feedback and guidance will be received from the TBS project manager as required. The information is also collected to form part of the status report on the WLM program to the WLM governance structure.

Execution Swimlanes v1.png


Close Out[edit | edit source]

Lessons Learned[edit | edit source]

Change is hard. Cloud requires a major culture shift in the organization, especially in IT as it means radical transformation to some roles. Do not underestimate the fear that people will have. Organizational change management must be at the forefront.

Strong support required by deputy head and all levels of senior leadership. Due to the magnitude of change required and the underlying complexity, the senior management table MUST demonstrate consistent, strong leadership to ensure success.

Cloud is a journey, not a destination. It is very complex, and will take longer than you think. Start now, before you have all of the information. BUT – start smaller and simple, avoid serious injury when you fall. Because you will fall. Learn to crawl before trying to run. Fully embracing cloud will take years.

Partner with others. Having an integrated project team with SSC has been key success factor. Leverage the expertise of industry and of others that have gone before you.

Strong support required by deputy head and all levels of senior leadership.

Shallow pool of resources with the required expertise. Resources are routinely targeted by other departments and private sector. Ability to attract and retain talent is key, and is very challenging in public sector environment.

Products may not be as advertised. While the products may be released as GA, and have been tested on the open market, they do not necessarily function as intended. There may be a lot of back and forth with the vendor (in our case MS) in order to get the functionality you were expecting - add some contingency time to your project for this.

Voice your concerns immediately. You have to watch your costs like a hawk and have a strong understanding of what the costs should be - more importantly, you have to voice your concerns immediately to the vendor so that they can investigate and adjust. eg Log analytics

Be like water You have to work with a singular vision and purpose, but you have to be like water otherwise. The landscape in the cloud is ever changing - gone are the days of set it and forget it. Also, politically, there are always changes too - so you must be prepared to pivot when needed. eg. Pathfinder, APDC Closure, desktop, etc...

Benefits realization[edit | edit source]

Technology transformation projects with benefits realization management aligns strategic goals with project lifecycles. This helps contribute to a more efficient core business processes. Listed below are some of the benefits have been realized after TBS’s migration from a legacy data centre to cloud.

  • Completely eliminated technical debt
  • Modernized our whole environment (PaaS, SaaS)
  • Adopted DevOps and automation
  • Gained end to end visibility and monitoring capabilities
  • Stronger Security posture
  • Resilience and fault tolerance

What benefits do you foresee to be realized? See Outcome Management Guide and Tools.


References & What's New[edit | edit source]

WHAT'S NEW[edit | edit source]

Renewed Cloud Adoption Strategy Vision, Measures, Principles

DEPARTMENTAL CLOUD STRATEGIES

Cloud Infocentre

OCIO Application Portfolio Management/Aging IT Application Assessment

Enterprise IT Service Standards - Standard on; IT Profile, IT Entitlements, IT Service Common Configurations, Enterprise IT Service Usage Restrictions and more!

TBS GC Enterprise Architecture/Enterprise Solutions

complianceweek-accelerating-protected-workloads-sept-2020fr Accelerating Protected Workloads (Sept 2020)

API Store API GC Collab

Zero Trust Security Concept PDF (Aug-2020)

Zero Trust Security (Jul-2020)


Workload Migration SSC WLM Program

SSC Cloud document portal

SSC Cloud Adoption Playbooks

(Jan-2021) Visit the M365 Playbook on GCpedia

PSPC EA and GC Programs and Solutions

The Canada School of Public Service (CSPS) Digital Academy is offering a virtual learning program: Getting Started with Cloud Computing

Stratosphere Cloud Event

FWDThinking Episode 5.2: Showing What’s Possible—an extended interview with Minister Murray

Gartner: Workload Placement in Hybrid IT

DPI - Charting a path to success for Workload Migration: Approaches and Best Practices

TB Policies & Standards[edit | edit source]

Digital Operations Strategic Plan: 2021-2024

Directive on Service and Digital

Policy on Government Security

Direction on the Secure Use of Commercial Cloud Services: Security Policy Implementation Notice (SPIN)

Guidance[edit | edit source]

Government of Canada Cloud Adoption Strategy

Government of Canada Digital Playbook

Security Playbook for Information System Solutions

Government of Canada Security Control Profile for Cloud-Based GC IT Services

Government of Canada Cloud Security Risk Management Approach and Procedures

CSE ITSG-22 Baseline Security Requirements for Network Security Zones in the Government of Canada

CSE ITSG-38 Network Security Zoning – Design Consideration for Placement of Services within Zones

CSE ITSG.30.031 V2 User Authentication Guidance for Information Technology Systems

CSE ITSG.40.062 Guidance on Securely Configuring Network Protocols

Blog[edit | edit source]

The GC Accelerators - Accelerating the Secure Adoption of Cloud Services

Part 1: Application Modernisation — Making IT Delivery Less Effort

Part 2: Application Modernisation — Understanding Modernisation Strategies

Part 3: Application Modernisation — Assessing Your Portfolio

Part 4: Application Modernisation — Choosing Your Target

Part 4 ¾: Application Modernisation – Continuous Modernisation

5–4–3–2–1 — Cloud!

Governance[edit | edit source]

Prioritization/Endorsement critical path

WLM Governance.png


Retrieved from "https://wiki.gccollab.ca/index.php?title=Application_Modernization&oldid=72755"