Suggested LOGO

for customer

XX Site of XX Company

Implementation
Solution for XX
Product Change
(Note: The selectable part of the title can be update/patch installation/rectification
according to the actual implementation scenario. )

Prepared by:

Date:

Reviewed by:

Date:

Suggested LOGO
for customer

Approved by:

Date:

Implementation Solution for Change

Contents
1

Description of Change..........................................................................................3
1.1

Description of Site......................................................................................3

1.2

Purpose......................................................................................................3

1.3

Description of Change and Change Influence...........................................3

Preparations for Change.......................................................................................4

2.1

Change Period...........................................................................................4

2.2

Composition of Change Team and Responsibility of Team Members.......4

2.2.1

Change Team of XX Company....................................................................4

2.2.2

Huawei On-site Change Team....................................................................5

2.2.3

Huawei Support & Guarantee Team...........................................................5

2.3

Check of Equipment Running....................................................................5

2.4

Change Risks and Countermeasures........................................................6

2.5

Check Before Change................................................................................7

Operation Steps for Change.................................................................................8

3.1
3.1.1

Overall Description......................................................................................8

3.1.2

Operation Steps for Change.......................................................................8

3.2

Test and Verification...................................................................................9

3.3

Solution for Changeback In the Case of Failure........................................9

3.3.1

Definition of Change Failure.......................................................................9

3.3.2

Overall Description of Changeback...........................................................10

3.3.3

Information Collection Before Changeback...............................................10

3.3.4

Changeback Steps....................................................................................10

3.3.5

Equipment Status Check..........................................................................10

3.3.6

Tests After Changeback............................................................................11

3.3.7

Changeback Risk Analysis........................................................................11

3.4
4

Change Steps............................................................................................8

Change of Spare Parts and Emergency Workstation..............................11

Work After Change..............................................................................................11

4.1

Observation..............................................................................................11

4.2

Provision of Materials...............................................................................11

4.3

Provision of Software...............................................................................12

4.4

Training....................................................................................................12

4.5

Matters Needing Attention.......................................................................12

Technical support website:

http://support.huawei.com

Technical support hotline:

Fax:

Page 3 of 12

Implementation Solution for Change

1 Description of Change
1.1

Description of Site

Briefly state main information of the site, for example, networking situation, user capacity,
trunk capacity, main problems existing in the early stage, and remote access information.
1). Clarify the network topology diagram, peripheral interface address and networking (if
there is any special networking scenario, interface address, equipment type and business
type, please state it separately).
2). Define the business amount related to the change operation (like user capacity and
trunk capacity).
3). Identify main problems of the live network (like networking limit, soft/hardware defect
and warning execution etc) and main problems which customers pay attention to
recently.
4). Environment for remote access must be available (including usability and customer
authorization); If remote access cannot be conducted due to the customer or product, it is
required to prepare precaution or strengthen safeguard in the change solution.

1.2

Purpose and Requirements

Customer requirement and acceptance standards

Change scenario: problem resolution/version sales/rectification/network performance
optimization/ engineering network adjustment
Change solution category: software upgrade/patch update/board replacement/data
configuration/parameter adjustment/ engineering cutover/ engineering restructuring
Change scope: first site/whole network/solution formulation and verification
Change time

1.3

Description of Change and Change Influence

Specify version numbers or patch numbers before and after the change, NEs involved by
the change, and whether corresponding modifications shall be made to relevant NEs
such as billing center and NMS.
Introduce new features, services, and functions related to the changed version or patch,
and specify the influences on users' daily operations such as data configuration and
Technical support website:
http://support.huawei.com

Technical support hotline:

Fax:

Page 4 of 12

Implementation Solution for Change

maintenance.
Specify if operations need to be finished on hardware to realize the change and if
changes of spare parts are needed, and state influences of the change on maintenance.

Preparations for Change

1.4

Change Period

The change period is from XX:XX, MM DD, 200X to XX:XX MM DD, 200X.
The change shall be made not during major holidays, large-scale activities, or the
adjustment of other NEs.

1.5

Composition of Change Team and Responsibility of Team Members

Introduce the composition of the change team, specify the owner for each change action,
and clarify work contents and responsibilities.

2.2.1 Change Team of XX Company

Name

Responsibility
Chief commander
Owner for xx product

Telephone No.

change
Coordination with other
NEs
Test owner
Charging verification
owner
Network management test
owner
Communication on
handling customer
complaints

2.2.2 Huawei On-site Change Team

Name

Technical support website:

http://support.huawei.com

Responsibility
Chief commander
Owner for xx product
Technical support hotline:
Fax:

Telephone No.

Page 5 of 12

Implementation Solution for Change

change

2.2.3 Huawei Support & Guarantee Team

Name

Responsibility
Supporting overall

Telephone No.

coordination as the
technical expert
Product support contact
person

1.6

Check of Equipment Running

Specify the performance that shall be analyzed before the change, and clarify the owner
for outputting the analysis report.
Clarify the owner for outputting the alarm analysis report. Know what problems have
existed before the change to avoid the misjudgment after the change.
Focus on network KPIs, performance indicators, hardware operation status, and alarm
during observation to avoid the disagreement between both parties on the success or
failure of the change.
1). Check if timed tasks exist in the system (like system timed task, regularly executed
job in database and periodically running script) and assess if the timed tasks affect the
normal upgrade.
2). Confirm with customer maintenance department if any operation will be done on
peripheral components at that night and if the operation will affect the change
(upgrade/cutover). Please pay special attention to the customer network and peripheral
billing parts.

1.7

Change Risks and Countermeasures

Assess the risks that may be encountered during the change and provide corresponding
countermeasures. Analyze and confirm the influence that may be brought by the change
process and change on existing network equipment. For example:
(1)

In the case of end site change, if the configuration of the CD interface link can
Technical support website:
http://support.huawei.com

Technical support hotline:

Fax:

Page 6 of 12

Implementation Solution for Change

support a large number of location update requirements after the change and if the
authentication/encryption shall be turned off and BSC shall be blocked during the change
to reduce the impact shall be taken into consideration. The analysis shall be conducted
based on real data.
(2)

Instantaneous traffic analysis: impact on main relevant NEs, HLR, BSC, SCP,
and STP.

(3)

Analysis of difference in CPU occupancy between two versions

(4)

Risk existing in change duration;

(5)

Long-time impact on traffic/link: Adopt risk mitigation methods such as

configuring the MAP function configuration table.

(6)

Hardware fault: Spare parts shall be prepared for boards that damage easily.

(7)

Is the interface protocol changed?

(8)

Refer to the risk mitigation experience libraries for various products.

Key points of software implementation:

Assess the impact of differences between the previous version and existing version
influence on the upgrade/patch implementation process and result (like the
upgrading path spanning several versions and north-faced port changes etc).

The relationship between the target version and the peripheral network element (e.g.
OSS and SmartCare tool).

Assess the influence of the known problems in live network on software change
(warning and restructuring etc).

Assess the warning, performance index, and license change.

If the configuration script for new version completes conversion and review during
version upgrade; if the script can have successful pre-execution, and the correlation,
mutual exclusion, off-line and on-line relationship in the script are completed.

Assess the software implementation pattern (field operation and TAC remote
operation).

If confirm the important information with customers (like the dialing test list).

If license change is involved, it is required to apply for license in advance and make
sure the license is correct.

Download the latest work instructions and tools before change.

Each preparation work needs to be checked and prepared based on the work
instructions.

Key points of important hardware change:

Assess based on the detailed description of product document-hardware

management-risk operation

Technical support website:

http://support.huawei.com

Technical support hotline:

Fax:

Page 7 of 12

Implementation Solution for Change

Confirm the work model of board: active and standby/single configuration..and load
sharing etc.

Estimate the business interruption scope resulted from hardware changes,

especially the single board single configuration model (like interface board, key
control framework exchange board, subtract, and backplane change etc).

It is required to confirm the correctness of DIP switch and the safety ground of
equipment before changing the board in the solution.

Assess if the soft and hardware versions of boards/modules are consistent after
change.

If power-off operation on cabinet and subtract is involved, pay attention to the order
(like master frame first and slave frame second, and power-off operation on board
with hard disks like OMU and SAU first).
Key points of network adjustment (including network architecture and configuration parameter
adjustment):

Assess if network adjustment solutions are developed based on work instructions of

each product (if there is any customized operation, it is required to assess and verify
the completeness and safety of these steps and scripts).

If there is assessment for the network data backup and rollback mechanism of the
configuration change, and the assessment scope and period of business impact.

If there is assessment of impact on the interworking port/equipment/network.

If there is assessment of solution maturity (focus on if the solution had been largely
used).

If there is any assessment solution for network performance/KPI after operation

implemented (like focusing on assessing if the business runs normally during traffic
peak).

No.

1
2
3

Risk Description

Possibility

Impact

(High/Middle/

(High/Middl

Low)

e/Low)

Countermeasure

Data backup
Impact on NEs
Risk in change
duration

Technical support website:

http://support.huawei.com

Technical support hotline:

Fax:

Page 8 of 12

Implementation Solution for Change

1.8

Check Before Change

No.

Preparations Before Change

Solution for changeback in the case of

2
3

failure
Test solution
Confirming change risks and emergency

4
5
6

measures
Readiness of mobile phone test card
Readiness of change test personnel
Readiness of relevant equipment

7
8
9
10

maintenance personnel
Readiness of support & guarantee team
Readiness of remote log-in environment
Readiness of emergency spare parts
Readiness of boards, tools, and

Owner

Completion
Date

instruments
11

2 Operation Steps for Change

2.1

Change Steps

2.1.1 Overall Description

Briefly describe all change steps.
1.

Sequence of site change

2.

Sequence of equipment module change

2.1.2 Operation Steps for Change

Specify operations that need to be finished to realize the change. Clarify the owner for
each step of operation, the estimated start and end time, and the basis for judging the
success. Specify measures for handling emergencies that may happen during the
change (such as too heavy CPU load, system overload, intermittent disconnection of
links, low success rate of location update, low success rate of short message sending,
and low call completion rate).
Specify feedback channels and handling owners for the problems that may emerge
during the change to ensure that the problems can be reported to all relevant personnel
Technical support website:
http://support.huawei.com

Technical support hotline:

Fax:

Page 9 of 12

Implementation Solution for Change

in time. (The specific operation steps must be based on the related technical instructions
of transformation operation. If there is any customized step, it is required to inform the
technical reviewer about risk assessment conduction).
No.

Change Step

Operation

Implementation

Time

Person
1

Describe specific contents of

Data backup

operation and the basis for

judging if the operation is
successful.

Standby
board
upgrade
Switchover

3
4

2.2

Test and Verification

Describe how to conduct the test during the change in details, and clarify owners for test
items and specific test contents. After the test, record details of the test process and
submit the results to the billing center for charging confirmation. Tests shall cover the
following aspects:
1.

Basic services (of this site and between sites) are normal.

2.

New functions and new features

3.

Original defects are corrected?

4.

Charging verification and network management verification after the change;

specifying owners for providing the report

5.
No.

Operation
Item

Operation Method

Owner

Time

1
2

2.3

Solution for Changeback In the Case of Failure

2.3.1 Definition of Change Failure

Define what is a change failure and who can recognize a change failure (negotiate with
the user before the change to determine this part).
Technical support website:
http://support.huawei.com

Technical support hotline:

Fax:

Page 10 of 12

Implementation Solution for Change

For example:
A change failure shall be recognized if the following major problems cannot be resolved
before 5:00 a.m. (within the stipulated period of time) and back-off operations shall be
finished.
(1) The dial test shows that calls cannot be made through a certain office route.
(2) Charging amount is wrong.
(3) A lot of users fail to make or receive calls.
(4) One-way audio in a large area
(5) Frequent breakdown

2.3.2 Overall Description of Changeback

Briefly describe the changeback in an overall manner.

2.3.3 Information Collection Before Changeback

Collect information of the problems that lead to changeback as far as possible before
changeback to facilitate cause analysis and prepare for the change in the next time.

2.3.4 Changeback Steps

Describe changeback steps in details, clarify owners, and specify the time period needed
for completing each step.

2.3.5 Equipment Status Check

Specify how to check the system operation status after changeback and clarify owners.

2.3.6 Tests After Changeback

Describe the tests that shall be conducted after changeback and clarify test owners.

Technical support website:

http://support.huawei.com

Technical support hotline:

Fax:

Page 11 of 12

Implementation Solution for Change

2.3.7 Changeback Risk Analysis

Analyze the risks that may be brought by changeback, and provide corresponding
countermeasures.

2.4 Change of Spare Parts and Emergency Workstation

Determine the time, and clarify owners for the change of spare parts and emergency
workstation. The change of spare parts and emergency workstation shall be finished
within one week after successful change.

3 Work After Change

3.1

Observation

Specify owners for maintenance during the equipment observation period after the
change and state work contents.

3.2

Provision of Materials

Clarify owners, provision time, and materials that shall be provided.

3.3

Provision of Software

Clarify owners, provision time, and software and disks that shall be provided.

3.4

Training

Clarify owners for and time of providing training on the changed parts for customers.

3.5

Matters Needing Attention

After completion of the change, notify customers of modifying the used account and
password and returning SIM cards and related tools.

Technical support website:

http://support.huawei.com

Technical support hotline:

Fax:

Page 12 of 12