Wholesale: Products & Services

Archived System CR SCR052416-1IG Detail

The EASE / CORA ASR Gateways are being updated to support changes for ASOG 53, including ASOG, MECH SPEC and UOM-ASR Schema changes as mandated by ATIS –OBF. Details of the ASOG 53 industry changes can be found at http://www.atis.org/. New or changed fields and forms being added to the ASOG form package are as follows:

• ECI Form – modification to update ASR revision process for National and Company Specific modifications and change in verbiage to remove record layout form reference.

• Transport Form – Modification to general text to identify the value in REQTYP on the ASR is mutually exclusive for the life of the ASR.

• EUSA Form – Modification to general text to identify the value in REQTYP on the ASR is mutually exclusive for the life of the ASR.

• NAI Form: Addition in general text to note regarding the cancellation of the NAI when the associated ARI/ACI form is cancelled.

• TQ Form: Addition of general text to require section if 1st postion of TQ field on the ASR form is ‘S’, ‘U’ or ‘T’.

• ASC-EC field (FORM:ASR) modification of Definition Note 2 to note the value must be retained for the life of the ASR.

• ASR NO (FORM:ASR, FGA, WAL, TRUNK, TRANSPORT, MSL, ACI, SES, OB, CN/R, CN, PC, EUSA, EOD, SALI, EVC, VCAT, MEC, TQ, RING, ARI, VC, NAI, ECI, PIP, DIS, PVC) modification of Definition and Usage Note to prohibit on initial requests.

• EVCI (FORM:ECI) Modification of Valid Entry Note 5 to require that all UREF data must be cancelled first thru UACT of “K” and, on a subsequent supplemental request, the EVCI field can then be changed from “B” to blank.

• GETO (FORM: EUSA, GETO) – Addition of valid entry for “F”.

• NVC (FORM:TRANSPORT, EUSA) – Addition of Valid Entries (Number of Virtual Connections (VC)) 1 – 20

• PON (FORM: ASR) - Addition of Note 2: Original value must be retained for the life of the ASR request.

• PTV (Form: ACI, SES)- Creation of New Field – Power Type and Voltage – Identifies the type of power and voltage at a host or end user location.

• PVC NUM (FORM: PVC) Addition of Definition Note 4 that the PC NUM is designated for the life of the ASR, Note 5: that the total number of PVC NUM must equal the value in the NPVC field, Note 6: the quantity cannot exceed 20 PVC NUMs on an order, and Note 7: the PVC NUM must be unique.

• PVCI (Form:ASR) Modification of Valid Entry Note 1 for verbiage Modification of Valid Entry Note 4 that cancellation of a PVCNUM is first thru a K, and supplemental requests will modify the PVCI field from “B” to Blank.

• QSA (FORM: ASR) Addition of Definition Note 3: The QSA field must equal the total number of PRILOC/SECLOC locations designated with an E. Note 4: The QSA field must equal the total number of Ring and ARI forms that contain an E in the first position.

• RCID (FORM:EUSA) Creation of New field – Related Circuit ID – Identifies the provider related NNI circuit ID to be used to determine the drop port equipment assignment.

• REF NUM (FORM :MSL, ACI, CN/R, CN, PC, ARI) Addition of Definition Notes to address the retention thru the life of the ASR.

• REQTYP (FORM:ARI) Addition of Definition Note 4 to identify retention for the life of the ASR.

• RTR (FORM: ASR) Relocation of Definition Note 1 to Usage Note section.

• SAC (FORM: TQ) Addition of Definition Note 2 to require unique value of SAC field entry.

• SEI (FORM: ASR) Addition of Definition Note 2 to further define no modification to the SEI field on a supplement.

• UACT (FORM: ASR) Addition of Valid Entries Note 3 to utilize the UACT of K to cancel EVC Connections.

• UREF (FORM: EVC) Modification of Definition Note 3 to include all UREFs being cancelled, addition of Definition Note 4: define a limit of 20 UREFs, and valid Entry Note 1 that the UREF value must be unique.

• ZIP CODE (FORM: ASR, WAL, SALI) Modification to provide additional examples.

Status History

Project Meetings

9/21/16 System CMP Meeting Mark Coyne – CenturyLink said this CR has been in CLEC TEST as of September 15, 2016. Mark asked if there were any objections to moving this CR to a Completed status.

Kim Isaacs - Electric Lightwave said she would like to keep it open another month.

Mark Coyne – CenturyLink said we will look at it again in October.

8/17/16 System CMP Meeting Mark Coyne – CenturyLink said for CORA, the Draft Technical Specifications were sent on July 8. A Walkthrough for CORA was held on July 18 and the planned effective date for CORA is September 19, 2016. For EASE, the Draft Technical Specifications were sent on July 22 and they have an effective date of October 3, 2016 to coincide with the Access Consolidation date.

7/20/16 System CMP Meeting Mark Coyne – CenturyLink said this CR was presented in June and it was originally specific to EASE. With the change in Production effective date for EASE 1.0 to October 3, 2016, there will be a release for CORA and one for EASE. For CORA, the Draft Technical specifications were sent on July 8 and the Walkthru was held on July 18 with the planned effective date of September 19, 2016. For EASE, the Draft Technical specifications will be sent on July 22 with the Walkthru to be held on August 2 and the effective date will coincide with the Consolidation implementation on October 3, 2016. These dates are included in Attachment M in the OSS Interface Release calendar.

6/15/16 System CMP Meeting Letty Walker – CenturyLink presented this new CR for EASE/CORA associated with ASOG 53. Letty presented a summary of all of the changes listed in the CR Description and said the ASOG release will be implemented on September 17, 2016. NOTE: The Release Production Date on the OSS Interface Release calendar is September 19, 2016.

Kim Isaacs – Integra asked why the CR included CORA.

Letty Walker – CenturyLink said if the Access System consolidation scheduled for August 1, 2016 was delayed for some reason, both EASE and CORA would need to be updated.

Mark Coyne – CenturyLink said the Draft Technical Specifications will be sent on July 8, 2016.

CenturyLink Response