18
edits
Changes
no edit summary
== '''Engagement''' ==
== '''Engagement''' ==
Once priorities are selected and endorsed by governance, funding is available to partner departments to initiate the discovery phase. A [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|simple worksheet]] has been devised to identify funding requirements. 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.
Once priorities are selected and endorsed by governance, funding is available to partner departments to initiate the discovery phase. A [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|simple worksheet]] has been devised to identify funding requirements. 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. The MoU generic template can be found here (insert template).
== '''Discovery''' ==
== '''Discovery''' ==
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
==== <big>Determine Rationalization and Retirement Opportunities</big> ====
By the end of this step you will have assessed your portfolio and infrastructure for rationalization and retirment oportunities.
By the end of this step you will have assessed your portfolio and infrastructure for rationalization and retirement opportunities.
===== <u>Obsolete Repositories</u> =====
===== <u>Obsolete Repositories</u> =====
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.
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 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 un-necessary data retention and actively dispose of data that has been deemed un-necessary. Un-necessary data is both a cost and a liability.
* 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.
===== <u>Obsolete Applications</u> =====
===== <u>Obsolete Applications</u> =====
|-
|-
! Strategy
! Strategy
! Altnerative Name
! Alternative Name
! Full Description
! Full Description
! Data Centre
! Data Centre
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]
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.
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.
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.
Migrating away from less common OSes such AIX, UNIX, or Solaris may require extensive changes to the application.
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 be applied to high business value applications.
Due to the high cost of refactoring, this strategy should only be applied to high business value applications.
====== '''Replace (Repurchase)''' ======
====== '''Replace (Repurchase)''' ======
===== '''<u>Identify Data Centre</u>''' =====
===== '''<u>Identify Data Centre</u>''' =====
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.
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.
===== '''<u>Identify Mission Critical Applications</u>''' =====
===== '''<u>Identify Mission Critical Applications</u>''' =====
===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====
===== '''<u>Generate Portfolio Analysis Dashboard</u>''' =====
Request that TBS generate a dashabord of your application portoflio. This will ensure your decisions have been correctly reflected. A sample of the dashabord 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||center|alt=Sample Application Portfolio Analysis]]
[[File:SamplePortfolioAnalysis.png||center|alt=Sample Application Portfolio Analysis]]
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.
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'' ===
=== ''Document Project Milestones (Roadmap)'' ===
[[File:SampleRoadmapAnalysis.png||alt=Sample Roadmap for Modernization]]
[[File:SampleRoadmapAnalysis.png||alt=Sample Roadmap for Modernization]]
=== ''Document Cost Estimates'' ===
=== ''Document Cost Estimates'' ===
A [[gccollab:file/view/2092934/enapplication-modernization-cost-estimates-templatefr|simple worksheet]] 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'' ===
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..
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..
If and when endorsement is provided by GC EARB, 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.
If and when endorsement is provided by GC EARB, 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. The MoU generic template can be found here (insert template).
== '''Execution''' ==
== '''Execution''' ==
Content not yet completed
Content not yet completed