Wholesale: Products & Services

Archived System CR SCR050214-1IG Detail

The CORA ASR Gateway application is being updated to support changes for ASOG 49, including ASOG, Mech Spec and UOM-ASR Schema changes as mandated by OBF. Details of the ASOG 49 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:

• EVCSP the usage rule is changing to allow 8 or 11 characters

• LAG the new value of “D” allowing disconnect of entire LAG group.

• VPN (Virtual Private Network) – 3 new fields identified are:

o ASN (Autonomous System Number) Indicates the unique number identifying the customer Internet network ordering the Border Gateway Protocol (BGP) service.

o VPN-ACT (Virtual Private Activity) Identifies the activity requested for the VPN-ID.

o VPN-ID (Virtual Private Network Identifier) Indicates a unique identifier for the virtual private network that creates a secure network connection over a public network.

• SES (Switched Ethernet Services) form is being introduced

o Fields specific to Switched Ethernet Services are being removed from the End User or Transport form and added to the SES form.

o New field ESP (Ethernet Service Point) which contains a valid Ethernet Switching CLLI

Company Specific Edits:

New CORA Pre-Order Validations - None

New CORA GUI and ASR Gateway Validations:

• EVCSP - CTL will only allow 11 character CLLI codes.

• LAG - Prohibited when the ACT field is not "N", "C", or "D" and the REQTYP is not "E" or "S". An entry of "N" or "E" is prohibited if the QTY field is populated with a value greater than 8. An entry of N or E is only valid when the SPEC field is MOENN, BGPLU, G8032 and MCLAG.

• EVC Form

o ASN - If ASN is populated the VPN-ID field is required.

o VPN ID - required when ordering 9-2-14 UPDATE [insert EVC] SPEC = BGPLU and ASN is populated and all of the associated S-VLAN fields are not populated. When ordering VPN-ID the range must be 0 (zero) to 4294967295 this is the only valid range.

Changed CORA GUI and ASR Gateway Validations:

• EVC RUID and EVC RPON Validation

5-28-14 UPDATE [DELETE The NIC Pivot functionality will cause MOE ASRs sent to ASRNDM to be sent to EASE. There are some validation rule changes, partly because EASE does not do some of the same validations that ASRNDM does.]

5-28-14 UPDATE [ADD THE FOLLOWING Validations for EVC.RUID: (NEW RULE)

• EVC.RUID is required when the EVCI field on the ASR Form is populated (A, or B), and the AUNT field on the EVC Form is not A {which is equivalent to not populated as the only valid value is "A"}.

•EVC.RUID is prohibited when the associated AUNT field on the EVC Form is populated]

5-28-14 UPDATE [ADD THE FOLLOWING Validation for EVC.RPON: (NEW RULE)

• EVC.RPON is prohibited when the associated AUNT field on the EVC Form is populated]

5-28-14 UPDATE [CHANGE THE FOLLOWING existing EVC.RUID rule:

• REVISED RULE: EVC.RUID is required when the associated UREF field is populated and the associated AUNT fields on the EVC form are not populated]

5-28-14 UPDATE [DELETE THE FOLLOWING existing EVC.RUID rule and its error message: DELETE: EVC.RUID is prohibited when EVC.RPON is populated]

5-28-14 UPDATE [DELETE THE FOLLOWING existing EVC.RUID rule and its error message:

• DELETE: EVC.RUID is prohibited when the associated EVC.AUNT field is populated and the ASR.ACT is N.]

• ASR SPEC Validation Rules

5-28-14 UPDATE [DELETE The NIC Pivot requirements call for the validation of ASR.SPEC on SUPs: (NEW RULE) New rule: On SUPs to MOE ASRs ONLY]

5-28-14 UPDATE [INSERT o A new validation rule of ASR.SPEC will occur for MOE ASRs ONLY to prohibit a code from being added or removed on a SUP.]

• EVC SVLAN – START

o Validations will be modified to validate the 9th position of the NCI code is “T”

o SVLAN is prohibited when VPN-ID is populated

CORA GUI Changes:

• Service Type changes are as follows:

o Remove EVC - Combo - End User (E), EVC - Combo - Transport (S)

o Add EVC – Combo (E,S), SES Switched Ethernet Service (E,S)

- Customer will be required to select REQTYP E or S as applicable

• Restructure Function

o If a customer requests a Combo (SES & EVC) and wants to change to SES only or EVC only, this change be allowed prior to ASR being submitted

• SALI for SES

o For REQTYPE = E a tab will be labeled as Priloc SALI

• Reports Tab

o Remove EVC - Combo - End User and EVC - Combo - Transport and replace with SES combo in the "Service Type is" pull down

• Reports Tab create new tab

o In the "Select Service Type" pull down create new options Switched Ethernet form (with E, S as REQTYP) and remove EVC - Combo - End User (E as REQTYP) and EVC - Combo - Transport (S as REQTYP).

• REQTYP Pull Down Menu

o When users select Switched Ethernet option from the "Select Service Type" pull down require users to select valid REQTYP from the REQTYP menu.

• Restructure Option for Switched Ethernet

o Restructure option no longer applies to Transport and EUSA but to SES form for EVC combos. Copy what was done for the Transport form.

• REQTYP for RING

o Remove the edit for when ECCKT begins with “HN” the REQTYP must be “R”.

• SALI SPOT or SALI SANO

o When the REQTYP is E and the SEI field is Y the customer is required to populate either the SALI.SANO and SALI.SASN fields or the SALI.SI and SALI.SPOT fields. The entry in the SI field must be a "C" if populated and the entry in the SPOT field must be a valid 8 or 11 CLLI code. If CLLI code is provided a call to LOSDB is required.

CORA GUI and ASR Gateway Conversion:

The following guidelines will be used to convert existing switched Ethernet ASRs.

6-15-14 UPDATE [INSERT For ASRs where the REQTYP first position is ‘E’ or ‘S’ only the following guidelines will apply. For ASRs where the REQTYP first position is NOT ‘E’ or ‘S’, the ASR will NOT be converted.]

If the SEI field on the End User or Transport form = ‘Y’ the ASR will be converted to the new SES form.

If the SEI is blank and the SECNCI positions 3 and 4 equal ‘CX’ the ASR will be converted to the new SES form.

If the SEI field is blank and the SECNCI is blank then ASRs where BOTH the service code & service modifier (second subset of the ECCKT) equals AWFD, AWGD, KDFS KDGS, KEFS, KEGS, KPFS, KPGS, KQFS, KQGS, KRFS, KRGS, KXFD, KXGD, KXFS, KXGS AND the company ID (last subset of ECCKT) request ‘ACSO’ will be converted to the new SES form.

(example: xx/KXGS/xxxxxx//ACSO or xx.KXGS.xxxxxx..ACSO)

For those ASRs converted to the SES form, if the SECLOC field on the End User or Transport form contains a ‘C’ followed by a CLLI code, that CLLI will be moved to the new ESP field on the SES form.

CORA GUI Report enhancements: None

ASR Gateway Notifications/Responses: None

Status History

Project Meetings

9/17/2014 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the CR will deploy this weekend with an effective date of September 22. Mark said after checking with SME team, everything appears to be on track for this weekend and the release is in a green status.

7/16/2014 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the CORA draft technical specifications were sent on July 11 and there is a Technical walk through on the Wholesale calendar scheduled for July 17.

6/18/2014 Monthly Systems CMP Meeting Mark Coyne – CenturyLink said the CR Description for this CR had been updated by Sue Morlan – CenturyLink after the last CMP meeting after the discussion that had occurred.

Bill West – CenturyLink then reviewed the update to the switched Ethernet ASRs edit under the "CORA GUI and ASR Gateway Conversion" Section that had been made after further review of the requirements. He said what was there was accurate but required some clarification. Bill then asked Kim Isaacs – Integra whether there were any questions on the proposed updates to the CORA technical specifications that had been discussed in the May CMP meeting.

Kim Isaacs – Integra thanked Bill for the additional time for review and said the proposed updates were fine.

Bill West – CenturyLink asked if anyone else had questions about the planned changes to the technical specifications. There were none. Bill said he would proceed then with the changes with the upcoming release cycle.

Mark Coyne – CenturyLink said that the CORA technical specifications will be distributed on July 11.

5/21/2014 Monthly Systems CMP Meeting Bill West – CenturyLink began the presentation of the new CR by first presenting the ASOG 49 Industry Changes as listed in the CR. Bill asked if there were any questions on the Industry Guideline changes. There were none.

Sue Morlan – CenturyLink then presented the CenturyLink company specific edits as listed in the CR.

Kim Isaacs – Integra asked about the CR content (5/30/14 Updates received from Integra in CAPS) that referenced NIC [insert] PIVOT functionality CAUSING MOE ASRS TO BE SENT TO EASE. EASE IS AN EMBARQ SYSTEM SO THIS IS [delete AND SAID THAT WAS] related to a merger change AND WOULD NEED TO FOLLOW THE OSS TRANSITION PROCESSES IN THE CENTURYLINK/QWEST MERGER CONDITIONS.

Mark Coyne – CenturyLink said these changes had been included for future changes and that it is still being evaluated. If the changes were merger related, they would follow the normal process.

Kim Isaacs – Integra said she did not understand how this related to the September release then.

Sue Morlan – CenturyLink said this is “heads up” if CenturyLink were to move to Ease for MOE ASRs in the future

Kim Isaacs – Integra said the wording (5/30/14 Updates received from Integra in CAPS) [THIS PART OF THE CR] needed to be removed unless the changes were happening in September otherwise the merger requirements for OSS changes would have to be followed.

Mark Coyne – CenturyLink said we would review this with the SME team and would include any updates in the meeting minutes.

NOTE: CR update subsequent to the CMP call, CenturyLink will be removing the forward looking wording in the CR Description related to NIC functionality and EASE.

Donna Miller - Neustar asked a question related to the range of the VPN ID.

Sue Morlan – CenturyLink repeated the VPN-ID the range of 0 (zero) to 4294967295 as listed in the CR.

Bill West – CenturyLink indicated that the VPN-ID range must fall between those numbers.

Donna Miller - Neustar then indicated that she thought the ASOG started with one.

Bill West – CenturyLink said he thought the range was zero but would verify this and we would include it in the minutes. NOTE: Bill West – CenturyLink confirmed that the VPN-ID range does indeed begin with one (1) and not zero (0). The CR will be revised to include this correction.

Donna Miller - Neustar also questioned the reference to NIC and requested confirmation that it was not ASOG.

Bill West – CenturyLink indicated that was correct.

Kim Isaacs – Integra asked what the Conversion changes listed in the CR mean.

Bill West – CenturyLink explained that at the time of the release, any ASRs that are not completed or cancelled, CenturyLink will convert the switched Ethernet ASRs from the format they are submitted in to the new ASOG 49 format. Bill then covered the CORA GUI and ASR Gateway Conversion changes as listed in the CR. Bill said if the ASR is not related to a switched Ethernet service, the rules do not apply and then no conversion would occur. Bill asked if there were any questions. There were none. Bill then reviewed the Technical Specification modifications that he is proposing to incorporate with the release and the related benefits. He reviewed the proposed Tech spec example. He asked if there were any objections to the proposed changes to only include the proposed differences rules.

Kim Isaacs – Integra said she understood the change being requested and would like to take the question back to her SMEs.

Jeff Sonnier – Sprint asked if this was implemented, would the programmers have to look at two documents.

Bill West – CenturyLink said they have to today since CenturyLink does not include all the ASOG rules. Bill said each company should be looking at ASOG today and then each company’s differences. He said he thinks the current CenturyLink document is confusing since it has a mixture.

Donna Miller – Neustar said CenturyLink would just provide CenturyLink specific rules and not present the ASOG rules.

Bill West – CenturyLink said his proposal is to remove the ASOG specific rules and will only include the CenturyLink specific rules.

Susan Lorence – CenturyLink asked Bill to clarify how this change would be presented with the CORA Release if it is agreed to by the customer community. She asked if all of the strikethroughs would be included in the tech specs.

Bill West – CenturyLink said if approved, he would remove all of the ASOG rules (not strike through) and leave a baseline of CenturyLink specific rules and would then redline the current release updates. Bill asked if there were any other questions. There were none.

CenturyLink Response