cr for call re establishment
TRANSCRIPT
Change Request - Management Process Operations
Mobile Network Operations Change Request FormChange 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 OkothDepartment NetworksPosition RAN Design& Optimization Engineere-Mail [email protected] No +256751323077
System / Network Element
BSRAN
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 AffectedAHRNC01/BURNC01 and the sites for both RNCsNEs / Services Potentially AffectedNot sevice affectingPerformance Degradation
document.doc 1/4
Change Request - Management Process Operations
Loss of Redundancy Protection
Design
Other
Dependencies
Has the Change Requested Been Tested?If Yes, Attach Test Documents.
Yes NoIf Yes, State Results: If No, Give Reasons:
In Case the Change Has Not Been Tested: Has the Change Requested Been Implemented Before?
Yes NoIf Yes, When and Where?
List Departments/Names That Should Be Notified of Change Requested or that have dependencies upon.
Core X RadioTX VAS
X OSS ITPower FixedIN Names added
Resource Plan (ASP)
1. Project ManagerName Edward okothe-Mail [email protected] No +25671323077
2. Implementation Engineer 2Name William Mpuugae-Mail [email protected] No +256704005066
3. Implementation Engineer 3Name Jerome Lubegae-Mail [email protected] No +256 704005665
Escalation Path (ERICSSON)
1. Project Manager Namee-MailPhone No
2. Implementation ManagerNamee-MailPhone No
3. On-site SupervisorNamee-MailPhone No
document.doc 2/4
Change Request - Management Process Operations
4. OtherNamee-MailPhone No
Attached Documentation*
Other:
* Additional documentation may be required for certain types of CRs.
document.doc 3/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 ApproverApprover’s NameDepartment Positione-Mail Phone NoApproved Yes NoDate (dd/mm/yy)
Additional Remarks
Signature
Airtel technical ApproverApprover’s NameDepartment Positione-Mail Phone NoApproved Yes NoDate (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
document.doc 4/4