1、 ATIS-0404120-0010 Multiple Exchange Carriers Ordering and Design (MECOD) Guidelines for Access Service Version 10 ATIS-0404120-0010 Issued September 22, 2017 Implemented March 17, 2018 As a leading technology and solutions development organization, ATIS brings together the top global ICT companies
2、to advance the industrys most-pressing business priorities. Through ATIS committees and forums, nearly 200 companies address cloud services, device solutions, M2M communications, cyber security, ehealth, network evolution, quality of service, billing support, operations and more. These priorities fo
3、llow a fast-track development lifecyclefrom design and innovation through solutions that include standards, specifications, requirements, business use cases, software toolkits and interoperability testing. ATIS is accredited by the American National Standards Institute (ANSI). ATIS is the North Amer
4、ican Organizational Partner for the 3rdGeneration Partnership Project (3GPP), a founding Partner of oneM2M, a member and major U.S. contributor to the International Telecommunication Union (ITU) Radio and Telecommunications sectors, and a member of the Inter-American Telecommunication Commission (CI
5、TEL). For more information, visit www.atis.org. ATIS 0404120-0010 Multiple Exchange Carriers Ordering and Design (MECOD) Guidelines for Access Service Is an ATIS standard developed by the Ordering Solutions Committee - Access Service Ordering Subcommittee under the ATIS Ordering and Billing Forum (O
6、BF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2017 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system
7、 or otherwise, without the prior written permission of the publisher. For information contact ATIS at 202.628.6380. ATIS is online at . Limited Exception for “Customized” Forms. In recognition of the business needs and processes implemented by companies throughout the industry, ATIS grants the follo
8、wing limited exception to the copyright policy. The forms contained within, once “Customized,” may be reproduced, distributed and used by an individual or company provided that the following is placed on all “Customized” forms: “This form/screen is based upon the Ordering and Billing Forums (OBF) in
9、dustry consensus approved guidelines, found in the Access Service Ordering Guidelines (ASOG) document. The ASOG may be obtained by contacting the Alliance for Telecommunications Industry Solutions (ATIS) at 1-800-387-2199 or: https:/www.atis.org/atis/docstore/index.asp.” ATIS-0404120-0010 Issued Sep
10、tember 22, 2017 Implemented March 17, 2018 For purposes of this limited exception, the term “Customized” means, the modification, by a company, of an ASOG form to be issued to a trading partner to make it company specific by, for example, adding a company logo, graying-out optional fields not requir
11、ed by that specific issuing company, and converting into an electronic format/screen. This limited exception does not affect the ASOG document itself which remains copyrighted and may not be reproduced in whole or part. Telcordia Technologies, Inc. was formerly known as Bell Communications Research,
12、 Inc. or Bellcore. Portions of this document, previously published by Bellcore, may still reflect the former name as it was embedded in the documentation under a prior license from the owners of the BELL trademark, which license has now expired. The use of this name does not suggest that Telcordia T
13、echnologies has licensed the names BELL, Bell Communications Research, or Bellcore for new uses or that the owners of the BELL trademark sponsor, endorse or are affiliated with Telcordia Technologies or its products. Printed in the United States of America. Notice of Disclaimer and Limitation of Lia
14、bility 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 engineering or other professional standards and applicable regulations. No recommendation
15、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 FURTHER, NO REPRESENTATION OR WARRANTY IS MADE OF MERCHANTABILITY OR FITNESS FOR A
16、NY 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 EVENT SHALL ATIS BE LIABLE FOR LOST PROFITS OR OTHER INCIDENTAL OR CONSEQUENTIAL D
17、AMAGES. ATIS EXPRESSLY ADVISES ANY AND ALL USE OF OR RELIANCE UPON THIS INFORMATION PROVIDED IN THIS DOCUMENT IS AT THE RISK OF THE USER. ATIS-0404120-0010 Issued September 22, 2017 Implemented March 17, 2018 MULTIPLE EXCHANGE CARRIERS ORDERING AND DESIGN (MECOD) GUIDELINES FOR ACCESS SERVICE Table
18、of Contents 1 GENERAL . 1-1 2 ASSUMPTIONS 2-1 3 NEGOTIATION 3-1 4 ORDERING PREPARATION AND ISSUANCE 4-1 5 DESIGN 5-1 6 TSP PREEMPTION 6-1 7 INSTALLATION AND MAINTENANCE 7-1 8 COMPLETION . 8-1 9 BILLING 9-1 10 ADDITIONAL POST-INSTALLATION ACTIVITIES 10-1 11 EXHIBIT - ORDERING AND PROVISIONING FLOW CH
19、ART 11-1 11. EXHIBIT - ORDERING AND PROVISIONING FLOW CHART (CONT) . 11-2 ATIS-0404120-0010 Issued September 22, 2017 Implemented March 17, 2018 1-1 1 GENERAL 1.1 These guidelines establish methods for processing orders for access service which is to be provided to an Interexchange Carrier (IC) by t
20、wo or more Exchange Carriers (ECs). No wording in this document is intended to represent or imply that the involved Exchange Carriers (ECs) must serve separate and discrete geographic areas. These guidelines cover the ordering and design process from submission of an Access Service Request (ASR) thr
21、ough issuance of work documents, and are based on the concept of one of the involved ECs being placed in an access service coordination role. Additional information regarding the business rules can be found in Access Service Ordering Guidelines (ASOG), ATIS-0404000-0404028. The determination of impl
22、ementing a multiple Exchange Carrier ordering arrangement between ECs that operate in the same territory is based upon EC to EC negotiations where the regulatory environment permits. When all involved ECs agree to a multiple Exchange Carrier ordering arrangement, these guidelines are used. In an eff
23、ort to insure that all possible providers, users and customers of Access Services are addressed in all issues and documentation maintained by or on behalf of the Ordering and Billing Forum, two terms describing these providers, users and customers will be used, AC (Access Customer) and AP (Access Pr
24、ovider). Throughout this document, the term IC (Interexchange Carrier) covers activity associated with the Access Customer (AC) and EC (Exchange Carrier) covers activity associated with the Access Provider (AP). Their use, however, does not imply exclusivity within the AC and AP categories. 1.2 All
25、changes made to this document are reflected in the Summary of Change. 1.3 Coordination requirements of all ECs may not be fully covered in this document because each EC has varying views and needs regarding its relationship with Other Exchange Carriers (OECs). This document does however, provide a f
26、ramework for ordering and design requirements. All references in this document regarding Feature Group A (FGA) and/or Feature Groups B, C, and D (FGB, FGC, FGD) include the equivalent lineside Basic Service Arrangement (BSA) or the equivalent trunkside BSA, respectively. The guidelines in this docum
27、ent apply to an individual service provided by more than one EC. 1.4 An “Access Service Coordination” (ASC) concept will be utilized to provide the required coordination for each function, i.e., negotiation, design, installation and maintenance. These functions will have an EC designated to perform
28、the ASC role; that EC will be identified by the term ASC-EC and may be a different EC for each of the functions. The ASC concept provides for (1) a single EC point of contact/interface between the IC and the ECs and (2) a coordinator for the activities of the involved ECs. Before an ASR is issued by
29、 the IC for an access service involving multiple ECs, the ECs involved should have developed a mutually agreeable working arrangement to allow one or more of the ECs to perform “Access Service Coordination” (ASC) for all services requested. The ASC-EC concept as embodied in this document will be uti
30、lized regardless of the method of billing employed by the involved ECs. It will be the responsibility of each EC to work cooperatively with the IC and other ECs to ensure that access services are installed, tested and turned up in a timely manner and that trouble conditions are resolved without undu
31、e delay. The ASC for Meet Point Services may be determined by the following method when not specifically designated by the responsible providers per paragraph 1.6 and Section 12. Switched Access A. First point of switching for the service requested. ATIS-0404120-0010 Issued September 22, 2017 Implem
32、ented March 17, 2018 1-2 Special Access A. For multipoint, first point of bridging for the service requested B. Service Termination/Delivery Address (SECLOC) of the service requested C. For a multi-node Ring, it is the SECLOC of the first segment D. For circuits that ride a higher facility, the EC w
33、ithin whose territory the SECLOC resides would be designated as the ASC-EC. Switched Ethernet Access A. ENNI/NNI/UNI a. It is the service address or ACTL. B. EVC/OVC a. The RUID is an ENNI/NNI, otherwise it defaults to the first UNI. 1.5 The EC to EC arrangements should also include the parameters f
34、or the exchange of various data elements that will ensure accurate and verifiable billing as outlined in the Ordering and Billing Forums “Multiple Exchange Carrier Access Billing (MECAB) Guidelines.” 1.6 For greater clarity of the IC/EC relationship in a multiple EC environment, the OBF recommends t
35、hat the involved ECs, on a combined or individual basis, develop and furnish written notification to the ICs identifying by types of access services the ECs providing the ASC-EC function for negotiation, design, installation and maintenance, and the DLR distribution arrangement. 1.7 The ASC-EC will
36、provide the negotiation organization locations and the telephone numbers of the ASC-EC contact groups responsible for negotiations, design, installation and maintenance to the OECs. 1.8 In the event the ASC responsibilities are changed for any of the four phases of the process as a result of EC-to-E
37、C arrangements, notification as described in 1.6 and 1.7 should be provided within 30 days.ATIS-0404120-0010 Issued September 22, 2017 Implemented March 17, 2018 2-1 2 ASSUMPTIONS 2.1 The IC is responsible for distribution of a common/identical ASR to all known ECs between the Access Customer Termin
38、al Location (ACTL)/Primary Location (PRILOC) to Secondary Location (SECLOC)/Ethernet Service Point (ESP) involved with the access service for all activity types. For EVC/OVC services the IC is responsible for distribution of a common/identical ASR to all known ECs associated with the Related UNI Ide
39、ntifiers (RUIDs). If an access service is provided by more than one EC, the order will be processed as multi-EC. This includes ECs that provide that portion of the access service transiting between the ECs at either end of the overall access service. These access services comprise all Special and Sw
40、itched Access Services including those where the service between an IC POP and an EC Tandem switch is entirely provided by one EC and one or more End Offices subtending the Tandem belong to another EC. 2.2 In scenarios involving rings where the immediate riding circuit has one EC between the ACTL/PR
41、ILOC to SECLOC but cross connects are required on a jointly provided ring for protection, the IC is responsible for distribution of a common/identical ASR to all known ECs associated with the jointly provided ring. 2.3 The ASR will reflect the entire access service including associated options regar
42、dless of the number of ECs involved. 2.4 The ASR issued to the ECs involved should include identical information that meets the ASC-ECs business process requirements to provide overall service. All other ECs involved with providing the overall service will accept the ASR as submitted by the IC. When
43、 exceptions to this requirement are determined to be necessary, the ASC-EC should coordinate the resolution with the IC and ECs. 2.5 One of the ECs will assume the responsibility for performing the Access Service Coordination (ASC) role. This company will be identified as the ASC-EC while the other
44、involved ECs will be identified as OECs in this document. 2.6 The ASC-EC assignment(s) can vary both by types of service and by ECs involved. It will be locally determined by the involved ECs and will be made available to the IC prior to ASR issuance. 2.7 The ASC-EC function 1) may be performed by t
45、he same EC for the life of the access order; or 2) may vary through the stages of the order depending on local agreements; e.g., in some situations there may be one ASC for negotiation and one for the design state. 2.8 The ASC-EC will assume the lead coordination role to ensure that the access servi
46、ce provided satisfies what was ordered on the ASR. 2.9 The ASC-EC will establish the common circuit/facility identification for the access service and provide it to the IC and all involved ECs. For this to be a viable procedure, this assignment should conform to some standard. A long-term goal is to
47、 develop this standard (see note following). In the event that the ASC-EC is not presently using COMMON LANGUAGE1Codes for Circuit/Facility Identification (CLCI), and one or more of the OECs is using CLCI-SS, CLCI-MSG or CLFI, the ASC-EC will obtain a Circuit/Facility ID from one of the involved OEC
48、s using CLCI-SS, CLCI-MSG or CLFI and pass that Circuit/Facility ID back to the IC and all involved ECs. For the subsequent steps of design, installation and maintenance, the OECs (and ASC-EC when they obtain CLCI-SS, CLCI-MSG or CLFI from an OEC) are responsible for maintaining the relationship bet
49、ween their internal identification and the ASC-EC established access service circuit/facility identification. The previous discussion does not address the case where the ASC-EC and none of the OECs are using CLCI-SS, CLCI-MSG or CLFI. In this situation the involved ECs should work out a circuit/facility ID suitable 1COMMON LANGUAGE is a registered trademark and CLEI, CLLI, CLFI, and CLCI are trademarks of Telcordia Technologies. ATIS-0404120-0010 Issued September 22, 2017 Implemented March 17, 2018 2-2 to their respective requirements. It would be desirable to use some sc
