1. CORA ASR Gateway 28.0/ ASOG 53 Release
September 17, 2016
CORA ASR Gateway 28.0/ ASOG 53 Release

2. ASOG 53/CORA ASR Gateway – 28.0
CenturyLink will implement the ASOG Version 53 Industry Standard changes to the ASR forms and fields effective on September 17, These changes were decided upon at an industry level with participating members of the OBF Committees. For detailed information about the changes, refer to the ATIS website: In support of the release, CenturyLink will implement upfront validations in the CORA (CenturyLink Online Request Application) ASR Gateway impacting all ASRs being transmitted through CORA electronically via the web-based CORA GUI, or through direct connections, such as NDM or UOM interfaces.

3. ASOG 53
ASOG Changes

4. ASOG 53: ASOG Issues included in this Release
ATIS Issue Number
Description
Champion
3492
UOM-ASR: Review and update the ‘Provider Jeopardy Status’ and ‘Customer Jeopardy Status’ business functions
ASO Committee
3515
Redefine ECI byte assignment process
3525
Update any field where Mech SPEC documentation reflects a restriction not noted in ASOG
3544
Add new field (PTV) to identify Power Supply Information on ACI and SES forms
Verizon
3547
Modify SES - GETO field to identify regulated entrance facility  to add value of F.
ATT Communications
3548
Add new RCID field to Practice 005, 007 and 013

5. ASR Form modification for ASR 53
Form Changes: • 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’.

6. Industry Field Modifications for ASR53
Field changes: • 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.

7. CORA 28.0 Edits and Enhancements

8. CORA 28.0: New or Changed Fields
New Fields to the following forms:
ASR Form: SES and ACI
Added new field - PTV - Power Type and Voltage
ASR Form: EUSA, TRANSPORT, and ACI
Added new field – RCID – Related Circuit ID
Please note – CenturyLink will allow the population of data in the PTV and RCID fields, but will not be utilizing them in any downstream provisioning or billing processes.
Custom Edits
There are no custom edits that will be implemented with CORA 28.0