HAM AFFIDAVIT Attachment 9

HAM AFFIDAVITAttachment 9

EH Attachment 9-1

Accessible

“Final Draft of the SBC 13-State Change Management Process Document – California”

Date: February 14, 2000

Number: CLECC00-036

Contact: Pacific Bell Account Manager

This Accessible Letter serves to provide the Final Draft of the SBC 13-State ChangeManagement Process document as stated in Accessible Letter CLECC00-014 dated January 24,2000. SBC will host a meeting, scheduled as follows, to “walk-through” the attached Final Draftdocument.

The 13-State Change Management Process document consists of the ten files listed below in theattached self-extracting WinZip file. Please review this document prior to the meeting.Attendance at this meeting is important for CLECs from all regions as it provides an opportunity tocomment and ask questions before the Final 13-State CMP document is implemented on April 1,2000.

Logistics for the meeting are:

Date: February 17, 2000Location: Holiday Inn, Mart Plaza

Wolf Point Ballroom, 15th Floor350 North OrleansChicago, Illinois

Time: 9:00 AM to 5:00 PM CSTConferenceBridge: 800.406.7410 Passcode: 831265#

If you have not already confirmed your attendance (for both conference bridge participants andthose attending in person), please respond by Tuesday, February 15th. You may confirm byemailing Eva Hardy at [email protected] (or call her on 925-277-3873).

Please direct any questions to your Account Manager.

Attachment

EH Attachment 9-2

File: SBC 13State CMP_021100.docFile: AppA-SBC 13State CMP_020700.xlsFile: AppB-SBC 13State CMP_021100.xlsFile: AppC-SBC 13State CMP_021100.xlsFile: AppD-SBC 13State CMP_021100.xlsFile: AppE-SBC 13State CMP_021100.xlsFile: AppF-SBC 13State CMP_021100.xlsFile: AppG-SBC 13State CMP_021100.docFile: AppH-SBC 13State CMP_021100.docFile: AppI-SBC 13State CMP_021100.doc

[See EH Attachment 9.1 – 9.10]

Draft 13-State CMP 02/11/2000 Version Page 1

EH Attachment 9.1-1

SBC

Competitive Local ExchangeCarrier (CLEC)

Interface

Change Management

Process


EH Attachment 9.1-2

Interface Change Management Process: SBC andCompetitive Local Exchange Carrier (CLEC)

Table of Contents

Table of Contents ........................................................................................................... 2

1.0 Purpose .................................................................................................................... 5

2.0 Scope........................................................................................................................ 5

3.0 Changes to Existing Interfaces............................................................................... 6

3.1 Types of Changes to Existing Interfaces......................................................... 6

3.2 Two Categories of Changes to Existing Interfaces........................................ 7

3.3 Category One (Gateway) Change Process.................................................... 7

3.4 Versioning of Gateway Releases… ..........................................................…10

3.5 Category Two (GUI) Change Process...........................................................10

4.0 Introduction of New Interfaces...............................................................................12

4.1 Two Categories of New Interfaces.................................................................12

4.2 Category One (Gateway) Process - New Interface......................................12

4.3 Category Two (GUI) Process - New Interface...............................................14

5.0 Retirement of Existing Interfaces .........................................................................16

5.1 Retirement Groups ..........................................................................................16

5.2 Interface Retirement Process.........................................................................16


EH Attachment 9.1-3

6.0 Other Items .............................................................................................................17

6.1 Emergency Situations .....................................................................................17

6.2 Exceptions........................................................................................................18

6.3 Training .............................................................................................................19

6.4 Documentation Change..................................................................................19

6.5 CLEC Joint Testing .........................................................................................19

7.0 Outstanding Issue Solution...................................................................................20

7.1 Process Initiation. ............................................................................................20

7.2 Issue Timeline. .................................................................................................20

7.3 Dispute Vote. ...................................................................................................20

7.4 Qualified CLECs..............................................................................................21

7.5 Voting Process. ...............................................................................................22

8.0 Managing the Change Management Process....................................................23

8.1 Change Management Points of Contacts.....................................................23

8.2 Change Management Process Meetings .....................................................23

8.3 Change Request Process ..............................................................................24

8.4 Modifications to the CMP Document.............................................................24

8.5 Enforcement .....................................................................................................25

9.0 New CMP Business ..............................................................................................25

Appendix A - SBC Interface Matrix

Appendix B - Timeline for Category One Changes to Existing Interfaces


EH Attachment 9.1-4

Appendix C - Timeline for Category Two Changes to Existing Interfaces

Appendix D - Timeline for Introduction of New Category One Interfaces

Appendix E - Timeline for Introduction of New Category Two Interfaces

Appendix F - Timeline for Retirement of Interfaces (Groups A and B)

Appendix G - Matrix View of Timelines in Appendices B Through F

Appendix H - CLEC Change Request Process

Appendix I - Transition Plan


EH Attachment 9.1-5

1.0 PurposeThis document contains the standards for the Change Management Process(“CMP”) by which SBC Communications (herein after referred to as “SBC”,consisting of Ameritech, Nevada Bell, Pacific Bell, Southwestern Bell Telephone,and Southern New England Telephone) will notify Competitive Local ExchangeCarriers (“CLECs”) of changes to the Operational Support Systems (“OSS”)interfaces, introduction of new interfaces and retirement of interfaces detailed belowand provides for the identification and resolution of CLEC issues associated withthe CMP. The CMP is intended to establish a structural means by which (1) CLECsmay propose changes to the OSS interfaces and (2) SBC will notify CLECs ofchanges to be made to the OSS interfaces. The parties intend for the CMP to bedynamic in nature, managed through regularly scheduled meetings (at a minimum ofonce a quarter) and based on group consensus. This document may be revised asbusiness and/or regulatory conditions dictate and any agreed-upon modifications tothe process will be included in this document as described in Section 8.4. NewCMP Business items are located in Section 9.0.

2.0 Scope2.1 This process pertains to all ordering, pre-ordering, and provisioning andmaintenance electronic interfaces, specific to end-user ordering only, including, butnot limited to, SBC’s Application to Application Interfaces and Graphical UserInterfaces (“GUI”), as listed in Appendix A of this document.

SBC will continue to develop its interfaces according to industry guidelines (asdiscussed in Section 3.3.1 of this document) for wholesale customers to order andmaintain Local Services. As industry guidelines evolve, SBC will use the CMP anddiscussions at the CMP meetings to review the guidelines and determineappropriate implementation choices.

2.2 This document applies to SBC and all CLECs operating in Arkansas,California, Connecticut, Illinois, Indiana, Kansas, Michigan, Missouri, Nevada, Ohio,Oklahoma, Texas and Wisconsin.

2.3 The following list of items will be addressed in the regional CLEC User Forumsusing documented processes developed by User Forum participants in eachregion. Issues may be initiated by either SBC or by CLEC participants. Theassumption used while developing this CMP is that the following issues will be dealtwith in regional CLEC User Forums. If this assumption proves incorrect, theseitems can be brought back and dealt with in Change Management and/or workedthrough the appropriate Account Manager.

♦ Manual Processes

♦ Manual Forms

♦ Business Processes


EH Attachment 9.1-6

♦ Methods &Procedures (except as necessary related to release walk-throughs)

The appropriate CLEC forums will address Non-OSS impacting businessprocess/operational issues not addressed in this CMP.

2.3.1 If a CLEC is unsure of the appropriate forum to which an issue should besubmitted, the CLEC can contact its Account Manager for direction or can bring theissue to a Change Management meeting or User Forum meeting to discuss theproper forum in which the issue can be worked to resolution.

2.3.2 Issues covered in one forum that are transferred to another forum will be fullydocumented in both forums at the time of transfer and appropriate notification willbe distributed, as necessary. If any issue is referred to the Change Managementgroup or a User Forum from another meeting, the CLEC community will be notifiedof the need for this issue to be addressed in the appropriate forum. All parties willmake every effort to insure that issues addressed in other meetings or forums arecommunicated to the appropriate CMP or User Forum.

3.0 Changes to Existing Interfaces3.1 Types of Changes To Existing Interfaces

The CMP manages changes to OSS interfaces that affect CLECs’ production ortest environments. Such changes may encompass:

3.1.1 Operations changes to existing functionality that impact the CLEC interface(s)upon SBC’s release date for new interface software. For example:

• adding/deleting/modifying fields required to access a function

• changing the flow, or sequence, of interface operation

• adding an edit to ensure a required field is entered

3.1.2 Technology changes that require CLECs to meet new technical requirementsupon SBC’s release date. For example:

• eliminating a previously supported operating system software (e.g.,Microsoft™ Windows™ 3.0), hardware or protocol

• requiring a new software, hardware (e.g., 8Mb RAM), or protocol

3.1.3 Additional functionality changes that may be used at the CLEC’s option, on orafter SBC’s release date for new interface software. For example:

• adding a new field to access a new function, without other impacts

• allowance for additional entries into existing fields

• adding a new supported software, hardware or protocol

3.1.4 Regulatory Mandates

• Those changes that may be mandated by regulatory bodies, as discussed inSection 6.2.4 of this document.


EH Attachment 9.1-7

3.2 Two Categories of Changes To Existing Interfaces

This process divides changes into two categories:

§ Category One (Gateway) changes include changes to gateway applications,such as Electronic Data Interchange (“EDI”) Ordering, EDI/Common ObjectRequest Broker Architecture (“CORBA”) and DataGate Pre-Ordering.

§ Category Two (GUI) is solely for changes to GUIs where the change is specificto a GUI (e.g., enhancements to the print capability in the Local Service Request(LSR) EXchange system (LEX)).

3.3 Category One (Gateway) Change Process (Appendix B)

3.3.1 For Gateway interfaces based on industry guidelines, the parties agree thatthe guidelines developed at the industry forums i.e., Alliance forTelecommunications Industry Solutions (“ATIS”), Ordering and Billing Forum (“OBF”)will be the basis for managing change. SBC anticipates using applicable OBFGuidelines; however the needs and constraints of SBC’s legacy systems may limituse of all such Guidelines; SBC will identify any proposed variances from OBFGuidelines.1 Therefore, as the industry guideline e.g., Local Service OrderingGuidelines (“LSOG”) requirements are being determined at OBF, SBC will reviewthe requirements to determine compatibility with SBC’s systems. There may beother changes initiated by SBC to gateway interfaces that are not a result ofATIS/OBF change drivers (e.g., changes to enhance order flow-through). SBC willalso consider changes recommended by CLECs through the Change RequestProcess (see Section 8.3).

3.3.2 Regardless of the change driver, SBC will prepare a preliminary package ofthe required changes and share these plans at a scheduled Change Managementmeeting nine (9) to twelve (12) months in advance of the target implementation date.SBC will share its plans as part of its 12-Month Development View (see Managingthe CMP, Section 8).

3.3.3 SBC will provide a Release Announcement delivered to CLECs via anemail Accessible Letter. The letter will contain a written summary of the change(s)in plain English, a target timeframe for implementation, any cross reference toindustry documentation, and any known exceptions to industry guidelines.

3.3.4 If a CLEC identifies issues or requires clarification, the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager. The

1 This is in accordance with General Section 1.0, paragraph 1.4 of the practices in the OBF Local ServiceOrdering Guidelines (LSOG), which states that “Options described in this practice may not be applicableto individual provider’s tariffs; therefore, use of either the field or valid entries within the field is based onthe provider’s tariffs/practices”.


EH Attachment 9.1-8

CLEC response will specify the CLEC’s questions, issues and any alternativerecommendations for implementation. The CLEC response must be received bythe SBC Account Manager in writing no later than the 7th calendar day following thedate of the Release Announcement.2

3.3.5 SBC will review all CLEC responses.

3.3.6 Within seven (7) calendar days of the end of the time period specified in Step3.3.4 (14th calendar day following the date of the Release Announcement), SBC willprovide written answers to CLEC questions via Accessible Letter. SBC’s answerswill be shared with all CLECs, unless any questions were specifically identified as“private” by any CLEC.

3.3.7 If SBC announces any changes before applicable guidelines are finalized atthe ATIS/OBF industry forums, SBC will review the final guidelines when they areissued for any alterations that may be necessary for compliance with the finalizedrequirements and will work these changes within the standards of this CMP.

3.3.8 No sooner than the last day of the period specified in Step 3.3.6, SBC willsend the Initial Release Requirements to CLECs via another email AccessibleLetter. The Initial Release Requirements will contain the planned implementationdate, Index of Changes, updated interface requirements (e.g., Local ServiceOrdering Requirements (“LSOR”) changes), exceptions to transaction sets or datamodels, industry cross reference, reporting impacts, (if any) and timeframes forCLEC joint testing. In setting the timeframes for CLEC joint testing, SBC willconsider the scope of the release and potential impact on CLEC developmentefforts. Generally, SBC’s planned implementation will fall within 152 to 172calendar days from the date of the Initial Release Requirements. SBC will sponsora walk-through for CLECs of the Initial Requirements with the appropriate internalsubject matter experts. It is SBC’s intent to hold this walk-through during the secondweek of the CLEC comment cycle, but no later than three business days before theend of the comment cycle.

3.3.9 If a CLEC identifies issues or requires clarification (including issues with theplanned implementation timeline and testing windows), the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager, whichmust be received not later than the 21st calendar day after the date of the InitialRelease Requirements.

3.3.10 SBC will review all CLEC responses to the Initial Release Requirements.

2 In all cases, the date of any Accessible Letter referenced in this Agreement will be the date on whichSBC emails the document to CLECs. Provided, however, that any Accessible Letter transmitted by e-mailafter 4:00 PM Central Time shall be considered as transmitted the next business day. SBC will send theAccessible Letters to the Change Management Point(s) of Contact designated by the CLEC. It is eachCLEC’s responsibility to ensure that SBC has a current contact list.


EH Attachment 9.1-9

3.3.11 Not later than the 21st calendar day following the end of the period specifiedin Step 3.3.9, SBC will provide written answers to CLEC questions via an emailAccessible Letter. SBC’s answers will be shared with all CLECs, unless anyquestions were specifically identified as “private” by any CLEC. Any changes thatmay occur as a result of the answers will be distributed to all CLECs in the sameAccessible Letter. This Accessible Letter will constitute the Final ReleaseRequirements, which will include a summary of changes from Step 3.3.8 above(Index of Changes), implementation date of the new version, the sunset date of theold version and reference to SBC’s CLEC web site location where the detailedFinal Release Requirements are stored. Generally, SBC’s planned implementationwill fall within 110 to 130 calendar days from the date of the Final ReleaseRequirements. The implementation timeline for the release will not begin until allrelated documentation is provided.

3.3.12 Should a CLEC elect to initiate the Outstanding Issue Solution (OIS)process described in this CMP related to the Final Release Requirements forCategory One Changes, the CLEC must send a written notice (via email, fax orregular mail) to its SBC Account Manager, which must be received within seven (7)calendar days from the date of the Final Release Requirements.

3.3.13 Upon receipt of a CLEC OIS notice relating to such Final ReleaseRequirements, SBC will schedule an OIS conference call for 2:00 PM Central Time,seven (7) calendar days after the due date for the OIS notices (14 calendar daysafter the date of the Final Release Requirements). Additional procedures for anOIS related to such Final Release Requirements are as specified in Section 7.0 ofthis document.

3.3.14 If no Final Release Requirements OIS is initiated (or after successfulconclusion of any such OIS), the established implementation time line will begin.Testing will be conducted, as defined in this section, by SBC and any interestedCLEC. Testing will continue until the agreed upon testing exit criteria have beensatisfied, in accordance with a negotiated joint release test plan, to the mutualsatisfaction of the parties.

a) SBC will make testing available in accordance with the timeframes specifiedin the Final Release Requirements. The available testing timeframe shall beno less than 30 calendar days.

b) For LEX LSR changes, SBC will provide CLECs access to the testenvironment in accordance with the timeframes specified in the Final ReleaseRequirements. The available testing timeframe shall be no less than 30calendar days.

c) Testing must be scheduled to end at least seven (7) calendar days prior tothe scheduled implementation date, unless otherwise agreed between SBCand the CLEC. This seven-day period is to accommodate the softwarefreeze in preparation of the release, and to provide CLECs an opportunity to


EH Attachment 9.1-10

invoke an OIS, if necessary as a result of release testing, as described inSection 7.0 of this document.

3.3.15 If the parties cannot agree on whether the test criteria have been satisfiedwithin the planned timeframe, either SBC or the CLEC may invoke a second OISprocess related to Gateway Implementation, using the eligibility requirementsand timeline defined in Section 7.0 of this document.

3.3.16 If no Gateway Implementation OIS is initiated after the completion of jointtesting (or after successful conclusion of any such OIS), SBC will implement the newrelease or updates.

3.4 Versioning of Gateway Releases

3.4.1 Unless mandated or properly proposed and accepted under the exceptionprocess outlined in Section 6.2, SBC will implement no more than four releasesrequiring coding changes to the CLECs’ interfaces, no less than three months apart,within a calendar year. SBC will support two versions of software for its EDIOrdering and EDI/CORBA Pre-Ordering interfaces. Those versions will be thecurrent and previous versions, whether the previous is a basic EDI/LSOG version ora SBC upgraded EDI/LSOG version (a dot release). SBC will version the latest tworeleases using a phased approach per regions, as outlined in the Transition Plan(attached as Appendix I).

3.4.2 Specifically, if the current LSOG version is considered LSOGA, then the firstrelease in 2000 would be LSOGB. SBC will continue to make LSOGA available foruse along with LSOGB. The following release would be LSOGB.1. WhenLSOGB.1 is implemented, SBC would sunset LSOGA and will maintain the currentversion and previous version, LSOGB and LSOGB.1. Thus, two consecutiveversions of software (including dot releases) for SBC's EDI Ordering andEDI/CORBA Pre-Ordering interfaces will be up and running at all times. SBC’sRelease Announcement of a new version will constitute notification of sunset for theoldest version.

3.4.3 Upon implementation of the newest release (LSOGB.1 in the example listed in3.4.2), SBC will no longer support the oldest version (LSOGA in the example listedin 3.4.2). SBC will maintain two versions, as described above, even if suchversioning departs from final guidelines adopted by OBF.

3.4.4 For mandated changes that occur between regularly scheduled releases, it isnot SBC’s intent to retire the oldest version in order to implement the mandatedchange. Mandated changes will be evaluated on a case-by-case basis forimplementation in either both versions or the latest version.

3.4.5 SBC’s DataGate Pre-Ordering interface utilizes similar versioningpatterns.SBC will support two versions of software, the current version and the immediatepast version. SBC will version the latest two releases beginning with the first



release of 2000. SBC’s release announcement of a new DataGate version willconstitute notification of sunset for the oldest DataGate version and will includenotification of the specific version of DataGate that will sunset with the new release.Upon implementation of the newest release, SBC will no longer support the oldestversion.

3.5 Category Two (GUI) Change Process (Appendix C)

3.5.1 SBC will share plans for changes to GUI at scheduled Change Managementmeetings, as part of its rolling 12-month Development View (see Managing theCMP, Section 8.0). SBC makes available one version of a GUI at any given time.

3.5.2 At least 21 days prior to its planned implementation date, SBC will detail thechanges in an Initial Requirements Release delivered to CLECs via an emailAccessible Letter. The letter will contain a written summary of the change(s) in plainEnglish, a target timeframe for implementation, and any cross-reference to updatedUser Guide or revised User Guide pages. LEX changes associated with the LSRwill be handled on a timeline to allow for the 30-day test window discussed in3.3.14b above.

3.5.3 If a CLEC identifies issues or requires clarification, the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager. TheCLEC response must be received by SBC within four (4) business days of the dateof the Initial Release Requirements. The response will specify the CLEC’squestions, issues and any alternative recommendations for implementation.


3.5.5 Within three (3) business days of the end of the period specified in Step 3.5.3above, SBC will provide written answers to CLEC questions via email AccessibleLetter. SBC’s answers will be shared with all CLECs, unless any questions werespecifically identified as “private” by any CLEC. Any changes that may occur as aresult of the responses will be distributed to all CLECs in the same AccessibleLetter. This will constitute the Final Release Requirements which will include asummary of changes from Step 3.5.2 above, indication of type of change (i.e.,documentation change, business rule change, clarification change), changedrequirements pages, and release date. Generally, SBC’s planned implementationdate will be no sooner than the 14th calendar day from the date of the Final ReleaseRequirements. The implementation timeline for the release will not begin until allrelated documentation is provided.

3.5.6 Should a CLEC elect to initiate the OIS process related to Final ReleaseRequirements for Category Two (GUI) Changes, the CLEC must send a writtennotice (via email, fax, or regular mail) to its SBC Account Manager, which must bereceived within two (2) business days of the date of the Final ReleaseRequirements.



3.5.7 Upon receipt of an OIS notice related to such Final Release Requirements,SBC will schedule a conference call to be held at 2:00 PM Central Time, two (2)business days after the due date for OIS initiation notices (four (4) business daysafter the Final Release Requirements). Additional procedures for an OIS related toFinal Release Requirements are specified in Section 7.0 of this document.

3.5.8 No provision for CLEC joint testing is included in the Category Two process,with the exception of LEX, referred to in Section 3.3.14b.

3.5.9 If there is no Final Release Requirements OIS for GUI changes (or aftersuccessful resolution of such an OIS), SBC will implement the new release orupdates following the established implementation timeline.

3.5.10 The OIS process is not available for SBC’s retail systems, as specified inSection 7.0 of this document.

4.0 Introduction of New Interfaces4.1 Two Categories of New Interfaces

This process divides the introduction of new interfaces into two categories:Category One (Gateway) and Category Two (GUI).

4.2 Category One (Gateway) Process-New Interface (Appendix D)

4.2.1 Approximately nine (9) months in advance of the target implementation date,SBC will convene a Design and Development meeting with the CLEC community.SBC will share preliminary plans for the new interface, including regional availability,proposed implementation timeline, SBC constraints and exceptions to industrystandards, etc. During the Design and Development meeting, CLECs may providefeedback to SBC, including interest in developing to the initial version of theinterface. If available, SBC will share draft Initial Release Requirements.

4.2.2 If a CLEC identifies additional issues or wishes to provide feedback, theCLEC must send a written response (via email, fax or regular mail) to its SBCAccount Manager which must be received no later than the 4th business dayfollowing the date of the Design and Development Meeting. The CLEC responsewill specify the CLEC’s questions, issues and any alternative recommendations forimplementation.

4.2.3 SBC will communicate via Accessible Letter its interface development plans,including how it has incorporated CLEC feedback from the Design andDevelopment Meeting and additional written feedback (this can be combined withStep 4.2.4).

4.2.4 SBC will provide a Release Announcement to CLECs via an emailAccessible Letter. The letter will contain a written summary of the new interface inplain English, a target timeframe for implementation, any cross reference to industrydocumentation and any known exceptions to industry guidelines.



4.2.5 If a CLEC identifies issues or requires clarification, the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager, whichmust be received no later than the 7th calendar day following the date of the ReleaseAnnouncement. The CLEC response will specify the CLEC’s questions, issues andany alternative recommendations for implementation.

4.2.6 CLECs who are interested in developing to the initial version of the interface(as described in the Release Announcement) within six (6) months of SBC’splanned implementation, will document that intent via one of the following methods:

§ a Record of Understanding (“ROU”),

§ a signed Interconnection Agreement (“ICA”) with an implementation schedule forthe interface,

§ negotiating terms and conditions for access to the interface, subject toacceptable substantiation and sanctioned by a majority vote of the otherQualified CLECs3.

ROUs can be modified or submitted through Step 4.2.13 of the process.


4.2.8 Within seven (7) calendar days of the end of the time period specified in Step4.2.5 (14 calendar days following the date of the Release Announcement), SBC willprovide written answers to CLEC questions via Accessible Letter. SBC’s answerswill be shared with all CLECs, unless any questions were specifically identified as“private” by any CLEC.

4.2.9 If SBC announces a new interface before applicable guidelines are finalizedat the ATIS/OBF industry forums, SBC will review the final guidelines when they areissued for any alterations that may be necessary for compliance with the finalizedrequirements. SBC will consider its system requirements and provide knownexceptions to industry guidelines.

4.2.10 No sooner than the last day of the period specified in Step 4.2.8, SBC willsend the Initial Release Requirements to CLECs via another Accessible Letter.The Initial Release Requirements will contain the planned implementation date,interface requirements, exceptions to the EDI transaction set (if applicable), industrycross-reference and reporting impacts, if any. Generally, SBC’s plannedimplementation will fall within 152 to 172 calendar days from the date of the InitialRelease Requirements.

4.2.11 If a CLEC identifies issues or requires clarification (including issues with theplanned implementation date), the CLEC must send a written response (via email,

3 The definition of “Qualified” CLECs is the same as is specified in Section 7.0 (the OIS section) ofthis document.



fax or regular mail) to its SBC Account Manager, which must be received no laterthan the 21st calendar day after the date of the Initial Release Requirements.

4.2.12 SBC will review all CLEC responses to Initial Release Requirements.

4.2.13 Not later than the 21st calendar day following the end of the period specifiedin Step 4.2.11, SBC will provide written answers to CLEC questions via an emailAccessible Letter. SBC’s answers will be shared with all CLECs, unless anyquestions were specifically identified as “private” by any CLEC. Any changes thatmay occur as a result of the answers will be distributed to all CLECs in the sameAccessible Letter. This Accessible Letter will constitute the Final ReleaseRequirements which will include a summary of the changes from Step 4.2.12above, indication of type of change, (i.e., documentation change, business rulechange, clarification change, etc.), changed requirements pages and Release date.Generally, SBC’s planned implementation will fall within 110 to 130 calendar daysfrom the date of the Final Release Requirements. The implementation timeline forthe release will not begin until all related documentation is provided.

4.2.14 Should a CLEC elect to initiate the OIS process related to the FinalRelease Requirements for a New Category One (Gateway) Interface, the CLECmust send a written notice (via email, fax or regular mail) to its SBC AccountManager, which must be received within seven (7) calendar days from the date ofthe Final Release Requirements.

4.2.15 Upon receipt of a CLEC OIS notice related to such Final ReleaseRequirements, SBC will schedule an OIS conference call for 2:00 PM Central Time,seven (7) calendar days after the due date for the OIS notices (14 calendar daysafter the date of the Final Release Requirements). Additional procedures for anOIS related to such Final Release Requirements are as specified in Section 7.0 ofthis document.

4.2.16 If no Final Release Requirements OIS for a new Gateway Interface isinitiated (or after successful conclusion of any OIS), the established implementationtimeline will begin. Testing will be conducted as defined in this section by SBC andany interested CLEC. Testing will continue until the agreed upon testing exit criteriahave been satisfied in accordance with a negotiated joint release test plan, to themutual satisfaction of the parties.

a) SBC will make testing available in accordance with thetimeframes specified in the Final Release Requirements. The availabletesting timeframe shall be no less than 30 calendar days.

b) Testing must be scheduled to end at least seven (7) calendardays prior to the scheduled implementation date, unless otherwise agreedbetween SBC and a CLEC.

4.2.17 If the parties cannot agree on whether the test criteria have been satisfiedwithin the planned timeframe, either SBC or the CLEC may invoke a second OIS



process related to New Interface Gateway Implementation, using the eligibilityrequirements and timeline defined in Section 7.0 of this document.

4.2.18 If no Gateway Implementation OIS is initiated after the completion of jointtesting (or after successful completion of any OIS), SBC will implement the newinterface.

4.3 Category Two (GUI) Process - New Interface (Appendix E)

4.3.1 Approximately eight (8) weeks in advance of the target implementation date,SBC will share Design and Development information with the CLEC community(e.g., via a meeting, conference call or email Accessible Letter, etc.). SBC willshare preliminary plans for the new interface, including regional availability,proposed implementation timeline, SBC’s constraints and exceptions to industrystandards, etc. CLECs will provide feedback to SBC, including interest inimplementing the initial version of the interface. If available, SBC will share draftInitial Release Requirements.

4.3.2 If a CLEC identifies additional issues or feedback, the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager, whichmust be received no later than the 2nd business day following the date the Designand Development information is provided. The CLEC response will specify theCLEC’s questions, issues and any alternative recommendations forimplementation.

4.3.3 SBC will communicate its interface development plans via Accessible Letter,including how it has incorporated CLEC feedback from the meeting and additionalwritten feedback (this can be combined with Step 4.3.4).

4.3.4 SBC will detail the new interface in the Initial Release Requirementsdelivered to CLECs via an email Accessible Letter. The letter will contain a writtensummary of the new interface in plain English, a target timeframe forimplementation, how and when the User Guide will be available and user trainingrequirements.

4.3.5 If a CLEC identifies issues or requires clarification, the CLEC must send awritten response (via email, fax, or regular mail) to its SBC Account Manager, whichmust be received no later than the 4th business day after the date of the InitialRelease Requirements. The response will specify the CLEC’s questions, issuesand any alternative recommendations for implementation.


4.3.7 No later than the 3rd business day after the end of the period specified in Step4.3.5, SBC will provide written answers to CLEC questions via email AccessibleLetter. SBC’s answers will be shared with all CLECs unless any questions werespecifically identified as “private” by any CLEC. Any changes that may occur as aresult of the answers will be distributed to all CLECs in the same Accessible Letter.This will constitute the Final Release Requirements which will include a summary



of the changes from Step 4.3.4 above, indication of type of change, (i.e.,documentation change, business rule change, clarification change, etc.), changedrequirements pages and release date. Generally, SBC’s planned implementationwill be no sooner than the 14th calendar day from the date of the Final ReleaseRequirements. The implementation timeline for the release will not begin until allrelated documentation is provided.

4.3.8 Should a CLEC elect to initiate the OIS process related to the FinalRelease Requirements for a New Category Two Interface, the CLEC must send awritten notice (via email, fax or regular mail) to its SBC Account Manager, whichmust be received within two (2) business days of the date of the Final ReleaseRequirements.

4.3.9 Upon receipt of a CLEC OIS notice related to such Final ReleaseRequirements, SBC will schedule an OIS conference call for 2:00 PM Central Time,two (2) business days after the due date for the OIS notices (four (4) business daysafter the date of the Final Release Requirements). Additional proceedings for anOIS related to Final Release Requirements are as specified in Section 7.0 of thisdocument.

4.3.10 The OIS process is not available for SBC’s retail systems, as specified inSection 7.0 of this document.

4.3.11 For New Category Two Interfaces, CLECs may negotiate through their SBCAccount Manager the ability to pass a limited number of test transactions. Thiswould only be available after the interface is in a production mode and at theCLEC’s initial turn up of the interface.

4.3.12 If no Final Release Requirements OIS is initiated (or after successfulconclusion of any OIS), SBC will implement the new interface following theestablished implementation timeline.

5.0 Retirement of Existing Interfaces5.1 Retirement Groups

This process divides the retirement of all interfaces in the scope of this documentinto two groups:

§ Group A: retail interfaces (see Appendix A)

§ Group B: wholesale interfaces (see Appendix A)

§ Category 1: Gateway applications

§ Category 2: GUI applications

5.2 Interface Retirement Process (Appendix F)

5.2.1 Prior to sending a Retirement Notice, SBC will share its initial plans forretirement of existing interfaces at a scheduled CMP meeting. During thatscheduled meeting, SBC will explain the rationale for retiring the interface, where



the replacement functionality resides or where it will exist in production at least sixmonths prior to the scheduled retirement date, its plans to maintain the interface fora specified period of time, and its target date for the Retirement Notice.

5.2.2 SBC will announce the retirement of the interface in a Retirement Noticedelivered to CLECs via an email Accessible Letter. The letter will contain a writtensummary of the retirement plans in plain English and a retirement date. The letterwill also specify the interfaces where comparable functionality currently exists or willexist in production at least six months prior to the scheduled retirement date. Oncean interface with comparable functionality is in production, no CLEC may begin touse (i.e., "turn up" for the first time) the interface that is scheduled for retirement.For retirement of interfaces, SBC will provide the following notice (broken out byInterface Group) from the time of the Retirement Notice to the retirement of theinterface, unless SBC invokes the use of the Exception process, as described inSection 6.2.

• Group A: 12 months

• Group B:

• Category 1: 24 months

• Category 2: 12 months

5.2.3 If a CLEC identifies issues or requires clarification, the CLEC must send awritten response (via email, fax or regular mail) to its SBC Account Manager, whichmust be received no later than the 21st calendar day following the date of theRetirement Notice. The CLEC response will specify the CLEC’s questions, issuesand any alternative recommendations.


5.2.5 Not later than the 21st calendar day following the end of the period specified inStep 5.2.3, SBC will provide written answers to CLEC questions via an emailAccessible Letter. SBC’s answers will be shared with all CLECs, unless anyquestions were specifically identified as “private” by any CLEC. Any changes thatmay occur as a result of the answers will be distributed to all CLECs in the sameAccessible Letter. This will constitute the Final Retirement Notice, which willinclude the retirement date and any changes in Step 5.2.2 above.

5.2.6 With respect to retirement of Group B interfaces only, a CLEC may elect touse the OIS process. Should a CLEC elect to initiate the process described inSection 7.0, the CLEC must send a written notice (via email, fax or regular mail) toits SBC Account Manager, which must be received at least 30 calendar days priorto the scheduled retirement date.

5.2.7 Upon receipt of a CLEC OIS notice related to such Final Retirement Notice,SBC will schedule an OIS conference call for 2:00 PM Central Time, seven (7)calendar days after the due date of the OIS notices.



5.2.8 If no OIS is initiated, (or after successful conclusion of any OIS), SBC will retirethe interface on the retirement date announced.

6.0 Other Items6.1 Emergency Situations

6.1.1 Operational Points of Contact (OPOC)

Each CLEC will designate primary and secondary Operational Points of Contact(OPOC) for the regions in which it operates. The OPOC will serve as the CLECs’official designee for notifications on all emergency situations. The CLECs mustprovide the OPOCs’ names, telephone numbers, email addresses and fax numbersto its Account Managers. SBC will create the OPOC list. It is SBC and the CLEC’sresponsibility to maintain and update the information on the list.

6.1.2 Emergency releases or emergency implementation date changes will behandled as special cases.

6.1.3 Emergency releases are releases that address major software problems,production system failure or an interface failure. These also include releases thataddress significant production problems, the failure of scheduled releaseenhancements and the failure of pre-existing functionality.

6.1.4 The notification process interval will be handled on a case-by-case basis andwill depend on the type and extent of the emergency. Notification to the CLECs willbe sent as soon as reasonably practicable after the emergency is recognized. Theemergency notification may not be in the form of an Accessible Letter, and may besent via other expedited means (e.g., fax, email or phone call).

6.1.5 In emergency situations, mutual testing and problem resolution will beconducted through the OSS contacts for all companies involved. Disagreementsregarding the existence of an emergency situation shall be resolved throughinvoking an OIS, as described in Section 7.0, and/or escalation and may be broughtbefore the appropriate regulatory body.

Should a release have a major problem which has a significant impact to a CLEC,the CLEC or SBC may invoke an OIS where a remedy to the emergency situation,including backout and recovery considerations, will be decided.

6.2 Exceptions

6.2.1 Above and beyond the need to handle emergency situations, the partiesrecognize the need to occasionally allow for other exceptions to the CMP describedherein. However, because it will be difficult for SBC or other CLECs to accuratelyassess the impact of SBC’s proposed change on any given CLEC’s current orfuture development, any agreement to deviate from the normal CMP shall be agreedto unanimously by Qualified CLECs and SBC. If SBC wishes to propose that aspecified change, introduction of a new interface or retirement of an interface behandled on an exception basis, it will issue a Release (or Retirement) Requirements



Exception Accessible Letter, which indicates that it seeks an exception following theconclusion of a reply and comment cycle.

6.2.2 Following the timelines outlined in this document, CLECs may respond withquestions and issues. SBC may request that the question and comment period beexpedited as part of the exception. This expedited comment cycle would also beopen to CLEC comment. Qualified CLECs as defind in Section 7.4 of thisdocument, may indicate objections to handling the change, new interface orretirement as an exception. Lack of a response within the specified timelineindicates no objection.

6.2.3 SBC may proceed to implement the change, new interface or retirement onan exception basis only if there are no outstanding issues, or CLEC objections atthe end of the CLEC response cycle specified in Step 6.2.2 above.

6.2.4 Regulatory mandated changes, whereby a regulatory body specifically ordersexpanded or modified functionality within a mandated timeframe that does not allowfor the timelines specified in the CMP, will not be subject to the objection processfor exceptions. If necessary, objections to the mandated change, the method forhandling the mandated change, or the associated timeline may be taken to theapplicable regulatory bodies. In the Accessible Letter notification, SBC will provideany modified timelines for the change. If no such timeframe is specified, regulatorymandated change shall be subject to the CMP process as described in thisdocument. Every effort will be made to work mandated changes within this CMP.

6.2.5 SBC/Ameritech merger related requirements are not considered mandatedchanges and shall follow the CMP.

6.3 Training

All changes to existing interfaces, as well as the introduction of new interfaces, willbe incorporated into external CLEC training and SBC’s internal processes forupdating employees on changes to CLEC and its own retail systems. This includesupdating external CLEC training, and all parties’ best efforts to update internaltraining and applicable Methods and Procedures (M&P).

All parties agree that information regarding changes to the interfaces, as well asinformation regarding new interfaces, needs to be communicated and coordinatedwith end users and support personnel to ensure effective implementation.

6.4 Documentation Change

CLECs will be notified (via email Accessible Letter) of Changes that impact OSSrelated documentation (e.g., LSOR, LSPOR, User Guide, ESO User Guide, RSOG,etc.). The applicable documention on the SBC CLEC web site will be updated asdefined in the written notification.

6.5 CLEC Joint Testing

6.5.1 Existing Interfaces



For changes to existing interfaces, CLEC joint testing will be conducted for gatewayinterfaces and LEX.

Where applicable, SBC and CLECs will perform gateway interface testing asnegotiated by the parties and documented in a customized test plan. SBCmaintains a Joint Release Test Plan template on its CLEC web site that may beused in the development of the customized test plan. Each testing party will meetwith SBC and agree on its own set of test scenarios that will be included in the test,applicable entrance and exit criteria and a test schedule. Regression testing will besupported in limited scenarios as agreed upon in the documented test plan. Alimited number of test accounts will be made available during CLEC testing. Shouldthe parties not agree that a successful test was achieved within the specifiedinterval, either SBC or the CLEC may initiate an OIS, as described in Section 7.0.

If an OIS call is requested based on the results of joint CLEC testing, the call will beheld the Tuesday prior to the scheduled release. A Qualified CLEC, as defined inSection 7.4 of this document, must notify its SBC Account Manager in writing by12:00 PM Central Time on the Monday prior to the scheduled releaseimplementation.

6.5.2 New Interfaces

For new interfaces, CLEC joint testing will be conducted for gateway interfaces.For GUIs, CLECs may negotiate through their SBC Account Manager the ability topass a limited number of test transactions, over the GUI interface, after the interfaceis in production mode.

If an OIS call is requested based on the results of joint CLEC testing, the call will beheld the Tuesday prior to the scheduled release. A Qualified CLEC, as defined inSection 7.4 of this document, must notify its SBC Account Manager in writing by12:00 PM Central Time on the Monday prior to the scheduled releaseimplementation.

7.0 Outstanding Issue SolutionAs outlined above, the OIS process may be invoked as follows:

• Category One-Changes, Step 3.3.12

• Category One-New Interfaces, Step 4.2.14

• Category Two-Changes, Step 3.5.6

• Category-Two New Interfaces, Step 4.3.8

• Category One-Changes, Step 3.3.15

• Category One-New Interfaces, Step 4.2.17

• Retirement of Interfaces, Section 5.2.6

• Emergency Situations, Section 6.1.5



7.1 Process Initiation

The initiating CLEC will provide its SBC Account Manager with written notification(via fax, email, or regular mail) of the outstanding issue(s). This notice will includethe disputing party’s reason(s) for raising the dispute and any alternativerecommendations. The CLEC initiating an OIS shall provide a bridge number for theconference call with its initiation notice. In the event more than one CLEC initiatesan OIS, SBC shall coordinate with the initiating CLECs to determine which bridgenumber to use.

7.2 Issue Timeline

In accordance with the appropriate timelines as set out in the above sections of thisdocument, SBC will publish a summary of all CLEC dispute(s) which will includeSBC’s position on those disputes. As soon as reasonably practicable after SBC’sreceipt of the OIS initiation notices, but in no event later than one (1) business daybefore the call, SBC will notify the CLECs (via email Accessible Letter) that there isa dispute along with the date, time and bridge for the voting call. Depending on theoutcome of an OIS or open issue, CLECs and/or SBC may request a delay of theimplementation date.

All parties agree that it is in their mutual interest to expedite the deliverables that aredue during the OIS process. All CLECs, including those not qualified to vote in theOIS process, may participate on the OIS calls.

7.3 Dispute Vote

If the parties are unable to reach a solution, a dispute vote may be called by anyQualified CLEC. Discussion on the voting call may include:

§ a dialogue for the opposing views

§ impacts of a “No” vote on the remainder of the release or other connectedreleases (applies to changes to existing interfaces only)

§ discussion of options

The vote by Qualified CLECs during the call will resolve the question appropriate tothe change category (e.g., change to existing interface, introduction of new interfaceor retirement of interface) as follows:

7.3.1 Change to Existing Interfaces: Will SBC implement the disputed item asdefined by SBC at the end of the notice and comment period (published in the FinalRelease Requirements)? The allowed votes are “Yes,” “No” and “Abstain”.

7.3.2 New Interfaces: Will SBC implement the new interface as defined by SBC atthe end of the notice and comment period (published in the Final ReleaseRequirements)? The allowed votes are “Yes,” “No” and “Abstain”.

7.3.3 Retirement of Interfaces: Has SBC provided comparable functionality? Theallowed votes are “Yes,” “No” and “Abstain”.



In the event of a “yes” vote (allowing SBC to retire the interface in thetimeframe SBC defined), CLECs who have an interest in continuing to usethe retiring interface, beyond the retirement date, should initiate two-partynegotiations with SBC. These negotiations will include, but will not be limitedto, discussions of the ongoing costs of maintaining a customized interfaceand its ultimate obsolescence. The OIS process does not apply in thisinstance.

7.3.4 Post Implementation Emergency Situations: Should SBC begin backoutand recovery process?

7.4 Qualified CLECs

7.4.1 Final Release Requirements: If the OIS relates to Final ReleaseRequirements, Qualified CLECs must meet the following criteria to participate in adispute vote:

A. For New Interfaces

CLECs with a documented intent to implement the initial version of the newinterface within six months of SBC’s planned implementation are consideredqualified. Documented intent is further defined as:

• either a CLEC with a signed Interconnection Agreement (“ICA”), with animplementation schedule for the interface, or

• one with a ROU/Memorandum of Understanding (“MOU”), or

• one who is negotiating terms and conditions for access to the interface, subjectto acceptable substantiation and sanctioned by a majority vote of the otherQualified CLECs.

B. For Changes to Existing Interfaces

§ CLECs must be in production and be providing service to paying customers(i.e., customers other than employees and/or “friendlies”), or

§ CLECs with a documented intent (as described above) to implement theinterface within one (1) month of the scheduled release date, includingproviding service to paying customers (i.e., customers other than employeesand/or “friendlies”)

§ In the case of an OIS relating to Final Release Requirements, both LEX andEDI users meeting the above criteria are qualified to vote on LSOR changes.

7.4.2 Implementation of Gateway Release

If the OIS relates to implementation of a release, Qualified CLECs must meet thefollowing criteria to participate in a dispute vote:

§ CLECs must be in production and be providing service to payingcustomers (i.e., customers other than employees and/or “friendlies”)



§ CLECs with a documented intent (as described above) to implement theinterface within one (1) month of the scheduled release date, includingproviding service to paying customers (i.e., customers other thanemployees and/or “friendlies”).

§ If the OIS call is to discuss implementation of a versioned release, CLECmust be testing release requirements for the newest version.

§ Category Two users do not vote in an OIS relating to implementation of agateway release.

7.4.3 Post Implementation Emergency Situations

If the OIS relates to a post implementation emergency situation, Qualified CLECs,as defined in this section, must be on the release in question (and may be LEX orEDI users) to participate in a dispute vote.

7.4.4 Retirement of Interfaces

If the OIS relates to the retirement of an interface, Qualified CLECs must meet thefollowing criteria to participate in a dispute vote:

§ CLECs who are currently live production users of the retiring interface.

§ SBC is qualified to vote in OIS on retirement of interfaces.

7.5 Voting Process

If agreement can not be reached, any OIS shall be resolved by a dispute vote.

A 50% quorum of all Qualified CLECs (as defined above) is required for a disputevote to be held. If a quorum is established, a 51% vote of the quorum (i.e., a simplemajority vote) is required to change a release requirement, delay implementation ofan EDI release, backout of a release, or delay retirement of an interface. For OISon Final Release Requirements dealing with LSOR changes, if a 50% quorum is notestablished, the vote can still be held if a 50% quorum of Qualified CLECs utilizingEDI is established. In the event of a tie, or if no quorum is established, then SBCshall proceed to change, implement, or retire the interface as specified in the FinalRelease Requirements.

A Qualified CLEC may not give its vote (i.e., proxy) to another voting CLEC.However, a Qualified CLEC may designate its company representative as it seesfit, provided that it may not designate another CLEC to cast its vote. Anindependent designee may represent more than one voting CLEC.

A corporation, including all affiliates, is entitled to a single vote, unless thecorporation can convince a majority of other Qualified CLECs that it has alegitimate need or right for multiple votes.



8.0 Managing the Change Management Process8.1 Change Management Points of Contact (CMPOC)

SBC and each CLEC will designate primary and secondary Change ManagementPoints of Contact (CMPOC) for the regions in which it operates. The CMPOC willserve as the official designee for all matters regarding CMP, including submissionof CLEC Change Request forms (described in Appendix H) and notification ofcritical matters (e.g., OIS, sidebar meetings, etc.). This notification is outside theAccessible Letter notification process. The CLECs must provide the CMPOCs’names, telephone numbers, email addresses and fax numbers to its AccountManagers. SBC will create the CMPOC list and publish this list on SBC’s regionalCLEC web sites. It is SBC and the CLEC’s responsibility to maintain and updatethe information on the list.

8.2 Change Management Process Meetings

8.2.1 Scheduled meetings will be held at intervals (at a minimum of once a quarter)agreed upon by SBC and CLECs to review the CMP and discuss developmentplans. During these meetings, the parties will review the effectiveness of the CMPand agree upon any changes. During the CMP meetings, SBC will share with theCLECs a non-binding, 12-Month Development View, with scheduled release dates.Prior to the close of the meeting, the location of the next meeting will be announced.To facilitate access to CMP documentation, SBC will maintain CMP information onits CLEC web site. At a minimum, SBC’s CMP web page will contain:

§ Current version of the SBC Competitive Local Exchange Carrier (CLEC)Interface Change Management Process document

§ LSR-EDI Joint Release Test Plan Template

§ A log of CLEC Change Requests and status as specified in Section 8.3 of thisCMP

§ References and/or Links to requirements for upcoming releases

§ SBC’s exceptions to the EDI LSOG Mechanization Specifications

8.2.2 SBC will maintain and distribute at the CMP meetings an Action Item Logcontaining action items from previous meetings and status. Additionally, during theCMP meetings, SBC will review status of the CLEC Change Requests. Themeetings will include discussions of SBC’s Development View, as well as anyCLEC suggested development to the SBC OSS.

8.2.3 Minutes will be taken during the meetings by SBC. A draft version of theminutes will be distributed to meeting participants for comments or revisions.Revisions and comments will be incorporated into the final minutes. Comments or



revisions not incorporated will be noted in the Accessible Letter distributing theFinal Meeting Minutes4.

8.3 Change Request Process

CMPOCs (see above) may recommend interface changes for future considerationby submitting a Change Request Form to the SBC’s CMPOC and its AccountManager (as described in Appendix H). The process and a sample form areincluded as Appendix H. SBC will maintain a log of these requests and providestatus of each. SBC will publish this log on its regional CLEC web sites. In makinga decision whether to include a CLEC Change Request in requirements, SBC willconsider such factors as industry guidelines, feasibility, costs, user benefits andcost reduction.

8.4 Modifications to the CMP Document

As noted in the “Purpose” paragraph of this document, the parties intend for theCMP to be dynamic in nature. Proposed modifications to the CMP document shallbe originated by means of discussion at any of the regularly scheduled CMPmeetings (regional or 13-State). Proposed modifications brought up at any of theregional CMP meetings will be forwarded to the Drafting Team. The Drafting Teamwill evaluate and if appropriate, will forward the proposed modification to all regionalCMP meetings or the 13-State CMP meeting, as appropriate. After the DraftingTeam reviews the proposed modification, the CLEC community will be notified ofthe outcome at the next regional or 13-State CMP meetings, as appropriate. Ifthere is consensus, the proposed modification will be incorporated in the documentand distributed via Accessible Letter. Such communication will include both a “red-line” copy of the previous CMP document, and a clean version of the new CMPdocument. Moreover, within seven (7) calendar days of its formal distribution, acopy of the new CMP will be available on SBC’s CLEC web site.

8.4.1 The Drafting Team consists of representatives from CLECs and SBC whowill be responsible for managing the CMP document. The responsibilities of theDrafting Team are:

• On-going commitment

• Participation in 13-State CMP meetings/conference calls

• Reviewing changes/suggestions to CMP

• Process improvements

• Managing 13-State meeting schedule/logistics

• Drafting language and maintaining CMP document

4 Due to a regulatory requirement in Texas, the SWBT CMP meeting minutes will be filed with theTPUC within two weeks of the meeting.



• Managing new CMP business that may require updates to the CMP document

8.5 Enforcement of CMP

A standing agenda item at the regular CMP meetings will provide an opportunity forSBC and CLECs to assess the effectiveness of the CMP and the need for anyrevisions.

Both CLECs and SBC will use this opportunity to provide feedback of instances ofnon-compliance and commit to taking the appropriate action(s).

If after using the discussion opportunity of the CMP meetings, there is consensusthat the process is no longer working to the mutual benefit of all, the parties willschedule meetings to begin the re-engineering of the process. If there is noconsensus, individual parties may approach the appropriate regulatory body.

Both CLECs and SBC will work to resolve any issue brought before the CMP.However, this process does not limit any parties rights to seek remedies beforeregulatory or legal arena.

If parties believe that non-compliance has been blatant and that the proposedsolutions offered by the offending party(ies) is (are) unacceptable, both SBC andindividual CLECs are free to pursue available legal remedies.

9.0 New CMP Business

The following are current items on which the Drafting Team is working:

• Adding the billing applications/interfaces (not listed in Appendix A) to the CMP

• Adding the Electronic Bonding Interfaces (‘’EBI”) for Trouble Administration(application to application) to the CMP

• Adding the prioritization process of CLEC Change Requests to the CMP

Appendix A - Interface Matrix

Interface SWBT PB/NB SNET Ameritech

Interface Function & Type (See

Legend)

EDI X X X PO, O, GW

MSAP X PO, O, MR2, GW

EASE X PO, O, GUI-R

Starwriter X PO, O, GUI-R

CORBA X X PO, GW

DataGate X X PO, GW

Verigate X X PO, GUI

CCTools X PO, MR2, GUI-R

TCNet Preorder X PO,GUI

LEX X X O, GUI2

Order Status X X X O, GUI

POS X X O, GUI

E911 Gateway X O, GW

Listings Gateway X O, GW

W-SNAP X O, GUI-R

SORD X X O, GUI-R

PBSM X O, MR, GUI-R

3B X OTrouble Administration X X MR, GUI

Legend:PO = PreorderingO = Ordering/ProvisioningMR = Maintenance/RepairMR2 = Maintenance/Repair SNET onlyGW = Gateway InterfaceGUI = Graphical User InterfaceGUI-R = Retail Graphical User InterfaceGUI2 = GUI with Category 1 timeframe for LSR changes Revised 2/7/2000

EH Attachment 9.2-1

Appendix B - Interface Change Management Process

Timeline for Category One Changes to Existing Interfaces(Gateway)

3.3.1 3.3.3 3.3.5 3.3.7 3.3.9 3.3.11 3.3.13 3.3.14c 3.3.16Review Release SBC Final CLEC Revised/Confirmed Voting Testing Imple-Adopted Announcement Reviews Industry Response Release Conference Ends mentatinIndustry CLEC Guidelines 3.3.8 Due Requirements Call

Guidelines Responses On Web Walk-Through IssuedInitial

Requirementswith CLECs

3.3.2 3.3.4 3.3.6 3.3.8 3.3.10 3.3.12 3.3.15Preliminary CLEC SBC Release SBC Outstanding Failed Package Response Response Requirements Reviews Issues 3.3.14a&b Testing Compiled Due Due Issued CLEC Due Begin Resolution

Responses Testing

7 Days 7 Days 21 Days 21 Days 30 days

7 7 7 DaysDays Days

37 Days

120 Days Target (Minimum 110 Days / Maximum 130 Days)

Days shown are calendar days Revised 2/8/2000

EH Attachment 9.3-1

Appendix C - Interface Change Management Process

Timeline for Category Two Changes to Existing Interfaces(GUI)

3.5.2 3.5.4 3.5.6 3.5.9Release SBC Oustanding Implementation

Announcement Reviews Issues CLEC Due

Responses

3.5.3 3.5.5 3.5.7CLEC Rev./Conf. Voting

Response Require. Conf.Due Issued Call

4 Business Days 3 Business Days 2 2Business Business

Days Days

14 Days

21 - 24 Days

Days shown are calendar days (unless otherwise noted)

EH Attachment 9.4-1

Appendix D - Interface Change Management Process

Timeline for Introduction of New Category One Interfaces(Gateway)

4.2.1 4.2.3 & 4.2.4 4.2.7 4.2.9 4.2.11 4.2.13 4.2.15 4.2.16b 4.2.18Design & Release SBC SBC CLEC Revised/Confirmed Voting Testing Imple-

Development Announce. Reviews Reviews Response Release Conference Scheduled mentationMeeting CLEC Final Industry Due Requirements Call To End

Responses Guidelines Issued

4.2.2 4.2.5 4.2.8 4.2.10 4.2.12 4.2.14 4.2.17CLEC CLEC SBC Release SBC Oustanding Failed Resp. Response Response Requirements Reviews Issues 4.2.16a Testing Due Due Due Issued CLEC Due Testing Resolution

Responses Begins

4 Business Days 7 Days 7 Days 21 Days 21 Days 30 Days

7 7 7 DaysDays Days

37 Days Minimum

120 Days Target (Minimum 110 Days / Maximum 130 Days)

9 Months (approximately)

Days shown are calendar days

EH Attachment 9.5-1

Appendix E - Interface Change Management Process

Timeline for Introduction of New Category Two Interfaces(GUI)

4.3.1 4.3.3 & 4.3.4 4.3.6 4.3.8 4.3.12SBC Release SBC Outstanding Implementation

Provides Announcement Reviews IssuesDesign & CLEC Due

Devel. Info Responses

4.3.2 4.3.5 4.3.7 4.3.9CLEC CLEC Rev/Conf. VotingResp. Response Rel/Req. ConferenceDue Due Issued Call

2 4 3 2 2Bus. Bus. Bus. Bus. Bus.Days Days Days Days Days

8 Calendar Weeks (approximately)

EH Attachment 9.6-1

Appendix F - Interface Change Management Process

Timeline for Retirement of Existing Interfaces: Group AGroup B Category 1Group B Category 2

5.2.2 5.2.4Retirement SBC

Announcement ReviewsCLEC 5.2.8

Responses 5.2.6 Retirement Outstanding

5.2.3 5.2.5 IssuesCLEC Revised/Conf. Due

Response Retirement 5.2.7Due Issued Comparable Voting

Functionality Conference Exists Call

3021 Days 21 Days 7 Days Days

Group A - 6 Months

Group B Category 1- (6 Months)

Group B Category 2 - (6 Months)

Group A - 12 Months



Days shown are calendar days

EH Attachment 9.7-1

Appendix G – Matrix View of Timelines in Appendices B Through F

EH Attachment 9.8-1

CHANGES NEW RETIREMENT

ACTIVITY

Category One(Gateway)Changes to

ExistingInterfaces

(Section 3.3)

Category Two(GUI)

Changes toExisting GUI

Interfaces(Section 3.5)

Category One(Gateway)

New Interfaces(Section 4.2)

Category Two(GUI)


Group A andGroup BCategory 1 andCategory 2(Section 5.2)

Total Time Line At least 152 – 172Calendar Days

At least 21 – 24Calendar Days

Approximately 9month cycle

Approximately8 Weeks

12 – 24 MonthsDepending onGroup andCategory

Design andDevelopmentMeeting /Information

N/A N/AApproximately 9months fromImplementationDate

Approximately8 weeks fromImplementationDate

N/A

CLEC Responsesfrom Design &Development

N/A N/A 4 Business Daysafter the DesignandDevelopmentMeeting

2 BusinessDays after theDesign andDevelopmentinformation

N/A

Release / RetirementAnnouncement

Delivered viaAccessible Letter

At ChangeManagementMeetings as part ofDevelopment view

No set standardtime betweenCLEC Responsesand the ReleaseAnnouncementtime

N/A

12 – 24 Monthsfrom PlannedRetirement

CLEC Responses toReleaseAnnouncement

7 Calendar Daysafter ReleaseAnnouncement

N/A7 Calendar Daysafter ReleaseAnnouncement

N/A21 Calendar Daysafter RetirementAnnouncement

SBC Response toCLEC Comments

7 Calendar Daysafter CLECresponses

N/A7 Calendar Daysafter CLECresponses

N/ADuring 21 Daysbetween CLECResponses andRevisedRetirement PlanIssuance

SBC Review ofFinal IndustryStandards

No Set Timebetween SBCResponse toCLEC Commentsand InitialRequirements

N/A

No Set Timebetween SBCResponse toCLECComments andInitialRequirements

N/A N/A

InitialRequirements orRevised RetirementDoc (for RetiringInterfaces

Via accessibleletter 152 – 172calendar days fromimplementation

Via accessibleletter at least 21days before theplannedimplementation

Via accessibleletter 152 – 172calendar daysfromimplementation

Delivered Viaaccessible letter

21 Days afterCLEC Responsesare due

SBC Hold ReleaseWalk-Through (forCategory One –Gateway changes toexisting interfacesonly)

Second week ofCLEC commentcycle after releaseof InitialRequirements, butno later than threebusiness daysbefore the end ofcomment cycle.

N/A N/A N/A N/A

Appendix G – Matrix View of Timelines in Appendices B Through F

EH Attachment 9.8-2

CHANGES NEW RETIREMENT

ACTIVITY

Category One(Gateway)Changes to

ExistingInterfaces

(Section 3.3)

Category Two(GUI)

Changes toExisting GUI

Interfaces(Section 3.5)

Category One(Gateway)


Category Two(GUI)


Group A andGroup BCategory 1 andCategory 2(Section 5.2)

CLEC Comments onInitial RequirementsDue

21 Calendar Daysafter release ofInitialRequirements

4 Business Daysafter release ofInitialRequirements

21 Calendar Daysafter release ofInitialRequirements

4 BusinessDays afterrelease of InitialRequirements

N/A

Final ReleaseRequirements/ComparableFunctionality existsfor retiringinterfaces

21 Calendar Daysafter CLECresponses arereceived by SBC

3 Business Daysafter CLECresponses arereceived by SBC

21 Calendar Daysafter CLECresponses arereceived by SBC

3 BusinessDays afterCLECresponses arereceived bySBC

All Groups andCategories - 6months before thedate of retirement

Start of Target toImplementationCountdown

Start of 110 – 130Day PeriodAt the same timethe Final ReleaseRequirements areDistributed

Start of 14 DayPeriodAt the same timethe Final ReleaseRequirements areDistributed

Start of 110 –130 Day PeriodAt the same timethe Final ReleaseRequirements areDistributed

N/A N/A

OIS Issues Due (Ifnecessary)

7 Calendar Daysafter Final ReleaseRequirements

2 Business Daysafter Final ReleaseRequirements

7 Calendar Daysafter FinalReleaseRequirements

2 BusinessDays afterFinal ReleaseRequirements

30 Days beforethe planned dateof retirement

OIS VotingConference Call (Ifnecessary)

7 Calendar Daysafter OIS Issuesare Due

2 Business Daysafter OIS Issuesare Due

7 Calendar Daysafter OIS Issuesare Due

2 BusinessDays after OISIssues are Due

7 Days after theOIS Issues aredue

Begin Testing 37 Calendar DaysbeforeImplementationTarget Date

N/A37 Calendar DaysbeforeImplementationTarget Date

N/A N/A

Testing Ends – DeadWeek begins

30 Calendar Daysafter TestingBegins or 7 DaysbeforeImplementationTarget Date

N/A

30 Calendar Daysafter TestingBegins or 7 DaysbeforeImplementationTarget Date

N/A N/A

OIS period ifnecessary as a Resultof Testing

If necessary, in the7 Day windowbeforeImplementation ofthe Release

N/AIf necessary, inthe 7 Day windowbeforeImplementationof the Release

N/A N/A

Implementation ofthe Release orRetirement of theSystem

7 Calendar DaysAfter end ofTesting or at least152 – 172 daysafter releaseannouncement

14 Calendar DaysAfter FinalRequirements aredistributed

7 Calendar DaysAfter end ofTesting orapproximately 9months fromoriginal DesignandDevelopmentMeeting

8 CalendarWeeks fromwhen SBCProvidesDesign andDevelopmentInformation

Group A – 12months from theRetirementAnnouncementGroup B – Category1 -- 24 monthsfrom the RetirementAnnouncementGroup B – Category2 -- 12 monthsfrom the RetirementAnnouncement

Draft 13-State CMP 02/11/200 VersionEH Attachment 9.9-1

Appendix HSBC Change Management Process (CMP)

CLEC Change Request (CCR) Process

Change Management Process (CMP)CLEC Change Request (CCR) Process


I. Overview

The purpose of this attachment is to overview SBCs process to receive CLEC Change Requests(CCR). This process identifies how SBC will receive and report the status of CCRs. CCRs are usedto request changes to those OSSs, as well as LSOR business rules, included in the SBC/CLEC ChangeManagement Process (CMP). These change requests fall into the following primary categories:

• New Functionality/Process• Change to Existing Functionality/Process

SBCs OSSs fall into the following categories:

• Pre-Order• Ordering• Maintenance• Billing• LSOR/LSR Business Rules• Other

CCRs are submitted by the CLEC CMPOC to SBCs CMPOC and Account Manager, and thenreviewed to determine the appropriate system and SME. SBC will maintain a log of these requests andprovide status of each. SBC will publish this log on its regional CLEC web sites. Status of CCRs willbe updated on SBC's regional CLEC web sites. If approved, the requested change is targeted to arelease. Notification of this change will be handled through the agreed upon Change ManagementProcess. If not approved, notification will be sent to the CMPOC and updated on SBC’s regionalCLEC web sites.

II. Initiator

CCRs will only be submitted by CMPOCs of Qualified CLECs as defined below.

• either a CLEC with a signed Interconnection Agreement (“ICA”), with an implementation schedulefor the interface, or

• one with a ROU/Memorandum of Understanding (“MOU”) for the interface, or

• one who is negotiating terms and conditions for access to the interface, subject to acceptablesubstantiation and sanctioned by a majority vote of the other Qualified CLECs,

and

• CLECs must be in production and be providing service to paying customers (i.e., customers otherthan employees and/or “friendlies”) on the interface, or



• CLECs with a documented intent (as described above) to implement the interface within one (1)month of the scheduled release date, including providing service to paying customers (i.e.,customers other than employees and/or “friendlies”)

III. The Change Request (CR) Form

Each requested change is initiated by a CCR. See Attachment 1 for the CCR form and fielddescriptions.

IV. The CCR Process

1. The CLEC CMPOC submits a CCR form to SBC’s CMPOC and its Account Manager.• Only the designated CLEC CMPOC can initiate a CCR.• If a CCR is received from someone other than the designated CMPOC, the CCR will

be returned requesting that the CCR must be submitted by the CMPOC.

2. The SBC CMPOC notifies the designated CLEC CMPOC (via email or fax) of its receipt of theCCR.

• This notice informs the CMPOC that the request has been received and the assignedtracking number.

• This notice will be sent five business days from the receipt of the CCR.

3. SBC CMP Internal Team reviews the CCR• The SBC CMP Internal Team will review the CCR for validity.• If clarification is needed, the SBC CMP Internal Team will direct all questions to the

designated CLEC CMPOC.• If the CCR is determined to be a valid request, a pending status will be assigned to

the CCR and it is sent to the appropriate SBC Internal SME for evaluation.• SBC publishes the CCR on its regional CLEC web sites within 14 calendar days of

receipt of the CCR.• If the CCR is determined not to be a valid request, a not approved status will be sent

to the designated CLEC CMPOC through the SBC CMPOC.

4. The SBC Internal SME evaluates the CCR.• The SBC Internal SME will evaluate the CCR using the following considerations:

• Industry guidelines• Technical feasibility• OSS direction• Financial feasibility

5. CCR evaluation results



• If it is determined that the CCR can be implemented, the CCR is scheduled to a particularrelease.

• If it is determined that it cannot be implemented, a “not approved” status will be sent to thedesignated CLEC CMPOC through the SBC CMPOC.

• The standard interval to approve or deny the CCR is 30 days from the date of receipt of theCCR. If SBC determines that additional time for analysis is required, SBC will notify the CLECCMPOC and advise of target date for decision. CLEC CMPOC may escalate the issuethrough the Account Team if necessary.

6. Notification of implementation of approved CCRs.• If the CCR has been approved, SBC will provide a target implementation date and will follow

the agreed upon CMP.

V. Reporting

The SBC CMP Internal Team is responsible for providing accurate and timely information to CLECsregarding CCRs. All CCRs will be shared with the CLEC community via SBC’s regional web sites.The CLEC will be identified as the originator of the request, unless the CCR is marked Semi-Private/Proprietary.

The following information will be maintained for each CCR on the SBC’s regional web sites:

• CCR Tracking Number• Originating CLEC (Region)• CLEC Primary Contact Name• Applicable Interface (Region)• Verbatim Description of the change• Status• Date Received• Decision Date• Committed Response Date

CLECs can provide comments on all CCRs through the Account Manager or SBC’s CMPOCClosed CCR’s will be archived on the web.

See Attachment 2 for the summary sheet.


Attachment 1EH Attachment 9.9-5

Attachment 1



CCR Form Definitions1. CLEC (company name) initiating the change request.2. Name of Account Manager assigned to the CLEC issuing the change request.3. Click on (mark an “x” in) the appropriate box(es) in which the CLEC is operating.4. Date the CCR is sent to the SBC Change Management Point of Contact (SBC

CMPOC).5. Click on (mark an “x” in) the appropriate box indicating if the CCR is being sent through

email, fax, TCNet, or other (e.g., paper, mail) medium.6. Name of Primary CLEC Change Management Point of Contact (CLEC CMPOC) for

the CLEC issuing the change request.7. Telephone Number of the CLEC CMPOC.8. Address and Room Location of the CLEC CMPOC.9. Email Address of the CLEC CMPOC.10. Fax number of the CLEC CMPOC.11. Click on (mark an “x” in) the appropriate box indicating if the CLEC would like the CCR

shared with other CLECs without identifying the originating CLEC, or including theidentity of the originating CLEC. All CCRs are shared with other CLECs.

12. Click on (mark an “x” in) the appropriate box indicating if the requested change is a newfunctionality or process, change to the existing functionality or process, and/or if therequested change is being finalized at the Industry level. Please fill out thecorresponding Issue number of the committee currently reviewing the Issue. If thechange has been included in an LSOG Version # and EDI release #, please providethat information.

13. Click on (mark an “x” in) the appropriate box indicating if the CLEC is requesting thechange with a high, medium, or low priority.

14. Click on (mark an “x” in) the appropriate box corresponding Pre-Order application forwhich this change is requested.

15. Click on (mark an “x” in) the appropriate box corresponding Ordering application forwhich this change is requested.

16. Click on (mark an “x” in) the appropriate box corresponding Repair & Maintenanceapplication for which this change is requested.

17. Click on (mark an “x” in) the appropriate box corresponding Billing application for whichthis change is requested.

18. Click on (mark an “x” in) the box if the requested change affects LSOR/LSR BusinessRules, and indicate the LSR form name, field name, and number to the correspondingLSOR/LSR Business Rule for which this change is requested.

19. Click on (mark an “x” in) the box if the requested change affects “Other” categories, andindicate the information for which this change is requested.

20. Include a detailed description of the requested change. Some items to include wouldbe the function within the specific interface or process. Other items to include would bethe LSR form name and field name and number within the specified form. If the priorityhas been deemed high, please provide the detail and reasoning to qualify this requestas a high priority. Please note: this verbatim description will be included on theChange Request Log, which will be posted on the CLEC web site.

CMP - CLEC CHANGE REQUEST (CCR) FORMOSS ELECTRONIC INTERFACE and ASSOCIATED BUSINESS RULES/PROCESSES

EMAIL TO: Chris Hines – at [email protected] SEND CC: TO Ameritech, NB, PB, SNET, or SWBT ACCOUNTMANAGER


CLEC COMPANY/NAME:

(1)

SBC ACCOUNT MANAGER:

(2)

CLEC OPERATING AREA Ameritech Nevada Bell

Pacific Bell (3) SNET SWBT

CCR SUBMITTED:

DATE:______(4)__________

VIA EMAIL

VIA FAX (5) VIA TCNET VIA OTHER

PRIMARY CLEC CHANGE MANAGEMENT POINT OF CONTACT (CMPOC) INFORMATION (Contact for additional details/questions or to whom response will be made)

NAME:

(6)TELEPHONE NO.:

(7)ADDRESS/LOCATION:

(8)EMAIL:

(9)FAX:

(10)

PROPRIETARY STATUS(CMPOC may indicate the degree to which CLEC wishes to share its CCR with other CLECs)

SEMI-PRIVATE/PROPRIETARY – SHARE WITHOUT CLEC IDENTIFICATION (11) NON-PROPRIETARY – SHARE NON-RESTRICTED

TYPE OF CHANGE: (12) NEW FUNCTIONALITY/PROCESS CHANGE TO EXISTING FUNCTION/PROCESS INDUSTRY STATUS:

Issue # OBF Initial Closure Issue # SOSC Review Issue # OBF Final Closure LSOG # EDI Release

PRIORITY REQUESTED: HIGH (Critical) MEDIUM

LOW (As resources permit) (13)

OSS FUNCTIONS CATEGORY & SPECIFIC INTERFACE/PROCESS IMPACTED (check appropriate box)

PRE-ORDER

(14)ORDERING

(15)REPAIR &

MAINTENANCE

(16)

BILLING

(17)LSOR/ LSR

BUSINESS RULES

(18)

OTHER

(19)

EDI Verigate DataGate CORBA CCTools MSAP TCNet

CEASE BEASE LEX EDI PBSM POS SORD

E911 Listings Starwriter Order Status W-SNAP MSAP 3B

Trouble Admin. PBSM CCTools MSAP

Bill Info

DETAILED DESCRIPTION OF REQUESTED CHANGE (Verbatim Description will be added to the Change Request Log on the web site)(If Priority = High, provide detail sufficient to qualify CCR as critical)

(20)

SBC USE ONLY:

INITIAL PROCESSING CCR TRACKING NUMBER REQUEST STATUS COMMENTS




DateReceived:

DateAcknowledged:

PENDING (Under review) APPROVED DEFERRED NOT APPROVED

CLEC COMPANY/NAME:

SBC ACCOUNT MANAGER:

CLEC OPERATING AREA Ameritech Nevada Bell Pacific Bell SNET SWBT

CCR SUBMITTED:

DATE:________________ VIA EMAIL VIA FAX VIA TCNET VIA OTHER

PRIMARY CLEC CHANGE MANAGEMENT POINT OF CONTACT (CMPOC) INFORMATION (Contact for additional details/questions or to whom response will be made)

NAME: TELEPHONE NO.: ADDRESS/LOCATION: EMAIL: FAX:

PROPRIETARY STATUS(CMPOC may indicate the degree to which CLEC wishes to share its CCR with other CLECs)

SEMI-PRIVATE/PROPRIETARY – SHARE WITHOUT CLEC IDENTIFICATION NON-PROPRIETARY – SHARE NON-RESTRICTED

TYPE OF CHANGE: NEW FUNCTIONALITY/PROCESS CHANGE TO EXISTING FUNCTION/PROCESS INDUSTRY STATUS:

Issue # OBF Initial Closure Issue # SOSC Review Issue # OBF Final Closure LSOG # EDI Release

PRIORITY REQUESTED: HIGH (Critical) MEDIUM LOW (As resources permit)

OSS FUNCTIONS CATEGORY & SPECIFIC INTERFACE/PROCESS IMPACTED (check appropriate box)

PRE-ORDER ORDERING REPAIR &MAINTENANCE

BILLING LSOR/ LSRBUSINESS RULES

OTHER

EDI Verigate DataGate CORBA CCTools MSAP TCNet

CEASE BEASE LEX EDI PBSM POS SORD

E911 Listings Starwriter Order Status W-SNAP MSAP 3B

Trouble Admin. PBSM CCTools MSAP

Bill Info

DETAILED DESCRIPTION OF REQUESTED CHANGE (Verbatim Description will be added to the Change Request Log on the web site)(If Priority = High, provide detail sufficient to qualify CCR as critical)

SBC USE ONLY:




INITIAL PROCESSING CCR TRACKING NUMBER REQUEST STATUS COMMENTSDate

Received:Date

Acknowledged: PENDING (Under review) APPROVED DEFERRED NOT APPROVED



Attachment 2

CMP - CLEC CHANGE REQUEST (CCR) SUMMARYOSS ELECTRONIC INTERFACE and ASSOCIATED BUSINESS RULES/PROCESSES


CCRTrackingNumber

OriginatingCLEC

(Region)

CLEC PrimaryContact Name

InterfaceAffecting(Region)

Verbatim Description Status DateReceived

DecisionDate

CommittedResponse

Date

EH Attachment 9.10

APPENDIX I

SBC 13-State Change Management Process Transition Plan

ITEM SWBT PB/NB Ameritech SNET

OSS Accessible Letters Already in place Already in place 4/1/00 Already in place

Category 1 ChangeProcessNotifications &CLEC Testing

Already in place Already in place LSOG 4 Release First MSAP release afterJuly, 2000

Versioning (dot releases) Release scheduled for7/2000

Release scheduled for7/2000

LSOG 4 Release Implementation ofcommon EDI platform

Category 2 ChangeProcess

Already in place Already in place 4/1/00 Already in place

Exception Process• For interim releases

Already in placeAlready in place

Already in placeAlready in place

LSOG 4 Release4/1/00

First MSAP Release afterJuly, 2000

Outstanding Issue Solution Already in place Already in place LSOG 4 Release First MSAP Release afterJuly, 2000

All other sections of 13-State CMP

4/1/00 4/1/00 4/1/00 4/1/00

Documents

HAM AFFIDAVIT Attachment 9