1、Version 1 Page i November 1999ATIS/OBF-PICC-001ORDERING AND BILLINGFORUM (OBF)CABS(Carrier Access Billing System)PICC DISPUTEFILE SPECIFIC ATIONSNOVEMBER 1999 ISSUE 1THIS PAGE INTENTIONALLY LEFT BLANK.Version 1 Page i November 1999Copyright 1999 by the Alliance for Telecommunications Industry Soluti
2、ons Inc.All rights reserved.The CABS PICC Dispute File Specifications document, November 1999, iscopyrighted, printed and distributed by the Alliance for Telecommunications IndustrySolutions (ATIS) on behalf of the ATIS-sponsored Ordering and Billing Forum (OBF).Except as expressly permitted, no par
3、t of this publication may be reproduced ordistributed in any form, in an electronic retrieval system or otherwise, without theprior express written permission of ATIS. All requests to reproduce this documentshall be in writing and sent to: OBF Manager, c/o ATIS, 1200 G Street, NW, Suite500, Washingt
4、on, DC 20005. OBF Funding Companies (which are defined in theOBF Guidelines) should refer to the OBF Guidelines as respects their rights toreproduce this publication.For ordering information, please contact:Mike Nichols, Manager - Industry ForumsATIS1200 G Street N.W., Suite 500Washington, DC 20005m
5、nicholatis.orgThe OBF Document store link is available on the ATIS Web Site at:http:/www.atis.org/atis/clc/obf/obfdocs.htmNoticeThis document was developed by the Billing Committee of the Alliance forTelecommunications Industry Solutions (ATIS) Ordering and Billing Forum (OBF). TheOBF provides a for
6、um for customers and providers in the telecommunicationsindustry to identify, discuss and resolve national issues which affect ordering, billing,provisioning and exchange of information about access services, other connectivityand related matters. The Billing Committee is responsible for identifying
7、 andincorporating the necessary changes into this document. All changes to thisdocument shall be made through the OBF issue resolution process and adopted bythe Billing Committee as set forth in the OBF Guidelines.This document is administratively maintained by Cap Gemini Telecommunicationsunder the
8、 direction of ATIS and the OBF. It is distributed exclusively by ATIS.Disclaimer and Limitation of LiabilityThe information provided in this document is directed solely to professionals whohave the appropriate degree of experience to understand and interpret its contents inaccordance with generally
9、accepted engineering or other professional standards andapplicable regulations. No recommendation as to products or vendors is made orshould be implied.NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION ISTECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE,GOVERNMENTAL RULE OR REGU
10、LATION, AND FURTHER NO REPRESENTATION ORWARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULARPURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS.ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED INPAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND
11、 INNO EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL ORCONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES THAT ANY AND ALL USEOF OR RELIANCE UPON THE INFORMATION PROVIDED IN THIS DOCUMENT IS ATTHE RISK OF THE USER.Version 1 Page i November 19991.0 PREFACE 12.0 GENERAL DESCRIPTION 22.1 S
12、COPE 22.2 D OCUMENT R EVISIONS . 22.3 R ELATED OBF I SSUES . 22.4 D ATA E LEMENT R EQUIREMENTS . 23.0 PICC DISPUTE DATA 33.1 I NTENT OF F ILE 33.2 D ISTRIBUTION 33.3 P APER D ISPUTE N OTIFICATION 33.4 M ECHANIZED F ILE R ECORDS . 34.0 FILE REQUIREMENTS . 44.1 M ECHANIZED F ILE O RGANIZATION 44.2 M E
13、CHANIZED D ATA F ORMAT 44.3 M ECHANIZED F ILE R ECORDS . 44.3.1 PICC Dispute File Header . 44.3.2 PICC Dispute File Data . 44.3.3 PICC Trailer Record 4APPENDIX A - OBF ISSUES INCLUDED IN PDFS REVISIONS . 5APPENDIX B - FILE DATA ELEMENT DEFINITIONS . 6COMPANY CONTACT 7CONTACT NUMBER . 7ACNA . 6BILLIN
14、G ACCOUNT NUMBER 6INVOICE DATE . 8PICC EXTRACTION DATE . 9CIC . 6STATE 10LATA . 8JURISDICTION 8PICC APPLICATION TYPE INDICATOR . 9PICC CENTREX INDICATOR . 9TELEPHONE NUMBER (TN) 10HUNT GROUP 8TERMINAL NUMBER . 10OUTGOING ONLY (OGO) 9NUMBER OF CHANNELS . 8REASON CODE . 9REASON TEXT 10UN-PIC DATE 10EN
15、D USER NOTIFICATION DATE 7END OFFICE CLLI 7CIRCUIT NUMBER . 6DISPUTE AMOUNT 7APPENDIX C - FILE LAYOUT . 11CABS PDFSVersion 1 Page ii November 1999THIS PAGE INTENTIONALLY LEFT BLANK.CABS PDFSVersion 1 Page 1 November 19991.0 PREFACEThis document represents the Ordering and Billing Forum (OBF) Billing
16、 Committeerequirement to create a document of CABS PICC Dispute File Specifications (PDFS).These procedures were cooperatively developed in the OBF. They were written inresponse to OBF Issue 1675. All changes to this document must be presented to theOBF Billing Committee and accepted by consensus. T
17、he OBF Billing Committee isresponsible for the on-going maintenance and distribution of this document based onresolved issues.The OBF is a voluntary, self-policing group of participants who meet together toidentify, discuss and resolve issues which are national in scope, involvingordering and billin
18、g of access services. The OBF functions under the auspicesof the Carrier Liaison Committee (CLC) of the Alliance for TelecommunicationsIndustry Solutions (ATIS). The Federal Communications Commission (FCC)authorized the CLC in a January 17, 1985 Memorandum Opinion and Order.CABS PDFSVersion 1 Page 2
19、 November 19992.0 GENERAL DESCRIPTION2.1 ScopeThe CABS PICC Dispute File Specifications (PDFS) are guidelines for providingstandard mechanized file layouts for line level or circuit level PICC Disputes.Implementation of PDFS outputs such as timing and media (CD-ROM, Diskette, e-mail, etc.) used to p
20、rovide this information will be negotiated between the individualcustomers and providers.2.2 Document RevisionsThe PDFS document will be updated as necessary based upon resolved OBF Issues asidentified by the OBF Billing Committee.All text revisions will be identified by a “|” in the right margin. T
21、he “|” will be placedto the immediate right of each line of revised text.All revisions to this document will have version numbers and associatedimplementation time lines .2.3 Related OBF IssuesOBF issues incorporated into the PDFS document are displayed as Appendix A of thisdocument.2.4 Data Element
22、 RequirementsThe data element requirements (including data attributes and other pertinentinformation) are documented within the text of each field defined in AppendixB.CABS PDFSVersion 1 Page 3 November 19993.0 PICC Dispute Data3.1 Intent of FileThis file is intended to provide, per OBF Issue 1675,
23、PICC Dispute Information,including all information needed to support and resolve the PICC dispute.3.2 DistributionPDFS files are provided in support of a PICC dispute. As such, a PDFS file should beproduced each time the customer identifies a dispute situation. As negotiatedbetween the individual cu
24、stomers and providers, these files may be sent separately foreach processing center within a company, or provided on one file representing theentire company. Customers will distribute the delimited text file based on thenotification process and timeline in accordance with individual customer and pro
25、videragreements.3.3 Paper Dispute NotificationWhile this document is intended to discuss the mechanized files in support of PICCdisputes, it is recognized that both customers and providers may wish to have sometype of paper notification of the dispute. Such notification may be sent as part of, orsep
26、arately from, the mechanized file records.Paper notification is typically in the form of a letter that may contain certain high levelinformation about the dispute (e.g., the type of PICC being disputed, associatedamount, and the cause of the dispute). The actual form and content is as negotiatedbetw
27、een the customer and provider.3.4 Mechanized File RecordsAs per the resolution to OBF Issue 1675, the mechanized file is to be provided as adelimited text file. The delimited text file was chosen because it allows the receiver ofthe file to view and manipulate the data into most PC software applicat
28、ions (such asMicrosoft Word or Microsoft Access. Expected delivery mediums include, but arenot limited to: CD-ROM, Diskette, or e-mail. Both the customer and the providershould agree upon the specific delivery medium.Section 4 of this document further discusses the mechanized file records.CABS PDFSV
29、ersion 1 Page 4 November 19994.0 File Requirements4.1 Mechanized File OrganizationEach file will contain PICC data in support of dispute(s). The data in each file willsupport a specific PICC dispute. The data contained within a file should be presentedin the same order as discussed in Appendices B a
30、nd C of this document.4.2 Mechanized Data FormatThe data format is a text-delimited file. The file should contain the data elementsidentified in Appendix B. See Appendix C for the layout of the delimited text file.4.3 Mechanized File RecordsEach PICC data file is comprised of three sections (i.e., a
31、 PICC Dispute File Header,PICC Dispute File Data, and PICC File Trailer) as follows:4.3.1 PICC Dispute File HeaderThe first record in the file should have six 0s (Zeros) in the Company Contactfield. The Version Number will reside in the ACNA field. This would indicatethe beginning of the file.4.3.2
32、PICC Dispute File DataThe following fields are included in the data record: Company Contact, ContactNumber, ACNA, Billing Account Number, Invoice Date, PICC Extract Date, CIC,State, LATA, Jurisdiction, PICC Application Type Indicator, PICC CentrexIndicator, Telephone Number, Reason Code, Reason Text
33、, Disconnect Date,Notification Date, End Office CLLI, Circuit Number, Dispute Amount.4.3.3 PICC Trailer RecordThe trailer record identifies the data just processed. The CompanyContact field should have 6 9s (nines) populated to identify that therecord is a trailer record. In addition, the Telephone
34、Number field shouldbe populated with the total number of records included in this file(including Header and Trailer), the Dispute Amount field, should bepopulated with the total dispute amount for the file.CABS PDFSVersion 1 Page 5 November 1999APPENDIX A - OBF ISSUES INCLUDED IN PDFS REVISIONSThis
35、appendix contains a record of all resolved OBF Issues incorporated in revisionsto this document.OBFIssueDescription PDFS VersionNumberImplementation TimeFrame1675 PICC Dispute Procedures 1.0 mm/dd/yyyyCABS PDFSVersion 1 Page 6 November 1999APPENDIX B - FILE DATA ELEMENT DEFINITIONSThis appendix prov
36、ides the definitions of the data elements appearing in the PICCDispute File. This appendix does not provide the presentation order. Please seeAppendix C for the record layout. The source for most of the information below is thePICC Backup provided to the customers. Since certain PICC Backup informat
37、ion isconsidered optional, it may not have been originally provided. As previously stated,customers cannot be required to provide information they have not received. Theseelements are referenced under “appearance” as conditional.ACNAThe abbreviation of the PIC for that Telephone Number/Circuit Numbe
38、r that is beingdisputed.Data Attributes: AlphanumericLength: 5 positionsSource: CustomerAppearance: RequiredBILLING ACCOUNT NUMBERThe Billing Account Number of the bill that contained the PICC being disputed.Note: Billing Account Number is comprised of Billing Number and Customer Code forsome compan
39、ies.Data Attributes: AlphanumericLength: 13 positionsSource: Providers PICC Backup ReportsAppearance: RequiredCICThe Carrier Identification Code (CIC) associated with the Telephone Number/CircuitNumber that is being disputed.Data Attributes: NumericLength: 5 positionsSource: Providers PICC Backup Re
40、portsAppearance: RequiredCIRCUIT NUMBERThe Circuit Number associated with the PICC being disputed.Data Attributes: AlphanumericLength: 29 positionsCABS PDFSVersion 1 Page 7 November 1999Source: Providers PICC Backup ReportsAppearance: Conditional, when the format for service was originally provided
41、inCircuit Number rather than Telephone Number format.COMPANY CONTACTThe person that the provider should contact with questions and/or information aboutthis PICC Telephone Number/Circuit Number dispute.Data Attributes: AlphanumericLength: 30 positionsSource: CustomerAppearance: Required.CONTACT NUMBE
42、RThe number that the provider should contact with questions and/or informationabout this PICC Telephone Number/Circuit Number dispute.Data Attributes: NumericLength: 10 positionsSource: CustomerAppearance: RequiredDISPUTE AMOUNTThe amount of the dispute for the Telephone Number/Circuit for line leve
43、l disputes.Note: In the trailer record, this field will be the total of all line level dispute amounts.Data Attributes: Numeric with 2 decimalsLength: 11 positions, including 2 decimalsSource: CustomerAppearance: RequiredEND OFFICE CLLIThe CLLI Code for the End Office of the Telephone Number or Circ
44、uit NumberIdentifier.Data Attributes: AlphanumericLength: 11 positionsSource: Providers PICC Backup Reports.Appearance: Conditional - Required only when included in the PICC Backup reportsEND USER NOTIFICATION DATEThe date the PIC owner notified the end user that the Telephone Number or CircuitNumbe
45、r will be un-PICd.Data Attributes: Numeric (YYYYMMDD)CABS PDFSVersion 1 Page 8 November 1999Length: 8 positionsSource: CustomerAppearance: Conditional this field is only used if the dispute involves a carrierinitiated un-PIC TN or Circuit NumberHUNT GROUPEC designation for a hunt group.Data Attribut
46、es: NumericLength: 4 positionsSource: Provider PICC Backup ReportsAppearance: Conditional Only included when necessary and provided on the PICCBackup reports.INVOICE DATEThe Invoice Date for the Billing Account Number that contained the PICC beingdisputed.Data Attributes: Numeric (YYYYMMDD)Length: 8
47、 positionsSource: Providers PICC Backup ReportsAppearance: RequiredJURISDICTIONThe Jurisdiction of the PICC Charge for the Telephone Number/Circuit Number.Data Attributes: NumericLength: 1 positionsSource: Providers PICC Backup ReportsAppearance: RequiredLATAThe Local Access Transport Area (LATA) as
48、sociated with the PICC being disputed.Data Attributes: NumericLength: 3 positionsSource: Providers PICC Backup ReportsAppearance: Conditional. Required only when included in the PICC Backup reports.NUMBER OF CHANNELSThe number of channels associated with a specific telephone number.Data Attributes:
49、alphanumericLength: 4 positionsSource: Providers PICC Backup ReportsCABS PDFSVersion 1 Page 9 November 1999Appearance: Conditional. Required only when necessary and included in the PICCBackup reports.OUTGOING ONLY (OGO)The Outgoing Only Service identifier associated with a telephone number.Data Attributes: alphanumericLength: 4 positionsSource: Providers PICC Backup ReportsAppearance: Conditional. Required only when necessary and included in the PICCBackup reports.PICC APPLICATION T
