Wholesale: Products & Services

Open Product/Process CR PC093002-05X Detail

Description Of Change

1) Interface differences not clear (EDI or GUI). Functional differences should not exist.

2) Field level of detail for both inquiry and response transactions lacking (what special characters apply?)

3) ALL valid entries be provided for each transaction type

4) Acronyms must be defined

5) Usage rules must be defined

6) References must defined or have links provided

7) Complete and accurate business rules must be provided

8) Restrictions must be clearly defined

9) Lack of business rules to support usage cannot occur

10) Process established to sync up EDI documentation (disclosure documents and appendices)

NOTE: As originally intended, MCI considers this CR to be a process change request. The CMP document is specific:

Section 5.1 states "A CLEC or Qwest seeking to change an existing OSS Interface, (CR to establish a new OSS Interface, or to retire an existing OSS Interface must submit a Change Request)."

Section 5.3 states "If a CLEC wants Qwest to change a product/process, the CLEC e-mails a Change Request (CR) Form to the Qwest CMP Manager, cmpcr@qwest.com."

MCI's CRs, as with Qwest internal documentation enhancements, should not be subject to IMA resources.

Project Meetings

4/17/03 CMP Systems Meeting Kit Thomte/Qwest stated that there is one more walk on to discuss regarding, from Liz Balvin. Liz Balvin/MCI stated that she was expecting a follow up call from Qwest last month and never got one. Kit Thomte/Qwest stated that nothing has changed in regard to this issue. Liz Balvin/MCI stated that WorldCom submitted process CRs and Qwest unilaterally processed them as systems CRs. Liz stated that if Qwest objected to MCI’s issuing these CRs as Process CRs, then Qwest needs to take this to the oversight committee. Kit Thomte/Qwest stated that Judy Schultz needs to address this issue and that Judy will be returning to the meeting after lunch. Liz Balvin/MCI stated that WorldCom wanted the CRs reverted back to Product/Process and sees that it was not done. Liz stated that she does not know if Judy is aware of that. Lynn Notarianni/Qwest stated that Judy is aware of your position on that. Lynn stated that from a standpoint of resolution, Qwest’s position is that we would not be escalating on ourselves on an issue that we feel that the decision was made congruent with how we’ve treated these types of issues in the past. Lynn stated that these CRs do need and take systems resources in order to do the work. Kit Thomte/Qwest recommended that we break for lunch and reconvene at 1:00 p.m. MT. Liz Balvin/MCI stated that WorldCom submitted 3 CRs as document changes and Qwest unilaterally changed them to systems CRs. Liz stated that this conversation has gone round and round. Liz stated that she tried to change the language back in December because she did not want these to impact IMA resources. Liz stated that the Qwest EDI implementation team changes documentation if Qwest finds a problem. Liz stated that if Qwest believes that WorldCom inappropriately sent these as Product/Process, Qwest needs to do something. Liz noted that any time there has been a cross over we’ve agreed to it in this forum and stated that she sees Qwest as out of process and doesn’t know how to better address that. Judy Schultz/Qwest stated that it is important to have this discussion and feels that we are at an impasse. Judy apologized if in the past Qwest has made unilateral decisions without communicating those decisions to change the CRs from Product/Process to Systems. Judy stated that Qwest is in the unique position of knowing which it should be and when there will be an impact to the systems. Judy stated that you might think it is just a process change, but we do know our internal systems and can say when a request would really impact a system. Judy noted that on the other hand, some changes come in as systems and we can look at it and determine that it would not require systems restraints and so we suggest crossing those CRs over to Product/Process. Judy stated that an email is sent to state if processed as a Product/Process or a Systems CR. Judy stated that the one issue that we are a little bit apart on is what to do with these systems documentation changes. Judy stated that in Section 8, which describes systems changes, the deliverables do include the system’s documentation, which is Sue’s (Stott) team. Liz Balvin/MCI stated that she agrees that the initial documentation to documented system enhancements per release should be included, but this is after it is implemented and a CLEC identifies a flaw with the documentation. Liz stated that in December, she said that the change was not intended to change existing documentation or previously existing versions, we just want issues addressed going forward. Liz stated that resources are required for new release documents, but once the document is used and a defect is identified, they should be corrected. Liz noted that the CLECs work with the EDI documentation team and when an issue is identified, that team fixes the problem. Sue Stott/Qwest stated that her team handles those in the same manner as a production support bug. Liz Balvin/MCI stated that these CR’s are for the issues that the EDI team said Qwest would not do as a bug fix. Wendy Green/Qwest stated that those were ones that Qwest viewed as enhancements rather than a bug in the documentation. Sharon Van Meter/AT&T asked if after a release is implemented and a bug is identified in the documentation, WorldCom sends an email to someone? Judy Schultz/Qwest stated that should go through production support. Liz Balvin/MCI stated that the production support help desk would not know this stuff. Liz Balvin/MCI stated that they do work with the EDI team and were told to issue these CRs. Wendy Green/Qwest stated that they are not a bug because the information is already there, it is an enhancement. Wendy noted that a lot of the time Qwest fixes issues that a CLEC brings forwards through that team but in this case you were requesting something a bit bigger than simply a clarification or a bug fix. Liz Balvin/MCI stated that it is not an enhancement because the documentation is incorrect. Lynn Notarianni/Qwest stated that we are disagreeing about a gray area, one side views as an enhancement and one side views as a bug. Donna Osborne-Miller/AT&T stated that her consumer team is finding this a challenge, they are trying to work with a manual and are feeling the same frustration. Liz Balvin/MCI stated that she understands Qwest’s position to not look at every data field so agreed to change the CR. Liz stated that the guidelines are for Qwest to focus on documentation going forward. Judy Schultz/Qwest stated that there is a process for documentation issues when Qwest and the CLECs believe that it is a bug. Liz Balvin/MCI stated is for when Qwest believes it to be a bug. Judy Schultz/Qwest asked when it happens that something in the documentation that a CLEC sees as a defect and Qwest doesn’t, would it satisfy the CLECs if going forward as fields are impacted in the course of a release, the documentation would be changed going forward to adhere to those expectations. Sue Stott/Qwest stated that this is currently occurring. Liz Balvin/MCI stated that in reference to this CR, they were told to issue a CR., as well as for the other 2 CRs. Sue Stott/Qwest stated that where it gets gray is when further clarification is needed for a field. Liz Balvin/MCI stated that these items are not gray, they are adding valid values or formats. Sue Stott/Qwest stated that the bigger issue for IT documentation is Qwest has people working on the releases and when they get a request for a documentation update, the people have to be diverted from the release in order to do the documentation updates. Sue stated that maybe the answer is less capacity for a release. Judy Schultz/Qwest stated that she wants to make sure that we’re clear. Judy noted that if there were 200 different fields to update, that would be a big effort. Judy stated that she thought she heard that IT was going forward in trying to follow the proposed guidelines. Sue Stott/Qwest stated that IT does that today and noted that her concern is, if you are an EDI user you are not going to pay close attention to the new release right away and that Qwest will not be made aware of issues until much later. Randy Owen/Qwest stated that Qwest needs to be careful because you cannot update for some products and not all, that would create other problems. Randy stated that we need to look at updates across the board, maybe a legend should be developed. Liz Balvin/MCI stated that the EDI documentation is going to come along because you now have users. Liz noted that consistency is an excellent point, if you only do that on one field then it could create inconsistency. Liz stated that she liked the idea of a legend but would need to check with her coders to see if one would work for them. Liz stated that she could possibly only be looking at a specific field and would need a guide to tell her what to look at first. Judy Schultz/Qwest asked what if we do a running cheat sheet. Randy Owen/Qwest stated that we saw that this CR might take us there and started down that path. Then heard that is not what was wanted. Sue Stott/Qwest stated that we have to carefully scrutinize to ensure that a documentation change doesn’t also mean a system change. It is so tightly related, the difference can be as subtle as an and/or difference. Sue stated that is another reason why system resources are needed. Judy Schultz/Qwest stated that she understands that it is the same resources and is just trying to explore if IT can do a piece at-a-time. Judy asked if there are ever any times when it would be logical do to this kind of work. Is there ever a time in development when we could spend time doing this? Sue Stott/Qwest stated that it would still take systems resources to do that and stated that the issue is if it affects the voting capacity for a release. Sue stated that in many cases the same resources are used for coding and documentation. Liz Balvin/MCI asked if she could update the single source CR with a title change to ‘Guiding Principals to Qwest Documentation on Going Forward Basis, When Documentation Happens’, and will list the 10-items that you say you are using. Liz stated that the CR would then be moved back to Process and the documentation would be done when the regular document comes out. Liz stated that when new documentation comes out in future releases and sees that the guidelines are not being adhered to, and when it severely impacts her ability to do business then she would bring it forward. Liz stated that she would be willing to do that in order to get these off the table. Liz stated that she understands where Qwest is coming from and that believes that Qwest understands where she is coming from. Kit Thomte/Qwest asked how the guidelines would be updated. Liz Balvin/MCI stated that they would be closed with this CR and for other items that come up, new CRs would be issued. Donna Osborne-Miller/AT&T asked if they are to call the Help Desk if problems after in production. Randy Owen/Qwest stated that the documentation team is to be contacted if prior to 30 days after production, after the 30 days, you contact the Help Desk. Wendy Green/Qwest stated that we took the principles and looked at redesigning to be 1 document for both EDI and GUI. Wendy stated that she did not know if that is still on the table. Liz Balvin/MCI stated that that was not the intent of the CR. Lynn Notarianni/Qwest asked if the guiding principles are separate from SBCs document. Wendy Green/Qwest stated that within the current format, will use the 10 guiding principles. Judy Schultz/Qwest asked if we should have a ‘guiding principles’ standing agenda item to identify what can be removed from the list. Wendy Green/Qwest stated that things would never be crossed off the list because they are principles and are there forever. Liz Balvin/MCI shared Judy’s concern and stated that they just came across a situation where they reserved TNs in the GUI and submitted the order in EDI. The reps populated the PON manually, typing them in lower case, but went out the door in upper case. Liz stated that it is not documented that they have to be in upper case. Liz stated that it would be helpful to have a tab for Documentation Experiences/Discussion. Lynn Notarianni/Qwest stated that there is a tab for design walkthrough’s and we can have one for documentation. Lynn noted that it could have something in it, or not. Liz Balvin/MCI stated that she understands Qwests position and stated that she did not know that she could call the Help Desk for documentation issues, that is a value add from this discussion. Sue Stott/Qwest asked that instead of a standing agenda item or separate tab, maybe we could add documentation issues to the SATE portion of the meeting. Wendy Green/Qwest stated that that would be fine. Liz Balvin/MCI stated that it could be EDI/SATE. Liz Balvin/MCI stated that she would review her 3 CRs to see if they are guiding principles. Judy Schultz/Qwest stated that if Liz wants to close as a process CR, is ok with that as long as it is noted that Qwest does not agree that this is Process work. Judy stated that Qwest truly believes them to be systems requests. Liz Balvin/MCI stated that she was not clear on closing the CR as a Process CR. Judy Schultz/Qwest responded that that is what Liz wanted. Randy Owen/Qwest stated that the guiding principles can be closed, Qwest has adopted them. Judy Schultz/Qwest stated that when a CLEC submits a CR, Qwest looks at it and determines if it is an impact for Product/Process or Systems. Judy stated that Qwest would email the CLEC if the category is different. Judy asked if that was an acceptable way to communicate. Liz Balvin/MCI stated that she did receive emails and that she responded that she did not agree with the assigned category. Judy Schultz/Qwest asked that when the email is sent, what happens if we cannot reach agreement, how do we break that stalemate? Lynn Notarianni/Qwest stated that in that case, if a CLEC says it is a Product/Process CR and Qwest says that it is not, it could result in a denial based on infeaseability. Judy Schultz/Qwest stated that it could result in a denial. Liz Balvin/MCI stated that she would not be unreasonable. Lynn Notarianni/Qwest stated that she is just stating that it could be a risk. Liz Balvin/MCI stated that the stalemate is due to the category of product/process or systems, and stated that she thinks that we have flushed out why each of us believes the way we do. Liz asked if these CRs are going to remain as Process CRs as they were originally intended? Judy Schultz/Qwest stated that she is ok with the change back to Process and closing it out, with Judy adding a note that Qwest believes the CR to be a Systems change. Judy stated that she has an obligation to represent Qwest’s position. Judy stated that in the future, as CRs come in the door, my team will send out an email with the category, and if you don’t agree you need to let us know and we will call a meeting to discuss. Judy asked if that was acceptable to the CLECs. Liz Balvin/MCI said yes. Lynn Stecklein/Qwest asked how the CRs that are marked as both Product/Process are to be handled. Judy Schultz/Qwest stated that in some instances the CR may be both, could be a systems CR and an MN. Judy stated that if the CR is for both P/P and Systems, the CRPM would ask that separate CRs be issued. Lynn Stecklein/Qwest clarified that all 3 CRs will be crossed-over to Product/Process and will be closed. There were no additional questions or comments.

4/18/03 Revised Description: That Qwest personnel utilize the following guidelines when updating documentation, on a going forward basis: 1) Interface differences not clear (EDI or GUI). Functional differences should not exist. 2) Field level of detail for both inquiry and response transactions lacking (what special characters apply?) 3) ALL valid entries be provided for each transaction type 4) Acronyms must be defined 5) Usage rules must be defined 6) References must defined or have links provided 7) Complete and accurate business rules must be provided 8) Restrictions must be clearly defined 9) Lack of business rules to support usage cannot occur 10) Process established to sync up EDI documentation (disclosure documents and appendices) NOTE: As originally intended, MCI considers this CR to be a process change request. The CMP document is specific:

Section 5.1 states "A CLEC or Qwest seeking to change an existing OSS Interface, (CR to establish a new OSS Interface, or to retire an existing OSS Interface must submit a Change Request)."

Section 5.3 states "If a CLEC wants Qwest to change a product/process, the CLEC e-mails a Change Request (CR) Form to the Qwest CMP Manager, cmpcr@qwest.com."

MCI's CRs, as with Qwest internal documentation enhancements, should not be subject to IMA resources.

--Original Message-- From: Elizabeth Balvin [mailto:liz.balvin@wcom.com] Sent: Monday, January 27, 2003 5:09 PM To: 'lsteckl@qwest.com' Cc: 'Johnson, Bonnie J.'; 'amaus@mainstreetcom.com'; 'arlen@contactcom.net'; 'Bart Atkinson (E-mail)'; 'byron.dowding@alltel.com'; 'Carla D NCAM Pardee (E-mail)'; 'chris@contactcom.net'; 'Dan Rosedahl (E-mail)'; 'David Hennes (E-mail)'; 'dosborne@att.com'; 'freddi@microtech-tel.com'; 'John Berard (E-mail)'; 'Karen Clauson'; 'Kimberly Isaacs'; 'Lea Barron (E-mail)'; 'Leilani Hines (E-mail)'; 'Linda Fowlkes (E-mail)'; 'Littler Bill (E-mail)'; 'Lori Mendoza (E-mail)'; 'lrucks@blackfoot.com'; 'Mark R. Powell (E-mail)'; 'mzulevic@covad.com'; 'Nancy Conant (E-mail)'; 'Peder Gunderson (E-mail)'; 'Sharon K NCAM Van Meter (E-mail)'; 'Sherry Lichtenberg (E-mail)'; 'Stephanie Prull (E-mail)'; 'Tom Hyde (E-mail)'; 'vicky@consolidatedtelcom.com' Subject: EDI Documentation Lynn, The following is a high level list of issues WCom has identified regarding Qwest's EDI documentation. While this list is not inclusive, per Qwest recommendation, WCom provides as a start at developing "guidelines" for Qwest documentation updates going forward: 1) Interface differences not clear (EDI or GUI), CLECs expect functionality would NEVER differ, need to confirm 2) Field level of detail for both inquiry and response transactions lacking (what special characters apply?) 3) ALL valid entries be provided for each transaction type 4) Acronyms must be defined 5) Usage rules must be defined 6) References must defined or have links provided 7) Complete and accurate business rules must provided 8) Restrictions must be clearly defined 9) Lack of business rules to support usage cannot occur 10) Process established to sync up EDI documentation (disclosure documents and appendices)

12/18/02 Email w/ Revised Description: --Original Message-- From: Elizabeth Balvin [mailto:liz.balvin@wcom.com] Sent: Wednesday, December 18, 2002 2:19 PM To: 'cmpcr@qwest.com' Cc: 'lsteckl@qwest.com' Subject: FW: SCR093002-05 Single Source Document for Implementing EDI

WCom is willing to change the language in the attached CR to better reflect the intended change. NOTE: The original request was submitted as a "process" CR which is still the intended CMP WCom wishes to follow. As such, the CR would not compete for IMA resources and impact prioritization. The new language should read:

This change request is not intended to modify in any way the current or planned Qwest applications or code to support these systems. In addition, this change request is not intended to be retroactive to current or previous OSS interface requirements. It is intended to be implemented on a going forward basis. The request seeks to require CLEC input such that Qwest understands from a "users perspective" what changes are need to provide "efficacy" as required by the FCC. WCom recommends working sessions with interested Parties as a means to establish ground rules for documentation.

An exception would not be necessary if Qwest agrees with following the Process CMP.

9/27/02 Original Description: At a minimum, the following documents are provided by Qwest for EDI Implementation: Product Catalog (PCAT) Qwest Preparation Guides EDI Disclosure Documentation LSR Developer Worksheets Premis Guide for City List EDI/SATE Error List and IMA User's Guide Sources are not always in sync and cross referencing causes delays