The document is a change request form for upgrading software on base stations (BS) and radio network controllers (RANC) to activate a call re-establishment feature. It requires filling out sections providing details of the change submitter, requested outage dates and times, risk analysis, and approval from technical approvers. Upon approval, it schedules the activity with a monitoring period to ensure the change was successfully implemented.

1. Change Request - Management Process Operations
Mobile Network Operations Change Request Form
Change Submitters are required to fill out section 1 of the CR completely and attach all relevant
documentation before handing it in for technical approval. Please mark fields with an ‘x’.
Section 2 will be filled out by the Change Approvers.
Note: Notification before work starts and feedback must be given by the change Implementer to the NOC
upon completion of work!
1. Change Request (CR)
CR Reference No
(To Be Assigned by
Change Manager)
Date (dd/mm/yy)
Change Submitter’s
Details
Name Edward Okoth
Department Networks
Position RAN Design& Optimization Engineer
e-Mail Edward.okoth.ext@nokia.com
Phone No +256751323077
System / Network
Element
BS
RAN
1. Hop Name SW Upgrade
Requested Outage
Date and Time
(Subject to Approval)
Start Date (dd/mm/yy)
Start Time
(hh:mm)
12:00Hrs
End Date (dd/mm/yy) End Time
(hh:mm)
23:00Hrs
2. Hop Name SW Upgrade
Requested Outage
Date and Time
(Subject to Approval)
Start Date (dd/mm/yy)
Start Time
(hh:mm)
End Date (dd/mm/yy)
End Time
(hh:mm)
3. Hop Name
Requested Outage
Date and Time
(Subject to Approval)
Start Date (dd/mm/yy)
Start Time
(hh:mm)
End Date (dd/mm/yy)
End Time
(hh:mm)
Roll-back Trigger Time Dates (dd/mm/yy)
Time
(hh:mm)
Implemented change
monitoring period
1Hrs
Detailed Description
of Change Requested
RAN 14 feature aimed at call drop reduction.
Reasons for Change
Requested / Results to
Be Obtained
To activate the call re-establishment feature in RNC AHRNC01 and BURNC02
Risk Analysis:
Impact of Change
Requested on Network
/ Service
NEs / Services Affected
AHRNC01/BURNC01 and the sites for both RNCs
NEs / Services Potentially Affected
Not sevice affecting
Performance Degradation
crforcallreestablishment-150821224140-lva1-app6892.doc
1/4

2. Change Request - Management Process Operations
Loss of Redundancy Protection
Design
Other
Dependencies
Has the Change
Requested Been
Tested?
If Yes, Attach Test
Documents.
Yes No
If Yes, State Results: If No, Give Reasons:
In Case the Change
Has Not Been Tested:
Has the Change
Requested Been
Implemented Before?
Yes No
If Yes, When and Where?
List
Departments/Names
That Should Be
Notified of Change
Requested or that
have dependencies
upon.
Core X Radio
TX VAS
X OSS IT
Power Fixed
IN Names added
Resource Plan (ASP)
1. Project Manager
Name Edward okoth
e-Mail Edward.okoth.ext@nokia.com
Phone No +25671323077
2. Implementation Engineer 2
Name William Mpuuga
e-Mail William.mpuuga@airtel.co.ug
Phone No +256704005066
3. Implementation Engineer 3
Name Jerome Lubega
e-Mail Jerome.lubega@airtel.co.ug
Phone No +256 704005665
Escalation Path
(ERICSSON)
1. Project Manager
Name
e-Mail
Phone No
2. Implementation Manager
Name
e-Mail
Phone No
3. On-site Supervisor
Name
e-Mail
Phone No
crforcallreestablishment-150821224140-lva1-app6892.doc
2/4

3. Change Request - Management Process Operations
4. Other
Name
e-Mail
Phone No
Attached
Documentation*
Other:
* Additional documentation may be required for certain types of CRs.
crforcallreestablishment-150821224140-lva1-app6892.doc
3/4

4. Change Request - Management Process Operations
2. Approvals
Submitters must hand in the CR to the MS technical Approver of the respective area first. If he approves it,
he will pass it on to the Airtel technical Approver. If he approves it, he will pass it on to the MS Ops Director
who will take it to the update the Airtel ND. The timeslot in case of dependencies with other planned work
may be changed.
MS technical Approver
Approver’s Name
Department Position
e-Mail Phone No
Approved Yes No
Date (dd/mm/yy)
Additional Remarks
Signature
Airtel technical Approver
Approver’s Name
Department Position
e-Mail Phone No
Approved Yes No
Date (dd/mm/yy)
Additional Remarks
Signature
Approved execution of the activity (atleast 4 days after the approval date)
Scheduled Date and Time
Start Date (dd/mm/yy) Start Time (hh:mm)
End Date (dd/mm/yy) End Time (hh:mm)
Scheduled Outage Time
(If Applicable)
Start Date (dd/mm/yy) Start Time (hh:mm)
End Date (dd/mm/yy) End Time (hh:mm)
Completion of
Implemented change
monitoring period
(recommended 48 hrs)
Date (dd/mm/yy) Time (hh:mm)
Reasons for New Timeslot
(If Applicable)
Additional Remarks
MS Operations Director Airtel Network Director
crforcallreestablishment-150821224140-lva1-app6892.doc
4/4