Wholesale: Products & Services

Archived System CR SCR010506-01IG Detail

- The LD fields in the pre-order environment on the GUI application, or the XML interface to the QORA pre-order tool, will be enhanced to accept any postal standard abbreviation for all three (LD1, LD2, LD3) fields. The pre-order application drop downs for all three LD fields will contain all of the valid abbreviations and will be the same list for all three. This is consistent with the change made to the ordering process for these same fields with the ASOG 31 release

- PON, CCNA, VER, and ICSC. Alpha entries in these fields must be in uppercase.

-------------------------------------------------------------------------------------------

The QORA ASR Gateway and EXACT applications need to be updated to support changes for ASOG 32, including ASOG, Mech Spec and UOM-ASR Schema changes as mandated by OBF.

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

The QORA application will be updated to include new up-front edits for the following entries on the ASR. If the ASR entries do not pass the validations as described, the ASR will be rejected.

- The ASR location entries will be validated to ensure both ends of the service are located within the same LATA. CLLI codes in the ACTL, SECLOC, PRILOC fields will be utilized. Where a CLLI code is not present, the LATA will be determined based on the service address provided. Exceptions for this validation include:

o REQTYP = L

- The requested due date must be a valid workday for Qwest. Weekends and holidays are not considered valid. Specific date fields included in this editing are as follows:

o ASR Form: DDD, PPTD, PFPTD

o Trunking Form: DFOC, DFDLRD, DDLRD

o Testing Service Request Form: DTSD

- The DDD entry on the ASR form must be equal to or later than the date received on all initial and SUP = 2 ASRs.

- CFA Validation will be enhanced to ensure that all CFA/SCFA entries on the ASR are unique when multiple quantities are present. This is to ensure CFA information is not duplicated, which may generate faulty validation responses.

- The DRC field on the ASR Form, when populated, will be validated against the CCNA entry to ensure the DRC entered is a valid code for the company submitting the request. If you do not currently have a DRC code established to receive mechanized distribution of your DLR, or distribution to CEMR, please contact your service manager.

- The TSC field on the ASR form is required when the REQTYP = M or L and ACT type of C or D. ASRs where the ASC-EC code is populated will be excluded from this edit.

- The AFO field, Pos 1 must be populated with 'Y' when the QTY is greater than 24 and the REQTYP = M or L.

- The CSPC field on the Trunking Form is required when:

o REQTYP = M, ACT = N or C and TCIC is populated

o REQTYP = L, ACT = N or C

- The TCIC field on the Trunking Form is required when:

o REQTYP = M, ACT = N or C and CSPC field is populated

- The ECCKT field on the Additional Ring Information (ARI) Form is required when the SEGACT field on the ARI form = C or D.

- The SPEC field on the ASR form must be a valid Industry assigned SPEC code for a Qwest offering.

Expected Delivery:

Planned release production date of April 10, 2006.

Status History

Project Meetings

- March 15, 2006 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that this CR will be deployed on April 10, 2006.

-- January 31, 2006 Ad Hoc Meeting ATTENDEES: John Martinez, San Isabell Tel, Kelly Leverich-ELI, Bob Eggert-SBC, Sharon Van Meter-AT&T, Chad Warner-Verizon Business, Linda Isaacson-Verizon Business, Rolph Olson-AT&T, Dianne Friend-Time Warner, Steve Moser-McLeod USA, Sid Huffington-AT&T, Jerry Cermak-AT&T, James Sturgeon-McLeod USA, Vickie Tintus-Frontier, Dave Priese-Eschelon, Kim Isaacs-Eschelon, Danell Capp-AT&T, Narika Oson-AT&T, Stephanie Prull-Eschelon, Peggy Esquibel Reed-Qwest, Cassandra Hunt-Qwest, Dan Wheeler-Qwest, Cindy Kalakis-Qwest, Curt Anderson-Qwest, Michael Lopez-Qwest, Bob Weimer-Qwest, Doug Slominski-Qwest, Lydell Peterson-Qwest DISCUSSION: Peggy Esquibel Reed-Qwest stated that this meeting was scheduled per the request of the CLEC Community in order to answer questions regarding the new QORA edits that will be implemented on April 10th, via the Systems CMP CR of SCR010506-01IG. Peggy stated that the QORA ASR Gateway and EXACT applications will be updated to support changes for ASOG 32. Details surrounding the ASOG 32 industry changes can be found via the ATIS web site at: http://www.atis.org/. The new edits will be up-front edits and could result in ASR rejects. Before I turn the call over to Cindy Kalakis (Qwest) to go over the information, I just want to make sure that you all have a copy of the document that Cindy will be using in today’s discussion. The document was distributed thru several avenues: via a CMP Notice on 1/26, it was attached to today’s Systems Notice for the formal QORA Release walkthrough, and the document is also attached to the Wholesale Calendar entry for today’s meeting. If all of your technical SMEs could not attend today’s meeting, the formal QORA Release walkthrough is scheduled for February 9th, so there will be another opportunity for Q&A. With that, I will turn the call over to Cindy Kalakis. Cindy Kalakis-Qwest stated that this CR will implement Industry changes and Qwest edits. Cindy noted that the edits could result in ASR rejects, so Qwest wanted to share some information with the CLEC Community. Cindy then stated that she will start reviewing the document, provided for this meeting. Cindy Kalakis-Qwest started the review with page 3: Qwest will implement the ASOG Version 32 Industry Standard changes to the ASR forms and fields decided upon at an industry level with participating members of the OBF Committees. The effective date for this release as dictated by the industry is April 10, 2006. For detailed information about the changes on the ASR, refer to the ATIS website: http://www.atis.org/. Qwest will implement upfront validations in the QORA ASR Gateway that impact all ASRs being transmitted to Qwest electronically. This includes the web-based QORA (Qwest Online Request Application) GUI application, or through direct connections, such as NDM or UOM interfaces. Cindy Kalakis-Qwest then reviewed page 4 and stated that the following is what Qwest wants to accomplish, with the implementation of this CR: Upfront edits streamline processing time for your request, by ensuring the data supplied by you is as accurate as possible. Prior to the ASR being accepted into Qwest’s systems, you are notified of the errors on the ASR allowing corrections to be made, thereby reducing the need for costly re-issues of the ASR (supplements). An accurate ASR helps ensure the accurate provisioning of your request the first time. Accurate entries also create accurate billing, reducing the possibility for errors on your monthly bill. Cindy Kalakis-Qwest reviewed the new edit summary on page 5: ASRs not passing these validations will be rejected upfront. Both ends of circuit must be in the same LATA, requested DD must be a Qwest workday (no holidays or weekend due dates) and the DD must be equal to or later than today, all CFAs on requests for multiple circuits must be unique (this is an enhancement to current CFA validation), the DRC entered on the ASR, when required, must be the correct DRC for the CCNA on the ASR (Qwest will be building a table), the TSC field is required on Switched requests (REQTYP = M or L and the activity on the ASR is a 'C' or 'D', on Switched requests, the AFO, pos 1 must be populated when QTY is >24, CSPC and TCIC fields are required and dependent upon each other, the SPEC code entered must be valid for Qwest and the services being requested, and the requirements for population of the ECCKT field on the Additional Ring Form will be based on the segment activity, not the ASR activity field. Cindy Kalakis-Qwest reviewed pages 6 thru 8. Same LATA validation: The Gateway will determine if both ends of the circuit/facility are in the same LATA using CLLI code entries in the ACTL/SECLOC or PRILOC/SECLOC fields or, when no CLLI code is present, the LATA will be determined during address validation based on the service location address. Bob Eggert-SBC asked if this would be a new error message. Cassandra Hunt-Qwest stated yes and noted that the messages are in the Draft Tech Specs that were sent last Friday. Cindy Kalakis-Qwest then reviewed Requested DD must be a Qwest workday and equal to or later than today: the DD must be a valid workday for Qwest, i.e., not a holiday or weekend date. Manual processes are in place today and will continue for pre-negotiated weekend/holiday provisioning when required. When agreed to with the company and the customer, the actual weekend/holiday due date is indicated in Remarks, rather then in the DDD field. Ed-AT&T asked for the cut-off time. Cindy Kalakis-Qwest stated that the cut-off time is 3:00 p.m. MT and noted that there was no change in that cut-off time. CLEC asked if a Saturday DD is to be posted in the field or in Remarks. Cindy Kalakis-Qwest stated that the DD should be the next available workday. Cindy Kalakis-Qwest then reviewed All CFAs must be unique on multiple circuit requests: CFAs cannot be duplicated on requests containing multiple circuits. This prevents the ASR Gateway from sending a 'false' response for CFA availability. For example, if the same slot of the same facility is duplicated on the ASR and is available, today, CFA validation today simply checks the same facility twice, finds it available and passes the ASR through. You are then contacted for a correction to the ASR. Jerry Cermak-AT&T asked if one was ordering a new T1 on an existing T3, how low the edit would be and asked how the CFA would be made unique. Cindy Kalakis-Qwest stated that she knew of this possibility and stated that this scenario was excluded from the edit. Cindy stated that Qwest would look at the CFA and secondary CFA’s, if not new. Doug Slominski-Qwest asked if the edit was not checking for busy CFA through to TIRKS. Cindy Kalakis-Qwest said yes. Doug Slominski-Qwest asked if there would be a reject if the CFA was busy. Cindy Kalakis-Qwest said yes. Cindy Kalakis-Qwest reviewed DRC Code Validation against CCNA: Today, the ASR Gateway only validates that the DRC is populated when a DLR is requested. This additional validation will ensure the DRC entered is valid and established for you based on your CCNA entry. Validate with your Service Manager the valid codes you plan to submit on your ASRs prior to implementation of the release. Danelle Capp-AT&T asked if the DRC and CCNA’s needed to match. Cindy Kalakis-Qwest stated yes and noted that a table would be built to contain the relationships of CCNA to DRCs. Danell Capp-AT&T asked if they could have several DRCs. Cindy Kalakis-Qwest said yes. John Martinez-San Isabell Tel stated that he had heard that DRCs are not needed and that they did not have to worry about them. Cindy Kalakis-Qwest stated that for ASR DLR requests, the DRC is needed to let Qwest know how the submitter wants distributed. Cindy Kalakis-Qwest asked if they viewed via CEMR or FAX. John Martinez-San Isabell Tel stated via FAX. Cindy Kalakis-Qwest stated that it sounded like they were currently getting DLRs. John Martinez-San Isabell Tel- asked if they would now get rejects if did not provide a DRC. Cindy Kalakis-Qwest said yes and noted that they should currently be rejected if no DRC was provided. John Martinez-San Isabell Tel stated that he would discuss with his Service Manager. Cindy Kalakis-Qwest reviewed TSC required on Change/Disconnect activity types: this edit is applicable when the REQTYP entry = 'M' or 'L' on Change and Disconnect activity requests. The TSC assigned to the trunk group must be populated in the TSC field. There were no questions or comment regarding this edit. Cindy Kalakis-Qwest then reviewed, for switched requirements, AFO Pos 1-required for QTY >24. For REQTYPs of 'M' or 'L', this will require that the Additional Circuit Information form is attached to the ASR, when appropriate. There were no questions or comment regarding this edit. Cindy Kalakis-Qwest reviewed CSPC/TCIC fields required: The CSPC field is required when the REQTYP = M, ACT = N or C and the TCIC is populated, or when the REQTYP = L and the ACT = N or C. The TCIC field is required when the REQTYP = M, ACT = N or C and the CSPC is populated. Jerry Cermak-AT&T asked how Qwest would deal with a REQTYP = M when no TCICs are involved. Linda Isaacson-AT&T asked if the question was regarding based on TQ values. Cindy Kalakis-Qwest stated that the TQ would indicate if will have TCIC and QTY assignment. Jerry Cermak-Qwest stated that TCIC is the issue, CSPC is not an issue. Cindy Kalakis-Qwest stated that would be the second bulleted item on page 7. Cassandra Hunt-Qwest stated that a TCIC is not required if the CSPC is left blank. Cindy Kalakis-Qwest stated that for a REQTYP = M and ACT = C, Qwest would require the CSPS field and asked if the TCIC would not be populated. Cassandra Hunt-Qwest stated that if the CSPC was not populated, the TCIC would not be required. Jerry Cermak-AT&T stated that the default should be ISI rules as that is how it is built. Cindy Kalakis-Qwest stated that Qwest would take another look at the edit and do some analysis. {Jerry Cermak-AT&T advised Qwest that there may be situations where the CSPC/TCIC fields being required would pose a problem for AT&T. These situations were 'code openings' where the CSPC is generated by their software but a TCIC was not generated on the order and would cause the order to fail with these new edits. Qwest agreed to re-think the edits. Jerry then advised Qwest that this would not be a problem for them after all. He had more time to analyze the new edit and their (AT&T) process and found no issue. Jerry advised Qwest to not pursue this any further} Linda Isaacson-Verizon Business asked regarding the AFO for REQTYP M & L, for translation ASRs, should they not have a Trunking Form so that there would be no quantity requirements. Cindy Kalakis-Qwest stated that was correct. Linda Isaacson-Verizon Business asked if the Trunking Form was provided even if there was no trunk activity. Cindy Kalakis-Qwest asked if she were referring to a quantity over 24. Linda Isaacson-Verizon Business stated that she would verify and send an email. Cindy Kalakis-Qwest the reviewed Additional Ring Information (ARI) Form -- ECCKT field requirement based on Segment Activity, instead of ASR Activity. Today, Qwest is requiring population of the ECCKT field based on the ASR form ACT field. This is changing to a dependency upon the SEGACT field on the ARI form. There were no questions or comment regarding this edit. Cindy Kalakis-Qwest reviewed SPEC Code entry must be valid for Qwest: This edit will require that the entry in the SPEC field be a valid industry-assigned code and, in addition, that it is valid for the specific requested Qwest service. Kim Isaacs-Eschelon stated that she needs a list of valid Qwest Spec Codes. Cindy Kalakis-Qwest stated that they would be published and that Qwest would advise of the location. CLEC asked if there were any services requiring Spec Codes. Cindy Kalakis-Qwest stated that they will not be required, just validated. Sharon Van Meter-AT&T asked how the location would be communicated. Cindy Kalakis-Qwest stated that communication would be via a notice and that it would be provided prior to the implementation of ASOG 32. Cindy Kalakis-Qwest stated that the CR was being revised to add a couple of items. The first item is an enhancement for pre-order. Cindy noted that the LD field would have additional validation. With ASOG 31, the LD field entry was required to be a valid postal standard abbreviation and was for ordering only. Cindy stated that the April Release will include this change for pre-order and noted that any standard postal abbreviation can be entered. CLEC asked to confirm that ordering would not change. Cindy Kalakis-Qwest stated that was correct. CLEC asked if there were any plans to go back to certain abbreviations being in certain fields. Cindy Kalakis-Qwest stated no. Cindy Kalakis-Qwest then stated that the second addition to the CR is for PON, CCNA, VER, and ICSC. Cindy stated that when alphas are used the entries must be in uppercase or the ASR would be rejected. Cassandra Hunt-Qwest noted that this edit was already in the GUI. Cindy Kalakis-Qwest stated that UOM and NDM will now need to be uppercase entries. Cindy Kalakis-Qwest asked if there were any additional questions regarding the information that was shared on this call. There were no additional questions or comments. Cindy Kalakis-Qwest stated that she would encourage all to attend the walk through, participate in the test, validate their DRCs with their Service Managers, and to obtain access to CEMR if they so choose. Sharon Van Meter-AT&T thanked Qwest for scheduling the ad hoc meeting prior to the walk through and stated that the call was helpful. Peggy Esquibel Reed-Qwest thanked the call participants and again noted that if other questions arise, to please attend the walk through on February 9th or to send their questions to the CMP CR mailbox. Peggy Esquibel Reed-Qwest then noted that the CR would be revised to include the meeting minutes from this call and to incorporate the new information that was shared today. The call was concluded.

-- January 18, 2006 Systems CMP Meeting Discussion: Cindy Kalakis-Qwest presented the CR and asked if there were any questions. Sharon Van Meter-AT&T asked if this is the first time that the CLECs were seeing this CR. Jill Martain-Qwest stated yes and noted that this was the presentation of the New CR. Sharon Van Meter-AT&T requested an ad hoc meeting and noted that this CR would also impact AT&T’s access side of their business. Sharon stated that she would like a technical meeting. Jill Martain-Qwest stated that an ad hoc would be scheduled. Sharon Van Meter-AT&T asked if this was a Regulatory request. Jill Martain-Qwest stated that it is not Regulatory and noted that it is an Industry Guideline CR. Sharon Van Meter-AT&T asked if a vote was required. Jill Martain-Qwest said no. Dianne Friend-Time Warner asked when the tech specs would be available. Jill Martain-Qwest stated that the date for the Draft Tech Specs was January 27th. Kim Isaacs-Eschelon asked if there would be a walk through of the tech specs. Connie Winston-Qwest stated yes and noted that they are loosely attended. Cindy Kalakis-Qwest asked if the technical meeting request could be the tech specs walk through instead of an ad hoc meeting. Sharon Van Meter-AT&T asked for the date of the tech specs walk through. Cim Chambers-Qwest stated that it is around February 9th. Sharon Van Meter-AT&T stated that she would like an ad hoc meeting sooner than February 9th. Sharon stated that AT&T will have questions. Jill Martain-Qwest stated that an ad hoc meeting would be scheduled and noted that the CMP Notice for the ad hoc meeting would be sent to the CLECs. Kim Isaacs-Eschelon stated that the System Notices typically show the timeline at the bottom of the notice and stated that it is easy to miss the date for the meeting. Kim asked if the information could be moved to within the body of the notice. Sharon Van Meter-AT&T asked if it were possible for a notice to be sent advising that there is a new CR, prior to the CR being presented at CMP. Jill Martain-Qwest asked to clarify if AT&T was requesting that when an ASOG CR is submitted, if an ad hoc meeting could be scheduled prior to CMP presentation. Sharon Van Meter-AT&T said yes. Jill Martain-Qwest stated that she would look into the request. Jill then asked if there were any other questions regarding this CR. There were none brought forward. This CR moves to Development Status.

-- January 10, 2006 Clarification Attendees: Cindy Kalakis-Qwest, Cassandra Hunt-Qwest, Curt Anderson-Qwest, Peggy Esquibel Reed-Qwest

Review Requested (Description of) Change: Peggy Esquibel Reed-Qwest reviewed the CR Title and Description and asked if there was additional information to be shared. Cindy Kalakis-Qwest stated that this was a standard upgrade to ASOG 32 and that the details were located on the ATIS web site, provided in the CRs description. Cindy then noted that QORA would also be updated to include new up-front edits, specified in the CRs description. Cindy stated that she would like this CR targeted for deployment on April 10, 2006.

Confirmed Impacted Area(s): Peggy Esquibel Reed-Qwest confirmed that this Change Request was for Ordering and Provisioning.

Confirmed Impacted Interfaces: Peggy Esquibel Reed-Qwest confirmed that this CR was for QORA and EXACT.

Confirmed Impacted Products: Peggy Esquibel Reed-Qwest confirmed that the impacted products are UDIT, EUDIT, CCSAC, LIS Trunks, UDF, and E911 PS/ALI.

Establish Action Plan & Resolution Time Frame: Peggy Esquibel Reed-Qwest stated that this CR is due for presentation at the January 18th CMP Meeting.

CenturyLink Response

The Industry Release portion of this Change Request is a Telcordia development effort. The Edits portion of this Change Request has an estimated Level of Effort of 3700 - 5000 hours.

Qwest will implement this change on April 10, 2006 to support the Industry Standards through OBF.