Application and Server Decommissioning Cookbook

Table of Contents

DOCUMENT INFORMATION

1 INTRODUCTION 4

1.1 PURPOSE OF THE DECOM PROCESS 4

1.2 AUDIENCE 4

1.3 KEY BENEFITS TO NOKIA4

1.4 ROLES AND RESPONSIBILITIES 4

1.5 KEY STATUSES IN ESL 6

2 DECOMMISSION PROCESS – OVERVIEW 7

3 INITIATION PHASE 8

3.1 INITIATION PHASE - INITIATE DECOM REQUEST 8

3.2 SUMMARY OF THE INITIATION PHASE 9

4 ASSESSMENT PHASE 9

4.1 ASSESSMENT PHASE - TECHNICAL ASSESSMENT BY THE HPE DECOM TEAM 9

4.2 ASSESSMENT PHASE – DECOM ASSESSMENT 10

4.3 SUMMARY OF THE ASSESSMENT PHASE 11

5 DECOMMISSION PROCESS - APPLICATION REMOVAL 11

5.1 STANDARD DECOMMISSION PROCESS FOR APPLICATIONS 12

5.2 PLANNING PHASE - APPLICATION STOPPED? 12

5.3 PLANNING PHASE – RFC TRACKER GENERATION 12

5.4 SUMMARY OF PLANNING PHASE – APPLICATION DECOM 12

5.5 EXECUTION PHASE - RFC GENERATION, APPROVAL, CLOSURE 13

5.6 SUMMARY OF EXECUTION PHASE OF APPLICATION DECOM 13

5.7 FINAL VALIDATION PHASE – ESL AND UCMDB UPDATED 14

5.8 SUMMARY OF FINAL VALIDATION PHASE OF APPLICATION DECOM 14

5.9 EXECUTION PHASE - SIMPLE AND COMPLEX APPLICATION DECOMMISSIONS 15

6 DECOMMISSION PROCESS – PARTIAL DECOM - INSTANCES 15

6.1 PLANNING PHASE – PARTIAL DECOM – INSTANCES 15

6.2 EXECUTION PHASE: PARTIAL DECOM – INSTANCES - RFC GENERATION, APPROVAL, CLOSURE
15

6.3 FINAL VALIDATION PHASE – PARTIAL DECOM – INSTANCES - ESL AND UCMDB UPDATED 16

7 DECOMMISSION PROCESS – PARTIAL DECOM – IN/OUT OF PRODUCTION SERVERS 16

7.1 DIFFERENCE BETWEEN IN PRODUCTION AND OUT OF PRODUCTION SERVERS 16

7.2 PLANNING PHASE – PARTIAL DECOM – IN/OUT OF PRODUCTION SERVERS 17

7.3 EXECUTION PHASE – PARTIAL DECOM – IN/OUT OF PRODUCTION SERVERS - RFC GENERATION,
APPROVAL, CLOSURE 17

7.4 FINAL VALIDATION PHASE: PARTIAL DECOM – IN PRODUCTION SERVERS - ESL AND UCMDB
UPDATED 18

7.5 SCRAPPING 18

8 GOVERNANCE 19

8.1 REPORTING 19

8.2 KEY PERFORMANCE INDICATORS (KPIS) 19

8.3 APPROVALS 20

8.4 ESCALATIONS 20

9 ACKNOWLEDGEMENTS 20

10 APPENDIX: REFERENCING OTHER CONTRIBUTING PROCESSES 21

10.1 APPENDIX A: GLOSSARY 21

Application Decommissioning
Reducing IT complexity through a focused
application cleanup process
8
• Complexity: increasing change capabilities by removing unnecessary IT
complexity.
• Cost: the IT budget is under pressure by global demand to reduce overall cost.
Much of the total IT spending is consumed by maintenance leaving not much
room
for innovations.
Why we want it
• Definition: an application is only decommissioned after its software is no longer
present within the organization on any of its OTAP environments.
• Scope: Incumbent Communication Service Providers have the potential to
reduce
total application portfolio with a substantial percentage. The surplus is a legacy of
many years of mergers and acquisitions with a cost reduction potential of tenths
of
millions year on year.
What it is
• Master plan: a master plan containing waves of 4-6 months
• Individual applications: standard activities and use of accelerators to perform
the
rationalizing activities include commercial and technical migration, data migration
and software-hardware rationalizing.
• KPI’s: clear set of KPI’s with the single most important KPI being the number of
applications rationalized.
How we do it
• Governance: program is governed by IT organization with strong connect to
the
business
• Working teams: dedicated domain teams representing functional
management,
infrastructure and architecture.
Who is involved