1、 ATIS-0401002-002 ORDERING AND BILLING FORUM (OBF) PICC DISPUTE FILE SPECIFICATIONS DOCUMENT ISSUE 2 DECEMBER 2005 ATIS is a technical planning and standards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and r
2、elated information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communications companies are active in ATIS 22 industry committees, and its Incubator Solutions Program. www.atis.orgATIS 0401002-002 Small Exchange Carrier Ac
3、cess Billing (SECAB) Guidelines Is an ATIS standard developed by the following committee(s) under the ATIS Ordering and Billing Functional Group: Ordering and Billing Forum Published by ATIS 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2005 by Alliance for Telecommunications Industry
4、Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Printed in the United States of America.
5、ATIS-0401002-002 Issued December 2005 Notice of Disclaimer and Limitation of Liability The information provided in this document is directed solely to professionals who have the appropriate degree of experience to understand and interpret its contents in accordance with generally accepted engineerin
6、g or other professional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUFFICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FU
7、RTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE OR AGAINST INFRINGEMENT OF INTELLECTUAL PROPERTY RIGHTS. ATIS SHALL NOT BE LIABLE, BEYOND THE AMOUNT OF ANY SUM RECEIVED IN PAYMENT BY ATIS FOR THIS DOCUMENT, WITH RESPECT TO ANY CLAIM, AND IN NO EV
8、ENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER CABS PDFS 1.0 PREFACE 1 2.0 GENERAL DESCRIPTION.2 2.1 SCOPE 2 2.2 DOCUMENT REVISION
9、S 2 2.3 RELATED OBF ISSUES .2 2.4 DATA ELEMENT REQUIREMENTS .2 3.0 PICC DISPUTE DATA.3 3.1 INTENT OF FILE 3 3.2 DISTRIBUTION3 3.3 PAPER DISPUTE NOTIFICATION 3 3.4 MECHANIZED FILE RECORDS.3 4.0 FILE REQUIREMENTS4 4.1 MECHANIZED FILE ORGANIZATION .4 4.2 MECHANIZED DATA FORMAT 4 4.3 MECHANIZED FILE REC
10、ORDS.4 4.3.1 PICC Dispute File Header4 4.3.2 PICC Dispute File Data4 4.3.3 PICC Trailer Record.4 APPENDIX A - OBF ISSUES INCLUDED IN PDFS REVISIONS.5 APPENDIX B - FILE DATA ELEMENT DEFINITIONS6 ACNA.6 BILLING ACCOUNT NUMBER 6 CIC6 CIRCUIT NUMBER 7 DISPUTE DESCRIPTION .7 DISPUTE REASON CODE .7 DISPUT
11、ED AMOUNT.7 CUSTOMER CONTACT NAME 7 CUSTOMER CONTACT PHONE.8 DISPUTED BILL DATE8 END OFFICE CLLI8 END USER NOTIFICATION DATE.8 HUNT GROUP.9 JURISDICTION .9 LATA9 NUMBER OF CHANNELS .9 OUTGOING ONLY (OGO) .9 PICC APPLICATION TYPE INDICATOR.10 PICC CENTREX INDICATOR10 PICC DISPUTED EXTRACT DATE.10 STA
12、TE10 TELEPHONE NUMBER (TN).10 TERMINAL NUMBER11 UN-PIC DATE .11 APPENDIX C - FILE LAYOUT12 APPENDIX D DISPUTE REASON CODES.13 Version 2 Page ii December 2005 CABS PDFS THIS PAGE INTENTIONALLY LEFT BLANK. Version 2 Page ii December 2005 CABS PDFS 1.0 PREFACE This document represents the Ordering and
13、Billing Forum (OBF) Billing Committee requirement to create a document of CABS PICC Dispute File Specifications (PDFS). These procedures were cooperatively developed in the OBF. They were written in response to OBF Issue 1675. All changes to this document must be presented to the OBF Billing Committ
14、ee and accepted by consensus. The OBF Billing Committee is responsible for the on-going maintenance and distribution of this document based on resolved issues. The OBF is a voluntary, self-policing group of participants who meet together to identify, discuss and resolve issues which are national in
15、scope, involving ordering and billing of access services. The OBF functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The Federal Communications Commission (FCC) authorized the CLC in a January 17, 1985 Memorandum Opin
16、ion and Order. Version 2 Page 1 December 2005 CABS PDFS 2.0 GENERAL DESCRIPTION 2.1 Scope The CABS PICC Dispute File Specifications (PDFS) are guidelines for providing standard mechanized file layouts for line level or circuit level PICC Disputes. Implementation of PDFS outputs such as timing and me
17、dia (CD-ROM, Diskette, e-mail, etc.) used to provide this information will be negotiated between the individual customers and providers. 2.2 Document Revisions The PDFS document will be updated as necessary based upon resolved OBF Issues as identified by the OBF Billing Committee. All text revisions
18、 will be identified by a “|” in the right margin. The “|” will be placed to the immediate right of each line of revised text. All revisions to this document will have version numbers and associated implementation time lines . 2.3 Related OBF Issues OBF issues incorporated into the PDFS document are
19、displayed as Appendix A of this document. 2.4 Data Element Requirements The data element requirements (including data attributes and other pertinent information) are documented within the text of each field defined in Appendix B. Version 2 Page 2 December 2005 CABS PDFS 3.0 PICC Dispute Data 3.1 Int
20、ent of File This file is intended to provide, per OBF Issue 1675, PICC Dispute Information, including all information needed to support and resolve the PICC dispute. 3.2 Distribution PDFS files are provided in support of a PICC dispute. As such, a PDFS file should be produced each time the customer
21、identifies a dispute situation. As negotiated between the individual customers and providers, these files may be sent separately for each processing center within a company, or provided on one file representing the entire company. Customers will distribute the delimited text file based on the notifi
22、cation process and timeline in accordance with individual customer and provider agreements. 3.3 Paper Dispute Notification While this document is intended to discuss the mechanized files in support of PICC disputes, it is recognized that both customers and providers may wish to have some type of pap
23、er notification of the dispute. Such notification may be sent as part of, or separately from, the mechanized file records. Paper notification is typically in the form of a letter that may contain certain high level information about the dispute (e.g., the type of PICC being disputed, associated amou
24、nt, and the cause of the dispute). The actual form and content is as negotiated between the customer and provider. 3.4 Mechanized File Records As per the resolution to OBF Issue 1675, the mechanized file is to be provided as a delimited text file. The delimited text file was chosen because it allows
25、 the receiver of the file to view and manipulate the data into most PC software applications (such as Microsoft Word or Microsoft Access. Expected delivery mediums include, but are not limited to: CD-ROM, Diskette, or e-mail. Both the customer and the provider should agree upon the specific delivery
26、 medium. Section 4 of this document further discusses the mechanized file records. Version 2 Page 3 December 2005 CABS PDFS 4.0 File Requirements 4.1 Mechanized File Organization Each file will contain PICC data in support of dispute(s). The data in each file will support a specific PICC dispute. Th
27、e data contained within a file should be presented in the same order as discussed in Appendices B and C of this document. 4.2 Mechanized Data Format The data format is a text-delimited file. The file should contain the data elements identified in Appendix B. See Appendix C for the layout of the deli
28、mited text file. 4.3 Mechanized File Records Each PICC data file is comprised of three sections (i.e., a PICC Dispute File Header, PICC Dispute File Data, and PICC File Trailer) as follows: 4.3.1 PICC Dispute File Header To indicate the beginning of a file, the first record should have six 0s (zeros
29、) in the first field and the Version Number of the PICC Dispute File Specifications document in the second field. (The Version Number should reflect the value and format of the “Issue Number” appearing on the Title Page of this document.) The remaining fields of the first record will be empty, repre
30、sented by a series of commas. 4.3.2 PICC Dispute File Data The dispute data fields are listed in Appendix B of this document. The Appendix includes the name and definition of the field as well as the data attributes, length of the field, and the appearance of the data. 4.3.3 PICC Trailer Record To i
31、ndicate the end of a file, the last record should have six 9s (nines) in the first field and the total number of records (including header and trailer) in the second field. The Disputed Amount field should be populated with the total disputed amount for the file. The remaining fields of the first re
32、cord will be empty, represented by a series of commas. Version 2 Page 4 December 2005 CABS PDFS APPENDIX A - OBF ISSUES INCLUDED IN PDFS REVISIONS This appendix contains a record of all resolved OBF Issues incorporated in revisions to this document. OBF Issue Description PDFS Version Number Implemen
33、tation Time Frame 1675 PICC Dispute Procedures 1 11/1999 2861 Billing Committee GTDD Normalization - Name 2 12/2005 2862 Billing Committee GTDD Normalization - Date 2 12/2005 2863 Billing Committee GTDD Normalization - Address 2 12/2005 Version 2 Page 5 December 2005 CABS PDFS APPENDIX B - FILE DATA
34、 ELEMENT DEFINITIONS This appendix provides the definitions of the data elements appearing in the PICC Dispute File. This appendix does not provide the presentation order. Please see Appendix C for the record layout. The source for most of the information below is the PICC Backup provided to the cus
35、tomers. Since certain PICC Backup information is considered optional, it may not have been originally provided. As previously stated, customers cannot be required to provide information they have not received. These elements are referenced under “appearance” as conditional. ACNA The abbreviation of
36、the Presubscribed Interexchange Carrier (PIC) for that Telephone Number/Circuit Number that is being disputed. Data Attributes: Alphanumeric Length: 5 positions Source: Customer Appearance: Required BILLING ACCOUNT NUMBER The Billing Account Number of the bill that contained the PICC being disputed.
37、 Note: Billing Account Number is comprised of Billing Number and Customer Code for some companies. Data Attributes: Alphanumeric Length: 13 positions Source: Providers PICC Backup Reports Appearance: Required CIC The Carrier Identification Code (CIC) associated with the Telephone Number/Circuit Numb
38、er that is being disputed. Data Attributes: Numeric Length: 5 positions Source: Providers PICC Backup Reports Appearance: Required Version 2 Page 6 December 2005 CABS PDFS CIRCUIT NUMBER The Circuit Number associated with the PICC being disputed. Data Attributes: Alphanumeric Length: 29 positions So
39、urce: Providers PICC Backup Reports Appearance: Conditional, when the format for service was originally provided in Circuit Number rather than Telephone Number format. DISPUTE DESCRIPTION Identifies the text of the reason code. Data Attributes: Alphanumeric Length: 30 positions Source: Appendix D of
40、 this document Appearance: Required DISPUTE REASON CODE Identifies the reason for the dispute. (Appendix D of this document for values). Data Attributes: Alphanumeric Length: 3 positions Source: Appendix D of this document Appearance: Required DISPUTED AMOUNT The amount of the dispute for the Teleph
41、one Number/Circuit for line level disputes. Note: In the trailer record, this field will be the total of all line level dispute amounts. Data Attributes: Numeric with 2 decimals Length: 11 positions, including 2 decimals Source: Customer Appearance: Required CUSTOMER CONTACT NAME The person that the
42、 provider should contact with questions and/or information about this dispute. Note: In a file header record, this field will contain six 0s (zeros). In a file trailer record, this field will contain six 9s (nines). Data Attributes: Alphanumeric Length: 30 positions Source: Customer Appearance: Requ
43、ired. Version 2 Page 7 December 2005 CABS PDFS CUSTOMER CONTACT PHONE The number that the provider should contact with questions and/or information about this dispute. Note: In a file header record, this field will contain the Version Number). In a file trailer record, this field will contain the to
44、tal number of records in the file (including header and trailer). Data Attributes: Numeric Length: 10 positions Source: Customer Appearance: Required DISPUTED BILL DATE The date of the bill on which the disputed charges appear. Data Attributes: Numeric (YYYYMMDD) Length: 8 positions Source: Provider
45、s PICC Backup Reports Appearance: Required END OFFICE CLLI The CLLI Code for the End Office of the Telephone Number or Circuit Number Identifier. Data Attributes: Alphanumeric Length: 11 positions Source: Providers PICC Backup Reports. Appearance: Conditional - Required only when included in the PIC
46、C Backup reports END USER NOTIFICATION DATE The date the PIC owner notified the end user that the Telephone Number or Circuit Number will be un-PICd. Data Attributes: Numeric (YYYYMMDD) Length: 8 positions Source: Customer Appearance: Conditional this field is only used if the dispute involves a car
47、rier initiated un-PIC TN or Circuit Number Version 2 Page 8 December 2005 CABS PDFS HUNT GROUP EC designation for a hunt group. Data Attributes: Numeric Length: 4 positions Source: Provider PICC Backup Reports Appearance: Conditional Only included when necessary and provided on the PICC Backup repor
48、ts. JURISDICTION The Jurisdiction of the PICC Charge for the Telephone Number/Circuit Number. Data Attributes: Numeric Length: 1 positions Source: Providers PICC Backup Reports Appearance: Required LATA The Local Access Transport Area (LATA) associated with the PICC being disputed. Data Attributes:
49、Numeric Length: 3 positions Source: Providers PICC Backup Reports Appearance: Conditional. Required only when included in the PICC Backup reports. NUMBER OF CHANNELS The number of channels associated with a specific telephone number. Data Attributes: alphanumeric Length: 4 positions Source: Providers PICC Backup Reports Appearance: Conditional. Required only when necessary and included in the PICC Backup reports. OUTGOING ONLY (OGO) The Outgoing Only Service identifier associated with a telephone number. Data Attributes: alphanumeric Length:
