Hot Cut Process. Timeframes for Hot Cut Standard for Basic Cut-Over Window: Amount of time from start to completion of physical cut-over of lines:

Transcription

1 Hot Cut This is a guideline that describes hot cuts that are either through an interconnection agreement or through a state tariff. The term "Hot Cut" is used in the local exchange industry to describe the near-simultaneous disconnection of a working loop from a port on one carrier's switch, and the reconnection of that loop to a port on a different carrier's switch, without any significant out-of-service period. Initially, the loop may be any of: (a) a Consolidated retail loop, (b) a loop being used to provide resold service, (c) a part of a UNE- P arrangement, or (d) a UNE-L connected, through a collocation arrangement, to a s switch, and being used by that carrier to provide local exchange service to one of its customers. After the cutover, the loop would generally be a UNE-L connected through to a different carrier s switch. The submits an local service request (LSR) via Wisor or EDI format to Consolidated, indicating that it wishes to use the existing loop to serve the customer. A properly d LSR will generate two related Consolidated service orders: A disconnect order, for example to discontinue the existing retail service where the customer was originally a Consolidated retail customer. This order also creates the 'trigger' which sends a message to NPAC 48 hours before the due date indicating that the end user's telephone number will be ported to the. A change order to establish the UNE-L for the, along with a record order detailing listing information, including 911 data. The LSR will be routed to the Regional Operations Center for manual processing or be rejected back to the for additional work. Timeframes for Hot Cut Standard for Basic Cut-Over Window: Amount of time from start to completion of physical cut-over of lines: One (1) to nine (9) lines: one (1) Hour 10 to 49 lines: two (2) Hours 50 to 99 lines: three (3) Hours If IDLC is involved Four (4) hour window (8:00AM to 12:00PM (on) or 1:00PM to 5:00PM). Four (4) hour window applies to start time. This is only applicable if Consolidated notified the CLEC by 2:30PM EST on DD-2 that the service was on IDLC. The Consolidated Hot Cut is defined by nine key notifications; Accuracy, Confirmation, Facilities check, Summary, Dial Tone, Concurrence, Failure, Completion and Pending Facilities. Page 1 of 3

2 Requirement 1. Hot Cut Order Accuracy Rules built into the WISOR gateway specifically for BB LSR that ensures the order is entered as correctly as possible. This will include an appropriate due date, frame due time, and cable/pair/port assignment. 2. Hot Cut Confirmation When the WISOR Gateway returns a Firm Order Commitment to the CLEC for BB LSR, the service order engine will have to validate the order as able to be provisioned, including AM or PM dispatch in FDT field. 3. Facilities Check Rules built into the WISOR gateway specifically for BB LSR that ensures the order is entered as correctly as possible. This will include an appropriate due date, frame due time, and cable/pair/port assignment. 4. Hot Cut Summary When the WISOR Gateway returns a Firm Order Commitment to the CLEC for BB LSR, the service order engine return the CLLI and FDT fields. 5. Dial Tone When the WISOR Gateway returns a jeopardy notification to the CLEC for BB LSR, the service order engine return the Response Code 3G with comments to indicate that the dial tone test has failed. When the issue is resolved, we will accept a supplement and begin to reprocess the request. 3G will be limited to BB LSRs only. 6. Hot Cut Concurrence When the service order engine knows the status is ready for a hot cut, it will send another Local Response notification back through the WISOR Gateway. We will also send an urgent notification or SMS text to the contact designated in the LSR. To be able to receive this, the CLEC would need to put the appropriate address in the REMARKS field of the LSR. Page 2 of 3

3 7. Hot Cut Failure If the Hot Cut fails, the service order engine return the appropriate response code and details, depending on the error condition, through the WISOR Gateway. For BB LSRs only, we will also send an urgent notification or SMS text to the contact designated in the LSR. To be able to receive this, the CLEC would need to put the appropriate address in the REMARKS field of the LSR. 8. Hot Cut Completion tice When the Hot Cut is, the service order engine will send the Provisioning Completion tice against the BB LSR through the WISOR Gateway. 9. Pending Facilities When the WISOR Gateway returns a jeopardy notification to the CLEC for BB LSR, the service order engine return the Response Code 2B with comments to indicate that we are pending facilities assignment. When the issue is resolved, we will resend a confirm or accept a supplement. 2B will be limited to BB LSRs only. Page 3 of 3

4 The following diagram outlines the process for completing a Hot Cut (Copper) order with Consolidated. FairPoint Hot Cut (Copper) submits hot cut request receives confirming hot cut is on track customer checks for problem customer resolves issue and supplements order for new DD starts over END WSC runs to identify new hot cut requests WSC monitors for order creation and FOC (day 0 1) WSC runs FOC 3 1) Facility check 2) If facility issue will jep 2B (day 2) CSPC runs FOC 2 NDT ticket opened to CO CSPC runs FOC 2 s confirming DD CSPC Jeps the order for NDT (3G) DD CSPC notifies frame 30 minutes prior to cut time (day 5) CSPC calls the customer to confirm cut is CO checks for NDT and notifies CSPC if any issues. CO performs hot cut within 1 hour of FDT requested CO tech notifies CSPC when cut Page 4 of 3

5 The following diagram outlines the process for completing a Hot Cut (SLIC) order with Consolidated. FairPoint Hot Cut (BB V) (SLIC) submits hot cut request receives confirming hot cut is on track customer checks for problem customer resolves issue and supplements order for new DD starts over END WSC runs to identify new hot cut requests WSC monitors for order creation and FOC (day 0 1) WSC runs FOC 3 1) Facility check 2) If facility issue will jep 2B (day 2) CSDC runs FOC 2 NDT ticket opened to CO and Field Dispatch CSDC runs FOC 2 s confirming DD CSDC Jeps the order for NDT (3G)/ calls FOC 1 Opens new ticket for dispatch out for FOC date/ confirms CO ticket open DD CSDC notifies frame 30 minutes prior to cut time (day 5) CSDC calls the customer to confirm cut is CO pre wires and cuts line down to verify DT CO performs hot cut within timeframe based on # of loops and of FDT CO tech notifies CSDC when cut FOC 1 Dispatch out does pre wire at the Crossbox and does DT Tech corrects issue in the field DD tech dispatchs out to crossbox to work coordinated cut with the CO Page 5 of 3