Wholesale: Products & Services

Archived System CR SCR061405-02EX Detail

The QORA application will be updated to support UOM (Unified Ordering Model). UOM will provide another method of interface and will provide XML capability for QORA.

The CLECs will not be required to move to UOM, upon initial deployment. QORA GUI and NDM will continue to be available on the initial deployment date.

Qwest requests that the Exception Vote be conducted in an ad hoc meeting that will be held prior to the July Monthly CMP Meeting.

A vote of ‘Yes’ will allow this Change Request to be implemented on October 10, 25005.

A vote of ‘No’ will cause this change request to not be deployed on October 10, 2005.

Qwest will host a supplemental meeting on Tuesday, June 21, 2005, from 1:00 p.m - 2:30 p.m. MT, for technical experts in Information Technology. This IT-to-IT information session is designed to enhance the understanding of all technical experts on both the customer and the Qwest-side. Qwest strongly recommends that Information Technology specialists and technical experts attend this session.

This meeting will be conducted using Raindance Meeting Edition. To join online, copy and paste the link below, to your browser. You do not need to call into the audio conference. Once the moderator arrives, the service will automatically offer to dial your phone number.

June 21, 2005 Meeting Link: http://www.raindance.com/rndc/register/outlook.jsp?confid=4351044

Conference ID: 4351044

Meeting Phone #: 877.564.8688

Moderator: Terri Davis

(Notification Dated June 14, 2005: SYST.06.14.05.F.03024.Info_Sharing_Mtgs_UOM-ASR)

Additional Information Sharing meetings are planned for the following dates:

July 8, 2005 - 10:30am -11:30am MT -- Call in number: 1-877-572-8687; ID#: 798-6282

August 19, 2005 – 1:00pm-2:00pm MT -- Call in number: 1-877-572-8687; ID#: 798-6282

Expected Deliverable:

Upgrade QORA Application to support UOM ASR ordering. Requested implementation date is October 10, 2005.

Status History

Project Meetings

- September 21, 2005 Systems CMP Meeting Discussion: This CR will deploy on 10/10/05.

July 20, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that this CR was presented as a walk on in the June CMP Meeting. She said that the Exception was granted and that we will move forward with the implementation in October. Jill Martain-Qwest stated that the LOE for this CR is 5200 to 6500 hours.

-- July 13, 2005 Email Received from Eschelon: Peggy, Thanks for the information. I will have to defer to the expert Steph to determine if she has additional concerns. Bonnie J. Johnson Director Carrier Relations Eschelon Telecom, Inc.

-- July 12, 2005 Email Sent to Eschelon: Hi Bonnie, I just wanted to provide you with some information regarding your concern/email below. Is your concern due to the fact that the UOM-ASR schemas have bugs in them, and would not support certain service types if Qwest followed the UOM-ASR industry schemas to the letter? If it is, the information that I received is as follows: The UOM-ASR schema does not support "Testing Only", "TQ Only", "EOD Only", "Just TQ and EOD" requests. The schemas make the Service Specific form REQUIRED in all circumstances, even though there are certain kinds of ASRs where the Service Specific Form would not be necessary. To alleviate this, Qwest's UOM Ordering solution will not be using the Industry UOM-ASR schema "to the letter". It will be using the UOM-ASR schema with one Qwest specific modification. Qwest is making the Service Specific Forms "minoccurs=0" in the Qwest version of the schema to make the form "optional" to handle the above kinds of service requests. Another problem is the UOM-ASR schemas do not allow RINGSVC to pass TSR forms. The Qwest specific version will have an entry to TSR under RINGSVC. Those are the only outstanding defects at the UOM-ASR industry level that Qwest is aware of. The other defects were corrected with ASOG31. Attached is a synopsis of the UOM ASR defects, and their status, that Qwest had raised, at the industry level. I hope this helps in alleviating your concerns. Peggy Esquibel-Reed Qwest Wholesale CMP

July 12, 2005 Exception Vote Meeting Attendees: Peggy Esquibel Reed-Qwest, Cindy Kalakis-Qwest, Cassandra Hunt-Qwest, Terri Davis-Qwest, Lynn Stecklein-Qwest, Rosalin Davis-MCI, Nancy Sanders-Comcast Meeting Discussion: Peggy Esquibel Reed-Qwest stated that the meeting is for Qwest to conduct the exception vote for the QORA UOM ASR Ordering CR and the exception request is to allow implementation of this CR Prior to the normal implementation timeline. The CR is for QORA to be updated to support UOM and will provide XML capability for QORA ASR Ordering. Peggy then noted that the vote meeting was originally scheduled to occur on July 7th but the Quorum was not achieved, so the vote was rescheduled to take place today. Peggy then noted that quorum is not applicable for today’s vote. Peggy stated that she would recap some information before the vote is conducted. Peggy stated that: - The CLECs will not be required to move to UOM with the October deployment, but Qwest would like to make UOM available for those CLECs who do want to make the move at that time. - CLECs will not be impacted with this new interface, unless they choose to move to UOM in October. - QORA NDM and GUI will continue to be available in October. - The QORA GUI (Pre-Order) is already XML. - NDM would remain as is and that there are no changes at this time. - UOM (XML for ASR Ordering) is a 3rd interface that Qwest is introducing and is in addition to GUI and NDM. Peggy then asked if there were any questions. Rosalin Davis-MCI asked if Qwest is continuing to support mandatory testing for NDM. Cassandra Hunt-Qwest stated that customer testing will remain the same as there are no changes to NDM at this time. Rosalin Davis-MCI asked if it would be mandatory to convert to XML within the next year. Cassandra Hunt-Qwest stated that there is no date at this time. There were no other questions. Peggy then explained what the yes and no votes would mean: A vote of ‘Yes’ will allow implementation prior to the normal implementation timeline, on October 10, 2005. A vote of ‘No’ will cause this CR to not deploy on October 10th and to follow the normal implementation timeline. Peggy stated that a unanimous vote is needed in order for the exception to be granted. Peggy then conducted the vote: Qwest voted ‘Yes’ via email AT&T voted ‘Yes’ via email Eschelon ‘Abstained’ from voting MCI voted ‘Yes’ Comcast voted ‘Yes' Peggy Esquibel Reed-Qwest asked Lynn Stecklein (Qwest) if there were additional emailed votes. Lynn Stecklein-Qwest stated that no other emailed votes were received. Peggy Stated that the exception was granted by a vote of 4 ‘Yes’ votes, 0 ‘No’ votes, and 1 ‘Abstain’ vote. Peggy stated that this CR would deploy on October 10, 2005. The call was concluded.

- July 11, 2005 Email Received from Eschelon: Hi Peggy, I am not able to attend the call tomorrow but Steph may attend. In a nutshell our vendor has concerns and there appear to be some known issues with the release (Steph could elaborate). It is my understanding that there are known bugs that cannot be fixed until the release next year anyway. Why would Qwest implement this early when the fixes are not scheduled until next year. In addition, since we are considering a non GUI type application here at Eschelon, we would want onfirmation that Qwest will make certain all fixes are in place to CLECs satisfaction before retiring the existing application. I probably have not explained this as well as Steph can but that is an overview. Eschelon abstained and did not vote NO because UOM is optional. Hope this helps. Bonnie J. Johnson Eschelon Telecom, Inc.

- July 11, 2005 Email Sent to Eschelon: Good Morning Bonnie, I received your email. The vote was rescheduled to take place tomorrow, July 12th. Please let me know what your concerns are and I will see if we can alleviate them. I have provided some information below in regard to this effort: - QORA would be updated to support UOM - The CLECs will not be required to move to UOM with the October deployment, but Qwest would like to make UOM available for those CLECs who do want to make the move at that time. - CLECs will not be impacted with this new interface, unless they choose to move to UOM in October. - QORA NDM and GUI will continue to be available in October. - The QORA GUI (Pre-Order) is already XML. - NDM would remain as is and that there are no changes at this time. - UOM (XML for ASR Ordering) is a 3rd interface that Qwest is introducing and is in addition to GUI and NDM.

I hope that this information is helpful. Please let me know if you have other concerns. Peggy Esquibel-Reed Qwest Wholesale CMP

- July 7, 2005 Email Received from Eschelon: Eschelon abstains but has many concerns. Bonnie J. Johnson Eschelon Telecom, Inc.

- July 7, 2005 Exception Vote Meeting Attendees: Peggy Esquibel Reed-Qwest, Cindy Kalakis-Qwest, Cassandra Hunt-Qwest, Terri Davis-Qwest, Lynn Stecklein-Qwest, Liz Balvin-Covad, Chad Warner-MCI Meeting Discussion: Peggy Esquibel Reed-Qwest stated that the meeting is for Qwest to conduct the exception vote for the QORA UOM ASR Ordering CR and the exception request is to allow implementation of this CR Prior to the normal implementation timeline. The CR is for QORA to be updated to support UOM and will provide XML capability for QORA ASR Ordering. Peggy then noted that the Quorum for today is 6 and has not yet been achieved. Peggy stated that she would briefly recap some information for those on the call, in case they wanted to submit their votes via email instead of calling back in to the rescheduled call. Peggy stated that: - QORA would be updated to support UOM. - The CLECs will not be required to move to UOM with the October deployment, but Qwest would like to make UOM available for those CLECs who do want to make the move at that time. - CLECs will not be impacted with this new interface, unless they choose to move to UOM in October. - QORA NDM and GUI will continue to be available in October. - The QORA GUI (Pre-Order) is already XML. - NDM would remain as is and that there are no changes at this time. - UOM (XML for ASR Ordering) is a 3rd interface that Qwest is introducing and is in addition to GUI and NDM. Peggy then asked if there were any questions. There were none. Peggy then explained what the yes and no votes would mean: A vote of ‘Yes’ will allow implementation prior to the normal implementation timeline, on October 10, 2005. A vote of ‘No’ will cause this CR to not deploy on October 10th and to follow the normal implementation timeline. Peggy stated that a unanimous vote would be required. Peggy then stated that the Quorum of 6 was not achieved on this call and stated that the vote would need to be rescheduled for next Tuesday, July 12th. Peggy then noted that if Covad and MCI wanted to call into the call on Tuesday that was fine, but that they could also submit an emailed vote. The call was concluded.

- June 21, 2005 Supplemental Information Sharing Meeting on UOM Interface (Non-CMP Meeting: SYST.06.14.05.F.03024.InfoSharingMtgsUOMASR) Facilitator: Terri Davis/Cassandra Hunt/Steve Edwards-Qwest Raindance Meeting Edition, via a meeting link that was provided on the June 14th Systems Notification

Attendees: Terri Davis-Qwest, Steve Edwards-Qwest, Cassandra Hunt-Qwest, Alan Bratetic-Qwest, Armando Garza-Time Warner, Bob Eggert-SBC, David Schlosser-Qwest, Dianne Friend-Time Warner, Kelly Morris-ELI, Bob Zula-Verizon, Christine Barth-TDS MetroCom, Prashanth-Wisor, Linda Isaacson-MCI, Basu Hombal-Wisor, Mary McDermott-Qwest, Raj Gill-Wisor, Chad Warner-MCI, Jay Whitney-MCI, Dan Wheeler-Qwest, Wayne Holmes-Qwest, Bob Weimer-Qwest, Cindy Kalakis-Qwest, Dannelle Haynes-Qwest, Peggy Esquibel Reed-Qwest, Steve Kast-Qwest, Richard Simon-AT&T, Stephanie Prull-Eschelon, Terri Davis-Qwest, Trixie Alabanza, Annelyn Aficial-CGI AMS, Susan Griffith-Qwest, Sharon Van Meter-AT&T, Bob Mazula-AT&T

Meeting Discussion: Steve Edwards-Qwest stated that this meeting is a follow-up call and noted that the meeting link, provided in the notice, contains a Power Point presentation that will be used during the call. Steve stated that the presentation is a high level conceptual design for the web based interface. Steve stated that on the first call, we talked about ideas and technical direction, based on the Industry TML Profile Document. On the first call Qwest wanted to see if other companies were moving in the same direction. Feedback was received from the last call and this follow-up call is for more detail and is a Q&A session. Steve asked if any one was implementing within the next 18-months and stated that AT&T has made the request and asked if AT&Ts technical staff was on the call. Richard Simon-AT&T stated that Rominan was planning to join the call. Bob Mazula-AT&T stated that he was on the call but that he was not technical. Wisor stated that they were interested in the UOM XML interface and noted that they did have technical staff participating on the call. Dan Wheeler-Qwest referred the call participants to the Power Point Presentation and stated that Slide 2 is for the scope and touches on 'handshaking', pull-model concept, and ASR validation web service. Slide 3 notes what is not in the scope: pre-order and ASOG rules. Slide 4 states that the TML Transport Diagram is taken from the industry TML Transport document. Slide 5 shows that there will be 3 web services that will be available for the customers. Slide 6 shows the ASR notifications from the customer to the provider. The arrows indicate messages. All calls are in SOAP. The ASR in TML format transmits to Qwest and an ok message is then sent back to the customer. The provider sends a request acknowledgement and an ok message back to Qwest. This ‘handshaking’ is so that Qwest and the customer know that they received it. The ok is for Qwest to begin processing the ASR. There could be 1 to many messages delivered to the customer, such as a syntax error. Qwest would notify the customer of the error via a result. The ASR the sends the error message to the customer as a result and it could be 1 of 4 items. Qwest will make an attempt to send to the customer and an ok message is then sent to Qwest. An ID# is associated to the ok. Qwest returns an ok message acknowledging the receipt of it. Slide 7 is a similar path and the bottom half of the slide shows that if Qwest sends the result to the customer and the customer didn’t receive the result, Qwest will send a list of the IDs not acknowledged, and the customer ok’s the receipt of the list. The customer looks at the list, calls Qwest, and gives the ID #’s to get the results. The customer then calls to acknowledge service. If a customer does not acknowledge a message sent, Qwest keeps sending the list and the list will grow. Slide 8 shows the SOAP Concepts and are from the TML Transport document and shows Envelope, Headers, Body, and Fault. There is a security header and Qwest hopes to do client certificates. The SOAP Body shows the example of ASR, OK, ID List, etc., and if something goes wrong, it could result in a SOAP Fault. Slide 9 is an example of an AML message. Slide 10 is an example of a TML Header Block. Slide 11 shows IDs (most important to Qwest), and the key is for all to understand how to populate IDs so can relate to one another. Slide 12 has Web Service Descriptions. Slide 13 lists Common Behaviors. Slide 14 is Request Listener and shows that Qwest does XSD Validation. If have XSD and the message is corrupted, Qwest will error the message. Slide 15 is an example of an OK Response. Slide 16 & 17 are for Request Listener (Client). Qwest does not process ASR if it errors. Slide 18 is a Request Listener Acknowledgement Message example. Slide 19 is Result Sender (client). Slide 20 is Results Ready Sender (client) and is Tier 2. Slide 21 is Results Ready Sender example.. Slide 22 is Result Retrievel Listener and states that a customer provides an ID, and retrieves one result from Qwest. The customer can do any number of times, as long as is within a reasonable amount of time. Slide 23 is an example of Result Retrieval Listener. Slide 24 is the Result Retrieval Listener Response. Slide 25 says that there are 3 types of child elements; there are other types of notification, but Qwest is only providing 3, at this time. Slide 26 is Result Ack Listener, and Slide 27 is the example. Slide 28 is ID Descriptions. There is a unique ID on every message, each direction. Slide 29 is the ID Flow Summary. The CorrelationID and TrackID are echoed in response for all web services. Slide 30 is a Summary of the ID Detailed Flow. When Qwest starts working with individual teams, Qwest can make it available to your technical staff. Slide 31 notes the Features under Consideration. Can implement using the an all-pull model. Slide 32 is Alternate All-Pull Model. Slide 33 are the Pro’s to Using All-Pull Protocol. Qwest is not implementing the All-Pull Model on the initial implementation due to lack of interest and the industry needs to define how it would look. Steve asked if this fits what other companies perceive to be what is needed for XML? Steve stated that Qwest wants to match what other companies are looking at. Steve Edwards-Qwest then asked for questions. Stephanie Prull-Eschelon stated that the vote is for this to be implemented in October, and asked why? Steve Edwards-Qwest stated that implementation in October fits well with the development lifecycle. This does not mean that all have to use it in October; Qwest just wants to get it out there. Steve stated that this will also allow for further testing together next year. Steve stated that we would work together thru any issues. Wisor stated that the OBF document has some transactions that cannot be done and asked if Qwest has their own schema. Steve Edwards-Qwest stated that ASOG 31 is adding some schemas and some are not yet addressed. Qwest has made some modifications so the defects could work with the schema. Qwest will work with companies that want to partner with Qwest. There are also schema changes with ASOG 32. The current defects will not impact customers. Qwest is re-introducing the defects in the ASR Committee to get them re-addressed and would like support. Jay Whitney-MCI stated that he does not understand the detail flow but stated that MCI was interested in XML. Dan Wheeler-Qwest stated that Qwest took the 6-23-03 document, which was mostly correct. 1 ID was not defined. Steve Edwards-Qwest stated that it would be re-published, with corrections. Wisor, AT&T, and MCI expressed interest in this move. Steve Edwards-Qwest asked if there were companies on the call that have concerns as Qwest moves forward and stated that Qwest will work closely and schedule lower level calls with companies who partner with Qwest. Steve then asked if calls should be with the interested companies only or if they should be global. Stephanie Prull-Eschelon stated that Qwest should offer the calls to all and state is a low level discussion. Steve Edwards-Qwest asked if the level of detail at this meeting met expectations. Wisor indicated that at a high level, the document was good. More may be needed later. Cassandra Hunt-Qwest stated that follow-up meetings would be scheduled for the lower level details and will work with the Service Management Teams. The call was concluded.

- June 20, 2005 Email Sent to AT&T: Sharon, The normal implementation timeline is 270 days. Qwest is asking for the exception to deploy on October 10th, in conjunction with the QORA 5.0 Release. I have provided some information below in regard to this effort: · QORA would be updated to support UOM. - The CLECs will not be required to move to UOM with the October deployment, but Qwest would like to make UOM available for those CLECs who do want to make the move at that time. · CLECs will not be impacted with this new interface, unless they choose to move to UOM in October. · QORA NDM and GUI will continue to be available in October. · The QORA GUI (Pre-Order) is already XML. · NDM would remain as is and that there are no changes at this time. · UOM (XML for ASR Ordering) is a 3rd interface that Qwest is introducing and is in addition to GUI and NDM. I hope that this information is helpful and answers your questions. Please let me know if you need more. Thanks much, Peggy Esquibel-Reed Qwest CMP

-- June 17, 2005 Email Received from AT&T: Peggy, If this is not implemented on October 10 - when would it be implemented? This vote is for the early deployment of UOM - not the fact that Qwest will support both platforms - right? Thanks. Sharon

- June 15, 2005 Systems CMP Meeting Discussion: Jill Martain-Qwest stated that this CR is not an Industry Guideline CR. Cindy Kalakis-Qwest stated that it is for QORA and that it is for a new UOM interface for ASR ordering. Cindy stated that Qwest is seeking an exception to the timeline and would like to implement this change on October 10, 2005. Cindy stated that QORA would be updated to support UOM. Cindy then stated that the CLECs would not be required to move to UOM with the October deployment, but Qwest would like to make UOM available for those CLECs who do want to make the move. Cindy stated that QORA NDM and GUI would still be available in October. Cindy stated that the exception vote meeting will be an ad hoc meeting and would occur prior to the July CMP Meeting. Cindy stated that a yes vote would allow this Change Request to be implemented on October 10, 25005 and a vote of no would cause this change request to not be deployed on October 10, 2005. Cindy stated that a supplemental meeting is scheduled for June 21 and is for technical experts, IT to IT. Cindy strongly recommended that the CLECs technical staff attend the meeting. Cindy stated that the call is via the link in the CR. Cindy stated that there is also additional information sharing meetings noted in the CR. The vote requires a unanimous decision. Bob Yeager-SBC stated that SBC currently uses the GUI and asked if the GUI would also have changes. Cindy Kalakis-Qwest stated that there are no changes to QORA GUI as it is already XML. Kim Isaacs-Eschelon asked if NDM would then be UOM. Cindy Kalakis-Qwest stated that NDM would remain as is and that there are no changes at this time. Cindy stated that Qwest is introducing a 3rd interface, which will be XML (UOM), and is in addition to GUI and NDM. Cindy asked if there were other questions. There were none. This CR moves to Presented status.

June 20, 2005 Clarification Meeting: Attendees: Cindy Kalakis-Qwest, Cassandra Hunt-Qwest, Peggy Esquibel Reed-Qwest Review CR Description: Peggy Esquibel Reed-Qwest read the CRs description and expected deliverable and asked if there was additional information to share. There was no additional information.

Confirm Impacted Area: Peggy Esquibel Reed-Qwest confirmed that the impact would be to Ordering and Provisioning

Confirm Impacted Interface: Peggy Esquibel Reed-Qwest confirmed that this request was to provide a 3rd interface for ASR Ordering. With implementation ASR Ordering could be done via QORA GUI, NDM, and/or UOM/XML

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

Action Plan: Peggy Esquibel Reed-Qwest stated that as requested, this CR was presented to the CLEC Community as a walk-on CR at the June 15, 2005 CMP Meeting. The Exception Vote will be conducted on July 7, 2005.

CenturyLink Response