ATIS 0404120-0009-2013 Multiple Exchange Carriers Ordering and Design (MECOD) Guidelines for Access Service (Version 9).pdf

1、 ATIS-0404120-0009 Multiple Exchange Carriers Ordering and Design (MECOD) Guidelines for Access Service Version 9 ATIS-0404120-0009 Effective March 15, 2014 Issued September 20, 2013 Implemented March 15, 2014 The Alliance for Telecommunication Industry Solutions (ATIS) is a technical planning and s

2、tandards development organization that is committed to rapidly developing and promoting technical and operations standards for the communications and related information technologies industry worldwide using a pragmatic, flexible and open approach. Over 1,100 participants from more than 350 communic

3、ations companies are active in ATIS 23 industry committees, and ATIS Incubator Solutions Program. ATIS 0404120-0009 Multiple Exchange Carriers Ordering and Design (MECOD) Guidelines for Access Service Is an ATIS standard developed by the Ordering Solutions Committee Access Service Ordering Subcommit

4、tee under the ATIS Ordering and Billing Forum (OBF) Published by Alliance for Telecommunications Industry Solutions 1200 G Street, NW, Suite 500 Washington, DC 20005 Copyright 2013 by Alliance for Telecommunications Industry Solutions All rights reserved. No part of this publication may be reproduce

5、d 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 . Limited Exception for “Customized” Forms. In recognition of the business needs and processes implemented by companie

6、s throughout the industry, ATIS grants the following 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: ATIS-0404120-0009 Effect

7、ive April 8, 2009 Issued April 8, 2009 Implemented April 8, 2009 “This form/screen is based upon the Ordering and Billing Forums (OBF) industry consensus approved guidelines, found in the Access Service Ordering Guidelines (ASOG) document. The ASOG may be obtained by contacting the Alliance for Tele

8、communications Industry Solutions (ATIS) at 1-800-387-2199 or: https:/www.atis.org/atis/docstore/index.asp.” 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 exam

9、ple, adding a company logo, graying-out optional fields not required 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 Tech

10、nologies, Inc. was formerly known as Bell Communications Research, 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 n

11、ow expired. The use of this name does not suggest that Telcordia Technologies 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 Un

12、ited States of America. 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 engineering or other pro

13、fessional standards and applicable regulations. No recommendation as to products or vendors is made or should be implied. ATIS-0404120-0009 Effective April 8, 2009 Issued April 8, 2009 Implemented April 8, 2009 NO REPRESENTATION OR WARRANTY IS MADE THAT THE INFORMATION IS TECHNICALLY ACCURATE OR SUF

14、FICIENT OR CONFORMS TO ANY STATUTE, GOVERNMENTAL RULE OR REGULATION, AND FURTHER, 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

15、 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 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. MECOD V

16、ERSION 9 SYNOPSIS OF CHANGES Page 1 of 2 MECOD VERSION 9 CHANGES - ISSUES INCLUDED IN THIS SYNOPSIS ISSUE NUMBER DESCRIPTION 3464 MECOD: Develop a more standardized provider to provider process for the communication of meet point information The following table depicts the type of change category de

17、finitions: TYPE OF CHANGE = CATEGORY DEFINITIONS NEW = Adding a new field REM = Removing an existing field FN = Field/Tag name change (e.g., EXEMPT REASON changed to ER) FORMAT = Field format change (e.g., moved to another section of the form, etc.) DEF = Definition change DEFN = Definition notes ad

18、dition, change, deletion VE = Valid entries addition, change, deletion VEN = Valid entry notes addition, change, deletion USE = Usage statement change USEN = Usage notes addition, change, deletion DC = Data characteristics change (e.g., change from numeric to alpha/numeric) DCL = Data characteristic

19、s length change DCN = Data characteristics note addition, change, deletion EX = Example addition, change, deletion EXN = Example notes addition, change, deletion FORM = Changes made to the ASR forms (i.e., additions, rearrangements, field length MECOD VERSION 9 SYNOPSIS OF CHANGES Page 2 of 2 The fo

20、llowing table depicts the type of change category definitions: TYPE OF CHANGE = CATEGORY DEFINITIONS changes or deletions of fields) GLOSSARY = Identifies changes within the glossary sections (i.e., additions or deletions of fields) TEXT = Identifies changes within the text of a section (i.e., addit

21、ions or deletions of fields) SYNOPSIS OF CHANGES ISSUE # Field/ Section Type Of Change Description of Change Field Length 3464 2.15 TEXT Updated Text to modify process for disconnect orders 3464 3.4.1 TEXT Removed EBD NOTES: ATIS-0404120-0009 Effective April 8, 2009 Issued April 8, 2009 Implemented

22、April 8, 2009 MULTIPLE EXCHANGE CARRIERS ORDERING AND DESIGN (MECOD) GUIDELINES FOR ACCESS SERVICE TABLE OF CONTENTS Section Page 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 MAINTENA

23、NCE _ 7-1 8. COMPLETION _ 8-1 9. BILLING _ 9-1 10. ADDITIONAL POST-INSTALLATION ACTIVITIES _ 10-1 11. EXHIBIT - ORDERING AND PROVISIONING FLOW CHART _ 11-1 12. EXHIBIT - ACCESS SERVICE COORDINATION (ASC-EC) PROCESS MATRIX _ 12-1 ATIS-0404120-0009 THIS PAGE INTENTIONALLY LEFT BLANK.1-1 ATIS-0404120-0

24、009 Effective April 8, 2009 Issued April 8, 2009 Implemented April 8, 2009 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 two or more Exchange Carriers (ECs). No wording in this document is intend

25、ed 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) through issuance of work documents. These guidelines are based on the concep

26、t of one of the involved ECs being placed in an access service coordination role. The determination of implementing 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 i

27、nvolved ECs agree to a multiple Exchange Carrier ordering arrangement, these guidelines are used. In an effort 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

28、 terms describing these providers, users and customers will be used, AC (Access Customer) and AP (Access Provider). 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 Acc

29、ess Provider (AP). Their use, however, does not imply exclusivity within the AC and AP categories. 1.2 All changes made to this document are reflected in the Summary of Change. 1-2 ATIS-0404120-0009 Effective March 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 1.3 Coordination requir

30、ements 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 framework for ordering and design requirements. All references in this document regarding Feat

31、ure 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 document apply to an individual service provided by more than one EC. 1.4 An “Access Service Coord

32、ination” (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 the ASC role; that EC will be identified by the term ASC-EC and may be a different EC for eac

33、h 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 the IC for an access service involving multiple ECs, the ECs involved should have developed

34、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 utilized regardless of the method of billing employed by the involved ECs. It will be the respon

35、sibility 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 undue delay. The ASC for Meet Point Services may be determined by the following method when not s

36、pecifically designated by the responsible providers per paragraph 1.6 and Section 12. A. First point of switching for the service requested B. First point of bridging for the service requested C. Service Termination/Delivery Address (SECLOC) of the service requested D. For circuits that will ride Jo

37、intly Provided Rings as an immediate service on the ring, the EC within whose territory the SECLOC resides would be designated as the ASC-EC 1-3 ATIS-0404120-0009 Effective April 8, 2009 Issued April 8, 2009 Implemented April 8, 2009 1.5 The EC to EC arrangements should also include the parameters f

38、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

39、hat, on a LATA-by-LATA basis, 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 arrange

40、ment. The ASC-EC process matrix is provided in Section 12 as an exhibit of how this may be done. 1.7 The ASC-EC will 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

41、.8 In the event the ASC responsibilities are changed for any of the four phases of the process as a result of EC-to-EC arrangements, notification as described in 1.6 and 1.7 should be provided within 30 days.1-4 ATIS-0404120-0009 THIS PAGE INTENTIONALLY LEFT BLANK.2-1 ATIS-0404120-0009 Effective Mar

42、ch 17, 2012 Issued September 23, 2011 Implemented March 17, 2012 2. ASSUMPTIONS 2.1 The IC is responsible for distribution of a common/identical ASR to all known ECs between the ACTL/PRILOC to SECLOC involved with the access service for all activity types. If an access service is provided by more th

43、an 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 Switched Access Services including those where the service betw

44、een 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/PRILOC to SECLOC but cross connects are required on a jointly p

45、rovided 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 regardless of the number of ECs involved. 2.4 The ASR issued to th

46、e 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 exceptions to this requirement are determined to be necessar

47、y, 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 involved ECs will be identified as OECs in this document. 2.6

48、 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-2 ATIS-0404120-0009 Effective April 8, 2009 Issued April 8, 2009 Implemented April 8, 2009 2.7 The ASC-EC function 1) may be performed by the same EC for the life of the access order; or 2) may vary through the stage