ISO/TR 18161 TECHNICAL REPORT First edition 2013-07-01 ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - Automation systems and integration — Applications integration approach using information exchange requirements modelling and software capability profiling Systèmes d’automatisation et intégration — Approche d’intégration des applications utilisant des exigences d’échange d’informations de modelage et un logiciel de capacité de profilage Reference number ISO/TR 18161:2013(E) Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST © ISO 2013 ISO/TR 18161:2013(E) COPYRIGHT PROTECTED DOCUMENT © ISO 2013 All rights reserved Unless otherwise specified, no part of this publication may 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 ISO’s member body in the country of the requester ISO copyright office Case postale 56 • CH-1211 Geneva 20 Tel + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyright@iso.org Web www.iso.org Published in Switzerland ii Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) Contents Page Foreword iv Introduction v 1 Scope Normative references Terms and definitions Abbreviated terms Applications interoperability requirements modelling 5.1 Application integration framework in ISO 15745 and ISO 18435 5.2 Elements of information exchanges in ISO 18435 5.3 Context for information exchange requirements 5.4 Content for information exchange requirements 5.5 Conveyance for information exchange 5.6 ADME for the smart pump application Approach for smart pump application interoperability 6.1 Smart pump system information model 6.2 Resolving ambiguity using OTD 6.3 Application integration using ISO 18435 Constructing AIME and ADME for smart pump application 7.1 Overview 7.2 AIME for pump control application 7.3 AIME for pump diagnostics application 10 7.4 ADME for the integrated smart pump application 10 General procedures for achieving application integration 10 Annex A (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 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST iii ISO/TR 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 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) on all matters of electrotechnical standardization 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 or 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 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 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - 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 noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2. www.iso.org/directives ISO/TR 18161:2013(E) Introduction The motivation 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 expertise 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 its 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 framework 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 concisely 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 aspects 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 described 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 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST v ``,,`````,,```,,,`` Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST TECHNICAL REPORT ISO/TR 18161:2013(E) Automation systems and integration — 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 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 interoperability requirements of the integrated smart pump application, which comprises the pump control application and the pump diagnostics application Normative references ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - The following documents, in whole or in part, are normatively referenced in this document and are indispensable for its application 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: Interface services, protocols and capability templates ISO 16100-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 automation systems and integration — Diagnostics, capability assessment and maintenance applications integration — Part 2: Descriptions and definitions of application domain matrix elements Terms and definitions For the purposes of this document, the terms and definitions given in ISO 16100-3, ISO 16100-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 denote the capabilities of the resource to support information exchange [SOURCE: ISO 18435‑2:2012, 3.4] © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) 3.3 application interoperability profile AIP single specification referencing a group of profiles that reference 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 profiling method that represents manufacturing software unit functionality and behaviour with regard to the software unit’s 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 when used in different manufacturing activities; however, the MSU’s 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 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 capability 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 resources 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 domain’s applications [SOURCE: ISO 16100‑5:2009, 3.5] 2 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) Abbreviated terms ADID Application Domain Integration Diagram AIF Application Integration Framework ADME AIME AIP CCS IG MDD MDM MSU OTD PID PLC UML VFD XML Application Domain Matrix Element Application Interaction Matrix Element Application Interoperability Profile Capability Class Structure Identification Guide Manufacturing Domain Data Manufacturing Domain Model Manufacturing Software Unit Open Technical Dictionary Proportional Integral Derivative Programmable Logic Controller Unified Modelling Language Variable Frequency Drive eXtensible Markup Language 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 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 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 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 integration diagram (ADID) © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST 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 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 operations 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 resources 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 part 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 templates Annex C shows the examples of capability profiles for the smart pump applications 4 ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - 28 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST 29 ISO/TR 18161:2013(E) Annex C (informative) Application software unit capability profiles C.1 Smart pump data acquisition capability profile ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - The following XML example represents the capability profile of the data acquisition application SmartPumpDaqMSU1 30 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) C.2 Smart pump diagnostics capability profile The following XML example represents the capability profile of the pump diagnostics application SmartPumpDiagnoseMSU2 © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST 31 ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - ISO/TR 18161:2013(E) C.3 Smart pump control capability profile The following XML example represents the capability profile of the pump control application SmartPmupControlMSU3 ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - 32 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST 33 ISO/TR 18161:2013(E) Annex D (informative) AIME and ADME in smart pump application D.1 Overview The sequence diagram in Figure D.1 shows the simple information exchange between the pump control application and the pump diagnostics application ADME supports the information exchange between the applications based upon the resource capabilities identified in the AIMEs In this scenario, the pump control application requests the diagnostic information (degree of pump cavitation) from the pump diagnostics application and adjusts the pump speed accordingly Figure D.1 — Simple information exchange between two applications ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - Clauses D.2 and D.3 show the example set of AIMEs for the pump control and the pump diagnostics Clause D.3 shows the example of an ADME for the integrated smart pump application More complicated information exchange will involve multiple ADMEs and AIMEs D.2 AIME for pump control The following XML example represents the AIME for the pump control PumpControlAIME 1a D.1.2.Ay_D.1.1Az ISO AIP 2012-12-30 Industry_specific_registry_name_ISO_13774_DM 34 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST D1.1 PumpControl Pump_DM_Context FlowPIDControl ControlLogix01 PLCiso15745profile PowerFlex00 VFDiso15745profile PumpControl to Diagnostics (Cavitation Detection) Example Diagnostics Request Message - AIME XML schema type CavInfoRequestMsg will have sensor values for flow, pressure and temperature Diagnostics Response Message - AIME XML schema type CavInfoResponseMsg will have degree of cavitation Role for Pump Control Behavior for PumpControl - use CIP for VFD control Pump Control Participant Pump Control to Diagnostics Channel Type Ethernet/IP channel based on ISO15745-2 Comm Profile © ISO 2013 – All rights reserved Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST 35 ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - ISO/TR 18161:2013(E) ISO/TR 18161:2013(E) D.3 AIME for pump diagnostics The following XML example represents the AIME for the pump diagnostics ``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,` - PumpDiagAIME 1a D.1.2.Ay_D.1.1Az ISO AIP 2012-12-30 Industry_specific_registry_name_ISO_13774_SD D1.2 PumpDiagnostics Pump_SD_Context CurrentHealthEvaluation ControlLogix02 PLCiso15745profile PumpControl to Diagnostics (Cavitation Detection) Example Diagnostics Request Message - AIME XML schema type CavInfoRequestMsg will have sensor values for flow, pressure and temperature Diagnostics Response Message - AIME XML schema type CavInfoResponseMsg will have degree of cavitation Role for Diagnostics - Cavitation Detection Behavior for Diagnostics Role - Cavitation Detection 36 Copyright International Organization for Standardization Provided by IHS under license with ISO No reproduction or networking permitted without license from IHS © ISO 2013 – All rights reserved Licensee=University of Alberta/5966844001, User=sharabiani, shahramfs Not for Resale, 11/29/2013 02:00:03 MST ISO/TR 18161:2013(E) file”> Diagnostics Participant Pump Control Participant Diagnostics Participant