Wholesale: Products & Services

Archived System CR SCR121305-01 Detail

Status History

Project Meetings

Hi, At this time Eschelon is ok to close SCR121305-01. Eschelon is in production with the 20.0 release. If you have any questions please let me know. Thanks Steph Stephanie Prull EDI Business Analyst Eschelon Telecom, INC Voice - 612-436-6058 Fax - 612-436-6158 Email - saprull@eschelon.com Web - www.eschelon.com

-- 4/18/07 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR has been in CLEC Test for some time and said that 2 CLECs have signed up for pre-order. He said that the 1st customer converted 4/9/07 and the second customer will convert sometime this week. He asked if there were any objections in closing this CR. Steph Prull-Eschelon stated that she would like to follow-up with Qwest off-line. She said that they are going through connectivity testing this week and will follow-up after that is complete.

Mark Coyne-Qwest said that would be fine and that this CR will remain in CLEC Test.

- 3/21/07 Systems CMP Meeting

Mark Coyne-Qwest stated that no one has converted yet to XML and that this CR will remain in CLEC Test.

-- 2/21/07 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR would remain in CLEC Test until the 1st CLEC goes into production. Bonnie Johnson-Eschelon stated they are getting close. Mark Coyne-Qwest stated that maybe we can close this action item next month.

1/17/07 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR and action item will remain open until the 1st CLEC goes into production

-

12/14/06 Systems CMP Meeting

Mark Coyne-Qwest stated that the in the November CMP Meeting, the CLECs said that they wanted additional time to review this change before agreeing to close. Steph Prull-Eschelon stated that she would like this CR to remain in CLEC Test until the 1st CLEC goes into production. Mark Coyne-Qwest stated that this CR would remain open until then.

-

11/20/06 E-mail from Eschelon Hi, I'm ok to close all 20.0 CRs except SCR121305-01 Implement XML Interface for IMA EDI. I would like for this to remain in CLEC test until we have some users actually in production on this. At this time there is no one in production yet. So we can not really say how its going or say we have given it a fair test.

Thanks

Steph

Stephanie Prull EDI Business Analyst Eschelon Telecom, INC Voice - 612-436-6058 Fax - 612-436-6158 Email - saprull@eschelon.com Web - www.eschelon.com

11/15/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and asked if this CR could be closed. Bonnie Johnson-Eschelon stated that she would like to check with Steph Prull (Eschelon) before closing this CR. She said that she would send an e-mail to the CMP CR mailbox if the CR could be closed.

10/18/06 Systems CMP Meeting

Susan Lorence-Qwest stated that this CR deployed on October 16, 2006 with the IMA 20.0 release and will remain in CLEC Test

9/20/06 Systems CMP Meeting

Carol McKenzie-Qwest stated that XML deployed in SATE on 9/16/06. She said that she also wanted to mention that she has been posting any changes since the final disclosure to the disclosure website and will continue to do so. Steph Prull-Eschelon said that they appreciate this effort.

Mark Coyne-Qwest stated that this CR will deploy in the IMA 20.0 release on 10/16/06.

8/16/06 Systems CMP Meeting

Carol McKenzie-Qwest stated that the EDI retirement CR will be presented in the September Systems CMP Meeting, with a proposed retirement date of October 27, 2007. Susan Lorence-Qwest stated that with the significant volume of PCAT updates associated with EDI to XML, Qwest is proposing a simple way to identify the changes that are simply a conversion of EDI to XML. Susan referred everyone to the three page attachment in the distribution package. The first page provides the overview of the proposal, the second page provides the example of the document specific to the EDI to XML change, and the third page is the example of the normal attachment that details the IMA LSOG/PCAT Updates. Susan said the proposal is to provide the normal Level 2 customer notice and the LSOG/PCAT Update attachment but to also provide a separate document that identifies the PCATs with ONLY the simple acronym change for XML. We believe this approach to the documentation updates for IMA Release 20 will allow the customer community a clear view of the numerous types of changes required. She said that the customer notice will be issued in the normal fashion for those documents that include a real content change other that the EDI XML conversion. Susan said that for those changes that are specific to the simple acronym change from EDI to XML, for clarity and simplicity, Qwest has created the summary document that itemizes the specific documents by name, the version number, the type of document, i.e. Business Procedure or PCAT, the Section requiring the acronym update, and the production URL for the document. Kim Isaacs-Eschelon asked if the URLs listed on page 2 would be linked to a redline document showing the changes or just where the document is on the web site. Susan Lorence-Qwest stated that the link will just show where the documents are on the website but the idea was NOT to provide all of the redline documents. She said that there are approximately 67 documents and thought this proposal would benefit everyone. She said that if the PCAT has a content change other than just a change from EDI to XML, it would be included in the normal attachment to the Level 2 customer notice. She said that the examples on page 2 list XML specific updates only and page 3 would be content changes. Kim Isaacs-Eschelon asked if it would be easier to send separate notices if the change was only for the acronym. Susan Lorence-Qwest stated that what Qwest is proposing is similar; it is just not a separate notice. Susan noted that it would be a separate document which would specify those changes. Susan stated that content changes would also be communicated. Susan then asked if Kim (Isaacs-Eschelon) was asking for them to be separated. Kim Isaacs-Eschelon said that either would be fine, and asked if the content changes would be red-lined. Susan Lorence-Qwest said yes and stated that they would be on the list and indicate that it was a content update, which is business as usual. Kim Isaacs-Qwest stated that in the past, Qwest missed following through in certain areas and asked why Qwest wouldn’t want another pair of eyes to review the documents. She asked if they should just report to Qwest if they find a reference to XML that Qwest missed. Susan Lorence-Qwest said that it would be great that when the CLECs review the documents, they could let Qwest know of any misses. Susan then noted that Qwest does have a number of eyes looking at the documents and that if misses are found they could be changed with a level 1 notice and pointed back to this, then there would be no risk of stopping a Product or Process. Susan asked if that would work. Kim Isaacs-Eschelon said yes. Susan Lorence-Qwest stated that if a miss was found, it would be great to send it in as a comment. Kim Isaacs-Eschelon said okay. Susan Lorence-Qwest asked if all were okay with this approach. There were no objections to the proposal. Susan Lorence-Qwest stated that the Level 2 notice would be sent out in September. Steph Prull-Eschelon asked if it made sense to change EDI to App-to-App, instead of EDI to XML. Cim Chambers-Qwest stated that EDI to XML and EDI to App-to-APP were discussed. Cim stated that App-to-App was considered but since the PCATs and other documentation are Release specific, it was determined that the change should be from EDI to XML. There were no additional questions or comments. Mark Coyne-Qwest stated that Qwest would move forward with the proposal.

7/19/06 Systems CMP Meeting

Mark Coyne-Qwest stated that there is no new status or updates on this action item. He said that this action item will remain open.

6/21/06 Systems CMP Meeting

Mark Coyne-Qwest stated that this action item has been open for several months and that there is no additional update. He said that a notice went out on June 16, 2006 and is open for comments. Mark proposed that this action item be closed.

Kim Isaacs-Eschelon stated that she would like the action item to remain open in case something comes up.

Mark Coyne-Qwest stated that we would leave the action item open.

5/17/06 Systems CMP Meeting

Jill Martain - Qwest reviewed the proposed XML and EDI retirement timelines. Jill stated that 18.0 would sunset on 10/10/06, 19.0 would be extended from the original 4/14/07 sunset date and EDI would officially retire in October 2007, 20.0 would deploy on 10/16/06, 20.0 would sunset on 11/07, and 21.0 would deploy 5/07. (Additional detail can be found in the May Systems Distribution Package in Attachment I) Dianne Friend - Time Warner stated that the 19.0 extension works better for them. Jill Martain - Qwest said that the OSS Calendar will be updated

Cim Chambers - Qwest reviewed the following disclosure changes with XML

Chapter #1: - Change name to Main Introduction & Base Schemas - Move the Generic Order Flow Business Models to the Order Chapter - Keep Developer Worksheets Usage Definitions - Remove TPAI information - Keep Thoroughfare Values - Include all the Base Schemas (IMA Base, Preorder Base, Order Base & Post-Order Base) and WSDL location/access information All Preorder Product Chapters: - Alphabetize the list - Keep Business Description and Business Model, however, replace pre-order flow diagrams with XML-specific diagrams - Remove EDI (X12) Mapping Examples - Remove Data Dictionaries - Include the preorder transaction-specific XML schemas Order Product Chapters: - Remove individual Order Chapters by product (entire chapter). Instead, include only one chapter for Order (no longer by product) - Move the Generic Order Flow Business Models from Chapter 1 and replace the flow diagrams with XML-specific diagrams -Move the FBDL Order Flow Business Model from the FBDL chapter and replace the flow diagrams with XML-specific diagrams - Include a table that summarizes Order forms required by product (general table with allowed forms for a given product – it will not be specific to ACT or LNA) - Include the XML Work Order schema Post-Order Chapters: - Alphabetize the list - Remove EDI (X12) Mapping Examples - Remove Data Dictionaries - Keep Business Description and Business Model, however, replace the flow diagrams with XML-specific diagrams - Include the Post-Order transaction-specific XML schemas

5/10/06 Adhoc Meeting

The following Companies participated in this meeting:

Accenture, AT&T, CGI, Comcast, Eschelon, Mcleod, New Access, Synchronous, Time Warner, Verizon Business, 702 Comm, Wisor, Qwest

Lynn Stecklein - Qwest stated that the purpose of this meeting was to provide a sample schema and examples of how Qwest uses the fields. She referred everyone to the Wholsale Resource Website for the documents that would be discussed.

Jan Martin - Qwest reviewed the following documents that can be found at:

http://www.qwest.com/wholesale/calendar/eventDetails/1,1456,49,00.html.

Av.req.txt Av resp.txt Address Validation schema

Lynn Stecklein - Qwest stated that iany additional questions could be sent to the CMPCR mailbox.

4/19/06 Systems CMP Meeting

Jill Martain-Qwest stated that another meeting would be scheduled to take place the first part of May and that Qwest would go over a sample of a schema and how Qwest was going to use fields. Jill then stated that Eschelon had volunteered to be the Beta Tester. Jill then stated that Qwest would also be changing the CMP Document due to the many references to EDI. Jill stated that Qwest would issue a CR for those changes. Jill stated that this effort is still on track for October deployment.

March 28, 2006

Adhoc Meeting

Agenda

- How will Qwest identify Qwest specific fields in schema - Response time for responses - Q&A log for questions around XML - Discuss in more detail flash cuts - Discussion around in flight LSRs - Next steps

Item #1 How will Qwest identify specific fields in the Schema

Connie Winston - Qwest stated that we did research taking the UOM approach and when we tried to map there was a lot of overhead and suggested that we continue to use the disclosure worksheet

Carl Larson - Wisor asked if Qwest could provide more detail on what are the issues are.

Connie Winston - Qwest said we could take this item offline and schedule a meeting with Carl and the technicians.

Carl Larson- Wisor agreed.

Steph Prull - Eschelon said that the ASOG representative can’t address LSOG issues.

Lee Gomez - Qwest said that she attends for the LSOG community but that she does not attend the UOM meetings.

Chris Terrell - AT&T asked who the person was talking about the UOM group

Carl Larson - Wisor stated that he was from Wisor and that he was the Co-Chair of the UOM group. He said that additional information can be found on the ATTIS website.

Chris Terrell- AT&T asked if others could be invited to the offline meeting.

Connie Winston - Qwest said that the meeting would be open to all.

#2 Response time for Responses

Connie Winston - Qwest stated we did an assessment on setting the time out level. Connie said that it would be 30 seconds for all pre-order and for CSR would be 45 seconds and that for large CSRs may not work. Connie said that every Company does different types of business and that at implementation we would monitor the system to determine if changes would be necessary.

#3 Q & A Log for Questions around XML

Connie Winston - Qwest stated that we want the ability to share questions/answers that we have received on the XML migration. She said that we would like to use the existing EDI log to track the Q& A’s and any open issues. Connie said that questions can still be sent to CMPCR@qwest.com.

#4 In Flight ASRs

Connie Winston - Qwest said that we would like to flash cut with that with EDI to XML conversion just like in the ASR world. Connie said that IMA is very mature and on a stable platform and the releases are getting smaller.

Steph Prull - Eschelon asked if when they move to XML is it Qwest’s desire to have everyone move to 20.0.

Connie Winston - Qwest said that Qwest would like everyone to move to 20.0 and that 21.0 would be a flash cut. Connie asked if everyone could be ready.

Steph Prull - Eschelon said that the way 20.0 is handled would determine how they move forward.

Connie Winston - Qwest said that we can be flexible with 21.0 and the date.

Chris Terrell - AT&T said that they have a concern with the flash cut

Comcast said that they would prefer not to flash cut.

Steph Prull - Eschelon said that Eschelon does not have an opinion one way or another.

Connie Winston - Qwest stated that with XML a flash cut is different with XML than EDI and the release versioning is also different.

Connie Winston - Qwest stated that we will continue to have discussions to determine if there are more creative ways for this to be handled.

#5 Next Steps

Connie Winston - Qwest stated that we will be getting together in the summer to share technical details that will be in draft form. Connie said that we will be updating the EDI mail log and that UOM LSOG will be an agenda item at the beginning of the summer.

Steph Prull - Eschelon asked if there was a timeframe for the 1st set of draft specs to be shared. She said that sooner they are shared the better.

Sai Kalaga - Qwest stated that they are a work in progress and that we should be able to share by mid June.

3/15/06 Systems CMP Meeting

Jill Martain - Qwest stated that an adhoc meeting to provide status on the XML conversion will be scheduled on March 28th, 2006. Jill said that we are working to resolve questions that have been submitted and that we will respond to those questions in the meeting on March 28th.

February 23, 2006

XML Adhoc Meeting

Lynn Stecklein - Qwest conducted roll call. She referred everyone to the document on the Wholesale Website that would be reviewed by Connie Winston and her team located at: http://www.qwest.com/wholesale/cmp/index.html. She stated that the purpose of this meeting is to continue discussions on the EDI to XML migration.

Connie Winston- Qwest referred everyone to the Agenda in the Document. She said that the following items would be reviewed:

XML Gateway Review (Slide 2) - LSR Ordering - Overview - Compare EDI vs. XML/Web Service - LSR Pre-Order - Overview - Compare EDI vs. XML/Web Service - LSR Post-Order - Notice Pull Overview - Notice Push Overview - High Level Timeline

Connie Winston - Qwest reviewed the following: (Slide 3)

For IMA 20.0 release, Qwest will implement XML based web services for LSR Pre- Order, Ordering, and Post-Order functionality (there will not be a 20.0 EDI version). - The Web Services effort referred to as IMA XML Gateway - exposes services Implemented using SOAP over HTTP and are completely described using WSDL. - Authentication to these Web Services will be through Qwest-provided digital certificates. - IMA XML Gateway serves as a front end to the already existing IMA Business Process components and serves as an eventual replacement for EDI. - IMA XML Gateway schemas will be based on the LSOG-9 schemas as appropriate and will include Qwest specific fields. Connie Winston - Qwest said that with the current mapping we are not finding significant differences. - IMA XML Gateway schemas will closely match the existing IMA Developer Worksheets. Carl Larson - Wisor asked how Qwest will identify Qwest specific fields in schema. Cim Chambers - Qwest said that they would be numbered (i.e. AVQA). She said that it maps the same and is what we are using to drive the naming conventions. Carl Larson - Wisor said that there were concerns around UOM OBF guidelines. He said that in schema the OBF practices, Qwest identified in name to standard. Cim Chambers - Qwest asked if they were asking for Qwest to be called out in tag. Carl Larson - Wisor said that they were looking to have Qwest in it. Connie Winston - Qwest said that we will look in to it. - Every request submitted by a CLEC goes through (a) authentication, (b) schema validation, (c) request authorization, and (d) request content validation. - Qwest’s business rules for local service ordering are not changed due to the implementation of XML Gateway. - The size of LSR requests via XML is expected to be less than twice that of comparable EDI requests. Connie said that she does not expect response time to be impacted. - Example XML requests/responses and draft XSDs will be available for review prior to the release. Connie Winston - Qwest said sometime at the beginning of the summer. - CLECs will be required to test 20.0 IMA/XML interface with the CLEC Electronic Access Implementation Team as a new implementation project and as a migration project when moving to newer releases. CLEC - asked if interactive agent will be used. Connie Winston - Qwest said no.

Connie Winston - Qwest reviewed the following: (Slide 5)

LSR submission will be asynchronous. CLEC - asked how this could be asynchronous. Connie Winston - Qwest said that Qwest will notify when processed. - Each request to LSR Ordering service will contain only one LSR, as today in EDI. - The requesting CLEC will receive an ACK containing a tracking id from Qwest for an LSR complying with LSR Ordering schema (schema validation only). - The CLEC will receive Error Response from Qwest if the LSR fails schema validation. - If CLEC fails to receive the Qwest ACK, they may resend the LSR to receive the ACK with tracking id (or the schema validation error response.) - If the LSR is successfully accepted by Qwest for order processing, an LR (FOC notice) will be generated by IMA. - If the LSR fails IMA edits, an LR (reject notice with error messages) will be generated by IMA. - Details about receiving LR and other notices are discussed in Post-Order section - Qwest will tune XML Gateway to accept quantities and sizes of LSRs per current EDI volumes and usage patterns. - A CLEC application may be multi-threaded to send multiple individual LSRs, pre-order requests, or notice requests to Qwest simultaneously. - Each LSR REQTYP utilizes the same LSR Ordering web service and XML Schema. The following diagrams walk through LSR Ordering scenarios while providing a comparison with existing EDI strategy.

Sai Kalaga - Qwest presented slide 6 - The IMA Gateway Comparison (Order) current EDI view. There were no questions.

Sai Kalaga - Qwest presented slide 7 - The IMA XML Gateway Comparison (Order) Mcleod asked if they pushed and their service was down would Qwest queue. Connie Winston - Qwest stated that our intent was to push once and that we will retain if the service is down. Connie Winston - Qwest asked if there is still interest on a push if there was more work on the CLEC side. CLEC - stated that they would need to evaluate further. He asked if Qwest would provide both methods and the user will be profiled accordingly. Connie Winston - Qwest said that we don’t want to create both if there is no interest. Connie asked that the CLECs send questions and concerns to the cmpcr@qwest.com mailbox. She also said that a technical meeting would be scheduled in June or July to review LSOG 9 mapping to WSDL.

Sai Kalaga - Qwest presented slide 8 - The IMA XML Gateway Comparison (Order) CLEC - asked if the ACK is expected when the FOC is sent.

Sai Kalaga - Qwest said that we prefer the ACK on the same connection. He said that if there is no ACK, Qwest believes that it has not been received by the CLEC.

Sai Kalaga - Qwest presented Slide 10 - IMA XML Gateway - LSR Pre-Order

All LSR Pre-Order transactions will be synchronous. - CLEC must block and wait for a Pre-Order response from IMA. - CLEC sends each pre-order request separately and Qwest responds with the corresponding pre-order transaction response. - Average response times for each Pre-Order transaction comply with existing benchmarks published by Qwest. - The average response time should be used as a guideline for how long to block and wait for a Pre-Order response. - The CLEC should set their timeout above the average for each transaction type. It is expected that some transactions take longer than the average. - Potential network traffic (internet and intranet) congestion, and occasional larger or slower transactions, and overhead in the CLEC application must be considered for setting a timeout. - If CLEC fails to receive a pre-order response, the request may be resent.

Sai Kalaga - Qwest presented Slide 1 - The IMA XML Gateway Comparison (PreOrder) current view and there were no questions.

Sai Kalaga - Qwest presented Slide 12 - The IMA XML Gateway Comparison (PreOrder) WS: CLEC Retrieving a CSR. He said that there is no ACK in this transaction.

Linda Birchen - Comcast asked how long they will have to wait before they can request the same CSR. Sai Kalaga - Qwest said that it should just be seconds. Sai said that they can request the transaction again. Connie Winston - Qwest said that we are not expecting this to happen a lot. Linda Birchen - Comcast asked if they can request a CSR out of the time limit. Sai Kalaga - Qwest said yes they can request again if the system is down. Linda Birchen - Comcast asked if pre order has the same parameters. Sai Kalaga - Qwest said that the LSR path takes longer and the pre order requires no ACK. Linda Birchen - Comcast asked why they would not expect an ACK on both. Sai Kalaga - Qwest stated that if an ACK is required, it puts a burden on the CLEC because the ACK needs to be accepted. CLEC - said that synchronous would be faster. Sai Kalaga - Qwest agreed and said that we need solutions that work best for all. Steph Prull - Eschelon asked if Qwest knew what the average time for pre order transactions.

Connie Winston - Qwest presented Slide 14 - The IMA XML Gateway – LSR Post-Order IMA XML Gateway will implement strategies to PUSH and PULL all IMA notices. - Notices will be available to the CLEC via XML Gateway as IMA generates them, based on applicable business processing. Pushing a notice - Qwest will send the notice to the CLEC when the notice is generated. - Pulling a notice - Each CLEC has ability to request for all of their unsent notices. Multiple notices may be sent in response to a single pull.

Connie Winston - Qwest stated that we may need to set boundaries for how many sent in a period of time. - The CLEC must acknowledge the receipt of each notice by sending an ACK back to Qwest. - Any notice not acknowledged by the CLEC will be considered unsent. Connie Winston - Qwest said that Qwest will not resend but CLECs can pull them - Notice acknowledgement acts as a confirmation to ensure that both Qwest and the CLEC know that each has the same delivery status awareness for each notice.

Connie Winston - Qwest presented Slide 15 - IMA XML Gateway - Notice Pull

Notice Pull Strategy CLEC implements a Web Service client to periodically request all unsent notices from Qwest. Qwest responds with unsent and unacknowledged notices, and CLEC acknowledges back to Qwest each notice received via a separate web service call. - Pull is a simpler solution for the CLEC to implement compared to the Push strategy. - Implementing a Web Service client is relatively simple and requires less infrastructure for the CLEC. - CLEC simply needs to call the Qwest notice web service regularly to receive all notices for any LSR in a timely manner. - A suggested frequency of the pull request is approximately every 5 minutes. - The more frequently a CLEC pulls for notices, the lesser the count of unsent notices on a response. - In the event of a large number of unsent notices, Qwest will cap number of notices on any given pull response and set an indicator to show there are additional notices available. CLEC would acknowledge the notices, then pull again immediately. (Max quantity of notices per response to be determined by Qwest prior to release.) - The pull web service also allows the CLEC the ability to request another copy (a resend) of a specific notice type for a given LSR. (This will be a separate web service call, requiring LSR number or PON/Ver and notice type as query parameters.)

Connie Winston - Qwest presented Slide 16 IMA XML Gateway - Notice Push

Notice Push Strategy Qwest pushes notices by sending a request containing a notice that has become available to CLEC’s web service. CLEC responds by acknowledging the notice to Qwest. - More complexity for the CLEC: implementing a Web Service requires application server (like WLS) licensing costs, setting up firewall rules to enable notices from Qwest, and setting up strategy to guarantee the availability of the Web Service. - Each CLEC wishing to RECEIVE notices must: - Implement Notice Receiver Web Service as per Qwest specifications - Accept Qwest digital certificate for authenticating Qwest transactions - Successfully demonstrate the Notice Receiver Web Service by testing in IMA SATE environment - Guarantee the up-time of the Notice Receiver Web Service - Qwest will attempt to push each notice at most once. - When errors are encountered while pushing notices to CLEC’s Notice Receiver Web Service, Qwest will not retry sending the notice. (However, any unsent/unacknowledged notice will be available to the CLEC via Qwest’s notice pull web service.) - It is Qwest’s recommendation that each CLEC is required to periodically pull for unsent notices to account for any failures in their Notice Receiver Web Service. Connie Winston - Qwest presented the Timeline- Slide 19. She said that if we need another technical meeting it should be held in the June/July timeframe. She said that we can review LSOG 9 mapping to WSDL.

CLEC asked if Qwest would be retiring EDI 19.0.

Connie Winston- Qwest said that we are and said that the CLECs could issue a CMP CR to extend the retirement date.

Jeff Sonnier- Sprint asked if a CLEC could convert anytime after the October conversion.

Connie Winston - Qwest said yes and that Qwest would entertain conversions towards the end of October. She said that we don’t want to convert on the actual conversion date.

Kelly Leverich - ELI asked if another call could be held at the end of March.

Connie Winston - Qwest said that would work.

Leo Demitriadus - AT&T asked that the action items identified today and the items the CLECs needed to ponder could be included in the agenda.

Connie Winston - Qwest said that a meeting will be scheduled at the end of March.

Dianne Friend - Time Warner asked how many releases per year will there be with XML

Connie Winston - Qwest stated that we announce the capacity every December in the CMP Meeting.

Dianne Friend - Time Warner said that they are trying to figure their budget.

Loretta Huff - Qwest stated that she did not see us going to more than 2 per year.

The CLECs said that this meeting was very informative and very well prepared.

The following actions items were captured in this meeting:

How will Qwest identify Qwest specific field in schema Issue on ACK on Pre-Order Response time for responses Push/Pull Discussion Possibility of building a Q&A website for questions around XML Discuss in more detail flash cuts Conversation around conversion from EDI to XML and that Qwest will respond to all pending EDI orders via XML and the CLECs would need to convert their side as well from EDI to XML.

1/25/06 Adhoc Meeting

Attendees: Qwest Participants - Connie Winston, Jill Martain, Loretta Huff, Peggy Esquibel-Reed, Lynn Stecklein, Lydell Peterson, Sai Kalaga, Cim Chambers, Deb Roth, Danelle Haynes, Dave Schlosser, Jan Martin, Steve Kast, Carol Mckenzie John Blascyk - AT&T, Sharon Van Meter - AT&T, Chris Terrell - AT&T, Donna Steele - AT&T, Maria Aquino - AT&T, Andy - AT&T, Frank - AT&T, Jeff - AT&T, Leo Dimitriadis - AT&T, Peggy Rehm - Neustart, Chad Warner - Verizon Business, Rosalin Davis - Verizon Business, Chad Whitney - Verizon Business, Graham - Verizon Business, Brian Miller - CGI, Annelynn - CGI, Linda Birchem - Comcast, Nancy Thompson - Wizor, Nancy Sanders - Comcast, Jeff Sonnier - Sprint, Sue Clark - XO Communications, Sue Wright - XO Communications, Joyce Billow - Mcleod, Dave Lee - McLeod, James - Mcleod, Steph Prull - Eschelon, Kim Isaacs - Eschelon, Laurie Fredrickson - Integra, Karen Johnson - Integra, John - Integra, Dianne Friend - Time Warner, Ian Coleman - XO Communications, John - Synchronous, Dan Synchronous, Jason - Accenture, Janna DuHammel - ELI, T Whitney - Verizon Business

Lynn Stecklein - Qwest stated that the purpose of this call is to discuss the new XML interface that is replacing the current EDI interface. She said that this CR was presented in the December CMP Meeting. She said that the CLECs requested that adhoc meetings be held to ask questions and to have their technical expertise participate in these meetings. Lynn said that we did receive questions from AT&T that will be discussed today.

Sharon Van Meter - AT&T said that we voted 6 months ago on who was interested in XML and AT&T said that they were not interested. Sharon asked why Qwest was still going forward when they said no several months ago.

Connie Winston - Qwest said that when this was discussed several months ago, AT&T and MCI were the only 2 CLECs who expressed no interest in XML. She said that there were several CLECs that were very interested in XML. Connie said that EDI is very expensive and some CLECs stayed out of EDI due to their costs. Connie said Qwest weighed the costs and benefits and decided that we needed to move to XML. She said that Qwest started conversations at least 1 ½ years in advance of the conversion and that the CMP request was issued 270 days in advance. Connie said that future support of EDI is too expensive and difficult.

Sharon Van Meter - AT&T stated that the CR was presented in December and that XML is targeted for October. She said that is not 1 ½ years in advance.

Connie Winston - Qwest said that EDI is not scheduled to retire until April 2007. She said that she did not expect that all CLECs would convert to XML in October. Connie said that she would like to see a staggered XML implementation and that we will work with all CLECs to convert.

Sharon Van Meter - Qwest asked if Qwest could delay XML until 2007. She said that AT&T has already budgeted for 2006 and XML is not included in their budget.

Connie Winston - Qwest said that we plan to deploy XML in 2006 and can look at extending EDI. She also said that some CLECs do want to convert to XML in 2006 and once again will look at a staggered timeline.

Chad Warner - Verizon stated that he was not sure how this will impact them after the merge with Verizon Business.

Connie Winston - Qwest stated that everyone has budgets and timelines and understands the efforts that will go into this project. She said that Qwest has some of the same concerns and that is why we are starting discussion early.

Sharon Van Meter - AT&T said thanks for the consideration and that they will build a business case and get back to Qwest.

Chad Warner - Verizon Business asked if Qwest was planning on using soap over XML

Connie Winston - Qwest said yes.

Connie Winston - Qwest addressed the question from AT&T on what type of security Qwest was planning to use for the interface. Connie said that a digital certificate will be required and will be different than the EDI digital certificate.

Connie Winston - Qwest answered the question from AT&T on what standards for the XML interface for Order will Qwest be following. Connie stated that we will be following the Industry Standards and LSOG 9 as closely as we can. She said that there are a few exceptions to LSOG versions and Qwest’s versions. Connie said that the mapping is going very well and that we will share information as soon as possible.

Steph Prull - Eschelon said that would be great.

John Moran - Verizon Business asked if schema would be based on the Industry Guidelines or would it be Qwest specific.

Connie Winston - Qwest said that LSOG 9 would be used as the base with some Qwest specific fields. Connie said that we have looked at field lengths due to back end Legacy systems. She said if the field lengths and business rules have to change they will be disclosed and will be communicated at CMP.

John Moran - Verizon Business asked if Qwest would be able to provide the WCL with schema early.

Connie Winston - Qwest said that there will be a draft prior to the final. She said that 45 days before the release we will know more.

Connie Winston - Qwest answered the question from AT&T asking if the RECTYP would be separate. She said that they would not be separate.

Connie Winston - Qwest answered the question from AT&T on whether the delivery is guaranteed over the XML interface. She said that we will need to change behavior to guarantee delivery. Connie stated that the CLECs will need to request notices and Qwest will push to the CLECs.

Sai Kalaga - Qwest stated that all services will be synchronous and that we will enhance the systems so that the CLECs can request if you did not receive. He said that with XML the CLEC will come to Qwest for the notices and once the notice is received the CLEC will acknowledge receipt the notices.

CLEC - asked if orders (LSRs) are going to be synchronous and how.

Sai Kalaga - Qwest said yes and that once the request is submitted, the CLEC will request response.

CLEC - said that it could take days to get the response back.

Sai Kalaga - Qwest stated that the CLEC will get the LSR ID back to say that Qwest received the request.

CLEC - asked if the CLEC had to request confirmations.

Sai Kalaga - Qwest said yes.

Leo Demitriadis - AT&T asked why they will have to pull for confirmation as opposed to a push. He asked if they sent 10 LSRs in a transaction, will all 10 be acknowledged.

Sai Kalaga - Qwest said all 10 would be acknowledged.

Mr Graham - Verizon Business asked if the acknowledgement will replace IA receipt or 997.

Sai Kalaga - Qwest said that it is beyond 997.

CLEC - asked how long it will take to generate the LSR ID.

Sai Kalaga - Qwest said that it will depend on the product. He said it could take several seconds or several minutes.

Sue Wright - XO Communications asked if there will be rejects returned synchronous or only acknowledgements.

Sai Kalaga - Qwest stated that you will get acknowledgements and rejects upfront.

CLEC - asked if you will get another reject beyond the business rule edits.

Sai Kalaga - Qwest said that it could be beyond edits.

CLEC - asked if they will get jeop’s.

Sai Kalaga - Qwest said yes.

CLEC - asked if they could request a specific type.

Sai Kalaga - Qwest said you can request a type or all you need.

AT&T stated that they prefer the push not the pull. They said that they don’t want to pull every hour for a FOC. They would prefer that Qwest send the notices.

Steph Prull - Eschelon stated that they prefer the push and said that the SGAT guidelines could be out of whack.

Connie Winston - Qwest stated that we will take this back as an action item.

Sai Kalaga - Qwest stated the CLECs need to be willing to comply with specifications.

Sue Wright - XO Communications stated that they prefer the push.

CLEC - asked if you have 1 order at a time will you get an acknowledgement with tracking ID.

Sai Kalaga - Qwest said that the LSR ID will be sent.

CLEC - asked what the response time will be for the LSR ID to be sent.

Sai Kalaga - Qwest said that for a simple order the response will be sent in less than a minute.

CLEC - asked how many orders can be handled per hour.

Sai Kalaga - Qwest stated that we did not have numbers yet. He said that the back end servers will be the same as current volumes.

Ian Coleman - XO Communications asked if they need to pull for a response for order on post FOC, jeops

Linda Birchem/Comcast asked if there will be a BETA test or something.

Connie Winston – Qwest stated that we would appreciate the CLECs participation on testing. She said that after we deploy 20.0, we will work with individual CLECs.

CLEC – stated that Qwest needs to understand what XML means internally to them as well. She said that they need open dialogue when documentation becomes available and would like to send Q&A’s via e-mail.

Connie Winston – Qwest stated that we welcome the CLECs questions and that they should be sent to the CMP CR mailbox. Connie said that we want to keep communication open and that we need to have more of these this type of meeting.

CLEC - asked if there would be a single LSR per transaction or multiple LSRs per transaction.

Sai Kalaga - Qwest said that there would be a single LSR per transaction.

CLEC - asked if there is a size limitation.

Sai Kalaga - Qwest said yes.

CLEC - said that EDI is very compact and XML transactions are going to twice as large.

Sai Kalaga - Qwest said that XML transactions will be larger (5-10 potentially).

Chad Warner - Verizon Business said that asynchronous connection is a concern.

CLEC - stated that they have over 200 provisioners nationwide. They are concerned with the response time and that they may not be able to do anything on the order for a minute.

Connie Winston - Qwest said that we will take an action item to determine if a customer can multi thread from 1 desktop.

Sue Wright - XO Communications asked if there can be multiple sessions open at the same time.

Sai Kalaga - Qwest said yes.

Sharon Van Meter - AT&T said that she hopes that the people working on doing this change will work with the CLECs.

Connie Winston - Qwest agreed.

Steph Prull - Eschelon asked if they will receive the LSR ID if it is rejected.

Sai Kalaga - Qwest said that the LSR ID will be given once the LSR has been accepted.

CLEC - asked if they have to pull for a reject just like the FOC

Sai Kalaga - Qwest said yes.

Graham - Verizon Business asked how the Supp process in the new environment will be handled and validated while edits are being applied. He asked how it will work if they send a Supp for PON and there is a mismatch on the version.

Sai Kalaga - Qwest said that there will be an upfront edit.

Comcast - said that it would helpful if Qwest could provide a document on the order flow.

Connie Winston - Qwest said that the flow is not changing and that with EDI all validation is the the BPL. Connie said that layer will enforce the same business rules with XML.

Linda Birchem - Comcast - said that they don’t understand flow and that they have a concern about constant monitoring for responses up to the due date.

Sai Kalaga - Qwest stated that we could provide a diagram that will highlite some of these processes.

Connie Winston - Qwest said that we can look to see if we can document some of these processes and have another call.

CLEC - asked how the interactive agent is different with XML.

Connie Winston - Qwest said that we will make a note to provide information on how he interactive agent is different with XML. Verizon Business asked if this applied to pre order.

Connie Winston - Qwest said yes.

CLEC - asked if this was asynchronous or synchronous.

Sai Kalaga - Qwest stated it was synchronous.

CLEC - - asked if it was multi- threaded.

Sai Kalaga - Qwest said yes.

CLEC - asked if there was a maximum on that (2, 6,50, 60 threads).

Sai Kalaga - Qwest stated that Qwest will continue to support volumes as they exist today.

Frank - AT&T said that by moving to XML, the CLECs have to re-architect their systems.

Connie Winston - Qwest that moving to XML has value overall.

Frank - AT&T said that the conversion to XML is an additional cost and said that all others are using NDM or Direct Connect.

CLEC - said that they now will need EDI and XML knowledge.

CLEC - asked if the costs outweigh the impact to Qwest and asked why Qwest did not go to CORBA.

Connie Winston - Qwest said is not the technical path that Qwest has chosen.

CLEC - said that Bell South supports both EDI and XML.

Connie Winston - asked if Bell South supported EDI and XML on the LSR.

CLEC - said yes.

Connie Winston - Qwest stated that Qwest has heard everyone’s concerns and have captured action items. She said that we will get back together in 4 to 6 weeks with a diagram to answer questions about pulling vs. pushing, what mapping will look like, what will stay the same and process changes.

Steph Prull - Eschelon asked if they could still send questions prior to next call.

Connie Winston - Qwest said that they should send additional questions to the CMP CR mailbox.

John Blasczyk - AT&T asked if Qwest could check with the Access side of UOM on the push issue. John said that two different approaches was a surprise.

Connie Winston - Qwest thanked everyone for pariticipated in the call.

1/18/06 January CMP Systems Meeting

Jill Martain - Qwest stated that an adhoc meeting is scheduled on January 23rd to discuss the XML interface and that this CR will move to a Development status. Sharon Van Meter - AT&T asked if technical people from Qwest would be in this meeting. Connie Winston - Qwest said yes.

12/14/05 December CMP Systems Meeting

Connie Winston/Qwest stated that Qwest would like to move forward with the IMA XML interface. Connie said that XML is more cost effective and that Qwest would like to implement in the 20.0 Release. Sharon Van Meter/AT&T stated that she needed to take this back internally and said that she thought that Qwest knew that AT&T was pretty adamant that they do not want to convert to XML Connie Winston/Qwest said that Qwest wanted to start conversations and that is why we walked this CR on in today’s meeting. Nancy Sanders/Comcast asked if this would be the only interface. Connie Winston/Qwest said yes. Rosalin Davis/MCI asked how long the CLECs would have to convert. Connie Winston/Qwest stated that generally it would be until the next release which would be April of 2007. She said that Qwest wanted to bring this forward as soon as possible and that we are required to provide notification 270 days in advance. Sharon Van Meter/AT&T clarified that they would have to deploy in October 2005 and that they would have until April 2007 when EDI would be retired. Connie Winston/Qwest agreed. Kathy Stichter/Eschelon asked if this impacted billing. Connie Winston/Qwest said no, that same bill output options would remain. She said that Qwest has heard from other companies and that some are highly interested in XML, some moderately interested and some may not be interested. Connie said that we wanted to provide adequate planning time for this conversion. Connie said that we would continue to discuss via the CMP Meetings as we move forward. Sharon Van Meter/AT&T asked if AT&T decided that they don’t want to convert to XML would there be a vote. Connie Winston/Qwest said no. She said that only be XML would be available in 20.0. She said that EDI will be retired in 21.0 if the CLEC is on 19.0. Dianne Friend/Time Warner asked if this applied to the LSR side only. Connie Winston/Qwest said yes, and that XML already exists with QORA. Dianne Friend/Time Warner asked if Qwest will still have NDM. Connie Winston/Qwest said yes. Unidentified CLEC asked what the plan is for Pre-Order. Connie Winston/Qwest stated that Pre-Order will use XML as well. Sharon Van Meter/AT&T asked if Qwest would schedule an adhoc meeting so that she can invite her technical people. Connie Winston/Qwest stated that adhoc meetings are part of the plan and that the 1st meeting would be held in the 1st quarter. Sharon Van Meter/AT&T said that there is a sense of urgency for these meetings because AT&T does not want to convert to XML. Sharon asked that Qwest schedule a meeting with AT&T the 2nd or 3rd week of January to start discussions. She said that this meeting would provide additional detail and would be a good use of time Chris Terrell/AT&T agreed and asked if this call would be for AT&T only. Connie Winston/Qwest said we could have a meeting with AT&T 1st due to their situation and then have a technical meeting with all CLECs. Rosalin Davis/MCI stated that MCI does not want to convert to XML either and that they would also like a meeting. Nancy Sanders/Comcast requested that they be included in the meeting. Sue Wright/XO Communications said that they would like to participate in the meeting. Connie Winston/Qwest stated that we will schedule an adhoc meeting with all CLECs. Sharon Van Meter/AT&T requested that the technical people attend the meeting. Chris Terrell/AT&T asked if there would be an associated LSOG change. Connie Winston/Qwest stated that we are currently on LSOG 5 & 6. She said that we will follow OBF standards but will not deploy LSOG 9. Lynn Kellas/ELI asked what was pushing Qwest to move to XML Connie Winston/Qwest said cost. Lynn Kellas/ELI stated that this appears as a slam dunk. She said that Qwest forced them to do EDI and now Qwest is requiring this move to XML. Connie Winston/Qwest stated that EDI is very expensive. Lynn Kellas/ELI stated that they should be able to use middleware and not have to incur more cost. Connie Winston/Qwest stated that this is not a slam dunk and that we are starting discussions 1 ½ years early. Lynn Kellas/ELI asked if Qwest will reimburse costs. Connie Winston/Qwest said no and that we will schedule an adhoc meeting. Lynn Kellas/ELI stated that she would like to participate in this meeting. Bonnie Johnson/Eschelon stated that there has been a lot of discussion about XML in CMP. She said that for those CLECs attending CMP this should not be a complete surprise. Lynn Kellas/ELI stated that ELI has been attending CMP. Connie Winston/Qwest said that we will begin having meetings and that the business rules will be similar to what we disclose now. Connie said that a schedule will be set up and shared with everyone. Dianne Friend/Time Warner said that the 19.0 sunset date is April 14, 2007 and asked if they could ask for an extension. Connie Winston/Qwest stated that we would certainly consider the extension and that we will do what we can to support the move. Dianne Friend/Time Warner said that they are dependent on their software vendor and it is not done in house. Dianne said that she understands that XML is the way the Industry is headed but that Qwest is the only ILEC that requires an interactive agent be used. She said that from ELIs perspective the concern is the costs that have been incurred to do business with Qwest. Connie Winston/Qwest stated that EDI has very high costs. Lynn Kellas/ELI stated that she is ok with XML but has heartache with EDI going away. Unidentified CLEC asked when Qwest would provide more detail on XML. Connie Winston/Qwest said we will have more detail in the January meeting. Jill Martain/Qwest stated that timelines to introduce a new interface can be found in the Change Management Document. Jill said that we will follow those timelines and provide as much advance notice as we can. Dianne Friend/Time Warner asked that when the meeting notice is sent that it is distributed to everyone that has a need to know. She said that Time Warner is usually not aware of these meetings. Jill Martain/Qwest said that we notify via mail outs and that the purpose of the meeting will be clearly noted in the meeting notice title. Bonnie Johnson/Eschelon asked if Qwest could change their Interactive Agent requirement. Connie Winston/Qwest said that Interactive Agent won’t be necessary for XML. Cim Chambers/Qwest stated that since this will be a Web Service, it will have a different transmission protocol. Connie Winston/Qwest said that XML removes a lot of middleware. Steph Prull/Eschelon said that the just joined the call and asked when Qwest will convert to XML. Connie Winston/Qwest said with 20.0 which is scheduled in October of 2006. Jill Martain/Qwest said that Qwest will schedule a meeting in January for further discussion. Bonnie Johnson/Eschelon asked if these discussions could be in conjunction with CMP. Jill Martain/Qwest said that a separate meeting would be better but that we could schedule the January meeting around the same timeframes of the January CMP. Chris Terrell/AT&T asked if they should submit questions prior to the January meeting. Connie Winston/Qwest said that would be great. Jill Martain/Qwest asked everyone to send their questions to the CMP mailbox.

CenturyLink Response