Wholesale: Products & Services

Archived System CR SCR120904-01IG Detail

Draft Technical Specifications Issued December 31. 2004

Comment cycle starts December 31, 2004

Comment cycle ends January 18, 2005

Final Technical Specifications Issued January 28, 2005

Testing Available February 12, 2005

Planned Release Production Date March 14, 2005

Details of this release could be found at:

http://www.atis.org/atis/clc/obf/obfhom.html

Expected Delivery:

Upgrade QORA Application to support ASOG 30 changes.

PLEASE NOTE: The following additional enhancements will be implemented in a point release, scheduled for May 16, 2005.

Additional change is if customers wish to have a DLR (ASR only), customers are required to provide Design Contact information only. In order to help automate/expedite the creation and delivery of DLRs, Qwest is requiring that customers be required to populate a routing field on the ASR. This field (DRC) would help systems route DLRs automatically and greatly reduce manual handling of DLRs. Qwest is also implementing an edit in QORA that requires that the DRC is populated when the RTR = S or 01 through 10.

Upgrades to support enhanced validations on referenced data and to support systematic rejection of ASRs for incorrect or inappropriate data in address, CFA, or NC/NCI/SECNCI fields, as described in detail in the Systems Notification SYST.03.01.05.F.02632.ASRPointReleaseDetails and supplemental notice, will also be included in the May 16, 2005 release.

Implementation dates of March 14, 2005 and May 16, 2005.

Status History

Project Meetings

May 18, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that this CR was deployed last Monday and is now in CLEC Test.

5/6/05 Adhoc Meeting with AT&T Attendees: Sharon Van Meter - AT&T, Ralph Olson - AT&T, Cassandra Hunt - Qwest, Cindy Kalakis - Qwest, Michael Lopez - Qwest, Lynn Stecklein - Qwest Purpose of Meeting Lynn Stecklein - Qwest stated that AT&T requested this meeting to discuss a question on the DRC edit in the upcoming point release scheduled for May 16, 2005. Discussion: Ralph Olson - AT&T stated that his question was associated with the CCNA and the DRC code. He wanted to know if Qwest performed any validation or edit against the CCNA used. He asked this question due to the fact that they use different CCNA's in different scenarios (ie. AT&T, ATX, TPM). Cindy Kalakis - Qwest said that we do not and will be routed appropriately. Ralph Olson - AT&T asked if address validation for LV1, LV2, LV3 would be in the release. Cassandra Hunt - Qwest said no. Ralph Olson - AT&T asked if Qwest was planning on this validation in the future. Cindy Kalakis - Qwest said that the decision was being reviewed by our leadership. Ralph Olson - AT&T asked if the release included any edits against the CCEA field requesting COAX information. Ralph said that they do not have that information. Cassandra Hunt - Qwest stated that edit is pending but will keep that in mind for the future. Ralph Olson - AT&T stated that he will let his agent know that the edit is pending. Sharon Van Meter - AT&T thanked Qwest for meeting with them on such short notice. There were no other questions.

- April 20, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that the edit portion of this CR is targeted for deployment on May 16, 2005. Connie Winston-Qwest stated that Eschelon submitted questions regarding the 4.1 Point Release. Connie stated that for pre-release testing, it is the same window as SATE, is available for ASR NDM for 1-month. Connie stated that this is an app-to-app test window and is critical to the IXCs because it is a flash cut. Bonnie Johnson-Eschelon asked if this was not for the GUI. Connie Winston-Qwest stated no, it is for NDM, and noted that the notice was not really clear. Connie Winston-Qwest stated that address validation follows the same disclosure rules. Connie stated that we are applying an edit and that for this there would not always be a test window. Connie stated that some Companies had not exactly coded to the disclosure document so Qwest opened-up NDM testing so there would be no surprises. Bonnie Johnson-Eschelon asked to clarify that the edits have been in the business rules and that some CLECs did not code to it, so now they need to because the edits will now be enforced. Connie Winston-Qwest said yes. Stephanie Prull-Eschelon asked how this was going in on a point release when code is needed. Connie Winston-Qwest stated that this is not a coding change; Qwest is just going to enforce what was there all along. Connie noted that there is only 1 person wanting to test. Stephanie Prull-Eschelon stated that she understands and stated that the question is if their Service Manager did not talk to them, it is like IMA in that enforcing an edit is coding. Connie Winston-Qwest stated that those that were talked to, by the Service Managers, were those who were at risk and are not CLECs. Connie stated that this is not impacting to the CLECs. Stephanie Prull-Eschelon asked if this was because it is ASR. Connie Winston-Qwest stated that this is not impacting to CLEC local products, via ASR. Liz Balvin-Covad questioned whether the documentation was accurate and that some Companies coded inaccurately. Connie Winston-Qwest stated yes and noted that the documentation has been accurate for 2 ½ years. Liz Balvin-Covad asked if the changes impacted ASRs for local products given the Interface is the same for ASR order processing. Connie Winston-Qwest stated that this was brought to CMP so that the CLECs would be aware that this was happening. Connie stated that Qwest has worked with the IXCs and stated that Qwest has not seen problems on CLEC orders. Liz Balvin-Covad asked that if the CLECs had to make coding changes it would not be in a point release. Connie Winston-Qwest stated yes and noted that this is for electronic ASRs, via NDM. Stephanie Prull-Eschelon stated that this could be impacting to the CLECs. Connie Winston-Qwest stated that there is a small potential and stated that for ASRs Qwest is working towards UOM OBF Guidelines and are working with the IXCs. Connie stated that this was brought to CMP due to the few products that are ASR local products. Connie noted that some CLECs are also IXCs and that is part of the confusion. Liz Balvin-Covad stated that if this impacts ASRs and is the same product for IXC and CLECs, this could impact a CLEC. Connie Winston-Qwest stated that Qwest notified everybody, issued a CMP CR and have had discussions about this. Stephanie Prull-Eschelon stated that she did see the documentation notice and stated that it had no comment cycle. Connie Winston-Qwest stated that a System Courtesy Notice was sent. Stephanie Prull-Eschelon stated that it did not follow the normal path. Connie Winston-Qwest stated that she would look at that but stated that she did not think that LIS Trunks would be impacted. Connie stated that there are very different rules for IXCs then for CLECs. Connie stated that she would look at the products impacted for local ASRs. Stephanie Prull-Eschelon asked to confirm that Qwest was only going to enforce the rules that were always there. Connie Winston-Qwest stated that documentation was not changed and noted that the Courtesy Notice was sent as an FYI just to remind the CLECs that this was taking place. Bonnie Johnson-Eschelon stated that maybe the notice needed more information. Connie Winston-Qwest stated that more information could be provided, for future notices. Bonnie Johnson-Eschelon suggested that the notice could have noted that the documentation had always been there, that Qwest was just going to enforce edits, and that there would be no documentation changes needed

- APRIL 1, 2005 COMMUNICATOR EXCERPT: Announcement Date: April 01, 2005 Proposed Effective Date: May 16, 2005 Document Number: PROS.04.01.05.F.02761.OrderingV71PreOrderV36 Notification Category: Process Notification Target Audience: CLECs, Resellers Subject: CMP - Ordering Overview V71 and Pre-Ordering Overview V36 Level of Change: Level 3 Associated CR Number or System Release Number: Qwest CR # SCR120904-01IG

Summary of Change: On April 1, 2005, Qwest will post planned updates to its Wholesale Product Catalog that include new/revised documentation for Ordering Overview and Pre-Ordering Overview. These will be posted to the Qwest Wholesale Document Review Site located at http://www.qwest.com/wholesale/cmp/review.html. The updates are associated with the QORA 4.1 Release also noticed on March 1, 2005 in the System Notification SYST.03.01.05.F.02632.ASRPointReleaseDetails. In the Pre-Ordering Overview, the Description section was updated to include information for services ordered with an ASR. In the Ordering Overview Description section, the Service Request Preparation subsection added an Activity Types-ASR table and added the subsection Requesting DLR - ASR. Current operational documentation for this product or business procedure is found on the Qwest Wholesale Web Site at this URL: http://www.qwest.com/wholesale/clecs/preordering.html http://www.qwest.com/wholesale/clecs/ordering.html

Timeline: Planned Updates Posted to Document Review Site: Available April 01, 2005 CLEC Comment Cycle on Documentation Begins : April 02, 2005 CLEC Comment Cycle Ends, 5:00 PM, MT: April 16, 2005 Qwest Response to CLEC Comments (if applicable): Avalable May 01, 2005 http://www.qwest.com/wholesale/cmp/reviewarchive.html Proposed Effective Date: May 16, 2005

- March 16, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that the upgrade was on March 14th and that there are no known problems. Jill stated that this CR would move back to Development status for the deployment of Phase 2, which is the Qwest edit portion, and is targeted for May 16th. Jill Martain-Qwest stated that the Qwest edits would deploy on May 16th and that this action item is now closed.

- MARCH 1, 2005 COMMUNICATOR EXCERPT: Announcement Date: March 1, 2005 Effective Date: May 16, 2005 Document Number: SYST.03.01.05.F.02632.ASRPointReleaseDetails Notification Category: System Notification Target Audience: CLECs, ILECs, Resellers, IXCs, Wireless Subject: QORA Gateway Release 4.1 Associated CR # or System Name and Number: Qwest CR # SCR120904-01IG ASOG 30-QORA Upgrade On February 21, 2005 Qwest posted changes to the ASR QORA GUI documentation demonstrating the final changes for Release 4.0 and point release 4.1. This notice serves as a detailed description of the changes customers can expect resultant from the implementation of the point release on May 16, 2005. Additional supplemental details are provided in an attachment to this notification. Changes to Connecting Facility Assignments (CFA) and NC-NCI Combinations Effective May 16, 2005, the QORA Gateway Release 4.1 will implement up-front validations on Access Service Requests (ASR) for service address, CFA, and NC-NCI combinations. Qwest will reject ASRs when the information provided by customers in these fields is not valid, or not provided, until the error condition is resolved. Qwest strongly encourages customers to take advantage of the Pre-Order Validation tools that are available through QORA that will assist them in resolving issues related to these new validations and avoid rejection of ASRs. - QORA-GUI Pre Order Validation: - Pre-Order XML interface For information concerning system access for these two resources, refer to: http://www.qwest.com/wholesale/systems/asr.html#doc For questions or assistance, customers should contact their Service Manager as soon as possible to avoid rejection of your ASRs once these validations are implemented. Changes to Design Routing Code (DRC) Information In addition to the validations described above, Qwest will also require that the Design Routing Code (DRC) field on the ASR form be populated whenever a Design Layout Report (DLR) is requested on the ASR. This enables customers to receive the DLR mechanically. An option is also available through the use of a DRC code to view the DLR via access to Customer Electronic Maintenance and Repair (CEMR). A digital certificate is required for this option. If customers currently do not have a DRC code established for mechanical distribution of the DLR with Qwest, or if they wish to establish access to CEMR, they should contact their Service Manager as soon as possible to avoid rejection of ASRs once this edit is implemented. Training Details Training is available specific to these new validations and is titled: 'QORA Pre-Order Validation Review.' For information on this and other training that is available for QORA, refer to: http://www.qwest.com/wholesale/trainingNotice.html Customer Testing Window The Customer testing window will be available 30 days prior to the May 16, 2005 release. Customers have the opportunity to submit test cases to our Production Validation (test) environment to help assure the new release works as documented by Qwest. Please contact Michael Lopez at Michael.Lopez@qwest.com or 303 965 2508 to schedule a desired timeframe for testing. A test plan will be required from you which will document how many and what type of ASRs will be submitted during testing. Timeline: Final QORA GUI Documentation was made available: February 21, 2005 Notice Providing Point Release Details: Available March 1, 2005 Customer Testing Window Begins: Available April 16, 2005 Point Release Implementation Date: May 16, 2005 If you have any questions or would like to discuss this notice please contact your Qwest Service Manager, on . Qwest appreciates your business and we look forward to our continued relationship. Sincerely, Qwest

ADDITIONAL SUPPLEMENTAL INFORMATION: SUPPLEMENTAL TO NOTICE: SYST.03.01.05.F. 02632.ASRPointReleaseDetails Following are descriptions of the validations and edits that will prevent the acceptance of the ASR.

SERVICE ADDRESS VALIDATION

QORA GUI Service Address Validations ASR Process Supplemental Match When the user's address entry produces a 'supplemental match' response, the system shall display an error message to the user indicating that an exact match has not been found.

The system shall then allow the user to select an address from a list of supplemental matches using a link to the existing GUI pre-order tool. The system shall populate the address value with the user's selection during the ASR process.

QORA-NDM Service Address Validations ASR Process Supplemental Match If the user submits an ASR via NDM for which supplemental address matches are found, the system shall reject the ASR with an error message indicating that the ASR was rejected because the address entered did not produce an exact match.

QORA GUI Service Address Validations ASR Process Near Match When the user's address entry produces a 'near match' response, the system shall display an error message to the user indicating that an exact match has not been found.

The system shall then allow the user to select an address from a list of near matches using a link to the existing GUI pre-order tool. The system shall populate the address value with the user's selection during the ASR process.

QORA-NDM Service Address Validations ASR Process Near Match If the user submits an ASR via NDM for which near address matches are found, the system shall reject the ASR with an error message indicating that the ASR was rejected because the address entered did not produce an exact match.

QORA GUI Service Address Validations ASR Process No Match When the user's address entry produces a 'no match' response, the system shall display an error message to the user indicating that an exact match has not been found.

The system shall then allow the user to use a link to the existing GUI pre-order tool to find a valid address. The system shall populate the valid address value during the ASR process.

QORA-NDM Service Address Validations ASR Process No Match If the user submits an ASR via NDM for which no address match is found, the system shall reject the ASR with an error message indicating that the ASR was rejected because the address entered did not produce an exact match.

EXCEPTIONS: For addresses receiving one of the above errors, the following entries may be used per the Industry Standard ASOG 30 Guidelines: - New Construction-if the location/address has not had Qwest telephone service prior to this request, the NCON field should be populated with 'Y' - For Unnumbered addresses, Provider Assigned Numbered addresses, descriptive addresses, or Rural route/Box number addresses, the AFT field should be populated with the appropriate entry for the condition. The address will not be validated under the following conditions: - The ASC-EC field is populated - The PRILOC field contains a valid CLLI code - The SECLOC field contains a 'C' and valid CLLI code. - the address state=NV -or- IL -or- CA

CFA VALIDATION:

NAME: CFA FORMAT DESCRIPTION: The system shall validate that the CFA format is correct. The correct format of the CFA is as follows: Facility Designation: 1-5 alpha/numeric characters Facility Type: 1-6 alpha/numeric characters Channel / Pair / Time Slot: 1-5 alpha/numeric characters Location A/Z: 8- or 11-character CLLI code

If the format of the CFA is not correct, the system shall reject the ASR.

Error Messages CFA value of '' invalid. Must be in form 'desg/type/channel(-endchannel)/loca/locz'. Facility Designator must be 1-5 alphanumeric characters. Facility Type must be 1-6 alphanumeric characters. Channel From must be numeric. Channel To must be numeric. When Channel To is populated, entry must be greater than Channel From. LOCA must be 8 or 11 characters. LOCZ must be 8 or 11 characters.

NAME: CHANNEL RQNGE DESCRIPTION: The system shall validate that the Channel / Pair / Time Slot entry falls within the valid range for the Facility Type. Valid ranges are:

T1 (or equivalent): 1-24 T3 (or equivalent): 1-28

If the CFA Channel / Pair/ Time Slot does not fall within the valid range, the system shall reject the ASR.

Messages that are produced as part of this requirement: Channel must be in range of 1-24. Channel must be in range of 1-28.

NAME: A/Z LOCATIONS DESCRIPTIONS: The system shall validate that the CLLI code entries for locations A and Z are valid CLLI codes. If the CLLI code entries do not represent valid CLLI codes, the system shall reject the ASR.

NAME: VALID CIRCUIT DESCRIPTION: The system shall validate that the facility information entered in the CFA field(s) represents a valid Qwest facility. A 'valid' facility is one for which each element meets the format and valid value requirements defined in above, and all elements together match a facility in the source system

If the CFA information does not represent a valid Qwest facility, the system shall reject the ASR.

NAME: AVAIILABLE CIRCUIT FOR ASR.ACT DESCRIPTION: When ASR.ACT=N, the system shall validate the CFA and /SCFA fields that the status on the facility returned by the source system is 'SPARE': Following are the forms and fields that are validated

Form Field(s) FGA CFA/SCFA TRANSPORT CFA/SCFA TRUNKING CFA/SCFA WAT CFA ACI CFA/SCFA EUS CFAPRI/CFASEC

If the facility status is anything other than SPARE for the CFA entered in any of these fields when ASR.ACT=N, the system shall reject the ASR.

NAME: AVAILABLE CIRCUIT FOR MSL.LEGACT DESCRIPTION: When MSL.LEGACT=N, the system shall validate that the status on the facility returned by the source system is SPARE Multi-Point Service Leg Form - .SCFA field

If the facility status is anything other than SPARE for the CFA entered in any of these fields when MLS.LEGACT=N, the system shall reject the ASR.

NAME: AVAILABILITY RANGE DESCRIPTION: If the user populates the CFA Channel / Pair / Time Slot information with a range of channels, the system shall validate that all channels in the entered range are available according to the rules for each CFA/SCFA field

The 'Channel From' must be lower than the 'Channel To' value in all cases where the user enters a range of channels. The channels may not be equal.

If the Channel/Pair/Time Slot information is invalid as described above, the system shall reject the ASR.

EXCEPTIONS: For CFA entries receiving one of the above errors, the following entries may be used per the Industry Standard ASOG 30 Guidelines, in which case the ASR will be accepted: - CFA entry = 'New' - ASRs that where RPON is populated, e.g., disconnect-new connect reusing facilities - 'OC' level CFAs - ASC-EC is populated

NC-NCI VALIDATION

FIELD/VALIDATION: NC Required DESCRIPTION ON CONDITIONS: The system shall validate that the NC code is populated according to the following conditions: TRANSPORT FORM: NC: Required when ACT= N, C, or T, otherwise optional.

TRUNKING FORM NC: Required when ACT=N or C, otherwise optional.

FEATURE GROUP A FORM NC: Required when ACT=N or C, otherwise optional.

RING FORM NC: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

ADDITIONAL RING INFORMATION FORM NC: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

END USER SPECIAL ACCESS FORM NC: Required when ACT=N, C, or T, otherwise optional.

If the ASR does not meet the conditions as described, the ASR will be rejected.

FIELD/VALIDATION: NCI Required DESCRIPTION ON CONDITIONS: The system shall validate that the NC code is populated according to the following conditions:

TRANSPORT FORM: NCI: Required when ACT= N, C, or T, otherwise optional.

TRUNKING FORM NCI: Required when ACT=N or C, otherwise optional.

FEATURE GROUP A FORM NCI: Required when ACT=N or C, otherwise optional.

RING FORM NCI: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

ADDITIONAL RING INFORMATION FORM NCI: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

END USER SPECIAL ACCESS FORM NCI: Required when ACT=N, C, or T, otherwise optional.

If the ASR does not meet the conditions as described, the ASR will be rejected.

FIELD/VALIDATION: SECNCI Required DESCRIPTION ON CONDITIONS: The system shall validate that the SECNCI code is populated, according to the following conditions.

TRANSPORT FORM SECNCI: Required when ACT = N, or when ACT = C AND SECLOC = E.

RING FORM SECNCI: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

ADDITIONAL RING INFORMATION FORM SECNCI: Required when ACT=N, or when ACT=C AND SEGACT=N or C, otherwise optional.

MULTI-POINT SERVICE LEGS FORM SECNCI: Required when LEGACT=N or C and SECLOC is not a CLLI code, otherwise optional.

WATS ACCESS LINE FORM SECNCI: Required when ACT=N, C, or T, otherwise optional.

If the ASR does not meet the conditions as described, the ASR will be rejected.

FIELD/VALIDATION: SECNCI Prohibited DESCRIPTION ON CONDITIONS: The system shall validate that the SECNCI is NOT populated, according to the following conditions:

TRANSPORT FORM SECNCI: Prohibited when an MSL form is present.

END USER SPECIAL ACCESS FORM SECNCI: Prohibited when an MSL form is present, otherwise optional.

If the ASR does not meet the conditions as described, the ASR will be rejected.

FIELD/VALIDATION: Valid NC Code DESCRIPTION ON CONDITIONS: The system shall validate that the NC code is valid for the REQTYP.

If the ASR does not meet the conditions as described, the ASR will be rejected.

FIELD/VALIDATION: NC/NCI/SECNCI Combination DESCRIPTION ON CONDITIONS: The system shall validate the combination of NC, NCI, and SECNCI codes.

Note 1: Regardless of the ASOG rule requiring the presence of any of these codes, if there is a valid combination where one of the elements is blank, the system shall accept the ASR

If the ASR does not meet the conditions as described, the ASR will be rejected.

DRC EDIT FIELD/VALIDATION: DRC Required DESCRIPTION ON CONDITIONS: The system shall require that the DRC code is populated when the entry in the RTR field on the ASR form equals 'S' OR '1-10'

If the ASR does not meet the conditions as described, the ASR will be rejected.

February 16, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that the QORA ASOG Upgrade would deploy on March 14, 2005 and noted that the Qwest specific edits would be deployed at a later date. Jill stated that it would be communicated when the implementation date for the edits has been determined.

- January 19, 2005 Systems CMP Meeting Discussion: Cassandra Hunt/Qwest stated that this CR is for the upgrade of QORA and will be implemented the weekend of March 12 thru 14. Cassandra stated that there is an additional component in the CR for Qwest specific rules, to modify DRC so can route DLRs appropriately. There were no questions or comments. This CR is in Development status.

- January 12, 2005 Qwest/CLEC Walkthrough: No CLEC participation, bridge closed at 8:20 a.m. MT.

December 14, 2004 Clarification Attendees: Gary Veik-Qwest, Cassandra Hunt-Qwest, Peggy Esquibel Reed-Qwest Peggy Esquibel-Reed-Qwest reviewed the CR description and asked Gary Veik (Qwest) if there was additional information to add. Gary Veik-Qwest stated that there is no additional info. Peggy Esquibel-Reed-Qwest confirmed that this is a QORA impacted request for UDIT, EUDIT, CCSAC, LIS Trunks, UDF, E911 PS/ALI. Peggy Esquibel Reed-Qwest stated that this CR is scheduled for presentation at the January CMP Meeting.

-- December 31, 2004 Communicator Excerpt: Announcement Date: December 31, 2004 Effective Date: Immediately Notification Number: SYST.12.31.04.F.02428.ASRDraftTechSpecs40 Notification Category: Systems Notification Target Audience: CLECs, Resellers, IXCs Subject: CMP-Systems Document In Review ASR NDM Gateway Release 4.0 and ASR XML Pre-Order-Draft Technical Specifications On December 31, 2004, Qwest will post planned updates to its Draft Technical Specifications for ASR NDM Gateway Release 4.0 and ASR XML Pre-Order-Draft Technical Specifications targeted for implementation on March 14, 2005. These will be posted to the Qwest Wholesale Document Review site, http://www.qwest.com/wholesale/cmp/review.html. Summary of Change: The summary of changes for the ASR NDM Gateway Release 4.0 and the ASR XML Pre-Order is included in the Draft Technical Specifications. The Qwest EXACT application will be enhanced to support ASOG 30 changes to conform to Industry Standards. These standards are set by the OBF Committee under the direction of ATIS. Information on this release can be found at http://www.atis.org/atis/clc/obf/obfhom.htm

CenturyLink Response