Changes

<multilang>  

<nowiki>__TOC__</nowiki><multilang>  

@en|__NOTOC__

@en|__NOTOC__

=== ''Application Porfolio Analysis'' ===

=== ''Application Porfolio Analysis'' ===

==== Determine Modernization Vision for the Organization ====

==== <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.

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.

For organizations that desire to forego modernization opportunities, the decision to rehost the entire application portfolio to a new data centre provides that opportunity.

For organizations that desire to forego modernization opportunities, the decision to rehost the entire application portfolio to a new data centre provides that opportunity.

==== Determine Rationalization Opportunities ====

==== <big>Determine Rationalization and Retirement Opportunities</big> ====

By the end of this step you will have assessed your portfolio and infrastructure for reationalization and retirment oportunities.  

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

===== Obsolete Repositories =====

===== <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 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.  

===== Obsolete Applications =====

===== <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 remain 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. 

==== Document Migration Strategy and Targets ====

==== <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 migrations 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.  

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.  

===== '''Choose the Appropriate Migration Strategy''' =====

===== '''<u>Choose the Appropriate Migration Strategy</u>''' =====

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

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

{| class="wikitable"

{| class="wikitable"

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 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''' =====

===== '''<u>Choose Your Migration Target</u>''' =====

DC or cloud

DC or cloud

===== '''Identify Data Centre''' =====

===== '''<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.

===== '''Identify Mission Critical Applications''' =====

===== '''<u>Identify Mission Critical Applications</u>''' =====

Ensure mission critical applications are correctly identified.  

Ensure mission critical applications are correctly identified.  

===== '''Identify Operating Systems''' =====

===== '''<u>Identify Operating Systems</u>''' =====

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.

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''' =====

===== '''<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 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:

=== ''Document Project Milestones'' ===

=== ''Document Project Milestones'' ===

[[File:SampleRoadmapAnalysis.png||upright|alt=Sample Roadmap for Modernization]]

[[File:SampleRoadmapAnalysis.png||alt=Sample Roadmap for Modernization]]

=== ''Document Cost Estimates'' ===

=== ''Document Cost Estimates'' ===