ham affidavit - attachment 32...2 ham attachment 32 in concert with phase 2 described in paragraph...

HAM AFFIDAVIT - ATTACHMENT 32

1Ham Attachment 32

Accessible

“SBC/Ameritech Plan of Record for Uniform and Enhanced OSS – California”

Date: March 6, 2000

Number: CLECC00-058

Contact: Your Pacific Bell Account Manager

This Accessible Letter is to notify you of the completion of the Plan of Record for Uniform andEnhanced OSS in compliance with the SBC/Ameritech Merger Conditions approved in theMemorandum of Understanding and Order, released on October 8, 1999 (Section VIII, Paragraphs 25-28).

In compliance with Phase 1 of the merger conditions, this notification and the attached Plan of Recordare being sent to all CLECs who have current interconnection agreements with SBC/Ameritech in anyof the following thirteen states: Arkansas, California, Connecticut, Illinois, Indiana, Kansas, Michigan,Missouri, Nevada, Ohio, Oklahoma, Texas and Wisconsin.

The Uniform and Enhanced OSS Plan of Record includes six attachments that contain supportingdocuments. Due to the size of the attachments, three are provided in this notification and three areprovided via SBC web sites. The attachments provided on the web sites are also available bycontacting your Account Manager.

Attachments

A: SBC CLEC Interface CMP document – provided belowB: Verigate User Guide

Under Job Aids on the IS Call Center location of the CLEC website at https://clec.sbc.comC: Uniform Pre-ordering Data Field Example – provided belowD: LEX User Guide

Under Job Aids on the IS Call Center location of the CLEC website at https://clec.sbc.comE: EBTA User Guide

Under Library on the Ameritech TCNet website at http://tcnet.ameritech.comF: Interconnection User Guide – provided below

2Ham Attachment 32

In concert with Phase 2 described in paragraph 28(b) of the merger conditions, SBC is ready to workwith CLECs in a series of collaborative workshop sessions. These sessions will be conducted to obtainwritten agreement on OSS interfaces, enhancements, business requirements identified in the Plan ofRecord, and a change management process, including a 12 month forward-looking view of processchanges and deployment schedule. To facilitate the successful completion of Phase 2 within the next30-day period, SBC requests CLEC comments to the Plan of Record by March 13, 2000, and providesthe proposed schedule for collaborative sessions. The first session will be sponsored in Dallas, Texas.

March 13, 2000 CLEC discussion items submitted

March 16, 2000 Collaborative Session #1 – Dallas, Texas

March 21-23, 2000 Collaborative Session #2Location to be determined

March 28-30, 2000 Collaborative Session #3Need and location to be determined

To bring focus to the collaborative sessions and move forward through Phase 2 in an expeditiousmanner, SBC requests that CLECs provide comments on the areas of this Plan of Record you wouldlike to have further discussion on. Comments to this Plan must be requested in writing and provided toyour Account Manager no later than March 13, 2000.

On March 16, 2000, SBC will hold the first workshop and facilitate a “listening session” which willprovide an opportunity for CLECs to discuss their comments provided by March 13. A secondworkshop session will be held based on mutually agreed upon dates and location as established in thefirst session. During the second session, SBC will lead discussions in the areas where CLECs haverequested further discussion and will work collaboratively with CLECs to reach written agreement onthe work to be done in those areas. A third workshop session will be scheduled to complete thecollaborative discussions if needed. The objective of these sessions is to successfully complete Phase 2with consummation of a written agreement between all parties on work to be done in the Plan ofRecord.

Attachments

3Ham Attachment 32

Ham Attachment 321

Uniform and Enhanced OSS Plan of Record

I. OVERVIEW.....................................................................................................................................................................3

A. INTRODUCTION...............................................................................................................................................................3

B. SCOPE.............................................................................................................................................................................3

C. PROCESS METHODOLOGY...............................................................................................................................................3

II. PRESENT METHODS OF OPERATION (PMO) ......................................................................................................7

A. PRE-ORDERING ...............................................................................................................................................................7

Available Interfaces...........................................................................................................................................................7

EDI Message Flows...........................................................................................................................................................8

Functions ...........................................................................................................................................................................9

B. ORDERING ....................................................................................................................................................................15

Available Interfaces.........................................................................................................................................................15

Ordering Message Flows.................................................................................................................................................16

C. PROVISIONING ..............................................................................................................................................................19

Functions .........................................................................................................................................................................19

D. MAINTENANCE AND REPAIR .........................................................................................................................................21

Available Interfaces.........................................................................................................................................................21

E. BILLING ........................................................................................................................................................................24

Billing Data Tape (BDT) .................................................................................................................................................24

Exchange Message Interface (EMI) ................................................................................................................................24

Electronic Data Interchange (EDI) .................................................................................................................................26

Online Viewing/GUI ........................................................................................................................................................26

Product Billing System Alignment ...................................................................................................................................26

F. CONNECTIVITY .............................................................................................................................................................29

III. FUTURE METHOD OF OPERATION (FMO) .....................................................................................................31

A. OVERVIEW....................................................................................................................................................................31

Standards.........................................................................................................................................................................31

Development Timeline .....................................................................................................................................................31

Versioning........................................................................................................................................................................32

CLEC Joint Testing .........................................................................................................................................................32

B. PRE-ORDERING .............................................................................................................................................................33

Ham Attachment 322

Uniform Pre-ordering Message Flows ............................................................................................................................33

Uniform Pre-ordering Functions.....................................................................................................................................34

C. ORDERING ....................................................................................................................................................................39

Uniform Ordering Message Flow....................................................................................................................................39

Uniform Product Ordering ..............................................................................................................................................39

D. PROVISIONING ..............................................................................................................................................................42

E. MAINTENANCE AND REPAIR .........................................................................................................................................43

F. BILLING ........................................................................................................................................................................47

Billing Data Tape (BDT) .................................................................................................................................................47

Exchange Message Interface (EMI) ................................................................................................................................47

Electronic Data Interchange (EDI) .................................................................................................................................50

Online Viewing/GUI ........................................................................................................................................................50

Product Billing System Alignment ...................................................................................................................................51

G. CONNECTIVITY .............................................................................................................................................................52

H. DOCUMENTATION.........................................................................................................................................................54

Current and Uniform Interface Documentation ..............................................................................................................54

I. TIMELINE......................................................................................................................................................................55

IV. GLOSSARY ...............................................................................................................................................................60

Ham Attachment 323

I. OVERVIEW

A. Introduction SBC/Ameritech currently makes a wide variety of Operational Support System (OSS) interfaces availableto CLECs in its four service areas: Ameritech, Pacific Bell/Nevada Bell (PB/NB), Southwestern BellTelephone (SWBT) and Southern New England Telephone (SNET). Although these interfaces all provideaccess to OSS functionality for pre-ordering, ordering, provisioning, maintenance and repair and billingservices, there are regional differences in the interfaces and how they operate. Accordingly, as part of theOctober 8, 1999 SBC/Ameritech Merger Conditions, SBC/Ameritech agreed to develop and deploycommercially ready, uniform application-to-application and graphical user (GUI) interfaces for the supportof these functions. This Uniform and Enhanced OSS Plan of Record (POR) is the initial milestone of the three-phase processset out in the Merger Conditions for the development and deployment of uniform application-to-applicationand GUI interfaces that present telecommunications carriers that are users of the interfaces with the sameversion(s) of industry standards, data formatting specifications and transport and security specificationsacross the 13-State SBC/Ameritech Service Area. B. Scope The focus of this POR defines a plan for SBC/Ameritech to make available modified OSS, in accordancewith the schedule and commitments outlined in the SBC/Ameritech Merger Conditions. These OSSinclude application to application interfaces and graphical user interfaces (GUIs) which support pre-ordering, ordering, provisioning, maintenance and repair and billing for resold services, individualUnbundled Network Elements (UNEs), and combinations of UNEs. While most of these interfaces areexisting and currently in use, additional access to these OSS functions will be provided as a result as thisplan. Section II of this POR details the Present Method of Operation (PMO) for all existing OSS interfaces in thefour SBC/Ameritech Service Areas. In Section III, the Future Method of Operation (FMO) of theseinterfaces, including plans for the development and deployment of modifications designed to ensure theavailability of uniform, electronic OSS interfaces throughout the 13-State SBC/Ameritech Service Area, isspecified. C. Process Methodology

This POR follows the framework established by the SBC/Ameritech Pre-Merger "OSS ProcessImprovement Plan".

The following steps were taken to create this plan:

Ham Attachment 324

• Subject matter experts representing all of the SBC/Ameritech service areas were assembled fromvarious OSS business requirement areas and from Information Technology system and architectureareas.

• The PMO was documented for pre-ordering, ordering, provisioning, maintenance and repair and billinginterfaces.

• The FMO interfaces and processes for pre-ordering, ordering, provisioning, maintenance and repair,and billing were identified and documented.

• An FMO implementation plan documenting the appropriate interface changes and associated timelineswas documented.

The criteria for determining the future method of operation included, but was not limited to:

• Business requirements, including the number of actual current users, the volumes currently processed,the flow-through capability that already exists as well as the expected number of users and requests(i.e., future capacity requirements).

• Industry standards or guidelines, such as those published by T1, the Ordering and Billing Forum (OBF)

and Telecommunications Industry Forum (TCIF). • Downstream impacts of any changes, such as the effect that changes in the applications would have on

methods and procedures. • CLEC input, including the types of change requests CLECs are initiating, the discussions in change

management meetings regarding developmental plans, CLEC specific feedback from the account teams,other OSS support personnel, training classes and CLEC forums.

• The architecture of SBC/Ameritech’s current OSS, including available data and functionality. • The current security methods including firewalls, addresses, passwords, and current CLEC access

methods. SBC/Ameritech will follow the three-phases identified in the SBC/Ameritech Merger Conditions.SBC/Ameritech will work collaboratively with CLECs and the FCC Staff to obtain written agreement onOSS interfaces, enhancements and business requirements identified in this POR and ultimately develop anddeploy those agreed upon changes in accordance with the schedules contained within the MergerConditions. Standards Multiple bodies are involved in the setting of standards and guidelines for the OSS interfaces used forcommunication between ILECs and CLECs. SBC/Ameritech actively participates in these organizations,and is supportive of the timely implementation of the standards and guidelines issued by them.

Ham Attachment 325

Forums and Committees of the Alliance for Telecommunications Industry Solutions (ATIS), the Orderingand Billing Forum (OBF), the Telecommunications Industry Forum EDI Service Order Subcommittee(SOSC), the Telecommunications Industry Forum Electronic Communications Implementation Committee(ECIC), and the T1M1 Committee are the industry-recognized bodies that issue standards and guidelinesapplicable to the interfaces used in the pre-ordering and ordering of resold local service and unbundlednetwork elements. The OBF issues guidelines covering the pre-ordering and ordering transaction flows andassociated data elements, the SOSC provides the guidelines for the implementation of those transactions inEDI, and T1M1 the implementation of pre-ordering transactions in CORBA. Currently, the OBF is developing version 5 of its Local Services Ordering Guide (LSOG 5), which istargeted for release in final form on July 26, 2000. The SOSC is expected to release version 5 of the EDIElectronic Local Mechanization Specifications (ELMS 5) on October 30, 2000 dependent on the release bythe OBF of LSOG 5. Version 4 (LSOG 4) was released April 9, 1999. ECIC has issued two standardsapplicable to pre-ordering via CORBA: T1.265-1999 approved April 1999, and T1.267-1999 approvedAugust 1999. ATIS committees also provide standards and guidelines applicable to the repair and maintenance, andbilling functional areas. The T1M1 committee has issued two standards governing the data elements andoperation of the repair and maintenance interface: T1.227a-1999 and T1.228-1995. The OBF MessageProcessing Committee maintains the Exchange Message Interface guideline. Version 17 of this guidelinewas issued in January 2000. Issue 9 of the EDI billing guideline, maintained by the TCIF EDI committeeand built upon the ANSI X.12, version 4010 EDI standard was published in December 1998. Telcordia’sCarrier Access Billing System (CABS) Billing Output Specifications (BOS) for Bill Data Tape (BDT),version 32, were published in April 1999. In this plan, SBC/Ameritech is committing to implementing the most current versions of standardsavailable in the industry today. Because of the evolving nature of industry standards, SBC/Ameritech willwork with the CLECs through the change management process to determine whether more advancedversions of the industry standards should be implemented in the uniform interfaces instead of thoseestablished in this document. The CMP will also be used to determine the appropriate implementation ofthe selected standards versions, because a strict adherence to the standard might result in loss of existingfunctionality and because of the flexibility of implementation allowed within the standards and guidelines. Change Management Each SBC/Ameritech service area has its own Change Management Process (CMP). These were developedcollaboratively with the CLECs well before the SBC/Ameritech merger, and have each been in place sinceat least June 1999. These processes provide a means by which each regional company and the CLECs canwork cooperatively to introduce changes to the OSS interfaces. These processes include specific intervals,such as when release specifications will be delivered to the CLECs for review and input.

A 13-state CMP is currently being addressed in a separate CLEC collaborative effort that began inNovember 1999 following the SBC/Ameritech merger close. The 13-state CMP is expected to be approvedby the CLECs in March 2000. This Change Management Process, in its current draft form, is detailed inthe attached document (see Attachment A). Once implemented as described in the CMP transition plan,

Ham Attachment 326

SBC/Ameritech will use this process in lieu of the current service area processes. SBC/Ameritech iscommitted to using the CMP to deliver the changes identified in this POR. SBC/Ameritech agrees that there needs to be a process that addresses business process changes, such asmanual processes and forms, that fall outside the scope of the OSS CMP. SBC/Ameritech is committed toputting in place by April 2000 a process by which these changes can be addressed, including establishmentof CLEC User Forums. Until these forums are established, SBC/Ameritech will address these changes inthe existing SBC/Ameritech user forums.

Ham Attachment 327

II. PRESENT METHODS OF OPERATION (PMO)

The PMO for all existing OSS interfaces in the four SBC/Ameritech Service Areas are outlined in thissection. The regional differences in these interfaces and the access they provide to OSS functionality forpre-ordering, ordering, provisioning, maintenance and repair, and billing are described, analyzed andcompared. A. Pre-ordering Available Interfaces The Southwestern Bell Telephone (SWBT), Pacific Bell/Nevada Bell (PB/NB), Ameritech and SouthernNew England Telephone (SNET) regions provide CLECs with application to application access to pre-ordering functions via Electronic Data Interchange (EDI), which has been selected by the Ordering andBilling Forum (OBF) as one of the methods for exchanging information between telecommunicationscompanies regarding orders for local service. SWBT and PB/NB also provide application to applicationpre-ordering functions via Common Object Request Broker Architecture (CORBA). SWBT and PB/NB have implemented EDI pre-ordering functions based on the Ordering and Billing Forum(OBF) Local Service Ordering Guidelines (LSOG) version 4, Telecommunications Industry Forum (TCIF)Electronic Data Interchange Local Mechanization Specification (ELMS) issue 4, and EDI ASC X12 version4010. Ameritech and SNET offer EDI pre-ordering interfaces which were implemented prior to acceptanceof industry guidelines, and utilize ASC X12 version 3072. CORBA became an Electronic Communications Implementation Committee (ECIC) approved IndustryGuideline for local service pre-ordering in September 1997. This approval provided two industryacceptable transport protocols for local pre-ordering, CORBA and EDI. CORBA was accepted as analternative due to its fundamental ability to support interactive data exchange. CORBA is defined by theObject Management Group (OMG) and uses Interface Definition Language (IDL) data models as definedby the T1M1 committee of the Alliance for Telecommunications Industry Solutions (ATIS). T1.265-1999covers the majority of pre-ordering functions and was approved April 1999. T1.267-1999 applies to theCustomer Service Information (CSI) Inquiry and Directory Listings Inquiry and was approved August 1999. SWBT and PB/NB have implemented CORBA pre-ordering functions based on the OBF LSOG version 4and ANSI T1.265-1999, with security implemented in accordance with T1M1 T1.265 security. Ameritechand SNET have not made a CORBA-based pre-ordering interface available to CLECs. In addition to the application to application interface using EDI/CORBA, the SWBT and PB/NB regionsalso provide pre-ordering functions via DataGate. DataGate is an SBC/Ameritech proprietary applicationto application interface implemented prior to the acceptance of industry guidelines. Graphical User Interface (GUI) access to pre-ordering functions is provided to CLECs in the SWBT andPB/NB regions via the Verigate application. SNET provides GUI access to pre-ordering functions via W-CIWin. Ameritech provides GUI access to pre-ordering functionality via TCNet.

Ham Attachment 328

The following table summarizes the pre-ordering interfaces currently available in the SBC/Ameritechoperating regions.

Pre-Ordering SWBT PB/NB SNET Ameritech Industry App to App Gateway Application Name EDI/CORBA EDI/CORBA MSAP EDI LSOG Version 4 4 NA NA Protocol / Version EDI 9 / 4010 EDI 9 / 4010 EDI / 3072 EDI / 3072 Protocol / Version CORBA / T1.265-1999,

T1.267-1999 CORBA /T1.265-1999,

T1.267-1999

Proprietary App to App Gateway Application Name DataGate DataGate Proprietary GUIs Application Name Verigate Verigate W-CIWin TCNet

EDI Message Flows The current application to application interfaces utilize ASC X12 transaction sets to pass EDI accessinformation between requestor (CLEC) and provider (SWBT, PB/NB, Ameritech or SNET). The SWBT, PB/NB and SNET regions utilize the 850, 855, and 997 transaction sets. A typical pre-ordering transaction begins when a CLEC submits an 850 transaction. When the 850 is received, a 997transaction is immediately returned to the CLEC to communicate the receipt of the request. Responses,whether positive or negative, are returned to the CLEC via an 855 transaction. The CLEC may return a 997transaction to communicate the receipt or rejection of the 855. Ameritech utilizes the 850, 855, and 864 transaction sets. A typical pre-ordering transaction begins withthe receipt of an 850 transaction from a CLEC. A 997 transaction is not used to communicate receipt of the850. Responses, whether positive or negative, are returned to the CLEC via an 855 transaction or an 864transaction. The 864 transaction is used to return Customer Service Information (CSI) to the CLEC.Ameritech does not require a CLEC to return a 997 transaction. The following table provides a summary of the EDI transaction usage on the pre-ordering application toapplication interfaces in the SBC/Ameritech operating regions:

RECORDTYPE

SWBT PB/NB SNET Ameritech

997 Acknowledgment Acknowledgment Acknowledgment N/A 850 Initial Request Initial Request Initial Request Initial Request 855 Response Response Response Response (except CSI) 864 N/A N/A N/A CSI Response

Ham Attachment 329

Functions Pre-ordering capabilities allow for the exchange of certain information between SBC/Ameritech andCLECs about a given end user. This information enables the CLEC to submit a complete and accuraterequest to SBC/Ameritech for the provision of local service by the CLEC to the end user. This exchangeof information is performed based on an inquiry and response process. The following pre-orderingcapabilities are available to and used by CLECs in one or more SBC/Ameritech Service Areas. Address Validation Inquiry The Address Validation Inquiry enables the CLEC to verify that the end user address it intends to submit toSBC/Ameritech via the local service request is valid. This inquiry is available in the SWBT and PB/NB service areas via the EDI/CORBA, DataGate andVerigate interfaces. Similarly, address validation is performed in the SNET service area via the applicationto application interface and W-CIWin. Ameritech provides this inquiry via the application to applicationinterface and TCNet. In the SWBT and PB/NB service areas, working telephone number (WTN) may alsobe used to retrieve a valid residential service address. In addition to the address validation information,supplemental information (such as tax area codes and the primary NXX of the local service office) also isreturned in each service area. The availability of supplemental information varies by service area becauseof differences in the OSS that perform the address validation inquiry. Common Language Location Indicator (CLLI) Inquiry This Inquiry provides the CLLI code associated with a telephone number, enabling the CLEC to submit theappropriate CLLI code on a local service request for stand-alone UNE switch port or a UNE loop andswitch port combination. This inquiry is available in the SWBT service area via the DataGate and Verigate interfaces. In the PB/NBservice area, this same information is provided as part of the Feature/Service Availability Inquiry inDataGate and Verigate. This information is not provided electronically in the Ameritech and SNET serviceareas, but is instead provided to CLECs manually. Connecting Facility Assignment (CFA) Inquiry By retrieving a list of channel assignments, design-related information and work authorization informationfor leased DS1 and DS3 facilities, this inquiry enables a CLEC to verify the status of a connecting facilityprior to submitting this information on a local service request. In the SWBT and PB/NB service areas, this inquiry is available via the DataGate and Verigate interfaces.This transaction is not supported in the Ameritech and SNET service areas. Customer Service Information Inquiry This inquiry retrieves current end user customer service records. The information provided on the CSI isused to verify existing features and services prior to the submission of a local service request. In the SWBT and PB/NB service areas, the Customer Service Information Inquiry allows for retrieval ofrecords by either account telephone number (ATN) or individual working telephone number (WTN), and is

Ham Attachment 3210

available via the EDI/CORBA, DataGate and Verigate interfaces. In the Ameritech service area, thisinquiry may also be performed by either account or working telephone number, and is available through theapplication to application interface and TCNet. In the SNET service area, this inquiry only supportsretrieval using account telephone number via the application to application interface and W-CIWin. In the SWBT service area, responses are provided for accounts of up to 5,000 working lines on theapplication to application interfaces, and for up to 1000 working lines on the GUI. PB/NB providesresponses for accounts containing up to 4 megabytes of data, and SNET up to 128 kilobytes of data.Ameritech provides responses for accounts up to 20,000 display lines. Requests for customer servicerecords exceeding these parameters must be submitted to the local service centers for fulfillment manually. In the SWBT, PB/NB, and SNET service areas, CLECs may retrieve Resale CSI when the end user accountis owned by another CLEC. Ameritech does not permit CLECs to view CSI when it is owned by anotherCLEC. Data Validation Files Data Validation Files are available for the purpose of providing requesting CLECs with an alternate methodof acquiring that pre-ordering information considered relatively static. Street Address Guide, PIC/LPIC Codes and Feature/Service availability information is available via FileTransfer Protocol (FTP) in the SWBT and PB/NB service areas. In the Ameritech service area, filescontaining directory names, class of service codes, USOC, community names, yellow page headings,feature/service availability, street address guides, and PIC/LPIC codes are available via Connect:Direct,CD-ROM and TCNet. Access to PIC/LPIC codes and product availability files can also be arranged viaConnect:Direct. SNET provides a file containing valid directory yellow page headings downloaded fromthe CLEC web site. Digital Subscriber Loop Pre-qualification Inquiry This inquiry provides an indication of theoretical loop length and indication of local serving office locationswhere SBC/Ameritech has deployed ADSL. In the SWBT and PB/NB service areas, this inquiry is available via the DataGate and Verigate interfaces.Also provided in the SWBT service area is theoretical 26-gauge loop length and taper code information.This inquiry is not available in the Ameritech and SNET service areas. Digital Subscriber Loop Qualification Inquiry This inquiry provides specific, detailed loop make-up information for a loop to a specific address andprovides information necessary to determine the suitability of that loop for xDSL services. In all SBC/Ameritech service areas, loop qualification is a manual process using fax and/or E-mail. Directory Listing Inquiry This inquiry retrieves directory listing information associated with an end user telephone account.

Ham Attachment 3211

The SNET service area provides this inquiry via the application to application interface and W-CIWin.This information is available as part of the Customer Service Information Inquiry via the EDI/CORBA andDataGate application to application interfaces and the Verigate interface in the SWBT and PB/NB serviceareas. In the Ameritech service area, directory listings are available as part of the Customer ServiceInformation Inquiry via the application to application interface and TCNet. Dispatch Inquiry This inquiry retrieves information indicating when the dispatch of an SBC/Ameritech technician is requiredfor residential service ordered on a local service request. Dispatch is based on the existence of cut-throughfacilities and assists the CLEC in determining the due date that may be quoted to the their end customer.. This inquiry in the SWBT and PB/NB service areas is available via the EDI/CORBA, DataGate andVerigate interfaces. In the SNET service area, this information is provided as part of the AddressValidation Inquiry. In the Ameritech service area, this information is provided as part of the Due DateInquiry (see below). Due Date Inquiry This inquiry provides a listing of available premise visit dates. This information is used by the CLEC asone factor in establishing the due date that may be quoted to their end customer. In the SWBT and PB/NB service areas, this inquiry is available via the EDI/CORBA, DataGate andVerigate interfaces. In the Ameritech service area, inquiry, reservation, confirmation and cancellationfunctions are supported via the application to application interface. In the SNET service area, the inquiryfunction is available via the EDI interface and W-CIWin. All service areas return the next available due date. In addition to that date, twenty-seven alternate datesare returned in the SWBT service area, twenty-nine alternate dates are returned in the Ameritech servicearea, and four alternate dates are returned in the SNET service area. No alternate dates are returned in thePB/NB service area. In the SNET service area, a standard interval appropriate to basic local service isreturned for non-dispatch orders. In the Ameritech service area, a non-dispatch, dispatch, or standardinterval due date is returned based on available facilities, and customer order parameters. Feature/Service Availability Inquiry This inquiry provides information indication the availability of specific features and services at a particularlocal serving office switch. In the SWBT and PB/NB service areas, this inquiry is available via the EDI/CORBA, DataGate andVerigate interfaces. The SWBT and PB/NB EDI/CORBA interfaces validate the availability of a singlefeature or service per transaction using the feature/service in Universal Service Order Code (USOC) formatas input. Inquiries via the DataGate and Verigate interfaces return a list of available features/serviceUSOCs retrieved by ten-digit telephone number in the SWBT service area. A list of USOCs and associatedSOSC codes are retrieved using CLLI or NPA-NXX in the PB/NB service area. In the SNET service area,a list of available features in terms of SOSC codes is provided via the application to application interfaceand W-CIWin. In the Ameritech service area, this information is provided from a Data Validation file inUSOC format, and is also available via TCNet.

Ham Attachment 3212

Network Channel/Network Channel Interface (NC/NCI) Inquiry This inquiry allows the CLEC to validate Network Channel (NC) and Network Channel Interface (NCI)codes and their combinations prior to submitting a local service request. In the SWBT and PB/NB service areas, this inquiry is available via the DataGate and Verigate interfaces.SNET does not currently support this inquiry. Ameritech does not currently support this inquiry, butinformation regarding valid NC/NCI codes is provided via CLEC ordering documentation on TCNet. Pending Order Status Inquiry This inquiry provides access to pending service order status and content prior to the conversion of an end-user account. Utilizing the DataGate interface in the SWBT service area, access to a list of pending service orders isprovided by working telephone number. Detailed service order information is provided when an inquirycontaining working telephone number and service order number is processed. This functionality is alsoavailable in the GUI interface called Order Status for both the SWBT and PB/NB service areas. In thatGUI, additional search criteria utilizing customer number and purchase order number are available toprocess a list of pending service orders and detailed service order information. SNET and Ameritech donot currently support this inquiry. PIC/LPIC Inquiry This inquiry provides a list of current Primary Interexchange Carrier (PIC) and IntraLATA PrimaryInterexchange Carrier (LPIC) codes for carriers providing service at a particular local serving office switch. A list of PIC/LPIC codes is retrieved by ten-digit telephone number via the EDI/CORBA, DataGate andVerigate interfaces in the SWBT service area. A list is available by CLLI or NPA/NXX in the PB/NBservice area. In the Ameritech service area, lists of PIC/LPIC codes are available using NPA/NXX throughthe application to application interface and via TCNet. Additionally, this information is available as part ofthe Data Validation Files. SNET does not currently provide this inquiry. Telephone Number Availability These functions allow available telephone numbers to be identified and held for use by a CLEC submittinga local service request: • Inquiry - Provides a list of available telephone numbers for a given local serving office switch.• Inquiry/Selection - Provides and holds a list of available telephone numbers for a given local serving

office switch.• Reservation - Allows available telephone numbers to be held until either the receipt of a valid local

service request, cancellation of reservation/selection, or the end of a specified holding period.• Confirmation - Confirms previously reserved or held telephone numbers.• Cancellation - Allows the release of telephone numbers previously reserved or held. This inquiry is available in the EDI/CORBA, DataGate and Verigate interfaces in the SWBT service areaand supports inquiry/selection and cancellation. This inquiry is available in the same interfaces in the

Ham Attachment 3213

PB/NB service area and supports inquiry, reservation and cancellation. This inquiry is available in theAmeritech service area via the application to application interface and supports inquiry, reservation,confirmation and cancellation. Via the application to application interface and W-CIWin in the SNETservice area, this inquiry supports inquiry/selection, and cancellation. The following table summarizes functionality currently available in each of the SBC/Ameritech serviceareas. Each row represents an inquiry offered in at least one service area. Unless otherwise noted, theInterface or GUI access options available by service area are shown in the heading.

Inquiry Existing Functionality and Interface(s) by Service Area

SWBT

EDI/CORBA, DataGate, andVerigate

PB/NB

EDI/CORBA, DataGate,and Verigate

SNET

EDI and W-CIWin

Ameritech

EDI and TCNet

Address Validation Numbered, Unnumbered,Unnamed, Descriptive inquiry

Numbered, Unnumbered,Unnamed, Descriptive inquiry



WTN inquiry WTN inquiry --- --- Common LanguageLocation Identifier (CLLI)

CLLI inquiry

DataGate and Verigate

Information included as partof Feature/Service Availability

--- ---

Connecting FacilityAssignment (CFA)

CFA inquiry


CFA inquiry


--- ---

Customer ServiceInformation (CSI)

ATN inquiry ATN inquiry ATN inquiry ATN inquiry

WTN inquiry WTN inquiry --- WTN inquiry

Data Validation Files SAG, PIC/LPIC,Features/Services

SAG, PIC/LPIC,Features/Services

Yellow Page Headings SAG, PIC/LPIC,Features/Services, YellowPage Headings, USOCs

FTP, Direct:Connect, CLECWeb site

FTP, Direct:Connect, CLECWeb site

CLEC Web site Direct:Connect, CD-ROM,CLEC Online Web site

DSL LoopPre-qualification

Pre-qualification inquiry


Pre-qualification inquiry


--- ---

DSL Loop Qualification --- --- --- --- Directory Listing

Information included as part of

CSI Information included as part

of CSI ATN inquiry Information included as part

of CSI

Dispatch Dispatch inquiry Dispatch inquiry Dispatch information includedin Address Validation inquiry

Dispatch information includedin Due Date inquiry

Due Date

Inquiry

Next available due date and 27alternate dates available

Resale and Loop w/ Port

Inquiry

Next available due date only

Resale and Loop w/ Port

Inquiry


Non-dispatch, dispatch orstandard interval

Inquiry


Non-dispatch, dispatch orstandard interval

EDI only

--- --- --- Reservation

--- --- --- Confirmation

--- --- --- Cancellation

Ham Attachment 3214

Inquiry Existing Functionality and Interface(s) by Service Area

SWBT

EDI/CORBA, DataGate, andVerigate

PB/NB

EDI/CORBA, DataGate,and Verigate

SNET

EDI and W-CIWin

Ameritech

EDI and TCNet

Feature/ServiceAvailability

Validation by individualFeature/Service EDI/CORBA

List of Features/Services viaDataGate and Verigate

USOCs

Validation by individualFeature/Service EDI/CORBA

List of Features/Services viaDataGate and Verigate

USOCs and SOSCs

List of Features/Services

SOSCs

---

Features/Services via DataValidation File and TCNet

USOCs

NC/NCI Validation Validation inquiry


Validation inquiry


--- ---

Pending Order Status Pending inquiry

DataGate and Order Status

Pending inquiry

Order Status

--- ---

PIC/LPIC List Code inquiry Code inquiry --- Code inquiry

TN Inquiry

Inquiry/Selection

5 TNs

Inquiry

5 TNs

Inquiry/Selection

4 TNs

Inquiry

10 TNs

EDI only

--- Reservation

5 TNs

--- Reservation

1 TN

--- --- --- Confirmation

Cancellation Cancellation Cancellation Cancellation

Ham Attachment 3215

B. Ordering Available Interfaces Application to application access to Local Service Request (LSR)-based ordering functions isprovided to CLECs in all SBC/Ameritech service areas via an EDI interface, which is the industrystandard means of communication for the ordering of local services. The application to applicationinterfaces in all SBC/Ameritech service areas currently run ASC-X12, Version 3072. SWBT,PB/NB and SNET have implemented LSOG Version 3, TCIF issue 8, whereas Ameritech iscurrently on LSOG Version 2, TCIF issue 7. EXACT is the Access Service Request (ASR)-based industry application to application interfaceutilized in the SWBT, Ameritech and SNET service areas for ordering Unbundled DedicatedTransport (UDT) and Interconnection Trunks. Customer’s Enhanced System for Access Requests(CESAR) is the ASR-based industry application to application interface utilized for the samepurpose in PB/NB. Ameritech also allows the use of EXACT to order Loops. All service areas arecurrently on ASOG Version 21. The LSR Exchange (LEX) system is a GUI available to CLECs for ordering LSR-based services inthe SWBT and PB/NB service areas. SNET and Ameritech do not offer a GUI for LSR-basedordering. Telis, an ASR-based GUI, is utilized in the SWBT, Ameritech and SNET service areas for orderingUDT and Interconnection Trunks. Ameritech also allows the use of Telis for ordering Loops.PB/NB provides CESAR/online as an ASR-based GUI, for ordering UDT and InterconnectionTrunks and also provides the GUI Customer’s Enhanced System for Access Requests –Interconnection Service Requests (CESAR-ISR), for ordering Loops, Number Portability, and Loopwith Number Portability. Companies may be on the same version/level of a given guideline, but the implementation may bedifferent. Companies may have implemented some functions or products in advance of standards. The following table summarizes the ordering application to application interfaces currently availablein the SBC/Ameritech service areas.

ORDERING SWBT PB/NB SNET Ameritech Industry Applications EDI EDI EDI (MSAP) EDI LSOG Version 3 3 3 2 TCIF Issue 8 8 8 7 X12 Version 3072 3072 3072 3072 ASR EXACT CESAR EXACT EXACT ASOG VER. 21 21 21 21

Ham Attachment 3216

The following table summarizes the ordering GUI interfaces available in the SBC/Ameritech serviceareas.

GUIs SWBT PB/NB SNET Ameritech LEX X X - - LSOG VER. 3 3 - - CESAR ISR - X - - ASOG VER. - 21 - - TELIS X - X X ASOG VER. 21 - 21 21 CESAR Online - X - - LSOG VER. - NA - -

Ordering Message Flows All SBC/Ameritech service areas utilize the standard 997, 850, 855, 860 and 865 transaction sets forthe various functions associated with the EDI ordering of Local Services. The following describesthe current environment and the differences between the service areas. 997 Transaction All SBC/Ameritech service areas currently return a 997 transaction to the CLEC to acknowledge thereceipt of a data transmission. 850/855 Transactions A typical ordering transaction begins with a CLEC sending an 850 transaction. Positive or negativeresponses are returned to the CLEC via an 855 transaction to communicate the disposition of therequest. If the request is error free, a positive response is sent in the form of a Firm OrderConfirmation (FOC). If errors are detected, a negative response is sent in the form of errorinformation detail. This process is the same in all service areas. In the SWBT and PB/NB service areas, two types of errors, fatal or super fatal, may be encounteredin a negative 855 transaction. Fatal errors are the most common and these are corrected by theCLEC sending an 860 transaction. Super fatal errors are such that the request could not be processeddue to key fields being invalid or missing. These are corrected by the CLEC by sending another 850transaction. In the SNET service area, when a negative response is received, regardless of the errortype, the request is not processed and corrected 850 transactions are sent by the CLEC until theCLEC receives a positive 855 transaction. In the Ameritech service area, when a negative response is received regardless of any error type, therequest is not processed and another 850 transaction is sent until the CLEC receives a positive 855transaction. Additionally in the Ameritech service area, a Purchase Order Advice is sent via an 855transaction to acknowledge receipt of a request for Number Portability when more than 50 lines areincluded. 860/865 Transactions The 860 transaction is used in all service areas for a CLEC to submit a change (supplement) to arequest. SWBT, PB/NB and SNET require a “full refresh” of the request, meaning that all previous

Ham Attachment 3217

and changed information is included in the supplement. In the Ameritech service area, only changedinformation is submitted on the 860 transaction. Positive or negative responses are returned to the CLEC via an 865 transaction to communicate thereceipt and acceptance or rejection of the supplement (860). Again if the request is error free, apositive response is sent in the form of an FOC. If errors are detected, a negative response is sent inthe form of error information detail. To correct errors on an 860 transaction, another 860 transactionis sent. This is the same in all service areas. In the SWBT and PB/NB service areas, the 860 transaction could also be a response by the CLEC toa negative 855 transaction due to errors on the original request (850). In the Ameritech service area, the 865 transaction is also used to notify CLECs of customerimpacting provider initiated changes. Additionally a Purchase Order Advice is sent via an 865transaction to acknowledge receipt of a supplement for a change to a request for Number Portabilitywhen more than 50 lines are included. The following table provides a summary of the EDI transaction usage on the ordering application toapplication interfaces in the SBC/Ameritech service areas.

RECORDTYPE


997 Acknowledgment Acknowledgment Acknowledgment Acknowledgment 850 Initial Request Initial Request Initial Request Initial Request 855 • FOC

• Error Notice• FOC• Error Notice

• FOC• Error Notice

• FOC• Error Notice• Purchase Order

Advice 860 Supplements:

• Initiate Change• Correct Errors on

850 record type• Correct Errors on

860 record type• Full refresh

Supplements:• Initiate Change• Correct Errors on

850 record type• Correct Errors on

860 record type• Full refresh

Supplements:• Initiate Change• Correct Errors on

860 record type• Full refresh on most

products

Supplements:• Initiate Change• Changes only on

supplement• Correct Errors on

860 record type

865 • FOC• Error Notice



• FOC• Error Notice• Customer impacting

- provider initiatedchanges

• Purchase OrderAdvice

Product offerings in all service areas were evaluated based on the following criteria: 1) whether theproduct is offered in a service area; 2) whether an OBF guideline exists for the product; and 3)whether the given product may be ordered electronically. Many products were offered across all service areas. Other products were available in multipleservice areas and in some instances, products were available in only one service area. Currently in the instances where there are OBF guidelines in place for product families, all serviceareas utilize OBF standards with minor modifications. Standard LSOG forms are used, howeverfield usage may be different based on service area-specific business rules and requirements.

Ham Attachment 3218

Additional fields may have been introduced in advance of standards. Fields that identify who thecustomer is, how the request is tracked, and what services and activities are being requested, varyacross the service areas. Some products, such as ISDN, CENTREX, and PBX for Resale and Unbundled Network Elements(UNE), have been implemented using forms designed based on OBF guidelines where possible.Field and data characteristics have been expanded to provide additional information for provisioningof the product. In some instances, service area-specific ordering requirements have been implemented for bothelectronic and paper/fax input, and in other instances only paper/fax input is supported. In the SWBT service area, white page listings for unbundled loops, unbundled switch ports, loopwith port combinations, and Resale services can be requested via the current ordering application toapplication and GUI interfaces. Yellow page listings are arranged directly with the directorypublisher, Southwestern Bell Yellow Pages, a separate subsidiary of SBC/Ameritech. In the Ameritech service area white page listings associated with products that include a white pageor basic yellow page listing, e.g. resale, unbundled switch ports, and loop with port combinations,may be ordered via the current EDI application to application interface. CLECs must establish abusiness relationship with the appropriate directory listings subsidiary to provide all other white oryellow page listings. In the PB/NB service area, white page listings for unbundled loops, unbundled switch ports, loopwith port combinations, and resale services can be ordered via the current application to applicationand GUI interfaces. Yellow page listings are arranged directly with the separate directory publishingsubsidiary. CLECs also have the capability to enter listing information directly into the ListingsGateway. In the SNET service area, white page listings for unbundled loops, unbundled switch ports, loop withport combinations, and resale services can be ordered via the current application to application andGUI interfaces. Yellow page listings arranged directly with the separate directory publishingsubsidiary.

Ham Attachment 3219

C. Provisioning SBC/Ameritech provides various electronic capabilities that enable a CLEC to track the status of anorder during the period between order placement and order completion. These capabilities areprovided by SBC/Ameritech via the pre-ordering and ordering application to application and GUIinterfaces. Those functions that are based on an inquiry/response model, e.g. a CLEC asking for andreceiving status on a pending order, are accessed using the pre-ordering interface. SBC/Ameritechproactively sends order statuses, such as order completion, to the CLEC as the order is processed viathe ordering interface. Functions Following are the various functionalities available to CLECs in the SBC/Ameritech service areas fortracking order status during the provisioning process. Jeopardy Notification When a situation is encountered in the provisioning of an order that could potentially cause theconfirmed due date to be missed, a Jeopardy Notification is issued to the CLEC. These notifications are provided via the transaction message flows in the ordering application toapplication interfaces in the SWBT and PB/NB service areas using the 865 transaction. This samenotification is provided via the LEX GUI interface. Jeopardy notification is currently provided inthe Ameritech service area via the ordering application to application interface using the 870transaction. The SNET service area provides this notification via a manual process. Service Order Completion Service Order Completion (SOC) is a notification to the CLEC that the work requested on a localservice request has been completed. The SWBT, PB/NB, Ameritech and SNET service areas all use the 865 transaction to return a SOCnotification via the ordering application to application interface. This notification is also availablevia the LEX ordering GUI application in the SWBT and PB/NB service areas. Loss Notification Loss Notification is a notification to the CLEC that a change requested by anotherTelecommunications Carrier (TC) has been completed and, as a result, the Local Service Providerassociated with a given telephone number has been changed. Ameritech currently provides Loss Notification via the ordering application to application interfaceusing the 836 transaction. The SWBT, PB/NB and SNET service areas provide equivalentnotifications to CLECs using the Carrier Access Record Exchange (CARE) process. Pending Order Status This inquiry provides access to a list of pending service orders, and their status and content. Thisinformation is provided prior to the conversion of an end-user account for pre-ordering purposes, andprior to the service order posting in the billing system for monitoring order progress.

Ham Attachment 3220

Utilizing the DataGate interface in the SWBT service area, access to a list of pending service ordersis provided by working telephone number. Detailed service order information is provided when aninquiry containing working telephone number and service order number is processed. This functionis also available in a GUI named Order Status in both the SWBT and PB/NB service areas. Thisfunction is not currently available in the Ameritech service area. CLECs may monitor the progressof their orders using an Interactive Voice Response (IVR) system made available by Ameritech.SNET does not presently support this function. Posted Order Status This inquiry provides access to posted service order status and content. The information providedrepresents completed service order status as posted to the billing system. Access to this information is available in the Order Status GUI for the SWBT service area. A list ofposted service orders or detailed service order information is provided when an inquiry containingcustomer number is processed. Detailed service order information is provided when an inquirycontaining working telephone number, service order number or purchase order number is processed.PB/NB, Ameritech and SNET do not currently support this function. Provisioning Order Status This inquiry provides access to the service order provisioning information to determine the pendingor dispatched status of a service order. The information provided presents the status of the order,such as whether it has been dispatched or notes regarding the order. Access to this information is provided via the DataGate interface in the PB/NB service area bycustomer number, service order number or telephone number. Access to this information is alsoavailable via the GUI named Provisioning Order Status for both the SWBT and PB/NB service areas.Ameritech and SNET do not currently support this function. The following table summarizes the provisioning functions currently available in the SBC/Ameritechservice areas.

RECORD TYPE SWBT PB/NB SNET Ameritech 865 • SOC

• Jeopardy Notice• SOC• Jeopardy Notice

• SOC • SOC

870 NA NA NA Jeopardy Notice 836 • N/A – Handled

via CAREprocess

• N/A – Handledvia CAREprocess

• N/A – Handledvia CAREprocess

• LossNotification

Proprietary Message Eventvia DataGate

• Pending OrderStatus

• ProvisioningOrder Status

NA NA

Graphical Data Provided via the OrderStatus and ProvisioningOrder Status GUIs



• Posted OrderStatus



NA NA

Ham Attachment 3221

A. Maintenance and Repair

Available Interfaces

All SBC/Ameritech service areas offer application to application and GUI maintenance and repairinterfaces. Ameritech, PB/NB, and SWBT all support application to application interfaces forElectronic Bonding Trouble Administration (EBTA) based on the American National StandardsInstitute (ANSI) Standards. SNET offers a non-standard application to application interface, MSAP,to support maintenance and repair functions. All service areas in SBC/Ameritech have developedtheir own GUI interface. Each GUI interface supports various functions with different presentationsto the end user.

PB/NB offers Pacific Bell Service Manager (PBSM). It allows a customer to: Create a troublereport, view trouble history, retrieve trouble status and perform MLT tests on Resale POTS and loopwith port.

SWBT offers Toolbar/Trouble Administration. It allows a customer to: Create a trouble report, viewtrouble history, retrieve trouble status and perform MLT tests on Resale POTS and loop with port.

SNET offers CCTools, which allows a customer to view trouble history and retrieve trouble statusfor resale POTS products.

Ameritech offers EBTA GUI. It allows a customer to: Create a trouble report, view status history,receive proactive status, clear and close trouble reports. It provides similar functionality to theapplication to application interface.

Ham Attachment 3222

The following table is a summary of the maintenance and repair application to application and GUIinterfaces in the various SBC/Ameritech service areas.

SYSTEM SWBT PB/NB SNET Ameritech

APP -TO-APP

System: Electronic Bonding –TA

T1.262:1998 (Release 4.58/99)T1.227:1995T1.227A (Release 5.1 10/99)T1.228:1995

Release 4.1.0


T1.262:1998 (Release 4.58/99)T1.227:1995T1.227A (Release 5.1 10/99)T1.228:1995

Release 4.1.0

System : MSAP

EDI format

Release: N/A


T1.227:1995T1.227A (Release 5.1 10/99)

T1.228:1995

Release: 5.0GUI System: Toolbar / TA

Create Trouble ReportsMLT Test POTS / loop withportView trouble historyView statusView trouble report list.Clear and CloseGUI-Windows Based

Release 5.1.0

System: PBSM

Create Trouble ReportsMLT Test POTS / loop withportView trouble historyView statusView trouble report list.Telnet –VT100 TerminalEmulation

Release: 8.3

System: CCTools

View trouble historyView statusGUI-Windows based

Release: NA

System: EBTA GUI

Create Trouble ReportsView status historyReceive statusView statusView trouble report list.Clear and CloseGUI-Windows Based

Release: 1.0

The following table shows the business functions that can be performed by the various service area-specific GUIs. The business functionality and the screen designs are different for each service area.In most cases the information entered into the fields on the GUI is mapped to data fields in the backend Operating Support Systems (OSS).

FUNCTION SWBT(TOOLBAR –

TA)

PB/NB(PBSM)

SNET(CCTOOLS)

Ameritech(EBTA GUI)

Create Circuit Types (Telcordia valid circuit ids) Access Hours (test and premise access hrs) Narrative Trouble Type Dispatch Authorization Contact information TSP Priority Status Interval Comments /Notes

Yes

Yes

YesYesYesYesNoNoNo

Yes

Yes

YesYesYesYesNoNoNo

No

No

NoNoNoNoNoNoNo

Yes

Yes

YesYesYesYesYesYesYes

Cancel No No No YesModify info after create No No No YesMessaging Yes Yes No YesGet Status (refresh) Yes Yes Yes YesModify No No No YesProactive Statusing No No No YesEscalations No No No YesClear / Close No No No Yes

Ham Attachment 3223

History Trouble Trouble Trouble Ticket StatusMLT Test Yes Yes No NoStatus notification No No No YesEstimated Repair Time No No No YesWEB Version No No No YesCircuit Security Supports MCN, ACNA, orCCNA

Yes Yes No Yes(except MCN)

Close out Narrative Yes Yes No YesCircuit Inventory Yes No No NoBinding Post No Yes No No

Ham Attachment 3224

A. Billing

CLEC billing has been organized into five categories:

• Billing Data Tape (BDT)

• Exchange Message Interface (EMI) Daily Usage

• Electronic Data Interchange (EDI)

• Online Viewing/GUI

• Product Billing System Alignment Billing Data Tape (BDT) All SBC/Ameritech service areas provide CLECs with billing data related to their purchase ofunbundled network elements (UNEs). The primary billing vehicle for billing UNEs is CarrierAccess Billing System (CABS), which produces the BDT file format. All service areas adhere to thesame CABS Billing Output Specifications (BOS) national guidelines for bill media, software versioncontrol, user documentation, and user notification. Additionally, all SBC/Ameritech service areasprovide BDT data on comparable output media that include electronic transmission and tape. All the SBC/Ameritech service areas use Billing Output Specifications (BOS) developed guidelines.A ‘differences list’ is produced with each BDT change outlining where and why a service area maydeviate from standards. Only those BDT records that are applicable to a given service area areproduced by that service area. Additionally, any fields on a record that do not apply to a service areaare populated with a default value. Three months prior to the first possible implementation of a change to the Billing Data Tape, a letteris sent to the customers identifying the changes and any deviations from standards. This is standardacross all service areas. There are differences in the BDT records produced for CLECs across the SBC/Ameritech serviceareas, but these are due largely to service area-specific tariff and contracts and will continue to exist. Exchange Message Interface (EMI) SBC/Ameritech has a responsibility to provide CLECs with usage messages that may be used in thebilling of their end-customers. The CLECs receive usage files containing EMI records that providethe billing details for individual messages. All SBC/Ameritech service areas follow industry-accepted Ordering and Billing Forum (OBF) EMI format for message exchange. At the inception of local exchange competition, Incumbent Local Exchange Carriers (ILEC)independently worked with CLECs to interpret the application of the OBF EMI guidelines, due tolack of complete and definitive industry guidelines. These service area-specific interpretationsresulted in the population of EMI records that currently differ somewhat amongst theSBC/Ameritech service areas.

Ham Attachment 3225

Some service area-specific products have caused a need for locally negotiated records. Therehas been no need for industry standard records for these local products. The records willcontinue to be provided in the daily usage file. The following table summarizes the existing functionality by service area. Where (n/a) is noted,products have not been developed in that service area.

Existing Functionality by Service Area Function SWBT PB/NB SNET Ameritech Bill Media & Version EMI records sent toCLECs in Daily UsageExtract: Header/Trailer Toll Specialized Services -Custom calling features New Class feature record Local D/A Operator Verification Operator Interrupt Credits Switched Data services UNE Specific Records: CABS MTS, Terminat-ing IntraLATA UNE UNE Originated,International Terminated Terminating Local UNE D/A (carrier involved) Terminating Access Originating 800 Originating 500

20-20-01/02 20-21-01/02 20-24-01/02 10-01-01 10-01-18 n/a 10-01-31 10-01-32 10-01-35 10-01-37 03-01-01 01-01-62 11-01-01 11-02-01 11-01-31 11-01-32 11-01-20 11-01-25 11-01-26

20-21-01/02 20-21-09/10 10-01-01 10-01-18 10-01-19 10-01-31 10-01-32 10-01-35 10-01-37 41-xx-xx 03-01-01 n/a 11-01-01 n/a n/a n/a n/a 11-01-25 n/a

20-21-01/02 10-01-01 *Operator handled only 10-01-18 n/a 10-01-31 10-01-32 10-01-35 10-01-37 03-01-01 01-01-62 n/a n/a n/a n/a n/a n/a n/a

20-24-01/02 10-01-01 10-01-18 n/a 10-01-31 10-01-32 10-01-35 10-01-37 41-xx-xx n/a n/a n/a n/a n/a n/a n/a n/a

Guidelines

• Follows the industryaccepted OBF EMIformat for messageexchange.




Ham Attachment 3226

Existing Functionality by Service Area Function SWBT PB/NB SNET Ameritech Delivery Media

• Tape• Connect: Direct• Dial Up

• Tape• Connect: Direct

• Connect: Direct


User Guide – mediaoffer on

SWBT/Inter-industry website or Email from AccountManager

PB/NB has a CLEChandbook that is availableon-line to the CLECs onthe internet.

CLEC Guide published viainternet. It is routinelymaintained

The Ameritech user guideis offered on the internet.

User Guide –Publicationnotification process

CLECs are notifiedthrough an accessible letter60 days in advance of anychanges to EMI recordsthat could impact them



CLECs are notified byletter at least 45 days priorto any change in the EMIrecords that could impactthem. Changes are postedto the TCNet web site.

Electronic Data Interchange (EDI)

The SBC/Ameritech service areas provide CLECs with billing information that originates from theircore retail billing systems representing primarily the Resale of local exchange service. Currently, theSWBT and PB/NB service areas provide this billing information following the EDI 811 transactionset, following Telecommunications Industry Forum (TCIF) guidelines (Issue 9) for billingtransactions. The other two service areas, Ameritech and SNET, are currently providing Resalebilling information under a Telcordia (Bellcore) standard, that is no longer supported by Telcordia.

Online Viewing/GUI

The SWBT service area offers the Bill Info GUI application that provides on-line access to billinginformation. This GUI application provides on-line access to the image of the CLEC’s rendered bill.CLECs have made minimal use of the capability. Recent collaborative meetings with representativesof the CLEC community did not identify an interest in on-line access to the rendered bill.

Product Billing System Alignment

Initial decisions on the system most appropriate to bill wholesale local exchange services were basedlargely on each individual service area’s existing system attributes. Despite being developed ondifferent platforms, the resulting billing outputs utilize consistent formats (e.g., EDI or BDT) acrossthe service area.

Billing systems for the Unbundled Network Elements (UNEs) across the four service areas are inalignment, with the exception of Ameritech’s Line-Side Ports. Ameritech bills the Line-Side Portthrough the Ameritech Customer Information System (ACIS), a CRIS-like billing system, whereother service areas bill through CABS. The unbundled products offered by Ameritech utilizing Line-Side Port and billed through ACIS include Unbundled Local Switching, Shared Transport, andCombined Platform Offering (i.e., UNE-Platform).

Billing for all Resale products across the four service areas are in alignment.

Ham Attachment 3227

Summary of CLEC Billing Interfaces and Product Billing System Alignment

The two tables below summarizes the currently available interfaces, versions and bill deliverymethods previously described as well as the existing product billing system alignment, respectively.

Current Available Billing Interfaces by Service AreaBilling SWBT PB/NB SNET Ameritech

EMI Record Format: EMR/EMI Record Format: EMR/EMI Record Format: EMR/EMI Record Format: EMR/EMI

(for Daily UsageDelivery) Transmit to CLEC Transmit or tape to CLEC. Transmit to CLEC. Transmit or tape to CLEC by

State.

BDT System: CABS System: CABS System: CABS System: CABS

Standard/Format: BillingData Tape (BDT)

Standard/Format: BillingData Tape (BDT)

Standard/Format: Billing DataTape (BDT)

Standard/Format: Billing DataTape (BDT)

Version 32 Version 32 Version 32 Version 32

EDI/AEBS System: Electronic DataInterchange Billing (EDIB)

System: Electronic DataInterchange Billing (EDIB)

System: Customer Records &Information System (CRIS)

System: Ameritech BillingManagement System (ABMS)

Standard: EDI 811 Standard: EDI 811 Standard: Bellcore MagneticBilling Tape Plan

Standard: Bellcore MagneticBilling Tape Plan

Record Format: 4010 Record Format: 4010 Record Format: AEBS 450 Record Format: AEBS 450

Same Info as Paper Bill Same Info as Paper Bill Detail Supporting Summary PaperBill

Detail Supporting Summary PaperBill

Transmitted to CLEC Transmitted to CLEC Magnetic Tape or Cartridge Offer Transmit & AlternativeMedia

Online Viewing System: TOOLBAR/BillInfoFunction: CLEC can viewResale & UNE billincludingpayments/adjustments,CSR, and Subscriptionreports.

None None None

Product Billing System Alignment by Service areaProduct SWBT PB/NB SNET Ameritech

Resale Residence BasicExchange

CRIS CRIS CRIS ACIS/RBS

Resale Business BasicExchange

CRIS CRIS CRIS ACIS/RBS

Resale Complex Business CRIS CRIS CRIS ACIS/RBS

Interim NumberPortability

CABS CABS CABS ACIS/RBS

UNE - Port CABS CABS CABS LINE: ACIS; TRUNK:CABS

UNE – Loop CABS CABS CABS CABS

UNE – Loop withNumber Portability

CABS CABS CABS INP: ACIS; LOOP: CABS

Ham Attachment 3228

UNE – Loop with basicPort

CABS CABS Not Supported No Product

Unbundled DedicatedTransport

CABS CABS CABS CABS

Blended/Shared Transport

CABS CABS CABS ACIS/RBS

Ham Attachment 3229

A. Connectivity

Although all service areas within SBC/Ameritech currently offer CLECs connectivity to OSS, thereare some differences in the form of connectivity offered, the type of facility utilized, and theownership and maintenance of connectivity equipment.

In both its SWBT and PB/NB service areas, SBC/Ameritech currently has a Remote Access Facility(RAF) that is solely dedicated for CLEC use in accessing SBC’s OSS. The SWBT facility, known asthe LRAF, is located in Dallas, Texas, while the PB/NB facility, called the PRAF, is centered inFairfield, California.

Both the LRAF and PRAF are configured with a number of routers capable of terminating privateline and frame relay connections and with access servers to terminate analog modem and ISDN dial-up connections. These terminating routers and access servers are connected to a Local AreaNetwork (LAN) which in turn provides for connectivity to the SBC/Ameritech network “firewall”systems. These secured firewalls use access lists to prevent unauthorized entry into other internalSBC/Ameritech systems that are outside the scope of those OSS offered to CLECs.

Routers for the LRAF and PRAF are provided and maintained by SWBT and PB/NB. CLECsprovide their own circuit, Data Service Unit/Channel Service Units (DSU/CSUs), connectors andcables. Specifications are given to the CLEC for the DSU/CSUs (to be placed on both ends of theCLEC provided circuit) and as well as circuit line coding and framing parameters.

SNET currently allows access to its OSS via their New Haven, Connecticut network connectivitylocation, but does not maintain a separate facility dedicated just for CLEC use. Private line andshared frame relay connections are allowed, but dial-up access is not available. CLECs must provideand maintain their own router and CSU/DSU. Hence, CLECs are given access to SNET’s premisesto install and maintain their own equipment. As part of the SNET merger initiative, work was doneduring 1999 to establish a dedicated facility (to be called the SRAF) for CLEC use within the SNETservice area. The building and testing of the private line and frame relay portion of the SRAF isslated to take place during the first quarter 2000, with plans to secure and install the addition ofaccess servers to terminate analog modem and ISDN dial-up connections shortly thereafter.

CLEC connectivity to most of Ameritech’s OSS is via private line or frame relay. However, someapplications are accessed via the Internet, where security is provided via the use of DigitalCertificates. For private line or frame relay connections, CLECs must provide their own CSU/DSU,which is then installed and maintained by Ameritech personnel. Ameritech provides connectivity toits OSS via either its Chicago, Illinois or Southfield, Michigan Electronic Commerce Network(ECN) rather than through a separate facility dedicated for CLEC use.

Ham Attachment 3230

The table below compares the present method of operation and the varying connectivity-relateditems within the four SBC/Ameritech service areas.

Item/Function SWBT PB/NB SNET Ameritech

Dedicated CLEC Facility Yes Yes No No

Private Line / Frame Relayconnections

Yes Yes Yes Yes

Dial-up Connections Yes Yes No No

SBC/Ameritech provides andmaintains routers

Yes Yes No Yes

CLEC provides circuit andCSU/DSUs

Yes Yes Yes Yes

SBC/Ameritech installs andmaintains CSU/DSUs

Yes Yes No Yes

Internet access using DigitalCertificates

No No No Yes

Ham Attachment 3231

III. FUTURE METHOD OF OPERATION (FMO)

A. Overview

The following section details SBC/Ameritech’s plans for developing and deploying commerciallyready, uniform application-to-application and GUI interfaces. As set out below, these plans arebased on modifications and enhancements to existing OSS interfaces that were identified during thecourse of the PMO evaluation described in Section II.

Standards

The planned modifications and enhancements outlined below are wholly consistent with standardsand guidelines of the industry bodies specified in the Merger Conditions and discussed in Section II.The specific versions of the standards and guidelines that will apply to this deployment are identifiedin the following table:

Function Applicable Standard(s)Pre-ordering, Ordering andProvisioning

• OBF LSOG 4• SOSC ELMS 4• ECIC T1.265-1999• ECIC T1.267-1999

Repair and Maintenance • T1M1 T1.227a-1998• T1M1 T1.228-1995• T1M1 T1.262-1998

Billing • OBF BDT 32• OBF EMI Version 17• TCIF Billing Issue 4010

If no industry guidelines exist, or if existing guidelines are not commonly accepted, SBC/Ameritechwill consider any appropriate industry guidelines in progress, consistency with existing guidelines,consistency with existing interface implementations, customer acceptance, customer-forecastedutilization and development/support costs. Development Timeline The development timeline associated with the deployment dates established for all releases will beconsistent with the SBC Competitive Local Exchange Carrier (CLEC) Interface ChangeManagement Process. The deployment of the uniform application to application interfaces will beconsidered Category One (Gateway) changes for the purposes of Change Management. The uniformGUI interfaces will be enhancements of existing GUI interfaces and therefore will be considered asCategory Two (GUI) changes. A 12-month OSS interface development view will be shared during Change Management Processmeetings. Six months prior to each application to application interface release, Initial ReleaseRequirements will be made available, and Final Release Requirements will be made available twomonths later. For the GUI interfaces, Initial Release Specifications will be provided twenty-one daysin advance of deployment, and will include uniform User Guide documentation. In some serviceareas, a uniform GUI will be the initial introduction of the GUI to that specific service area. In those

Ham Attachment 3232

cases, a special CLEC meeting will be held in advance to demonstrate the existing GUI and toexplain planned enhancements to migrate it to the uniform GUI. Additional detail and requirements on all planned releases will be made available per the ChangeManagement Process. This process also allows for ongoing clarification and CLEC input throughcomment cycles prior to implementation of the releases. Each application to application interface release version will be made available for CLEC testingthirty-seven days in advance of the production deployment date. During the period of this plan, it is anticipated that forces other than this plan will cause additionalchanges and enhancements to the ordering application to application and GUI interfaces offered toCLECs by SBC/Ameritech. Consistent with the CMP, as these changes and enhancements areknown, release announcements will be issued by SBC/Ameritech and the OSS 12-month view willbe revised. Versioning All SBC/Ameritech service areas will have a uniform versioning process for the uniform applicationto application interfaces. The process will be employed as defined in the SBC Competitive LocalExchange Carrier (CLEC) Interface Change Management Process. The uniform versioning processwill be implemented as indicated on the timelines provided in the Implementation Timeline andHigh-level Milestones section of that plan. CLEC Joint Testing All SBC/Ameritech service areas will provide for a uniform CLEC Joint Testing process for theuniform application to application interfaces. The process will be employed as defined in the SBCCompetitive Local Exchange Carrier (CLEC) Interface Change Management Process. The uniformtesting process will be implemented in conjunction with the uniform versioning process as indicatedon the timelines provided in the Implementation Timeline and High-level Milestones section of theChange Management Process plan.

Ham Attachment 3233

B. Pre-ordering All SBC/Ameritech service areas will implement a single uniform version of their existingapplication to application pre-ordering interface which will be accessible using either EDI orCORBA protocols. This interface version will utilize industry guidelines and standards, and will bebased on OBF LSOG version 4. The EDI access will be based on TCIF ELMS 4 and the associatedASC X12 version 4020. The CORBA access will be based on the ECIC T1.265-1999 and T1.267-1999 standards. The uniform pre-ordering application to application interface which will utilize EDIand CORBA will be referred to as the “application to application interface” in the remainder of thispre-ordering section of this plan. All SBC/Ameritech service areas will implement a uniform GUI to access pre-ordering functions.The GUI, which will be an enhanced version of the Verigate application currently offered bySBC/Ameritech in the SWBT and PB/NB service areas, will have a presentation that makes use ofthe terminology employed in OBF LSOG version 4, and have functionality similar to that offered viathe uniform application to application interface. Attached to this document is the User Guide for theexisting Verigate application (see Attachment B). The uniform pre-ordering GUI will be referred toas the “GUI” in the remainder of this pre-ordering section of this plan. There are multiple phases scheduled for the implementation of the uniform pre-ordering interfaceduring the twenty-four months following the SBC/Ameritech merger close. The first will be the introduction of new functions to the current EDI application to applicationinterface in the Ameritech service area. These pre-ordering functions, Connecting FacilityAssignment Inquiry, Feature/Service Availability, and Network Channel/Network Channel InterfaceInquiry, will be made available to provide interactive access to data previously provided byAmeritech through other means. These functions will be available in April 2000. This will be followed by the introduction of the uniform version of the EDI/CORBA application toapplication interface in two phases. The interface will be implemented in the Ameritech service areain March 2001, and in the SWBT, PB/NB, and SNET service areas in June 2001. This version of theinterface will provide full uniform functionality, and will update the interface to LSOG 4 unlessanother guideline version is selected via the Change Management Process. It will include CORBAas an alternative to EDI. Coincident with the implementation of the uniform version of the application to application interfacein each service area, the uniform version of the pre-ordering GUI will also be made available. Uniform Pre-ordering Message Flows The uniform EDI application to application interface will utilize ASC X12 transaction sets to passinformation between requestor and provider using the 850 and 855 transaction sets. A typical pre-ordering transaction will begin when a CLEC submits an 850 purchase order. Responses, whetherpositive or negative, will be returned to the CLEC via an 855 purchase order acknowledgement. Dueto the interactive nature of the pre-ordering functions and a desire for consistency across theSBC/Ameritech 13 state service area, the 997 functional acknowledgement transaction set will not

Ham Attachment 3234

be used. Also, the 855 purchase order acknowledgement will be used, instead of the 864 textmessage, to return customer service information. The uniform CORBA application to application interface will employ T1M1 IDL data models in arequest-response message flow to exchange data between a message requestor and provider. Uniform Pre-ordering Functions The following pre-ordering functionality is planned for the uniform application to application andGUI interfaces. These functions will be available via the application to application interface in bothEDI and CORBA. In order to understand and describe the data field-level specifications for theuniform pre-ordering interfaces, SBC/Ameritech has analyzed a single function (Feature/ServiceAvailability) and developed a proposed uniform specification for that transaction (see AttachmentC). The actual final data field-level specifications will be developed with CLEC input per thetimeline established by the Change Management Process. Address Validation Inquiry The Address Validation Inquiry will continue to be available in all SBC/Ameritech service areas. Aspart of the uniform application to application and GUI interfaces, it will provide access to validatedaddress information by address or working telephone number. This working telephone numberinquiry will be available for residential service only. Address information will also continue to beavailable as a Data Validation File in the SWBT, PB/NB and Ameritech service areas, and will bemade available as a Data Validation File in the SNET service area with the implementation of theuniform application to application and GUI interfaces in that service area. Common Language Location Indicator (CLLI) Inquiry The Common Language Location Indicator (CLLI) Inquiry will provide the CLLI code associatedwith a telephone number, and is used to determine the appropriate CLLI to be submitted on a localservice request for port or loop with port service. This inquiry will be available in all service areas inthe uniform application to application and GUI interfaces. This will be the first implementation ofthis inquiry in the Ameritech and SNET service areas. Connecting Facility Assignment (CFA) Inquiry Based on the input facility number, this inquiry may be used to verify the status of a connectingfacility prior to submitting this information on a local service request. This inquiry will be availablein all SBC/Ameritech service areas via both the uniform application to application and GUIinterfaces. This inquiry will be introduced in the Ameritech service area as part of the functionalityaddition to the existing Ameritech EDI interface in April 2000. It will be introduced in the SNETservice area with the implementation of the uniform application to application and GUI interfaces inthat service area. Customer Service Information Inquiry The Customer Service Information Inquiry will continue to be available in all SBC/Ameritechservice areas via both the uniform application to application and GUI interfaces. It will provide theCLEC the ability to retrieve Customer Service Information (CSI) records for accounts belonging tothe requesting CLEC or to SBC/Ameritech retail units, but not when accounts are owned by anotherCLEC. CSI records may be retrieved using account telephone numbers or individual working

Ham Attachment 3235

telephone numbers. A uniform size limit will be established on CSI responses. The CSI responsewill be in a parsed format consistent between service areas, however the data content will differbased on the availability of information in the source backend systems and service area productdifferences. Data Validation Files Data Validation Files will continue to be available in all SBC/Ameritech service areas. Thedirectory names, class of service codes, USOC, community names, yellow page headings,feature/service availability, and PIC/LPIC code files will be available via Connect:Direct, CD-ROMor downloadable using the pre-ordering GUI. Due to its size, the street address guide will beavailable only via Connect:Direct and CD-ROM. The Data Validation Files will be modified informat and content to be as uniform as possible allowing for the differences in source backendsystems. Digital Subscriber Loop Pre-qualification Inquiry The Digital Subscriber Loop Pre-qualification Inquiry will continue to be available in the SWBT andPB/NB service areas via the uniform application to application and GUI interfaces. This inquiry willbe made available in the Ameritech and SNET service areas with the introduction of the uniformapplication to application and GUI interfaces in those service areas. Digital Subscriber Loop Qualification Inquiry This inquiry will provide CLECs with access to a mechanized loop qualification capability that canbe used to qualify unbundled loops on a pre-order basis. This mechanized loop qualification willprovide the CLECs with the information needed to make an informed business decision regarding itsability to provide DSL-based service to the end user. This inquiry will be available in allSBC/Ameritech service areas via the uniform application to application and GUI interfaces. It willbe introduced in the SWBT and PB/NB service areas via the DataGate and Verigate interfaces inMarch 2000, and via the EDI/CORBA application to application interface in April 2000. In theAmeritech service area, this inquiry will be introduced via the EDI application to applicationinterface in April 2000, and via TCNet in June 2000. The Loop Qualification Inquiry will beintroduced in the SNET service area via the EDI application to application interface in July 2000. The pre-ordering interfaces offered by SBC/Ameritech will be enhanced during 2000 specificallywith respect to the Digital Subscriber Loop Qualification Inquiry. These enhancements come inresponse to the FCC’s UNE Remand Order (Third Report and Order in Docket 96-98), CLECrequests, and in response to specific requirements in the FCC’s SBC/Ameritech Merger Conditionson providing loop makeup information for unbundled DSL-capable loops. SBC/Ameritechcontinues to discuss and provide information on these enhancements through the ChangeManagement Process. Directory Listing Inquiry The Directory Listing Inquiry will be available in all SBC/Ameritech service areas via the uniformapplication to application and GUI interfaces. This will be the introduction of this inquiry in theSWBT, PB/NB, and Ameritech service areas. The Directory Listing Inquiry will provide for theretrieval of listing information by either account telephone number or individual working telephonenumber. CLECs will be able to retrieve directory listing information for accounts belonging to therequesting CLEC or to SBC/Ameritech retail units, but not for accounts owned by another CLEC. A

Ham Attachment 3236

uniform transaction size limit will be implemented and the format of the information will beconsistent between service areas. The data content of the response transaction will differ betweenoperating service areas based on the availability of information in the source backend systems. Thisinformation will also continue to be available in all SBC/Ameritech service areas using the CustomerService Information Inquiry. Dispatch Inquiry The Dispatch Inquiry will be available in all SBC/Ameritech service areas via the uniformapplication to application and GUI interfaces. This inquiry indicates when the dispatch of anSBC/Ameritech technician is required for residential service ordered on a local service request.Dispatch is based on the existence of cut-through facilities and assists the CLEC in determining thedue date that may be quoted to the end user. Although similar functionality is available currently inall service areas, this standalone inquiry will be first introduced in the Ameritech and SNET serviceareas with deployment of the uniform application to application and GUI interfaces. Due Date Inquiry The Due Date Inquiry will continue to be available in all SBC/Ameritech service areas, and will beavailable via both the uniform application to application and GUI interfaces. This inquiry allows forthe identification of available premise visit dates for services to be ordered on a local service request.If alternate dates are requested, the next available and twenty-nine alternative dates will be returned. Feature/Service Availability Inquiry The Feature/Service Availability Inquiry, which provides information regarding the availability ofspecific features and services at a particular local serving office switch, will be available in allSBC/Ameritech service areas via the uniform application to application and GUI interfaces.Available features will be identified using USOCs, which vary between service areas due to productand tariff differences. This inquiry will be first introduced in the Ameritech service area as part ofthe functionality addition to the current EDI interface in April 2000. This same Feature/ServiceAvailability information will also continue to be available in all service areas as a Data Validationfile. Network Channel/Network Channel Interface (NC/NCI) Inquiry The Network Channel (NC) and Network Channel Interface (NCI) Codes Inquiry will be available inall SBC/Ameritech service areas via the uniform application to application and GUI interfaces. Thisinquiry provides for the validation of Network Channel (NC) and Network Channel Interface (NCI)codes and their combinations prior to submitting a local service request. This inquiry will be firstintroduced in the Ameritech service area as part of the functionality addition to the current EDIinterface in April 2000, and first available in the SNET service area with the implementation of theuniform application to application and GUI interfaces in that service area. Pending Order Status Inquiry The Pending Order Status Inquiry will be available in all SBC/Ameritech service areas via theuniform application to application and GUI interfaces. A list of pending service order informationwill be provided by working telephone number and detailed service order information will beavailable using multiple search criteria. This inquiry will be first introduced in the Ameritech andSNET service areas with the implementation of the uniform application to application and GUIinterfaces in those service areas.

Ham Attachment 3237

PIC/LPIC Inquiry The PIC/LPIC Inquiry provides a list of current Primary Interexchange Carrier (PIC) and IntraLATAPrimary Interexchange Carrier (LPIC) codes for carriers providing service at a particular localserving office switch. This inquiry will be available in all SBC/Ameritech service areas via theuniform application to application and GUI interfaces. PIC/LPIC Inquiry will be first introduced inthe SNET service area with the implementation of the uniform application to application and GUIinterfaces in that service area. This same information will continue to be available in all serviceareas as a Data Validation file. Telephone Number Availability The Telephone Number Availability function will be available in all SBC/Ameritech service areasvia the uniform application to application and GUI interfaces. The Telephone Number Availabilityfunctions supported in the uniform application to application and GUI interfaces will be inquiry,reservation, confirmation, and cancellation. The maximum number of available telephone numbersreturned in response to an inquiry will be ten, the quantity of telephone numbers that can be reservedin a single transaction will be one, and the telephone number reservation period will be standardizedat thirty calendar days. The following table summarizes the pre-ordering functions to be available in all SBC/Ameritechservice areas via the uniform application to application and GUI interfaces:

Inquiry Uniform Application to Application and GUIInterface

Address Validation Numbered, Unnumbered, Unnamed, Descriptive inquiry

WTN inquiry

Common Language Location Identifier(CLLI)

CLLI inquiry

Connecting Facility Assignment (CFA) CFA inquiry

Customer Service Information (CSI) ATN inquiry

WTN inquiry

Data Validation Files SAG, PIC/LPIC, Features/Services, Yellow Page Headings,USOCs

Direct:Connect, CD-ROM, Download via GUI

DSL Pre-qualification Inquiry Pre-qualification inquiry

DSL Loop Qualification Loop Qualification inquiry

Directory Listing Inquiry ATN inquiry

WTN inquiry

Dispatch Dispatch inquiry

Due Date Inquiry

Inquiry

Next available due date and 29 alternate dates available

Feature/Service Availability List of Features/Services by USOC

Ham Attachment 3238

Inquiry Uniform Application to Application and GUIInterface

NC/NCI Validation Validation inquiry

Pending Order Status Pending inquiry

PIC/LPIC List Code inquiry

Data Validation File

TN Availability

Inquiry

10 TNs

Reservation

1 TN

Confirmation

Cancellation

Ham Attachment 3239

C. Ordering All SBC/Ameritech service areas will implement a single uniform application to application orderinginterface. This interface will utilize EDI per industry guidelines, and will be based on OBF LSOG 4,TCIF ELMS 4, and the associated ASC X12 version 4020. These choices of guidelines andstandards levels are subject to discussion under the CMP. The uniform ordering application toapplication interface will be referred to as the “application to application interface” in the remainderof this ordering section of this plan. All SBC/Ameritech service areas will implement a uniform GUI to access ordering functions. Thepresentation of the GUI, which will be an enhanced version of the existing LEX application offeredin the SWBT and PB/NB service areas, will make use of the terminology employed in OBF LSOG 4,and have functionality similar to that offered via the uniform application to application interface.Attached to this document is the User Guide for the existing LEX application (see Attachment D).The uniform ordering GUI will be referred to as the “GUI” in the remainder of this ordering sectionof this plan. The uniform versions of the application to application and GUI interfaces will be deployed inmultiple phases. The uniform ordering GUI interface will be first implemented in March 2001 in theAmeritech service area. The uniform application to application interface will be first implementedin August 2001 in the SWBT and PB/NB service areas. The uniform GUI interface will beimplemented in those service areas at the same time. The uniform application to applicationinterface will be implemented in the Ameritech service area in September 2001. Both the uniformapplication to application and GUI interfaces will be implemented in the SNET service area inMarch of 2002. Uniform Ordering Message Flow 997 Transaction All service areas currently return a 997 transaction to the CLEC to acknowledge the receipt of datatransmission and expect a 997 transaction in response to transactions set to the CLEC. This practicewill be continued in the uniform application to application interface. 850/855 Transactions In the uniform environment, an 850 transaction will be sent until a positive 855 transaction isreceived regardless of the types of errors that may be detected. An 855 transaction will only be usedto return a response to the 850 in the format of an FOC or error notification. 860/865 Transactions In the uniform environment, all 860 transactions will be utilized to effect a change using the fullrefresh process or to respond to a negative 865 transaction to correct errors on an 860. The 865 willbe used for returning confirmation notices (FOCs and SOCs), error notices on 860 transactions,jeopardy notification notices and to advise CLECs of customer impacting provider initiated changes. Uniform Product Ordering

Ham Attachment 3240

SBC/Ameritech has established a process for evaluating the ordering requirements of its variousexisting interfaces and the appropriate industry standards and guidelines to enable the developmentof specifications for the uniform ordering application to application interface. Fields that identify who the customer is, how the request is tracked, and what services and activitiesare being requested, will be made uniform, e.g. use of USOCs to order features rather than SOSCcodes, uniform use of NC, NCI, SECNCI combinations, and use of uniform activity types. The uniform application to application and GUI interfaces will be adapted to accommodate anyproduct submitted electronically. This includes Resale, Loop, Number Portability, Loop withNumber Portability, Port, Loop with Port combination as well as varieties of these products. Productavailability will not change due to implementation of the uniform interfaces, i.e. some productsbelow may not be offered in all service areas. When OBF guidelines exist, and where the product is offered, the ordering process for the productwill follow the OBF guideline, taking into consideration service area-specific provisioning needs. Ifno OBF guideline is available, and the product is offered in multiple service areas, a uniformSBC/Ameritech guideline will be developed which will encompass regional provisioning needs. Ifno OBF guideline is available and the product is offered in only one service area, existing regionalguidelines will remain in place. Ordering of all product varieties listed in the table below will be supported by the uniformapplication to application and GUI interfaces. The table also indicates which service areas offereach product, and whether an OBF guideline for ordering of that product currently exists.

PRODUCT VARIETIES

OBFSTANDARD

SWBT PB/NB Ameritech SNET

RESALE • Resale Basic Exchange X X X X X• Resale Centrex X X X X X• Resale Private Line X X X X X• Resale ISDN PRI X X X X• Resale ISDN BRI X X X X• Resale Advance Digital Trunking Services (DS1 Trunk) X X X X• Resale Base Rate Service (56kb) X X• Resale DS1, DS3 (Line Side) X X X X• Resale DID X X X X X• Resale PBX X X X X X• Resale Foreign Exchange X X X• Resale Off Premise Extension X X X X• Resale Coin X X X X PORT • Basic Port X X X X X• Centrex Line Port X X X • Analog Trunk Port X X X X• DID Trunk Port X X X X• BRI Line Port X X X X• PRI Trunk Port X X X • DS1 Trunk Port X X X • DS1 Network Port X X LOOP with Basic PORT Combo X X X X X LOOP • Basic Loop X X X X X• Includes ISDN, xDSL, PBX, DS1 X X X X X NUMBER PORTABILITY

Ham Attachment 3241

PRODUCT VARIETIES

OBFSTANDARD

SWBT PB/NB Ameritech SNET

• Stand-alone X X X X X• With Loop X X X X X MISC • Listings X X X X X

Processes for the Listing and E-911 services associated with ordering products listed above havebeen analyzed in concert with the product offerings. Service area-specific differences do exist on thebasis of tariff product offerings and contract arrangements with publishing companies as described inthe PMO section of this document. Listings or E-911 information not included in the Resale or UNEproduct offerings will be handled directly with the Directory or E-911 service provider outside of theuniform ordering application to application and GUI interfaces as is currently done. The data field-level specifications for the uniform ordering interfaces will be developed with CLECinput per the timeline established by the Change Management Process. These specifications will bedeveloped in a manner similar to those for pre-ordering as shown in the sample specifications(Attachment C). The existing ordering application to application interface offered by SBC/Ameritech, the LEX GUIapplication available in the SWBT and PB/NB service areas, will be enhanced during 2000specifically with respect to the ordering of unbundled DSL-capable loops. These enhancementscome in response to the FCC’s Line Sharing Order (Third Report and Order in Docket 98-147 andFourth Report and Order in Docket 96-98), CLEC requests, and in response to requirements in theFCC’s SBC/Ameritech Merger Conditions on the ordering of unbundled DSL-capable loops.SBC/Ameritech continues to discuss and provide information on these enhancements through theChange Management Process.

Ham Attachment 3242

D. Provisioning As described in the PMO, based on the nature of the function, some provisioning functions are madeavailable via the pre-ordering interfaces while others are made available via the ordering interfaces.Therefore, the uniform version of these provisioning functions will be available in each service areain accordance with the schedules for the implementation of the uniform versions of the pre-orderingand ordering interfaces. Jeopardy Notification Jeopardy Notification is used when alerting the CLEC that a situation has been encountered in theprovisioning of an order that will potentially cause the confirmed due date to be missed. Jeopardy notification will continue to be provided in all SBC/Ameritech service areas. It will beavailable via the uniform ordering application to application interface using the 865 transaction, andwill be a function of the uniform ordering GUI interface. Service Order Completion Service Order Completion, which is a notification to the CLEC that the work requested on apreviously provided purchase order (or request) has been completed, will continue to be provided byall SBC/Ameritech service areas via the uniform ordering application to application interface usingthe 865 transaction, and will be a function of the uniform ordering GUI interface. Loss Notification All SBC/Ameritech service areas will continue to provide Loss Notification. This notification alertsthe CLEC that a change requested by another Telecommunications Carrier (TC) has been completedand, as a result, the Local Service Provider associated with a given telephone number has beenchanged. It will be provided via the uniform ordering application to application interface using the836 transaction, and will be available via the uniform ordering GUI interface. Pending Order Status Pending Order Status will be available in all SBC/Ameritech service areas via the uniform pre-ordering application to application and GUI interfaces. This will be the introduction of this functionin the Ameritech and SNET service areas. Posted Order Status Posted Order Status will continue to be available in the SWBT service area via the uniform pre-ordering application to application and GUI interfaces. Since the capability to provide this functiondoes not currently exist within Ameritech, PB/NB, and SNET, and it is therefore also not available toretail customer service representatives in those service areas, it will not be made in those serviceareas. Provisioning Order Status Provisioning Order Status will be available in all SBC/Ameritech service areas via the uniform pre-ordering application to application and GUI interfaces. This will be the introduction of this functionin the Ameritech and SNET service areas. The input and output fields for this function will be madeuniform to the extent allowed by the service order data available in the source backend OSS.

Ham Attachment 3243

E. Maintenance and Repair SBC/Ameritech will continue to offer an application to application interface in all service areas.This uniform application to application interface will be similar to the current EBTA interfaceoffered in the SWBT, PB/NB, and Ameritech service areas, and be based on ANSI standardsT1.227:1995, T1.227a:1998, and T1.228:1995 developed by the T1M1 committee. This applicationto application interface will support the set of data attributes defined by the standards in a mannerconsistent with those standards. This list of supported attributes is contained in a table later in thisMaintenance and Repair section of this document. SBC/Ameritech will also continue to offer a GUI interface for maintenance and repair in all serviceareas. The uniform GUI application offered by SBC/Ameritech will be similar in functionality andpresentation to the EBTA GUI available in the Ameritech service area. The GUI will provide auniform presentation to end users in all service areas, and have functionality equivalent to that of theuniform EBTA application-to-application interface. Attached to this document is the User Guide forthe existing EBTA GUI application (see Attachment E). As a first phase toward the uniform application to application and GUI interfaces, SBC/Ameritechwill enhance its current application to application interface and GUI in the Ameritech service area insecond quarter of 2000. The following business functionality will be added: • MLT Testing functionality for application to application and GUI

This will enable CLECs to test resold POTS and loop with port. This will allow a fasterdetermination of the trouble source without Ameritech manual intervention. This ability willallow a CLEC to test the loop while the customer reporting the trouble is still on the call. The application to application interface will be compliant with the ANSI T1.262 industrystandard. The EBTA GUI will provide equivalent functionality.

• GUI edits to conform to TRFD3 (ECIC Trouble Report Format Definition)

This enhancement will reduce the amount of information necessary to report trouble on aPOTS or loop with port line by using enhanced industry guidelines. This will simplify andstreamline the process for reporting troubles through the GUI, and will give the GUIfunctionality equivalent to that of the application to application interface.

• GUI Activity Duration window to show billable hours

The Activity Duration window will provide the CLEC with information on what type ofrepair activity occurred (e.g., dispatch, after hours repair) while clearing a special servicestrouble. This will supply details on the duration of each activity and whether or not it wasbillable, and will give the GUI functionality equivalent to that of the application toapplication interface.

Ham Attachment 3244

MLT testing will be made available in the Ameritech service area in April 2000. The other twochanges, the TRFD3 edits and the Activity Duration window enhancement, will be made available inJune 2000. As a further step toward uniform functionality, SBC/Ameritech will enhance its application toapplication and GUI interfaces in the SWBT and PB/NB service areas to support the abbreviatedidentification code for message trunks, commonly referred to as the “2/6 code”. This change will bemade in the SWBT service area in September 2000 and in the PB/NB service area in June 2001. The final step to uniformity will be the deployment in each service area of an updated version of theEBTA application to application interface and the enhanced EBTA GUI interface. These interfaceswill be deployed in the SWBT, PB/NB, and Ameritech service areas in September 2001 and inMarch 2002 in the SNET service area. As previously described, the updated version of theapplication to application interface will support the standard set of attributes in a manner consistentwith industry standards. The uniform GUI interface will support a consistent set of functions in allservice areas. The set of functions is detailed in a table below. The following table details the data attributes that will be supported by the uniform application toapplication interface:

ATTRIBUTE LABEL

Uniform Interface

ActivityDuration

Supported with Limitations

AdditionalTroubleInfoList Supported per Standard AdditionalTroubleStatusInfo Supported per Standard AgentContactPerson Supported per Standard AuthorizationList

Supported per Standard

CalledNumber Supported per Standard CancelRequestedByManager Supported per Standard closeOutNarr Supported per Standard commitmentTime Supported per Standard commitmentTimeRequest Supported per Standard closeOutVerification


custTroubleTickNum Supported per Standard customerWorkCenter Supported per Standard escalationList


aLocationAccessAddress


ZLocationAccessAddress


AlocationAccessHours


ZlocationAccessHours


aLocation Access Person


zLocationAccessPerson


MaintServiceCharge


Ham Attachment 3245

ATTRIBUTE LABEL

Uniform Interface

managedObjectInstance


managedObjectInstAliasList Supported per Standard managerContactPerson


perceivedTroubleSeverity


preferredPriority


receivedTime Supported per Standard repeatReport


restoredTime Supported per Standard troubleClearancePerson


troubleDetectionTime Supported per Standard troubleFound Supported per Standard troubleReportFormatObjectPtr


troubleReportFormatIdentifier Supported per Standard troubleReportID Supported per Standard tRMustBePresentAttrIdList Supported per Standard tRMayBePresentAttrIdList Supported per Standard troubleReportState Supported per Standard troubleReportStatus Supported per Standard troubleReportStatusTime Supported per Standard trouble Report Status Window Supported per Standard trouble Type Supported per Standard tsp Priority Supported per Standard customerInfo Supported per Standard

The following table details the business functions that will be supported by the GUI interface. Theinformation input into the GUI’s fields will be mapped to the same locations, in the back end OSS,as the application to application interface.

FUNCTION

EBTA GUI

Create Circuit Types Access Hours Narrative Trouble Type Dispatch Authorization Contact information TSP Priority Status Interval Comments /Notes

Telcordia valid circuit ids test and premise access hrs Yes Yes Yes Yes Yes Yes Yes

Cancel Yes Modify info after create Yes Messaging Yes Get Status (refresh) Yes Modify Yes Proactive Statusing Yes Escalations Yes Clear / Close Yes Trouble History Yes

Ham Attachment 3246

MLT Test Yes Status notification Yes Estimated Repair Time Yes WEB Version Yes Circuit Security Supports MCN, ACNA, orCCNA

Yes

Close out Narrative Yes

Ham Attachment 3247

F. Billing Billing as delivered by SBC/Ameritech is substantially in accordance with the applicable industrystandards and guidelines. For example, Bill Data Tape (BDT) output standards are mature, sincethey have been used for access billing for several years. The use of BDT in SBC/Ameritech islargely consistent with those standards. The industry evolved ahead of the formulation of industryEMI guidelines, so variations from current guidelines exist in the EMI implementations in thevarious SBC/Ameritech service areas. SBC/Ameritech will align the essential elements of theseEMI implementation attributes consistent with industry guidelines and direction. Ameritech andSNET adopted a former Telcordia standard for Resale electronic bill presentation, while the EDI 811transaction set is used for this purpose in the SWBT and PB service areas. All service areas will nowadopt the EDI 811 transaction set for this purpose. Billing Data Tape (BDT)

All SBC/Ameritech service areas produce BDT that is consistent with the most current version of theapplicable guidelines. All service areas adhere to the Technical Review Group (TRG) version release schedule. Versionreleases are implemented twice per year during two separate industry established three-monthperiods. All service areas are currently producing Version 32 Billing Data Tapes. Exchange Message Interface (EMI) SBC/Ameritech will standardize throughout its service areas on the suite of resolved OBF issues thattarget the local market. Detail on provisions for these OBF issues will be documented in a singleSBC/Ameritech user guide that will encompass all SBC/Ameritech service areas. SBC/Ameritechwill also provide consistent 60-day notification of planned EMI changes prior to the scheduledimplementation date via the Accessible Letter process. SBC/Ameritech will continue to provide thesame Usage Data Packaging currently offered. These modifications to the SBC/Ameritechimplementations of EMI will be implemented in the SWBT, PB/NB, and Ameritech service areas inApril 2001, and in the SNET service area in October 2001. Media Delivery methodology will be made uniform. Connect:Direct, File Transfer Protocol (FTP),and magnetic tape will be offered. This uniformity in media offered will be effective in the SWBT,PB/NB, and Ameritech service areas in August 2000, and in the SNET service area in February2001.

Ham Attachment 3248

To provide consistency in application of industry guidelines, SBC/Ameritech will provide themodifications as shown on the following table:

Function Proposed Future Method ofOperation

Work Required


Bill Media &Version EMI records sent toCLECs in Daily UsageExtract: Header/Trailer Toll Specialized Services -Custom callingfeatures New Class featurerecord Local D/A Operator Verification Operator Interrupt Credits Switched Dataservices UNE SpecificRecords: CABS MTS,TerminatingIntraLATA UNE UNE Originated,InternationalTerminated Terminating LocalUNE

202401/02 Also implement new2024xx/xx H/T’s 10-01-01 10-01-18 10-01-19 10-01-31 10-01-32 10-01-35 10-01-37 41-xx-xx 01-01-62 110101 110201 110131 110132

Eliminate 202001/02and 202101/02 Implement new2024xx/xx H/T’s No change required. No change required. Move Class Featuresfrom 10-01-18 record to10-01-19 No change required. No change required. No change required. No change required. Eliminate 03-01-01records and implement41-xx-xx records. No change required. No change required.

Eliminate 202101/02and 202109/10 Implement202401/02 Implement new2024xx/xx H/T’s No change required. No change required. No change required. No change required. No change required. No change required. No change required. Eliminate 03-01-01records. Implement 01-01-62 Implement UNEconsistentlythroughoutSBC/Ameritechusing the EMIrecords listed in theFMO.

Eliminate 202101/02 Implement 202401/02 Implement new2024xx/xx H/T’s No change required. No change required. Move Class Featuresfrom 10-01-18 recordto 10-01-19 No change required. No change required. No change required. No change required. Eliminate 03-01-01records and implement41-xx-xx records. No change required. Implement UNEconsistentlythroughoutSBC/Ameritech usingthe EMI records listedin the FMO.

Implement new2024xx/xx H/T’s No change required. No change required. Move Class Featuresfrom 10-01-18 recordto 10-01-19 No change required. No change required. No change required. No change required. No change required. Implement 01-01-62 Implement UNEconsistentlythroughoutSBC/Ameritechusing the EMIrecords listed in theFMO.

Ham Attachment 3249

Function Proposed Future Method ofOperation

Work Required


D/A (carrier involved) Terminating Access Originating 800 Originating 500

110120 110125 110126

Guidelines

SBC/Ameritechfollows OBF EMIformat. OBF issues areevaluated bySBC/Ameritech andimplemented based onbusiness needs andcontractualcommitments.

Follows the industryaccepted OBF EMIformat for messageexchange.




Delivery Media


No change required Implement Dial up Implement Tape andDial up.

No change required.

User Guide – mediaoffer on

SBC/Ameritech UserGuide to be availablevia the Internet.

Develop the SBC UsageExtract guide and Webpresentation.

Develop the SBCUsage Extract guide.



User Guide –Publicationnotification process

SBC/Ameritech tosupply a 60 daynotification via theAccessible Letterprocess.

No change required. CLECs will benotified through anaccessibility letter 60days in advance ofany changes to EMIrecords that couldimpact them

CLECs will be notifiedthrough anaccessibility letter 60days in advance of anychanges to EMIrecords that couldimpact them

CLECs will benotified through anaccessibility letter 60days in advance ofany changes to EMIrecords that couldimpact them

As noted previously, locally negotiated records for service area-specific products will continue to beprovided in the daily usage file. Details will be documented in the SBC/Ameritech user guide.Approved OBF guidelines, as appropriate, will continue to be implemented by SBC/Ameritech.

Ham Attachment 3250

Electronic Data Interchange (EDI) All SBC/Ameritech service areas will use the EDI 811 transaction set, following an approved versionof Telecommunications Industry Forum guidelines (currently Issue 9), for creation of resale bills.Use of the EDI 811 transaction set for resale bills is a commonly accepted industry practice, and willbe available in the Ameritech service area in January 2001, in NB in April 2001, and in the SNETservice area in October 2001.

Function Uniform

Electronic DataInterchange (EDI)

Existing EDI Functionality by Region

SWBT PB/NB

SNET

AMERITECH

Bill Format andVersion

X12 EDI 811 TSimplementation of auniform approvedversion of TCIFGuidelines

Currently providingthe selected uniformapproved version ofTCIF Guidelines –Issue 9.

PB – Currentlyproviding the selecteduniform approvedversion of TCIFGuidelines – Issue 9.

NB – Will implementX12 EDI 811 TS usingselected uniformapproved version ofTCIF Guidelines.

Will implement X12EDI 811 TS usingselected uniformapproved version ofTCIF Guidelines.

Will implement X12EDI 811 TS usingselected uniformapproved version ofTCIF Guidelines.

Industry Guidelines An approved versionof TCIF Guidelines –Currently Issue 9. Atwww.atis.org inPDF format.

TCIF Guidelines –Issue 9. Available atwww.atis.org

PB - TCIF Guidelines –Issue 9. Available atwww.atis.org NB – Will implementan approved version ofTCIF Guidelines – Issue9 or later.

Will implement anapproved version ofTCIF Guidelines –Issue 9 or later.

Will implement anapproved version ofTCIF Guidelines –Issue 9 or later.

DeliveryMethodology

Provide delivery ofdata via Value AddedNetwork (VAN) orConnect:Direct.

Will provide deliveryof data via VAN orConnect:Direct.

Will provide delivery ofdata via VAN orConnect:Direct.



User GuideAvailability

At www.sbc.com inPDF format.

Will be made availableat www.sbc.com inPDF format.

Will be made availableat www.sbc.com inPDF format.

Will be madeavailable atwww.sbc.com inPDF format.

Will be madeavailable atwww.sbc.com inPDF format.

Change notification

90 days for versionX12, TCIF, or EDIgenerated changes(e.g., version orstructure changes).

30 days for datarelated changes (e.g.,new services billed).

Will conform touniform changenotificationcommitments.




Online Viewing/GUI There are no plans to create an on-line access capability for viewing bill images. Lack of currentCLEC utilization of the SBC/Ameritech Bill Info application for billing, available in the SWBT

Ham Attachment 3251

service area, and the absence of expressed interest during a prior CLEC collaborative billing forumsuggest there is no business need for this capability. Product Billing System Alignment SBC/Ameritech will modify its systems to provide consistent billing system orientation forunbundled network products. Billing systems in the Ameritech service area will be modified to alignthe billing for Line-Side Port unbundled products through a BDT bill format. This change will becompleted in October 2001.

Ham Attachment 3252

G. Connectivity To standardize CLEC connectivity among its service areas, SBC/Ameritech will build a dedicatedRemote Access Facility (RAF) in both Ameritech and SNET. This ARAF and SRAF, along with theexisting SWBT LRAF and PB/NB PRAF will provide CLECs dedicated access to the uniformapplication to application and Graphical User Interfaces. Internet access will also be provided forthese uniform GUIs. Each of the four RAFs will use TCP/IP protocol and will be configured with: 1) routers capable ofterminating private line or frame relay connections, and 2) access servers to terminate analog modemand ISDN dial-up connections. SBC/Ameritech will install and maintain these routers and willprovide CLECs with specifications for the DSU/CSUs that are to be placed on both ends of thecircuit. CLECs will provide their own circuit to the ARAF, the DSU/CSUs, as well as connectorsand cabling from their CSU/DSU to the SBC/Ameritech router. Application to application interfaceswill be accessible only via the CLEC’s private line or frame relay connection to the RAF and willnot be accessible by a dial-up connection or the Internet. Common security will be provided by SBC/Ameritech’s firewall systems that will use access lists toauthorize RAF users access to designated OSS. Dial-up access users of the GUI interface(s) will passthough the same security methods as private line/frame relay users but must also authenticate uponconnecting to the SBC/Ameritech access server by supplying a unique User ID and password pair tolog onto the SBC/Ameritech network. When a CLEC wants to use Internet access, SBC/Ameritechwill utilize Digital Certificates to secure access. Uniform GUIs can be accessed through either aregional RAF or the Internet. Documentation describing connectivity requirements and procedures for each of the regional RAFswill be standardized and made available to CLECs desiring connectivity to SBC/Ameritech’s OSS.As an example of this documentation, a guide for the existing LRAF is attached (see Attachment F).Once the ARAF and SRAF go into production in the fourth quarter 2000, any CLEC wanting toestablish connectivity for the first time or CLECs wanting to upgrade their existing connection inthose service areas, will be provided specifications for connecting to the dedicated facility. CLECconnections to any other facility within the Ameritech or SNET service areas will becomegrandfathered and no new CLEC connections will be made to such non-dedicated facilities. Below is a list of items and functions regarding connectivity that will become the future method ofoperation in all SBC/Ameritech service areas for secured access to SBC/Ameritech’s OSS.

• Dedicated CLEC Facility• Private Line / Frame Relay connections• Dial-up Connections• SBC/Ameritech provides and maintains routers• TCP/IP protocol used• CLEC provides circuit, CSU/DSUs, connectors and cables• CLEC provides publicly registered IP addresses for both ends of the private line or frame

relay connection• SBC/Ameritech installs and maintains CSU/DSUs• Internet access (available for GUIs only) is secured by use of Digital Certificates

Ham Attachment 3253

• Standard CLEC connectivity documentation• Grandfather existing CLEC connectivity arrangements

In some cases, to make use of the SBC/Ameritech OSS interfaces via a dedicated regional RAF,certain software requirements must be met by the accessing CLEC.

• For pre-ordering application to application EDI access, Interactive Agent software perthe Electronic Commerce Implementation Committee (ECIC) Interactive Agentspecification will be used. For the CORBA protocol, non-repudiation of EDI requestswill not be supported and message receipts will be required. CORBA security will be inaccordance with T1M1 T1.265 security specifications.

• The pre-ordering and/or ordering GUI will be accessed via browser software, such as

Internet Explorer (version 4.0 or greater) or Netscape Navigator (version 4.0 or greater.)Communications will be secured with the Secure Socket Layer (SSL), X.509 digitalcertificates and individual user IDs and passwords.

SBC/Ameritech will provide a centralized point of contact for handling OSS connectivity andinterface application questions from CLECs across all the SBC/Ameritech service areas. This Centerwill be staffed with managers who are trained on both uniform and service area-specific OSS andwill be dedicated to supporting CLEC users only. A centralized group will be designated to handleCLEC requests for User IDs and for Digital Certificates.

Ham Attachment 3254

H. Documentation

Current and Uniform Interface Documentation

The following table summarizes the current documentation available to CLECs supporting theelectronic OSS interfaces associated with local exchange services.

UNIFORM SWBT PB/NB AIT SNETProduct InformationDocument

• CLECHandbook

• CLECHandbook

• Resale OrderGuide

• UnbundledElement OrderingGuide

• CMIS Guide• CLEC Order

Guide

Order RuleInformation Document

• LSOR• LSPOR

• LSOR• LSPOR• Resale Users

Guide (RUG)• ISR User Guide

• Product Matrices • CMIS Guide• CLEC Order

Guide

Pre-ordering,Ordering, andProvisioning UserGuide (GUI)

• LEX UserGuide

• Verigate CLECUser Guide

• Order StatusUser Guide

• ProvisioningOrder StatusUser Guide

• LEX User Guide• Verigate CLEC

User Guide• Order Status

User Guide• Provisioning

Order StatusUser Guide

NA • W-CIWin UserGuides

• EF User Guides• SNAP User Guides

Pre-ordering,Ordering andProvisioning EDIImplementationGuide

• Refer to TCIFSOSC Matrices

• Refer to TCIFSOSC Matrices

• ElectronicService OrderGuide

• CMIS Guide

Maintenance andRepair User Guide

• TroubleAdministrationUser Guide

• PBSM UserGuide

• EBTA UserGuide

• CMIS Guide

Billing User Guide • BDT• EMI User

Guide• EDI User

Guide

• BDT• EMI – CLEC

Handbook

• BDT• EMI – CLEC

Guide

• BDT• EMI – User Guide

A common suite of documentation will be developed to support the uniform interfaces. Uniformdocumentation will likely consist of a product information document, an order rule informationdocument, GUI user guides, and an EDI implementation guide. The choice of specificdocumentation format and content will be determined with CLEC input through CMP meetingsscheduled for this purpose.

Ham Attachment 3255

I. Timeline

FCC FMO Timeline -- Release Schedule Milestones Availability Date OSS Interfaces Use of Accessible Letter for Notification (Ameritech)• Implementation 4/1/2000 Pre-ordering, Ordering, and Provisioning Pre-ordering Functionality Addition (Ameritech)• Release Announcement 12/16/1999• Initial Release Requirements 1/14/2000• CLEC Testing Start Date 3/18/2000• Implementation 4/3/2000 Uniform Pre-ordering Application-to-Application Interface (Ameritech)• Release Announcement 9/2000• Final Release Requirements 11/2000• CLEC Testing Start Date 1/2001• Implementation 3/2001 Uniform Pre-ordering Graphical User Interface (Ameritech)• Release Announcement 2/2001• Release Requirements and User Guide Documentation 2/2001• Implementation 3/2001 Uniform Ordering Graphical User Interface (Ameritech)• Release Announcement 2/2001• Test Environment Access, Release Requirements and User Guide Documentation 2/2001• Implementation 3/2001 Uniform Pre-ordering Application-to-Application Interface (SWBT, PB/NB, SNET)• Release Announcement 12/2000• Final Release Requirements 2/2001• CLEC Testing Start Date 4/2001• Implementation 6/2001

Ham Attachment 3256

Uniform Pre-ordering Graphical User Interface (SWBT, PB/NB, SNET)• Release Announcement 5/2001• Release Requirements and User Guide Documentation 5/2001• Implementation 6/2001 Uniform Ordering Graphical User Interface (SWBT, PB/NB)• Release Announcement 7/2001• Test Environment Access, Release Requirements and User Guide Documentation 7/2001• Implementation 8/2001 Uniform Ordering Application-to-Application Interface (SWBT, PB/NB)• Release Announcement 2/2001• Final Release Requirements 4/2001• CLEC Testing Start Date 6/2001• Implementation 8/2001 Uniform Ordering Application-to-Application Interface (Ameritech)• Release Announcement 3/2001• Final Release Requirements 5/2001• CLEC Testing Start Date 7/2001• Implementation 9/2001 Uniform Ordering Graphical User Interface (SNET)• Release Announcement 2/2002• Test Environment Access, Release Requirements and User Guide Documentation 2/2002• Implementation 3/2002 Uniform Ordering Application-to-Application Interface (SNET)• Release Announcement 9/2001• Final Release Requirements 11/2001• CLEC Testing Start Date 1/2002• Implementation 3/2002

Ham Attachment 3257

Repair and Maintenance MLT EBTA and GUI Enhancements (Ameritech)• Release Announcement 1/2000• Initial Release Requirements 2/2000• CLEC Testing Start Date Negotiated• Implementation 4/3/2000 TRFD3 and History Window GUI Updates (Ameritech)• Release Announcement 1/2000• Release Requirements and User Guide Documentation 5/2000• Implementation 6/2000 2/6 Code EBTA and GUI Enhancement (SWBT)• Release Announcement 4/2000• Final Release Requirements 5/2000• CLEC Testing Start Date Negotiated• Implementation 9/2000 2/6 Code EBTA and GUI Release (PB/NB)• Release Announcement 1/2001• Final Release Requirements 2/2001• CLEC Testing Start Date Negotiated• Implementation 6/2001 Uniform EBTA Release (SWBT, PB/NB, Ameritech)• Release Announcement 4/2001• Final Release Requirements 5/2001• CLEC Testing Start Date Negotiated• Implementation 9/2001 Uniform EBTA GUI Release (SWBT, PB/NB, Ameritech)• Release Announcement 5/2001• Release Requirements and User Guide Documentation 8/2001• Implementation 9/2001

Ham Attachment 3258

Uniform EBTA Release (SNET)• Release Announcement 10/2001• Final Release Requirements 11/2001• CLEC Testing Start Date Negotiated• Implementation 3/2002 Uniform EBTA GUI Release (SNET)• Release Announcement 11/2001• Release Requirements and User Guide Documentation 2/2002• Implementation 3/2002 Billing EMI Uniform Delivery Medium and User’s Guide (SWBT, PB/NB, Ameritech)• Release Announcement 6/2000• Implementation 8/2000 EMI Uniform Delivery Medium and User’s Guide (SNET)• Release Announcement 12/2000• Implementation 2/2001 EDI 811 Implementation (Ameritech)• Final Release Requirements 12/2000• Implementation 3/2001 EMI Uniform Record Types (SWBT, PB/NB, Ameritech)• Final Release Requirements 1/2001• Implementation 3/2001 EDI 811 Implementation (NB only)• Final Release Requirements 1/2001• Implementation 4/2001 Wholesale Product Billing System Conversion (Ameritech)• Final Release Requirements 7/2001• Implementation 10/2001

Ham Attachment 3259

EDI 811 Implementation (SNET)• Final Release Requirements 7/2001• Implementation 10/2001 EMI Uniform Record Types (SNET)• Final Release Requirements 8/2001• Implementation 10/2001 Connectivity Ameritech RAF• Implementation 12/2000 SNET RAF• Implementation 12/2000 IS Call Center• Implement support for Ameritech and SNET regions 12/2000

Ham Attachment 3260

IV. Glossary

2/6 Code TIRKS “shorthand” abbreviation for Trunk Group

ACNA Access Carrier Name Abbreviation

AEBS Telcordia (formerly Bellcore) billing format standard.

Ameritech The five-state operating region of SBC/Ameritech which encompasses the statesof Illinois, Indiana, Michigan, Ohio and Wisconsin.

ANSI American National Standards Institute

ARAF The data communications facility that provides a secure network interface fromCLEC networks to Ameritech’s Data Communications Network (DCN).

ASC Accredited Standards Committee - A designation for a industry body that hasbeen given accreditation by the American National Standards Institute to issueANSI standards. X12 and T1 are examples of such committees.

ASOG Access Service Order Guidelines - The industry standard format documentationdeveloped under the auspices of Ordering and Billing Forum (OBF) for theordering of access services

ASR Access Service Request - The industry standard format developed under theauspices of Ordering and Billing Forum (OBF) for the ordering of accessservices.

ATIS Alliance for Telecommunications Industry Solutions

BDT Bill Data Tape - Bill detail created in CABS which is predicated by the BillingOutput Specifications (BOS) national standards.

BOS Billing Output Specifications

CARE Carrier Access Record Exchange

CCNA Carrier Customer Name Abbreviation

CESAR - ISR Customer's Enhanced System for Access Requests – Interconnection ServiceRequest - Is a “gateway” for several applications. It is utilized in the PB/NBservice area for pre-ordering for Resale and Unbundled Loops, and orderingfunctions for Unbundled Loops, Local Number Portability, and Interconnectiontrunks.

CLEC Competitive Local Exchange Carrier

CMIS Certified Local Exchange Carrier Mechanized Interface Specification - Adocument created to aid CLECs in preparation of an LSR for ordering UnbundledNetwork Elements and Resale Services in the SNET service area.

CMP Change Management Process - Process negotiated between ILEC and CLECs tocommunicate changes made to the Operational Support Systems

Connect:Direct A product of Sterling Commerce used to transport data files.

CORBA Common Object Request Broker Architecture (CORBA) is an industry standardprotocol for the mechanical exchange of data between computer systems.

Ham Attachment 3261

CPO Combined Platform Offering - An Ameritech unbundled network elementplatform (loop with port) offering.

DataGate An SBC/Ameritech proprietary application to application interface for themechanical exchange of pre-ordering information.

DSU/CSU Data Service Unit/Channel Service Unit. The DSU part of the unit is the deviceused in digital transmission for connecting Data Terminal Equipment (DTE),such as a router, to Data Communications Equipment (DTE) or to a service. TheCSU part of the unit is a digital interface device that connects end user equipmentto the local digital telephone loop. (DTE) and data circuit termination equipment(DCE) for terminals

EBTA Electronic Bonding Trouble Administration

ECIC Electronic Communications Implementation Committee (ECIC) is an industryforum that develops a common understanding of electronics communicationsstandards and develop guidelines for the implementation of electronicinformation exchange

EDI Electronic Data Interchange - An industry standard protocol for the mechanicalexchange of data between computer systems.

EMI Exchange Message Interface - Usage record format for message exchange whichis developed under the auspices of the Ordering and Billing Forum (OBF).

ESOG Electronic Service Order Guide - A document created to aid CLECs inpreparation of an LSR for ordering Unbundled Network Elements and ResaleServices in the Ameritech service area.

EXACT Exchange Access Control and Tracking - The industry standard for orderingaccess services.

FMO Future Method of Operation

FTP File Transfer Protocol - A common industry defined data transmission pollingprotocol.

GUI Graphical User Interface - A user-friendly presentation of data input screens.

GUI-Web Web based GUI

ILEC Incumbent Local Exchange Carrier

ISO International Standards Organization

ITU-T International Telecommunications Union - Telecommunication

JIA Joint Implementation Arrangement – arrangement between SBC/Ameritech andApplication to application customers regarding implementation of mandatory andoptional fields defined in T1M1.5 standard, as well as timing, security,measurements, etc.

LEC Local Exchange Carrier

LEX LSR Exchange - A GUI application available to CLECs for ordering LSR-basedlocal services from SBC.

Ham Attachment 3262

LRAF The data communications facility that provides a secure network interface fromCLEC networks to Southwestern Bell’s Data Communications Network (DCN).

LSOG Local Service Order Guidelines - The industry standard format documentationdeveloped under the auspices of Ordering and Billing Forum (OBF) for theordering of local service Resale, Number Portability, Unbundled NetworkElements (UNE) Loops and Ports.

LSOR A document created to aid CLECs in preparation of an LSR for orderingUnbundled Network Elements and Resale Services in the SWBT and PB/NBservice areas.

LSPOR A document created to aid CLECs with pre-ordering inquiries to exchangecertain information prior to the submission of an LSR for ordering UnbundledNetwork Elements and Resale Services in the SWBT and PB/NB service areas.

LSR Local Service Request - The industry standard format developed under theauspices of Ordering and Billing Forum (OBF) for the ordering of local serviceResale, Number Portability, Unbundled Network Elements (UNE) Loops andPorts.

M&P Methods and Procedures

MIB Managed Information Base

NPA Numbering Plan of North America

NXX Local Exchange Number

OBF Ordering and Billing Forum - The industry forum that develops the guidelines forordering Wholesale Local and Access services.

OSS Operation Support System

PB/NB Pacific Bell/Nevada Bell - The two-state operating service area ofSBC/Ameritech which encompasses the states of California and Nevada.

PIC/LPIC Primary Interexchange Carrier (PIC) and IntraLATA Primary InterexchangeCarrier (LPIC) – Codes assigned to interexchange (long distance) and intraLATA(local) carriers

PMO Present Method of Operation

PRAF The data communications facility that provides a secure network interface fromCLEC networks to the PB/NB Data Communications Network (DCN).

RAF The Remote Access Facility is the regional access point available to CLECs fordirect or dial-up connectivity to the SWBT and Facility

SBC The corporate entity which encompasses the Ameritech, PB/NB, SNET andSWBT service areas.

SNET Southern New England Telephone - The SBC/Ameritech service area whichincludes the state of Connecticut.

Ham Attachment 3263

SRAF The data communications facility that provides a secure network interface fromCLEC networks to Southern New England Telephone’s Data CommunicationsNetwork (DCN).

SWBT Southwestern Bell Telephone- The five-state operating service area ofSBC/Ameritech which encompasses the states of Arkansas, Kansas, Missouri,Oklahoma, and Texas.

T1M1 Industry standard body that develops inter-network operations standards andsupport the CORBA data model for pre-ordering.

TA Trouble Administration

TCIF Telecommunications Industry Forum - An industry standard body that producesthe EDI mechanization specifications for the LSOG.

TCNet A Web-based GUI available to CLECs that provides for the mechanical exchangeof pre-ordering information.

TCP/IP Transmission Control Protocol/Internet Protocol

TRFD3 Trouble Report Format Definition

UNE Unbundled Network Element

USOC Universal Service Order Code - The industry standard ordering codes associatedwith products and assigned by the Universal Service Order Standards atTelcordia.

Verigate A GUI available to CLECs that provides for the mechanical exchange of pre-ordering information.

W-CIWin Wholesale Customer Information Window - An SNET proprietary system thatfacilitates Resale and UNE order processing by enabling integrated access to theoperational support systems.

WSM Wholesale Service Manager - An Operational Support System that providesordering and flow through capability and data element validation for Resaleservices.

X.25 Developed by the ITU-T as an interface between data terminal operating in thepacket mode on public data networks

Ham Attachment 3264

Attachment A – Change ManagementProcess

Ham Attachment 3265

Attachment B – Verigate User Guide

Ham Attachment 3266

Attachment C – Uniform Pre-ordering DataField Detail Example

Ham Attachment 3267

Attachment D – LEX User Guide

Ham Attachment 3268

Attachment E – EBTA User Guide

Ham Attachment 3269

Attachment F – Interconnection User Guide

ham affidavit - attachment 32...2 ham attachment 32 in concert with phase 2 described in paragraph...

Documents