VHA+Implementation+Icon Removal+2019

VHA IP 2017v0.
1 (Site Decommissioning)
This document contains explanatory information and examples which are shown in this font.
Also, embedded comments are provided to assist with completion of the implementation
plan.
To view the comments:
1. Go to “Review” on the toolbar
2. Under the “Tracking” group, select the drop box “Display for Review” and
select “Final Showing Markup”.
< CRQ000000608171 >

<Site Decommissioning>
Implementation plan
IF PRINTED OR REPRODUCED IN ANY FORMAT

Documentation Classification: C2 Vodafone Restricted, Template Version 2017v0.1
Page 1 of 21
VHA IP 2017v0.1 (Site Decommissioning)
1. Document Control
Update this section each time a new version of implementation plan for this change is issued or released.
Version Date Author Description of Change
1.0
2. Change Specific Acronyms

The following table provides the acronyms used in this implementation plan, specific to this change.
Acronym Definition

Page 2 of 21
3. Summary of Change
The purpose of this section is to provide a summary of the change. All questions must be answered. Do not
refer to other sections, but instead, provide a summary of the detailed information.
Requirement Summary or Brief Explanation
3.1 ITSM CR number(s) CRQ000000608171
3.2 Summary of Change Site Decommissioning

(In non-technical words)
3.3 Reason for Change To remove the below sites as per the VHA request
200248_SydFootballStdm
200251_SydFootballStdW
404012_Burbank
(Site Decommission)
3.4 Impact to VHA Business, No Impact

including Care/Retail,
during this deployment
(summary only; details to
be provided in Section 6)
3.5 Impact to customers No Impact

during this deployment
(summary only; details to
be provided in Section 6)
3.6 Who in Customer Care VHA TCM

has approved this
Change? (Required for
changes impacting Care,
Self-Service or Sales.)
3.7 Risk Profile High  Medium Low

Start: End:
3.8 Implementation Window
without Rollback <Day 26/03/2019 23:00 NSW <Day 05/04/2019 06:00 NSW
Time> Time>
Start: End:
3.9 Implementation Window
with Rollback <Day 26/03/2019 23:00 NSW <Day 05/04/2019 06:00 NSW
Time> Time>
Start: End:
3.10 Outage Window without
Rollback <Day 26/03/2019 23:00 NSW <Day 05/04/2019 06:00 NSW
Time> Time>
Start: End:
3.11 Outage Window with
Rollback <Day 26/03/2019 23:00 NSW <Day 05/04/2019 06:00 NSW
Time> Time>

Page 3 of 21
Requirement Summary or Brief Explanation
3.12 Rollback Duration
3.13 Rollback Checkpoint
3.14 Who has reviewed this TCM

plan
3.15 Confirm level of TechM BAU PRA  Nokia: ORCA 3 ORCA 5

operational acceptance ORCA 7
TechM Full PRA
obtained from MSP
ORCA Representative:
(Nokia/TechM)
None/Other
Provide details:
3.17 Has the Change been Yes

scheduled on the
RASR/IT Roadmap?
3.18 Who in VHA Information N/A

Security has provided
sign-off? If sign-off is not
required, please advise
why this is the case?

Page 4 of 21
4. Information Security
4.1. Is this change part of a larger project? If so who is the security resource assigned? If not please
complete questions 4.2 to 4.9.
Comment: No
4.2. Does this change affect how confidential data is handled?
Comment: No
4.3. Does this change modify any firewall rules?
Comment: No
4.4. Does this change affect who and how systems are accessed?
Comment: No
4.5. Does this change alter any internet facing components?
Comment: No
4.6. Does this change implement any new computer or network systems?
Comment: No
4.7. Does this change introduce any new 3rd parties?
Comment: No
4.8. Does this change involve the deployment of software or patches?
Comment: No
4.9. Will any systems be decommissioned as a part of this change?
Comment: No

Page 5 of 21
5. Scope of the Change
5.1. Included in Scope
This section should describe the scope of the change. For IP Network changes, please provide an
appropriate network diagram.
200248_SydFootballStdm
200251_SydFootballStdW
404012_Burbank
(Site Decommission)
5.2. Dependencies
This section should describe all dependencies on the successful deployment of this implementation.
<NA>

Page 6 of 21
6. Impacts and Outages

6.1. Systems Changed or Affected
This section lists the impacted severs of a system being changed.
Ref. System Server Host Name or other details

No.
6.1.1. N/A
6.1.2.
6.2. Planned Impacts and Outages

This section provides the detail of all impacts and outages (including loss of redundancy) resulting from the
planned change, that is, assuming there is no rollback.
Ref. System or Planned Outage Window Business and/or Customer

No. Application Day dd/mm/yyyy 24hh:mm TZ Outage/Impact
Start End
6.2.1. N/A No Impact

<Day 26/03/2019 <Day 05/04/2019
23:00 NSW Time> 06:00 NSW Time>
6.2.2.
6.3. Planned Rollback Impacts and Outages

This section provides the detail of all impacts and outages (including loss of redundancy) resulting from
rolling-back the change, that is, the planned change including the rollback.
Ref. System or Rollback Outage Window Business and/or Customer

No. Application Day dd/mm/yyyy 24hh:mm TZ Outage/Impact
Start End
6.3.1. NA
6.3.2.

Page 7 of 21
7. Testing
This section provides a summary of the planned testing related to the deployment i.e. pre-deployment,
deployment and post-deployment testing. If an additional type of testing is planned, such as Billing
Verification Testing (BVT), additional sections can be added.
7.1. Pre-Deployment Testing

This section provides a summary of all of the pre-deployment testing and the results of the testing.
7.1.1.1. Have the implementation steps N/A YES NO

been successfully tested?
Comments:
7.1.1.2. Have the rollback steps been N/A YES NO

successfully tested?
Comments:
7.1.1.3. Have all required test phases (SIT, N/A YES NO

UAT, CRR, non-functional testing and performance testing)
been successfully completed and the test results reviewed
and approved by the VHA Technology owner/architect and
VHA test team?
Comments:
7.1.1.4. Are there any known open defects? N/A YES NO

Comments:
7.2. Deployment Testing

This section provides a summary of all of the testing to be performed during deployment of the
change.
NA
8. Cutover Verification Testing (CVT)
Provide/Attach the detailed CVT plan. Details should include test descriptions and the expected
results of each test.
NA
8.1. Post-Deployment Testing

This section provides a summary of all of the testing to be performed after the deployment of the
change.
NA

Page 8 of 21
9. Production Verification Testing (PVT)
Provide/Attach the detailed PVT plan. Details should include test descriptions and the expected
results of each test.
<NA>
9.1.1.1. Stability period defined? N/A YES NO

Comments:
10. Critical Success Criteria

Provide details of all key criteria/KPIs which will be measured as part of this change to determine
whether the change has been successful or not. The details should document the KPI/criteria, as well
as the agreed acceptable baseline for this measure.
This criteria should form the input into any decision to continue with a change or to initiate a rollback.
KPI/Criteria Description Acceptable Baseline

Measure

Page 9 of 21
11. Implementation
11.1. Implementation Strategy
This section should provide details of the overall strategy of the implementation.
<implementation_strategy>
11.2. Detailed Implementation Steps

This section provides the detailed implementation steps to perform the change. The details provided here
should allow a step-by-step walkthrough of the entire change, including identifying where customer impact
may occur.
12. Pre-Requisite Tasks

This section provides details of the pre-requisite tasks of the change, i.e. the tasks that do not affect the
production environment and can be performed prior to the implementation window.
Step Application Detail Start Date- End Date-Time Who? Who?

or System Time or Duration (Primary) (Backup)
13.
<Perform pre-
change backup.> I
<Verify backup has
completed
successfully.>
<Execute Pre-
change system
health check.>
mplementation Tasks
This section provides detailed steps for the implementation of the change, i.e. the tasks to be perform during
the implementation window.

Page 10 of 21
Step Application Detail Start Date- End Date- Who? Who?

or System Time Time (Primary) (Backup)
or
Duration
13.1.1.1. 1. Call the following contact centres Nokia
to confirm that the network is <Day <Day RIC
stable, that the change can
26/03/201 05/04/201
commence, and to obtain the
start receipt number: 9 23:00 9 06:00
NSW NSW
 GNOC (Nokia) - for Network
Time> Time>
changes
 BSS/IT (TechM) Service desk -
for IT changes
2. If there is an impact to VHA
Customers or VHA Customer
Care, inform:
 VHA Mumbai Call Centre
 VHA Kingston Call Centre
13.1.1.2. Record the start receipt number Start of Nokia
from GNOC or BSS/IT Service approved RIC
Desk. CR
13.1.1.3. <Include Implementation Steps>
13.1.1.4. <Include Rollback decision point>
13.1.1.5. <Include Testing and Health Check
Steps>
13.1.1.6. For each contact centre that was
contacted at the commencement or
during the change, contact them
again to notify of the completion of
the change:
 GNOC
 BSS/IT (TechM) Service desk
 VHA Mumbai Call Centre
 VHA Kingston Call Centre.
13.1.1.7. Record the end receipt number
from GNOC or BSS/IT Service
Desk.
13.1.1.8. Email stakeholders regarding the
outcome of the deployment.
13.2.Rollback Strategy
This section should provide details of the rollback strategy, or strategies, of the implementation.

Page 11 of 21
Note that for any deployment with an Extreme risk (as identified in section 10.2), the approval from General
Manager, Technology Operations must be obtained prior to any rollback. This engagement must be pre-
arranged and documented in the Deployment Communication Plan (section 11.2).
< If during the soft decomm process, it is determined that further modifications are required prior to
the site being decommissioned, This determination would be made on the basis of the Performance
Reports and Team Feedback>
13.3.Detailed Rollback Steps

This section provides the detailed steps to roll back the change, i.e. the steps to rollback the changes
performed in the implementation window.
Step Application Detail Start Date- End Date- Who? Who?

or System Time Time (Primary) (Backup)
or Duration
13.3.1.1. For each contact centre
that was notified at the <Day <Day
commencement of or
26/03/201 05/04/2019
during the change,
please inform them that 9 23:00 06:00 NSW
Rollback has NSW Time>
commenced. Time>
13.3.1.2. <Include Rollback
Steps>
13.3.1.3. <Include Testing and
Health Check Steps>
13.3.1.4. For each contact centre
that was notified at the
commencement of or
during the change,
please inform that that
Rollback has
completed.

Page 12 of 21
14. Issue and Risk Management

This section provides the details of the issues and risks of the change.
14.1.Issues
Ref. Description Status Impact Owner

No.
14.1.1. No issues
14.1.2.
14.2.Risks
Risks related to Deployment with a Risk rating>21 (Extreme) must be included

here. Deployment risks include those related to rollback and roll forward.
Clarity Description Mitigation Category Residual Risk

Risk # (Benefit Impact, Additional Deployment Number 1-25 As per Clarity
Cost, Roadmap Impact, Service Impact)
As per Clarity
RS-XXXX No risks
RS-YYYY

Page 13 of 21
15. Communication Plan

15.1.Pre-Deployment Communication Plan
This section describes for any additional communication requirements before
the deployment.
<NA>
15.2.Deployment Communication Plan

Provide the conference bridge details that will be used for this deployment.
Conference Bridge Number <NA>
See Appendix : Deployment Communications for the communication

requirements during the deployment.
Where extreme deployment risks have been identified in section 10.2,

engagement of the VHA Service Manager, General Managers for impacted
domains and the General Manager, Technology Operations is required for any
rollback decision. This engagement must be agreed with the VHA Service
Manager prior to the deployment and must be documented in the deployment
communication plan. SM and GM contact details must be captured in Appendix
A.2.
<NA>
16. Escalations
Provide the name of the person(s) who will be contacted to escalate issues.
VHA On-call Service Manager - Contact should be established via the Nokia on-
call SM (+61 450 929 170) for Networks changes or TechM Service Desk (+91
7875757371 or 1800 153 580 option 1) for IT changes.
<other_escalation_names>
17. Rollback Authority

If the change is being rolled back in accordance with the approved deployment
and communication plan, then no further authorisation is required. However, if
there is any deviation from the approved plan, then approval must be obtained
from the VHA On-call Service Manager (contact via relevant service desk).
Additionally, if the roll back strategy involves engagement of General Managers
from impacted domains, then authorisation must be taken from the General
Manager, Technology Operations prior to initiating a rollback.

Page 14 of 21
Provide the name of the person(s) who will decide if the change should be
rolled back.
VHA On-call Service Manager - Contact should be established via the Nokia on-
call SM (+61 450 929 170) for Networks changes or TechM Service Desk (+91
7875757371 or 1800 153 580 option 1) for IT changes.
General Manager, Technology Operations
17.1.Post-Deployment Communication Plan

This section describes the communication requirements after the deployment.
<additional_post-deployment_communications>

Page 15 of 21
Appendix : Implementation Contact Details
1 Technical Support
This section provides the contact details for technical support staff who are involved in the deployment.
Name Team Phone Email Role Responsibility Backup
Balasubram Nokia RIC +91- balasubram Team

aniam.P 029429922 aniam.pachi lead
appan@noki
4 Option
a.com
1-2
2 Business Support
This section provides the contact details for the business support who are involved in the deployment.
VHA On-call VHA Service Contact via VHA Service Escalation for
Service Management +61 450 Manager Go/No decisions
Manager – 929 170 and major
Networks & (Networks/ issues.
IT Nokia) or
+91 7875
757371
(IT/TechM).
<VHA_Proje Project VHA Project Managing the
ct_ Manager project
Manager>
<Deployment Deployment Deployment Managing the
_Manager_N Manager deployment
ame>
<Vendor_Pro <Vendor> Vendor Managing the
ject_ Project project
Manager> Manager

Page 16 of 21
Appendix : Deployment Communications

The following table provides the list of contact centres and service desks that may need to be contacted
during the implementation.
Centre When to Contact Telephone Number Email Address
GNOC The GNOC operates 24x7. 1800 683 683 Option 1 nmc.vha@nsn.com
It is mandatory to telephone or
the GNOC: +61 2 9429 9988 Option 1
 at least 15 minutes prior to
commencement of a
Have the CR number ready for
Networks change.
reference.
Depending on the stability of
the VHA Network, the GNOC
will provide approval to Please note:
proceed and a start receipt In the event you are unable to
number log in via the contact number
 for any variations to the provided above, please email
implementation steps the GNOC (nmc.vha@nsn.com)
documented in this plan or - seeking login (stating CR no.
unexpected impacts and contact details).
 at the conclusion of the Further escalation can be made
change to provide the status to the GNOC Duty manager: ph:
(successful or unsuccessful). 02 94299196 or email: nsn-vha-
GNOC will provide an end gdc-duty-managers@mlist.nsn-
receipt number. inter.net

Page 17 of 21
BSS/IT The BSS/IT (TechM) Service 1800 153 580 bss-it-

(TechM) Desk operates 24x7. or servicedesk@vodafon
Service e.com.au
+91 20 42259390
Desk
It is mandatory to contact the and follow the IVR options (If in
BSS/IT Service Desk prior to doubt, select option 1) For email
the commencement of an IT correspondence,
change. Depending on the include:
stability of the VHA Network, Have the CR number ready for
 the CR number
the Service Desk will provide reference.
approval to proceed and a  a description of the
start receipt number unexpected BSS/IT
impact
 the
The BSS/IT (TechM) Service
Project/Deployment
Desk must be telephoned
Manager contact
and/or emailed for any
details
unexpected BSS/IT impact.
VHA VHA Hobart Call Centre serves +61 406 824 488 RTM@Techmahindra.c
Hobart VHA customers and is open om
(Shift Leader)
Call Monday to Friday 08:00 to
Centre 20:00 AEST/AEDT and and
Saturday to Sunday 09:00 to Or
itsupporthobart@vodaf
17:30 AEST/AEDT.
one.com.au
If open, the call centre must be +61 414 187 185
telephoned if a change has an (IT Support)
expected impact to the For email
centre’s ability to serve VHA correspondence,
customers: Have the CR number ready for include:
reference.  the CR number
commencement of the  the start and end
change time of change
 for any unexpected impacts  the systems affected
 at the conclusion of the  the
change to provide the status Project/Deployment
(successful or unsuccessful). Manager contact
The centre must be emailed if details
a change has an expected  any other contacts
impact to the centre’s ability to for the change
serve VHA customers:
commencement of the
change
 at the conclusion of the
change to provide the status
(successful or unsuccessful).

Page 18 of 21
VHA VHA Mumbai Call Centre +91 9820 810 176 Servicedesk.Aus@3gl
Mumbai serves VHA customers and is obalservices.com
Call open 24x7.
Centre The centre must be For email
reference.
telephoned if a change has an correspondence,
expected impact to the include:
centre’s ability to serve VHA  the CR number
customers:  the start and end
 at least 15 minutes prior to time of change
commencement of the  the systems affected
change
 the
 for any unexpected impacts Project/Deployment
 at the conclusion of the Manager contact
change to provide the status details
(successful or unsuccessful).  any other contacts
The centre must be emailed if for the change
a change has an expected
impact to the centre’s ability to
serve VHA customers:
commencement of the
change
 at the conclusion of the
change to provide the status
(successful or unsuccessful).
TCM The TCM team can assist with 1800 683 683 tcm.au@vodafone.co
Team Change Management issues, or m
such as CR issues. The team
+61 2 9429 9988
operates Monday to Friday
09:00 AEST/AEDT to 17:00 IVR option: option 3
AEST/AEDT.
reference.

Page 19 of 21
Appendix : Other Communications
Contact Email address
NSN Change Management change.management@nsn.com
NSN Release Management release.management@nsn.com
VHA CAB Correspondence release.management@nsn.com
VHA Customer Care contactcentresystems@vodafone.com.au

Appendix : CMDB Updates
1 CMDB Updates
1.1.1 Is this Change creating a new application or deploying new N/A YES NO
hardware?
Comments:
1.1.2 Is this Change decommissioning an existing application and/or N/A YES NO

any hardware?
Comments:
1.1.3 Is this Change creating a new Business Service? N/A YES NO

Comments:
1.1.4 Is this Change replacing hardware? N/A YES NO

Comments:
Note: If any of the above responses have been answered ‘Yes’ then the ITSM CMDB Support team
need to be formally engaged for this Change and the Templates in the ITSM Help  VHA Process
Documents mentioned below under the name ITSM CI ADDM Template v1.0.xlsm
 ADDM Readiness Checklist Template for CI discovery_v0.x (latest version)
 ITSM CI Template V0.x (latest version)

These need to be completed and returned to the ITSM CMDB Support Group email address:
IMS04VHABMCTeam@TechMahindra.com and the ITSM Team formally engaged with Tasks within the
Change to perform updates to ITSM CMDB.

VHA+Implementation+Icon Removal+2019

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VHA+Implementation+Icon Removal+2019

Uploaded by

Copyright:

Available Formats

VHA IP 2017v0.

To view the comments:

1. Go to “Review” on the toolbar

< CRQ000000608171 >

IF PRINTED OR REPRODUCED IN ANY FORMAT

Version Date Author Description of Change

2. Change Specific Acronyms

IF PRINTED OR REPRODUCED IN ANY FORMAT

Requirement Summary or Brief Explanation

3.1 ITSM CR number(s) CRQ000000608171

3.2 Summary of Change Site Decommissioning

3.4 Impact to VHA Business, No Impact

3.5 Impact to customers No Impact

3.6 Who in Customer Care VHA TCM

3.7 Risk Profile High  Medium Low

IF PRINTED OR REPRODUCED IN ANY FORMAT

3.12 Rollback Duration

3.13 Rollback Checkpoint

3.14 Who has reviewed this TCM

3.15 Confirm level of TechM BAU PRA  Nokia: ORCA 3 ORCA 5

3.17 Has the Change been Yes

3.18 Who in VHA Information N/A

IF PRINTED OR REPRODUCED IN ANY FORMAT

4.2. Does this change affect how confidential data is handled?

4.3. Does this change modify any firewall rules?

4.5. Does this change alter any internet facing components?

4.7. Does this change introduce any new 3rd parties?

4.8. Does this change involve the deployment of software or patches?

4.9. Will any systems be decommissioned as a part of this change?

IF PRINTED OR REPRODUCED IN ANY FORMAT

IF PRINTED OR REPRODUCED IN ANY FORMAT

6. Impacts and Outages

Ref. System Server Host Name or other details

6.2. Planned Impacts and Outages

Ref. System or Planned Outage Window Business and/or Customer

6.2.1. N/A No Impact

6.3. Planned Rollback Impacts and Outages

Ref. System or Rollback Outage Window Business and/or Customer

IF PRINTED OR REPRODUCED IN ANY FORMAT

7.1. Pre-Deployment Testing

7.1.1.1. Have the implementation steps N/A YES NO

7.1.1.2. Have the rollback steps been N/A YES NO

7.1.1.3. Have all required test phases (SIT, N/A YES NO

7.1.1.4. Are there any known open defects? N/A YES NO

7.2. Deployment Testing

8.1. Post-Deployment Testing

IF PRINTED OR REPRODUCED IN ANY FORMAT

9.1.1.1. Stability period defined? N/A YES NO

10. Critical Success Criteria

KPI/Criteria Description Acceptable Baseline

IF PRINTED OR REPRODUCED IN ANY FORMAT

11.2. Detailed Implementation Steps

12. Pre-Requisite Tasks

Step Application Detail Start Date- End Date-Time Who? Who?

IF PRINTED OR REPRODUCED IN ANY FORMAT

Step Application Detail Start Date- End Date- Who? Who?

IF PRINTED OR REPRODUCED IN ANY FORMAT

13.3.Detailed Rollback Steps

Step Application Detail Start Date- End Date- Who? Who?

IF PRINTED OR REPRODUCED IN ANY FORMAT

14. Issue and Risk Management

Ref. Description Status Impact Owner

Risks related to Deployment with a Risk rating>21 (Extreme) must be included