--``,,`````,,```,,,```,````,`,-`-`,,`,,`,`,,`---© ISO 2013 – All rights reserved iiiForeword ...iv Introduction ...v 1 Scope ...1 2 Normative references ...1 3 Terms and definitions ...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 consists of various manufacturing processes, resources, and information exchanges among these resources Manufacturing resources include diverse communication networks, devices, software, equipment, materials, and personnel essential for supporting the necessary processes and information exchanges within the application.
To achieve a manufacturing application, it is essential to have a collection of manufacturing resources that meet specific interoperability and integration requirements An integrated manufacturing application is facilitated by a manufacturing system that comprises a cohesive 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 3
Elements of information exchanges in ISO 18435
ISO 18435 emphasizes the integration of applications, while ISO 16100 addresses the interoperability of Manufacturing System Units (MSUs) and the exchange of manufacturing information, whether within a single application or across multiple applications The exchange of information 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 AIMEs set represents the resource capabilities necessary for information exchange to ensure interoperability between two applications, forming a crucial component of an ADME Figure 2 illustrates the ADME that defines the interoperability relationship between these applications An example of an integrated application, the smart pump application, is detailed in Clause A.1 Capability profiles for MSUs are created by completing appropriate capability templates, with Annex C providing examples of these profiles for smart pump applications.
The ADME outlines the interoperability and integration requirements necessary for applications, modeling information exchanges through the application interoperability profile (AIP) notation as specified in ISO 15745-1 It facilitates information exchange based on capabilities identified in the AIMEs, with a complete set of AIMEs defining the information exchange requirements essential for achieving interoperability between two applications.
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 manufacturing process consists of a series of activities arranged in a specific order, with each activity linked to a set of functions These functions are carried out by manufacturing resources, such as Manufacturing System Units (MSUs), which facilitate the necessary information exchanges related to the performed functions.
The context for information exchange is informed by the activities and capability class structure (CCS) illustrated in Figure 3 Clause A.2 provides an example of CCS specifically for the smart pump application Following the ISO 16100 methodology, each capability class is associated with a capability template, with examples for the smart pump application detailed in Annex B.
Figure 3 — Activity tree of an application
Content for information exchange requirements
The information exchanged between the MSUs provides the content for the ADME structure as described in the manufacturing domain data (MDD).
The capability profile outlined in ISO 16100 specifies an activity model that illustrates the information exchange among resources or Manufacturing System Units (MSUs) involved in various activities This exchange typically encompasses input/output data necessary for MSU execution, including recipes, geometric data, schedules, and other essential parameters Additionally, it involves control information such as commands and service requests, as well as status updates that report faults, equipment conditions, alerts, and quality metrics.
The manufacturing domain model (MDM) is a particular view of a manufacturing domain, consisting of MDDs and relationships among them, corresponding to the domain’s applications as shown in Figure 4
A collection of MDDs functions as a terminology set within a specific domain, encapsulating various forms of manufacturing information These MDDs facilitate the exchange of data both among resources within an application and across different applications.
Control information for equipment and devices, such as pumps and variable frequency drives (VFDs), is typically managed by MSUs, although this example does not include those details.
Action performance report / Progress state / Product data / Manufacturing data
Information exchanged - between the methods
Relationship - between MDDs or actions
Support the methods to fulfill the action
Standard time Actual time Start time End time Standard cost Actual cost
Device Equipment Material Workpiece / Substance / Item
Order / Control data / Product data / Manufacturing data
Method Methods in the action
Constraints - in the methods / actions
Figure 4 — Partial activity model represented by MDDs
5.4.2 MDDs used in ADME Content
In a particular manufacturing sector, a manufacturing application is characterized by a collection of Multi-Dimensional Data (MDDs), which convey essential information about different facets of the domain These MDDs facilitate information exchange between applications, playing a crucial role in detailing the content section of the Application Data Management Environment (ADME) Annex C illustrates examples of MDDs that outline the information exchange requirements for the integrated smart pump application.
Conveyance for information exchange
The ADME conveyance section outlines the necessary resource types and configurations for facilitating information exchanges detailed in the content section It addresses interoperability requirements that define the constraints for these resource configurations An example provided in Clause D.4 illustrates how the conveyance section can support the integration of pump control and diagnostics applications, with the channel configured to enable effective information exchange for the integrated smart pump application.
ADME for the smart pump application
The sections 5.3, 5.4, and 5.5 outline the context, content, and conveyance necessary for the ADME framework, which defines the information exchange requirements essential for ensuring interoperability between pump control and diagnostics applications within the integrated smart pump system.
6 Approach for smart pump application interoperability
Smart pump system information model
The asset design environment offers extensive information for managing manufacturing assets, such as pumps used in various processes ISO 15926 plays a crucial role in integrating asset information to enhance life-cycle activities within production facilities It provides a comprehensive model, along with library classes and templates, for representing life-cycle information related to technical installations and their components Figure 5 illustrates the pump information model based on ISO 15926.
Figure 5 — Pump model based on ISO 15926
The ISO 15926 information model can be effectively combined with the ISO 18435 framework to facilitate information exchange By employing an ISO 15745 application integration modeling approach, the information exchange requirements for essential interoperability interfaces can be clearly identified and documented through resource-specific AIMEs These AIMEs outline specific standards that support context-, content-, and conveyance-oriented exchanges, thereby enhancing asset interoperability and the integration of applications related to asset information structures.
Resolving ambiguity using OTD
The relationships between terms and definitions in design and operational environments are often unclear, leading to ambiguity and inconsistency The interpretation of these terms varies depending on the context in which they are used The Open Technical Dictionary (OTD), based on ISO 22745, addresses these issues by providing clarity and consistency in terminology.
The integration of ISO 8000 for data quality can be achieved through ISO 22745 by defining the necessary data requirements for messages that convey master data between organizations This includes specifications for syntax, semantic encoding, and portability.
ISO 22745 is primarily facilitated by the OTD, which serves as a repository for concept identifiers and their corresponding descriptions that define individual data elements By utilizing the concept identifiers from the OTD, organizations can effectively store, transmit, receive, and display descriptive elements while preserving their intended meaning.
ISO 22745 provides guidelines for identification guides (IG), which are sets of rules for describing specific item classes to meet data recipient requirements Specified using an XML schema, an IG enhances machine-aided data quality analysis by clearly defining necessary data elements, eliminating the need for manual review Utilizing an IG in the creation of master data for product catalogs serves as a model for employing concept identifiers in developing application information exchange profiles (AIMEs and ADMEs).
The concept identifiers in the AIMEs and ADMEs' context, content, and conveyance sections reference standards registered in the OTD, which define information exchange objects These identifiers are essential for completing the capability profiles and templates necessary for application integration.
ISO 29002 establishes a framework for aligning ISO 22745 OTD concept identifiers with various other identifier schemes It allows for the expression of IEC 61987 definitions, which include device properties and classifications, as well as ISO 13584 parts libraries and ISO 15926 object identifiers, in terms of ISO 22745 concept identifiers However, the specifics of these mappings and the use of additional concept identifiers are not covered in this Technical Report.
NOTE 2 Concept identifiers are not used in the XML examples in the annexes, for better human readability.
Application integration using ISO 18435
ISO 18435 outlines the interoperability profiles that applications must meet for effective information exchange For instance, a diagnostic application assessing asset condition requires compatible profiles with the control application managing a pump to obtain flow information The ADME serves to define these information exchange requirements, while the AIME describes the interfaces and resource capabilities necessary to ensure interoperability between applications.
A set of AIMEs represents the interface profiles supported by the applications and the corresponding resources and these AIMEs comprise an ADME.
7 Constructing AIME and ADME for smart pump application
Overview
The integrated smart pump application combines two distinct applications: the control application and the diagnostics application This integration enables the smart pump to demonstrate intelligent behavior, such as adjusting its operation modes based on diagnostic results to safeguard equipment and processes An example of the information exchange between the pump control and diagnostics applications is depicted in the sequence diagram in Figure D.1 in Annex D, highlighting the integration of the smart pump application.
AIME for pump control application
The pump control system comprises two distinct applications, each with its own Management and Supervision Unit (MSU): one for proportional integral derivative (PID) control and the other for sensor data acquisition The integration of the PID control and data acquisition applications leads to the formation of a single Advanced Data Management Entity (ADME), which is not detailed in this Technical Report.
In the article, the context and conveyance sections from the ADME are replicated, with symbolic names in the matrix elements of AIMEs and ADMEs replaced by registered concept identifiers from the reference OTD Figure 5 demonstrates the application of these concept identifiers within an AIME Additionally, Figure 6 contrasts the conveyance section, displaying the left side without concept identifiers and the right side incorporating them, highlighting the importance of using standardized identifiers for clarity and consistency.
Flow Rate Request
Flow Rate Response