HAM AFFIDAVIT Attachment 6 - att.com AFFIDAVIT Attachment 6. EH Attachment 6-1 Accessible “Invitation to Discussion of SBC/Ameritech 13-State Change Management Process

HAM AFFIDAVITAttachment 6

EH Attachment 6-1

Accessible

“Invitation to Discussion of SBC/Ameritech 13-State Change Management Process –California”

Date: November 1, 1999

Number: CLECC99-350

Contact: Pacific Bell Account Manager

In our continuing negotiations efforts with interested CLECs in compliance with theSBC/Ameritech merger conditions (Paragraph 32), SBC/Ameritech will host a meeting forCLECs in all SBC regions for the purpose of initiating a discussion on the negotiation of a uniformChange Management Process to be implemented in the 13-state area.

Logistics for the meeting are:

Date: November 17th, 1999

Location: Sauganash Ball Room, 14th Floor Holiday Inn, Mart Plaza

350 North Orleans Chicago, Illinois

Time: 9:00 am to 5:00 PM CST

ConferenceBridge: 800.406.7410 Passcode: 648189#

Attached to this letter are:• CLEC Change Management Process for Ameritech• Draft of 8-State SBC Competitive Local Exchange Carrier (CLEC) Interface Change

Management Process.

Please review these documents prior to the meeting. The two processes will be reviewed andcompared at a high level in order to familiarize participants with the two documents.

EH Attachment 6-2

SBC/Ameritech is proposing that a “Core Drafting Team” be formed with volunteers frominterested CLECs and SBC, for the purpose of coming up with a single document. This 3-daysession has been tentatively scheduled for November 30th through December 2nd in San Ramon,California. For optimum success, participation on the Core Drafting Team should be limited innumber in order to have productive working sessions. The result of the Drafting Team’s effortswill be presented to all CLECs in the 13-State area for comment and approval. This process wasvery successful in the creation of the SBC 8-State Change Management Process document.Further discussion and request for participation will occur as part of this meeting.

An agenda for this session is forthcoming. I f you would like to have discussions regarding thismeeting or on the two attached Change Management Process documents prior to November 17th,please contact your Account Manager.

Attachments

File: SBC 8State CMP_101199.docFile: AppA-SBC 8State CMP_101199.xlsFile: AppB-SBC 8State CMP_101199.xlsFile: AppC-SBC 8State CMP_101199.xlsFile: AppD-SBC 8State CMP_101199.xlsFile: AppE-SBC 8State CMP_101199.xlsFile: AppF-SBC 8State CMP_101199.xlsFile: AppG-SBC 8State CMP_101199.doc

Ameritech Change Management Document

[See EH Attachments 6.1-6.9]

10/11/1999 Version

EH Attachment 6.1-1

SBC

Competitive Local ExchangeCarrier (CLEC)

Interface

Change Management

Process

10/11/1999 Version

EH Attachment 6.1-2

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

Table of Contents

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

1.0 Purpose .................................................................................................................... 4

2.0 Scope........................................................................................................................ 4

3.0 Changes to Existing Interfaces............................................................................... 4

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

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

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

3.4 Versioning of Gateway Releases… ............................................................ …8

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

4.0 Introduction of New Interfaces...............................................................................10

4.1 Two Categories of New Interfaces.................................................................10

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

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

5.0 Retirement of Existing Interfaces .........................................................................14

5.1 Retirement Groups ..........................................................................................14

5.2 Interface Retirement Process.........................................................................14

10/11/1999 Version

EH Attachment 6.1-3

6.0 Other Items .............................................................................................................15

6.1 Emergency Situations .....................................................................................15

6.2 Exceptions........................................................................................................16

6.3 Training .............................................................................................................17

6.4 CLEC Joint Testing .........................................................................................17

7.0 Outstanding Issue Solution...................................................................................18

7.1 Process Initiation. ............................................................................................18

7.2 Issue Timeline. .................................................................................................18

7.3 Dispute Vote. ...................................................................................................18

7.4 Qualified CLECs..............................................................................................19

7.5 Voting Process. ...............................................................................................20

8.0 Managing the Change Management Process....................................................21

8.1 Change Request Process……………… .....................…………………….22

8.2 Enforcement .....................................................................................................22

Appendix A - SBC Interface Matrix

Appendix B - Timeline for Category One Changes to Existing Interfaces

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 - CLEC Change Request Process

10/11/1999

EH Attachment 6.1-4

4

1.0 PurposeThis documents the Change Management Process (“CMP”) by which SBCCommunications (herein after referred to as “SBC”, consisting of Nevada Bell,Pacific Bell, Southwestern Bell Telephone, and Southern New England Telephone)will notify Competitive Local Exchange Carriers (“CLECs”) of changes to theOperational Support Systems (“OSS”) interfaces, introduction of new interfaces andretirement of interfaces detailed below and provides for the identification andresolution of CLEC issues associated with the CMP. The parties intend for theCMP to be dynamic in nature, managed through regularly scheduled meetings (at aminimum of once a quarter) and based on group consensus. Any agreed-uponmodifications to the process will be included in this document.

2.0 ScopeThis 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. Notwithstanding theforegoing, this process does not pertain to Electronic Bonding Interfaces (“EBI”).The parties may discuss expansion of this process to billing processes, and non-end user ordering functions during the scheduled meetings, and will later addressmanual processes.

This document applies to SBC and all CLECs operating in Arkansas, California,Connecticut, Kansas, Missouri, Nevada, Oklahoma, and Texas.

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

10/11/1999

EH Attachment 6.1-5

5

• 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.

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 presume 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.1).

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”.

10/11/1999

EH Attachment 6.1-6

6

3.3.2 Regardless of the change driver, SBC will prepare a preliminary package ofthe required issue changes and share these plans at a scheduled ChangeManagement meeting nine (9) to twelve (12) months in advance of the targetimplementation date. SBC will share its plans as part of its 12-Month DevelopmentView (see Managing the 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. TheCLEC 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.

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 development

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 point(s) of contact designated by the CLEC. It is each CLEC’s responsibility toensure that SBC has a current contact list.

10/11/1999

EH Attachment 6.1-7

7

efforts. Generally, SBC’s planned implementation will fall within 152 to 172calendar days from the date of the Initial Release Requirements.

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.

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.

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 ofthis document.

3.3.14 If no Final Release Requirements OIS is initiated (or after successfulconclusion of any such OIS), testing will be conducted by SBC and any interestedCLEC until the agreed upon testing exit criteria have been satisfied, in accordancewith a negotiated joint test plan, to the mutual satisfaction 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.

10/11/1999

EH Attachment 6.1-8

8

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.

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 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 SBC will support two versions of software for its EDI Ordering andEDI/CORBA Pre-Ordering interfaces. Those versions will be the current andprevious versions, whether the previous is a basic EDI/LSOG version or a SBCupgraded EDI/LSOG version (a dot release). SBC will version the latest tworeleases beginning with the first release in 2000.

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. If the next release is LSOGB.1, at release time, SBC wouldsunset LSOGA and will maintain LSOGB and LSOGB.1. Thus, two consecutiveversions of software (including dot releases) for SBC's EDI Ordering andEDI/CORBA Pre-Ordering interfaces would 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 release, SBC will no longer support the oldestversion. SBC will maintain two versions, as described above, even if suchversioning departs from final guidelines adopted by OBF.

3.4.4 SBC’s DataGate Pre-Ordering interface utilizes similar versioning techniques.SBC will support two versions of software, the current version and the immediatepast version. SBC will version the latest two releases beginning with the firstrelease of 2000. SBC’s release announcement of a new version will constitutenotification of sunset for the oldest version. Upon implementation of the release,SBC will no longer support the oldest version.

10/11/1999

EH Attachment 6.1-9

9

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). 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.3SBC will provide written answers to CLEC questions via email Accessible Letter.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.

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 of this document.

10/11/1999

EH Attachment 6.1-10

10

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.

3.5.10 The OIS process is not available for SBC’s retail systems, as specified inSection 7 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 Release

10/11/1999


11

Announcement. 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,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.

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

10/11/1999


12

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.

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 ofthis document.

4.2.16 If no Final Release Requirements OIS for a new Gateway Interface isinitiated (or after successful conclusion of any OIS), testing will be conducted bySBC and any interested CLEC, 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) Testing must be scheduled to end at least seven (7) calendar days prior tothe scheduled implementation date, unless otherwise agreed between SBCand 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 OISprocess related to New Interface Gateway Implementation, using the eligibilityrequirements and timeline defined in Section 7 of this document.

10/11/1999


13

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 summaryof the changes from Step 4.3.4 above, indication of type of change, (i.e.,

10/11/1999


14

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.

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 of thisdocument.

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

4.3.11 CLECs may negotiate through their SBC Account Manager the ability topass a limited number of test transactions. This would only be available after theinterface is in a production mode and at the CLEC’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.

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, wherethe replacement functionality resides or where it will exist in production at least six

10/11/1999


15

months 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, the CLEC must send a written notice (via email, fax or regular mail) to itsSBC Account Manager, which must be received at least 30 calendar days prior tothe scheduled retirement date.

10/11/1999


16

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 Emergency releases or emergency implementation date changes will behandled as special cases.

6.1.2 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.3 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 need not be in the form of an Accessible Letter, and may besent via other expedited means (e.g., broadcast fax).

6.1.4 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 throughescalation and may be brought before the appropriate regulatory body.

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) RequirementsException Accessible Letter, which indicates that it seeks an exception following theconclusion of a reply and comment cycle.

6.2.2 In CLEC responses, due within the applicable timeframe documented in theprocess, CLECs will raise questions and issues. Qualified CLECs will indicateobjections to handling the change, new interface or retirement as an exception.Lack of a response indicates no objection.

10/11/1999


17

6.2.3 SBC may proceed to implement the change, new interface or retirement on anexception basis only if there are no outstanding issues, or CLEC objections at theend 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 the mandated timeframes, will not besubject to the objection process for exceptions. In the Accessible Letter notification,SBC will provide any modified timelines for the change. If no such timeframe isspecified, regulatory mandated change shall be subject to the CMP process asdescribed in this document.

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 CLEC Joint Testing

6.4.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. 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.

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 must notify itsSBC Account Manager in writing by 12:00 PM Central Time on the Monday prior tothe scheduled release implementation.

6.4.2 New Interfaces

10/11/1999


18

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 must notify itsSBC Account Manager in writing by 12:00 PM Central Time on the Monday prior tothe scheduled release implementation.

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

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.

All parties agree that it is in their mutual interest to expedite the deliverables that aredue during the OIS process.

7.3 Dispute Vote

10/11/1999


19

If the parties are unable to reach a solution, a dispute vote may be called by aquorum of Qualified CLECs. 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.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

10/11/1999


20

• 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”).

§ 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 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.

All CLECs, including those not qualified to vote, may participate on the OIS calls.

7.5 Voting Process

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

10/11/1999


21

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, or delay retirement of an interface. For OIS on Final ReleaseRequirements dealing with LSOR changes, if a 50% quorum is not established, thevote can still be held if a 50% quorum of Qualified CLECs utilizing EDI isestablished. In the event of a tie, or if no quorum is established, then SBC shallproceed 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 ProcessScheduled 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.1 of thisCMP

§ References and/or Links to requirements for upcoming releases

§ SBC’s exceptions to the EDI LSOG Mechanization Specifications

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. Minutes will be taken during the

10/11/1999


22

meetings. A draft version of the minutes will be distributed to meeting participantsfor comments or revisions. Revisions and comments will be incorporated into thefinal minutes. Comments or revisions not incorporated will be noted in theAccessible Letter distributing the Final Meeting Minutes.

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 the regularly scheduled CMP meetings.Any modification agreed upon by group consensus at the CMP meetings will bedocumented in the Final Meeting Minutes, and then given to a designated draftingteam in order to develop final language. The drafting team will bring proposed finallanguage back to the next CMP meeting for overall approval. Once approved by theparticipants in the CMP meeting, modifications to the CMP document will bedocumented in the Final Meeting Minutes and then distributed to all participantsinvited to the CMP meetings, as well as the appropriate regulatory agencies. Suchcommunication will include both a “red-line” copy of the previous CMP document,and a clean version of the new CMP document. Moreover, within seven (7)calendar days of its formal distribution, a copy of the new CMP will be available onSBC’s CLEC web site.

8.1 Change Request Process

CLECs may recommend interface changes for future consideration by submitting aChange Request Form to their SBC Account Manager. The process and a sampleform are included as Appendix G. SBC will maintain a log of these requests andprovide status of each. In making a decision whether to include a CLEC ChangeRequest in requirements, SBC will consider such factors as feasibility, costs, userbenefits and cost reduction.

8.2 Enforcement

A standing agenda item at the CMP meeting will provide an opportunity for SBCand CLECs to assess the effectiveness of the CMP and the need for any revisions.

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 aftergiving notice of its intent to do so at a CMP meeting. The party will also describethe action it intends to take and the reason(s) for its proposed actions.

10/11/1999


23

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.

Appendix ASBC Eight-StateInterface Matrix

Interface SWBT PB/NB SNETInterface Function & Type

(See Legend)EDI X X X PO, O, MR2, GWCORBA X X PO, GWDataGate X X PO, GWVerigate X X PO, GUICCTools X PO, O, MR2, GUI-RRMI X O, GW2LEX X X O, GUI2Order Status X X O, GUI POS X X O, GUICESAR ISR X O, GUI3E911 Gateway X O, GWListings Gateway X O, GWEASE X PO, O, GUI-RStarwriter X PO, O, GUI-RW-CIWIN X PO, O, GUI-RSORD X X O, GUI-RPBSM X O, MR, GUI-RTrouble Administration 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 changesGW2 = Grandfathered Gateway InterfaceGUI3 = Grandfathered GUI

EH Attachment 6.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 Due Requirements Call

Guidelines Responses On Web Issued

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 Oustanding 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

EH Attachment 6.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 6.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)


EH Attachment 6.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 6.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




EH Attachment 6.7-1

EH Attachment 6.8-1

Appendix GSBC Change Management Process (CMP)

CLEC Change Request (CCR) Process3/31/99

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

EH Attachment 6.8-2

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 received by SBCs Internal Change Management team and then reviewed to determine theappropriate system and SME. Status of CCRs will be given in a monthly summary to be posted onSBC's CLEC website. If approved, the requested change is targeted to a release. Notification of thischange will be handled through the agreed upon Change Management Process. If not approved,notification will be sent to the CLEC and updated in the monthly summary.

II. Audience

CCRs will come only from those CLECs who have signed an OSS agreement. Each CLEC will have adesignated initiator or SME contact name who is to send the CCR and be the primary contact for anyquestions.

III. The Change Request (CR) Form

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


EH Attachment 6.8-3

IV. The CCR Process

Step 1. The CLEC Primary Contact initiates a CCR.• Only the designated CLEC Primary Contact can initiate a CCR.• If a CCR is received from someone other than the designated CLEC Primary

Contact, then the CCR will be returned to the originator stating that this needs tocome through the designated CLEC Primary Contact.

Step 2. The SBC CMP Internal Team notifies the designated CLEC Primary Contact of receipt ofthe CCR.

• This notice informs the CLEC that the request has been received and has beenassigned a tracking number. The tracking number will be given to the CLEC with thisnotice.

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

Step 3. The 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 Primary Contact.• 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.• If the CCR is determined not to be a valid request, a not approved status will be sent

to the designated CLEC Primary Contact through the SBC CMP Internal Team.

Step 4. The SBC Internal SME evaluates the CCR.• The SBC Internal SME will evaluate the CCR to determine:

1. If the CCR is technically feasible and it lines up with the direction for thatparticular OSS.

2. The time and cost of the request, if the CCR is technically feasible.3. If and when the CCR can fit into the interface's schedule.

• If the CCR is determined that it can be implemented, then the CCR is scheduled to aparticular release.

• If the CCR is determined to be that it cannot be implemented, a not approved statuswill be sent to the designated CLEC Primary Contact through the SBC CMP InternalTeam.

Step 5. Notification of implementation of approved CCRs.• If the CCR has been approved and scheduled to a release, notification of

implementation will follow the agreed upon CMP.


EH Attachment 6.8-4

V. Reporting

The SBC CMP Internal Team is responsible for providing accurate and timely reports to CLECs aboutCCRs. A summary sheet of all active CCRs will be sent to the CLECs on a monthly basis. All CCRswill be shared with the CLEC community. The CLEC will be identified as the originator of the request,unless the CCR is marked Semi-Private/Proprietary.

The Monthly Summary Sheet will contain the following information:• CCR Tracking Number• Originating CLEC• Interface Affecting• Description• Status• Date Received

CLECs can provide replies or input into all CCRs. These replies are to be sent to the SBC CMPInternal Team Single Point of Contact (SPOC) 1 week after distribution of the monthly summary sheet.

See Attachment 2 for the monthly summary sheet.


Attachment 1EH Attachment 6.8-5

Attachment 1



CCR Form Definitions

1. CLEC (company name) initiating the change request.2. Name of Account Manager assigned to the CLEC issuing the change request.3. Date the CCR is sent to the SBC Internal Change Management Team.4. Place an ‘x’ here if the CCR is being sent through an email medium.5. Place an ‘x’ here if the CCR is being sent through a fax medium.6. Place an ‘x’ here if the CCR is being sent through any other medium (i.e. paper, mail).7. Name of Primary SME Contact for the CLEC issuing the change request.8. Telephone Number of the CLEC Primary SME Contact.9. Address and Room Location of the CLEC Primary SME Contact.10. Fax number of the CLEC Primary SME Contact.11. Email Address of the CLEC Primary SME Contact.12. Place an 'x' here if the CLEC would like the CCR shared with other CLECs without identifying the originating

CLEC. All CCRs are shared with other CLECs.13. Place an 'x' here if the CLEC would like the CCR shared with other CLECs, including the identity the

originating CLEC. All CCRs are shared with other CLECs.14. Place an 'x' here if the requested change is a new functionality or process.15. Place an 'x' here if the requested change is a change to the existing functionality or process16. Place an 'x' in the corresponding box if the requested change is being finalized at the Industry level. Please fill

out the corresponding Issue number of the committee currently reviewing the Issue. If the change has beenincluded in an LSOG Version # and EDI release #, please provide that information.

17. Place an 'x' here if the CLEC is operating in and requesting the change for the 5 state region.18. Place an 'x' here if the CLEC is operating in and requesting the change for the 2 state region (CA or NV).19. Place an 'x' here if the CLEC is operating in and requesting the change for the 7 state region.20. Place an 'x' here if the CLEC is requesting the change with a high priority.21. Place an 'x' here if the CLEC is requesting the change with a medium priority.22. Place an 'x' here if the CLEC is requesting the change with a low priority.23. Place an 'x' next to the corresponding Pre-Order application for which this change is requested.24. Place an 'x' next to the corresponding Ordering application for which this change is requested.25. Place an 'x' next to the corresponding Repair & Maintenance application for which this change is requested.26. Place an 'x' next to the corresponding Billing application for which this change is requested.27. Place the LSR form name and field name and number to the corresponding LSOR/LSR Business Rule for

which this change is requested.28. Place an 'x' next to Manual/Fax Ordering for which this change is requested.29. Place a detailed description of the requested change. Some items to include would be the function within the

specific interface or process. Other items to include would be the LSR form name and field name andnumber within the specified form. If the priority has been deemed high, please provide the detail andreasoning to qualify this request as a high priority.

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

SBC EMAIL ADDRESS: Eva Hardy - [email protected] SEND CC: TO SWBT, PB or NV ACCOUNT MANAGERAttachment 1

EH Attachment 6.8-7

CLEC INITIATOR/NAME:1

SBC ACCOUNT MANAGER2

CCR SUBMITTED: DATE: 3 VIA EMAIL: 4 VIA FAX: 5 VIA OTHR: 6PRIMARY CLEC SME CONTACT INFORMATION

(Contact for additional details/questions or to whom response will be made)

NAME7

TELEPHONE NO.8

ADDRESS/LOCATION9

FAX10

EMAIL11

CHECKHERE

PROPRIETARY STATUS(CLEC may indicate the degree to which they wish to share their CCR with other CLECs)

12SEMI-PRIVATE/PROPRIETARY – SHARE WITHOUT CLEC IDENTIFICATION

13NON-PROPRIETARY – SHARE NON-RESTRICTED

CHECKHERE

TYPE OF CHANGE CHECKHERE

CLEC OPERATING AREA CHECKHERE PRIORITY REQUESTED

14NEW FUNCTIONALITY/PROCESS

175-STATE (AR, KS, MO, OK,TX)

20HIGH (Critical)

15CHANGE TO EXISTING FUNCTION/PROCESS

18

[ ][ }

2-STATECANV

21MEDIUM

16

[ ][ ][ ][ ]

INDUSTRY STATUSIssue # OBF Initial ClosureIssue # SOSC ReviewIssue # OBF Final ClosureLSOG # EDI Release

197-STATE (All SBC Locations)

22LOW (As resources permit)

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

PRE-ORDER ORDERINGREPAIR &

MAINTENANCE BILLINGLSOR/LSR

BUSINESS RULES OTHER[ ] Verigate[ ] Datagate[ ] EDI SSL3[ ] CORBA

23

[ ] CEASE [ ] BEASE[ ] LEX [ ] EDI[ ] PBSM [ ] POS[ ] SORD [ ] PBOD[ ] E911 [ ] Lstg[ ] Starwriter[ ] Order Status

24

[ ] Trouble Admin.[ ] PBSM

25

[ ] Bill Info

2627

[ ] Manual/FAX Ordering

28

DETAILED DESCRIPTION OF REQUESTED CHANGE(If Priority = High, provide detail sufficient to qualify CCR as critical)

29

SBC USE ONLY:



EH Attachment 6.8-8

INITIAL PROCESSING REQUEST STATUS COMMENTS CCR TRACKING NUMBERDate

Received:Date

Acknowledged:

[ ] PENDING (Under review)[ ] APPROVED[ ] DEFERRED[ ] NOT APPROVED

CLEC INITIATOR/NAME:

SBC ACCOUNT MANAGER

CCR SUBMITTED: DATE: VIA EMAIL: VIA FAX: VIA OTHR:

PRIMARY CLEC SME CONTACT INFORMATION (Contact for additional details/questions or to whom response will be made)

NAME

TELEPHONE NO.

ADDRESS/LOCATION

FAX

EMAIL

CHECKHERE

PROPRIETARY STATUS(CLEC may indicate the degree to which they wish to share their CCR with other CLECs)

SEMI-PRIVATE/PROPRIETARY – SHARE WITHOUT CLEC IDENTIFICATION

NON-PROPRIETARY – SHARE NON-RESTRICTED

CHECKHERE

TYPE OF CHANGE CHECKHERE

CLEC OPERATING AREA CHECKHERE PRIORITY REQUESTED

NEW FUNCTIONALITY/PROCESS 5-STATE (AR, KS, MO, OK,TX) HIGH (Critical)

CHANGE TO EXISTING FUNCTION/PROCESS[ ][ }

2-STATECANV

MEDIUM

[ ][ ][ ][ ]

INDUSTRY STATUSIssue # OBF Initial ClosureIssue # SOSC ReviewIssue # OBF Final ClosureLSOG # EDI Release

7-STATE (All SBC Locations) LOW (As resources permit)

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

PRE-ORDER ORDERINGREPAIR &

MAINTENANCE BILLINGLSOR/LSR

BUSINESS RULES OTHER[ ] Verigate[ ] Datagate[ ] EDI SSL3[ ] CORBA

[ ] CEASE [ ] BEASE[ ] LEX [ ] EDI[ ] PBSM [ ] POS[ ] SORD [ ] PBOD[ ] E911 [ ] Lstg[ ] Starwriter[ ] Order Status

[ ] Trouble Admin.[ ] PBSM

[ ] Bill Info [ ] Manual/FAX Ordering

DETAILED DESCRIPTION OF REQUESTED CHANGE(If Priority = High, provide detail sufficient to qualify CCR as critical)



EH Attachment 6.8-9

SBC USE ONLY:

INITIAL PROCESSING REQUEST STATUS COMMENTS CCR TRACKING NUMBERDate

Received:Date

Acknowledged:

[ ] PENDING (Under review)[ ] APPROVED[ ] DEFERRED[ ] NOT APPROVED



Attachment 2

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


CCRTrackingNumber

OriginatingCLEC

CLEC PrimaryContact Name

InterfaceAffecting

Description Status Date Received

EH Attachment 6.9-1

Ameritech OSS Interfaces

CLEC Change Management Process forAmeritech

Version 6/7/1999

Ameritech OSS Interface: CLEC ChangeManagement Process for Ameritech

Page 2 of 17 Confidential for Ameritech and Certified CLEC Use Only Version 6/7/1999EH Attachment 6.9-2

Purpose

This document establishes a framework of guidelines (the “Change ManagementProcess” or “CMP”) to facilitate effective communications between AmeritechInformation Industry Services (AIIS) and CLECs regarding Changes to Ameritech’s OSSInterfaces. The CMP is intended to establish a structural means by which (1) CLECsmay propose Changes to the Ameritech OSS Interfaces and (2) Ameritech may notifyCLECs of Changes to be made to the OSS Interfaces. The CMP should be viewed as apractical guide to all parties to exchange valuable information regarding the AmeritechOSS Interfaces and to implement Change control practices and procedures. Thisdocument may be revised as business and/or regulatory conditions dictate.

Ameritech will continue to support the industry standards (OBF/TCIF) interfaces for itswholesale customer to order and maintain Local Services. As industry standards evolve,Ameritech intends to use the CMP and discussions at the CLEC Forum to review thestandards and determine appropriate implementation choices. If the standard is clear ,consistent and financially feasible from Ameritech’s perspective, Ameritech willimplement that standard. If the standard is unclear, inconsistent, or not financiallyfeasible from Ameritech’s perspective, Ameritech will work with the CLEC Forum todevelop an acceptable solution. If no standard exists, or if the existing standard(s) areambiguous or have not been generally accepted for implementation by the industry, thenAmeritech will, with the advice of the CLEC Forum participants, determine whatstandard(s) to implement and any applicable implementation schedule. In making thatchoice, Ameritech will consider any “standard in progress”, consistency with existingstandards, cost and cost recovery mechanisms, viewpoints of CLEC Forum participants,customer acceptance and other relevant factors.

The CMP is intended to clarify the methods and procedures by which Ameritech willoccasion a Change to its OSS Interfaces. The CMP is not intended, nor shall it bedeemed to expand or limit, Ameritech’s obligations to implement a Change, as definedby applicable law and the express language of Ameritech’s agreements under Section 251and 252 of the Telecommunications Act of 1996. In the event of any conflict betweenthe obligations of Ameritech as described in the CMP, as revised from time to time, andthose Ameritech obligations imposed by applicable law or its 251/252 agreements, thelatter shall control and Ameritech’s obligations shall be limited or expanded accordingly.For purposes of the previous statement, a conflict does not exist merely because onedocument (the CMP or the interconnection agreement) does not address an issueidentified in the other document.



Overview

The CMP includes the following topical areas:

• Change Definition• Parties Involved in the CMP• Steps of the CMP, including:• Notification

• Testing• Backout/Recovery• Version Control• Implementation• Post Implementation

• OSS Interface Change Notification Form

Throughout this document, any reference to “day” or “days” shall be deemed a referenceto a Calendar Day, unless otherwise specifically noted.

Change Definition

Generally, a “Change” subject to the CMP includes any preordering and orderingChanges that impacts ongoing and future technical and operational processes and altersthe relationship in the manner Ameritech and CLECs do business today. A non-exclusivelist of “Changes” includes:

• Changes that alter the production and test environments.

• Modifications to software and hardware maintenance, upgrades, testing of newapplications, new applications systems and Changes in the hours of the system/s orinterface availability.

• Fixes to known problems, network maintenance and modifications, scheduled outagesduring scheduled business hours and Changes to data fields, formats and/orsignificant content.

• Method and procedure Changes that impact a CLEC’s ability to order and preorderAmeritech services.



Parties Involved in the Change Management Process

The primary participants in the CMP include:

• Change Initiator: The entity that initiates a Change Request.• Change Recipient: The entity that receives the Change Request.• Change Management Point of Contact (CM POC): Each CLEC and Ameritech

will designate a CM POC to serve as its liaison between the parties regarding theCMP. If there is a Change in the CM POC, notice of the Change will be provided atthe earliest possible opportunity to enable a smooth transition.

The Ameritech and CLEC CM POC list will contain primary and secondary names,telephone numbers and email addresses. The Ameritech and CLEC CM POC list will bepublished on the Ameritech TCNet web page. It is the responsibility of Ameritech andeach CLEC to maintain the corresponding information. This list will serve as the contactlist for verbal and written notification of a Change. The existing TCNet notificationprocess will be used to support revisions to the CM POC list. Revisions to the CM POClist will be submitted by the CLEC via the TCNet update process and must be notified toaffected parties as soon as possible.

Identification /Classification of a ChangeWhen Should A Change Be Initiated?

Due to the nature of the telecommunications industry, there are various drivers thatwarrant Change in business operations between CLECs and the ILEC. Broadlydescribed, these Changes may include anything that alters the relationship betweenparties in the manner Ameritech and CLECs do business today, including both manualand electronic processes. Change initiators may include, but are not limited to, thefollowing types of Changes:

• Industry Standards as they apply to the Ameritech OSS Interfaces• Business Rules (i.e. Resale Service Ordering Guide & Unbundling Service Ordering

Guide)• Change in Operational Procedures• New Products• OSS EDI Interface• Documentation• Organizational• Contractual• Ameritech Specific Forms• Regulatory Requirements



Change Request Categories and Urgency

When submitting a Change, the Change Initiator must assign a Category, describedbelow, to that Change. The Change Initiator shall assign a category on the ChangeManagement Notification Form, a copy of which is attached as Appendix A (a “ChangeRequest”). If the Change Recipient disagrees with the Category selected by the ChangeInitiator, and the parties are unable to informally resolve the issue, either party mayinvoke the escalation process described in the escalation section of this document.

Changes shall be categorized as follows:

“Category 1” or “Emergency Change”

A Change that must be implemented in less than two calendar days after receipt of theChange Request. An Emergency Change may be the result of an emergency situation orregulatory mandate that requires immediate implementation.

Urgency:Emergency, Stops Production – Critical Fix – Due Date: Immediate

“Category 2” or “Critical Change”

A Change that requires implementation within two to one hundred twenty calendar days.Critical Changes will be introduced within two to one hundred twenty calendar daysdepending upon the impact on the CLEC or internal Ameritech processes. Examples ofCritical Changes include a mandated regulatory Change and an OBF/Standards Changethat Ameritech is either obligated or has agreed to implement but not immediately.

Urgency:Critical - Does not stop production, but affects key applications and causesinterference with major systems/applications. Must be handled ASAP, i.e.quicker than a standard Change, but it is not an emergency. A mutually agreedupon work-around will be implemented, where possible - Due Date: One toseventy five days depending upon trading partner business impact.

“Category 3” or “Standard Change”

A Change that (i) enhances the OSS interface process or corrects an OSS Interfaceproblem that has a work-around implemented, (ii) introduces new functionality for thepreordering or ordering of services, or (iii) alters the business rules and methods andprocedures that affect the manner by which a CLEC preorders or orders services. Anexample of a standard Change is an LSOG update. New functionality and products thatdo not negatively impact the CLEC current processing will not require mutual agreement.Standard Changes will be introduced with at least ninety days notification.



“Category 3” or “Standard Change” (continued)

When a Standard Change (i.e. LSOG updates) is being implemented, a project planwith milestones will be developed and reviewed at the CLEC Forum.

Urgency:Standard - Standard Change Management Process for all major releases (i.e.LSOG updates), including other regularly scheduled releases. Due Date: Ninetydays or greater depending upon Ameritech’s assessment of the trading partnerbusiness impact.

“Category 4” or “Interim Changes”

A Change that addresses interim releases and/or updates, including software “bug” fixes.Interim Changes will be introduced with at least one hundred and twenty daysnotification.

Urgency:Low - Interim releases and/or updates, including software “bug” fixes. Whenever

possible, an interim Change should be included in a Standard Change to makeefficient use of releases. Includes major Changes, including new OBF standardimplementation. Due Date: One hundred twenty days or greater depending uponAmeritech’s assessment of the trading partner business impact.

“Category 5” or “Non-Critical Documentation Change”

A Change that impacts documentation but does not impact CLEC methods andprocedures for preorder or order functions. Typically, a Category 5 Change may correctmisspelled words in, or provide additional clarity to, documentation. No notification (asdescribed below) is required for a Category 5 Change.

Urgency:Low – Documentation Changes that provide clarification. Notwithstanding thelow urgency, simple documentation Changes will generally be implemented assoon as possible. Due Date: Implemented when documentation is updated



Notification

The following notification requirements apply when a Change Initiator provides aChange Request to the Change Recipients. Notification requirements vary dependingupon the Category of the Change.

Pre-notification is defined as Ameritech’s effort to inform the CLEC community ofChange definition and attributes at the earliest possible opportunity. Pre-notification doesnot start the implementation clock nor is the delivered data binding on Ameritech sincethe nature of the notification is early in the process and may be volatile and subject toChange. Typically Pre-notification will occur at the CLEC Forum. Pre-notification datathat would be inappropriate to hold for the next CLEC Forum will be distributedelectronically. Pre-notification applies only to Category 3 (standard) and Category 4(Interim) Changes and not to the remaining Change categories.

Formal notification will be provided via TCNet as noted on the following matrices. Theemail will provide awareness that a detail of the Change is available on TCNet andassociated documents. The email text will include the category of Change in thebeginning of the notification. (i.e. ** STANDARD **)

The interval timing included in the following matrices does not reflect sequential timing,but may run concurrent. The implementation clock formally begins when the TCNetemail notification is provided. Full documentation will be available at this time onTCNet as noted in the associated notification detail. Pre-notification, as definedpreviously, will begin prior to the Implementation timeframe.



Notification Matrix

Step Category

Notification Timeframe (minimum)(see Notification Section)

1Emergency

ASAP

2Critical

1-75Days

3Standard

90Days

4Interim

120Days

5Doc Only

N/A

Initial Contact MethodVerbal to CMPOC followedby TCNETemail

Verbal (1-7)TCNETEmail

CLECForum &TCNETEmail

CLEC Forum& TCNET

Email

TCNETEmail

Documentation Verbal follow-up by TCNET

ChangeRequest Form

TCNetChangeRequest

Form

FormalDocument

and TCNETChangeRequest

Form

FormalDocument

and TCNETChange

Request Form(Joint dev.Proj. plan –Forum act.)

TCNETChangeRequest

Form

Documentation GenerallyImpacted

ESO GuideMatrices

ESO GuideMatrices

ESO Guide: EDI/OBF/ Scenarios/ErrorMsg/Tech

Spec:Case Scen.Matrices(bus. Rules):

MatricesOrder form

InstructionsOrd. Guides

ESO Guide: EDI/OBF/ Scenarios/Error Msg/Tech

Spec:Case Scen.Matrices(bus. rules):

MatricesOrder form

InstructionsOrderingGuides

RSOG/USOG

PotentiallyAll

supportingdocuments

* Category 3 and Category 4 implementation timeframes begin when all relateddocumentation is made available to the CLEC. Category 4 must have all open issuesclosed (activity of the CLEC Forum) or an approval to commence implementation by amajority vote of the companies attending the CLEC Forum.



Change Management Process

The following chart provides the requisite activities and associated interval to implementa Change. Unless otherwise indicated, the timeframes commence as of the date propernotification for the Change Request has been received. The Customer Test is dependenton the Implementation activity and the timeframe noted represents the period fromImplementation through Customer Testing.

The following definitions apply to the steps noted below:

1. Change Definition: Written documentation (i.e. Ameritech matrices, businessrules, EDI mapping) as well as description of the Change, perceivedcustomer impact and urgency, if applicable.

2. Customer Impact Analysis: CLEC process of reviewing the customer impactand engaging in discussions with Ameritech. Ameritech will provide anunderstanding of the Change in a timely manner as permitted by theimplementation of the Change according to its Category.

3. Customer Test: CLEC testing in an the Ameritech test environment prior toCLEC production implementation.

Step: Category1

Emergency2

Critical3

Standard4

Interim5

Doc OnlyPre-Notification N/A N/A 30 days 60 days N/A

Change Definition(see Notification Section)

** ASAP 1-75 days min 30 days min 120days

N/A

Customer ImpactAnalysis(expressed in

days after ChangeDefinition)

(see Notification Section)

** ASAP max 30days***

max 30 days* 45 daysor greater

N/A

Implementation(see Notification Section)

ASAP Between2 to

120days***

*****90 days or

greater

*****120 days or

greater

ASAP

Customer Test N/A ****as

applicable

****As applicable, upto 90 days afterimplementation

120 days orgreater

N/A



Change Management Process (continued)

Notes:

* Typically, subsequent Changes to documentation during Change Definition andCustomer Impact Analysis would not reset the implementation “clock”. Thiswould be reviewed on a case by case basis between the Change Initiator andChange Recipient.

** May be provided post implementation. Adequate information will be providedimmediately.

*** Where applicable, a mutually agreed approach and implementation date will beestablished and supercede noted interval

**** Upon request and availability***** Standard Changes (i.e. LSOG) will be scheduled through the CLEC Forum

CLEC/Ameritech Review Process

In the event a CLEC has concerns with or needs further explanationfollowing either a Pre-Notification announcement or a Change DefinitionAnnouncement the following process will apply.

1. The CLEC will provide a written description of it’s concernsincluding business impacts and issues within ten business days followingthe announcement.

2. Ameritech will respond to the CLEC concerns in writing within tenbusiness days following the receipt of the CLEC document.

3. If the CLEC continues to have concerns or requires furtherexplanation/s the CLEC should present it’s issues/concerns to theirAIIS Account Team for additional review.

It should be noted that Ameritech and the CLEC will make every effortto resolve and minimize the impacts and business concerns brought aboutby the changes inherent in interface and process management.

Not withstanding, Ameritech reserves the right, after due considerationof CLEC’s concerns, to revise, update or modify it's interfacesand/or processes in the interest of Ameritech’s business needs provided suchrevision, update or modification is consistent with applicable law.

The change management process outlined in this document also pertainsto the CLEC community's ability to initiate for consideration



CLEC/Ameritech Review Process (continued)

change requests to the Ameritech OSS interface. CLECs will be expectedto present a business case in writing to accompany such requests.

Ameritech agrees to take under consideration the proposed requestand respond in writing within 10 business days. If mutually agreeable,implementation of the change will follow the same guideline andtimeframe agreed upon in this document.

Testing

The testing phase of this CMP references the process that the CLEC takes to ensure aquality product. It assumes that Ameritech has conducted internal quality testing prior tomaking the Change available to the CLEC.

The parties will cooperate to ensure that the Change will function properly andefficiently. Such testing will simulate actual operational procedures and systeminterfaces where possible. A CLEC may request additional cooperative testing to ensureservice performance and reliability.

Ameritech supports a customer test environment for CLEC testing. The CLEC has theoption to use this environment. Testing is the responsibility of the CLEC. Ameritech willprovide resources to expedite and execute testing activities through the Ameritechcustomer implementation team. Ameritech reserves the right to limit availability ofimplementation resources to ensure nondiscriminatory opportunities to test among allCLECs in a timely manner. If this limitation adversely impacts a CLEC, that CLEC maypursue the Escalation Process.

For Category 3 and Category 4 Changes, the CLEC will be required to comply with thefollowing testing steps. This will ensure that testing resources are available, improve thequality of the test and provide a structured approach to the testing process.

The steps listed below must be followed when a CLEC requests to test on the Ameritechcustomer test environment. Ameritech does not require testing for CLEC productionimplementation unless severe problems are encountered in the production environment.



Testing (continued)

Customer Test System Procedure:

1. CLEC develops forecast of testing needs.2. CLEC develops detail test plan.3. Ameritech and CLEC mutually accept test plan.4. CLEC develops Test case scenarios.5. CLEC defines Measures for test success.6. Ameritech customer implementation team works with recipient during

execution of test plan.7. CLEC determines when the Change will be implemented in its production

environment (within defined timeframes).8. CLEC may conduct end-to-end testing with the CLEC live accounts in the

production environment

Backout/Recovery

Ameritech reserves the right to determine if the recent software Change requires backoutor recovery. The CLEC may request a backout, which can be requested by calling theAmeritech Resource Center. When requesting a backout, the CLEC must include in itsrequest the reason for backout and the business impacts. The Resource Center willrespond to the requesting CLEC with a status of the backout request within two hoursafter the center receives a complete request. When making the decision to backout aChange, Ameritech will review the impact of the problem from both the CLEC andAmeritech perspective and will give consideration to the timeliness of an emergency fix;provided, as noted above, Ameritech shall have the discretion to require backout orBackout/Recoveryrecovery. If the CLEC disagrees with the Ameritech backout decision, that CLEC maypursue the Escalation Process.

Version Control

The following version control will apply to Category 3 and Category 4 Changes. BecauseCategory 1 and Category 2 Changes are emergency or immediate Changes that must beimplemented to avoid a serious business impact to either the Change Recipient or ChangeInitiator, there is no ability to support multiple versions.



Version Control (continued)

When a Standards Change (i.e., LSOG updates) is being implemented, the ChangeInitiator and Change Recipient(s) are required to support the current version of theinterface and the previous versions for a defined “sunset” period. The Ameritechproduction version will be the basis for this reference. Upon the implementation of a newproduction version, Ameritech will allow nine months from the date on which the newproduct was made generally available prior to sunsetting or eliminating the older of thetwo versions unless (i) a different date is agreed upon in the Ameritech-CLEC Forum, or(ii) a national OBF standard is unacceptable to Ameritech. The Ameritech-CLEC Forumwill address development of version control and associated milestones. This may berevised on a version by version basis as required.

During the sunset period, a Change Initiator may only submit Category 1 or a regulatorymandated Change if such Change is to be applied to the older of the two versions.

Implementation

Not withstanding anything to the contrary herein, Ameritech reserves the right toimplement a Change as determined by the impact to the business entities and discussionwith the CLEC Forum. If an individual CLEC determines that the implementation of aChange will cause serious problems, the CLEC must contact the Ameritech CM POC,request a delay and provide a written explanation for such request. Ameritech willreview the written explanation to determine whether to honor the delay request andrespond to the CLEC with its decision within 1 day of such request. If the CLECdisagrees with Ameritech’s determination, that CLEC may invoke the Escalation Processto request further review of the Change decision.

CLECs determine if testing is required. If testing is required, Ameritech will providecustomer implementation support as outlined in the testing section of this document.

Implementation dates may be postponed only under the following conditions:

1) Mutual agreement; or2) If a delay is caused by one’s party’s failure to fulfill the Change requirements, then

the other party can unilaterally delay implementation by providing written notice tothe party failing to fulfill its Change requirements.



Post-Implementation

To ensure proper functioning, each Change will be closely monitored for at least thirtycalendar days following the implementation of the Change.

Acceptance of Completion

After implementing the Change and testing the Change in a production environment, theChange Initiator will determine whether the Change has been completed and isoperational. The Change Recipient will notify the Change Initiator if problems exist thatshould prevent the Change from being closed.

The Change Initiator will review all reported issues to determine if the Change isoperational. When it is determined that the Change request can be closed, the ChangeInitiator will notify the Change Recipient that the Change is closed. In the event of adispute, the Change Recipient should contact the Change Initiator’s CM POC to lodge acomplaint. The Change Initiator will review this request and contact the ChangeRecipient within 2 business days to discuss the specific issues.

Escalation Process

If a CLEC has an issue or dispute with respect to the implementation plan or Changeapproach, the following procedures should be followed. The Ameritech TCNET WebSite contains contact numbers for each party’s CM POC and the Resource Center. Pleaserefer to the TCNET for this information.

Procedure :

1. CLEC will contact the Ameritech Resource Center and indicate that acomplaint is being issued. The CLEC must provide the followinginformation:

A. CLEC Representative Name, Title and Management LevelB. CM POC Name, Pager Number and Call Back Numbers & FaxC. Reason for escalationD. Associated Ameritech OSS Change Management Notification NumberE. Detailed CLEC Business Impact if the issue is not resolvedF. Description of the Desired ActionG. Possible Remedy Date (if applicable)H. Any additional information that will help Ameritech evaluate the issue

and its impact.



Procedure (continued)

2. Ameritech Resource Center will respond within 6 business hours for aCategory 1 Change and 12 business hours for Category 2, 3 and 4 Changes ofthe original call to the Resource Center with an assessment of actions that canbe taken to remedy the situation. The Resource Center hours of operation areprovided on the Ameritech TCNET Web site in the Library Section –Electronic Service Ordering Guide.

3. If the remedy is not acceptable to the CLEC, the CLEC will notify Ameritechof this situation and must escalate the situation to its next higher level ofmanagement.

4. Ameritech will provide the next level of management name and telephonenumber to the CLEC at the time Ameritech is notified that the remedy is notacceptable.

5. The escalation process will begin at the appropriate management level withinboth Ameritech and the CLEC.

6. The CLEC should contact the assigned Ameritech Account Manager when anescalation process is required. This will alert the Sales/Marketing departmentof an issue that cannot be resolved at the first level of resolution.

Ameritech OSS Change Management Notification Form


General Information:

Notification Number:

Notification Date:

Change Management Point of Contact:

Change Initiator Company Name: Point of Contact Telephone Number:

Point of Contact Fax Number: Point of Contact Email Address:

General Change Description:

Implementation Plan:

Planned Production Implementation Date: __________________

Planned Test System Implementation Date: __________________

Release(s) Impacted: ____________________________________

Applies to a Sunset: ___ Yes ___ No If Yes, Associated Sunset Date: ______________

Change Classification:

___ 1) Emergency ___ 2) Critical ___ 3) Standard ___ 4) Interim ___ 5) Documentation

Type of Change:

___ Standard ___ New Product ___ Business Rule ___ Operation Procedure ___ OSS EDI Interface

___ Documentation ___Organization ___ Contractual ___ Ameritech Forms

Impacted Business Process:

___ Pre-Order ___ Ordering/Provisioning ___ Maintenance ___ Billing

___ Other (please specify): _____________________________________________________

Ameritech OSS Change Management Notification Form


Impacted Business Segment:

___ Residential ___ Business

Impacted Interface(s):

___ EDI Ordering ___ EDI Pre-order ___ Maintenance GUI ___ Maintenance App-App

___ Billing ___ECN Connection ___ Other (please specify): __________________________

Impacted Documentation:

___ ESO Guide ___ Matrices ___ RSOG/USOG

**** End of Change Request Process ****

Documents

HAM AFFIDAVIT Attachment 6 - att.com AFFIDAVIT Attachment 6. EH Attachment 6-1 Accessible “Invitation to Discussion of SBC/Ameritech 13-State Change Management Process