213
edits
Changes
Jump to navigation
Jump to search
Line 2:
Line 2: − + − '''''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 !'''''+ + + + + + + + + + + + + + + + + + + + Line 324:
Line 343: − The analysis and planning undertaken as part of the discovery phase will be presented to GC EARB to request endorsement to release the 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. − 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 (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 by GC EARB, 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.+ + + + + + + + + + Line 335:
Line 362: − 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. A new model for funding calculations has been and has been implemented in 2021. A Memorandum of Understanding between the Chief Information Officer of Canada (GC CIO) and the Deputy Head of a department will be agreed upon to secure the funding.+
no edit summary
@en|
@en|
'''''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.
'''''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 !'''''
{| 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
($13,876,802 available)
| $11,000,000
($ 9,124,586 available)
|-
|}
<!-- BACKGROUND -->
<!-- BACKGROUND -->
=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===
=== ''Gate2: GC EARB Endorsement and MoU to Release Funds'' ===
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 [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.
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'' ===
== '''Execution''' ==
== '''Execution''' ==
With the execution funds now received, the analysis and planning undertaken as part of discovery will be now be executed. 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 recevied 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]]
[[Image:Execution Swimlanes v1.png]]
