1、 IHS Additional Content Page Access to Additional Content for ATIS-0404130-0011- 2009 (Click here to view the publication) This Page is not part of the original publication: This page has been added by IHS as a convenience to the user in order to provide access to additional content as authorized by
2、 the Copyright holder of this document. Click the link(s) below to access the content and use normal procedures for downloading or opening the files. ATIS-0404130-0011 ZIP File Information contained in the above is the property of the Copyright holder and all Notice of Disclaimer however, the Custom
3、er may incur additional charges from the Provider for assembling the DLR(s). The Customer should forward their requests to the Providers DLR point of contact and each request will be handled on an Individual Case Basis (ICB) for charges and response time. 2.7 Requests to issue duplicate DLRs to the
4、same location or to multiple locations should be negotiated between the Customer and appropriate Provider. 2.8 This practice is reissued to clarify current definitions as recommended by users of this practice. Additions, deletions and significant changes are summarized in the synopsis of changes. 2.
5、9 The Design Layout Report Guideline does not convey licensing rights to non-COMMON LANGUAGE licensees to use the COMMON LANGUAGE code sets identified throughout the Design Layout Report Forms in their internal operations. Where COMMON LANGUAGE is provided, its intended use by non-COMMON LANGUAGE li
6、censees is limited. Allowable uses will be specified by the COMMON LANGUAGE licensee per their COMMON LANGUAGE contract. 2.10 Options described in this practice may not be applicable to individual provider tariffs; therefore, use of either the field or valid entries within the field is based on prov
7、ider tariffs/contracts/negotiations. _ COMMON LANGUAGE is a registered trademark and CLLI is a trademark of Telcordia Technologies, Inc. ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 3-1 3. DLR CONTENT AND FORMAT 3.1 The DLR document represents the i
8、nformation needed on the DLR and the actual field name, usage and data characteristics. 3.2 The DLR is divided into four forms with nine subdivided sections. 3.3 The DLR Administrative Form of the DLR is sent with each DLR and contains two sections: The Administrative section which includes: A. Cust
9、omer and Provider identification and contact B. Critical date information C. Issue date, issue number, page number and page range D. Remarks The Design section which includes: A. The service technical requirements B. Sequential listing The DLR sequential listing should contain the ID of the last ass
10、igned equipment or facility at the interface excluding any locally assigned tie pairs, e.g., HICAP CFA, Bay, Panel, Jack and Pin. 3.4 The DLR Additional Detail Form section of the DLR is an optional form based upon additional sequential listings being required to provide a complete document. This fo
11、rm is separated into two sections: The Administrative section provides a subset of the previous Administrative section, relating additional forms with the DLR Administrative Form as part of a complete DLR document. The Design section is a continuation of a sequential listing information presented on
12、 the DLR Administrative Form. ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 3-2 3.5 The DLR Additional Notes Form section of the DLR is optional, it is provided when the Note Indicator (N) field in the Design section has an entry(s). This page is sep
13、arated into two sections: The Administrative section provides a subset of the previous Administrative section, relating additional forms with the DLR Administrative Form as part of a complete DLR document. The Notes section provides details relative to an entry(s) in the Note Indicator field in the
14、Circuit Design section of the DLR. 3.6 These three forms (Administrative, Additional Detail, and Additional Notes) are the forms that could be utilized to provide a DLR for all services that terminate in a location that is identified by a CLLI Code. This would include terminations in a Provider Cent
15、ral Office, Centrex-like terminations, and Secondary ACTLs. 3.7 The End User Information section is utilized to provide specific address and termination information for those services that terminate in an end user premises. This section is separated into three sections: The Administrative section pr
16、ovides a subset of the previous Administrative section, relating additional forms with the DLR Administrative Form as part of a complete DLR document. The Primary Location section provides the end user specific address and termination information for the end users primary location on services provid
17、ed between two end user premises. (Ordered via the ASR utilizing the End User Special Access Form.) The Secondary Location section provides the end user specific address and termination information for the end users secondary location. (As reflected in the appropriate SECLOC field). ATIS-0404130-001
18、1 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-1 4. DESCRIPTIONS OF VALID FORM ENTRIES The DLR-ISI incorporates the following conventions for the population of form entries: Required - is defined as the field must be populated. Optional - is defined as the field ma
19、y or may not be populated by the provider. Prohibited - is defined as the field must not be populated. Conditional - is defined as the field is dependent upon the relationship to another entry as specified in the usage statement and is dependent upon the presence, absence or combination of other dat
20、a entries. ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-2 4.1 ADMINISTRATIVE AND ADDITIONAL DETAIL FORMS ENTRIES 4.1.1 ADMINISTRATIVE SECTION 1. IC - Interexchange Carrier/Access Customer Name Identifies the COMMON LANGUAGE IAC code of the custome
21、r or the customer name. NOTE 1: This information should be extracted from theCCNA field on the Access Service Request (ASR),unless indicated differently on the ASR. NOTE 2: For an occasional customer, who has not andprobably will not be assigned a CCNA; thisinformation should be extracted from the C
22、USTfield on the ASR. USAGE: This field is required. DATA CHARACTERISTICS: 25 alpha/numeric characters EXAMPLES: J O H N S O N C A R R I E R C O D E A B C ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-3 2. PON - Purchase Order Number Identifies the
23、Customers unique purchase order or requisitionnumber that authorizes the issuance of this request orsupplement. NOTE 1: This PON field entry must be identical to the PONfield entry on the ASR Form. NOTE 2: When multiple DLRs are issued in response to anASR, the PON will be identical on each DLR issu
24、ed. USAGE: This field is conditional. NOTE 1: Required when the DLR is in response to aCustomers ASR, otherwise optional. DATA CHARACTERISTICS: 16 alpha/numeric characters EXAMPLE: W 6 W W 1 2 3 4 5 6 7 8 6 9 0 1 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March
25、21, 2009 4-4 3. VER - Version Identification Identifies the Customers version of a PON number. NOTE 1: This will identify the Customer version of the ASRto which the DLR is responding. This does notimply that a DLR will be required for each versionof the Customers ASR. USAGE: This field is condition
26、al. NOTE 1: Required when the VER field is populated on theASR, otherwise prohibited. DATA CHARACTERISTICS: 2 alpha/numeric characters EXAMPLE: 2 A ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-5 4. ECIA - EC (Provider) Initiated Activity Identifie
27、s this DLR as a provider initiated document for whichthere is no associated customer request (ASR) at time of issuance. VALID ENTRIES: Y = Provider initiated activity X = Provider initiated network groom with ECCKT change Blank = ASR initiated activity USAGE: This field is conditional. NOTE 1: Requi
28、red when the DLR is for a provider initiatedactivity. DATA CHARACTERISTICS: 1 alpha character EXAMPLE: Y ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-6 5. PG - Page Number of Pages Identifies the particular page number of the DLR as well as thetot
29、al number of pages. USAGE: This field is required. DATA CHARACTERISTICS: 7 alpha/numeric characters EXAMPLE: PG D 0 0 1 of 0 0 6 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-7 6. CKR - Customer Circuit Reference Identifies the circuit number or ra
30、nge of circuit numbers beingused by the Customer. NOTE 1: CKR is used by the Customer as a cross-referenceto the Provider circuit ID(s) and in many cases toidentify the Customers end-to-end service. NOTE 2: CKR must be returned to the Customer and matchwhat was provided by the Customer to the Provid
31、eron the ASR. USAGE: This field is conditional. NOTE 1: Required when the CKR field on the ASR Form ispopulated, otherwise prohibited. DATA CHARACTERISTICS: 53 alpha/numeric characters CIRCUIT EXAMPLE: / F D D C / 1 2 3 4 5 6 / 0 0 1 / N Y FACILITY EXAMPLE: 1 1 4 / T 1 / N B W K N J N B W 0 1 / N W
32、R K N J 0 2 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-8 7. ISS - DLR Issue Date Identifies the Providers issue date of the DLR. VALID ENTRIES: U.S. Standard Metric Format Two Digit Month (01-12) Two Digit Century (00-99) Two Digit Day (01-31) T
33、wo Digit Year (00-99) Two Digit Century (00-99) Two Digit Month (01-12) Two Digit Year (00-99) Two Digit Day (01-31) USAGE: This field is required. DATA CHARACTERISTICS: 10 alpha/numeric characters (including 2 preprinted hyphens) EXAMPLES: 0 3 - 0 2 - 1 9 9 9 1 9 9 9 - 0 3 - 0 2 ATIS-0404130-0011 E
34、ffective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-9 8. CO - Provider Company Identifies the COMMON LANGUAGE Products IAC code orNECA code for the Provider company that prepared the DLR forthe affected access. VALID ENTRIES: Valid COMMON LANGUAGE Products code or a four a
35、lpha/numeric character code structure for all ExchangeCarriers in North America and certain U.S. territoriesmaintained by NECA. USAGE: This field is required. DATA CHARACTERISTICS: 4 alpha/numeric characters EXAMPLES: P A 1 2 A 3 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 I
36、mplemented March 21, 2009 4-10 9. ORD - Order Number Identifies the Providers service order number for the requestedservice. USAGE: This field is conditional. NOTE 1: Required if the DLR is in response to a CustomersASR, otherwise optional. DATA CHARACTERISTICS: 17 alpha/numeric characters EXAMPLE:
37、C 1 2 3 4 5 6 7 8 9 8 7 6 5 4 3 2 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-11 10. DLR _ OF _ - DLR _ of _ Identifies the particular DLR as well as the total number ofDLRs being issued. NOTE 1: The PON will be identical on each DLR when inrespo
38、nse to an ASR. USAGE: This field is required. DATA CHARACTERISTICS: 6 alpha/numeric characters EXAMPLE: D L R 0 1 0 of 1 2 0 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-12 11. ISS NO - Issue Number Identifies the Providers issue number of the DLR
39、. NOTE 1: For resend scenarios, the entry of this field will notchange. USAGE: This field is required. DATA CHARACTERISTICS: 2 numeric characters EXAMPLE: 0 2 ATIS-0404130-0011 Effective March 21, 2009 Issued September 26, 2008 Implemented March 21, 2009 4-13 12. ECCKT - Exchange Company Circuit ID
40、Identifies the Provider circuit ID. NOTE 1: This information is the same information found onthe ICSC Confirmation Notice in the ECCKT fieldfor new installations and on the ASR in the ECCKTfield for subsequent change requests, outsidemoves and changes in capacity to existing circuitgroups. NOTE 2: T
41、his field should match the ECCKT previouslyprovided on the firm order confirmation includingspaces and delimiters. NOTE 3: On DLRs for a multi-point circuit, the ECCKTshould also include the segment number for thegiven circuit segment. USAGE: This field is required. DATA CHARACTERISTICS: 53 alpha/numeric characters EXAMPLES: 3 2 / L G G S / 6 7 8 5 6 2 / N Z / 0 0 1 9 1 0 1 / T 1 / N Y C M N Y B W K Z Z / N Y C M N Y B S 0 2 A
