ANSI ISA 95.00.06-2014 Enterprise- Part 6 Messaging Service Model.pdf

《ANSI ISA 95.00.06-2014 Enterprise- Part 6 Messaging Service Model.pdf》由会员分享，可在线阅读，更多相关《ANSI ISA 95.00.06-2014 Enterprise- Part 6 Messaging Service Model.pdf（66页珍藏版）》请在麦多课文档分享上搜索。

1、 AMERICAN NATIONAL STANDARD ANSI/ISA95.00.062014 Enterprise- Part 6: Messaging Service Model Approved 10 November 2014 ANSI/ISA95.00.062014, Enterprise-Contro Messaging Service Model ISBN: 978-1-941546-26-0 Copyright 2014 by ISA. All rights reserved. Not for resale. Printed in the United States of A

2、merica. No part of this 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 Alexander Drive P. O. Box 12277 Research Tri

3、angle Park, North Carolina 27709 USA 3 ANSI/ISA-95.00.06-2014 PREFACE This preface, as well as all footnotes and annexes, is included for information purposes and is not part of ANSI/ISA-95.06.01-2014. The standards referenced within this document may contain provisions which, through reference in t

4、his text, constitute 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 standar

5、ds indicated within 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

6、, toward a goal of 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

7、 Board; ISA; 67 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 Internat

8、ional System 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 count

9、ries. Toward 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

10、 by the American Society for Testing as president of the American Automatic Control Council (AACC) from 1965 to 1967; as president of ISA in 1969; and as the first chairman of the IFAC/IFIP Task Force on Architectures for Integrating Manufacturing Activities and Enterprises from 1990 to 1996. Dr. Wi

11、lliams was awarded the Sir Harold Hartley Silver Medal by the Institute of Measurement and Control in London, England in 1976, and the A. F. Sperry Founder Award Gold Medal by ISA in 1990. This page intentionally left blank. 7 ANSI/ISA-95.00.06-2014 CONTENTS FOREWORD . 11 INTRODUCTION . 13 1 SCOPE .

12、 15 2 REFERENCES 15 3 DEFINITIONS AND ABBREVIATIONS . 15 3.1 Terms and definitions 15 3.2 Abbreviations . 16 3.3 Conventions . 17 4 THE MESSAGING SERVICE MODEL 17 4.1 Interface model 17 4.2 Application to application data exchange . 17 4.3 Transaction model . 19 4.4 Communicating applications 19 4.5

13、 Managed communication channels 20 4.6 Notification services . 21 4.7 MSM channel services . 21 4.8 MSM publication channel services . 22 4.9 MSM request channel services 23 5 METHODS OF OPERATION OF MSM CHANNELS . 24 5.1 Channel and topic identification . 24 5.2 Channel names and hierarchy 24 5.3 M

14、essage filtering . 26 5.4 Publication expiration. 26 5.5 Topics 27 5.6 MSM sessions . 27 5.7 Security . 28 6 MSM SERVICE DEFINITIONS 30 6.1 Type definitions . 30 6.2 MSM service returns and faults 31 6.3 MSM channel management services 32 6.4 Notify listener service 35 6.5 MSM provider publication s

15、ervices . 35 6.6 MSM consumer publication services 37 6.7 MSM provider request services 39 6.8 MSM consumer request services . 42 ANSI/ISA-95.00.06-2014 8 7 SCENARIOS . 45 7.1 Publish-subscribe scenarios 45 7.2 Request channel scenarios 50 8 COMPLIANCE . 53 ANNEX A (INFORMATIVE) MSM SERVICE PROVIDER

16、 CONSIDERATIONS 55 A.1 Service provider considerations . 55 A.2 Notification 55 A.3 Security considerations 55 A.4 MSM application implementation considerations 55 A.5 MSM channel security considerations 55 A.6 MSM session ID considerations . 55 A.7 Data format validation 56 A.8 Allowed application

17、checking . 56 A.9 Data exchange logging 56 A.10 Common error handling . 56 A.11 Data transformation services . 56 A.12 Cross company bridges . 57 A.13 Message maintenance . 59 ANNEX B (INFORMATIVE) ENTERPRISE SERVICE BUSES 61 ANNEX C (INFORMATIVE) BIBLIOGRAPHY . 63 9 ANSI/ISA-95.00.06-2014 Figures F

18、igure 1 Steps in application-to-application communication 14 Figure 2 Application communication stack 18 Figure 3 Defined standards at each level 19 Figure 4 Messaging service model names 20 Figure 5 MSM channel management services . 22 Figure 6 MSM publication channel services 22 Figure 7 Services

19、for request/response 23 Figure 8 Changes and checkpoint channel example . 26 Figure 9 Security of channels . 28 Figure 10 Publication scenario with notification 45 Figure 11 Publication scenario with multiple messages . 46 Figure 12 Publication scenario without notification 47 Figure 13 Publication

20、scenario with multiple provider applications 48 Figure 14 Publication scenario with expired publications 49 Figure 15 GET/SHOW request service scenario . 50 Figure 16 CHANGE / RESPONSE request service scenario 51 Figure 17 Multiple providers CHANGE/RESPONSE scenario 52 Figure 18 Transformation servi

21、ces with the MSM service provider 57 Figure 19 Cross company bridge between multiple MSMs 58 Figure 20 Standard interface to ESBs and other message exchange systems . 62 Tables Table 1 - MSM type definitions 30 Table 2 - MSM service returns and fault definitions . 31 Table 3 - Create channel . 32 Ta

22、ble 4 Add security token . 32 Table 5 Remove security token . 33 Table 6 Delete channel . 33 Table 7 Get channel . 34 Table 8 Get channels . 34 Table 9 Notify listener . 35 Table 10 Open publication session . 35 Table 11 Post publication . 36 Table 12 Expire publication 36 ANSI/ISA-95.00.06-2014 10

23、Table 13 Close publication session . 37 Table 14 Open subscription session . 37 Table 15 Read publication 38 Table 16 Remove publication 38 Table 17 Close subscription session . 39 Table 18 Open provider request session . 39 Table 19 Read request . 40 Table 20 Remove request . 40 Table 21 Post respo

24、nse 41 Table 22 Close provider request session 41 Table 23 Open consumer request session 42 Table 24 Post request 42 Table 25 Read response . 43 Table 26 Remove response 43 Table 27 Close consumer request session 44 11 ANSI/ISA-95.00.06-2014 Enterprise-Control System Integration Part 6: Messaging Se

25、rvice Model FOREWORD ISA-95 is a multi-part series of standards that defines enterprise to control system integration. This Part 6 standard defines a set of services (Messaging Service Model MSM) used to interface business and manufacturing activities. Clause 4 is normative. It defines the general s

26、ervice model and functions of the MSM services. Clause 5 is normative. It defines the methods of operation of MSM channels, topics, and security. Clause 6 is normative. It defines the MSM service definitions. Clause 7 is informative. It illustrates scenarios for use of the MSM services. Clause 8 is

27、normative. It defines compliance. Annex A is informative. It provides considerations for (MSM) service providers. Annex B is informative. It provides a brief description of Enterprise Service Buses as a message exchange mechanism. Annex C is a bibliography. The ISA-95 series consists of the followin

28、g standards under the general title Enterprise-Control System Integration: Part 1: Models and Terminology Part 2: Object Models and Attributes Part 3: Activity Models of Manufacturing Operations Management Part 4: Object Models and Attributes of Manufacturing Operations Management Part 5: Business-t

29、o-Manufacturing Transactions Part 6: Messaging Service Model For more information on the ISA-95 series of standards, visit www.isa.org/standards. This page intentionally left blank. 13 ANSI/ISA-95.00.06-2014 INTRODUCTION This ISA-95 Part 6 standard is based on the use of ISA-95 object models defined

30、 in ISA-95 Parts 2, 4 and 5 (Parts 1 and 3 do not contain object models) to define a set of services that may be used to exchange information messages. It is recognized that other, non-Part 6 sets of services are possible and are not deemed invalid as a result of this standard. This Part 6 standard

31、defines a Messaging Service Model (MSM) for exchanging data exchange messages in a publish/subscribe mode and a request/response mode. It defines a minimal interface s ubset to message exchange systems. The Messaging Service Model provides a method for applications to send and receive messages from

32、MSM service providers without regard to the underlying communication mechanism, as part of a complete application-to-application communication protocol. This Part 6 standard defines a set of services definitions that are designed to provide the functionality needed for a vendor-independent method fo

33、r sending and receiving data exchange messages on a message exchange system, such as an Enterprise Service Bus (ESB). The knowledge requirements to interface to just one message exchange system can be immense, and are usually not transferable to a different system. MSM defines a single interface, in

34、dependent of the underlying services, for Level 3-3 and Level 4-3 communications. This removes the need for vendors to build custom interface after custom interface, and for end users to get locked into a single vendor because their investment prevents them from reusing any of the integration effort

35、s. Enterprise-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. This representati

36、on is usually 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. This conversion, from l

37、ocal to global and global to local, is usually performed twice for any two-way communications. 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: AL HA c f b f f h

38、qu d , b f BETA c format for the requ d , BETA c f b f f h p d , d b f AL HA f f h p d . b) Conversion must be performed to align the namespaces among the exchanging applications, and is usually performed four times for any two-way communications. EXAMPLE 2 Names for elements of data may be codes, t

39、ag names, or equipment identifiers. EXAMPLE 3 Data which are represented in one element namespace, such as codes 1,2,3,4, may have a different namespace in another application, such as codes Ok, Done, Error, Delay. c) Once information is in the global format with appropriate global names, the exchan

40、ged information is sent from one application to another application. d) Messages are transported from one application to another, either within the same computer environment or across computers. Transport mechanisms are defined in other standards, such as TCP/IP and Ethernet standards. e) When data

41、exchange information is received, there are specific rules that define what resultant data are to be returned. The transaction rules are defined in the ISA-95 Part 5 standard. ANSI/ISA-95.00.06-2014 14 Figure 1 Steps in application-to-application communication 15 ANSI/ISA-95.00.06-2014 Enterprise-Co

42、ntrol System Integration Part 6: Messaging Service Model 1 Scope This part of ISA-95 defines a model of a set of messaging services for information exchanges across Levels 3 and 4, and within Level 3, between applications performing business and manufacturing activities. This standard defines a stan

43、dard interface for information exchange between systems. 2 References 1 ANSI/ISA-95.00.01-2010 (IEC 62264-1 Mod), Enterprise-Control System Integration Part 1: Models and Terminology 2 ANSI/ISA-95.00.02-2010 (IEC 62264-2 Mod), Enterprise-Control System Integration Part 2: Object Model Attributes 3 A

44、NSI/ISA-95.00.04-2012, Enterprise-Control System Integration Part 4: Objects and Attributes for Manufacturing Operations Management Integration 4 ANSI/ISA-95.00.05-2013, Enterprise-Control System Integration Part 5: Business-to-Manufacturing Transactions 3 Definitions and abbreviations 3.1 Terms and

45、 definitions 3.1.1 channel description text that describes a channel 3.1.2 channel type primary use of a channel for publications or requests 3.1.3 channel URI primary identifier for a channel 3.1.4 filter expression filtering element that may be applied to messages on a channel 3.1.5 listener ident

46、ification implementation defined element that is used to indicate to an application when a new message has arrived 3.1.6 message content body of the message 3.1.7 message expiry duration until the expiration of a publication message on a publication channel ANSI/ISA-95.00.06-2014 16 3.1.8 message ID

47、 identifier generated upon posting of a message to a channel in a session 3.1.9 namespace collection of names or words that define a formal and distinct set 3.1.10 security token physical device or software code used to gain access to a channel 3.1.11 session ID identifier generated upon an applicat

48、ion creating a session on a channel and provided to the application for use in the MSM services 3.1.12 topic identification of the information content in a message 3.2 Abbreviations B2MML Business to Manufacturing Markup Language CB (radio) C z Band radio CCOM-ML Common Conceptual Object Model Marku

49、p Language ERP Enterprise Resource Planning ESB Enterprise Service Bus FTP File Transfer Protocol HTTP Hypertext Transmission Protocol JMS Java Message Service MSM Messaging Service Model MIMOSA An Operations and Maintenance Information Open System Alliance OAG Open Applications Group OAGIS Open Applications Group