1、 ISO 2013 Automation systems and integration Applications integration approach using information exchange requirements modelling and software capability profiling Systmes dautomatisation et intgration Approche dintgration des applications utilisant des exigences dchange dinformations de modelage et
2、un logiciel de capacit de profilage TECHNICAL REPORT ISO/TR 18161 First edition 2013-07-01 Reference number ISO/TR 18161:2013(E) ISO/TR 18161:2013(E)ii ISO 2013 All rights reserved COPYRIGHT PROTECTED DOCUMENT ISO 2013 All rights reserved. Unless otherwise specified, no part of this publication may
3、be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address below or ISOs member body in the country of the r
4、equester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org Web www.iso.org Published in Switzerland ISO/TR 18161:2013(E) ISO 2013 All rights reserved iii Contents Page Foreword iv Introduction v 1 Scope . 1 2 Normative refere
5、nces 1 3 Terms and definitions . 1 4 Abbreviated terms 3 5 Applications interoperability requirements modelling 3 5.1 Application integration framework in ISO 15745 and ISO 18435 . 3 5.2 Elements of information exchanges in ISO 18435 . 4 5.3 Context for information exchange requirements 5 5.4 Conten
6、t for information exchange requirements 6 5.5 Conveyance for information exchange . 7 5.6 ADME for the smart pump application 7 6 Approach for smart pump application interoperability . 8 6.1 Smart pump system information model . 8 6.2 Resolving ambiguity using OTD . 8 6.3 Application integration usi
7、ng ISO 18435 . 9 7 Constructing AIME and ADME for smart pump application 9 7.1 Overview 9 7.2 AIME for pump control application 9 7.3 AIME for pump diagnostics application .10 7.4 ADME for the integrated smart pump application 10 8 General procedures for achieving application integration .10 Annex A
8、 (informative) Modelling smart pump application .12 Annex B (informative) Capability profiling templates of application software units 14 Annex C (informative) Application software unit capability profiles .30 Annex D (informative) AIME and ADME in smart pump application .34 Bibliography .40 ISO/TR
9、18161:2013(E) Foreword ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject
10、 for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC)
11、on all matters of electrotechnical standardization. The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular the different approval criteria needed for the different types of ISO documents should be not
12、ed. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any o
13、r all such patent rights. Details of any patent rights identified during the development of the document will be in the Introduction and/or on the ISO list of patent declarations received. www.iso.org/patents Any trade name used in this document is information given for the convenience of users and
14、does not constitute an endorsement. The committee responsible for this document is Technical Committee ISO/TC 184, Automation systems and integration, Subcommittee SC 5, Architecture, communication and integration frameworks.iv ISO 2013 All rights reserved ISO/TR 18161:2013(E) Introduction The motiv
15、ation for ISO 16100 stems from the industrial and economic environment, in particular: a) a growing base of vendor-specific solutions; b) user difficulties in applying standards; c) the need to move to modular sets of system integration tools; d) the recognition that application software and the exp
16、ertise to apply that software are assets of the enterprise. ISO 16100 is an International Standard for the computer-interpretable and human readable representation of a capability profile. Its goal is to provide a method to represent the capability of manufacturing application software relative to i
17、ts role throughout the life cycle of a manufacturing application, independent of a particular system architecture or implementation platform. This can lead to reduced production and information management costs to users and vendors/suppliers of manufacturing applications. ISO 18435 provides a framew
18、ork for harmonized use of industry and international standards in order to integrate control, diagnostics, prognostics, capability assessment, and maintenance applications. By using an ISO 15745 application integration modelling approach, key interoperability interfaces can be identified and concise
19、ly documented in terms of profiles. ISO 18435 also provides the elements and the rules to describe the integration requirements of an automation application. The elements include the key aspects when integrating an automation application with other applications and the relationships of these key asp
20、ects. The rules include the information exchanges to support interoperability within an application and between applications. This Technical Report describes a use case of modelling the smart pump application described in Annex A. The detailed manufacturing software unit profiling templates are desc
21、ribed in Annex B. The detailed manufacturing software unit profiles are described in Annex C. The information exchanged among manufacturing software units in the smart pump application based on ISO 18435 methodology is described in Annex D. ISO 2013 All rights reserved v Automation systems and integ
22、ration Applications integration approach using information exchange requirements modelling and software capability profiling 1 Scope This Technical Report describes an approach for using ISO 16100 and ISO 18435 to specify information exchange requirements between applications. This approach is based
23、 on the use of ISO 18435 application interaction matrix element (AIME)/application domain matrix element (ADME) templates in conjunction with ISO 16100 manufacturing software unit (MSU) capability profiles. This Technical Report also provides an example approach as applied to describing the interope
24、rability requirements of the integrated smart pump application, which comprises the pump control application and the pump diagnostics application. 2 Normative references The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its applicatio
25、n. For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments) applies. ISO 16100-3:2005, Industrial automation systems and integration Manufacturing software capability profiling for interoperability Part 3:
26、Interface services, protocols and capability templates ISO 16 100-5:2009, Industrial automation systems and integration Manufacturing software capability profiling for interoperability Part 5: Methodology for profile matching using multiple capability class structures ISO 18435-2:2012, Industrial au
27、tomation systems and integration Diagnostics, capability assessment and maintenance applications integration Part 2: Descriptions and definitions of application domain matrix elements 3 Terms and definitions For the purposes of this document, the terms and definitions given in ISO 16100-3, ISO 16100
28、5, ISO 18435-2, and the following apply. 3.1 application domain matrix element ADME entry in an application domain matrix to organize information exchange among applications SOURCE: ISO 18435-2:2012, 3.2 3.2 application interaction matrix element AIME entry in application interaction matrix to deno
29、te the capabilities of the resource to support information exchange SOURCE: ISO 18435-2:2012, 3.4 TECHNICAL REPORT ISO/TR 18161:2013(E) ISO 2013 All rights reserved 1 ISO/TR 18161:2013(E) 3.3 application interoperability profile AIP single specification referencing a group of profiles that reference
30、 parts of base specifications which may themselves be profiles Note 1 to entry: The group of profiles can include process profile(s), information exchange profile(s), resource profile(s) and sometimes other AIPs. SOURCE: ISO 18435-2:2012, 3.5 3.4 capability class element within the capability profil
31、ing method that represents manufacturing software unit functionality and behaviour with regard to the software units role in a manufacturing activity, as denoted in a capability inheritance structure and as deployed in a capability aggregation structure Note 1 to entry: The role of a MSU changes whe
32、n used in different manufacturing activities; however, the MSUs corresponding capability class is positioned uniquely in an inheritance structure, but can assume different positions in an aggregation structure. Note 2 to entry: In this Technical Report, a capability class template is identical to a
33、capability template (ISO 16100-2:2003, 6.3, gives requirements for capability templates). SOURCE: ISO 16100-5:2009, 3.1, modified 3.5 capability class structure CCS hierarchy of capability classes 3.6 capability profiling template capability template template schema for a manufacturing software capa
34、bility profile Note 1 to entry: It could be partially filled. SOURCE: ISO 16100-3:2005, 3.1.14, modified 3.7 manufacturing domain data MDD unified modelling language (UML) class representing information about manufacturing resources, manufacturing activities, or items exchanged among manufacturing r
35、esources within a particular manufacturing domain SOURCE: ISO 16100-5:2009, 3.3 3.8 manufacturing domain model MDM particular view of a manufacturing domain, consisting of manufacturing domain data and relationships among them, corresponding to the domains applications SOURCE: ISO 16100-5:2009, 3.52
36、 ISO 2013 All rights reserved ISO/TR 18161:2013(E) 4 Abbreviated terms ADID Application Domain Integration Diagram ADME Application Domain Matrix Element AIF Application Integration Framework AIME Application Interaction Matrix Element AIP Application Interoperability Profile CCS Capability Class St
37、ructure IG Identification Guide MDD Manufacturing Domain Data MDM Manufacturing Domain Model MSU Manufacturing Software Unit OTD Open Technical Dictionary PID Proportional Integral Derivative PLC Programmable Logic Controller UML Unified Modelling Language VFD Variable Frequency Drive XML eXtensible
38、 Markup Language 5 Applications interoperability requirements modelling 5.1 Application integration framework in ISO 15745 and ISO 18435 The application integration framework (AIF) that is explained in ISO 15745-1 provides a basis for integrating an automation and control system architecture within
39、a manufacturing application architecture. An integrated manufacturing application can be modelled as a combination of a set of manufacturing processes, resources and a set of information exchange among the manufacturing resources, as shown in Figure 1. Manufacturing resources can be further divided
40、as several types of communication networks, devices, software, equipment, material, and personnel necessary to support the processes and information exchanges required by the application. A set of manufacturing resources that satisfy a set of interoperability and integration requirement is needed to
41、 realize a manufacturing application. An integrated manufacturing application is enabled by a manufacturing system consisting of a set of integrated manufacturing resources. The categories of application domains of interest are enumerated in ISO 18435-1 and represented using an application domain in
42、tegration diagram (ADID). ISO 2013 All rights reserved 3 ISO/TR 18161:2013(E) Figure 1 Application integration model 5.2 Elements of information exchanges in ISO 18435 ISO 18435 focuses on integration of applications. ISO 16100 focuses on interoperability of MSUs, including manufacturing information
43、 exchange either within one application or within different applications. The information exchange among resources is represented by ISO 18435. ISO 18435-1 provides an overview of the integration requirements of a manufacturing application. The focus is on the production operations and maintenance o
44、perations domains, including the capability assessment activities. ISO 18435-2 provides the detailed definitions of the AIME and ADME structures and their relationships. General procedures for constructing AIMEs and ADMEs are also described. An AIME represents capabilities provided by a set of resou
45、rces of an application in order to exchange information with another set of resources associated with another application. The set of AIMEs that represents the resource capabilities that meet the information exchange requirements to support the interoperability of two applications comprises a key pa
46、rt of an ADME. ADME that qualifies interoperability relationship between two applications is elaborated in Figure 2. Clause A.1 has an example of an integrated application which describes the smart pump application. The capability profiles of MSUs are obtained by filling adequate capability template
47、s. Annex C shows the examples of capability profiles for the smart pump applications.4 ISO 2013 All rights reserved ISO/TR 18161:2013(E)Activities Activities 1M 1* AIME 1* 1* Resource Information Exchange 1* 1N AIME Integrated Application X 1* Process 1* 1* ADME (X, Y) Integrated Application Y Resou
48、rce Process Information Exchange Figure 2 AIME and ADME The purpose of the ADME is to describe the interoperability and integration requirements that are required by the applications. The general concept of an ADME is to model the information exchanges between applications using the application inte
49、roperability profile (AIP) notation as described in ISO 15745-1. The ADME supports the information exchange between the applications based upon the capabilities identified in the AIMEs. The complete set of AIMEs that represents the information exchange requirements for realizing the interoperability of two applications comprises an ADME. 5.3 Context for information exchange requirements The context for the information should be established using the application domain of interest as described in ISO 18435-1. A
