Wholesale: Products & Services

Archived System CR SCR120308-01IG Detail

 
Title: ASOG 38 Industry Release/QORA and ASR Gateway Enhancements
CR Number Current Status
Date
Level of
Effort
Interface/
Release No.
Area
Impacted
Products
Impacted

SCR120308-01IG Completed
3/23/2009
-   24/ Pre-Ordering
Originator: Dalton, Laurie
Originator Company Name: Qwest Corporation
Owner: Dalton, Laurie
Director:
CR PM: Stecklein, Lynn
Description Of Change
ASOG 38 Industry Changes

The QORA ASR Gateway application needs to be updated to support changes for ASOG 38, including ASOG, Mech Spec and UOM-ASR Schema changes as mandated by OBF.

Details of the ASOG 38 industry changes can be found at: http://www.atis.org/

Qwest Specific Edits: The following changes that are customer affecting are also being implemented.

QORA Pre-OrderValidation Enhancement

-.Qwest is implementing an enhancement to the Pre-Order CFA validation tool to display the customers circuit id and PON, when available, for each circuit id returned on the CFA validation.

Ordering Enhancement

- Qwest is implementing an enhancement to associate CCNAs (Customer Carrier Name Abbreviation) that belong to the same company. When the CCNA on the CFA (Connecting Facility Assignment ) belongs to the same company as the CCNA on the ASR (Access Service Request), the CFA is considered to be 'owned' by the CCNA on the ASR..

QORA GUI Changes

-.Qwest will split the VALIDATE/NEXT button into two separate selectable buttons. The validate function can be performed at any point in the population of the ASR which may reduce input time.

New QORA GUI and ASR Gateway Validations

-..Qwest is implementing an edit to ensure that when the CFA and SCFA are both populated and when the CFA and SCFA both contain the ACTL CLLI codes in the circuit names, that the CFA is a higher facility than the SCFA. If the CFA is not a high facility, the ASR will be rejected with an error message - CFA and SCFA speed, not valid combination

-. ECCKT validation – The system shall implement an enhancement t when the ACT = C, D, and R, REQTYP = S or E for serialized circuit ids (64/hcgs/123456//ms) validate that the ECCKT is valid. If the ckt id is not found the ASR is rejected with a message of ECCKT not found.

- CFA Validation – The system shall implement an enhancement to validate the CFA on all service specific forms when the ECCKT is populated with a multipoint and segmented circuit id. When the ECCKT is populated with a multipoint or segmented circuit id, the system shall perform all existing availability CFA checks and the ASR will be rejected if the CFA is invalid or not available for assignment.

-DDD/EXP Field – When the ASR is populated with REQTYP = S or E and the ACT = N and the NC code begins with HF++ and X+++, the system shall validate that the DDD field is equal to or greater than the standard interval as shown in the standard interval guide for DS3 and DS0 services. If the interval is shorter than the standard interval, the system shall validate that the EXP field is populated. If the EXP field is not populated, the ASR will be rejected.

-.HVP Field – Transport Form – The system shall validate that the HVP field is populated when the address validation identifies High Voltage Protection is required. If the HVP field is not populated the ASR will be rejected.

- RECCKT Field - For REQTYP = M, L, ACT = D the system shall validate that the RECCKT is valid and that the Trunks shown on the ASR page ECCKT field and on the ACI ECCKT are actually riding on the RECCKT associated with them. If either of these validations fail, the ASR shall be rejected by the system with a message. For RECCKT not found or RECCKT not valid for ECCKT.

-ECCKT Field - For REQTYP = M, L and ACT = D the system shall validate that the trunks requested to be disconnected are the last trunks in a trunk group. If they are not the last, RPON must be populated or the ASR will be rejected.

ASC-EC Field – When the ACTL field or the SECLOC field is populated with a CLLI code that is not in QWEST territory, the system will validate that the ASC-EC is populated. If the ASE-EC is not populated , the ASR will be rejected.

TCIC Field – Trunking and Additional Circuit Information Forms – For REQTYP = M, ACT = N, C, D, the system shall validate the TCICs and perform busy checks if appropriate for the order type. If the TCIC is not found, or is busy for inward activity, the ASR will be rejected.

ACTI Field - The system shall implement the usage rules for this field as detailed in the ASOG. Required when the first position of the REQTYP field is "M" and ACT field is "N". Valid ACTI values must be "A", "B" or "C". Required when the first position of the REQTYP field is "M" and the ACT field is "D". Valid ACTI values must be "D", "E" or "F". If these validations are not met, the ASR will be rejected.

ACTI Field - When the REQTYP = M, ACT = D, ACTI = D and the TQ=Blank, the system shall validate that the quantity to be disconnected does not reflect the total number of trunks in the group. If the total group is being disconnected, the ASR will be rejected.

ACTI Field - When the REQTYP = M, ACT = D, and ACTI = F, the system shall validate that the quantity to be disconnected does reflect the total number of trunks in the group. If the quantity to be disconnected is less than the total group, the ASR will be rejected.

ACTI Field - When the REQTYP = M, ACT = D, and ACTI = E, the system shall validate that the quantity to be disconnected does reflect the total number of trunks in the group. If the quantity to be disconnected is less than the total group, the ASR will be rejected.

ACTI Field - When the REQTYP = M, ACT = N, and ACTI = B,the system shall validate that the first position of the TQ field is populated. If field is blank, the ASR will be rejected.

REQTYP Field - For REQTYP S or E, The system shall validate that ASRs submitted for Metropolitan Optical Ethernet which is determined by an NC code beginning with KP, KQ, or KR that the REQTYP = S or E. If the REQTYP is not S or E, the ASR shall be rejected.

Expected QORA Deliverables/Proposed Implementation Date (if applicable):

Upgrade for ASOG 38 industry related changes with additional edits to provide upfront editing and validation of ASR entries.

New options to be available in the QORA GUI March 23, 2009

Industry Guideline - OBF - ASOG 38

Status History

Date Action Description
12/3/2008 CR Submitted CR Submitted 
12/4/2008 CR Acknowledged CR Acknowledged 
12/17/2008 Status Changed Status changed to Presented 
12/17/2008 Discussed at Monthly CMP Meeting Discussed in the December ProdProc CMP Meeting - See Attachment D in the Distribution Package 
12/17/2008 Discussed at Monthly CMP Meeting Discussed at the December Systems CMP Meeting - See Attachment D in the Distribution Package 
1/9/2009 Communicator Issued SYST.01.09.09.F.05957.ASRQORA_Rel13.0DftSpec 
1/30/2009 Status Changed Status changed to Development 
2/13/2009 Communicator Issued SYST.02.10.09.F.06041.ASRQORARel13.0TechSpecUPD 
3/18/2009 Discussed at Monthly CMP Meeting Discussed in the March Systems CMP Meeting - See attachment K in the Distribution Package 
3/23/2009 Status Changed Status changed to CLEC Test 
3/23/2009 Record Update  
5/20/2009 Discussed at Monthly CMP Meeting DIscussed in the May CMP Meeting - See Attachment K in the Distribution Package 
6/2/2009 Status Changed Status changed to Completed 

Project Meetings

5/20/09 Systems CMP Meeting

Mark Coyne-Qwest said that this CR deployed on 3/23/09.

3/18/09 Systems CMP Meeting

Mark Coyne-Qwest said that this CR will deploy on March 23.

12/17/08 Systems CMP Meeting

Laurie Dalton-Qwest said that the QORA ASR Gateway application needs to be updated to support changes for ASOG 38, including ASOG, Mech Spec and UOM-ASR Schema changes as mandated by OBF. She said that it will be available on March 23, 2009. Details of the ASOG 38 industry changes can be found at: http://www.atis.org/ Qwest Specific Edits: The following changes that are customer affecting are also being implemented. QORA Pre-OrderValidation Enhancement -.Qwest is implementing an enhancement to the Pre-Order CFA validation tool to display the customers circuit id and PON, when available, for each circuit id returned on the CFA validation. Ordering Enhancement - Qwest is implementing an enhancement to associate CCNAs (Customer Carrier Name Abbreviation) that belong to the same company. When the CCNA on the CFA (Connecting Facility Assignment ) belongs to the same company as the CCNA on the ASR (Access Service Request), the CFA is considered to be 'owned' by the CCNA on the ASR.. QORA GUI Changes -.Qwest will split the VALIDATE/NEXT button into two separate selectable buttons. The validate function can be performed at any point in the population of the ASR which may reduce input time. New QORA GUI and ASR Gateway Validations -..Qwest is implementing an edit to ensure that when the CFA and SCFA are both populated and when the CFA and SCFA both contain the ACTL CLLI codes in the circuit names, that the CFA is a higher facility than the SCFA. If the CFA is not a high facility, the ASR will be rejected with an error message - CFA and SCFA speed, not valid combination -. ECCKT validation - The system shall implement an enhancement t when the ACT = C, D, and R, REQTYP = S or E for serialized circuit ids (64/hcgs/123456//ms) validate that the ECCKT is valid. If the ckt id is not found the ASR is rejected with a message of ECCKT not found. - CFA Validation - The system shall implement an enhancement to validate the CFA on all service specific forms when the ECCKT is populated with a multipoint and segmented circuit id. When the ECCKT is populated with a multipoint or segmented circuit id, the system shall perform all existing availability CFA checks and the ASR will be rejected if the CFA is invalid or not available for assignment. -DDD/EXP Field - When the ASR is populated with REQTYP = S or E and the ACT = N and the NC code begins with HF++ and X+++, the system shall validate that the DDD field is equal to or greater than the standard interval as shown in the standard interval guide for DS3 and DS0 services. If the interval is shorter than the standard interval, the system shall validate that the EXP field is populated. If the EXP field is not populated, the ASR will be rejected. -.HVP Field - Transport Form - The system shall validate that the HVP field is populated when the address validation identifies High Voltage Protection is required. If the HVP field is not populated the ASR will be rejected. - RECCKT Field - For REQTYP = M, L, ACT = D the system shall validate that the RECCKT is valid and that the Trunks shown on the ASR page ECCKT field and on the ACI ECCKT are actually riding on the RECCKT associated with them. If either of these validations fail, the ASR shall be rejected by the system with a message. For RECCKT not found or RECCKT not valid for ECCKT. -ECCKT Field - For REQTYP = M, L and ACT = D the system shall validate that the trunks requested to be disconnected are the last trunks in a trunk group. If they are not the last, RPON must be populated or the ASR will be rejected. ASC-EC Field - When the ACTL field or the SECLOC field is populated with a CLLI code that is not in QWEST territory, the system will validate that the ASC-EC is populated. If the ASE-EC is not populated , the ASR will be rejected. TCIC Field - Trunking and Additional Circuit Information Forms For REQTYP = M, ACT = N, C, D, the system shall validate the TCICs and perform busy checks if appropriate for the order type. If the TCIC is not found, or is busy for inward activity, the ASR will be rejected. REQTYP Field - For REQTYP S or E, The system shall validate that ASRs submitted for Metropolitan Optical Ethernet which is determined by an NC code beginning with KP, KQ, or KR that the REQTYP = S or E. If the REQTYP is not S or E, the ASR shall be rejected. Laurie said that there are several new edits associated with the ACTI field that are all ASOG compliant and can be found in the description of the CR at: http://www.qwest.com/wholesale/cmp/cr/CLECQwestCMPSystemsInteractiveReport.html.

CenturyLink Response

Information Current as of 1/11/2021