1、 NOTICE OF COPYRIGHT This is a copyright document and may not be copied or distributed in any form or manner without the permission of ISA. This copy of the document was made for the sole use of the person to whom ISA provided it and is subject to the restrictions stated in ISAs license to that pers
2、on. It may not be provided to any other person in print, electronic, or any other form. Violations of ISAs copyright will be prosecuted to the fullest extent of the law and may result in substantial civil and criminal penalties. AMERICAN NATIONAL STANDARD ANSI/ISA-95.00.07-2017 Enterprise-Control Sy
3、stem Integration Part 7: Alias Service Model Approved 28 September 2017 ANSI/ISA95.00.072017, Enterprise-Control System Integration Part 7: Alias Service Model ISBN: 978-1-945541-78-0 Copyright 2017 by ISA. All rights reserved. Not for resale. Printed in the United States of America. No part of this
4、 publication may be reproduced, stored in a retrieval system , or transmitted, in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), without the prior written permission of the Publisher. ISA 67 T.W. Alexander Drive P. O. Box 12277 Research Triangle Park, North
5、 Carolina 27709 USA 3 ANSI/ISA-95.00.07-2017 PREFACE This preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-95.07.01-2017. The standards referenced within this document may contain provisions which, through reference in this text, constit
6、ute requirements of this document. At the time of publication, the editions indicated were valid. All standards are subject to revision, and parties to agreements based on this document are encouraged to investigate the possibility of applying the most recent editions of the standards indicated with
7、in this document. Members of IEC and ISO maintain registers of currently valid International Standards. ANSI maintains registers of currently valid U.S. National Standards. This document has been prepared as part of the service of ISA, the International Society of Automation Society, toward a goal o
8、f uniformity in the field of instrumentation. To be of real value, this document should not be static but should be subject to periodic review. Toward this end, the Society welcomes all comments and criticisms and asks that they be addressed to the Secretary, Standards and Practices Board; ISA; 67 T
9、.W. Alexander Drive; P. O. Box 12277; Research Triangle Park, NC 27709; Telephone (919) 549-8411; Fax (919) 549-8288; E-mail: standardsisa.org. The ISA Standards and Practices Department is aware of the growing need for attention to the metric system of units in general, and the International System
10、 of Units (SI) in particular, in the preparation of instrumentation standards. The Department is further aware of the benefits to USA users of ISA standards of incorporating suitable references to the SI (and the metric system) in their business and professional dealings with other countries. Toward
11、 this end, this Department will endeavor to introduce SI-acceptable metric units in all new and revised standards, recommended practices, and technical reports to the greatest extent possible. Standard for Use of the International System of Units (SI): The Modern Metric System, published by the Amer
12、ican Society for Testing certifies industry professionals; provides education and training; publishes books and technical articles; hosts conferences and exhibits; and provides networking and career development programs for its 40,000 members and 400,000 customers around the world. ISA owns A, a lea
13、ding online publisher of automation-related content, and is the founding sponsor of The Automation Federation (www.automationfederation.org), an association of non-profit organizations serving as “The Voice of Automation.“ Through a wholly owned subsidiary, ISA bridges the gap between standards and
14、their implementation with the ISA Security Compliance Institute (www.isasecure.org) and the ISA Wireless Compliance Institute (www.isa100wci.org). This standard was approved by the ISA Standards and Practices Board on 18 August 2017. 5 ANSI/ISA-95.00.07-2017 CONTENTS FOREWORD .9 INTRODUCTION . 11 1
15、SCOPE . 13 2 REFERENCES 13 3 DEFINITIONS, ABBREVIATIONS, AND CONVENTIONS . 13 3.1 Terms and definitions 13 3.2 Abbreviations . 14 3.3 Conventions . 14 4 IDENTIFYING OBJECTS AND ENUMERATIONS IN DATA EXCHANGES . 14 4.1 Converting data element IDs 14 4.2 Principle item . 15 4.3 Identifier categories .
16、15 4.4 Alias directory use . 15 4.5 Item predicate rules . 16 5 ALIAS DIRECTORY OBJECT MODEL . 16 5.1 Alias directory model . 16 5.2 Alias directory elements . 17 5.3 Category 18 5.4 Principle item . 19 5.5 Principle item property . 19 5.6 Namespace 20 5.7 Namespace item 20 5.8 Namespace item proper
17、ty 22 5.9 Predicate . 22 5.10 Predicate item property 24 6 ALIAS SERVICES . 24 6.1 Alias service elements . 24 6.2 Security . 24 6.3 ASM service type definitions 25 6.4 ASM service returns and faults 25 6.5 ASM mapping services 26 7 ALIAS DIRECTORY MODEL TRANSACTIONS 35 7.1 Alias directory elements
18、. 35 7.2 Alias directory verbs 36 7.3 Alias directory verb actions 37 ANSI/ISA-95.00.07-2017 6 8 COMPLETENESS, COMPLIANCE AND CONFORMANCE. 37 8.1 Completeness 37 8.2 Compliance 37 8.3 Conformance . 38 ANNEX A (NORMATIVE) RECOMMENDED VALUE PROPERTIES . 39 1. ParentIdentifierID . 39 2. ChildIdentifier
19、ID . 39 3. PossibleEquivalentIdentifierID . 39 4. EffectiveStartDate 39 5. EffectiveEndDate . 39 ANNEX B (NORMATIVE) STANDARD AND RECOMMENDED CATEGORIES. 41 ANNEX C USE SCENARIOS 47 ANNEX D FAQ . 53 7 ANSI/ISA-95.00.07-2017 Figures Figure 1 Steps in application-to-application communication 12 Figure
20、 2 Specifications in application-to-application communication . 16 Figure 3 Alias directory model 17 Figure 4 Object grouping for the alias directory model 36 Figure 5 ASM simple example using services . 47 Figure 6 ASM simple example using messages 48 Figure 7 ASM cache example using services 49 Fi
21、gure 8 ASM cache example using messages . 50 Figure 9 ASM multiple methods 51 Tables Table 1 Attributes of alias directory 18 Table 2 Attributes of category . 18 Table 3 Attributes of principle item . 19 Table 4 Attributes of principle item property 19 Table 5 Attributes of namespace 20 Table 6 Rela
22、tionships of namespace item . 21 Table 7 Attributes of namespace item . 21 Table 8 Attributes of namespace item property . 22 Table 9 Relationships of predicate 23 Table 10 Attributes of predicate 23 Table 11 Attributes of Predicate item property 24 Table 12 ASM type definitions 25 Table 13 ASM serv
23、ice returns and fault definitions . 25 Table 14 Get namespace IDs . 26 Table 15 Get principle IDs 27 Table 16 Get equivalent IDs . 28 Table 17 Get item predicates 29 Table 18 Set item predicates 30 Table 19 Get alias directory information . 31 Table 20 Get alias directory information rules . 31 Tabl
24、e 21 Set namespace items . 33 Table 22 Set principle items . 34 Table 23 Set equivalent identifiers 35 Table 24 Alias directory verb actions 37 Table 25 Supported services and verb/noun transactions . 38 Table 26 Standard category names for enumerations . 41 Table 27 - Categories for object classes
25、and property . 43 This page intentionally left blank. 9 ANSI/ISA-95.00.07-2017 ENTERPRISE-CONTROL SYSTEM INTEGRATION Part 7: Alias Service Model FOREWORD ISA-95 is a series of standards that defines enterprise to control system integration. This standard, Part 7 in the series, defines an alias servi
26、ce model (ASM) that includes a set of services and exchange information used to map identifiers from one applications or systems identifier namespace to another applications or systems identifier namespace. Clause 4 is normative. It defines the general service model and functions of the ASM services
27、. Clause 5 is normative. It defines the ASM object model. Clause 6 is normative. It defines the ASM services. Clause 7 is normative. It defines the ASM transactions. Clause 8 is normative. It defines conformance points for compliance. Annex A is normative. It provides property values. Annex B is nor
28、mative. It provides category names. Annex C is informative. It provides example of use of the ASM. Annex D is informative. It provides answers to frequently asked questions. As currently envisioned, the ISA95 series consists of the following standards under the general title Enterprise-Control Syste
29、m Integration: - Part 1: Models and terminology - Part 2: Objects and attributes for enterprise-control system integration - Part 3: Activity models of manufacturing operations management - Part 4: Object models and attributes of manufacturing operations management - Part 5: Business to manufacturin
30、g transactions - Part 6: Messaging service model (MSM) - Part 7: Alias service model (ASM) This page intentionally left blank. 11 ANSI/ISA-95.00.07-2017 INTRODUCTION This ISA-95 Part 7 standard is based on the use of ISA-95 object models defined in Parts 2, 4 and 5 (Parts 1 and 3 do not contain obje
31、ct models) to define a set of services that may be used to facilitate the mapping of identifiable elements between communicating applications. Applications may have, and often do have, different identifications for the same objects. In any exchange all parties to the exchange must agree on the names
32、 or identifiers of the objects. Often this agreement is managed through a set of alias identification registration services. This standard defines an alias service model (ASM) and formal object model for translating context in information exchanges. This standard defines a simple implementation appr
33、oach to a subset of the much broader issue that is addressed by ISO/IEC 11179 Information technology Metadata registries (MDR) and ISO/IEC 19763 Information technology Metamodel framework for interoperability (MFI). This standard enables the use of existing ontology mapping standards (e.g., OWL / RD
34、F. topic maps) as part of the contextualization of objects in the exchange and new standards as they are developed as part of the predicate definition between items. This standard provides for the exchange of the semantic mapping information as well as format information. The specific grammar and me
35、chanisms used to express the context in these standards is not part of the scope of this standard. All references to levels in this standard pertain to the levels of the function hierarchy model identified in the ISA-95 Part 1 standard. This standard defines a set of services definitions that are de
36、signed to provide the functionality needed for a vendor independent method for translating identifiers across different namespaces. Using a common representation of objects, such as enumeration strings, property names, and equipment tag names, is an important element of any integrated system. Enterp
37、rise/Control system integration involves multiple different steps to exchange data between different computer system applications, as shown in Figure 1. a) The applications usually have different internal representations of exchanged objects in their own local data stores. In an exchange, this repre
38、sentation is converted from the local format to a commonly accepted global format. The ISA-95 Part 2 standard defines representations of a global format for Level 4-3 data exchanges. The Part 4 standard defines representations of a global format for Level 3-3 data exchanges. b) Any object identifica
39、tion and enumeration which needs to be exchanged and is not the same on all systems can be converted from a local namespace to a principle namespace (step 3 in the figure) and the principle namespace to the local namespace (step 7 in the figure). This standard defines a minimal set of services and m
40、essage rules which can be used to translate local to principle and principle to local identifiers. Example 1 Assume two applications, ALPHA and BETA, the ALPHA application initiates a data exchange with the BETA application, and BETA responds back to ALPHA. The format conversions are: 1. ALPHAs loca
41、l format is converted to a global format for the request data. 2. Local items in ALPHA are mapped into a principle (global) items namespace. 3. The message is sent from ALPHA to BETA. 4. Upon receipt of the message, BETA must map the principle (global) items into BETAs item namespace. 5. The global
42、format must be converted to BETAs local format for the request data. 6. If there is any response required, then the process is reversed. Example 2 IDs for identified elements may be status codes, tag names, or equipment identifiers. Example 3 Data which is represented in one element namespace, such
43、as codes 1,2,3,4 may have a different namespace representation in another application, such as codes Ok, Done, Error, Delay. ANSI/ISA-95.00.07-2017 12 c) Messages are transported from one application to another, either within the same computer environment or across computers. Transport mechanisms ar
44、e defined in other standards, such as TCP/IP and Ethernet standards. The Part 6 standard defines a set of message services for the exchange of messages between applications. d) When data exchange information is received, there are specific rules that define what resultant data is to be returned. The
45、 transaction rules are defined in the Part 5 standard (step 10 in the figure). Figure 1 Steps in application-to-application communication This standard does not specify what technology an underlying system would use to implement the Alias services. Possible implementations include web services using
46、 a SOAP (Simple Object Access Protocol) interface, an HTTP/HTTPS implementation using a REST (Representational State Transfer) interface, or an API defined interface. This part defines the basic services with the assumption that specific technology implementations will be defined in companion specif
47、ications. A pp l i c a ti o n B E T AA pp l i c a ti o n A LP HAC o n v e r t l o c a lf o r m a t t o g l o b a l f o r m a tC o n v e r t l o c a li t e m se m a n t i cs t o pr i nc i pl e i t e m se m a n t i csS e n d i n f o r m a t i o n t o e x ch a n g e se r v i ceI n f o r m a t i o ne x
48、ch a n g e se r v i ce sC o l l e ct l o c a l i n f o r m a t i o nC o n v e r t g l o b a l f o r m a t t o l o c a l f o r m a tC o n v e r t pri nc i pl e i t e mse m a n t i cs t o l o c a li t e m se m a n t i csR e ce i v e i n f o r m a t i o n f r o m e x ch a n g e se r v i ceS a v e “My n
49、ame” EXAMPLE 3 An item that is used in an environment that has multiple namespaces has the namespace added to the ensure the item is unique; “My namespace/My name” EXAMPLE 4 An item that is used across directories (as global id) is represented by the fully qualified namespace item; “My directory/My category/My namespace/My name” NOTE The separator format for a fully qualified namespace is expressed with the “/” separator as defined in IETF (https:/t
