1、 Confidential | Copyright 2016 IHS Markit Ltd Access to Additional Content For: ATIS-0410002-0029, Dated: 09/2016 (Click here to view the publication) This Page is not part of the original publication This page has been added by IHS Markit as a convenience to the user in order to provide access to a
2、dditional content as authorized by 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-0410002-0029 Information contained in the above is the property of the Copyright holder and all Notice of Discla
3、imer however they resulted in no impact to the contents of this document: 3524, 3551, 3556, 3557, 3560, 3563 Global Changes Change all ASOG 53 to ASOG 54; Version 53 to Version 54; Issue 28 to Issue 29 Change ATIS document number from ATIS-0410002-0028 to ATIS-0410002-0029 Update Issue Date Other gr
4、ammatical and spelling corrections that do not impact the technical content of this document are not reflected in the Summary of Changes Text Removed references to DLR-MIS in Section 6.6.1.3 (Issue 3536) Updated References section to remove references to DLR-MIS and ASR Mechanized Interface Specific
5、ation (Issue 3536) Removed section 5.3.6 Retrieve Service Request Information by Provider. (Issue 3549) In Section 6.4.1.2 Added references to forms PIP and DIS (Issue 3549) In Section 6.5.1 Added clarifying language for when SUP field is required to be populated in a later resend of order (Issue 35
6、49) In Section 6.6.1.1 added clarifying language for when transmitting an ERROR Clarification Notification, removed the optional part for the CNR. The model change is making CNR required to be sent with the Errors when using the Error Clarification type. (Issue 3549) Removed the BAN Correction Notif
7、ication Section 6.6.1.4, updated subsequent section numbers (Issue 3549) Updated Section 6.6.1.4 (previously Section 6.6.1.5) section text description (Issue 3550) Table of Contents Updated to reflect new sections, re-numbered sections, and document re-pagination SUMMARY OF CHANGES ASOG V54 Page 2 o
8、f 2 UOM-ASR VOLUME II SUMMARY OF CHANGES FOR ASOG V54 Section # Issue # Model Object or Section Name Description of Change 6.4.1.2.1 3552 CONTACT Added the following new attributes: SITECON, SITECON_TEL, and SITECON_EMAIL. 6.4.1.3.3 3543 ECI_ASR_LEVEL Removed the following attributes: CHPD, PEND_ORD
9、 SM, SM2, SM3, SM4, SM5, SM6, SM7, QOPT, PCT, EASPEED, EA_TYPE, CONFIG_REMARKS, ACPON, ACAT 6.4.1.3.3 3543 ECI_CKT_LEVEL Removed the following attributes: TNT, VCCID, SOPTCON, SUBNET_MASK, TRM, VPN_NM, OPTCON, IPAI, IP_Address, ICID, EXDI, EGRESS, EAID, ASN 6.6.1.2 3543 ECI_CKT_LEVEL_RTN Removed th
10、e following attributes: ACCESSID, ACCESSORD, PORTID, PORTORD, VCORD, VCCID 6.6.1.2 3543 ECI_ASR_LEVEL_RTN Removed the following attributes: CHPD 6.6.1.1 3549 ERROR_CLARIFICATION_Type Modified the multiplicity of the CNR Class from 0 to 1 to make it required 6.6.1.4 3549 BAN_CORRECTION_Type Removed t
11、he BAN Correction Type Class Diagram 6.6.1 3549 ASR Notification Classes Removed the BAN_CORRECTION_Type 6.6 3550 CUSTOMER_NOTIFY_Type Removed the CUSTOMER_NOTIFY_Type Class from the Notification Classes Diagram 6.6.1.4 3550 JEOPARDY_NOTIFY_Type Removed the following attribute: CC 6.6.1.4 3550 Jeopa
12、rdy Notification Modified the multiplicity of the CNR Class from optional (“01”) to required 6.6.2 3550 Customer Notification Class Removed Customer Notification Class section 6.6.2.1 3550 Customer Jeopardy Notification Removed Customer Jeopardy Notification section ATIS-0410002-0029 UOM-ASR Volume
13、II Issued September 23, 2016 Issue 29 for ASOG v54 Page 6 Table of Contents CHANGE HISTORY 4 TABLE OF CONTENTS 6 1 UOM DOCUMENTATION 8 2 INTRODUCTION TO UOM-ASR VOLUME II 9 2.1 INTENDED AUDIENCE . 9 2.2 PURPOSE 9 2.3 SCOPE 9 2.4 DEVELOPMENT NOTE . 10 3 OVERVIEW OF UOM-ASR VOLUME II 10 3.1 ASSUMPTION
14、S OF THIS DOCUMENT. 10 3.2 STRUCTURE OF DOCUMENT . 11 3.3 OVERALL PROCESS DESCRIPTION 11 3.4 UOM-ASR HIGH LEVEL PROCESS OVERVIEW 11 4 UOM REQUIREMENTS SUMMARY . 12 4.1 BUSINESS REQUIREMENTS . 12 4.2 SYSTEM REQUIREMENTS . 12 4.3 SECURITY REQUIREMENTS: 12 4.4 MESSAGING REQUIREMENTS: . 13 4.5 USER PROF
15、ILE REQUIREMENTS . 14 4.6 REPORTING REQUIREMENTS 15 5 USE CASE REALIZATIONS USING SEQUENCE DIAGRAMS . 15 5.1 UOM PRE-ORDER USE CASES 15 5.1.1 Location Inquiry 16 5.1.2 Service Availability Inquiry . 17 5.1.3 CFA Inquiry 19 5.2 UOM SERVICE REQUEST USE CASES 20 5.2.1 Customer Provider Communication .
16、21 5.2.2 Multiple Exchange Carrier Communication . 34 5.3 UOM POST-CONFIRMATION USE CASES 52 5.3.1 Jeopardy Status . 53 5.3.2 Provider Initiated Jeopardy 53 5.3.3 Customer Initiated Jeopardy 55 5.3.4 Retrieve Service Request Information . 56 5.3.5 Retrieve Service Request Information by Customer . 5
17、6 5.3.6 Retrieve Service Request Information by Provider Error! Bookmark not defined. 5.3.7 Completion Notification 57 5.3.8 Design Notification . 58 6 INFORMATION MODEL 60 6.1 UOM-ASR HIGH LEVEL VIEW 60 6.2 INQUIRY REQUEST CLASSES 61 6.2.1 ASR Inquiry Request Classes . 62 6.3 INQUIRY RESPONSE CLASS
18、ES 67 6.3.1 ASR Inquiry Response Classes . 67 6.4 SERVICE REQUEST CLASSES . 71 6.4.1 ASR Service Request Classes 71 ATIS-0410002-0029 UOM-ASR Volume II Issued September 23, 2016 Issue 29 for ASOG v54 Page 7 6.4.2 Multiple Exchange Carrier Communication Request Classes . 112 6.5 SERVICE RESPONSE CLAS
19、SES . 115 6.5.1 ASR Service Response Classes . 116 6.5.2 Multiple Exchange Carrier Communication Response Classes 117 6.6 NOTIFICATION CLASSES . 120 6.6.1 ASR Notification Classes . 121 6.6.2 Customer Notification Class Error! Bookmark not defined. 6.6.3 Multiple Exchange Carrier Communication Notif
20、ication Classes 128 6.7 ACKNOWLEDGEMENT CLASSES 131 6.7.1 ASR Acknowledgement . 131 6.7.2 MEC Acknowledgement. 132 6.8 EXCEPTION RESPONSE CLASS . 132 7 BEHAVIOR MODEL 134 7.1 STATE AND ACTIVITY DIAGRAMS . 134 REFERENCES 137 APPENDIX A: MEET POINT COORDINATION PROCESS FLOW 138 ATIS-0410002-0029 UOM-A
21、SR Volume II Issued September 23, 2016 Issue 29 for ASOG v54 Page 8 1 UOM Documentation The document, Unified Ordering Model Volume II Analysis, (UOM-ASR Volume II) is part of a set of documents that provides an end-to-end structured systems engineering approach to perform the analysis related to un
22、ified ordering via electronic interfaces. This document provides the analysis of the detailed business and systems requirements for an ordering model. It describes the information model and the behavioral model with the intent that service providers, customers, and their vendors understand how the d
23、ata, business rules and systems rules work together with the behavior of the data and rules. Because of the level of complexities inherent in such an electronic ordering model, Unified Modeling Language (UML) tools by RationalRose and MyEclipse have been used to develop this volume. UOM-ASR Volume I
24、I utilizes UML for descriptive purposes and in some instances may not strictly adhere to existing UML specifications. The intent of Unified Ordering Model (UOM) is to develop a complete set of system documentation using an end-to-end structured methodology. The scope of UOM encompasses business requ
25、irements, analysis, design, and implementation. Logically, these components are defined within the UOM in four volumes. UOM-ASR Volume I - Business Requirements This document describes the business requirements. This volume includes a high-level overview of the three primary processes in ordering: p
26、re-ordering, service request, and post-confirmation activities. It also includes more detailed information in the use cases and activity diagrams. Two appendices include the data dictionary and the functional data matrix. The UOM-ASR Volume I is focused on ordering for access services only. As other
27、 services are added in the future, additional Volume I documents may be developed. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains the UOM-ASR Volume I document. UOM-ASR Volume II - Analysis This analysis document provides the logical view of the business requirem
28、ents stated in Volume I. The primary sections include the information model, sequence diagrams, and behavior model. Both the informational and behavioral models are described using the Unified Modeling Language (UML). UOM-ASR Volume II utilizes UML for descriptive purposes and in some instances may
29、not strictly adhere to existing UML specifications. The UML provides the notation used within Volume II. Because of the level of complexities inherent in such an electronic ordering model, unified modeling language tools (RationalRose and MyEclipse) have been used to develop this Volume II. Some add
30、itional requirements are included in Volume II in order to accommodate fundamental aspects of ordering services via electronic interexchange. Volume II is not specific to any particular technology or protocol. If additional Volume I documents are developed, this Volume II may need to be expanded to
31、address additional requirements. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume II. UOM-ASR Volume III - Design The logical view of the proposed resolution (model), created in the Analysis Phase, is translated into the language appropriate for the
32、selected implementation technology. The first technology selected is XML; therefore UOM-ASR Volume III includes appropriate XML schemas related to unified ordering. This document does not specify a particular protocol as it is assumed that the trading partners will determine the appropriate transpor
33、t protocol. It may be necessary to repeat the Design Phase when more than one implementation technology is selected. The OBF Ordering Solutions Committee/Access Service Ordering Subcommittee maintains UOM-ASR Volume III. UOM-ASR Volume IV - Implementation This document includes implementation specif
34、ications that must be addressed before the system specifications can be realized using the selected implementation technology. In addition, a sample Joint Implementation Agreement (JIA) may be included as an appendix for trading partners to use as a starting template. As with the Design Phase, the I
35、mplementation Phase may also have to be repeated in order to ATIS-0410002-0029 UOM-ASR Volume II Issued September 23, 2016 Issue 29 for ASOG v54 Page 9 provide support for multiple technologies. The OBF Ordering Solutions Committee maintains UOM-ASR Volume IV Generic Implementation Guideline. Unifie
36、d Model1. Business Requirements:-High Level Use Cases-Scenarios-Activity Diagrams-Data Element Definitions-Data/Presentation Requirements-Business Validation Rules2. Logical Analysis:-Informational Model-Behavioral Model-Sequence Diagrams-Class/Object Diagrams-State Diagrams-Traceability Matrix3. Te
37、chnical Standard:-Technology Specific- Interface Specification4. Implementation Guidelines-Design Choice Suggestions-Implementation ProfileOBF1. Business ProcessDefinition2. Analysis3. Design4. ImplementationProcessVolume IVolume IIVolume IIIVolume IVUOM Process and Document Development2 Introductio
38、n to UOM-ASR Volume II 2.1 Intended Audience The audience for this volume is the technical and software development staff of service providers and customers. The audience includes anyone who wishes to gain a better understanding of the interface between the customer and the provider, or between prov
39、iders, in the provisioning of Access Services. 2.2 Purpose The document is intended to assist providers and customers in the process of conducting the analysis phase of their development steps to realize an electronic, unified ordering system. 2.3 Scope UOM-ASR Volume II describes the detailed analy
40、sis of the informational and behavioral model within a Unified Ordering Model. In addition, it defines at a more detailed level of the business requirements and ATIS-0410002-0029 UOM-ASR Volume II Issued September 23, 2016 Issue 29 for ASOG v54 Page 10 systems requirements needed to conduct ordering
41、 activities efficiently over an electronic interface. This includes a blending of the pre-ordering, service request and post-confirmation activities. Specifically, UOM-ASR Volume II-Analysis describes access service ordering as defined in: UOM-ASR Volume I Access Service Ordering Guidelines (ASOG) M
42、ultiple Exchange Carriers Ordering and Design (MECOD) Design Layout Report (DLR) Guidelines for Access Service These business requirements are developed and maintained within the Ordering and Billing Forum (OBF) under the auspices of the Ordering Solutions Committee/Access Service Ordering Subcommit
43、tee. UOM-ASR Volume II Analysis contains both the Informational and Behavioral Models that provide the reader a broad understanding of Service Ordering. Specifically, each model provides a dimension to the overall process: Informational Model describes the data relationships. Behavioral Model descri
44、bes the data as it acts with stimuli/events over time. Both the Informational and Behavioral Models are described using the Unified Modeling Language (UML). The UML provides the notation used within UOM-ASR Volume II. Because of the level of complexities inherent in such an electronic ordering model
45、 unified modeling language tools (RationalRose and MyEclipse) have been used to develop this volume1. NOTE: A new UML tool has been chosen for updating class diagrams, starting with ASOG35. With the previous UML tool, one and only one associations displayed a 1 on the association line connecting cl
46、asses. With this new tool, the 1 is omitted. Any changed class diagrams (moving forward) will no longer display the 1. The absence of a multiplicity indicator on these association lines should be interpreted as one and only one multiplicity. 2.4 Development Note The UOM process is iterative in natur
47、e. Subsequent iterations of UOM-ASR Volume II - Analysis may expand the functionality or services supported by the model. 3 Overview of UOM-ASR Volume II 3.1 Assumptions of this Document UOM-ASR Volume II should be generic and not be technically or protocol specific. UOM-ASR Volume II Informational
48、and Behavioral models reflect the current parameters defined within the OBF business rules. UOM-ASR Volume II should be backward compatible, flexible, have reusability and add value. UOM-ASR Volume II is modeled using synchronous messaging; this is done simply for notation purposes, unless explicitl
49、y noted. The synchronous/asynchronous discussion may be revisited in UOM-ASR Volume III and UOM-ASR Volume IV. Validation rules and processes are generally left to the customer/provider back end systems. System acknowledgements are not explicitly defined within the sequence diagrams. 1The use of RationalRose and MyEclipse does not reflect a tool recommendation by either the authors or the associated Industry Forums. ATIS-0410002-0029 UOM-ASR Volume II Issued September 23, 2016 Issue 29 for ASOG v54 Page 11 3.2
