Mop Cut Over Process

4,971 views
4,529 views

Published on

The presentation will focus on overview of a majority of processes required for the FOA Cutover and on-going Cluster Cutovers. As a result of the process development, detailed Methods of Procedures (MOP) were created which will provide a step by step guidelines in the execution of the processes.

0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
4,971
On SlideShare
0
From Embeds
0
Number of Embeds
16
Actions
Shares
0
Downloads
0
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide
  • The Coordination Team consists of Cingular and Ericsson Project Managers with Cingular as final decision maker.The Coordination Team will include escalation directions, review of alternative solutions or backup plans in the event Cut-Over is not feasible as scheduled within the maintenance window. After Site Readiness is accepted, Ericsson to coordinate BTS delivery and scheduling of resources, etc. as part of the Sch’d Site Cutover. Pre-Checks will verify that cables, floor space, are still available as detailed in the FEED package and site walk that was performed at RFS notification. The Site Cut-Over includes activities at the BSC and MSC, Transport (T1s transferred), etc. Upon initial confirmation that Green Light Test is successful on WLS, cell tech to perform E911 test calls/sector. Site Cut-Over includes E911 P2 compliance
  • Side By Side - Available floor space to install RBS without affecting service. Interface cables may or may not be required to swap over from Nokia RBS or new cables (RF/T1/E911) are installed. Temporary Move – Nokia RBS will be relocated due to floor space requirements for the Ericsson RBS. Nokia RBS will be moved in area that will permit cables to be re-connected as afallback in the event that Ericsson RBS is not able to be cut-over. Formerly considered as a “Hot Slide” but due to anchoring system, Nokia RBS will have to be powered down. RIP – Requires that Nokia RBS be deactivated and removed before Ericsson RBS can be installed. This requires longer outage. COW/COP – Cell On Wheels/Cells On Pallet
  • Pre installation Site Walk down will consist of Ericsson and NAVL (transportation resource) with the objective of identifying any site readiness issues and to clearly identify site access issues (crane required, elevator sizing for T/I on multi-floor bldg, access road difficulty, etc.). Ericsson will record detailed site readiness conditions in order to minimize “show-stoppers” for the cutover process. The Logistic Center Process and Delivery Process is identified in another slide.
  • NOC to be contacted by Coordination Team to verify status of sites. Reference to approved MOP for the activities to be performed. T1 migration could consists of utilizing existing T1s or new tested T1s. Network Access reference to having IP address and passwords in order that Switch engineer will have access for changes/modifications during the cutover process. E911 Preparations – Field tech has TVW and PSAP information. Re-cabling from Nokia to Ericsson RBS is clearly identified
  • Develop Cut-Over Sequence – Based on the site readiness in [particular cluster to be cutover the the Coordination Team (Cingular,Ericsson, Bechtel, and others) will develop a site cut-over sequence. This process assumes that the installation steps for Side By Side have been completed, while other configurations may require additional work during the Maintainance window for installation efforts.
  • Trouble shooting requires prior coordination with equipment vendors, Ericsson, Cingular, Andrews, Intrado, Powerwave. The first line support is the initial step in identifying problems.
  • Before Fall back decision is approved, all technical support would have been investigated. Fallback requires that testing of Nokia RBS be performed, including E911 verification.
  • Pre Cut Activities Process developed by Ericsson RF Group.
  • Mop Cut Over Process

    1. 1. MOP and Process Review Ericsson - Cingular
    2. 2. Prologue <ul><li>Presentation Objective </li></ul><ul><li>The presentation will focus on overview of a majority of processes required for the FOA Cutover and on-going Cluster Cutovers. As a result of the process development, detailed Methods of Procedures (MOP) were created which will provide a step by step guidelines in the execution of the processes. </li></ul><ul><li>Additional MOPs will be required as the processes are executed through out the Cut-Over Project. </li></ul><ul><li>Role Definitions </li></ul><ul><li>Coordination Team consist of decision makers from Cingular with Ericsson Support (PMs). The Coordination Team will be active during the cutover (per cluster) to ensure that obstacles and resolutions are methodically analyzed with final decisions implemented with minimal service impact to Cingualr customer’s. </li></ul>
    3. 3. Prologue (cont.) <ul><ul><li>Process for Finalizing MOPs </li></ul></ul><ul><li>The MOPs are draft versions and intended for review/updates. Review schedule with updates: </li></ul><ul><ul><ul><li>Preliminary review – February 7, 2005 with Technical Support Team </li></ul></ul></ul><ul><ul><ul><li>Review with Cingular, Bechtel - Feb.10, 2005 </li></ul></ul></ul><ul><ul><ul><li>Ericsson incorporate changes as outcome of Feb.10 and submit to Cingular on Feb.14 </li></ul></ul></ul><ul><ul><ul><li>“ Dry Run” – Round Table or On-Site (with techs), Feb.17 </li></ul></ul></ul><ul><ul><ul><li>FOA - On Cutover night, Ericsson MOP reviewers to monitor execution of MOPs </li></ul></ul></ul><ul><ul><ul><li>Ericsson update MOPs within 5 days after FOA Cutover </li></ul></ul></ul><ul><ul><ul><li>Future Cluster Cut-Overs will warrant revisions </li></ul></ul></ul><ul><ul><ul><li>Format Preference? </li></ul></ul></ul><ul><ul><li>Configuration Changes </li></ul></ul><ul><li>Elimination of “Hot Slide” configurations due to sliding of Nokia RBS requires powering down the RBS. </li></ul>
    4. 4. <ul><li>Cut Over Process Overview </li></ul><ul><li>Logistics Process </li></ul><ul><li>BTS Installation Prerequisites </li></ul><ul><li>Preparation for Installation </li></ul><ul><li>Cut-Over: Prerequisites </li></ul><ul><li>Cut-Over Process </li></ul><ul><li>E911 Cut-Over Process </li></ul><ul><li>Trouble Shooting Process </li></ul><ul><li>Fall Back Process </li></ul><ul><li>Post Cut-Over Process </li></ul><ul><li>Pre Cut (RF) Activities </li></ul><ul><li>Post Cut (RF) Activities </li></ul><ul><li>Daily Reporting Process </li></ul>
    5. 5. Cut-Over Process Overview Identify Punch list Items Yes No Yes No Yes Yes No Yes No Yes No No CUTOVER NIGHT RFS Notification Site Walk down Site Readiness Accepted Correct Punch list Sch’d Site Cutover Pre-Check Site Prior to Cutover Notify Coordination Team Review Cluster Pre-check Status NTP Swapout Perform E911 Test Calls Initiate Escalation Process NTP Cutover per MOPs Site Cut-Over Int’g Site per MOPs Escalation Procedure Troubleshoot/ Correct by 3 AM Notify Cluster Coordination Team Evaluate Cluster Fallback Perform Post-Check Acceptance Inventory Nokia/ Prepare to Ship Submit Report/ Identify Action Perform Site Tests Activate Nokia RBS/BSC Trouble shoot/Correct Problems Site Back in Service Modify DT/CDD Re-Install Nokia RBS/Site Reconnect Cabling to Nokia Notify Coordination Team
    6. 6. Logistics Process NAVL Received equipment, scanned in by NAVL and put in storage area until call out Equipment Build Specs Receive from Ericsson PM, Build and test specifications Cingular Scan Call out equip, uncrate, notify Cingular personnel to scan equipment before the start of build and test Equipment Move Request NAVL to move equipment to test area. Build and Test Ground cabinet, connect power and power up cabinet, remove flash card, load flash card with site specific IDB, change hardware to match site specs, test with BSC and load proper software for functionality, power down and place in staging area for Cingular scan Cingular Scan After building and testing to site specification, Cingular personnel will re-scan equipment to be sent to staging area for hold Return to Storage Scanned equipment is to be repacked and labeled per cluster with the correct site number. Equipment will be returned to storage by cluster and held for site deployment Shipment Request Receive shipment request from Ericsson PM for equipment by cluster and site number Equipment to Site Call out equipment request to NAVL for shipping to specific site location for install.
    7. 7. BTS Installation Prerequisites VCF Develop Work Order Create RFDS FEED Package Approved. Identify Site Type in Cluster Execute Plan and Schedule Cutover Activities Side By Side Temporary Move RIP COW COP Prepare Plans (Pre install) /// BTS Equipment Create Bill of Material Cingular approve SOW NTP/RFS Received Develop Cutover Schedule Installation Preparation
    8. 8. Preparation for Installation RFS Pre-install/Site Walk down Site Construction Complete Logistic Center Process Delivery Process RIP site COW / COP site Site Ready For Install Pre-Install “Side By Side” and /or Temporary Move MOPs Identify Site Issues Identify Delivery Issues No Identify Nokia Removal Req. Installation preparation Notify Cingular / Bechtel Yes Cut-Over Pre-Req No Yes
    9. 9. Cut-Over: Prerequisites Cut-Over Process Installation Preparations Logistics in place /// DT Pre-loaded Nokia DT ready BTS equipment ready T1 Spans Identified/Tested E911Preparations Site Ready Go / No-Go decision at 10:00 PM Proceed with Cut-Over Postpone cut-over Ready to RIP and install? No Yes Go Network Access (TelNet) No Yes No No No No No No No No No Go Coordination Team Decision Yes Yes Yes Yes Yes Yes Yes
    10. 10. Cut-Over Process Cut-Over Prereq . Develop Cut-Over Sequence Reroute/Add Cabling E911 Support Eqpmt. Confirm Maintainance Window Availability Deactivate Nokia BTS Reroute/Connect T1/RF Jumper cables Perform test calls Migrate T1 BSC/BTS Verify NIU/T1s Operational Activate Ericsson BTS BTS Processing Calls/Sector E911 (Phase 2) Successful Finalize Acceptance Testing/Record Data Trouble Shooting Yes No Troubleshooting Process Continue No Report Connect/Verify External Alarms Proceed with first/next BTS cut-over NTP Next BTS No No Yes No Yes No
    11. 11. E911 Cut-over Process 30 days advance notice to PSAP PSAP location Identified PSAP Simulator Pre-Cutover Test Call Correct PSAP Identified New / Existing T1 Reconfigure T1 Cut - over ( new ) Existing Cable Reroute RF cable ASU Verify PSAP functionality Escalate-Andrew Intrado “ Live ” PSAP Add/Reroute RF cable For 850 (TDMA) Existing New Cut-over WLS No Yes Notify Coordination Team Pass Fail Troubleshoot NTP E911 Pre Cutover Calls Verify T1/E911 (TS21) Continue trouble shooting Fallback Process Escalate E911 Support Group Fail Pass
    12. 12. Trouble Shooting Process Cut-Over Process Troubleshoot (Local Support) Problem Corrected Cutover Process Escalation Process (Need details?) Problem Corrected Yes Still within maintenance window? No Yes Continue troubleshooting Yes Fall Back Process No No No Identify Options Implement Corrective Actions MOPs
    13. 13. Fall Back Process E911 Cut-Over Coordination Team Develop Options Fall Back Site by site Basis Cut-Over Process Re-Install Nokia RBS And Related Equipment Yes Call/Drive Testing Verified Troubleshoot/Correct Coordinate Cluster Cutover Yes No No MOPs Implement COW/COP Or Other Solution
    14. 14. Post Cut-Over Process Cluster drive test Monitor cluster Any Alarms? Investigate and identify fault type Ericsson issue Dispatch resources Fix fault Yes Notify Coordination Team No Log fault and report to Cingular Notify Cingular No Trouble shoot fault Fault Corrected No Notify Coordination Team Post Cluster Cut-Over Post Cluster Success Log entry Yes
    15. 15. Pre Cut (RF) Activities
    16. 16. Post Cut (RF) Activities
    17. 17. Daily Reporting Process Prepare Site Daily Cut-over Report Send to Ericsson Project Manager Identify Problems/Institute Corrective Procedures Cut-Over Process Submit Daily/Weekly Reports to Cingular
    18. 18. Questions?

    ×