i data exchange i - apscservices.info · i data exchange i 5. records ... from to length tl'pe...
TRANSCRIPT
I DATA EXCHANGE I
5. Records
The Primary Carrier system is utilized for intercompany compensation. This process is dependent upon the exchange of category 92 originating call records. The detail category 92 records are summarized into category 92-99-01 summary records and provided to each LECKLEC on the call path.
The following has been included in this section:
Record Creation Process Flowchart Record Types Included
92-99-01 Record Layout Header and Trailer Requirements
Definition of Category 92 Records
1
t 1
DATA EXCHANGE I I
Record Creation Process
End User makes call F I AMA recording made
Recording forwarded to Rating Company I
I I PTC Record I
copy 0 1-0 1 -xx Message to 92-0 1 -XX
PTC Record
Process 0 1-0 I -XX Message as usual
J- copy 01-01-xx
Message to 92-0 1 -XX
CHR Record PTC and 92-0 I-XX
Set PJD 5 to ‘0’ in 92-0 1 -XX PTC message
Exchange 92-99-01 Summary records With other PTCs
Set N D 5 to ‘ 1 ’ in 92-0 1 -XX CHR message
Forward 92-0 1 -XX CHR record to
Clearinghouse agent
3 S W BT-AR-38
I DATA EXCHANGE I
Record Types Included
The following record types are included in the Category 92 Intercompan!, Compensation process:
01-01-01 MTS
01-01-02 OUTWATS w o n SMDR)
01-01-03 OUTWATS (SMDR)
01-01-25 Originating 800 (SSP)
01-01-31 Local Service
An example of an 01 -01 -01 MTS and 0 1-01 -3 1 Local Service record layout are provided on pages 4 and 5 following.
SWBT-AR-39 3
BR 010-200-010 Issue 15. October 1996 BILLABLE MESSAGE
NORTH AMERICAN ORIGINATED, TERMINATED AND BILLABLE MESSAGE TELEPHONE SERVICE CHARGE
noC-0-
01 31 01 - rm C w n m.04
Indicators 9
9 Recordmg I Send Oblqation Number ID
109 I . to1 1 1 1 1
112
- Btlling RAO 9
Number North
Amencan Standard
I Billing
Number Non
Standard
1 Resewed
Far Local Company
Use
~
PROPRIETARY - -CORE AND AUTHORIZEO CLIENTS ONLY See propnetary restncoons on otle page
J
SWBT-AR-40
3-3
0 R 010-200-010 Issue 15, October 1996
BILLABLE MESSAGE NORTH AMERICAN ORIGINATED, TERMINATED AND BILLABLE
LOCAL OR MESSAGE UNIT CHARGE
01 k.gaT
Field Description pa. C h
Record ldenaficaaon Group
Record Type 1 7
9 8
10 1 1 12 13 14
- Year Date
Record - Month Of
- Day
- From Number Length
NPA I C ' 18 From 19 N X X From Base 20 Number Staaon - Number 22 tine 23 Number
- N u n b . r Of - M.cugs Uniu
- To Number Length
-
21
24 26 26 27 29 29 30 31 NPA -
To &SO
Number Staaon Number
Line
Amount Collected
Connect T i m
I * . I I
01 U-0
Field Description Ch
Method Of Recording
Return Code
From RAO
Message Billing Index ~~
7 7 LOCOl zone 78 Rate Penod 79 Rate Class
is4131 p-] 1 8 6 1 6 I
.. . , 1 MA Indicators ri
99 18 100 18
101 20
Oblgatmn ID
Billing RAO
Billing 1 N;r$r 1 Number ''ling
Non Standard Amencan
Standard
Field Description C k
bbrary Code
Settlement Code
Carner Carner Identification 162 ldenafication
163 Expanded
Reserved
Indicators
166) 28 166 29 167 30 168 169 - - 170 Reserved 171 For - 172 Local Company 173 Use
- -
Billable Or
Reported Time
PROPRIETARY - BELLCORE AND AUTHORIZED CLIENTS ONLY sdd Qunctendc
x-- 9 - N ~ C
See propnetary restncuons on tide page
~
SWBT-AR-41
3-35
I DATA EXCHANGE I
Definition of Cateporv 92 Records
Category 92 records are copies of the category 0 1 billing records (where XX equals the specific record types) that are included in the Plan. There are two basic types of Category 92 detail records:
1. Category 92-01-XX detail records with Indicator 5 set to ‘0‘
92-0 1 -XX A copy of the Intrastate IntraLATA 01 -0 1 -XX EMR message with Indicator 5 = ‘0’. These records are summarized for switched access billing.
2. Category 92-01-XX detail records with Indicator 5 set to ‘ 1 ’
92-0 1 -XX CHR A copy of the Intrastate IntraLATA 0 1-0 1 -XX EMR message with Indicator 5 = ’ 1 * .
An example of the 92-01-01 record layout is provided on page 7 following.
6 S WBT-AR-42
92-01-xx Record C r e a t i o n
The 92-01-xx is a copy of the 01-01-xx.
FROM TO LENGTH TYPE VALUE
1
7
13
15
25
28
3 0
40
47
48
55
61
68
70
72
75
78
6 6 N 920101 = MTS 920102 = OUTWATS 920103 = OUTWATS 920125 = Orig 800 920131 = Local
12 6 N YYMMDD
14 2 N 10
24 10 N NPANXXLLLL
27 3 N 0
29 2 N 10
39 10 N NPANXXLLLL
46 7 N 0
47 1 N 0
54 7 N
60 6 N
0
HHMMS S
67 7 N MMMMSST
69 2 N See EMI, 4-90 - 4-92
71 2 N 0-
74 3 X
77 3 N 0
78 1 N 0-6
DESCRIPTION
Message ID
Message Date
Number of Digits in the "From Number"
llFromll NPA/NXX and line number
Overflow Digits
Number of Digits in the "To Number
rlT~II NPA/NXX and line number
Charge or Amount Collected
Type of Regulation Indicator
Taxes
Connect Time or Time of Day the c a l l began
Billable Time
Method of Recording
Return Code
From RAO
Local Company Information
Rate period based on time and/or day of week (See EMI, 4-116)
7 SWBT-AR-43
92-01-xx Record Creation (Cont.'d)
The 92-01-xx is a copy of the 01-01-xx.
FROM TO LENGTH TYPE VALUE
79 79 1 N 1-6
DESCRIPTION
Rate class based on whether the message was person or station and customer-dialed or OPH (See 4-116)
80 80 1 N l=Sent Paid 2=Third Number 3=Calling Card 4 =Collect 5=Special Collect 6=Coin Paid
Message type identifies the billing arrangement
1 N 0 IOC Code 81 81
82 101 20 N See EMI, 4-52 - 4-58 Commonly used Indicators are: Indicator 4 = 7 for UNE Indicator 5 = 0 €or STL Indicator 5 = 1 €or CHR
102 103 2 N
104 109 6 N
110 112 3 X
113 122 10 N
123 134 12 X
135 146 12 X
147 140 2 X
0-9
0-9
NPANXXLLLL
Operator Unit
Recording Point Identifier
Billing RAO
Billing NPA/NXX and line number
Standard Abbreviation of the location and state from which the message originated
Standard abbreviation for the called location and state
Library code used to identify the source of messages recorded
149 149 1 X 6=Local Settlement Code for the 8=Intrastate - ~.s./u.s. classification of messages
150 153 4 N 0 CIC Code
154 156 3 N 0 Reserved
SWBT-AR44 8
92- 01- xx Record Creation (Cont.'d)
The 92-01-xx is a copy of the 01-01-xx.
FROM TO
157 157
158 167
168 171
172 172
173 173
174 174
175 175
176 185
186 195
196 205
206 206
207 210
LENGTH
1
10
4
1
1
1
1
10
10
10
1
4
TYPE VALUE
N 0
See EMI, 4-52 - 4-58
N
N l=Originating UNE 2=Terminating UNE
N
N - =
0
RN Substi u ion O=No LRN Substitution
N NPANXXLLLL
N NPANXXLLLL
N NPANXXLLLL
N 0
N
DESCRIPTION
Treatable indicator
Indicators
Originating OCN of UNE Customer
Orig/Term Indicator on UNE records only
Transport ID - For local company use
Re served
LRN Substitution Per-Drmed
Originating LRN
Terminating LRN
Billing LRN
Re served
Originating Recording Identifying Terminating UNE Company
9 SWBT-AR-45
I Intrastate/lntralata Originating Messaae Telephone Service
Field Description Pos Char
1
92
1
01
170 tTT 1 7 2
01
Keturn Code Cancel Codt
r
/6! Record Type I 7 1 I I
~
Reported .- 1/10 9 = Numeric
Field Charadenstic:
14 From Number Length
16 NPA From
18 ' From 19 NXX Base 20 Number Station 21 Number T Line
15 9
9
148 Library Code 149 I X I Settlement Lode
arrier Carrier Idehication 1 9 i
I
t i Ori ./Term. IVdica&r on UNE
Records Only l = O r i q . Z=Term.
,173 9 ' 174 ( X
j 9 1
Billing ,
Billing 1 -
- F i e l d s 186-195 E T e r m i n a t i n g L R N 9 -
- F i e l d s 196-205 - 9 - B i l l i n g L R N
1206 Reserved X
I Field Description I 1 Pos Char I
I
Field Description I Pos Char - 9
x 7
Record
From RAO Lllj Year 1 D;:
Month Record
t 7 5 i Local 9
Day I
Indicator 4 1154 1 I
To Denote ='I UNEiessage Number 1
To Number Length 9 I I I
9
O r i g i n a t i n g G C N o f UFJE Customer
Obligation
Charge
Amount
L R N S u b s t i t u t i o n Performed
(Va lue = 0 o r 1) F i e l d s 176-185
O r i g i n a t i n g L R N
127 Cent
1 Cent Tax SSAS Code
134 CnCrCd
X
Oriq. Reco rd ing Only AECN/OCN I d e n t i f y i n q
Term. U N E Company-/ d 1 10 X = Alphanumenc
SWBT-AR-46
I ~ ~~~
I DATA EXCHANGE
Definition of Category 92 Records (con't)
Category 92-99-0 I Summary records are used for intercompany settlements. These records are summaries of the category 92-0 1 -XX records and utilize a 'traffic type' to identify the type of usage. These records are exchanged monthly.
92-99-0 1 A summary of the 92-0 1 -XX message summarized by date, traffic type, originating aggregate NPA/NXX and terminating NPA/WXX. 92-01 -XX CHR messages are not included in this summary.
An example of the 92-99-0 1 record is provided on pages 9 - 13 following.
11 SWBT-AR47
DATA EXCHANGE
92-99-01 Record Creation
FROM TO LENGTH Tl'PE I'ALUE SOURCE
1 6 6 N
7 7 1 h
8 13 6 N
14 15 - 3 N
16 21 6 N
22 29 8 '4N
30 35 6 N
36 43 8 AN
44 51 8 N AN = AlphaNumenc N = Numenc
92990 1
0 1
\'YMMDD 92-01-XX
01 02 03 04 05 10 1 1 12 13 14 15
0-9
0-9
# Blank
Position 7- 12
92-0 1 -XX Position 15- 30
Table
92-01 -XX Position 30- 35
Table
Calculated 13
DESCRI PT IO N
Message ID
Tandem Direct
Message Date
Traffic Type 0 1 =MTS 02=WATS 03=ORIG. 800 DAL 04=ORIG. 800 CML 05=OPH 1 O=LOCAL 1 1 =LOCAL EAS 12=Local Plus (S WBT orig.) 13=Local Plus (non-S WBT orig.) I4=IntraLATA Wholesale Svc. (IWS) 15=Local Minutes Plus
Aggregate origmating NP.4lh'XX (The six digit NPt\/Tc'XX of the originating end office)
Originating CLLI code (The first 8 characters of the originating CLLI code associated with the origmating NPA/NXX in positions 16-2 1 above)
Aggregate terminating NPAh'XX (The six digit NPA/NXX of the terminating end office)
Terminating CLLI code (The first 8 characters of the terminating CLLI code associated with the terminating NPANXX in positions 30-35 above)
Total Message Count
SWBT-AR48
DATA EXCHANGE
FROM TO LENGTH Tl’PE
52 59 8 N
60 61 - 7 h’
62 62 1 N
63 66 4 N
67 70 4 N
\’ALCE
f Blank
# Blank
# Blank
0-9
0-9
71 73 3 AN Table
SWB GTE CEK SC
LSP LC;F LTC FID
CON CSM SGL AP
ALT LWE
SOURCE DESCRIPTION
92-0 1 -NS Total Minutes Position 6 1 - 61
92-0 1 -Xi Total Seconds Position 65- 66
92-0 1 -XX Position 67
Total Tenths of Seconds
Table NECA Code of PTC (PTC creating 92- 99-0 1 )
Table OriFnating LEC NECA code (The four digit NECA code associated with the LECs aggregate originating NPA/NXX in positions 16-2 1 above)
74 77 3 N
AN = AlphaNumeric V = Numeric
0-9 Table
LEC Description Table Code SWB-SWBT GTE-GTE CEN-Centel (TX) SC-Secondary Camer (MO, KS) LSP-Local Service Provider LUF-Lufkin Conroe (TX) UTC-United (TX, MO, KS) FID-Fidelity (MO) CON-Contel (TX, MO, AR. KS) CSM-Century-San Marcos (TX) SGL- S ugarl and (TX) AP-Access Provider (OK) ALT-Alltel (AR) WE-Unbundled Network Element
Terminating LEC NECA code (The four digt NECA code associated with the LECs aggregate terminating NPANXX in positions 30-35 above)
S WBT-AR-49
I ~~~ DATA EXCHANGE I
FROM TO LENGTH TI'PE j 'ALUE SOURCE DESCRIPTION 7 78 80 AN Table LEC Description (See positions 7 1-73
a bo \re )
81 84 3 Ii 0 - 0 Table Transiting LEC # I (The four digit NECA code of the transiting LEC in the path of the call located between the originating and terminating LEC)
85 87 3 AN
88 91 4 N
92 94 3 AN
95 98 4 N
99 101 3 AN
I02 105 4 N
106 108 3 AN
109 112 4 N
113 115 3 AN
AN = AlphaNumenc N = Numeric
Table
0-9 Table
Table
0-9 Table
Table
0-9 Table
Table
0-9 Table
Table
14
LEC Description (See positions 7 1-73 above)
Transiting LEC #2 (The four digit NECA code of the transiting LEC in the path of the call located between the orignating and terminating LEC)
LEC Description (See positions 7 1-73 above)
Transiting LEC #3 (The four digt NECA code of the transiting LEC in the path of the call located between the originating and terminating LEC)
LEC Description (See positions 7 1-73 above)
Transiting LEC k4 (The four digit NECA code of the transiting LEC in the path of the call located between the orignating and terminating LEC)
LEC Description (See positions 7 1-73 above)
Transiting LEC #5 (The four digit NECA code of the transiting LEC in the path of the call located between the orignating and terminating LEC) LEC Description (See positions 7 1-73 above)
SWBT-AR-50
DATA EXCHANGE
FROM TO LENGTH Tl'PE \'ALUE SOURCE DESCRIPTION 116 119 4 N 0-9 Table Transiting LEC ~6 (The four digit
NECA code of the transiting LEC in
the path of the call located betLveen the originating and terminating LEC)
120 1 ;!2 3 AN Table LEC Description (See positions 7 1-73 above)
123 12!6 4 N 0-9 Table Transiting LEC #7 (The four digit NECA code of the transiting LEC in the path of the call located between the originating and terminating LEC)
127 12:9 3 AN
130 13'3 4 N
Table LEC Description (See positions 7 1-73 above )
0-9 Table Transiting LEC #8 (The four digit NECA code of the transiting LEC in the path of the calf located between the originating and terminating LEC)
134 136 3 AN Table
137 14.0 4 N 0-9 Table
141 144 4 N 0-9 Table
145 155 1 1 .4N 0-9 Table
156 166 ' 1 1 AN 0-9 Table
167 167 I N 1 0
168 2110 43 N 0
AN = AiphaNumeric N = Numenc
LEC Description (See positions 7 1-73 above)
LATA Code
Receiving LEC
Orignating CLLI Code
Terminating CLLI Code
LWE Not UNE
Reserved
June 1999
IntrastateAntraLATA Originating Message Telephone Service
92
Field Description IPOS Cha
Record
Record Type
99 01
Field Description Cha
a PASPpCompany 1 Descri tion Code
Transiting Company 2 NECA C&
PASPCompany
Transiting Company 3 NECA
Reserved
SWBT-AR-52 Field Cburc~nrUc. 9 - Numcnc X - Alphmumcnc
I6
DATA EXCHANGE
Header and Trailer Requirements
Headers and Trailers are required for data processing. The appropriate Headers and Trailers are based on a company’s RAO status.
There are two types ofstandard Bell - Non-Bell Exchange Camer Pack Header and Trailer record formats used for data transmission:
Format
0 Full RAO Companies use 20-20-xx
0 Non-Full RAO Companies use 20-2 1 -xx
Category 92 records cannot be transmitted over CMDS and require a separate transmission from other types of records.
For category 92 records, we substitute a ‘90’ (Full RAO Companies) or ‘9 1 ’ (Non-Full RAO Companies) for the record group in the standard EMR Bell - Non-Bell Exchange Carrier Pack Header and Trailer record formats shown above:
Category 92 Records Header Trailer
0 Full RAO Companies use 20-90-0 1 20-90-02
0 Yon-Full RAO Companies use 30-9 1-0 1 20-9 1-02
1-
~~
DATA EXCHANGE 1
20-90-0 1
Header and Trailer Records
Full Status RAO Companies
A copy of the Standard EMR 20-20-0 1 CMDS Pack Header Record. This record is used by full status RAO companies for the category 92 records with the group value changed from ‘20’ to ‘90’.
20-90-02 A copy of the Standard EMR 20-20-02 CMDS Pack Trailer Record. This record is used by full status RAO Companies for the category 92 records with the group value changed from ‘20’ to ‘90’.
An example of the 20-90-0 I record layout is provided on page 16 following.
An example of the 20-90-02 record layout is provided on page 17 following.
SWBT-AR-54
20 . I I Field Description Pos
Record ldentificatior
Sent To RAO
23 Billing RAO
25 26
28
32
Reserved H Local
Company Use
1461
Reserver
Full RAO Pack Header Record
Field Charactenstic: 9 = Numeric
90
Field Description
Reserved
E Hour 1 Time Created
Minute 122 NBEC indicator
Reserved
Reserved
X = Alphanumenc 19
01
i Field Description Char 1
Reserved
SW BT-AR-55
20
1 - 2 Category
26 27 28
- -
Month 1 Created
- 30
32 33 34
31 - - - 35
Et== Invoice Number
Company Number
From RAO m Sent To RAO
Billing RAO
Reserved
Reserved
Full RAO Pack Trailer Record
91
I
i I i
~
I
I 9 1
i
j -
9 '
Field Charactenstic 9 = Numeric
90
I Field Description I Pos Char
Reservea 4
I Grand Tota
Revenue- 7s
Grand Total
Record 9 Count
Time Created
1127 I Status Code 9
Reserved 1 9 I 1 1
I ! 1 ;
mq 1 1 X = Alphanumeric
20
02
1 I Field Description I Pos Char 1135
Reserved
m r
9
DATA EXCHANGE
Header and Trailer Records
Non-Full Status RAO Companies
20-9 1-0 1 A copy of the Standard EMR 20-2 1-01 Bell - Yon-Bell Exchange Carrier message file Pack Header record. This record is used by non-full status RAO companies for the category 92 records with the group value changed fkom ‘2 1 ’ to ‘9 1 ’.
20-9 1-02 A copy of the Standard EMR 20-2 1-02 Bell - Yon-Bell Exchange Carrier message file Pack Trailer Record. This record is used by non-full status RAO companies for the category 92 records with the group value changed from ‘2 1 ’ to ‘9 1 ’.
A copy of the 20-9 1-0 1 record layout is provided on page 19 following.
A copy of the 20-9 1-02 record layout is provided on page 20 following.
SWBT-AR-57
Non-Full RAO Pack Header Record
20 91 01 I i r I '
I N Field Description Field Description Pos Char I ! POS Char! IPns
1 Field Description , . --
Category Record I 9 1
ILEC or Service Bureau
ILEC Identification Code
Billing
Company 9
I I I . .. - .
I I
Reserved
Status Indicator 1150 I 3 158
Reserved
Char r
9
- 9
x -
# 572-7
kl S W BT-AR-58
I
9
Field Charactenstic. 9 = Numeric X = Alphanumenc 22
20
Field Description
Record 1 9
I
f l 1 I Record Type
I
7d Year 1 !
Month Created
Date 9 1 9
11
1 Interfacing Bell 1 ; RAO Code
ILEC or Service Bureau
I g ILEC Identification Code
Billing
Company
Reserved
Number of Rated
$ Sent Paid Revenue
Non-Billable 1 9
Field Charactenstic 9 = Numeric
Non-Full RAO Pack Trailer Record
91 02
Field Description Field DescriDtion I Char 1
Non-Billable Q -
Revenue
Number of Returned Messages I 9
I a5 !
1 Number of Unrated Messages 9 1
I Foreign [:I State Tax 1 9
94 Cent ,
$ Grand Total -
I Revenues aLi 1111 I Cent
X = Alphanurnenc 113
Reserved
1149 I Status indicator 14cn I
Reserved
SWBT-AR-59 5
I
I
9 I I I
1
9
x
DATA EXCHANGE I
1+ DDD and Operator Handled Call Flow
The following pages depict example call flow drawings which describe record creation and exchange information for 1 + DDD and operator handled calls.
S WBT-AR-60
r DATA EXCHANGE I
I + DDD Call Flow
Originating
Creates 0 1-0 1-0 1 92-0 1-0 1 92-99-0 1
Forwards copy of 92-99-0 1 to
SWBT (T-I) ILEC, (T-2) ILEC, (Terminating)
T- I T-2 Terminating
T- 1 , T-2, Terminatinc Co. Bills CLEC applicable rate elements.
35
I DATA EXCKANGE 1
Operator Handled Call Flow Billing
Clearinghouse
SGL 2147
9
Billing
Clearinghouse
SGL 2147
. I OSPI
9-
CLEC LEC ILEC, ILEC, AT1 SWBT LCTX CTC 7403 5216 2109 2154 ong T- 1 T-2 Term
- OSP
Creates 0 1-0 1-0 1 91-01-01 CHR 92-0 1-0 I STL
Forwards 0 1-0 1-0 1 to the Billing Co. 92-0 1-01 CHR to Clearinghouse 92-01-01 STL to Ong. Co. (CLEC)
T-1, T-2 & Terminating Companv
Bills CLEC applicable rate elements
Originating Companv
Receives 92-0 1-0 1 STL from OSP
Creates 92-99-0 1 Summary
Forwards copy of 92-99-0 I
ILEC, (T-2) ILEC, (Term)
SWBT (T-1)
Clearinghouse
Returns revenues (less the 5 cent billing and collection charge) to the onginating (earning) company. Assesses 2 cent processing charge to onginating company for processing the message
Assumptions: S W T is OSP S W T performs rating function SW BT-AR-62
DATA EXCHANGE
6. Data Exchange Requirements
Specific requirements are used to ensure that the data necessary to accomplish intercompany compensation can be transmitted and processed on a timely basis.
The following has been included in this section:
Data Exchange Media Options Available Data Set Name Requirements Recommended Naming Conventions for Primary Carrier Tapes Header and Trailer Invoice Numbers Primary Carrier Tape Volume Serial Numbers Tape Transmittal Form Data Exchange Schedule Primary Carrier Flow
1 SWBT-AR-63
I DATA EXCHANGE I
Data Exchange Media Options Available
The following data exchange media options are available for the transmission of category 92 records:
Tape 18 track
NDM
0 TCP/IP
SWBT -AR-64
DATA EXCHANGE I
Data Set Name Requirements
0 Must Be IBM Standard
Can Contain Up to 17 alphanumeric Characters without National Characters or Blanks
Each DSN Level Must Begin with an Alpha Character
0 Reads From Right to Left
0 Must Agree with Tape Transmittal Form
0 Must Agree with DSN on Tape
0 Must be Consistent from Month to Month
3
DATA EXCHANGE I
Recommended Narninp Conventions
For Primaw Carrier Tapes
The naming conventions provided are currently in use and ensure that the data is entered into the appropriate state Primary Carrier process.
YYS TL .F XXXX
Where YY = Two letter state abbreviation
Where XXXX = The LEC four-digit numeric code
4
I DATA EXCHANGE I
Catepory 92 Record Header and Trailer Invoice Numbers
0 Must be sequential
0 An invoice number must be accepted before the next sequential number will be accepted
0 The invoice number on the header must match the master number in the program
The header and trailer invoice numbers must match
Must begin with ‘01’
DATA EXCHANGE I
Primary Carrier Tape Volume Serial Numbers
0 Must be IBM standard
0 6 Position alphanumeric
Must have a different volume serial number for each tape
The volume serial number on the tape transmittal and tape label must match the volume serial number contained internally on the tape
SWBT-AR-68 6
I DATA EXCHANGE I
Recommended Volume Serial Numbers
The recommended volume serial number process is currently in use and ensures that the correct data is processed. Duplication of volume serial numbers provides for the potential of processing the data more than once.
xxooo 1
Increment by 1 with each transmission
Where XX = the LECKLEC specific identifier
7
I DATA EXCHANGE 1
Tape Transmittal Form
This form should accompany each tape sent to the SWBT Data Center
For companies operating in Texas, Kansas, Missouri, Arkansas and Oklahoma, the tapes should be sent to:
Southwestern Bell Telephone Attn: AMAUnit 9051 Park West, Room 2242 Houston, Texas 77063
Copies of the tape transmittal forms are provided on page 9 following.
8 SWBT -AR-70
TAPE TRANShIITT..V, September 1997 (Must Ascompany Each Tape Containing I Category 92 Messages)
TO: Southwestern Bi l l Telephone ATTN ,LMA Unit 9051 Park %‘est. Room 2242 Houston. TS 77063
FROM: CornpanvY m e Company Number: Contact Name Phone Number:
Fax Number:
TAPE LABEL INFORMATION Tape Transmittal External Tape Label Internal Tape Label DSN: VOL SER: Record Format: Record Length: Blocksize: Total Packs: Total Messages: FromThrough Dates Create Date/Time:
RETURN TAPES TO
Company Name. Attention. Address : City, State, Zip:
RETURN REPORTS TO.
Company Name: Attention : Address: City, State. Zip:
9 S W BT-AR-7 I
TAPE TRANSMITTAL September 1997 (Must Accolnpany Each Tape Containing Category 92 Messages)
TO: Southwestern Be11 Telephone A m : AMAL'nit 9051 Park !!'est. Room 2242 Houston, TS '-063
FROM: Company Kame Company Number: Phone Number: Fax Number: ( 6 )
Contact Name W
-
TPPE LABEL INFORMATION Tape Transmittal External TaDe Label lnternai Taoe Label
VOL s Record Format: Record Length:
Total Packs: ( 12 ) From/Througiih%t es . (, 7 Blocksize: -T
Total Messages: - Create Datenime: ( 1s ) - - I
RETURN TAPES TO.
Company Name. a- Attentron: ( 1 7 )
Address: ( 1 8 ) '=( City, State, Zip: ( 1 9 1
RETURN REPORTS TO:
Company Name: - Attention: ( 2 1 )
Address: ( 2 2 ) y City, State. Zip: (23) -
I O SWBT -AR-72
I DATA EXCHANGE 1
Title
(1) To:
(2) Company Name:
(3) Company Number:
(4) Contact Name:
(5) Contact Number:
(6 ) Fax Number:
Tape Label Information
(7) Data Set Name:
LECKLEC Tape Transmittal
Description
Enter the name and address of the LECKLEC receiving the transmittal. For tapes being sent to Southwestern Bell, this information has already been completed.
Enter the company name of the sending LECKLEC.
Enter the four-digit NECA company number of the sending LECICLEC
Enter the name of the person to be contacted at the sending LECXLEC.
Enter the telephone number of the person to be contacted at the sending LEUCLEC.
Enter the Fax number of the person to be contacted at the sending LECKLEC.
Enter the Dataset Name (DSN) of the tape accompanying this transmittal. For tapes being sent to southwestern Bell, the suggested dataset name should be YYSTL.FXXXX (Where XXXX equals the four-digit NECA company number of the LECICLEC sending the tape and YY equals the state). The same DSN should appear on the tape transmittal form, on the External Tape Label and on the Internal Tape Label.
1 1 S W BT-A R-73
I DATA EXCHANGE 1
(8) Tape Vol. Ser.:
(9). Record Format:
(1 0) Record Length:
(1 1) Block Size:
(12) Total Packs:
(1 3) Total Messages:
( 14) FrodThru Dates:
Space has been provided on the form for each of the requirements in order to ensure that all three are equal.
Enter the Volume Serial Number (VOL. SER.) of the tape accompanying this transmittal. A standard label is required. The same VOL. SER. should appear on the tape transmittal form. the External Tape Label and on the Internal Tape Label. Space has been provided on the form for each of the requirements in order to ensure that all three are equal.
Enter the Record Format of the tape. The format may be fixed or variable. For tapes being sent to Southwestern Bell, the Record Format should be fixed.
Enter the Record Length of the records contained on the tape. Settlement data has a record length of 2 10. For tapes being sent to Southwestern Bell, the record length should be 210.
Enter the Block Size (standard block size is 2 100; however. this may vary by LEC/CLEC).
Enter the total number of packs contained on the tape accompanying this transmittal.
Enter the total number of messages contained on the tape. This number should reflect the total number of messages from all packs.
Enter the FrodThru Dates of the messages contained on the tape. The dates should reflect the earliest date and the most current date of the messages on the tape.
12 SWBT-AR-74
DATA EXCHANGE I
(1 5) Create Date/Time:
Return TaDe To:
( 16) Company Name:
(1 7) Attention:
(1 8) Address:
(1 9) City, State, Zip:
Return ReDort To:
(20) Company Name:
(21) Attention:
(22) Address:
(23) City, State, Zip:
Enter the date and time this tape was created.
Enter the name of the company that this tape is to be returned to.
Enter the name of the person to whom this tape should be sent.
Enter the address of the company where the tape should be sent.
Enter the city, state and zip code of the company where the tape should be sent.
Enter the name of the company receiving the reparts.
Enter the name of the person who will be receiving the reports.
Enter the address of the company where the reports should be sent.
Enter the city, state and zip of the company where the reports should be sent.
SWBT-AR-7 5 13
I DATA EXCHANGE I
Primary Carrier System Data Exchange Schedule
92-01-XX
92-0 1 - X X detail records are sent at least once a month.
A representative billing month based on each company's current billing cycle(s) may be used.
92-99-01
92-99-01 summary records are sent once a month.
SWBT -AR-7 6 14
DATA EXCHANGE L
7. Primary Carrier System Tables
The Primary Carrier System utilizes several tables to correctly identify and summarize the data required for mutual compensation.
This section will identifjr and describe the following tables:
Primary Carrier Tables (20 - 80) Calling Scope Tables (1 & 4)
SWBT-AR-78 1
DATA EXCHANGE
Primarv Carrier Tables
The Primary Carrier System tables are used in the creation of category 92-99-0 1 intraLATA toll and local summary records. These state specific tables are created and maintained by SWBT. Each month the tables are updated and sent to all primary carriers, both LEC and CLEC, and any other LEC requesting them.
These tables are provided via diskette.
The Primary Carrier tables consist of the following:
Table 20 - LATA Table - Identifies by LATA number and name each of the LATAs in the state.
Table 30 - Company Table - Identifies all companies operating in the state by company number, name, status in the state plan, RAO status and the media used for data exchange.
0 Table 50 - Toll Center to Toll Center Table - Identifies the relationships between tandems. This information is required for the creation of the 92-99- 01 summary records.
Table 60 - End Office to Toll Center Table - Identifies each end office (CLLI Code) and the tandem it subtends.
0 Table 70 - Toll Center Table - Identifies each toll center by CLLI and LATA.
0 Table 80 - NPA/NXX to CLLI Table - Lists valid NPA/NXXs, associated CLLI Code, owning company and associated primary carrier (if any).
Examples of Primary Carrier Tables 20 - 80 are provided on pages 3 - 9 following.
2
I
D
DATA EXCHANGE
E
I
ID ELP MID LUB AMA WIC AB1 DAL LON
A
LATA LATA LATA LATA LATA LATA LATA LATA
NAME ELPASO MIDLAND LUBBOCK AMARILLO WICHITA FALLS ABILENE DALLAS LONGVIEW
PRIMARY CARRIER LATA TABLE 020
B
20 20 20 20 20 20 20 20
C
ID 540 542 544 546 548 550 552 554
A
B Primary Carrier Table number. C D E Lata name.
Primary Carrier Table name or type and date of activity (A-add, C-change. R- rehome).
Lata number used in positions 137 - 140 in the 92-99-01 summary records. Three digit code identifying the Lata.
SWBT-ARSO
P R l h l A R Y C A R R I E R COMPANY T A B L E 030
M
E
A
S O R T
( ‘ O M P A N Y
A970302
COMPANY
COMPANY
C961102
COMPANY
C
Y
Y
Y
Y
Y
Y
B
30
30 30 30 30 30
NAME----
CUMBY
MUENSTER
PEOPLES
CONTELTX
GTESWTX
SOTHWEST
C
KEY
OCN
2065
21 16
2130
2154
4344
5216
D
BELL
CORE
OCN
2065
21 16
2130
2154
2080
9533
E
CLASS
STAT
PTC
PTC
PTC
PTC
PTC
PTC
F
STATUS
PTC
PTC
PTC
CON
GTE
SWB
H
A Prirniiry Carrier Table name or type and date ot activity (A-add. C-change, R-rehome). u c‘ V E F
ci t i I
:1 K L M VI
* N 2
I
SOMPANY NAME-------
SUMBY TEL
MUENSTER TEL
PEOPLES TEL
SONTEL OF TEX (GTE)
GTE SW - TEXAS
SWB TEL - TEXAS
J
FUL
RAO
N
N
N
Y
Y
Y
K
BILL
RAO
149
150
149
380
34 5
149
Primary Carrier Table nurnhcr. (‘onipany number used in the plan (state coinpany nuinher). Viis information is used in positions 67 - 7 0 and 7 4 . 77 ill t t lc c ) p ) ( j . ( ) l . ; u l l l l i l a ~ rccortls Bellcore company numhcr (ovcTall company nuinher). Idcntifics the status of a company (PTC, SC) [>efiiies the company description used in the 92-09-01 surilmary records. Used in positions 7 I -~ 73, 78 - 8 0 , 85 106 - I O R , I 13 - I 15, I20 - 122, 127 - I29 and I34 - I36 in the 92-99-01 suminary rLxords. SC = Secoridary Carrier; All other codes -~ Primary (’arricrs. For SWBT use only. Eight digit code for company nmie. Company name. indicates i fa company is a lull RAO. Company RAO nuinher. (‘(>nipany Or vendor nurnber to whom category Y2 records are transmittetl. For SWBT use only. For SWBT use only.
87, 92 (14, 09 I 1 ,
L
NAME
5065
5065
2130
2154
4344
5216
M
MECH
Y
Y
Y
Y
Y
Y
N
MED
IUM
NDM
NDM
TAP
NDM
NDM
NUL
4
A
I NTE RTO L
INTERTOL
C960502
I NTE RTOL
INTERTOL
I NT E RTO L
A B C 1) E F G-K
I, M N
B
50 50 50 50 50 50
C
LAT
552
552
552
552
552
552
D .
ROM-C LLI
)LLSTXTA
)LLSTXTA
INTNTXXA
INTNTXXA
MMNTXXA
;HMNTXXA
TO__CLLI
DNTNTXXA
SHMNTXXA
DLLSTXTA
SHMNTXXA
DLLSTXTA DNTNTXXA
F
FROM
LEC
5216
5216
4344
4344
4 344
4 344
G
TRAN
LEC
1
5216
521 6
H
TRAN
LEC
2
I
TRAN
LEC
3
J
T RAN
LEC 4
K
TRAN
LEC
5
['r-ilnary Carrier Table name or date ot activity (A-add, C-change, K-rehome). Primary Carrier Table number. Lata number used in positions I37 Originating Toll Center CLL.1 code Terminating Toll Center CLI>I code. Originating Toll Center company number. Company number o f I,EC/CLEC that OWIS facilities between the originating and terminating ' T o l l Center. This is used in positions 8 1 - 84, 88 - 91, 95 ~ 98, I02 - 105, 10') ~ I I 2, I 16 ~- 1 19, 123 -- 126, 130 ~ 133 in the 92-994) 1 summary records. 'Terminating Toll Center company number. Originating 'Toll Center name. Tcnninating Toll Center name.
140 i n the 92-99-01 summary records.
L
TO
LEC
4344
4344
521 6
4344
521 6
4344
M
FROM
TOLL
CENTER
DALLAS
DALLAS
DENTON
DENTON
SHERMAN
SHERMAN
N
IO roLL EENTER
DENTON
SHERMAN
DALLAS
SHERMAN
DALLAS
DENTON
5
PRIMARY CARRIER TOLL CONNECT TABLE 060: END OFFICE ->TOLL CENTER
u
60 60 00
C
1.A I
54x 5 14 542
I1
---KEY-- Cl,Ll----
A C C Y T X X A A C F F T X X A A C K R T X X A
E
F R O M 1.EC-
0332 2143 216X
G
T R A N i_I<('2
H
CLASS 4,s CLLI----
WCFt .TXN I L R C K I X P S M DLDIXM U
I
LEV-
5216 521h 5216
J
A S S O C PTC CLL.I----
K
LEC-
L
T R A N LEC3
M
T R A N L E C 4
N
FROM-C1.I.I I I
ACCY I X X A R S O A C F t 1 X X A D S O AC'KR I X X A R S O
0
Toll Switch
PTCI ,LI -
O L N Y T X X A W D R W T X X A I~TI iR' I 'XXA
A 13 C 1) E F-G
I 1
I J K 1,-M
N 0
P
v) z tx1 ? b A do w
E'rimary Carrier 'Table name or type and date of activity (A-add, C-change, R-rehome) l'rimary C'arrier table number. 1.ATA number used in positions I37 ~ 140 i n the 92-99-01 summary records. ~~xchange CLL1 code (settlement GLIA code). This is used in positions 145 ~~ 155 and I56 LEC/CI,EC company number. Company number of LEC/CLEC that owns facilities between the exchange and the Toll Center. This is used in positiolls 8 1 95 - 98, 102 - 105, 109 - 112, I16 - 119, 123 I f there is no entry in column J, then this entry is the Toll Center CLLI code. If there is an entry in column J, then this entry is the tandem CLLI code. The tandem or Toll Center company number. The Toll Center CLLI if column I1 is populated. 'The Toll Center company number. Company number of LECKLEC that owns facilities between the exchange and the 1.011 Center. ']'his is used in positiorls 8 1 95 - 98, 102 ~- 105, 109 - 112, I16 - 119, 123 'I'he I 1 character CLLI code for the aggregating N P N N X X found on Table 80, column <;. Frlle point where toll switching occurs i f the toll is not switched by the toll centers listed in Table 70. 'This usually applies to intracompany traffic. The toll switch point compaiiy number.
166 in the 92-99-01 s1iiIII11;1ry records.
84, 88 9 1, 126, 130 -- 133 in the 92-99-01 summary records.
84, 88 1 126, 130 - 133 in the 92-99-01 summary records.
6
I'
roil Sw i tcli
I .II( ' -
0332 2147 2 I o x
PRIMARY CARRIER TOLL CENTER TABLE 070
A
TOLCENTR c97 1002
TOLCENTR TOLCENTR TOLCENTR
B
70 70 70 70 70
C
NPANXX 214815 940369 903388 8 17332 903813
D
CLLI---- DLLSTXTA DNTNTXXA FRFDTXXB FTWOTXED SHMNTXXA
E
LAT 552 552 552 552 552
F
TOLL-CENTER-NAME-- DALLAS DENTON
FA IRF IE LD
SHERMAN FORT WORTH-EDISON
A
B Primary Carrier Table number C D E F
Primary Carrier Table name or type and date of activity (A-add, C-change, R- rehome).
NPANXX used to identify the Toll Center or tandem on Table 80, column H. The CLLI code of the Toll Center or tandem. Lata number used in positions 137 - 140 in the 92-99-0 1 summary records. Toll Center or tandem name.
SWBT-AR-84
PRIMARY CARRIER NPANXX TABLE 080: NPANXX TO CLLI
D A
C960102 C97 1002 NPANXX
A Primary
E B
80 80 80
SETTLE
COMOTXXA FSBGTXXA GNTRTXXA
CLLI----
C
--KEY-
NPANXX 903488 940964 903433
LEC- 2154 2116 4344
’anier Table na le or type and date ofac
F
PTC- 2154 4344 4344
vity (A-
G I ” AGGRE-
GATE NPANXX 903488 940964 903433
TOLL CENTER NPANXX 214815 940369 9038 13
dd, C-change, R-rehome).
I
LAT 552 552 552
J
TRUE LERG
--CLLI-- COMOTXXA FSBGTXXA GNTRTXXA
K
0 P R
B Primary Carrier Table number. c‘ NPA/NXX associated with a LECICLEC operating in the state.
8
DATA EXCHANGE
Calling Scope Tables
These tables are utilized by the Primary Carrier system to correctly identify local/local and local/EAS usage as defined in the interconnection agreement between SWBT and the CLEC.
Tables 1 and 4 are initially created by SWBT. The tables are updated by each holder of the tables based upon the information contained in Primary Carrier Table 80. These tables are used by SWBT in processing local usage terminating to CLECs.
Examples of the Local Calling Scope tables are provided on the following pages.
SWBT-AR-86
9
NPANXX 817441 817441 81 741 9 8 1 7449 8 1 7465 8 1 7268 8 1 7280 8 1 7282
TABLE 1 SWBT Exchanges in the Local Calling Area
Use in the XYX Co.-CLEC Agreement For the Ft. Worth, TX Metro Area
SETTLE c LLI ---- FTWOTXAL FTWOTXAR FTWOTXAR FTWOTXAR FTWOTXAR FTWOTXAT FTWOTXAT FTWOTXAT
LEC- 521 6 521 6 5216 521 6 521 6 5216 5216 521 6
PTC- 5216 521 6 5216 5216 521 6 5216 5216 521 6
LATA 552 552 552 552 552 552 552 552
LERG --CLLL FTWOTXAL FTWOTXAR FTWOTXAR FTWOTXAR FTWOTXAR FTWOTXAT FTWOTXAT FTWOTXAT
NPANXX Is the three digit NPA combined with the three digit NXX assigned in Bellcore’s Local Exchange Routing Guide (LERG) and obtained from SWBT PTC Table 80.
SEITLE CLLl Is the eight digit code used for access settlements and is used in
positions 22-29 and 36-43 in the 92-99-01 summary message records. This is obtained from SWBT P I C Table 80.
LEC This is the Local Exchange Carriers OCN Number and is obtained from LERG by way of SWBT PTC Table 80.
PTC This is the Primary Toll Carrier within a LATA who is assigned responsibility for the Settlement CLLl for toll and local settlement purposes and is obtained from SWBT PTC Table 80.
LATA This is the Local Access and Transport Area (LATA) code for the Settlement CLLl and is obtained from LERG by way of SWBT PTC Table 80.
LERG CLLl This is the True LERG CLLl and is found in the Bellcore LERG for a given NPA-NXX and due to PTC billing program requirements may be different than the PTC Settlement CLLI. This CLLl code is obtained from LERG by way of SWBT PTC Table 80.
SW BT-AR-87
10
NPANXX 972359 972390 972727 817783 8 1 7790 817517 81 7645 214213 214215
NPANXX
SETTLE CLLl
LEC
PTC
LATA
LERG CLLl
TABLE 4 SWBT Exchanges in the Optional Calling Areas
Use in the XYX Co.-CLEC Agreement For the Ft. Worth, TX Metro Area
SETTLE c L L L - ALLNTXSA ALLNTXSA ALLNTXSA ALVDTXTI ALVDTXTI CLBNTXMI CLBNTXMI DLLSTXAD DLLSTXAD
LEC- 521 6 521 6 5216 5216 5216 521 6 521 6 521 6 5216
PTC- - 5216 521 6 521 6 5216 5216 5216 521 6 521 6 521 6
LERG LATA --c LLI -- 552 ALLNTXSA 552 ALLNTXSA 552 ALLNTXSA 552 ALVDTXTI 552 ALVDTXTI 552 CLBNTXMI 552 CLBNTXMI 552 DLLSTX31 552 DLLSTX31
Is the three digit NPA combined with the three digit N M assigned in Bellcore’s Local Exchange Routing Guide (LERG) and obtained from SWBT PTC Table 80.
Is the eight digit code used for access settlements and is used in positions 22-29 and 36-43 in the 92-99-01 summary message records. This is obtained from SWBT PTC Table 80.
This is the Local Exchange Carriers OCN Number and is obtained from LERG by way of SWBT PTC Table 80.
This is the Primary Toll Carrier within a LATA who is assigned responsibility for the Settlement CLLl for toll and local settlement purposes and is obtained from SWBT PTC Table 80.
This is the Local Access and Transport Area (LATA) code for the Settlement CLLl and is obtained from LERG by way of SWBT PTC Table 80.
This is the True LERG CLLl and is found in the Bellcore LERG for a given NPA-NXX and due to PTC billing program requirements may be different than the PTC Settlement CLLI. This CLLl code is obtained from LERG by way of SWBT PTC Table 80.
SWBT-AR-88
1 1
I DATA EXCHANGE I
8. Primary Carrier System Timeline
The Primary Carrier system performs specific functions at specific times during the month. LECs/CLECs must utilize the timeline provided to ensure the timely exchange of data thus resulting in the appropriate intercompany compensation and settlement of alternately billed messages.
i
. ..
1 SWBT-AR-89
I DATA EXCHANGE I .. . -
Monthly Schedule
1" Work Day
2"d Work Day
3rd Work Day
4'h Work Day
12'h Work Day*
13 th Work Day
5'h Work Day
- The following records must be received by noon: 92-01 -XX Clearinghouse Records 92-01 -XX Settlement Records
- By4p.m. S WBT will send any applicable 92-0 1 -XX records Transmission will contain 92-0 1 -XX data received by noon on 1 St work day
- Data received by LEC/CLEC
- 92-99-0 1 processing begins
- By4p.m. 92-99-01 s are distributed
- 92-99-0 1 s are received
- A month later SWBT mails billing statements
*92-99-01 s may be distributed prior to the 12th work day.
SWBT-AR-90
2
I DATA EXCHANGE
9. ClearinghouseKATS
SWBT serves as the Clearinghouse agent for the LECsKLECs operating in the SWBT five state areas. In its role as Clearinghouse agent, SWBT is responsible for the settlement of intraLATA toll alternately billed (third number, calling card and collect) messages.
The Clearinghouse system returns the end user toll revenue (minus a 5-cent per message billing and collection charge) from the billing company to the originating (earning) company .
For calls billed in another of SWBT’s states (i.e., an intraLATA alternately billed toll call originated in Texas and billed in Kansas) the money is moved from the billing state (Kansas) to the earning state (Texas). This process is included in the Clearinghouse settlement process.
The Clearinghouse agent assesses the originating company a 2-cent per message charge for processing the message. This charge is reflected on the netting statement.
1 SW BT-AR-9 A
I DATA EXCHANGE I
Clearinghouse Svstems
CATS
An intraLATA calling card or 3rd number message originating in the SWBT 5 state area and billed outside of the SWBT 5 state area.
i
Cleariwhouse
An intrastate intraLATA collect, calling card or 3rd number message originating in a SWBT state and billed in one of the SWBT states.
S WBT-AR-92 3 L
I DATA EXCHANGE I
Clearinphouse CharPes
0 Billing and Collection Charges
0 5 cents 0 Remitted to the billing company
0 Processing Charges
2 cents 0 Paid to the Clearinghouse agent (SWBT) by the
originating company
SWBT-AR-93
I DATA EXCHANGE
Example Reports
Clearinghouse Reports
CATS Reports
Examples of the Clearinghouse and CATS reports are provided on the following pages.
SW BT-AR-94 4
(‘A IS EARNED REVENUE REPORT INI)l!I’ENIX!NT CO STAlE SIJMMARY
33 SNJB4 3 N
SOIITIIWI!STI!HN 11l!1 .I.
DAm M W Y Y :
M R N t ! D BY : COMPANY NUMBEIKOMPANY N A M E ( I I ! X A S ) Illl.l.W I l Y A L L COMI’ANII!S
INTWALAI A SrCIION , ,NTRASTAm ............................... ._..._..... ........ _._-.-.. - MeSSAOeS T A X WEVt!NIJI! A I .ICs MSO TOTAL 2.279 $IOU70 S3.0J3 2 0
2 BlLLlNO CIiAROl!S S I 13 60 3 IM R A S l N M RUV 2,279 sloe 70 $2.939 60
IN W R L A I A
MeSSAOeS TAX Rl!VI!NIW
..................................
0 s 00 s 00 $ 0 0
0 s 00 $ 0 0
I . (X ‘AI .
MESSAGES T A X RI!VI!NIII! . . . .
69 S I on $22 20 53 45
6 Y S I 08 $18 1 5
0 J no $ o(l 4 HICI’IJNN HI!VI!NIJl!
M A R K I T SI!(IMI!NTS . . . . . . . . . . . . . . . . Ill I)A
2 I ’AYI ’ I I i )NI ! I ) A 3 I ’AY I’IIONI! 1.W.‘ 4 I ’AYYI I (1NU IC ~PAYl’l lONf!(:l lSr 6 sc r IISU FEE 7 VBNDOR CIIAROt! ( 6 MOIIII I! 9 IM:O PROVIDI!R
10 RL?S/IIIIS
(
...................... CI .TOTAI.
1 0 s no 5 00
2 1 I
13 1 0
us 0 ) 01 0 0
1.1106
2.279 .....
U J s 20 $ 4 60 IO 00 I2 66 so 00 so 00 so 00 $0 00
$100 31
SI08 70
0 0 0 0 0
0) 0 ) 0 0 0
0 .......
I I $ 1111
0 s o 0 f b s n 4
0 1 011 0 s 00
OJ J 0 1 ) 0) $ 00 0 I00 0 s 00 3 S 24
69 si on ....
SECTION 2 INTERSTATE
DI ICs MSCI TOTAL*
. . . . . . . . . . w . . .
2 IIILLINO C‘IIARGCS 3 INIf!WSI NET R e v
4 Hl iTl lHN RI!VI!NIII!
0 s 00 s o 0 so0
0 so0 s 00 2 5
5 $00 $6 2 1 TO-FAL I N I R A S T A T E .
MI!SSA(II!S: 2 . 3 . ~ J l W 7u TAX:
REV l?N I If!- sz.o)n 35 A V O RI !VIMSO: S I 2 5
MI?SbAGt!S 5 T A X : $ 0 0 REVf!NIII!: $6 27 A V O REVlhlSO. S I 2 5
M@SSA(IBS Z , . I > l TAX: I I ( r ) . l U
. REVRNIIl!: 52.964.62 A V O RI!V/MSO: SI 25
PRWBSSINO DATE: MMlUDNR PROCESSIN0 TIM@: tIWMIN/SUC
IO1 A I IN.FI!RSTA-II!
O R A N D TOTAI.:
J O I I 0 S 00 $ 00
MARKI! I SUCIMI!NTS . _ UI D A
2 PAYPIIONI! UA 3 PAYYllONR I - e C 4 PAYPllONB IC S YAYPIIONRCIJST 6 SKF MI! I?@ ( 7 VBNIXJR CIIAROB ( II MOUll I! 9 INRI I’R0VII)ER IO Ht!s/!!lJ~~ . _.- _ _ .
PI TOTAL 01 O R A N D TO1 AI .
5 00 s 00 s 00 s 00
so0 ( so0 f s 00 s 00
54 94
$6 5 2
S I 5n
. . . . . . . .
s 2 . w n7
0 0 0 0 0
0 ) 0 ) 0 0
s 00 $00 $00 s 00 s 00 s 00 s 00 s 00 s 00
s 00 t 00
.A O? ..
I 00 s 00 s 00 s 00 S 00 s 00 s 00 s 00 5 00
S 00 s 00
3 e?
0 0 0 0 I
0 ) 0 ) 0 0 4 J
2.284
............. 0 0
............ ....... .........
0
I’HOl’HII!FARY --. B@UCOR@ AND AUTllORJZeD CLleN TS ONLY
Id091611'2fMS .... B3IION .... C l 662'9s 88 t Z C ' 9 S
00 s 00 s 00 s 00 s LT CS 00 s 69 SS 00s on s
-. is c ic%S
00 s I 6hz49S
SL CES R R ZZf 9s
5 1 ) S l b OLk 0 0 (0 (0 I 0 b 0 0
.......
0
SLP
SLP
I O 8OZ'ps
P8 6b8'IS 00s 00s 00s 00s b t CS 00s H 6 b S ,
OOS M S
F.! I?'!! OL 9P lS
00 s 00 t 00 t 00 s 00 t 00 t 00 s 00 t oot 00 s
E!. -.
' IVIOI CJNVMO' IO POP'C 6Ct ' I V I O l . I d 8 i i - sfl WSaM'Ol
Maal A O I d alN1.6 0 0 E11IrlOW'8
) a D l V H 3 UOUNBA L (0
t lsn3 aNOlldAVd'C 0 31 aNOlldAVdb 6C S I BNOIldAVdt 0 V a a N O l l d A V d 2
.............................
(0 1 aiw nsn iils'9
0 va. I R .......................... S u i a W w t s . a ~ i l y ~ v c y
.... ... .....
9 b Ilf OE 68 1'8s 00s k l f
i l l lN i lAaY N H l l l i l l b
A W M N lSMalN1 C SBDIIVII3 ON11~118 2
00s 00s 0
L I ohn'is 00 s 6CE C6 IIS E l Z O h ' l t 00s 6rt IVLQL DSW s a ia
\o .............................. a l V l S Y i l l N l Z N 0 1 1 3 a S
00s
00s
00s
: x v I :Silwssaw
:il L V I S V N L N I 1 V J O . l - - - - - - - - - - - j
0 OL 9 b I s . . . . IZ ant 00 us 00 os ou ns on nt u1 L t 00 (1% L G 6fl 69 s Z ( z t
SPC'C
C T L ' I 0 o 10 (6 AI* 0 91 C' 1 11 IC
..... -- .. ... ... Zl,O
0 0 (0 ill V I , I 0 9W' I LZ R I
0 0 0 ( 0 (0 0 0 0 0 0
I
(MI s 00 t U 00 P 0 0 s 0 (MJ 0% 00 s 0 i l l l N i l h i i Y N Y l l l i l M P
PB 1 I ( ' t i OL 9PlS S9C'C A a H l i l ~ LSVMLNI c 01 9 b l t W'C 1 V l Q I D S W S 3 1 I V
i l f l N i l A i l M X V l ~ O V S S ~ -.... ............. .--.-..-..-. m POC'H S B O l l V l l D ONll l lH t CZ 891s
.............................. i L l V l S V U I N 1 I N O I W R S V IV ' IVW I N 1
PZ OC('ZS LZ ZES bLS'Z 01 9 L l S tfl95b'?S c7 78s bCS'2
i l l l N i l A A M X V I S i IOVSSi IW
IV.)(l I
00 s 00s 0 00 s 00 t oot 0
i l l l N i l A i l H X V I W D V S S a W ................................. VI.V'IH;I l NI
.I l r l l l N H t I l S i l M I l . L I I 0 S
Nb b8SNS C C
REPORT AC3S83 001
UW-PCC, PART X I . SEX X SWUT-DP CRT DALLAS
T e X A S INTRALA FA IN1 I!RTANDEM ClEARlNOllOUSB LEC DLTAll. H1!I'ORT
PTC I ) A l A MONl II
PAW!
R U N I ) A l I!
RI!Il!NTION 0 1 ' 4 1
x 1 4 ) in
o on n oo 0 00 0 00
It 00 0 00 0 00 0 00
I I I J O I I bIXJ I .002 2 3 + 4 u5 0 0 0 )(I 10 2.494 13 I .26Y 1 4 1 1 4 8 I 1 uo 61 J I
2 RED
3 RET
4 TOT
0 0 00 0 00 0 (X) ow 0 0 111)
0 0 00 0 00 o m i 0 00 0 It I10
1,269 1 4 1 7 4 n o on 63 4'1 1,374 0 3 819 28 I.002 1,544 US 000 >o 10 2.494 7 5
MeSSAOE R@VENll(! I>@TAIL:
5 COI 338 I .OlU 20 0 co 6 MOB 0 000 000
0 0 0 4
7 BR 6b4 I .4(r6 65
I6 W
000
3 3 20
I .OC I 30
000
I .4J3 45
JS2
0
n17
231 4 2 1.312 7 2 1.335 3 2 0 00 2 2 60
0 00 0 00 0 00 0 00 0 00
b27 86 2.061 31 2,102 16 0 00 40 85
1.W WILL. RECEIVE 87Y 28
Y (CALCULAIION. ROW I - ROW S * HOW 6 * ROW 7 )
g 4(
(CALCIJLATION: HOW 4 - HOW I . (HOW 2 ROW 3) )
cb
I DATA EXCHANGE 1
10. Primary Carrier CLEC Checklist
This section contains a copy of a checklist that should be completed by the CLEC and forwarded to the SWBT Account Manager. This checklist will provide the CLEC with a guide in identifying the information necessary to successfully accomplish the intercompany compensation billing process in an accurate and timely manner. The completed checklist and any subsequent revisions should be mailed/faxed to:
S WBT Director-Carrier Compensatiofiilling One Bell Center, 32-B-1 St. Louis, MO 63 101 Fax: 3 14-247-41 85
Also included in this section is an explanation for each of the fields on the checklist and the information required in each section.
SW BT-AR-98 I
DATA EXCHANGE I
Primary Carrier CLEC Checklist
1. CLECName /1)
2. Company Number fB 3. Service Area (3)
4. Effective Date (41
5 . N P m X x s (5)
6. CLLI Code(s) (6)
7. CMDS Host (7l
8. RAONumber (8) Status Full (9) Non-Full
9. Operator Services Provider [lo)
If SWBT, will SWBT provide rating function Yes (11) No
10. Appendix Signed CH Yes (12) BCR Yes (13) Host Yes (141
No No No
1 1. Type of media used to exchange originating category 92 summary records (15) NDM TCP/IP Tape 18track
12. Category 92 Vendor Name (1 6) Vendor Number (1 n
Page 1 of2
2 SWBT-AR-99
I DATA EXCHANGE I
Primary Carrier CLEC Checklist
13. Facilities Used for: (18) 1+ ILEC IXC OPH ILEC IXC
14. Does this interconnection agreement contain EAS calling areas? (19) Yes No
15. Have intraLATA BIPs been negotiated? (20) CLEC SWBT
16. Please provide the following Compensation Rates: (21) LocalLocal Special Provisions Transit Optional EAS IntraLATA Access Rates: CCL
LTF TST RIC
17. Primary CLEC Contact Name (22) Telephone Number (23) FAX Number (24)
18. CLEC Billing Contact Name (25) Telephone Number (26) FAX Number (27)
19. Data Contact Name (28) Telephone Number (29) FAX Number (30) Mailing Address (31)
20. SWBT Account Manager (32)
Remit to: S WBT Director-Carrier CompensatiodBilling One Bell Center, 32-B-1 St. Louis. MO 63101 F a : 314-247-4185
Page 2 of 2 SWBT-AR-100
3
I DATA EXCHANGE I
Primary Carrier CLEC Checklist
- Title
(1) CLECName
(2) Company Number
(3) Service Area
(4) Effective Date
(6) CLLI Codes
(7) CMDSHost
(8) RAONumber
(9) KAO Status
Descrktion
Enter the name of the Company.
Enter the four-digit NECA facility based company number.
Enter the metropolitan (geographic) area in which the CLEC will be providing service (e.g. Dallas, Austin, St. Louis, etc.). Each new metro area in a state should have a new checklist completed.
Enter the date when service is to begin.
Enter the N p A M x x s assigned to the CLEC.
Enter the CLLI codes assigned to the NPAMXXS.
Enter the name of the CMDS Host.
Enter the RAO.
Enter the RAO status of this company. If the company is Full status, they will be assigned their own RAO number. If' the company is a non-full status company, they will share an RAO number with their host.
4
I DATA EXCHANGE I
.-
- Title Description
(10) Operator Services Provider Enter the name of the OSP.
(1 1) Rating Function
(12) Appendix CH
(1 3) Appendix BCR
( 14) Appendix Host
(1 5) Data Exchange Media
(16) Category 92 Vendor
(1 7) Vendor Number
If SWBT is the OSP, will they provide the rating fbnction? A ‘NO’ answer will impact the requirements necessary for the Clearinghouse hnction.
Has Appendix CH to the Interconnection Agreement been signed? This appendix addresses the settlement of alternately billed (calling card, third number and collect) toll messages.
Has Appendix BCR been signed? This appendix addresses billing, collection and remittance of specific services.
Has Appendix Host been signed? This appendix addresses the CMDS hosting of the CLEC by SWBT. This agreement provides for either nation- wide hosting or in-region hosting.
Enter the type of media used for Category 92 record data exchange. For NDM and TCPAP, additional time is required to establish the facilities.
Enter the name of the vendor who will be preparing your Category 92-99-01 records (if applicable).
Enter the vendor number.
5
I DATA EXCHANGE
- Title Description
(1 8) Facilities Used
(1 9) EAS Calling Area
(20) IntraLATA BIPs
(2 1) Compensation Rates
(22) Primary CLEC Contact
(23) Primary CLEC Contact'
(24) Primary CLEC Contact
(25) CLEC Billing Contact
(26) CLEC Billing Contact
(27) CLEC Billing Contact
(28) Data Contact
Indicate the facilities that will be utilized for each of the traffic types listed.
Indicate whether or not this agreement provides for EAS calling scopes.
Enter the intraLATA Billing Percentages (BIPs) for the CLEC and SWBT.
Enter the applicable rates for each of the traffic types.
Enter the name of the primary CLEC contact.
Enter the telephone number of the primary CLEC contact.
Enter the FAX number of the primary CLEC contact.
Enter the name of the CLEC billing contact.
Enter the telephone number of the CLEC billing contact.
Enter the FAX number of the CLEC billing contact.
Enter the name of the Data contact for the CLEC (employee, vendor, etc.).
6 SWBT-AR-103
I DATA EXCHANGE I
- Title
(29) Data Contact
(30) Data Contact
(3 1) Data Contact
(32) Account Manager
Description
Enter the telephone number for the above named Data contact.
Enter the FAX number of the Data contact.
Enter the Mailing Address of the Data contact.
Enter the name of the SWBT Account Manager.
SWBT-AR-104
7
1.
2.
3.
4.
5 .
Primary Carrier CLEC Checklist
CLEC Name
Company Number
Service Area
Effective Date
NPA/NXXs
6. CLLI Code(s)
7. CMDSHost
8. RAONumber Status Full- Non-Full
9. Operator Services Provider
If SWBT, will SWBT provide rating function Yes No -
10. Appendix Signed CH Yes BCR Yes Host Yes
No No No
1 1. Type of media used to exchange originating category 92 summary records NDM TCP/IP Tape 18 track
12. Category 92 Vendor Name Vendor Number
Page 1 of2
1/98
Primary Carrier CLEC Checklist
13. Facilities Used for: I + ILEC OPH ILEC
IXC IXC
14. Does this interconnection agreement contain EAS calling areas? Yes No
15. Have intraLATA BIPs been negotiated? CLEC SWBT
16. Please provide the following Compensation Rates: LocalLocal Special Provisions Transit Optional EAS IntraLATA Access Rates: CCL
LS LTF TST RIC
17. Primary CLEC Contact Name Telephone Number FAX Number
18. CLEC Billing Contact Name Telephone Number FAX Number
19. Data Contact Name Telephone Number FAX Number Mailing Address
20. SWBT Account Manager
Remit to: S WBT Director-Carrier CompensatiodBilling One Bell Center. 32-B-1 St. Louis, MO 63 101 Fax: 314-247-4185
Page 2 of 2
SWBT-AR-I06
ARKANSAS DATA
DISTRIBUTION GUIDELINES
FOR CATEGORY 92 SUMMARY RECORDS
Southwestern Bell Telephone Company Carrier CompensatiodBilling District
December 1998
SWBT-AR-I 07
DATA DISTRIBUTION GUIDELINES
Table of Contents
1.
2.
3.
4.
5 .
6 .
7 .
8.
9.
Introduction
Definitions
Data Distribution Service Description
Data Exchange Timeline
Header and Trailer Records
Data Exchange Media Options
Dataset Naming Conventions
Data Tape Transmittal
Compensation
1
~
DATA DISTRIBUTION GUIDELINES
1. Introduction
This document has been prepared to provide the guidelines supporting SWBT's Category 92 Summary Record Data Distribution Process in the state of Arkansas. The references to data set names, monthly processing schedules and company codes are Arkansas specific and may not be appropriate for use in any other state.
The Category 92 record process utilizes originating end user recordings. It is the responsibility of the originating company to create the appropriate Category 92 records and provide them to all the other Primary Carrier ILECs andor CLECs on the call path.
2. Definitions
CLEC: Competitive Local Exchange Carrier ILEC: Incumbent Local Exchange Carrier IXC: Interexchange Carrier LEC: SWBT: southwestern Bell Telephone Company
Local Exchange Carrier (generic term for ILEC and/or CLEC)
2
DATA DISTRIBUTION GUIDELINES
3. Data Distribution Service Description
Under this service S W T will assist other companies in the transmission of their originating 92-99-01 summary usage records to the appropriate Primary Carrier ILECs and/or CLECs on the call path involved in transporting and/or terminating the underlying messages. The companies will send the 92-99-01 summary usage records to be distributed by SWBT via a separate tape or data transmission from the records to be processed by SWBT's billing system. A separate "data pack" is required for each receiving company (the receiving company is identified based on the information contained in the "Receiving Company" field on the 92-99-0 1 summary usage records). SWBT will distribute the data packs containing the 92-99-01 summary usage records sent to it by the other companies based on the information contained in the data pack's Header Record. No records will be created for the other companies by S W T as a part of this service. The only 92-99-01 summary usage records that qualify for inclusion in the Data Distribution process are for completed ILEC and/or CLEC transported intrastate intraLATA Toll and Local traffic that was carried over jointly provided ILEC and/or CLEC telecommunications facilities (Le., excluding IXC carried traffic).
4. Data Exchange Timeline
Monthly Schedule
sth Work Day - Data Packs to be distributed are received by SWBT.
12Ih Work Day - Data Packs received by other companies from SWBT.
Data Packs received after the 8Ih work day will be processed in the following data month. Data Packs that do not conform with these guidelines and/or cannot be processed by SWBT will be rejected. It is the responsibility of the sending company to provide any necessary corrections and resend the rejected data.
3
SWBT-AR-I 10
DATA DISTRIBUTION GUIDELINES
5. Header and Trailer Records
Introduction to 20-XX-XX Header and Trailer Records
When mechanized data is transmitted between Parties, standard EMR Pack Header and Trailer conventions are used as well as unique compensation plan Pack Header and Trailer records. The compensation plan Header and Trailer records are identified as 20-90-XX and 20-9 1 -XX and are defined in this section. For transmission purposes, Category 92 records must be packed separately from other EMR records.
There are two types of standard Bell - Non-Bell Exchange Camer Pack Header and Trailer record formats:
Full RAO records 20-20-xx Non-Full RAO records 20-2 1 -xx
For Category 92 records, substitute 90 (Full RAO) or 91 (Non-Full RAO) for the record group in the standard EMR Bell - Non-Bell Exchange Carrier Pack Header and Trailer records formats:
Header Trai 1 er Full Rao 20-90-0 1 20-90-02 Non-Full RAO 20-9 1-0 1 20-9 1-02
All Companies should total the number of Category 92 summary records (92-99-01) contained in each pack. This total is reflected in the Grand Total Record Count field on the Trailer record (20-90-02 fields 1 1 1-1 17 or 20-91-02 fields 95-101).
Examples of the 20-90-XX and 20-91-XX record layouts are provided on the following pages.
4
SWBT-AR-111
I DATA DISTRIBUTION GUIDELINES I Instructions for Creating Full Status RAO Header Records (20-90-01)
FROM TO LENGTH ~~ ~
TYPE VALUE DESCRIPTION
1
7
13
15
17
20
23
26
40
44
6 6
12 6
14 2
16 2
19 3
22 3
25 3
39 14
43 4
210 167
N = Numeric
N
N
N
N
N
N
N
N
N
N
20900 1
YYMMDD
0 1-99
33
0 Filled
0 Filled
SOURCE
Table 30
Table 30
Table 30
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
Originating Company’s RAO
Receiving Company’s RAO
Billing Company’s RAO
Not Used
Originating Company’s four-digit NECA Company Number
Not Used
All the information in Fields 7-25 must match the information contained in the associated Trailer Record
5
SWBT-AR-I 12
Full RAO Pack Header Record
90 I i1
01 - - 20 - Field Description I Field Description 11
Por Char 1 1 I 1
Record 9 Identincation
I 1
Year - Date 9 9
10 Month Created 11 12 Day 13
14 invoice Number 9 15 16 Company Number 9
- -
4 7 /q dl9
From RAO 1 -
20 21 22
- - Sent to RAO 9
23 24 26 26 27 28 29 30 31
- - Billing RAO !
- -
Resewed
Local Company
US2
ReSeWed
Po. 68 69 70 71 72 73 74
- - - - -
ha
1 Field Description
Resewed
SWBT-AR-113
6
I DATA DISTRIBUTION GUIDELINES I Instructions for Creating Full Status RAO Trailer Records (20-90-02)
FROM ~~
TO LENGTH TYPE VALUE SOURCE DESCRIPTION
1
7
13
15
17
20
23
26
111
118
6’ 6
12 6
14 2
16 2
19 3
22 3
25 3
110 85
117 7
210 93
N
N
N
N
N
N
N N N
N
209002
YYMMDD
01-99
33
0 Filled
0 Filled
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
Table 30 Originating Company’s RAO
Table 30 Receiving Company’s RAO
Billing Company’s RAO
Not Used
Grand Total Record Count (Total number of 92-99 summary records contained in this pack - this is a right justified field)
Not Used
N = Numeric
All the information in Fields 7-25 must match the information contained in the associated Header Record
7
SWBT-AR-I 14
- 20 I
Field Description 1 Pos
Record ldentiflcatioi
5 b RecordType
r 0 Year 9
10 Month Created 11 12 Day 13 14 Invoice Number 15 16 Company Number
-
- Date
- - -
4 7 Jq ‘4P
From RAO
Reserved
I 47 I
Reserved
-. Field Characteristic: 9 = Numeric
Full RAO Pack Traller Record
90
Field Description
-
I Pot
Reserved
- 08 09 90 91 92 93 94 96 96 97 98 98 100 101
- - - - - - - - - - -
Grand t I Total
Revenues
Cent
114
Grand Total
Record Count
117 iir 118 I 1 Hour 1 Time
Mhute Created
122 NBEC Indicator 123 -.
1 24 Reserved 126 126 127 Status Code 128 129 130
132 133 1
- -
- - -
131 Reserved - -
hanumeric
8
02 r -
Field Description
RWXVed
SWBT-AR-115
DATA DISTRIBUTION GUIDELINES
Instructions for Creating Non-Full Status RAO Header Records (20-91-01)
DESCRIPTION TO LENGTH FROM
1
7
13
15
17
20
24
28
34
6 6
12 6
14 2
16 2
19 3
23 4
27 4
33 6
210 177
TYPE VALUE SOURCE
N 209101
N YYMMDD
N 01-99
N 33
N . 147
N
N
N
N 0 Filled
Table 30
Table 80
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
SWBT RAO
Four-digit number of the LEC or Service Bureau sending the data
Four-digit number of the Responsible LEC
NPANXX of the Company to which the data should be sent
Not Used
N = Numeric
All the information in Fields 7-33 must match the information contained in the associated Trailer Record
9
SWBT-AR-116
Non-Full RAO Pack Header Record
Field Description
Record 9 Identification
1 6 RecordType 7 8 Year 9 Date 9
I O Month Created 11 12 Day 13
- - -
lnvolce Number
ldentlficatlon Number
lnterfaclng Bell RAO Code
ILEC or Sewlce Bureau
_- tu1
I I
I - 2s ILEC 9
27 28 2s NPA
- 26 ldentlncatlon Code
- - 30 Billing 9 - 31 Company 32 NNX 33 34
- I
36 Reserved 9
37 Numbw of R a w 9 36 - - - 38 Sent Pald Messages 39 - 40) 1 11 I I
_I - Number M)
- 51 Received Coaect 9 - 52 Messages 53 54 56 56
- - - $ Reahred - 57 COlIect 9
58 ReVenUe 59 60 Cent 6 4
-
Number of Non-Billable 9
RccordS I
Held Characteristlc: 9 = Numeric
91 I
- Field Description 1 E, , ,Char
- 67 -
Non- Blltabfe - 68 $ 69 Revenue 9 70 71 72 Cent 73 74 Number of
- - - - - 76 Returned Messages 9
77 1 76 - f
Number o? U n ~ M e s s a g a s
Percent E m
I X = Alphanumeric
10
01
Field Description
-
Po, 131 132 133
136 136 137
- - Total Totaf
134 Mlnutes Universal - Voluma -
O V e W Count
Reserved .-
149 1 Status lndlcator 150 I
Resewed
SWBT-AR-117
DATA DISTRIBUTION GUIDELINES
Instructions for Creating Non-Full Status RAO Trailer Records (20-91-02)
FROM TO LENGTH TYPE VALUE SOURCE DESCRIPTION
1 6 6 N 209 102 Record Identification
7 12 6 N YYMMDD Date Created
13 14 2 N 0 1-99
15 16 2 N 33
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
17 19 3 N 147 SWBT RAO
20 23 4 N
24 27 4 N
28 33 6 N
Four-digit number of the LEC or Service Bureau sending the data
Four-digit number of the Responsible LEC
NPANXX of the Company to which the data should be sent
Table 30
Table 80
34 94 61 N 0 Filled Not Used
95 101 7 N Grand Total Record Count (Total number of 92-99 summary records contained in this pack - this is a right justified field)
102 210 109 N 0 Filled Not Used
N = Numeric
AU the information in Fields 7-33 must match the information contained in the associated Header Record
1 1
SWBT-AR-I I 8
- 20
Record Identification
5
Field Description (". , , ;"h
5
I 132 - - 133 ToQl Total 134 Minutes Unlversat - 136 Volumes
136 137 138 Dlrectiona I lndlcator 139 140 141
143 144 146 146
-
- - Totat - Access 142 OveMow - C a n t -
I
pi Date Month Created
11
9
Day I 78 -
79 - - 80 t Returned - 81 Message 9
82 Revenue 83 84 Cent -
lnvolce Number Bel Company
16 ldentltlcatlon Number 17 .. - - 4 8 Interfacing Bell . g
19 RAO Code 20
54 55
Received 56 t sr Collect 9 58 Revenue 59 60 Cent
- - - - -
6 4
Sewlce Bureau
Number of Rated Sent Paid Messages
Sent Paid 9 Revenue
47
Number Recelved Collect
Messages
Number of
Records Ich :TBlllab; 1 9
arac e s c: = umerc
Non-Full RAO Pack Trailer Record
91 - I I Field Description
Non- Blllable Revenue
70 7 9
Number of Returned Messages
Number of Unrated Messages
f Grand Total
Revunes
Count
Error Recorda
Cent 112
Recorda
Total Acmt8s
overnow RccCrnk
9
. ..
t 118 I I I
I
I
I Field Description Por 131 I I
Resewed
Status lndlcator 149 I
Resewed 9
SWBT-AR-119
12
I DATA DISTRIBUTION GUIDELINES I
6. Data Exchange Media Options
The following media options are available for the transmission of data:
Electronic NDM TCP/IP
18 Track
7. Dataset Naming Conventions
The dataset should be named in such a way as to identify the originating Party. The following are the recommended naming conventions:
Electronic MPSH.AG5301 lA.INDCO.# # # # XXXX
w e MPSH.AG530.# # # # XXXX
Where # # # # = Company Name Abbreviation (Alpha) Where XXXX = Four-Digit NECA Company Number (Numeric)
Each transmitting company should coordinate with the receiving company to define the transmission specifics of the data file.
13
SWBT-AR-120
DATA DISTRIBUTION GUIDELINES
8. Data Tape Transmittal
A tape transmittal form should accompany each data tape. If a company sends more than one tape, a separate tape transmittal form should be prepared for each tape and should indicate the tape processing order.
Companies sending data via tape to SWBT should prepare and utilize the tape transmittal form as detailed on the following pages. If a LEC prepares their own tape transmittal form, it should contain all the data requirements as identified on the tape transmittal form found in these guidelines. SWBT utilizes IBM standards in the processing of tapes.
9. Compensation
Compensation will be paid to SWBT based on a charge per 92-99-01 summary usage record distributed to other companies (there is no charge for the records to be processed by SWBT's billing system). This charge will appear as an amount due on SWBT's monthly billing statement to the originating company.
14
SWBT-AR-121
ARKANSAS DATA DISTRIBUTION TAPE TRANSMITTAL FORM
To: Southwestern Bell Telephone ( 1) ATTN: AMA Unit Room 2242 9051 Park West Houston, TX 77063
From: Company Name: (2) Company Number: (3)
Contact Name: (4) Phone Number: (5)
Fax Number: (6)
TAPE LABEL INFORMATION
Tape Transmittal External Tape Label Internal Tape Label
DSN:
VOL SER:
Record Format:
Record Length:
Blocksize:
Total Packs:
(8)
(9 )
(1 1)
(12) Total Messages: (13)
FrodThru Dates: (14) Create DateiTime: (1 5 )
RETURN TAPES TO: Company Name: (16)
Attention: (17)
Address: (18)
City, State, Zip: (19)
RETURN REPORTS TO: Company Name: (20)
Attention: (21)
Address: (22)
City, State, Zip: (23)
15 SWBT-AR-I 22
ARKANSAS DATA DISTRIBUTION TAPE TRANSMITTAL FORM
TITLE
To:
Company Name:
Company Number:
Contact Name:
Phone Number:
Fax Number:
DESCRIPTION
Enter the name and address of the company receiving the transmittal. For tapes being sent to SWBT, this information has already been completed.
Enter the sending company name.
Enter the four-digit NECA company number of the sending company.
Enter the name of the person to be contacted at the sending company.
Enter the telephone number of the person to be contacted at the sending company.
TAPE LABEL INFORMATION
Enter the fax number of the person to be contacted at the sending company.
Dataset Name: Enter the Dataset Name (DSN) of the tape accompanying this transmittal. For tapes being sent to SWBT for data distribution, the dataset name should be MPSH.AG530.# # # # XXXX (Where # # # # equals the four letter company abbreviation and XXXX equals the four-digit NECA company number of the company sending the tape). The same DSN should appear on the tape transmittal form, on the External Tape Label and on the Internal Tape Label. Space has been provided on the form for each of the requirements in order to ensure that all three are identical.
Tape Vol. Ser.: Enter the Volume Serial Number (VOL. SER.) of the tape accompanying this transmittal. A standard label is required. The same VOL. SER. should appear on the tape transmittal form, the External Tape Label and on the Internal Tape Label. Space has been provided on the form for each of the requirements in order to ensure that all three are identical.
Record Format: Enter the Record Format of the tape. For tapes being sent to SWBT, the Record Format should be fixed.
SWBT-AR-123 16
ARKANSAS DATA DISTRIBUTION TAPE TRANSMITTAL FORM (Cont'd)
-- TITLE
(1 0) Record Length:
(1 1) Block Size:
(12) Total Packs:
( 13) Total Messages:
( 14) FrodThru Dates:
(1 5) Create Date/Time:
RETURN TAPE TO: ( 16) Company Name:
( 1 7) Attention:
( 18) Address:.
(19) City, State, Zip:
RETURN REPORT TO: (20) Company Name:
(2 1) Attention:
(22) Address:
(23) City, State, Zip:
DESCRIPTION
Enter the Record Length of the records contained on the tape. For tapes being sent to SWBT, the record length should be 2 10.
Enter the Block Size (?. block size of 2,100,2 1,000 or 32,760 may be used).
Enter the total number of packs contained on the tape accompanying this transmittal.
Enter the total number of messages contained on the tape. This number should reflect the total number of messages from all packs.
Enter the FrodThru Dates of the messages contained on the tape. The dates should reflect the earliest date and the most current date of the messages on the tape.
Enter the date and time this tape was created.
Enter the name of the company that this tape is to be returned to:
Enter the name of the person to whom this tape should be sent.
Enter the address of the company where the tapes should be sent.
Enter the city, state and zip code of the company where the tape should be sent.
Enter the number of the company receiving the reports.
Enter the name of the person who will be receiving the reports.
Enter the address of the company where the reports should be sent.
Enter the city, state and zip code of the company where the reports should be sent.
17
11/98 Page 1 of 3
CATEGORY 92 SUMMARY RECORD DATA DISTRIBUTION AGREEMENT
I.
I I .
I l l .
IV.
V.
Introduction
This Category 92 Summary Record Data Distribution Agreement (Agreement) is between Southwestern Bell Telephone Company (SWBT) and (Company), and sets forth the terms and conditions under which the Parties agree to provide intrastate intraLATA (Toll and Local) record flow assistance to each other for intercompany com pensation.
Definitions
CLEC: Competitive Local Exchange Carrier ILEC: Incumbent Local Exchange Carrier IXC: In terexchange Carrier
Data Distribution Service Provided bv SWBT
Under this Agreement SWBT will assist Company in the transmission of its 92-99-01 summary usage records to the appropriate ILECs and/or CLECs on the call path involved in transporting and/or terminating the underlying messages. Company will send the 92-99-01 summary usage records to be distributed by SWBT via a separate tape or data transmission from the records to be processed by SWBT's billing system. A separate "data pack" is required for each receiving company (the receiving company is identified based on the information contained in the "Receiving Company" field on the 92-99-01 summary usage records). SWBT will distribute the data packs containing the 92-99-01 summary usage records sent to it by Company based on the information contained in the data pack's Header Record. No records will be created for Company by SWBT as a part of this service. The only 92-99-01 summary usage records that qualify for inclusion in the Data Distribution process are for completed ILEC and/or CLEC transported intrastate intraLATA Toll and Local traffic that was carried over jointly provided ILEC and/or CLEC telecommunications facilities (Le., excluding IXC carried traffic).
Responsibilities of the Parties
A. SWBT shall provide the Data Distribution Service described above during the term of this Agreement.
B. Company shall conform with the Data Distribution Guidelines furnished by SWBT. Company will provide the monthly data to be distributed on a separate tape or data transmission. Company's tape or data transmission will contain data packs (each data pack containing a Header Record, the 92-99-01 summary usage records to be distributed, and a Trailer Record for each receiving company) to be distributed to the other ILECs and/or CLECs on the call path. Data that cannot be processed by SWBT will be rejected. It is the responsibility of Company to provide any necessary corrections and to resend the rejected data.
Compensation
Compensation will be paid to SWBT based on the rate of $.004 per 92-99-01 summary usage record distributed to other companies (there is no charge for the records to be processed by SWBT's billing system). SWBT will include amounts due under this Agreement on its monthly billing statements to Company. Remittance of amounts owed to SWBT is due within thirty (30) days from the billing statement date. Past due balances shall bear interest at the rate designated in SWBT's intrastate access service tariff.
SWBT-AR-125
11/98 Page 2 of 3
VI.
VII.
Vlll
IX.
The Data Distribution Service provided under this Agreement is provided to Company in the state of Arkansas beginning December 1, 1998. This service is provided on a month to month basis. The service provided under this Agreement may be changed, in whole or in part, upon sixty (60) days written notice by SWBT. Either Party may terminate this Agreement upon sixty (60) days written notice to the other Party.
Assignments
Neither Party may assign any right, obligation or duty, in whole or in part, or any other interest hereunder, without written consent from the other Party. This provision shall not excuse a Party from the obligation to pay for previously billed amounts which are still outstanding at the time of the assignment.
Limitation of Liability
By undertaking to provide Data Distribution Service for Company, SWBT assumes no liability for the receipt of revenues due from any other ILECs and/or CLECs. Company agrees that SWBT shall not be liable for damages (including but not limited to lost profits and exemplary damages) to Company, any ILEC, CLEC or other entity, as a result of any inaccurate or insufficient information resulting from any other person's actions, omissions, mistakes, or negligence, and upon which SWBT may rely in distributing data. Neither Party shall be liable to the other Party or any third party for any damages or for any losses, of any kind, resulting or arising from, in whole or in part, events or occurrences beyond the Party's control including but not limited to: inclement weather; strikes; work stoppages; power outages; war; andlor national emergency.
The Parties agree to indemnify and hold each other harmless against and with respect to any and all third party claims, demands, liabilities or court actions arising from any actions or omissions of the indemnifying Party relating to this Agreement. If both Parties' actions or omissions contributed to such claim, demand, liability or court action, indemnification shall be apportioned between the Parties according to their respective contributing responsibility.
Confidentiality
The Parties anticipate that they will exchange, or come into possession of, data about each other's customers and each other's business as a result of this Agreement. All Parties agree (a) to treat all such data as confidential; and (b) to use such data only for purposes of performance under this Agreement. The Parties further agree nat to disclose any such data with respect to the other Party's customers or business to any person, except those involved with or anticipated by the Data Distribution Service, without first securing the prior written consent of the other Party or Parties.
If a court or governmental agency which has jurisdiction over one of the Parties orders or requests a Party to disclose or to provide any data or information covered by this Agreement, that Party will immediately inform the affected Party of the order or request and will provide the affected Party with a reasonable opportunity to object to the order or obtain a protective order covering the confidential information to be disclosed. The Party ordered or requested to disclose such data will inform the affected Party both by telephone and overnight express delivery with receipt.
The provisions of this Section will remain in effect notwithstanding the termination of this Agreement, unless agreed to in writing by the Parties. The obligation to protect the confidentiality of proprietary information shall survive the termination of this Agreement. The obligation shall be binding on the respective successors and assigns of any Party. The Parties shall have the right to pursue any remedy available at law or in equity for breach of this confidentiality obligation.
SWBT-AR-126
11/98 Page 3 of 3
X. Acrreement Does Not Benefit Non-Parties
This Agreement is not intended, nor should this Agreement be construed, to benefit any third party. This Agreement does not enlarge, nor change in any way, any rights of any third party.
XI. Lawfulness and Severability
If a court or other governmental agency with proper jurisdiction issues a final order finding that a provision of this Agreement is unlawful, or that this Agreement, as a whole, is unlawful or may not be enforced, the Parties shall expeditiously and in good faith enter into negotiations to modify or terminate this Agreement.
XII. Defaults or Violations
If any Party defaults in the payment of any amounts due or violates any other provision of this Agreement, and if such default or violation shall continue for thirty (30) days after written notice thereof, the defaulted Party may then and at any time thereafter terminate this Agreement effective immediately upon giving written notice.
XIII. Notice
All notices required by, permitted by or relating to this Agreement shall be in writing and sent to the Party's representative. Representatives of the Parties for purposes of notice are shown below. Any Party may change its representative by giving written notice in accordance with this Section of the Agreement.
ComDany
Name: Name:
Address: Address:
Phone: Phone:
XIV. Execution
The undersigned signatories represent that they have the authority to execute this Agreement on behalf of their respective companies.
This Agreement is executed this day of , 1998.
By: By: for Southwestern Bell Telephone Company for
(Name) (Name)
(Title) (Title)
TEXAS DATA
DISTRIBUTION GUIDELINES
FOR CATEGORY 92 SUMMARY RECORDS
Southwestern Bell Telephone Company Carrier Compensation/Billing District
January 1999
SWBT-AR-128
DATA DISTRIBUTION GUIDELINES
1.
2.
3.
4.
5 .
6 .
7 .
8.
9.
Table of Contents
Introduction
Definitions
Data Distribution Service Description
Data Exchange Timeline
Header and Trailer Records
Data Exchange Media Options
Dataset Naming Conventions
Data Tape Transmittal
Compensation
I SWBT-AR-129
DATA DISTRIBUTION GUIDELINES
1. Introduction
This document has been prepared to provide the guidelines supporting SWBT's Category 92 Summary Record Data Distribution Process in the state of Texas. The references to data set names, monthly processing schedules and company codes are Texas specific and may not be appropriate for use in any other state.
The Category 92 record process utilizes originating end user recordings. It is the responsibility of the originating company to create the appropriate Category 92 records and provide them to all the other Primary Carrier ILECs and/or CLECs on the call path.
2. Definitions
CLEC: Competitive Local Exchange Carrier ILEC: Incumbent Local Exchange Carrier IXC: Interexchange Camer LEC: SWBT: Southwestern Bell Telephone Company
Local Exchange Carrier (generic term for ILEC and/or CLEC)
SWBT-AR-130
I DATA DISTRIBUTION GUIDELINES
3. Data Distribution Service Description
Under this service SWBT will assist other companies in the transmission of their origmating 92-99-01 summary usage records to the appropriate Primary Carrier ILECs and/or CLECs on the call path involved in transporting and/or terminating the underlying messages. The companies will send the 92-99-01 summary usage records to be distributed by SWBT via a separate tape or data transmission from the records to be processed by SWBT's billing system. A separate "data pack" is required for each receiving company (the receiving company is identified based on the information contained in the "Receiving Company" field on the 92-99-0 1 summary usage records). SWBT will distribute the data packs containing the 92-99-01 summary usage records sent to it by the other companies based on the information contained in the data packk Header Record. No records will be created for the other companies by SWBT as a part of this service. The only 92-99-0 1 summary usage records that qualify for inclusion in the Data Distribution process are for completed ILEC and/or CLEC transported intrastate intraLATA Toll and Local traffic that was camed over jointly provided ILEC and/or CLEC telecommunications facilities (i.e., excluding IXC camed traffic).
4. Data Exchange Timeline
Monthly Schedule
8'h Work Day - Data Packs to be distributed are received by SWBT.
12'h Work Day - Data Packs received by other companies from SWBT.
Data Packs received after the Sth work day will be processed in the following data month. Data Packs that do not conform with these guidelines and/or cannot be processed by SWBT will be rejected. It is the responsibility of the sending company to provide any necessary corrections and resend the rejected data.
3
SWBT-AR-131
DATA DISTRIBUTION GUIDELINES
5. Header and Trailer Records
Introduction to 20-XX-XX Header and Trailer Records
When mechanized data is transmitted between Parties, standard EMR Pack Header and Trailer conventions are used as well as unique compensation plan Pack Header and Trailer records. The compensation plan Header and Trailer records are identified as 20-90-XX and 20-9 1 -XX and are defined in this section. For transmission purposes, Category 92 records must be packed separately from other EMR records.
There are two types of standard Bell - Non-Bell Exchange Carrier Pack Header and Trailer record formats:
Full RAO records 20-20-xx Non-Full RAO records 20-2 1 -XX
For Category 92 records, substitute 90 (Full RAO) or 91 (Non-Full RAO) for the record group in the standard EMR Bell - Non-Bell Exchange Carrier Pack Header and Trailer records formats:
Header Trailer Full Rao 20-90-0 1 20-90-02 Non-Full RAO 20-9 1-0 1 20-9 1-02
All Companies should total the number of Category 92 summary records (92-99-01) contained in each pack. This total is reflected in the Grand Total Record Count field on the Trailer record (20-90-02 fields 1 1 1 - 1 17 or 20-9 1-02 fields 95- 101).
Examples of the 20-90-XX and 20-9 1 -XX record layouts are provided on the following pages.
4
DATA DISTRIBUTION GUIDELINES
Instructions for Creating Full Status RAO Header Records (20-90-01)
FROM TO LENGTH
1
7
13
15
17
20
23
26
40
44
6 6
12 6
14 2
16 2
19 3
22 3
25 3
39 14
43 4
210 167
TYPE VALUE
N
N
N
N
N
N
N
N
N
N
20900 1
YYMMDD
0 1-99
33
0 Filled
0 Filled
SOURCE
Table 30
Table 30
Table 30
DESCRIPTION
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
Originating Company’s RAO
Receiving Company’s RAO
Billing Company’s RAO
Not Used
Originating Company’s four-digit NECA Company Number
Not Used
N = Numeric
All the information in Fields 7-25 must match the information contained in the associated Trailer Record
5
Field Description l P Y l , c
- 12 Day
14 lnvolce Number
16 Company Number
13
15
17
- -
- - 18 From RAO
Record Identification
Date 10 Month Created 11
I
Sent to RAO ~!
I
Reserved 9
El i Field Characteristic: 4 = Numeric X = I
Full RAO Pack Header Record
90 - I
Field Description I
Reserved
I$ 106
Grand Total
Revenues
~~
Status Code '
127 128 129 -
Reserved
hanumeric
6
01 I
- Field Description I
i SWBT-AR-134
! a
DATA DISTRIBUTION GUIDELINES ,
Instructions for Creating Full Status RAO Trailer Records (20-90-02)
FROM TO LENGTH TYPE VALUE SOURCE DESCRIPTION
1
7
13
15
17
20
23
26
111
6
12
14
16
19
22
25
110
117
6
6
2
2
3
3
3
85
7
N 209002
N YYMMDD
N 0 1 -99
N 33
N Table 30
N Table 30
N
N 0 Filled
N
118 210 93 N 0 Filled
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
Originating Company’s RAO
Receiving Company’s RAO
Billing Company’s RAO
Not Used
Grand Total Record Count (Total number of 92-99 summary records contained in this pack - this is a right justified field)
Not Used
N = Numeric
All the information in Fields 7-25 must match the information contained in the associated Header Record
7
SWBT-AR-I 35
Full RAO Pack Trailer Record
90 -
Reserved
I
Grand t Total
Revenues
110 Cent
Grand Total
Record Count
Created Mlnute
Reserved
..
hanumenc
8
20 -
invoice Number
Com an Number 17 .. - 10 From RAO
4 9 20 - 21 Sent to RAO
22 23 - 24 Billing RAO
26 26 27 28 29 30 31
-
-
- - - -
46
~
57 Reserved
66 E L Field 67 Characteristic: 9 Numcnc
:hrr 1 02 -
I Field Description L-
Reserved
SWBT-AR-136
9
I DATA DISTRIBUTION GUIDELINES
Instructions for Creating Non-Full Status RAO Header Records (20-91-01)
FROM TO LENGTH TYPE VALUE SOURCE DESCRIPTION
1 6 6 N 209101 Record Identification
7 12 6 N YYMMDD Date Created
13 14 2 N 0 1-99
15 16 2 N . 33
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
17 19 3 N 149 SWBT RAO
20 23 4 N
24 27 4 N
28 33 6 N
Four-digit number of the LEC or Service Bureau sending the data
Four-digit number of the Responsible LEC
NPANXX of the Company to which the data should be sent
Table 30
Table 80
34 210 177 N 0 Filled Not Used
N = Numeric
All the information in Fields 7-33 must match the information contained in the associated Trailer Record
9
SWBT-AR-137
Field Description 6 Field Description Pos Char 66 67 - -
Non- Billable 68 s 69 Revenue 9 - -
70
Record E Identiflcatlon
I
138 I Directional lndlcator 139 I
I I I
9 1 Date
Created
- - s Foreign 91 92 State 9 93 Tax 94 c8nt 95 96 Grand count 97 Total of 9
98 Record Good - Cwnt Records
- - -
99 100 101 102 103 -
9
- 104 106 t . Grand 106 Total 9 - 107 Revunes
- - -
108 109 110 111 Cent 112 113 Count Total 114 O f A- 9 115 Error overnow
T F Records Records rn
- - - - -
Day I
- 50 Number
- 52 Messages - 51 Recelved Collect 9
53 54 55 - -
ReceiWd 56 t 57 Collect 9 58 Revenue 59 60 Cent
- -
-
itlfication Number I
I
- 119 120 121
interfacing Bell 9 RAO Code
20 i
Percent Error 9
ILEC or Service Bureau
ILEC identification Code
-.
t 28 I I I 1
Billing Company
NNX
Reserved
Numbef of Rated Sent Paid Messages
I I
Sent Paid Revenue ..., 9
Number of Non-BMa bi t
Records I g ~~
9 = Numeric
Non-Full RAO Pack Header Record
a4
I I
118 I I
I
Count of NonAppkable
Records 9
f77 I I I
Sample &ti0
( = Alphanumeric 1
10
01
Field Description
- 1 I
Char / I i 1
137
Total Minutes
Total Universal Volumes
9
I Overnow
Count 144
Reserved
E 164 Reserved
SWBT-AR-738
9
I DATA DISTRIBUTION GUIDELINES I Instructions for Creating Non-Full Status RAO Trailer Records (20-91-02)
FROM TO
1
7
13
15
17
20
24
28
34
95
102
6
12
14
16
19
23
27
33
94
101
210
LENGTH
6
6
2
7 .-
3
4
4
6
61
7
109
TYPE
N
N
N
N
N
N
N
N
N
N
N
VALUE SOURCE
209 102
YYMMDD
0 1-99
33
149
Table 30
Table 80
0 Filled
0 Filled
DESCRIPTION
Record Identification
Date Created
Invoice Number (Assigned by the sending company or vendor)
SWBT Company ID Number
SWBT RAO
Four-digit number of the LEC or Service Bureau sending the data
Four-digit number of the Responsible LEC
NPANXX of the Company to which the data should be sent
Not Used
Grand Total Record Count (Total number of 92-99 summary records contained in this pack - this is a right justified field)
Not Used
N = Numeric
All the information in Fields 7-33 must match the information contained in the associated Header Record
1 1
SWBT-AR-I 39
- 20
Field Description
Pot Chi 1 1 i i
/61 RecordType 1 7 1 I
Date Month Created
I 1 ' 12 Day 1 13 1
Invoice Number Bell Company
16 identification Number *7
Interlacing Bell RAO Code
28 I
ILEC or Servke Bureau
ILEC Identlilcatlon Code
28 29 NPA 30 Bllllng - 31 Company
32 NNX 33 34 35 Resewed 36 37 Number of Rated - 38 Sent Paid Messages
39
- -
-
- - - - I 41 I I
w Sent Paid Revenue
..
1 47 I
Number Recelved Collect
Messages
1 f 1 Received 57 Callect - . - - .. - - - 58 Revenue 59 60 Cent 61 62 - Number of
63 Non-Billa ble 64 Records
-
- -
65 he1 Characteristic: 9 = Numerit
Non-Full RAO Pack Trailer Record
91 - Field Description
I Pas
Non- Blilable Revenue
Cent
Number of Returned Messages
Returned Message Revenue
83 1841 Cent I I 86 I
Number of Unrated Messages
Cwnt
Error Records
1 I1 118 i
Foreign State Tax
count of
Good Records
Grand Total
Revunes
Total Access
overnow Records
Percent Error
Count of Nondppilcable
Records
26 _.
Sample Ratio
= p anumenc 12
C h
Field Description 1 Pot
130
144 B 146
Total Total Mlnutes Universal
Volumes
L Directional Indicator
Total Access
Overnow Count
SWBT-AR-140
I
Char1
1
DATA DISTRIBUTION GUIDELINES
6. Data Exchange Media Options
The following media options are available for the transmission of data:
Electronic NDM TCP/IP
Tape 18 Track
7. Dataset Naming Conventions
The dataset should be named in such a way as to identify the originating Party. The following are the recommended naming conventions:
Electronic MPST.AG5301 lA.INDCO.# # # # XXXX
Tape MPST.AG530.# # # # XXXX
Where # # # # = Company Name Abbreviation (Alpha) Where XXXX = Four-Digit NECA Company Number (Numeric)
Each transmitting company should coordinate with the receiving company to define the transmission specifics of the data file.
13 S W BT-AR- 1 4 1
DATA DISTRIBUTION GUIDELINES
8. Data Tape Transmittal
A tape transmittal form should accompany each data tape. If a company sends more than one tape, a separate tape transmittal form should be prepared for each tape and should indicate the tape processing order.
Companies sending data via tape to SWBT should prepare and utilize the tape transmittal form as detailed on the following pages. If a LEC prepares their own tape transmittal form, it should contain all the data requirements as identified on the tape transmittal form found in these guidelines. SWBT utilizes IBM standards in the processing of tapes.
9. Compensation
Compensation will be paid to SWBT based on a charge per 92-99-01 summary usage record distributed to other companies (there is no charge for the records to be processed by SWBT's billing system). This charge will appear as an amount due on SWBT's monthly billing statement to the originating company.
14
SWBT-AR-I 42
TEXAS DATA DISTRIBUTION TAPE TRANSMITTAL FORM
To: Southwestern Bell Telephone ( 1 ) ATTN: Ah4A Unit Room 2242 9051 Park West Houston, TX 77063
From: Company Name: (3) - Company Number: (3)
Contact Name: (4) Phone Number: (5)
Fax Number: (6)
TAPE LAE3EL INFORMATION
Tape Transmittal External Tape Label Internal Tape Label
DSN: ( 7 )
VOL SER: (8)
Record Format: (9)
Record Length: (10)
Blocksize: (11 )
Total Packs: (12) Total Messages: (13)
F r o f l h r u Dates: (14) Create DateiTime: ( 15)
RETURN TAPES TO: Company Name: (16)
Attention: (17)
Address: (18)
City, State, Zip: (19)
RETURN REPORTS TO: Company Name: (20)
Attention: (21)
Address: ( 2 2 )
City, State, Zip: (23)
15 s 7 - 4 - 7 43
TEXAS DATA DISTRIBUTION TAPE TR4NSMITTAL FORM
--- TITLE
To :
Company Name:
Company Number:
Contact Name:
Phone Number:
Fax Number:
DESCRIPTION
Enter the name and address of the company receiving the transmittal. For tapes being sent to SWBT, this information has already been completed.
Enter the sending company name.
Enter the four-digit NECA company number of the sending company.
Enter the name of the person to be contacted at the sending company.
Enter the telephone number of the person to be contacted at the sending company.
TAPE LABEL INFORMATION
Enter the fax number of the person to be contacted at the sending company.
Dataset Name: Enter the Dataset Name (DSN) of the tape accompanying this transmittal. For tapes being sent to SWBT for data distribution, the dataset name should be MPST.AG530.# # # # XXXX (Where ## ## # # equals the four letter company abbreviation and XXXX equals the four-digit NECA company number of the company sending the tape). The same DSN should appear on the tape transmittal form, on the External Tape Label and on the Internal Tape Label. Space has been provided on the form for each of the requirements in order to ensure that all three are identical.
Tape Vol. Ser.: Enter the Volume Serial Number (VOL. SER.) of the tape accompanying this transmittal. A standard label is required. The same VOL. SER. should appear on the tape transmittal form, the External Tape Label and on the Internal Tape Label. Space has been provided on the form for each of the requirements in order to ensure that all three are identical.
Record Format: Enter the Record Format of the tape. For tapes being sent to SWBT, the Record Format should be fixed.
SWBT-AR-144 16
TEXAS DATA DISTRIBUTION TAPE TRANSMITTAL FORM (Cont'd)
TITLE
(1 0) Record Length:
(1 1) Block Size:
(12) Total Packs:
(1 3) Total Messages:
(14) FrodThru Dates:
( 15) Create Date/Time:
RETURN TAPE TO: ( 16) Company Name:
(1 7) Attention:
(1 8) Address:
(1 9) City, State, Zip:
RETURN REPORT TO: (20) Company Name:
(2 1) Attention:
(22) Address:
(23) City, State, Zip:
DESCRIPTION
Enter the Record Length of the records contained on the tape. For tapes being sent to SWBT, the record length should be 2 10.
Enter the Block Size (a block size of 2,100,2 1,000 or 32,760 may be used).
Enter the total number of packs contained on the tape accompanying this transmittal.
Enter the total number of messages contained on the tape. This number should reflect the total number of messages from all packs.
Enter the FrodThru Dates of the messages contained on the tape. The dates should reflect the earliest date and the most current date of the messages on the tape.
Enter the date and time this tape was created.
Enter the name of the company that this tape is to be returned to:
Enter the name of the person to whom this tape should be sent.
Enter the address of the company where the tapes should be sent.
Enter the city, state and zip code of the company where the tape should be sent.
Enter the number of the company receiving the reports.
Enter the name of the person who will be receiving the reports.
Enter the address of the company where the reports should be sent.
Enter the city, state and zip code of the company where the reports should be sent.
S W BT -AR-145
17
11/98 Page 1 of 3
CATEGORY 92 SUMMARY RECORD DATA DISTRIBUTION AGREEMENT
I. Introduction
This Category 92 Summary Record Data Distribution Agreement (Agreement) is between Southwestern Bell Telephone Company (SWBT) and (Company), and sets forth the terms and conditions under which the Parties agree to provide intrastate intraLATA (Toll and Local) record flow assistance to each other for intercompany com pensation.
11. Definitions
CLEC: Competitive Local Exchange Carrier ILEC: Incumbent Local Exchange Carrier IXC: lnterexchange Carrier
Ill. Data Distribution Service Provided bv SWBT
Under this Agreement SWBT will assist Company in the transmission of its 92-99-01 summary usage records to the appropriate ILECs and/or CLECs on the call path involved in transporting and/or terminating the underlying messages. Company will send the 92-99-01 summary usage records to be distributed by SWBT via a separate tape or data transmission from the records to be processed by SWBT’s billing system. A separate “data pack” is required for each receiving company (the receiving company is identified based on the information contained in the ”Receiving Company” field on the 92-99-01 summary usage records). SWBT will distribute the data packs containing the 92-99-01 summary usage records sent to it by Company based on the information contained in the data pack’s Header Record. No records will be created for Company by SWBT as a part of this service. The only 92-99-01 summary usage records that qualify for inclusion in the Data Distribution process are for completed ILEC and/or CLEC transported intrastate intraLATA Toll and Local traffic that was carried over jointly provided ILEC and/or CLEC telecommunications facilities (i.e., excluding IXC carried traffic).
IV. Responsibilities of the Parties
A. SWBT shall provide the Data Distribution Service described above during the term of this Agreement.
B. Company shall conform with the Data Distribution Guidelines furnished by SWBT. Company will provide the monthly data to be distributed on a separate tape or data transmission. Company’s tape or data transmission will contain data packs (each data pack containing a Header Record, the 92-99-01 summary usage records to be distributed, and a Trailer Record for each receiving company) to be distributed to the other ILECs and/or CLECs on the call path. Data that cannot be processed by SWBT will be rejected. It is the responsibility of Company to provide any necessary corrections and to resend the rejected data.
V. Compensation
Compensation will be paid to SWBT based on the rate of $.004 per 92-99-01 summary usage record distributed to other companies (there is no charge for the records to be processed by SWBT’s billing system). SWBT will include amounts due under this Agreement on its monthly billing statements to Company. Remittance of amounts owed to SWBT is due within thirty (30) days from the billing statement date. Past due balances shall bear interest at the rate designated in SWBT’s intrastate access service tariff.
SWBT-AR-146
VI.
VII.
Vlll
IX.
11/98 Page 2 of 3
The Data Distr-ibution Service provided under this Agreement is provided to Company in the state of Texas beginning February 1, 1999. This service is provided on a month to month basis. The service provided under this Agreement may be changed, in whole or in part, upon sixty (60) days written notice by SWBT. Either Party may terminate this Agreement upon sixty (60) days written notice to the other Party.
Assiclnments
Neither Party may assign any right, obligation or duty, in whole or in part, or any other interest hereunder, without written consent from the other Party. This provision shall not excuse a Party from the obligation to pay for previously billed amounts which are still outstanding at the time of the assignment.
Limitation of Liability
By undertaking to provide Data Distribution Service for Company, SWBT assumes no liability for the receipt of revenues due from any other ILECs and/or CLECs. Company agrees that SWBT shall not be liable for damages (including but not limited to lost profits and exemplary damages) to Company, any ILEC, CLEC or other entity, as a result of any inaccurate or insufficient information resulting from any other person's actions, omissions, mistakes, or negligence, and upon which SWBT may rely in distributing data. Neither Party shall be liable to the other Party or any third party for any damages or for any losses, of any kind, resulting or arising from, in whole or in part, events or occurrences beyond the Party's control including but not limited to: inclement weather; strikes; work stoppages; power outages; war; and/or national emergency.
The Parties agree to indemnify and hold each other harmless against and with respect to any and all third party claims, demands, liabilities or court actions arising from any actions or omissions of the indemnifying Party relating to this Agreement. If both Parties' actions or omissions contributed to such claim, demand, liability or court action, indemnification shall be apportioned between the Parties according to their respective contributing responsibility.
Confidentiality
The Parties anticipate that they will exchange, or come into possession of, data about each other's customers and each other's business as a result of this Agreement. All Parties agree (a) to treat all such data as confidential; and (b) to use such data only for purposes of performance under this Agreement. The Parties further agree not to disclose any such data with respect to the other Party's customers or business to any person, except those involved with or anticipated by the Data Distribution Service, without first securing the prior written consent of the other Party or Parties.
If a court or governmental agency which has jurisdiction over one of the Parties orders or requests a Party to disclose or to provide any data or information covered by this Agreement, that Party will immediately inform the affected Party of the order or request and will provide the affected Party with a reasonable opportunity to object to the order or obtain a protective order covering the confidential information to be disclosed. The Party ordered or requested to disclose such data will inform the affected Party both by telephone and overnight express delivery with receipt.
The provisions of this Section will remain in effect notwithstanding the termination of this Agreement, unless agreed to in writing by the Parties. The obligation to protect the confidentiality of proprietary information shall survive the termination of this Agreement. The obligation shall be binding on the respective successors and assigns of any Party. The Parties shall have the right to pursue any remedy available at law or in equity for breach of this confidentiality obligation.
SWBT-AR-147
11/98 Page 3 of 3
X.
XI.
XII.
XIII.
Agreement Does Not Benefit Non-Parties
This Agreement is not intended, nor should this Agreement be construed, to benefit any third party. This Agreement does not enlarge, nor change in any way, any rights of any third party.
Lawfulness and Severability
If a court or other governmental agency with proper jurisdiction issues a final order finding that a provision of this Agreement is unlawful, or that this Agreement, as a whole, is unlawful or may not be enforced, the Parties shall expeditiously and in good faith enter into negotiations to modify or terminate this Agreement.
Defaults or Violations
If any Party defaults in the payment of any amounts due or violates any other provision of this Agreement, and if such default or violation shall continue for thirty (30) days after written notice thereof, the defaulted Party may then and at any time thereafter terminate this Agreement effective immediately upon giving written notice.
Notice
All notices required by, permitted by or relating to this Agreement shall be in writing and sent to the Party's representative. Representatives of the Parties for purposes of notice are shown below. Any Party may change its representative by giving written notice in accordance with this Section of the Agreement.
SWBT ComDany
Name: Name:
Address: Address:
Phone: Phone:
XIV. Execution
The undersigned signatories represent that they have the authority to execute this Agreement on behalf of their respective companies.
This Agreement is executed this day of , 1999
By: By: for Southwestern Bell Telephone Company for
(Name) (Name)
(Title) (Title)
SWBT-AR-148
I From: WALLACE, MARY JO (SWBT) Sent:
Subject: RE: e.spire
Friday, January 21,2000 3:18 PM FELAN, MARTHA J(MARlY) (SWBT)
MaW, Sony for the delay. The attached file should help. Give me a call if you would like to discuss what I have written. Thanks, mj
---Original Message-
Friday, January 21,2000 252 PM WALLACE, MARY JO (SWBT) I STOukject: espire
Please send me the info that I need to send to e.spire so that 1 can get them squared away for next week.
Thanks,
Many Felan Account Manager - LPAT (214) 464-4373
SW BT-AR-? 49
e.spire / SWBT Conference Call January 13,2000
SWBT identdied and explained that there are certain types of traffic whch is not part of the compensation process and therefore no Category 92 records axe exchanged. Examples of excluded traffic types are non-SWBT origmated calls, cellular, Directory assistance, conference calling and UNE-P customer originated traffic. Types of calls that are subject to compensation and which are identified in the Data Exchange Binder are LEC carried intralata MTS, OUTWATS, LEC carried originating 800 intralata traf6c and certain local calls. The settlement and data exchange process can be found in the T.E.S.P. and Data Exchange Binders. It was requested that SWBT furnish to e.spire a list of the call types included. SWBT requested that e.spire provide additional background information on the call types included in the analysis of the billing issues. Thls request was agreed to by e-spire.
Based upon concerns expressed by e.spire, SWBT indicated that they were reviewing the category 92 records being sent to e-spire. e.spire inquired whether or not a l l end offices were accurately reporting. SWBT advised that as a pro-active measure, a review was in progress but could not commit to a completion date. E.spire requested that the results of this review be shared. E.spire stated that they would be submitting comments regarding SBC's 271 filing on Jan. 31 and would include a discussion of these topics. E.spire requested an explanation of the methodology of i d e n m g ISP traffic. SWBT referred to SWBT's f i g s with the Texas PUC and the FCC but briefly explained the process of identrrfvlng possible ISP numbers as those numbers generating 200 calls and/or 60 minutes/call per month. An attempt is then made to validate these numbers as potential ISP numbers.
Request to identify call types included in the compensation process
Call types included in the compensation process can be found in the Data Exchange Binder, Tab 5, page 3. They are:
01-01-01 MTS 1- 1-3 1 OUTWATS (Non-SMDR)
0 1-0 1-25 Originating 800 (SSP) 1-1-31 Local Service
1- 1-32 OUTWATS (SMDR)
Category 92 detail records are copies of these intraLATA LEC carried completed calls. These detail records are summarized on a monthly basis by date, originating/terminating NPA/NXX, and tr&c type. This information is also found in the Data Exchange Binder, Tab 5 , page 8.
Originating vs terminating records
The comparison of origmating to terminating records will most often lend itself to a disparity in the matching of all records. This disparity can be attributed to several situations.
0 UNE-P providers sharing SWBT numbers - When the terminating recording is made, the end office making the recording is unable to determine the owner of the originating number. (SWBT vs UNE-P)
Local Number Portability (LNP) - Because customers are allowed to port numbers within a rate center, the terminating end office may not be able to determine ownership of the number.
Calls utilizing MF' Signaling - When an originating call is made utilizing MF signaling the originating number may be lost by the time the terminating recording is made. IntraLATA LEC carried toll calls originated by a third party may be inadvertently included in the terminating recordings.
Miscellaneous Traffic - The terminating recordings may also include cellular tr&c, traf6c not subject to compensation (tragic other than MTS, OUTWATS, 800 or local), and non-SWBT originated traffic
Certamly ths list should not be considered complete, but it does begin to identdy other usage that may be captured in the terminatkg recordings.
SWBT-AR-151
I.
11.
111.
IV.
V.
VI.
VI1 .
VIII.
IX.
X.
XI.
XI1 .
XIII.
XIV.
xv. XVI.
XVII .
XVIII .
MX.
xx. XXI.
XXII .
XXIII.
XXIV
xxv.
TABLE OF CONTENTS
INTERCONNECTION AGREEMENT BETWEEN
SOUTHWESTERN BELL TELEPHONE COMPANY AND
CONNECT COMMUNICATIONS CORPORATION
DEFINITIONS ............................................................... ............. 1
NETWORK INTERCONNECITON ARCHITECTURE ........................... 1
COMPENSATION FOR D
NUMBERING.. .............................................................
APPENDICES .........................................................................
ADDITIONAL SERVICES ............................... 9
POLES, DUCTS, CONDUITS & RIGHT-OF-WAY ................................ 12
UNBUNDLED ARRANGEMENTS ........................................................ 12
LOCAL NUMBER PORTABILITY.. ...................................................... 12
RESALE ........................................................................
LEASED SPACE ........................................................................
ADDITIONAL RESPONSIBILITY OF THE PARTIES .......
OTHER OBLIGATIONS OF LSP ..............
NETWORK MAINTENANCE & MANAGEMENT.. ............................. 15
FORCE MAJEURE ................ 16
INDEMNIFICATION & LIMITATION OF LIABILITY .............. 17
LIQUIDATED DAMAGES FOR SPECIFIED ACTIVITIES 19
NONDISCLOSURE.. ............................................................................ . 2 1
PUBLICITY .......................................................................................... .22
ASSIGNMENT ....................................................................................... 22
DISPUTE RESOLUTION ..................................................................... .23
VERIFICATION REVIEWS ................................................................. .25
COMPLIANCE WITH LAWS .............................................................. .25
EFFECT OF OTHER AGREEMENTS . .
CERTIFICATION REQUIREMENTS ............
SWBT-AR-152
XXVI. NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27
XXVII. THIRD PARTY BENEFICIARIES.. ..................................................... .27
XXVIII. TAXES.. .............. ....................................................... . 28
XXIX. TERM.. ..................................................................... ........... .28
XXX. WAIVER ............................ .......................................... 28
XXXI. DISCLAIMER OF WARRANTIES ............................
XXXII. EFFECTIVE DATEAMPLEMENTATION ........
XXXIII.
XXXIV. COMPLETE TERMS ......................................
RELATIONSHIP OF THE PARTIES ...............................
SWBT-AR-I 53
AGREEMENT
This Agreement is between Connect Communications Corporation, (“CONNECT”), on the one hand, and Southwestern Bell Telephone Company (“SWBT”), on the other hand, (with CONNECT and SWBT collectively referred to as, “the Parties”) entered into this day of , 1997.
WHEREAS, the Parties wish to establish terms for interconnection for purposes of exchanging local, intraLATA interexchange and interLATA interexchange traffic pursuant to the Telecommunications Act of 1996 (the “Act”); and
WHEREAS, CONNECT desires to provide local exchange service to residential and business end users and to wholesale customers through use of its own telephone exchange service facilities in combination with unbundled network elements, facilities and services of SWBT in the state of Arkansas.
THEREFORE, the Parties hereby agree as follows:
I. DEFINITIONS
Definitions of the terms used in this Agreement are listed in Appendix DEFINE, attached hereto and incorporated by reference.
I1 NETWORK INTERCONNECTION ARCHITECTURE
The Parties shall provide for interoperation of their networks as stated below:
A. Parties shall interconnect their facilities as follows:
1. CONNECT shall interconnect with SWBT’s facilities as follows:
a. In each SWBT exchange area in which CONNECT chooses to offer local exchange service, CONNECT, at a minimum, will interconnect its network facilities to (a) each SWBT access tandem(s), and (b) to either each SWBT local tandem(s) or each SWBT end office(s) subtending that local tandem(s). SWBT End Offices (“EO’) and tandems through which CONNECT will terminate its traffic will be called Designated Connecting Offices (“DCOs”) and are identified in Appendix DCO attached hereto and incorporated herein by reference. Subsequent changes in DCO designations consistent with the requirements of this provision (e.g., changes from local tandem to end offices subtending the local tandem) can be accomplished through mutual agreement of the Parties, which agreement shall not
SWBT-AR-154
be unreasonably withheld. As CONNECT initiates exchange service operations in additional SWBT exchange areas, S W T and CONNECT shall agree upon additional DCOs in each new exchange area. CONNECT agrees that if SWBT establishes additional tandems in an exchange area within which CONNECT offers local exchange service, CONNECT will interconnect to the additional tandems.
b. Interconnection to a SWBT local tandem(s) will provide CONNECT local access to the SWBT end offices and NXX’s which subtend that tandem(s), and to other LSPs and LECs [subject to Section XI1 (Other Obligations of the LSP] which are connected to that tandem(s). Interconnection to a SWBT end office(s) will provide CONNECT access only to the NXX’s served by that individual end office(s) to which CONNECT interconnects.
c. Interconnection to a S W T access tandem will provide CONNECT interexchange access to S W T , Interexchange Carriers (IXCs), LECs and CMRS providers [subject to Section XI1 (Other Obligations of CONNECT)] which are connected to that tandem. Where an access tandem also provides local tandem functions, interconnection to a S W T access tandem serving that exchange will also provide CONNECT access to SWBT’s end offices with the same hnctionality described in (b) above.
d. Where CONNECT requires ancillary services (e.g., Directory Assistance, Operator Assistance, 91 1Ell) additional DCOs or special trunking will be required for interconnection to such ancillary services.
2. SWBT shall interconnect with CONNECT’S facilities under terms and conditions no less favorable than those identified in Section A, Paragraph 1, above, at points designated in Appendix DCO as follows:
B. Where the Parties interconnect, for the purpose of exchanging traffic between networks, the Parties will use the following interconnection method for each tandem and EO identified in Appendix DCO. Technical parameters, descriptions and charges for that method is defined or referenced, as appropriate, in Appendix NIM (Network Interconnection Methods), which is attached hereto and made a part hereof.
2
1 . For the LSP’s local exchange areas, CONNECT and SWBT agree to provide facilities and trunks from their respective ofices to the NIP, as outlined in Appendix DCO, subject to the terms and conditions of the NIM and ITR Appendices. This arrangement will provide for connection between the appropriate SWBT tandems and CONNECT facilities for the purpose of terminating CONNECT local, intraLATA, 911, Operator Services, and meet point billed interLATA trunks. These interconnection facilities will be utilized for SWBT trunks terminating to the CONNECT switch, and for trunks terminating to the SWBT tandems.
2. SWBT will provide to CONNECT at CONNECT’ request, virtual collocation at the same rates, terms, and conditions as FCC 73, Section 25.
3 . SWBT will provide to CONNECT, at CONNECT’ request, physical collocation under the same terms and conditions available to similarly situated carriers at the time of such request.
4. SWBT will provide to CONNECT, at CONNECT’ request, SONET Based Interconnection (“SBI”) whereby CONNECT would provide fiber cable to SWBT for connection to SWBT- designated basic transmission equipment located in the DCO at the DCO and dedicated solely for CONNECT’ use. SWBT would own and maintain the basic transmission equipment. For ease of drafting, this option shall be offered under terms and conditions which are consistent with SWBT’s SBI tariff.
5 . Other interconnection methods as may be negotiated.
C. In addition, the Parties agree to follow the interconnection and trunking requirements listed in Appendix ITR, which is attached hereto and made a part hereof.
D. The Parties shall identifl the V&H coordinates for each NIP. Appendix DCO which identifies the specific interconnection points agreed upon by the Parties is attached hereto and incorporated herein by reference.
E. To the extent a Party provides only one switching facility in an exchange, such facility shall be treated as an end office for compensation purposes.
3 SWBT - AR -1 55A
COMPENSATION FOR DELIVERY TRAFFIC
For purposes of compensation under this Agreement, the telecommunications traffic traded between the Parties shall be classified as either Local traffic, Through-put traffic, IntraLATA Interexchange traffic, or InterLATA Interexchange. The Parties agree that, notwithstanding the classification of traffic under this Agreement, either Party is free to define its own “local” calling scope(s) for purposes of its provision of telecommunications service to its end users.
Calls originated by one Party’s end users and terminated to the other Party’s end users shall be classified as local traffic under this Agreement if the call originates and terminates in the same SWBT exchange area (for illustrative purposes as defined and described in SWBT tariffs), or originates and terminates within different SWBT exchanges which share a common mandatory local calling scope. Calls not classified as local under this Agreement shall be treated as interexchange for intercompany compensation purposes.
Intercompany compensation for Feature Group A traffic is described in Appendix FGA, which is attached hereto and incorporated herein by reference.
The Parties agree that they shall include the originating calling number in the information they transmit with each call being terminated on the other’s network, so that correct jurisdiction of the call can be made under this section for the purpose of intercompany compensation. The type of originating calling number transmitted is dependent upon the protocol of the trunk signaling utilized for interconnection. Traditional toll protocol is used with Multi-frequency (MF) signaling and Automatic Number Identification (ANI) is sent from the end office switch towards the tandem switch. Signaling System Seven (SS7) protocol utilizes Calling Party Number (CPN) to identi@ the originating calling number. The CPN is defined by the Originating switch to be the billing number. In some cases (i.e., call forwarding) this may not be the actual originating calling number.
Intercompany compensation records for calls hereunder shall be subject to the verification procedures set forth in Section XVIII (Verification Reviews). Compensation for all calls shall be paid regardless of a Party’s ability to collect charges from its end user for such call or calls. Subject to the foregoing principles, the following compensation terms and conditions apply:
Moreover, with respect to calls originated by or terminated to CONNECT end users that traverse SWBT’s network and that either terminate to or originate from a subscriber to CMRS services, the Parties agree that compensation shall be governed by Appendix CELLULAR.
Subject to the foregoing principles, the following compensation terms and conditions shall apply:
4 SWBT-AR-I 56
A. Reciprocal Compensation for Termination of Local Traffic
1. Applicability of Rates:
a. The rates, terms, and conditions in this subsection A apply only to the termination of Local Traffic, except as explicitly noted.
b. CONNECT agrees to compensate SWBT for the termination of CONNECT Local Traffic originated by CONNECT end users in the SWBT exchanges described in Appendix DCO and terminating to SWBT end users located within those exchanges referenced therein. SWBT agrees to compensate CONNECT for the termination of SWBT Local Traffic originated by SWBT end users in the SWBT exchanges described in Appendix DCO and terminating to CONNECT end users located within those exchanges referenced therein.
2. Local Interconnect Rates: **
Rate per Minute of Use Tandem and End Office Served Traffic* $0.012
Usage shall be measured up to the nearest tenth of a minute and cumulated to one minute increments for billing.
*Subject to direct end office trunking commitment contained in Appendix ITR.
**Agreed upon with Brooks Fiber prior to release of FCC Order in Docket 96-98. This Agreement is entered into pursuant to @I 252(i) of the Act, and this term is included in this Agreement on that basis only.
C. Reciprocal Compensation for “Through-put” Traffic
1. Applicability of Rates:
The Parties agree to compensate one another for the transport of “through-put’’ or (intermediate tandem) traffic which neither originates nor terminates on billing Party’s network.
2. Rate Element:
SWBT-AR-157 5
A Tandem Through-put rate element applies to all minutes of use between local exchange service providers which traverse the billing Party’s tandem switch, but which neither originate with, nor terminate to that Party’s end user. This rate element includes compensation for tandem switching to connect local exchange service providers to third party providers, including CMRS providers. Charges are owed by the originating local exchange service provider. The local interconnect rate does not apply to such traffic.
3 . Rates: Rates Per Minute of Use
Tandem Through-put $0.0030
D. Reciprocal Compensation for termination of IntraLATA Interexchanae Traffic
For intrastate intraLATA interexchange service, compensation for termination of intercompany traffic will be at terminating access rates for Message Telephone Service or “MTS” and originating access rates for 800 Service, including the Carrier Common Line or “CCL” as set forth in each Party’s intrastate access service tariff.
E. Compensation for Origination Termination of InterLATA Interexchange Traffic (Meet-Point Billing “MPB ”Arrangements)
1. CONNECT and SWBT may mutually agree to establish Meet-Point billing arrangements in order to provide Switched Access Services to IXCs via an SWBT access tandem switch, in accordance with the Meet-Point Billing guidelines adopted by and contained in the Ordering and Billing Forum’s MECAT3 and MECOD documents, except as modified herein. CONNECT’ Meet-Points with SWBT shall be those identified in Appendix DCO.
2. The Parties will maintain provisions in their respective federal and state access tariffs, or provisions within the National Exchange Carrier Association (NECA) Tariff No. 4, or any successor tariff, sufficient to reflect this Meet-Point Billing arrangement, including Meet-Point Billing percentages.
3 . As detailed in the MECAB document, the Parties will, in accordance with accepted time intervals, exchange all information necessary to accurately, reliably and promptly bill third parties for Switched Access Services traffic jointly handled by the Parties via
SWBT-AR-158 6
IV.
the Meet-Point arrangement. Information shall be exchanged in Exchange Message Record (EMR) format, on magnetic tape or via a mutually acceptable electronic file transfer protocol.
4. Initially, billing to IXCs for the Switched Access Services jointly provided by the Parties via the Meet-Point Billing arrangement shall be according to the multiple bilVmultiple tariff method as described in the MECAB document.
5 . Meet-Point billing shall also apply to all traffic bearing the 900, 800, 888 NPA.
F. Billing Terms and Conditions
Other than for traffic described in subsection D above, each Party shall deliver monthly settlement statements for terminating the other Party’s traffic based on a mutually agreed schedule as follows:
a. Each Party will record its originating minutes of use including identification of the originating and terminating NXX for all intercompany calls.
b. Each Party will transmit the summarized originating minutes of use (from a. above) to the transiting and/or terminating Party for subsequent monthly intercompany settlement billing.
c. Bills rendered by either Party shall be paid within 30 days of receipt subject to subsequent audit verification as described in Section XVII (Verification Reviews).
d. Detailed technical descriptions and requirements for the recording, record exchange and billing of traffic are included in the Technical Exhibit Settlement Procedures (TESP).
NUMBERING
A. CONNECT is responsible for obtaining its own NXX codes. This responsibility shall include obtaining a separate NXX code or codes for each SWBT exchange or mandatory SWBT local calling scope where CONNECT intends to provide local service. The purpose of this responsibility is to provide the means by which to rate and measure the jurisdictional nature of traffic consistent with PSC and other lawful
1 Technical Exhibit Settlement Procedures, previously provided to CONNECT
7 SWBT-AR-159
requirements. Either Party’s rights to employ or to request and be assigned central office codes (NXX), are set forth in the Central Office Code Assignment Guidelines.2 CONNECT agrees it will assign numbers from the assigned NXX codes to end users located in the SWBT exchange or mandatory local calling scope where the NXX is assigned.
B. To the extent SWBT serves as Central Office Code Administrator for a given region, SWBT will work with CONNECT in a neutral and nondiscriminatory manner, consistent with regulatory requirements, in regard to CONNECT’ requests for assignment of central ofice code(s) (NXX) consistent with the Central Office Code Assignment Guidelines, and any applicable PSC rules and/or orders.
C. It shall be the responsibility of each Party to program and update its own switches to recognize and route traffic to other Party’s assigned NXX codes. Neither Party shall impose fees or charges on the other Party for required programming and updating switching activities.
D. CONNECT agrees that it shall input all required data necessary to update the Local Exchange Routing Guide (LERG) on its own behalf. In the alternative, upon CONNECT’ request, SWBT shall update the LERG for CONNECT. The charge for such service shall be $ 1 10 per NXX. SWBT shall not be liable for any losses or damages arising out of errors, defects, or failures associated with the input of CONNECT’ data into the LERG other than direct damages. CONNECT’ direct damages shall not exceed the amount of the charges paid to SWBT by CONNECT for LERG input under this Agreement.
E. CONNECT agrees to defend, indemnifl and hold harmless SWBT from any and all losses, damages, or other liabilities, including attorneys’ fees, that it may incur as a result of claims, demands, or other suits brought by any party that may arise out of the data submitted and/or the input of that data into the LERG by SWBT. CONNECT shall defend against all end user claims just as if CONNECT had performed its own input to the LERG.
F. Neither Party is responsible for notifjrlng the other Parties’ end users of any changes in dialing arrangements’ including those due to NPA exhaust.
2
Revision 4/7/95, formerly ICCF 93-0729-010. Last published by the Industry Numbering committee (“INC”) as INC 95-0407-008,
SWBT-AR-160 8
V.
VI.
APPENDICES
Attached to this Agreement are Appendices DEFINE, LIDB, CA, WP, RESALE, SS7, CH, RF, PORT, NMC, DCO, ITR, 911, CELLULAR, FGA, HOST, UNC, DA, OS, OSS, CNAM, RECORDING, BCR. To the extent that any definitions, terms, or conditions in such Appendices differ from those contained in the main body of this Agreement (not including the Appendices), those definitions, terms, or conditions shall supersede those contained in the main body of this Agreement, but only in regard to the services or activities listed in such Appendices. In particular, if an Appendix contains a term length and the main body of this is for a different term length, the term length of that Appendix shall control the length of time that services or activities are to occur under the Appendix but shall not be held to extend the term length of the remainder of this Agreement, except as may be necessary to interpret the Appendix.
ADDITIONAL SERVICES
A. 911/E911
SWBT shall make available nondiscriminatory access to 91 1 or E91 1 service under the terms and conditions described in Appendix 9 1 1, which is attached hereto and incorporated by reference.
B. Dialing Parity
1. Local Dialing Parity
SWBT agrees that local dialing parity will be available to CONNECT . That is, when customers of SWBT and CONNECT have the same exchange boundaries, these customers will be able to dial the same number of digits when making a "local" call.
2. IntraLATA Dialing Parity.
SWBT agrees to make intraLATA dialing parity available in accordance with Section 271(e) of the Telecommunications Act of 1996.
C. White Page Directory Listinps and Distribution
SWBT shall provide nondiscriminatory access to White Pages directory listing and distribution services under the terms described in Appendix WP, which is attached hereto and incorporated by reference.
9 SWBT-AR-I61
D. Directory Assistance (,DAI)
SWBT will provide nondiscriminatory access to DA services under the terms and conditions identified in Appendix DA, which is attached hereto and incorporated by reference.
E. Support Svstems Services
1 . Transfer of Service Announcements (Intercept)
When an end user changes from SWBT to CONNECT, or fi-om CONNECT to SWBT, and does not retain its original telephone number, the Party formerly providing service to the end user will provide a transfer of service announcement on the abandoned telephone number. This announcement will provide the new number to be dialed to reach this end user, unless the end user requests that the new number not be published, Each Party will provide this service consistent with its tariffs.
2. Coordinated Repair Calls
The Parties will employ the following procedures for handling misdirected repair calls:
a. The Parties will inform their respective end users of the correct telephone numbers to call to access their respective repair bureaus.
b. To the extent the correct provider can be determined, misdirected repair calls will be referred to the proper provider of local exchange service in a courteous manner, at no charge, and the end user will be provided the correct contact telephone number.
In responding to repair calls, neither Party shall make disparaging remarks about each other, nor shall they use these repair calls as the basis for internal referrals or to solicit customers or to market services. Either Party may respond with accurate information in answering customer questions.
C. The Parties will provide their respective repair contact numbers to one another on a reciprocal basis.
SWBT-AR-162 10
3 . Information Pape
At LSP’s request, SWBT shall include information in the “Informational Page” section of SWBT’s White Pages directory for those geographical areas in which LSP provides Exchange Services, for LSP’s customer contact information regarding emergency services, billing and service information, repair services and other similar such pertinent information. SWBT shall provide this service under the terms described in Appendix WP, which is attached hereto and incorporated by reference.
F. Operator Services
SWBT shall provide nondiscriminatory access to Operator Services, including Line Status Verification and Busy Line Interrupt, under the terms and conditions identified in Appendix OS, which is attached hereto and incorporated by reference.
G. LIDB Services
SWBT shall provide nondiscriminatory access to LIDB services pursuant to tariff and the additional terms and conditions in Appendix LIDB, which is attached hereto and incorporated by reference.
H. Clearinghouse Services
SWBT shall provide for the settlement of revenues from certain messages through the Clearinghouse services provided by SWBT pursuant to the terms and conditions in Appendix CH, which is attached hereto and made a part hereof.
I. Hosting;
Upon request, SWBT shall perform hosting responsibilities for the provision of billable message data and/or access usage data received from CONNECT for distribution to the appropriate billing and/or processing location or for deliver to CONNECT of such data via SWBT’s internal network or the nationwide CMDS network pursuant to Appendix HOST, which is attached hereto and made a part hereof.
11 SWBT-AR-163
VII.
J.
K.
L.
M.
N.
Recording
Upon request, SWBT shall perform recording, message processing and message detail services for CONNECT pursuant to Appendix RECORDING which is attached hereto and made a part hereof.
CNAM
Upon request, SWBT shall provide Calling Name Delivery Query Service to CONNECT pursuant to Appendix CNAM which is attached hereto and made a part hereof.
BCR
Upon request, S W T shall provide Billing, Collecting and Remitting services to CONNECT pursuant to Appendix BCR which is attached hereto and made a part hereof.
Upon request, the Parties shall provide access to Riser Space pursuant to the terms and conditions of Appendix RF.
ass Set forth the terms and conditions under which SWBT will provide operation Support System access.
POLES. DUCTS. CONDUITS. AND RIGHTS-OF-WAY
Upon request, the Parties shall provide non-discriminatory access to the poles, ducts, conduits, and rights-of-way they own or control. If a request for such access is made, the Parties will negotiate a stand alone agreement to provide for it.
VIII. UNBUNDLED ARRANGEMENTS
Upon request, the S W T shall provide to CONNECT unbundled network components. SWBT’s terms and conditions are identified in Appendix UNC, which is attached hereto and made a part hereof.
IX. LOCAL NUMBER PORTABILITY
Upon request, the Parties shall provide reciprocal interim number portability arrangements. SWBT’s terms and conditions for the provisioning of this service are outlined in Appendix PORT, which is attached hereto and made a part hereof
12 SWBT-AR-164
X.
XI.
XI.
RESALE
Upon request, SWBT shall provide certain services for resale. SWBT’s terms and conditions regarding the resale of local exchange telephone services are outlined in Appendix RESALE, which is attached hereto and made a part hereof.
LEASED SPACE
Conditioned upon the provisions contained in Appendix NIM, SWBT shall permit LSP to place, maintain and operate in collocation premises any telecommunications equipment not specified by the FCC in CC Docket 9 1 - 14 1 that is necessary for LSP to provide any and all services which LSP has legal authority to provide.
ADDITIONAL RESPONSLBILITIES OF THE PARTIES
A. Notice of Network Changes
The Parties agree to provide each other reasonable notice of changes in the information necessary for the transmission and routing of services using that local exchange carrier’s facilities or networks, as well as other changes that would affect the interoperability of those facilities and networks.
B. Cooperation on Fraud
The Parties agree that they shall cooperate with one another to investigate, minimize and take corrective action in cases of fraud. The Parties’ fraud minimization procedures are to be cost effective and implemented so as not to unduly burden or harm one Party as compared to the other.
At a minimum, such cooperation shall include providing to the other Party, upon request, information concerning end users who terminate services to that Party without paying all outstanding charges, when such end user seeks service fiorn the other Party. It shall be the responsibility of the Party seeking such information to secure the end user’s permission to obtain such information.
C . Payments of Rates and Charges
When a Party orders service from another Party, the service provider may require, prior to the time the service order is accepted, an advance payment. The Parties shall pay all rates and charges due and owing within 30 days of receipt of an invoice unless such charges are governed by the clearinghouse process included as Appendix CH. Interest on overdue
SWBT-AR-I65 13
invoices shall apply at the applicable rates specified in S W T ’ s Access Services Tariffs.
If a Party is billed incorrectly for services rendered pursuant to this Agreement, a billing adjustment will be calculated. If a refund is due, an adjustment shall be made for the entire period of the overcharges, not to exceed twenty-four (24) months. If an overcharge is adjusted within three billing cycles of the bill in error, interest will not be applicable. If the overcharge is not adjusted within three billing cycles, interest on the amount will be credited at the applicable rate from SWBT’s Access Services Tariffs.
D. Enforcement for Non-Pavment or Other Violations
Upon nonpayment of any sum due, or upon violation of any conditions governing the hrnishing of service, a Party may, after exhaustion of the dispute resolution procedures specified in Section XXI., herein, seek redress by any and all means as may be available under state or federal law, regulations or decisions. If a Party disputes any charges billed or imposed by the other Party, it shall promptly noti@ the other Party of the charges which it disputes and pay any undisputed amount.
Prior to termination of service for nonpayment, the Parties agree to investigate any allegations of improper charges and agree to attempt to resolve each dispute prior to the disconnection of any account(s) for nonpayment.
E. Changes in Subscriber Carrier Selections
Changes in subscriber carrier selections shall be effected only in a manner consistent with rules and decisions of the Federal Communications Commission (FCC) or, if applicable, respective state public utility commissions. In the absence of any state or federal rules applicable to changes in subscriber carrier selections for in local service, the rules of the FCC establishing methods for subscriber changes in Primary Interexchange Carrier selections shall apply to changes in subscriber carrier selections for local service under this Agreement.
XIII. OTHER OBLIGATIONS OF LSP
A. ComDensation Between LSP and Third Parties
CONNECT acknowledges that it has the responsibility to make such compensation arrangements as may be necessary with third-parties where traffic originated on CONNECT’ network is destined to a third-party’s
14 SWBT-AR-166
network. CONNECT agrees to indemnify and hold harmless SWBT with respect to any claims or damages arising from any dispute between CONNECT and a third-party concerning compensation for the termination of CONNECT’ traffic on such third-party’s network. CONNECT firther agrees to take all reasonable steps to avoid situations where a third-party would block termination of CONNECT’- originated traffic which traverses SWBT’s network.
For the purposes of establishing service and providing efficient and consolidated billing to CONNECT, CONNECT is required to provide SWBT its authorized and nationally recognized Operating Company Number (OCN).
B. Special Service Arrangements
For special service arrangements not covered under this Agreement, special charges shall apply as provided in the applicable state General Exchange Tariff or the interstate Access Services tariff.
C. Special Construction
If CONNECT’ request for service requires construction of special facilities, special construction charges shall apply as provided in the applicable state General Exchange Tariff or the interstate Access Services tariff
XIV. NETWORK MAINTENANCE AND MANAGEMENT
The Parties will work cooperatively to install and maintain a reliable network. The Parties will exchange appropriate information (e.g., maintenance contact numbers, network information, information required to comply with law enforcement and other security agencies of the government, etc.) to achieve this desired reliability.
A. Law Enforcement and Civil Process
SWBT and CONNECT shall handle law enforcement requests as follows:
1) INTERCEPT DEVICES. Local and federal law enforcement agencies periodically request information or assistance from local telephone service providers. When either Party receives a request associated with a customer of the other Party, it shall refer such request to the Party that serves such customer, unless the request directs the receiving Party to attach a pen register, trap-and-trace or form of intercept on the Party’s facilities, in which case that Party shall comply with any valid request.
SWBT-AR-167 15
xv.
2) SUBPOENAS. If a Party receives a subpoena for information concerning an end user the Party knows to be an end user of the other Party it shall refer the subpoena back to the requesting Party with an indication that the other Party is the responsible company, unless the subpoena requests records for a period of time during which the Party was the end users service provider, in which case the Party will respond to any valid request.
3) HOSTAGE OR BARRICADED PERSONS EMERGENCIES. If a Party receives a request from a law enforcement agency for temporary number change, temporary disconnect or one way denial of outbound calls for an end user of the other Party by the receiving Party’s switch, that Party will comply with any valid emergency request. However, neither Party shall be held liable for any claims or damages arising from compliance with such requests on behalf of the other Party’s end user and the Party serving such end user agrees to indemnify and hold the other Party harmless against any and all such claims.
B. Network Management Controls
Each Party shall provide a 24-hour contact number for Network Traffic Management issues to the other’s surveillance management center. A FAX number must also be provided to facilitate event notifications for planned mass calling events. Each Party agrees, at a minimum, to maintain the network traffic management controls capabilities set forth in Appendix Nh4C Each Party shall maintain the capability of respectively implementing basic protective controls such as “Cancel To” and “Call Gap.”
FORCE MAJEURE
Neither party shall be responsible for delays or failures in performance resulting from acts or occurrences beyond the reasonable control of such Party, regardless of whether such delays or failures in performance were foreseen or foreseeable as of the date of this Agreement, including, without limitation: fire, explosion, power failure, acts of God, war, revolution, civil commotion, or acts of public enemies; any law, order, regulation, ordinance or requirement of any government or legal body; or labor unrest, including, without limitation, strikes, slowdowns, picketing or boycotts; or delays caused by the other party or by other service or equipment vendors; or any other circumstances beyond the Party’s reasonable control. In such event, the Party affected shall, upon giving prompt notice to the other Party, be excused from such performance on a day-to-day basis to the extent of such interference (and the other Party shall likewise be excused from performance of its obligations on a day-for-day basis to the extent such Party’s obligations relate to the performance so interfered with). The affected party shall use its best efforts to
16 SWBT-AR-168
avoid or remove the cause of non-performance and both parties shall proceed to perform with dispatch once the causes are removed or cease.
XVI . INDEMNIFICATION AND LIMITATION OF LIABILITY
A. INDEMNIFICATION
1. Each Party shall be responsible only for service(s) and facility(ies) which are provided by that Party, its authorized agents, subcontractors, or others retained by such parties, and neither Party shall bear any responsibility for the services and facilities provided by the other Party, its agents, subcontractors, or others retained by such parties.
2 . Except as otherwise provided in this Section, and to the extent not prohibited by law and not otherwise controlled by tariff, each Party (the “Indemnifjing Party”) shall defend and indemnify the other Party (the “Indemnified Party”) and hold such Indemnified Party harmless against any Loss to a third party arising out of the negligence or willhl misconduct by such Indemnifjring Party, its agents, its end user, contractors, or others retained by such parties, in connection with its provision of services or functions under this Agreement
3. In the case of any Loss alleged or made by an end user of either Party, the Party (“Indemnifjling Party”) whose end user alleged or made such Loss shall defend and indemnifjl the other Party (the “Indemnified Party”) and hold such Indemnified Party harmless against any or all of such Loss alleged by each and every end user. CONNECT agrees to indemnify, defend, and hold harmless SWBT from any Loss arising out of SWBT’s provision of 91 1 services or out of CONNECT’ end users’ use of the 91 1 service, whether suffered, made, instituted or asserted by CONNECT or its end users, including for any personal injury or death of any person or persons, except for Loss which is the direct result of SWBT’s own negligence or willhl misconduct.
4. Each Party (“Indemnified Party”) shall be indemnified, defended and held harmless by the other Party (“Indemnifying Party”) against any Loss arising from such Indemnitling Party’s use of services offered under this Agreement, involving:
(a) Tort claims, including claims for libel, slander, invasion of privacy, or infringement of copyright arising from the
17 SWBT-AR-169
Indemnifiing Party’s own communications or the communications of such Indemnifying Party’s end users; or
Claims for patent, trademark, copyright infringement or other Infringement of intellectual property rights, arising from the Indemnifying Party’s acts combining or using the service hrnished by the Indemnified Party in connection with facilities or equipment furnished by the Indemnifying Party or its end users, agents, subcontractors or others retained by such parties.
5 . The Indemnifying Party agrees to defend any suit brought against the Indemnified Party for any Loss identified in this Section. The Indemnified Party agrees to notify the Indemnifying Party promptly in writing of any written claims, lawsuits, or demand for which such Indemnifying Party is or may be responsible and of which the Indemnified Party has knowledge, and to cooperate in every reasonable way to facilitate defense or settlement of claims. The Indemnifying Party shall have the exclusive right to control and conduct the defense and settlement of any such actions or claims subject to consultation with the Indemnified Party. The Indemnifying Party shall not be liable for any settlement by the Indemnified Party unless such Indemnifjring Party has approved such settlement in advance and agrees to be bound by the agreement incorporating such settlement.
B. LIMITATION OF LIABILITY
1. Except for Losses alleged or made by an end user sf either Party, in the case of any Loss alleged or made by a third party arising from the negligence or willful misconduct of both Parties, each Party shall bear, and its obligations under this Section shall be limited to, that portion (as mutually agreed to by the Parties) of the resulting expense caused by its (including that of its agents, servants, contractors, or others acting in aid or concert with it) negligence or willhl misconduct.
2. Except for Indemnity obligations under this Section, each Party’s liability to the other Party for any Loss relating to or arising out of any negligent act or omission in its performance of this Agreement, whether in contract or in tort, shall not exceed in total the amount SWBT or CONNECT has or would have charged to the other Party for the affected service(s) or hnction(s) for the time period during which the service(s) or fiinction(s) were not performed or were otherwise improperly performed.
18 SWBT-AR-170
3. In no event shall either Party have any liability whatsoever to the other Party for any indirect, special, consequential, incidental, or punitive damages, including but not limited to, loss of anticipated profits or revenue or other economic loss in connection with or arising from anything said, omitted or done hereunder (collectively, “Consequential Damages”), even if the other Party has been advised of the possibility of such damages; provided, that the foregoing shall not limit a Party’s obligation under this Section to indemnifjr, defend and hold the other Party harmless against any amounts payable to a third party, including any losses, costs, fines, penalties, criminal or civil judgments or settlements, expenses (including attorneys’ fees) and Consequential Damages of such third party.
4. Notwithstanding any other provision of this Section, none of the limitations on liability restrictions shall apply to actions by either Party against the other Party under applicable regulatory laws, rules, regulations or orders.
XVII . LIQUIDATED DAMAGES FOR SPECIFIED ACTIVITIES
A. Certain Definitions. When used in this Section, the following terms shall have the meanings indicated:
1. “Specified Performance Breach” means the failure by SWBT to meet the Performance Criteria for any Specified Activity for a period of three (3) consecutive calendar months.
2. “Specified Activity” means any of the following activities:
The installation by SWBT of unbundled Loops for CONNECT, including the installation of unbundled Loops under applicable tariff( s) (“Unbundled Loop Installation”);
SWBT’s provision of Interim Number Portability; or
(c) the repair of out of service problems for CONNECT (“Out of Service Repairs”).
3. “Performance Criteria” means, with respect to each calendar month during the term of Agreement, the performance by SWBT during such month of each Specified Activity shown below within the time interval shown in at least eighty percent (80%) of the covered instances:
19 SWBT-AR-171
SPECIFIED ACTIVITY (i) Unbundled Loop Installation
1-10 Loops per Service Order
PERFORMANCE INTERVAL DATE
5 days from SWBT's Receipt of valid Service Order
11-20 Loops per Service Order I I 10 days from SWBT's Receipt of valid Service Order
21 + Loops per Service Order I To be Negotiated
B. Specified Performance Breach. In recognition of (1) the loss of end user opportunities, revenues and goodwill which CONNECT might sustain in the event of a Specified Performance Breach; (2) the uncertainty, in the event of such a Specified Performance Breach, of CONNECT having available to it customer opportunities similar to those opportunities currently available to CONNECT; and (3) the difficulty of accurately ascertaining the amount of damages CONNECT would sustain in the event of such a Specified Performance Breach, SWBT agrees to pay CONNECT, subject to Section D., below, damages as set forth in Section C., below in the event of the occurrence of a Specified Performance Breach.
(ii) Interim Number Portability
1 - 10 Numbers per Service Order
SWBT-AR-172
5 days from SWBT's Receipt of valid Service Order
20
11-20 Numbers per Service Order I 10 days from SWBT's Receipt of valid Service Order
21 + Numbers per Service Order
(iii) Out-of-Service Repairs
To be Negotiated
Less than 24 hours from SWBT's Receipt of Notification of Out-of- Service Condition
XVIII.
C. Liquidated Damages. The damages payable by SWBT to CONNECT as a result of a Specified Performance Breach shall be $75,000 for each Specified Performance Breach (collectively, the “Liquidated Damages”). CONNECT and SWBT agree and acknowledge that (1) the Liquidated Damages are not a penalty and have been determined based upon the facts and circumstances of CONNECT and SWBT at the time of the negotiation and entering into of this Agreement, with due regard given to the performance expectations of each Party; (2) the Liquidated Damages constitute a reasonable approximation of the damages CONNECT would sustain if its damages were readily ascertainable; and (3) CONNECT shall not be required to provide any proof of the Liquidated Damages.
D. In no event shall SWBT be liable to pay the Liquidated Damages if SWBT’s failure to meet or exceed any of the Performance Criteria is caused, directly or indirectly, by a Delaying Event. A “Delaying Event” means (1) a failure by CONNECT to perform any of its obligations set forth in this Agreement , (2) any delay, act or failure to act by an end user, agent or subcontractor of CONNECT, (3) any Force Majeure Event, or (4) for INP, where memory limitations in the switch in the SWBT serving ofice cannot accommodate the request. If a Delaying Event (a) prevents SWBT from performing a Specified Activity, then such Specified Activity shall be excluded from the calculation of SWBT’s compliance with the Performance Criteria, or (b) only suspends SWBT’s ability to timely perform the Specified Activity, the applicable time frame in which SWBT’s compliance with the Performance Criteria is measured shall be extended on an hour-for-hour basis, as applicable, equal to the duration of the Delaying Event.
E. Sole Remedy. The Liquidated Damages shall be the sole and exclusive remedy of CONNECT for SWBT’s breach of the Performance Criteria or a Specified Performance Breach as described in this Section XVII and shall be in lieu of any other damages or credit CONNECT might otherwise seek for such breach of the Performance Criteria or a Specified Performance Breach through any claim or suit brought under any contract or tariff except for repeated problems as found in the State Commission.
F. Records. SWBT shall maintain complete and accurate records, on a monthly basis, of its performance under this Agreement of each Specified Activity and its compliance with the Performance Criteria. SWBT shall provide to CONNECT such records in a self-reporting format on a monthly basis. Such records shall be deemed “Proprietary Information” under Section XVIII.
NONDISCLOSURE
The Parties to this Agreement anticipate and recognize that they will exchange or come into possession of, technical or business information or data about each
21 SWBT-AR-173
XIX.
xx.
other's end users and each other's business as a result of this Agreement which will be considered confidential by that Party. Each Party agrees (1) to treat all such information as strictly confidential and (2) to use such information only for purposes of performance under this Agreement. Each Party agrees not to disclose confidential information on the other Party's end users or business to any person without first securing the written consent of the other Party. The foregoing shall not apply to information which is in the public domain.
If a court or governmental agency orders or a third-party requests a Party to disclose or to provide any data or information covered by this Section, that Party will immediately inform the other Party of the order or request before such data is provided and will inform the other Party both by telephone and certified mail. Notification and consent requirements described above are not applicable in cases where a court order requires the production of toll billing records of an individual residence or business end user customer.
This section will not preclude the disclosure by the Parties of information or data described in this Section to consultants, agents, or attorneys representing the respective Parties or the State Commissions or their staffs or FCC Staff, provided that these third-parties are bound by the same or comparable confidentiality requirements as the Parties to this Agreement.
The provisions of this Section will remain in effect notwithstanding the termination of this Agreement, unless agreed to in writing by both Parties.
Pursuant to Section 222 of the Act, both Parties agree to limit their use of proprietary information received from the other to the permitted purposes identified in the Act.
PUBLICITY
The Parties agree not to use in any advertising or sales promotion, press releases or other publicity matters any endorsements, direct or indirect quotes, or pictures implying endorsement by the other Party or any of its employees without such Party's prior written approval. The Parties will submit to each other for written approval, prior to publication, all such publicity matters that mention or display one another's name and/or marks, or contain language from which a connection to said name and/or marks may be inferred or implied, in a manner that conveys or implies endorsement of the other Party.
ASSIGNMENT
Neither Party may assign, subcontract, or otherwise transfer its rights or obligations under this Agreement except under such terms and conditions as are
22 SWBT-AR-174
XXI.
mutually acceptable to the other Party and with such Party’s prior written consent, which consent shall not be unreasonably withheld.
DISPUTE RESOLUTION
A. Finality of Disputes
No claims shall be brought for disputes arising from this Agreement more than 24 months from the date of occurrence which gives rise to the dispute.
B. Alternative to Litigation
The Parties desire, where possible, to resolve disputes arising out of this Agreement without litigation. Accordingly, except for action seeking a temporary restraining order or an injunction related to the purposes of this Agreement, or suit to compel compliance with this dispute resolution process, the Parties agree to use the informal dispute resolution process described in subsection 1 below. Additionally, the Parties may, by mutual consent regarding a particular dispute, agree to use the arbitration procedure described in subsection 2 below as their sole remedy with respect to a controversy or claim of $25,000 or less, arising out of or relating to this Agreement or its breach. If either party declines to utilize the arbitration procedures described in subsection 2 below, the Parties shall be free to pursue any and all legal and administrative remedies which may be available under the circumstances once they have exhausted the procedures outlined in subsection 1 below.
1. Resolution of Disputes Between Parties to the Agreement
At the written request of a Party, each Party will appoint a knowledgeable, responsible representative to meet and negotiate in good faith to resolve any dispute arising under this Agreement. The location, form, frequency, duration and conclusion of these discussions shall be lee to the discretion of the representatives. Upon agreement, the representatives may utilize other alternative dispute resolution procedures such as mediation to assist in the negotiations. Discussions and correspondence among the representatives for purposes of settlement are exempt from discovery and production and shall not be admissible in the arbitration described below or in any lawsuit without the concurrence of all Parties. Documents identified in or provided with such communications, which are not prepared for purposes of the negotiations, are not so exempted and, if otherwise admissible, may be admitted in evidence in the arbitration or lawsuit. If the Parties are unable to resolve the dispute within thirty (30) days after
23 SWBT-AR-I 75
the initial notification of the dispute (or within such shorter period as the circumstances may require, they shall thereafter have the right to pursue such legal or administrative remedies as may be available in the circumstances.
2. Arbitration
If the negotiations do not resolve the dispute within sixty (60) days of the initial written request, the dispute shall be submitted to binding arbitration by a single arbitrator pursuant to the Commercial Arbitration Rules of the American Arbitration Association. A Party may demand such arbitration in accordance with the procedures set out in those rules. Discovery shall be controlled by the arbitrator and shall be permitted to the extent set out in this section. Each Party may submit in writing to a Party, and that Party shall so respond, to a maximum of any combination of thirty-five (35) (none of which may have subparts) of the following:
(a) Interrogatories (b) Demands to produce documents (c) Requests for admission
Additional discovery may be permitted upon mutual agreement of the Parties. The arbitration hearing shall be commenced within sixty (60) days of the demand for arbitration. The arbitration shall be held in Little Rock, unless otherwise agreed. The arbitrator shall control the scheduling so as to process the matter expeditiously. The Parties shall submit written briefs five days before the hearing. The arbitrator shall rule on the dispute by issuing a written opinion within thirty (30) days after the close of hearings. The arbitrator has no authority to order punitive or consequential damages. The times specified in this section may be extended upon mutual agreement of the Parties or by the arbitrator upon a showing of good cause. Judgment upon the award rendered by the arbitrator may be entered in any court having jurisdiction.
3 . costs
Each Party shall bear its own costs of these procedures. A Party seeking discovery shall reimburse the responding Party the costs of production of documents (including search time and reproduction costs). The Parties shall equally split the fees of the arbitration and the arbitrator.
24 SWBT-AR-176
XXII
XXIII .
VERIFICATION REVIEWS
Each Party to this Agreement will be responsible for the accuracy and quality of its data as submitted to the respective parties involved. Upon reasonable written notice, each Party or its authorized representative (providing such authorized representative does not have a conflict of interest related to other matters before one of the Parties) shall have the right to conduct a review and verification of the other Party to give assurances of compliance with the provisions of this Agreement. This includes on-site verification reviews at the other Party’s or the Party’s vendor locations.
Each Party’s right to access information for verification review purposes is limited to data not in excess of 24 months in age. Information of either Party involved with a verification review shall be subject to the nondisclosure terms of this Agreement.
The Party requesting a verification review shall fidly bear its costs associated with conducting the review. The Party being reviewed will provide access to required information, as outlined in this Section, at no charge to the reviewing Party. Should the reviewing Party request information or assistance beyond that reasonably required to conduct such a review, the Party being reviewed may, as its option, decline to comply with such request or may bill actual costs incurred in complying subsequent to the concurrence of reviewing Party.
COMPLIANCE WITH LAWS.
This Agreement is entered into pursuant to Section 252(i) of the Act. SWBT believes in good faith that the services to be provided under this Agreement satisfL the requirements of the Telecommunications Act of 1996, specifically $25 1, $252 and $271, and is in the public interest. CONNECT believes the Agreement satisfies the standard of review for negotiated interconnection agreements under Sec. 252(e)(2) of the Act. CONNECT makes no fbrther or additional admissions concerning whether and to what extent the Agreement may satisf) other provisions of the Act. In the event a court or regulatory agency of competent jurisdiction should determine that modifications of this Agreement are required to bring the services being provided hereunder into compliance with the Act, the affected Party shall promptly give the other Party written notice of the modifications deemed required. Upon delivery of such notice, the Parties shall expend diligent efforts to arrive at an agreement respecting such modifications required, and if the Parties are unable to arrive at such agreement, either Party may terminate this Agreement, without penalty, effective the day the affected Party is ordered to effect the modifications deemed required, or effective on the day either Party concludes and gives notice that the Parties will not be able to arrive at any agreement respecting such modifications, whichever date shall occur earlier.
SWBT-AR-177 25
This Agreement is an integrated package that reflects a balancing of interests critical to the Parties. It will be submitted to the Arkansas Commission and the Parties will specifically request that the State Commissions refrain from taking any action to change, suspend or otherwise delay implementation of the Agreement. So long as the Agreement remains in effect, the Parties shall not advocate before any legislative, regulatory, or other public forum that any terms of this specific Agreement be modified or eliminated, except pursuant to procedures specifically sanctioned by the terms of this Agreement, including those established in Section XXIII, below. Notwithstanding this mutual commitment, however, the Parties enter into this Agreement without prejudice to any positions they have taken previously, or may take in the fbture in any legislative, regulatory, or other public forum addressing any matters, including matters related to the types of arrangements prescribed by this Agreement.
XXIV. EFFECT OF OTHER AGREEMENTS
If either Party enters into an agreement (the “Other Agreement”) approved by the Arkansas Public Service Commission, pursuant to Section 252 of the Act which provides for the provision of arrangements covered in this Agreement to another requesting Telecommunications Carrier, such Party shall make available in Arkansas, to the other Party such arrangements upon the same rates, terms and conditions as those provided in the Other Agreement. At its sole option, the other Party may avail itself of either (i) the Other Agreement in its entirety or (ii) the prices, terms and all material conditions of the Other Agreement that directly relate to any of the following duties as a whole:
All Interconnection Rates - Section 25 l(c)(2) of the Act (Section 111 of this Agreement); or
Access to Unbundled Network Elements - Section 251(c)(3) of the Act (Section VI11 and Appendix UNC of this Agreement); or
Resale - Section 251(c)(4) of the Act (Appendix RESALE of this Agreement); or
Collocation - Section 251(c)(6) of the Act (Appendix NIM of this Agreement); or
Number Portability - Section 251(b)(2) of the Act (Appendix PORT) of this Agreement); or
Access to Rights of Way - Section 25 1 (b)(4) of the Act (by separate Agreement); or
Cellular Traffic (Appendix Cellular); or
26 SWBT-AR-I78
(9) White Pages - (Appendix WP);
(10) Operator Services - (Appendix OS);
(1 1) Directory Assistance - (Appendix DA);
If and to the extent the respective state public utility commission, the FCC or a court of competent jurisdiction issues a final and effective order obligating either Party to provide interconnection and related services and functions in a particular state(s) at specific rates terms and conditions which differ from those contained in this Agreement, nothing in this Agreement shall be construed to prevent prospective implementation of such different rates terms and conditions for the remainder of the term of this Agreement.
Nothing herein shall be interpreted to require CONNECT to pay to SWBT the same rates or charges as CONNECT pays to a third party for the same type of services or facilities provided to CONNECT by SWBT under this Agreement.
xxv. CERTIFICATION REOUIREMENT S
At the time CONNECT commences the offering of regulated services utilizing services or hnctions pursuant to this Agreement, CONNECT will warrant that it has obtained all necessary jurisdictional certification required in those jurisdictions in which CONNECT has ordered such services.
XXVI. NOTICES
In an event any notices are required to be sent under the terms of this Agreement, they shall be sent by registered mail, return receipt requested to:
To SWBT: To CONNECT:
24 Hour Network Management Contact
For SWBT: For CONNECT:
XXVII . THTRD PARTY BENEFICIARIES
This Agreement shall not provide any non-party with any remedy, claim, cause of action or other right.
27 SWBT-AR-179