34
Accessible

PACIFIC BELL

Embed Size (px)

Citation preview

Page 1: PACIFIC BELL

Accessible

Page 2: PACIFIC BELL

“PACIFIC BELL - BDS Telis Testing Period and Ordering Changes to Prepare for December 2000 Retirement of CESAR ASR, ISR and WCSR”

Date: November 7, 2000

Number: CLECCS00-186

Contact: Account Manager

Online ASR testing period on the new BDS Telis platform has begun. As previously announced, Pacific Bell will stop accepting new or supplemental CESAR ASRs, ISRs and WCSRs at noon PST on Friday, December 1, 2000. BDS Telis provides customers with a replacement online system to create ASRs.

The BDS Telis platform is available for customer user ID testing and set-up now through Friday, December 1, 2000. Until November 17, 2000, customers can also create and send test ASRs to Pacific Bell using the BDS Telis platform. This testing period is intended to give customers an opportunity to get ready for the start of live ASR processing from BDS Telis, beginning at 7 am PST on Monday, December 4.

Customers who previously used the online CESAR ASR, ISR and WCSR ordering processes are encouraged to take advantage of this testing period. CESAR online customers will be able to connect to BDS Telis through existing PRAF firewall connections, but need to obtain BDS Telis User IDs. Please contact your Account Manager if you have not yet started this process.

In addition, attached please find updated ordering information along with job aids included in the September / October ASM Customer Workshops. Additional information or clarifications discussed during the customer workshops are enclosed in “boxes” within the document to aid workshop participants in reviewing this information. Please contact your SBC Account Manager if you need assistance or have additional questions. We appreciate your cooperation and support during this transition.

Attachment

Page 3: PACIFIC BELL

PACIFIC BELL & NEVADA BELLConversion to BDS TELIS & EXACT

CESAR ASR, ISR and WCSR will no longer accept customer service requests after December 1, 2000 (noon PST). This document contains ordering process changes originally published in Accessible Letters SWA99-203 and SWA99-204 (September 16, 1999), supplemented with job aids included in the September/October 2000 Access Systems Merger Customer Workshop training materials (ref: Accessible Letters SWA00-198, SWA00-199, CLECNS00-120, CLECCS00-129, CEL00-016, CEL00-017).

1) Project Overview - Access Systems Merger Project

Conversion Schedule:

Conversion DatePhase 1 Ordering and Billing (Special and Feature Group Switched Access Products)

Replacing CESAR ASR with December 4, 2000 ***

BDS Telis (Online) and EXACT (Batch)

Replacing P*B CABS with SBC CABS December 2000 Bills

Phase 2 Ordering * (Wireless Usage, Unbundled Network Elements, Interconnection)

Retirement of CESAR ISR December 4, 2000 ***

For LSR-Ordered Products & For ASR-Ordered Products

Retirement of CESAR ASR December 4, 2000 ***

Retirement of CESAR WCSR December 4, 2000 ***

* Billing conversion for Phase 2 products to be scheduled in 2001 ** Please see Attachment 2 for a list of replacement ordering processes for the Phase 2 products*** As of noon Dec. 1, 2000, CESAR will no longer be available for the processing of the above products.

(ref: Pacific Bell Accessible Letters SWA00-052, CEL00-007 and CLECCS00-025; Nevada Bell Accessible Letters: SWA00-053, CEL00-008 and CLECNS00-023). The retirement of CESAR ISR for LSR-ordered products has also been aligned with the retirement dates for CESAR ASR, ISR and WCSR (Accessible Letters CLECCS00-176, CLECNS00-165)

Systems Involved:

CESAR (Customers Enhanced System for Access Requests) is the incumbent Pacific Bell and Nevada Bell ordering system that prepares ASRs, WCSRs and LSRs for subsequent provisioning and/or billing activities.

BDS Telis ™ is an industry-standard ASR preparation software maintained by CAP Gemini (formerly Beechwood) system that runs on SBC’s UNIX platform in Dallas TX. Customers can access the Telis system from a personal computer with dial-out modem capability through the PRAF firewall.

1

Page 4: PACIFIC BELL

EXACT ™ (EXchange Access Control & Tracking) is an industry-standard ordering system that was centrally developed and maintained by TelCordia (Bellcore). Batch Access Service Requests (ASRs) transmissions are accepted by EXACT and prepared by SBC personnel for subsequent provisioning and/or billing activities.

P*B CABS (Pacific Bell Carrier Access Billing System) produces access, wireless, unbundled network element and interconnection bills for Pacific Bell and Nevada Bell customers.

SBC CABS (formerly called SWB CABS) is the SBC Customer Access Billing System which currently produces industry-standard access, wireless, unbundled network element and interconnection bills for customers in Southwestern Bell's five state territory. Pacific Bell and Nevada Bell billing will be migrated to SBC CABS beginning in December 2000.

- -

The remainder of this document republishes ordering conversion information from the September 1999 Accessible Letters and supplemental information from the September / October 2000 ASM Customer training workshop.

· For customers currently using CESAR ASR dial-up service, the replacement system offered is BDS-Telis (or Telis). Please see Section 2.1 below.

· For customers with systems capable of generating ASRs, current file transfer options (e.g., NDM, FTP) will continue to be used. (See Section 2.2)

Please note: Customers can elect to use either BDS Telis or a batch file transfer process by CCNA, but not both order methods concurrently.

· Other processing changes affecting both batch and online customers is discussed beginning with Section 2.3.

· Section 3 itemizes changes in preparation of ASR service requests.

2) Customer conversion activities required to convert to BDS Telis / EXACT processing2.1 Telis

2.1.1 What is Telis?

· BDS-Telis (or Telis) is a CAP Gemini™ system that runs on a UNIX platform in Dallas TX. Customers can access the Telis system from a personal computer with dial-out modem capability through the PRAF firewall.

· Telis supports electronic versions of the ASR and can be used to:

- Create ASRs from a blank screen or a template

- Verify the ASR contains valid information

- Store, display and update ASRs

- Electronically transfer ASRs to Pacific/Nevada Bell

- Issue supplements for ASRs

- Create and view ASR reports

- Receive acknowledgements and Firm Order Confirmations (FOCs) on line

- Create data reports using varied selection criteria

2.1.2 A copy of the Telis Users Manual can be obtained from the CAP Gemini web site at any time so you can become familiar with Telis functionality.

· The documentation can be found at the following internet web site:

http:// www.usa.capgemini.com/telis/default.htm

2

Page 5: PACIFIC BELL

· On this CAP Gemini web site, there are several documents listed. Pacific and Nevada Bell will be using the UNIX version of Telis. Please print the first document, listed as “TelisUnix22”.

2.1.3 How do I access Telis?

· The Telis platform in Dallas, Texas can be accessed through the PRAF using an existing PC with a modem using a terminal emulation / communication software package (e.g. Telnet, Procomm, Chameleon).

· Section 3 of the User Manual provides PC setup instructions.

2.1.4 Security

· Telis provides a secure environment where customers can create, submit and save their ASRs.

· Only employees the customer authorizes can access Telis.

· No customer can view another company’s ASR data.

· User Ids for Telis are required. Please contact your Account Manager to obtain an electronic copy of the Telis User ID Request Form.

· After submitting your request for Telis User Ids to your Account Manager, the IS Call Center (1-314-235-7225) will provide ongoing User ID and system connectivity support.

2.1.5 Training

· The Telis Users manual provides thorough documentation to help new Telis users get started. (http:// www.usa.capgemini.com/telis/default.htm)

· The Telis Help Desk (1-210-377-6100) provides on-line assistance in resolving Telis application problems.

2.1.6 Testing

· Customers will be able to create and submit California and Nevada test ASRs through the Telis production complex from October 16 through November 17, 2000.

· This testing period will allow customers to test their new Telis user Ids, practice connecting to Telis and navigating through the Telis screens.

· Before November 18, all California and Nevada ASRs sent from Telis to EXACT are assumed to be test ASRs and will not affect live production. As an added precaution, please clearly mark all test ASRs as “TEST ASRs” in the Remarks section.

· Customers are encouraged to use previously submitted ASRs when testing Telis. We will NOT delete test ASRs from BDS Telis, enabling customers to use their test ASRs as templates for future ASR submissions after December 4, 2000.

· BDS Testing will end on November 17, 2000 in order to prepare for live conversion.

· Even though customers cannot submit live ASRs from Telis to EXACT until December 4, Telis will remain available for customer set-up through December 1. During this period, customers can begin keying in new ASRs into Telis in anticipation of the December 4 conversion.

2.2 Batch File Transfer Options

3

Page 6: PACIFIC BELL

2.2.1 For those companies with internal systems capable of creating ASRs, NDM delivery option will continue to be offered. We will also support FTP transmission protocol upon request (same rules for NDM customers apply to FTP customers).

· Customers that currently use NDM to send their ASRs to CESAR will be able to use NDM to send their ASRs to EXACT.

· Ordering outputs - - acknowledgments, error files and Firm Order Completions (FOC) - - will be returned via NDM.

· Design Layouts Record will also be returned via NDM for customers using the NDM option

2.2.2 EXACT processing requires NDM customers to split their Nevada, Northern California and Southern California ASRs into separate files based on the ICSC code.

· Please note - - new ICSC codes will be established at conversion for EXACT processing. See Section 3.1.

2.2.3 NDM customers will receive their ordering outputs in three separate files - - Nevada Bell, Northern California and Southern California.

2.2.4 Customers requesting NDM connectivity to EXACT should request the appropriate electronic forms by contacting their Account Manager.

2.2.5 CESAR and EXACT data should not be combined on the same file.

· At the time of conversion, both Phase 1 and Phase 2 products will be converted from CESAR ASR to EXACT.

· Prior to December 1 (noon), batch ASR will continue to be accepted by CESAR.

· After 7 am on December 4, batch ASRs will only be accepted by EXACT.

· Customer orders will be directed to either CESAR or EXACT based on the NDM node.

· Likewise, customers should expect to receive CESAR FOCs and EXACT FOCs on separate files. (CESAR will continue to send return files for pipeline ASRs after the December 1-3 conversion. Please see Section 2.5)

2.2.6 Between now and December 4, all CESAR batch customers need to be converted to EXACT. Customers interested in moving from a dial-up service to a batch NDM arrangement, please contact your account manager. We would advise current CESAR ASR online users to convert to BDS Telis until we can plan and successfully convert you to batch processing in 2001.

Other Important Notes – ASR Processing

2.3 On-line Tools - - Toolbar 2.3.1 Toolbar is an on-line tool that provides dial-up access to various customer support functions. Loaded on the user’s PC, users can click on Toolbar buttons to initiate modem dialing procedures to access a specific ordering or billing-related function.

2.3.2 Toolbar will provide functionality previously provided by CESAR. For example:

· MAPS/PREMIS is available through the Verigate menu option to validate addresses

· NC/NCI data is available through Verigate NC/NCI validation

4

Page 7: PACIFIC BELL

Please note: MAPS functionality on the CESAR main menu will remain available after December 4, 2000 to ease the transition. Customers are encouraged to migrate to the Toolbar MAPS/PREMIS.

2.3.3 Please contact your Account Manager to request an electronic copy of the Toolbar application.

2.4 Confirmations2.4.1 NDM users will continue to receive confirmation via an NDM feed.

2.4.2 Telis users will receive confirmations via Telis

2.4.3 Confirmation records will be provided in accordance with MECH SPECS. No changes in the confirmation record are expected.

Please note - LSR processes were designed to return both Firm Order Confirmations (FOCs) and Service Order Completions (SOCs). ASR processes return FOCs only.

2.5 ASRs in the Pipeline at the Time of Conversion2.5.1 ASRs submitted through CESAR ASR will be completed through existing CESAR processes, unless the order is SUPPed

2.5.2 If a CESAR ASR order is subsequently SUPPed on or after December 4, 2000

· NDM users need to send the SUPP to EXACT. Please be sure to include the original PON number from the CESAR ASR so we can locate the original ASR in CESAR

· Telis users need to reenter the entire CESAR ASR through Telis. Please be sure to include the original PON number from the CESAR ASR so we can locate the original ASR in CESAR.

(Please note: ASRs originally entered through Telis can be SUPPed without reentering the ASR. Reentering the ASR being SUPPed through Telis only applies to ASRs originally entered in CESAR).

2.5.3 Firm Order Confirmations (FOCs) on CESAR ASRs and WCSRs will be returned through the current CESAR confirmation process. If the CESAR ASR or WCSR is SUPPed through EXACT, then the FOC will come from EXACT.

· Batch CESAR customers should continue to poll for return files after December 4 and until all of the pipeline CESAR ASRs have been completed, cancelled or SUPPed to EXACT.

· New ICSC codes for EXACT processing will take effect on December 4 (See Section 4.1). CESAR FOCs returned after December 1 will be returned without converting the ICSC code.

This same process will apply for any pipeline CESAR ISRs

For any ISR submitted through CESAR ISR prior to retirement on December 4, 2000.

· The ISR will be completed through existing CESAR processes, unless the order is SUPPed

· If a CESAR ISR order is subsequently SUPPed after the ISR retirement date, then the order needs to be reentered through the appropriate LSR or ASR process.

5

Page 8: PACIFIC BELL

· FOCs on CESAR ISRs will be returned through the current CESAR confirmation process. If the CESAR ISR is SUPPed, then the FOC will come from the appropriate LSR or ASR process.

2.6 Design Layout Records (DLRs)2.6.1 The current process for requesting DLRs through CESAR will be maintained for an interim period. Plans for moving this functionality to a new application are under development.

2.6.2 DLRs will continue to be delivered to NDM users through NDM.

2.7 CESAR Post Conversion2.7.1 CESAR functionality will be maintained for an interim period following the December 2000 conversion.

2.7.2 CESAR on-line customers should keep their CESAR connectivity to:

· Receive confirmations on CESAR service requests in the pipeline at conversion time

· Access DLRs on-line. As noted in the previous section, we expect to move requests for on-line DLRs will be moved to a new application in the near future

· Access CESAR history

A preview of the new CESAR menu screens effective December 4, 2000 can be found as Attachment 3.

2.8 Ordering of Wireless Type 1 DID and Type 1 Dial Lines2.8.1 Effective December 4, 2000, customers who currently order Type 1 DID and Type 1 Dial Line via CESAR WCSR will use a new “Line Side Product Request” form. A copy of this form can be found as Attachment 4. Customers can also obtain a soft copy of this form at:

[email protected]

2.8.2 Completed forms may be emailed to [email protected] or faxed.

3) Service request changes 3.1 Changes in ICSC codes

· ICSC codes for EXACT processing will be changed at conversion time. The following chart shows the current ICSC Code used for CESAR processing, along with the new ICSC Code for EXACT.

ICSC Code(current CESAR)

ICSC Code(new EXACT)

Nevada Bell NV06 SW06Northern CA PT04 SW04Southern CA PT02 SW02

3.2 Serial circuit ID changes· Serial Circuit ID formats will be changed for all new access services facilities

ordered through EXACT.

6

Page 9: PACIFIC BELL

· The new Serial Circuit ID format is the industry standard format currently used at Southwestern Bell and is 3 positions shorter than the current Pacific & Nevada Bell Serial Circuit ID format. The 3-position field being removed is the customer ID. Without delimiters, the change in format would look like this:

Current Format: 84LCGS000001049PT (underlined data is being removed)New Format:84LCGS001049PT (format used by Southwestern Bell)

· Existing Serial Circuit IDs will remain unchanged, eliminating the need to convert existing circuit information. In other words, any serial circuit ID established in the old format will not be converted to the new format.

· Existing and new circuit ID assignments will continue to be unique as if the customer ID had been removed from existing Serial Circuit Ids.

3.3 New Billing Account Numbers (BANs) · At conversion time, a new BAN will be assigned to all CABS billing accounts

containing Phase 1 products. This BAN format is consistent with the BAN number structure used by Southwestern Bell.

The prefix of the new BAN denotes the processing site / state:

BAN starting with 071 = Nevada (Fairfield Data Center)

BAN starting with 072 = Northern California (Fairfield Data Center)

BAN starting with 073 = Southern California (San Diego Data Center)

· BANs for billing accounts containing Phase 2 services will remain unchanged until Phase 2 products are converted.

· A “BAN” conversion file is available to each customer that provides updated bill period and BAN number changes. Please contact your Account Manager.

· To assist with this transition, a new ZBAN FID will be created effective with December 2000 bills. Pre-conversion BAN numbers will be found on the SBC CABS Customer Service Record (CSR) behind the ZBAN FID.

· The ZBAN FID will be missing for any BAN established after the Phase 1 conversion.

· At the same time BANs are changed, Phase 1 customers with an ACNA of “ZZZ” will be changed to ACNA “ZAA”. This will insure these customers receive paper bills comparable in size to their current P*B CABS bills.

7

Page 10: PACIFIC BELL

Information in the following sections (3.4 through 3.7) and Attachment 1 were included in the September / October ASM Customer Workshops.

3.4 VTA field changes when ordering pricing plans · Today, Pacific and Nevada Bell customers can order variable pricing plans for

Fiber Advantage, SONET, ITAS and the Optional Payment Plan. The pricing plans give discounts on the service for higher quantities ordered and longer terms of service.

· Effective December 4, 2000, the ordering requirements in the VTA field for these pricing plans will be different. The new VTA field format is consistent with the Southwestern Bell ordering approach. Below is an example of the before and after entries for an order for one DS1.

SERVICE PRICING PLANPRE-CONVERSION

ENTRY IN THE VTA FIELD

POST CONVERSIONENTRY IN THE VTA

FIELDFiber Advantage DS1 Month to Month DS1 M FAmm-dd-yy 01 001Fiber Advantage DS1 1 Year Plan DS1 1 FAmm-dd-yy 01 012Fiber Advantage DS1 3 Year Plan DS1 3 FAmm-dd-yy 01 036Fiber Advantage DS1 5 Year Plan DS1 5 FAmm-dd-yy 01 060

· In the 3 year pricing plan example above, the VTA field is formatted as follows:

FA: This entry describes the service (Fiber Advantage).

MM-DD-YY: This is the start date of the contract.

01: Represents the volume, in this case one DS1 was ordered.

036: This entry represents the length of the contract in months.

Please note: 1) Spaces between fields are required.

2) The combination of the NC code and the entry in the VTA field allows SBC to determine the service ordered and the pricing plan the customer has selected

· The format for the ITAS and OPP plan are slightly different.

· Attachment 1 provides a job aid for the various VTA options.

3.5 Changed requirements when ordering DS3X3s· A DS3X3 request to a premise location requires a DS3X3 facility and three DS3

facilities to be established at the same time. In other words, 4 circuits will need to be provisioned to provide this service.

· Effective December 4, 2000, two ASRs will be required when ordering a DS3X3 to a premise location.

· CURRENT REQUIREMENTS FOR DS3X3

- 1 ASR with a quantity of 1 in the QTY field is populated.

- Service rep issues separate service order to establish the 3 DS3 circuits that are provisioned with the DS3X3

- FOC is returned with 4 Circuit Ids. One Circuit ID in the ECCKT field the other 3 circuits in the REMARKS field.

· POST CONVERSION REQUIREMENTS FOR DS3X3 (eff. 12/4/2000)

8

Page 11: PACIFIC BELL

- Two ASRs will be required with appropriate NC/NCI codes & VTA entries:

· One ASR with quantity of 1

· Second ASR with quantity of 3

- The two ASRs must be related to each other using the RPON field on the ASR.

- FOC back to the customer will reflect the appropriate data for each ASR in the correct fields.

3.6 NC Code changes when ordering DS3X3s and DS3X12s· For DS3X3 and DS3X12 ASRs, Pacific & Nevada Bell required the use of non-

OBF standard NC codes of HH-M and HHHM to allow orders to be pre-translated in CESAR. Using these NC codes allowed CESAR to create a CLF format for the system established.

· Effective December 4, 2000, BDS Telis and EXACT will only accept the OBF standard NC for DS3X3 and DS3X12 is HH--and HHH-, as shown below:

NC Codes

Pre-conversion

(CESAR ASR)

Post Conversion

(TELIS / EXACT)

DS3X3 HH-M HH--

DS3X12 HHHM HHH-

9

Page 12: PACIFIC BELL

Attachment 1 – Job Aid for VTA field for Pacific & Nevada Bell Pricing Plans(Effective December 4, 2000)

Fiber Advantage

SERVICEPRICING PLAN PRE CONVERSION

ENTRY IN THE VTA FIELD

POST CONVERSIONENTRY IN THE VTA

FIELDFA DS1 Month to Month DS1 M FAmm-dd-yy 01 001FA DS1 1 Year Plan DS1 1 FAmm-dd-yy 01 012FA DS1 3 Year Plan DS1 3 FAmm-dd-yy 01 036FA DS1 5 Year Plan DS1 5 FAmm-dd-yy 01 060

DS3 Month to Month DS3 M FAmm-dd-yy 01 001 DS3 1 Year Plan DS3 1 FAmm-dd-yy 01 012DS3 3 Year Plan DS3 3 FAmm-dd-yy 01 036DS3 5 Year Plan DS3 5 FAmm-dd-yy 01 060

DS3X3 Month to Month DS3XM FAmm-dd-yy 03 001DS3X3 1 Year Plan DS3X1 FAmm-dd-yy 03 012DS3X3 3 Year Plan DS3X3 FAmm-dd-yy 03 036DS3X3 5 Year Plan DS3X5 FAmm-dd-yy 03 060DS3X12 3 Year Plan DS3123 FAmm-dd-yy 12 036DS3X12 5 Year Plan DS3X125 FAmm-dd-yy 12 060

Breakdown of new Post-Conversion VTA Entry - “FAmm-dd-yy ## len”:

FA: This entry describes the service (Fiber Advantage).

MM-DD-YY: This is the start date of the contract.

##: Represents the volume of DS1 or DS3s being ordered. (Please note the quantity values for DS3X3 and DS3X12 in the table above)

len: This entry represents the length of the contract in months.

Note: All spaces and hyphens are required

10

Page 13: PACIFIC BELL

SONET SERVICE PRICING PLAN PRE CONVERSION

ENTRY IN THE VTA FIELD

POST CONVERSIONENTRY IN THE VTA

FIELDOC-48 3 Year Plan OC48 3 SOmm-dd-yy 01 036OC-48 5 Year Plan OC48 5 SOmm-dd-yy 01 060OC-12 3 Year Plan OC12 3 SOmm-dd-yy 01 036OC-12 5 Year Plan OC12 5 SOmm-dd-yy 01 060OC-3 3 Year Plan OC03 3 SOmm-dd-yy 01 036OC-3 5 Year Plan OC03 5 SOmm-dd-yy 01 060DS1 Month to Month DS1 M SOmm-dd-yy 01 001DS1 1 Year Plan DS1 1 SOmm-dd-yy 01 012DS1 3 Year Plan DS1 3 SOmm-dd-yy 01 036DS1 5 Year Plan DS1 5 SOmm-dd-yy 01 060DS3 Month to Month DS3 M SOmm-dd-yy 01 001 DS3 1 Year Plan DS3 1 SOmm-dd-yy 01 012DS3 3 Year Plan DS3 3 SOmm-dd-yy 01 036DS3 5 Year Plan DS3 5 SOmm-dd-yy 01 060

STS-1 Month to Month STS1 M SOmm-dd-yy 01 001STS-1 1 Year Plan STS1 1 SOmm-dd-yy 01 012STS-1 3 Year Plan STS1 3 SOmm-dd-yy 01 036STS-1 5 Year Plan STS1 5 SOmm-dd-yy 01 060OC-3c Month to Month OC03 M SOmm-dd-yy 01 001OC-3c 1 Year Plan OC03 1 SOmm-dd-yy 01 012OC-3c 3 Year Plan OC03 3 SOmm-dd-yy 01 036OC-3c 5 Year Plan OC03 5 SOmm-dd-yy 01 060OC-12c Month to Month OC12 M SOmm-dd-yy 01 001OC-12c 1 Year Plan OC12 1 SOmm-dd-yy 01 012OC-12c 3 Year Plan OC12 3 SOmm-dd-yy 01 036OC-12c 5 Year Plan OC12 5 SOmm-dd-yy 01 060

Breakdown of new Post-Conversion VTA Entry - “SOmm-dd-yy ## len”:

FA: This entry describes the service (SONET).

MM-DD-YY: This is the start date of the contract.

##: Represents the volume ordered (e.g., one SONET DS1)

len: This entry represents the length of the contract in months.

Note: All spaces and hyphens are required

11

Page 14: PACIFIC BELL

ITASSERVICE PRICING PLAN POST CONVERSION

ENTRY IN THE VTAFIELD

POST CONVERSIONENTRY IN THE VTA

FIELDITAS Month to Month Field is blank /SPP IT MM-DD-YY 01 001ITAS 1 Year Plan Field is blank /SPP IT MM-DD-YY 01 012ITAS 3 Year Plan Field is blank /SPP IT MM-DD-YY 01 036ITAS 5 Year Plan Field is blank /SPP IT MM-DD-YY 01 060

OPTION PAYMENT PLAN SERVICE PRICING PLAN POST CONVERSION

ENTRY IN THE VTAFIELD

POST CONVERSIONENTRY IN THE VTA

FIELDOPP Month to Month OPP M /SPP IT MM-DD-YY 01 001OPP 1 Year Plan OPP 1 /SPP IT MM-DD-YY 01 012OPP 3 Year Plan OPP 3 /SPP IT MM-DD-YY 01 036OPP 4 Year Plan OPP 4 /SPP IT MM-DD-YY 01 048OPP 5 Year Plan OPP 5 /SPP IT MM-DD-YY 01 60

Breakdown of new Post-Conversion VTA Entry - “/SPP IT mm-dd-yy ## len”:

/SPP IT: This entry describes the service (ITAS or OPP).

MM-DD-YY: This is the start date of the contract.

##: Represents the volume ordered

len: This entry represents the length of the contract in months.

Note: All spaces and hyphens are required

12

Page 15: PACIFIC BELL

Attachment 2 – Supporting Conversion Information

List of Affected Products

PHASE 1 PRODUCTS

Last Day to submit CESAR ASR, ISR and WCSRs: December 1, 2000 (Noon PST)First Day to submit ASRs through BDS Telis / EXACT: December 4, 2000 (7 AM PST) Billing Conversion: December 1-3, 2000First Bills from new platform: December 2000

SWITCHED FEATURE GROUP SERVICESFGAFGBFGCFGDMeet Point BillingPICCPublic Access Coin LinesSelect a CarrierSwitched Multimegabytes DataSwitched SS7 **WATS

SPECIAL ACCESS SERVICES **DS1 DS3 and above Additional Engineering and LaborADNATMContracted SpecialsDigital DataFiber Advantage Pricing PlanFrame RelayMetallic Grade OPP Pricing PlanProgram AudioProgram VideoSONETSSE/SSA (ICB)Switched FacilitiesTelegraphTRSVoice Grade

** Phase 1 include Wireless SS7 Links and Wireless Special Access products

13

Page 16: PACIFIC BELL

PHASE 2 PRODUCTS

Last Day to submit CESAR ASR, ISR and WCSRs: December 1, 2000 (Noon PST)First Day to submit ASRs through BDS Telis / EXACT: December 4, 2000 (7 AM PST)

Billing Conversion: (Date to be established)First Bills from new platform: (Date to be established)

WIRELESS Wireless Interconnection (e.g., Type 1, Type 2A, Type 2B)

UNBUNDLED NETWORK ELEMENT (UNE) & INTERCONNECTION End Office Trunk PortLocal Interconnection TrunksLocal Interconnection Facilities Number PortabilityOperator Assistance / Directory AssistanceCustomized Routing Unbundled Dedicated TransportUnbundled Loops (including DS1 Loops)Unbundled Loops with Number PortabilityUnbundled SS7 Links

All remaining Pacific Bell CABS billed services

14

Page 17: PACIFIC BELL

Ordering Method Changes (Phase 2 Products)

Products: Unbundled Loops (including DS1 Loops)Unbundled Loops with Number PortabilityNumber Portability

Effective Date Online Order Method Batch Order Method

Prior to December 4, 2000 LSR process via LEX CESAR ASR or CESAR ISR

LSR process via EDI CESAR ASR

On or After December 4, 2000 LSR processes via LEX LSR processes via EDI

Products: Local Interconnection TrunksLocal Interconnection Facilities Operator Assistance / Directory AssistanceUnbundled Dedicated TransportUnbundled SS7 Links

Effective Date Online Order Method Batch Order Method

Prior to December 4, 2000 CESAR ASR or CESAR ISR CESAR ASR

On or After December 4, 2000 BDS Telis EXACT

Products: Customized Routing

End Office Trunk Port

Effective Date Online Order Method Batch Order Method

Prior to December 4, 2000 CESAR ASR CESAR ASR

On or After December 4, 2000 BDS Telis EXACT

Products: Wireless Products

Effective Date Online Order Method Batch Order Method

Prior to December 4, 2000 CESAR ASR or CESAR WCSR

CESAR ASR or CESAR WCSR

On or After December 4, 2000 BDS Telis EXACT

15

Page 18: PACIFIC BELL

Attachment 3 - FUNCTIONS AVAILABLE IN CESAR AFTER DECEMBER 1, 2000

Several menu options in CESAR will be “turned off” or no longer supported after December 1, 2000. Some options will still be available for viewing only. Below is a preview of the new CESAR menus with notations on which menu options will change.

CESAR General Menu Changes (Effective 12/4/2000)

PACIFIC BELL CESAR GENERAL MENU 1 ACCESS SERVICE REQUEST MENU (ASR) 2 NEWS BULLETIN 3 EASY ACCESS REQUEST MENU (EAR) 4 DESIGN LAYOUT REPORT MENU (DLR) 5 CBIS (NOT AVAILABLE) 6 ON-LINE CABS BILL 7 WIRELESS CARRIER SERVICE REQUEST (WCSR) 8 QUERY 9 MECHANIZED ADDRESS PREVALIDATION SYSTEM (MAPS) 10 PIU MANAGEMENT SYSTEM (NOT AVAILABLE) 11 INTERCONNECTION SERVICE REQUEST MENU (ISR) 12 CLEOPATRA 13 CLC ACCESS TO INFORMATION SELECT OPTION __ X=EXIT

ASR Issue 22 Menu Changes (Effective 12/4/2000) ASR ISSUE 22 MENU FOR XXX 1 ISSUE ASR (USE EXACT) 12 ASR TRACKING INQUIRY 2 FINISH ASR (USE EXACT) 13 REFERENCE TABLE INQUIRY 3 SUPP 4 (CORRECT ASR) (USE EXACT) 14 (OPTION NOT AVAILABLE) 4 CONFIRMATION INQUIRY (FOC,SRC) 15 QUALITY CONDITION INQUIRY 5 SUPP 1 (CANCEL ENTIRE REQUEST) 16 PON INQUIRY 6 SUPP 2 (CHANGE DDD) (USE EXACT) 17 ADMINISTRATIVE SCREEN 2 MASTER 7 SUPP 3 (CHANGE ASR) (USE EXACT) 18 CONFIRMATION SUMMARY INQUIRY 8 ASR INQUIRY 19 RESEND CONFIRMATION 9 PRINT 20 CBIS (NOT AVAILABLE) 10 BATCH INQUIRY FOR ASR 21 MAPS - ADDRESS VALIDATION 11 PREPARATION GUIDE X EXIT SELECT OPTION __ ENTER PON ________________ VERSION ___ COPY PON ________________

16

Page 19: PACIFIC BELL

17

Page 20: PACIFIC BELL

WCSR Menu Changes (Effective 12/4/2000) WCSR MENU 1 ISSUE WCSR (USE EXACT) 7 INQUIRY 2 FINISH WCSR (USE EXACT) 8 TABLE INQUIRY/MAINTENANCE 3 SUPP 4 (CORRECT WCSR) (USE EXACT) 9 CONFIRMATION SUMMARY 4 SUPP 1 (CANCEL WCSR) 10 PON INQUIRY 5 SUPP 2 (CHANGE DDD) (USE EXACT) X EXIT 6 SUPP 3 (CHANGE WCSR) (USE EXACT) OPTION __ CCNA AAX PON ________________ VERSION __ COPY PON ________________ VERSION __ REQ TYPE _

WCSR Table Maintenance Menu Changes (Effective 12/4/2000)(Add. Change and Delete Options will be removed from the WCSR Table Maintenance Menu)

WCSR TABLE MAINTENANCE MENU 1 BILLING AND CONTACT INFORMATION TABLE 2 WSC/ACTL TABLE 3 CELL/TRANSMITTER SITE TABLE TABLE SELECTION _ OPTION _ I INQUIRY X EXIT

18

Page 21: PACIFIC BELL

ISR Menu Changes (Effective 12/4/2000)

ISR MENU FOR XXX 1 ISSUE ISR (USE EXACT OR LEX/EDI) 12 (OPTION NOT AVAILABLE) 2 FINISH ISR (USE EXACT OR LEX/EDI) 13 REFERENCE TABLE INQUIRY 3 SUPP 4 (USE EXACT OR LEX/EDI) 14 (OPTION NOT AVAILABLE) 4 CONFIRMATION INQUIRY (FOC) 15 QUALITY CONDITION INQUIRY 5 SUPP 1 (CANCEL ENTIRE REQUEST) 16 PON INQUIRY 6 SUPP 2 (USE EXACT OR LEX/EDI) 17 ADMINISTRATIVE SCREEN 2 MASTER 7 SUPP 3 (USE EXACT OR LEX/EDI) 18 CONFIRMATION SUMMARY INQUIRY 8 ISR INQUIRY 19 (OPTION NOT AVAILABLE) 9 PRINT 20 CBIS (NOT AVAILABLE) 10 (OPTION NOT AVAILABLE) 21 MAPS - ADDRESS VALIDATION 11 PREPARATION GUIDE X EXIT SELECT OPTION __ ENTER PON ________________ VERSION ___ COPY PON ________________

19

Page 22: PACIFIC BELL

Attachment 4

Line Side Product Request Form

DATE SENT ______________________(1) CARRIER ____________________________________(2)TO Anaheim ASC ACNA ____________ (3) TAX EXEMPT YES (4)E-MAIL WWW/XXXXX (5) INITIATOR NAME ______________________________(6)FAX 714-563-0347 E-MAIL WWW/ ____________OR FAX ___________(7)

PHONE _______________________(8) BILL ADDRESS ________________________________(9) CITY, STATE, ZIP ______________________________

REQUEST TYPE NEW (10) BILLING TN ________________________ (11) PON # ___________________ (12)

CHANGE DESIRED DUE DATE ________________(13) R RON # __________________(14)

DISCONNECT Type 1 DID Type 1 dial line (15) SUPP

TRUNKS AND OUTPULSING ARRANGEMENTP*B ORIGINATING CLLI _____________________(16) TERMINATING ACTL CLLI ________________(17) ADDRESS _____________________________ (18) CITY,STATE ________________________

MPOE............................. SMPOE (19)

TRUNK QTY ________ (20) NC _______ (21) NCI ________________ (22) TBE YES NO (23) NUMBER (100) BLOCK QTY ______________ (24)

RANGE REQUESTED _____________________________________ (25) NPA/NXX DEDICATED FULL CODE (PART 3 ATTACHED) (26)

DIAL LINES OPTIONS Ô PIC __________ (27) HUNTING ________ (28) JACK __________ (29)START DIAL IMMEDIATE DELAY WINK (30)TYPE OF PULSING MF DTMF DP (31)NUMBER OF DIGITS OUTPULSED __________ (32)

CFA (optional) _______________________________________________________________________ (33)CHANNELS __________________________ (34)

LCON __________________________________ (35) TN ___________________________________ (36)REMARKS ___________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________(37)

20

Page 23: PACIFIC BELL

Attachment 4

(PACIFIC BELL USE ONLY)

P*B ORDER # ______________ DUE DATE ___________________ FOC DATE ________________ NBR (100) BLOCKS _______ NBR RANGE _________________________________________________________________________________________________________________________________________________________________________

SERVICE REPRESENTATIVE____________________________ TN _____________________________

21

Page 24: PACIFIC BELL

Attachment 4

Instructions for Line Side Product Request FormFor additional information see: Telcordia Technical Advisory TA-NPL- 000912 and Telcordia Technical Reference GR-145-CORE

1. Date – Enter date order is sent to Pacific Bell.2. Carrier – Enter your company name.3. ACNA – Enter your company ACNA4. TAX – Entry required for new service requests. Check YES if exempt state and federal tax - an exemption

certificate must be on file with Pacific Bell or included with order form. If no exemptions apply, leave blank.

5. E-MAIL or FAX – How will this order be sent to Pacific Bell. Check the appropriate box.6. Initiator - Enter the name and title of the person completing request.7. E-MAIL or FAX – How should order confirmation be sent. Check the appropriate box8. Phone # - Enter your telephone number9. Address – Enter your complete mailing and billing address.

REQUEST TYPE10. Check service activity desired (one type per request) NOTE: If SUPP is checked, indicate the original PON,

P*B order number, and reason for change in Remarks. For example, due date change, cancel, etc.11. Billing TN - Indicate telephone number to which this service will be billed. (NOTE: If new service, P*B will

provide Billing Telephone Number on confirmation).12. PON – Enter Purchase Order Number.13. Desired Due Date – Enter date that service is requested.14. R PON – Related Purchase Order Number (if applicable)15. Type 1 DID or Type 1 dial line – Enter type of service requested. NOTE: All other Wireless service must be

ordered on the ASR.TRUNKS AND OUTPULSING ARRANGEMENT

16. P*B ORIGINATING CLLI – CLLI code for P*B switch where dial tone is requested.17. TERMINATING ACTL CLLI – CLLI code assigned to your ACTL.18. ADDRESS – Enter complete ACTL address.19. MPOE or SMPOE – Check the appropriate point of entry. Main point of entry or secondary point of entry.20. QTY – Enter quantity of trunks being installed, removed or changed 21. NC – Entry the appropriate NC code for the product ordered.22. NCI - Entry the appropriate NCI code for the product ordered.23. TBE – Toll Billing Exception. A = no collect calls or 3rd # billing accepted will be provided UNLESS checked

NO.24. NBR (100) blocks – Number of blocks of numbers requested.25. RANGE REQUESTED – Desired range of blocks of numbers. NOTE: Requested ranges may not be

available. See confirmation for ranges assigned.26. NPA NXX – Requests for dedicated codes must include Part 3 of the XXXXX form.27. PIC – Primary Interexchange Carrier Code. (Type 1 Dial Line only)28. HUNTING – Type of hunting if requested. (Type 1 Dial Line only)29. JACK – Type of jack if requested. (Type 1 Dial Line only)30. TYPE OF PULSING – Supply pulsing type. MF= multi-frequency, DP = dial pulse, DTMF = Dual Tone Multi-

Frequency.31. # of digits outpulsed – Indicate the number of digits outpulsed from the equipment 32. 2 wire or 4 wire – not needed33. CFA – Entry required when a digital facility is requested. Enter existing CFA information or NEW when a

digital facility has been requested on the RPON.34. CHANNELS - Entry the channel assignment for the CFA indicated.35. LCON – Local Contact – Indicate name of person to be contacted for access.36. TN - Tel # - Enter telephone number of contact.37. Remarks – Description or notes about the order request

22