ISO/TC 184 - Automation systems and integration

This document specifies how to apply the Test Process Improvement method to the assessment of organizational process maturity. This document refines the language in the method, which has an original purpose of more than just data quality management. This document supports improving data quality management when an organization uses the process reference model in ISO 8000‑61 as the foundation for specifying the measurement goals for the process measurement necessary when performing maturity assessment. The following are within scope of this document: — the relationship between the Test Process Improvement method[11][12] and the procedure for assessing process maturity of data quality management as specified by ISO 8000‑61; — the role of process measurement in accordance with ISO 8000‑63 when performing assessment of process maturity; — the outputs from the procedure. The following are outside the scope of this document: — the purpose, outcomes and activities of processes for data quality management; — specific content for the scope of individual quality management areas, the maturity levels and the maturity level targets; — specific content for each inspection order including the frequency of inspection points; — instructions on how to develop a process improvement strategy in response to the outputs of the procedure. This document can be used in conjunction with or independently of quality management systems standards.

This document specifies the key considerations for organizations that are establishing appropriate roles and responsibilities for data quality management. The following are within the scope of this document: — implementing roles and responsibilities for data quality management; — providing documentary evidence of this implementation; — a framework for roles and responsibilities; — a functional model of roles and responsibilities; — example deployment scenarios for the framework of roles and responsibilities; — comparison with the processes specified by ISO 8000‑61. The following are outside the scope of this document: — process reference models for data quality management (ISO 8000‑61 specifies a process reference model for data quality management); — methods for data quality evaluation and certification; — models for assessing the maturity of data quality management (ISO 8000‑62 and ISO 8000‑64 specify approaches to assessing the maturity of data quality management). This document can be used in conjunction with or independently of standards for quality management systems.

This document provides an overview of the ISO 8000 series. The following are within the scope of this document: — stating the scope of the ISO 8000 series as a whole; — establishing the principles of information and data quality; — describing the path to data quality; — describing the structure of the ISO 8000 series; — providing a summary of the content of each part in the ISO 8000 series; — establishing the relationship of the ISO 8000 series to other international standards.

This document specifies a mapping of EXPRESS (ISO 10303–11) constructs to SysML constructs for the purpose of representing EXPRESS schemas in SysML models. The specified mapping is a one-way transformation from an EXPRESS schema to a SysML information model. The following are within the scope of this document: — the specification of the transformation of EXPRESS constructs to SysML constructs represented in CXMI; — the specification of the transformation of EXPRESS UNIQUE rules to SysML constructs represented in CXMI; — the specification of the transformation of derived attributes to implement renaming to SysML constructs represented in CXMI. The following are outside the scope of this document: — the transformation of EXPRESS elements into SysML metamodel constructs that are not used in the STEP Extended Architecture; — transformation of EXPRESS FUNCTIONS; — transformation of EXPRESS-G to SysML diagrams; — tools, codes, and scripts to transform an EXPRESS schema to SysML CXMI; — transformation of EXPRESS interface specification; — SysML constraints transformation from EXPRESS DERIVE attributes, except the ones used for renaming; — SysML constraints transformation from EXPRESS SUPERTYPE expressions; — SysML constraints transformation from EXPRESS GLOBAL rules; — SysML constraints transformation from EXPRESS WHERE rules. NOTE EXPRESS DERIVE attributes, EXPRESS SUPERTYPE expressions, EXPRESS GLOBAL rules and EXPRESS WHERE rules are transformed into OCL specifications. OCL specifications are integrated in the SysML model based on a separate process.

This document describes the COLLADA™ schema. COLLADA is a Collaborative Design Activity that defines an XML-based schema to enable 3D authoring applications to freely exchange digital assets without loss of information, enabling multiple software packages to be combined into extremely powerful tool chains. The purpose of this document is to provide a specification for the COLLADA schema in sufficient detail to enable software developers to create tools to process COLLADA resources. In particular, it is relevant to those who import to or export from digital content creation (DCC) applications, 3D interactive applications and tool chains, prototyping tools, real-time visualization applications such as those used in the video game and movie industries, and CAD tools. This document covers the initial design and specifications of the COLLADA schema, as well as a minimal set of requirements for COLLADA exporters. This document covers the following information: initial design and specifications of the COLLADA schema; requirements of COLLADA tools and a minimal set of requirements for COLLADA exporters; detailed explanations for COLLADA programming; core elements that describe geometry, animation, skinning, assets, and scenes; physics model, visual effects (FX), boundary representation (B-rep) of animation, kinematics. The document does not specify the implementation of, or definition of a run-time architecture for viewing or processing of COLLADA data.

This document specifies requirements for the exchange of messages that contain master data consisting of characteristic data. These requirements can be checked by computer. The messages are suitable for exchange between organizations and between systems. EXAMPLE 1 A supplier sends a message to a customer. The message contains characteristic data describing an item that the customer is considering buying. The following are within the scope of this document: — conformance of master data messages to a formal syntax; — semantic encoding of master data messages; — conformance of master data messages to data specifications; — requirements on access to the data dictionaries that enable decoding of master data messages. The following are outside the scope of this document: — master data that are not characteristic data; — data that are not in messages; — messages that do not exchange master data between organizations or systems; EXAMPLE 2 A merchant sends a message to a credit card company. The message represents a credit charge transaction and does not exchange master data between the organizations. — recording the provenance of master data; EXAMPLE 3 ISO 8000‑120 addresses the capture and exchange of data provenance information. — accuracy of master data; EXAMPLE 4 ISO 8000‑130 addresses the representation and exchange of information about the accuracy of master data that consists of characteristic data. — exchange of data that are not master data; EXAMPLE 5 ISO 8000‑140 addresses the representation and exchange of information about the completeness of master data that consists of characteristic data. — management of master data internally within an organization; EXAMPLE 6 Data within an organization's enterprise resource planning or product data management system is out of scope. EXAMPLE 7 Making backup copies of data files containing master data is out of scope. — quality of data dictionaries; — a specific formal syntax for the exchange of master data. EXAMPLE 8 The ISO 9735 series, the ISO 13584 series, the ISO 15926 series and the ISO 22745 series specify formats that enable exchange of master data. The requirements in this document are considered necessary but not sufficient to achieve data quality with respect to exchange of master data. Issues such as the accuracy and provenance of master data also need to be addressed as part of an overall data quality strategy.

This document provides an overview and general principles of a digital twin framework for manufacturing including: — terms and definitions; — requirements of the digital twin framework for manufacturing.

This document identifies technical requirements for information exchange between entities within the reference architecture. The requirements for information exchange in the following networks are within the scope of this document: — user network that connects the user entity and the digital twin entity; — service network that connects sub-entities within the digital twin entity; — access network that connects the device communication entity to the digital twin entity and to the user entity; — proximity network that connects the device communication entity to the observable manufacturing elements.

This document examines the standardization requirements for the necessary digital validation technology for improving design efficiency by effectively utilizing simulation data at the functional design stage of digitally integrated products.

This document provides a reference architecture for the digital twin in manufacturing including; — reference model from domain and entity point of view; — functional view specifying functional entities supported by the entity-based reference model.

This document specifies assessment indicators to support the assessment of organizational process maturity for data quality management in the context of manufacturing operations management as specified by IEC 62264‑1. The following are within scope of this document: — assessment indicators that are work products generated by data processing (as specified by ISO 8000‑61) and, thus, enable rating of process performance, a process attribute specified by ISO/IEC 33020; — the role played by each work product in the processes of manufacturing operations management; — the connection of each work product to the outcomes of the processes of manufacturing operations management. The following are outside the scope of this document: — assessment indicators for any of the other process attributes specified by ISO/IEC 33020; — methods or procedures to measure process capability.

This document provides a list of basic information attributes for the OMEs: — examples of information attributes are given; — standards that can define these information attributes are discussed in Annex A.

This document lists smart manufacturing related standards with their characteristics as specified in ISO/IEC TR 63306-1.

This document specifies the transformation of SysML (ISO/IEC 19514:2017) constructs to XSD (World Wide Web Consortium's XML schema definition language) constructs for the purpose of representing the SysML model represented in XMI (ISO/IEC 19509:2014) as XML (World Wide Web Consortium's XML) schemas. The specified mapping is a one-way transformation from SysML information model represented in XMI into an XML schema. These limitations make the mapping unsuitable for the transformation of arbitrary SysML models to XML schemas. The following are within the scope of this document: — the specification of the structure, components, and conventions of the XSD for the STEP (ISO 10303-1) XML implementation method; — the transformation of SysML metamodel constructs represented in XMI to XSD constructs for the purpose of representing SysML information models as XML schemas. The following are outside the scope of this document: — the transformation of SysML metamodel constructs into XSD constructs that are not used in the STEP extended architecture; — the transformation of SysML metamodel constructs into XSD constructs for other purposes than representing SysML constructs as STEP concepts; — codes and scripts to transform SysML XMI to XSD schema; — the transformation of SysML constraints (OCL, see ISO/IEC 19507) into Schematron (see ISO/IEC 19757‑3).

This document specifies a mapping of SysML (ISO/IEC 19514:2017) constructs to EXPRESS (ISO 10303-11:2004) elements for the purpose of representing SysML model represented in XMI (ISO/IEC 19509:2014) as EXPRESS (ISO 10303-11:2004) schemas. The specified mapping is a one-way transformation from SysML information model represented in XMI into an EXPRESS schema. NOTE Due to this limitation 10303-16 does not define the transformation of arbitrary SysML models to EXPRESS. The following are within the scope of this document: — the transformation of SysML metamodel constructs represented in XMI to EXPRESS elements for the purpose of representing SysML information models as EXPRESS schemas. The following are outside the scope of this document: — the transformation of SysML metamodel constructs into EXPRESS elements that are not used in the STEP Extended Architecture. NOTE The STEP Extended Architecture is defined in References [8], [9] and [10]. — the transformation of SysML metamodel constructs into EXPRESS elements for other purposes than representing SysML constructs as STEP concepts; — codes and scripts to transform SysML XMI to EXPRESS schema; — the transformation of SysML constraints (OCL[5]) into EXPRESS global and local rules; — the transformation of EXPRESS elements into SysML constructs.

This document deals with the safety interface and control interface. It allocates signals to a conformance class and/or conformance option. It describes the detailed functions of each signal, describes and displays the timing interactions between signals in flow charts and shows examples for safety matrices and safety-related functional relationships. This document defines three conformance classes and dedicated conformance options. Classes and options consist of a number of signals to: — allow a flexible adaptation of the interface(s) to a project-specific scope of functions and simultaneously; — tie sets of signals tight enough to avoid unnecessary coordination efforts between suppliers of the machine tending systems and machines.

This document specifies the definition for services at the point of interaction between a client and server. The following are within the scope of this document: — the specification of the structure, components and conventions for domain- and technology-independent services implementation methods for STEP (ISO 10303-1); — transformation of the SysML metamodel constructs to OpenAPI constructs for RESTful web services (see OpenAPI:3.0.0[25] and IETF RFC7231). The following are outside the scope of this document: — domain specific services definitions; — the transformation of SysML metamodel constructs into OpenAPI constructs that are not used in the STEP extended architecture[12][13]; — the transformation of SysML metamodel constructs into OpenAPI constructs for other purposes than representing SysML constructs as STEP concepts; — codes and scripts to transform SysML XMI to OpenAPI schema; — the transformation of SysML constraints into OpenAPI schema; — implementation of technology-specific services definitions other than RESTful OpenAPI; — definition of management and maintenance of information and data on a server.

This document specifies a procedure for data profiling to generate the foundation for performing data quality assessment. This profiling is applicable to data sets that are either originally in a structure of tables and columns or are the output from a transformation to create such a structure. NOTE 1 Data profiling is applicable to all types of database technology. The following are within the scope of this document: — performing structure analysis to determine data element concepts; — performing column analysis to identify relevant data elements, including statistics about a data set; — performing relationship analysis to identify dependencies in a data set. The following are outside the scope of this document: — methods for extracting and sampling data to be profiled from a data set; — deriving data rules; — measuring the extent of nonconformities in a data set. NOTE 2 ISO 8000‑8 specifies approaches to measuring data and information quality. This document can be used in conjunction with, or independently of, quality management systems standards.

This document provides an overview of ISO 10303. ISO 10303 provides a representation of product information along with the necessary mechanisms and definitions to enable product data to be exchanged. The exchange is among different computer systems and environments associated with the complete product lifecycle, including product design, manufacture, use, maintenance, and final disposition of the product. This document defines the basic principles of product information representation and exchange used in ISO 10303. It specifies the characteristics of the various series of parts of ISO 10303 and the relationships among them. The following are within the scope of this document: — scope statement for ISO 10303 as a whole; — overview of ISO 10303; — architectures of ISO 10303; — structure of ISO 10303; — terms and definitions used throughout ISO 10303; — overview of data specification methods used in ISO 10303; NOTE This includes the EXPRESS data specification language and graphical presentation of product information models. — introduction to the series of parts of ISO 10303: — integrated resources; — application interpreted constructs; — application modules; — business object models; — application protocols; — implementation methods; — usage guides; — conformance testing methodology and framework; — abstract test suites; — scheme for identification of schemas and other information objects defined within parts of ISO 10303.

This document analyses visualization elements that are key components of the interface between the physical asset and the avatar (digital replica of the physical asset).

This document defines the maturity model and the evaluation methodology on convergence of informatization and industrialization in industrial enterprises. The scope of this document includes the following: — maturity model definition; — principles of evaluation questionnaires; and — guidance for a maturity evaluation method.

This document defines the basic principles for an assessment concerning the convergence of informatization and industrialization (CII) in industrial enterprises, including the following: — assessment framework definitions; — assessment reference model definitions; — assessment reference model components.

This document specifies the concept and structure of the ISO 16400 series. This series specify a methodology for preparing a template and items of an equipment behaviour catalogue (EBC) as a basis to structure a virtual production system.

This document describes the general content and structure of the entire QIF information model. It describes the highest level data structures of QIF, that are expanded in Clauses 6 through 12 using data dictionaries and XML schema files. All QIF XML schema files can be found at www.qifstandards.org. This document also describes practices for forming QIF instance files, called "documents," that support quality workflow scenarios. Its focus is to show how the QIF information model, and data formed into XML instance files, support the entire scope of model based definition manufacturing quality workflow. It describes how the information model is partitioned among the XML schema files and contains all terms used in the subject area clauses. The purpose of this document is to orient potential users of QIF to the organization of the information model to make their study of the details more rewarding and efficient. It should also help solution providers and users to evaluate QIF for their uses, without needing to go to the lowest technical details of the XML schemas. The information model narrative focuses on the approach to modeling the core data structures of QIF, which model the content of ASME GD&T and ISO GPS, and the plans and results data elements defined in Dimensional Measuring Interface Standards (DMSI) ISO 22093 and ANSI/DMSC DMIS 5.3. The material on XML practices describes consistent design practices to be used by QIF working groups who will be designing new schemas. It should also help data processing experts to write software that writes and reads manufacturing quality data using the XML schemas.

This document specifies a questionnaire to audit the performance of the processes specified by the process reference model in ISO 8000‑61. NOTE 1 This questionnaire is applicable to all types of business process, technology, information system, data and data processing. This questionnaire can be used as part of a continuous improvement process. The following are within the scope of this document: — guiding principles for generating questions from the process outcomes specified by ISO 8000‑61; — one or more questions for each outcome of every process in ISO 8000‑61; — a measurement method based on a simple indicator and measurement scale for each question; — guidance on how to present the results generated by the questionnaire. NOTE 2 The questions and corresponding indicators in this document conform to the requirements of ISO 8000‑63. The following is outside the scope of this document: — defining how the questions relate to models of organizational process maturity. NOTE 3 Such models define an overall scale by which to understand the degree to which an organization is performing effectively and efficiently. EXAMPLE ISO 8000‑62 and ISO 8000‑64 [1]specify how to use maturity models with ISO 8000‑61. [1] Under preparation.

This document defines the formatting, syntax and semantic rules for describing ? an object oriented interface for using services provided by a coordinator and ? the configuration of virtual devices and the environment for their use.

This document defines terms relating to data quality used in the ISO 8000 series of parts.

This document identifies and specifies constructs necessary for users that model enterprises in conformance with ISO 19439. This document focuses on, but is not restricted to, engineering and the integration of manufacturing and related services in the enterprise. The constructs enable the description of structure and functioning of an enterprise for use in configuring or implementing in different application domains. This document specifies an implementation framework in Clause 6 to map model constructs into such domains.

This document specifies the process data for additive manufacturing. This document describes additive manufacturing at the micro process plan level without making a commitment to particular machines, processes or technologies.

This document defines the principle of verification and validation according to the activity models and workflow of an advanced process control and optimization (APC-O) system, analyses and defines the general process for verification and validation of APC-O systems, and specifies a set of indicators and checkpoints used for verification and validation.

This document specifies a structure for process measurement stacks that organizations can instantiate to measure the characteristics of processes for data quality management. This structure consists of goal, sub goal, question, indicator and metric. The instantiated stack consists of content that is determined by a chosen model for assessing the maturity of the processes under consideration. The following are within the scope of this document: — the fundamentals of process measurement; — the inspection plan and inspection order by which to perform measurement; — the structure of the measurement stack; — the role of the chosen maturity model in instantiating the stack. The following are outside the scope of this document: — methods for inspecting implemented processes; — methods for generating measured values from the inspection of processes; — how to choose a suitable maturity model. This document can be used in conjunction with, or independently of, quality management systems standards. NOTE ISO 8000‑8 specifies concepts and methods for measuring information and data quality.

This document specifies a reference base of concepts and principles for enterprise architectures that enable enterprise development, enterprise integration, enterprise interoperability, human understanding and computer processing. This document further specifies requirements for models and languages created for expressing such enterprise architectures. This document specifies those terms, concepts and principles considered necessary to address stakeholder concerns and to carry out enterprise creation programmes as well as any incremental change projects required by the enterprise throughout the whole life of the enterprise. This document forms the basis by which enterprise architecture and modelling standards can be developed or aligned. This document does not define standard enterprises, standard organizational structures, standard enterprise processes, or standard enterprise data. In addition, this standard does not specify enterprise modelling processes.

This document defines the principles and methods for conformance testing of software implementations of ISO 15926. It provides guidance for developing test cases and testing procedures that cover the requirements specified in the ISO 15926 series and in different industry usage contexts, e.g. data exchange, use of reference data libraries and interface services. This document provides guidance in addition to the conformance in the parts. NOTE 1 Guidance on conformance ISO 15926 testing of complex scenarios which represent integrated interoperability is outside the scope of this document. NOTE 2 Guidance on the development of software that supports the way of file exchange in the simple scenario which represents unified interoperability is outside the scope of this document.

This document specifies the search methodology from software unit catalogues for acquiring candidate capability units which satisfy the manufacturing application requirements.

ISO 21919 describes interfaces for automated machine tending of at least one computer numerically controlled (CNC) machine by using a machine tending device. These interfaces are the link between automated machine tending devices and machines used for production. The automated machine tending is initiated by either the machine tending system or by the machine. This document gives an overview and defines the fundamental principles on how the interfaces are set up. It defines the necessary vocabulary and sets the syntax for the structure of signals. It distinguishes between the safety interface, the control interface and project specific extensions. This document defines three conformance classes and dedicated conformance options. Classes and options consist of a number of signals to simultaneously: — allow a flexible adaptation of the interface(s) to a project-specific scope of functions; — tie sets of signals tight enough to avoid unnecessary coordination efforts between suppliers of the machine tending devices and machines. ISO 21919 concentrates on the control-related and safety-related connections. It does not describe the mechanical connections, it does not determine the transfer physics, a pin assignment, the hardware of the interfaces or measure of communication, e.g. protocol, and it is not intended to be used for communication to a MES (Manufacturing Execution System). NOTE ISO 21919‑2 deals with the safety interface and control interface, allocating signals to a conformance class and/or conformance option, describing the detailed functions of each signal, describing and displaying the timing interactions between signals in flow charts and showing examples for safety matrices and safety-related functional relationships.

This document specifies the initial set of core reference data items which can be used to record information about process plants, including oil and gas production facilities. The following are within the scope of this document: — core classes for process plants, including oil and gas production facilities; NOTE 1 Reference data items can be core classes, de facto classes, commodity classes and manufactured product classes. Reference data items can also be standard classes or proprietary classes. The terms for the different types of class are defined in 3.1. A discussion about the different types of classes is contained in Annex D. NOTE 2 A core class defined by this document can be used by ISO 15926-2, ISO/TS 15926-7, ISO/TS 15926-8, ISO/TS 15926-11, ISO/TS 15926-12, ISO 15926-13 and ISO 10303-221. — the unique name for each reference data item; — the definition of each reference data item; — subclass and classification relationships between reference data items; — the entity within ISO 15926-2 that can be used to record each reference data item. NOTE 3 Each reference data item that is a class is directly or indirectly a subclass of an entity in ISO 15926-2. The following are outside the scope of this document: — data requirements for additional reference data items; — the procedures to be followed for registration and maintenance of additional reference data items.

This document provides the overview and general principles of a method for evaluating environmental performance, including energy efficiency and other factors, of a manufacturing system that influence the environment. This document is applicable to manufacturing systems for discrete, batch, and continuous manufacturing. This document is applicable to an entire manufacturing system and to a part of the manufacturing system. Life cycle assessment of products manufactured by the manufacturing system is outside the scope of ISO 20140.

This document specifies the requirements for representing authoritative legal entity identifiers (ALEI). These requirements supplement those of ISO 8000‑115. The following are within the scope of this document: — the requirements for the prefix element, a single sub-domain element and the identifier element to represent authoritative legal entity identifiers. NOTE ALEIs are applicable to all types of legal entity, whether individuals or organizations. The following are outside the scope of this document: — the methods used to create a legal entity identifier; — the syntax of the query and of the response used in the resolution of the representation of an authoritative legal entity identifier; — the methods used for the resolution of the representation of an authoritative legal entity identifier.

This document provides requirements, specifications and guidance for an architecture of a supplier-neutral industrial digital ecosystem. It includes a standardized connectivity and services architecture, and a standardized use case architecture with methods to specify atomically re-usable scenarios and events, which can be used to specify the characteristics of standardized industry use cases. NOTE 1 Examples of standard industry use cases included in the secondary business process are included in Annex A along with standardized use case architecture. This document gives: — guidance for an architecture applicable to the oil and gas, petrochemical, power generation, public utilities and other asset-intensive industries; — requirements for interoperability among systems of systems, systems (including hardware and software) and components included in the secondary business process of a plant, platform or facility at any given time; — guidance on how these interoperability requirements are to be achieved and sustained in support of operations in the same plant, platform or facility; — specifications enabling the specialization of a digital ecosystem concept for the requirements of the secondary business process in included industries; — guidance to industry participants, including owner/operators and their product and services suppliers, to support their secondary business process requirements using products, which interoperate based on the specifications included in this document. NOTE 2 This document is focused on interoperability requirements for systems which play roles in the secondary business process, including those in domains identified in Figure 7.

This document describes an approach for using ISO 16100 to achieve cooperation between software agents by exchanging manufacturing software unit (MSU) capability profiles. The exchanged profiles among agents describe the manufacturing capabilities requested by the requester and to be fulfilled by the performer.

This document specifies the use of the integrated resources necessary for the scope and information requirements for the representation of engineering property data that are used for product design, product validation and other purposes. NOTE 1 The application activity model in Annex F provides a graphical representation of the processes and information flows that are the basis for the definition of the scope of this document. The following are within the scope of this document: — descriptions and definitions of the manufactured product, the sample of the product and the testable version of the sample; — description of the composition and substance of the product; — description of the processes used in the measurement; — descriptions of the data values produced by the measurement, with the specification of the conditions in which the data is valid; — references to standards and other documents wherein sampling, measurement and other details of testing and measurement processes can be specified or described; — descriptions and qualifications of the personnel and or organizations responsible for the measurement; — specification of the requirements, conditions and tolerances to be satisfied in the measurement and a description of the outcome; — descriptions of the locations of the measurement process and the effectivity of the results; — descriptions of the approval that establishes the validity of the measurements and the use of the properties for product design, design validation and other product characteristics such as structural integrity. NOTE 2 Data representations sometimes need to be archived to meet legal and regulatory requirements and to meet quality objectives. The following are outside the scope of this document: — data describing rules, guidelines and expert knowledge in the testing of products; — names of properties and test methods; — data describing why a decision was made to use a particular process; — scheduling data for measurement processes; — algorithms used for data evaluation and data processing. NOTE 3 The names and definitions of properties and test methods are assumed to be provided in computer processable dictionaries, conforming to ISO 13584 Parts Libraries, which could classify measurement methods and their associated property types.

This document specifies an aggregation process that provides aggregated environmental performance evaluation data in accordance with a given environmental performance evaluation specification conforming to ISO 20140-2, by using a set of environmental performance evaluation data conforming to ISO 20140-5. This document does not specify any aggregation processes specific to particular implementations of manufacturing systems.

This document specifies a set of template definitions to describe the capability of a software unit of an automation solution that can be mapped to the functional requirements of a target manufacturing application. This document specifies how to develop and manage a software unit catalogue in terms of capability properties and defines mapping rules from capability profiles to a software unit catalogue.

This document specifies a formal description of the manufacturing change management (MCM) processes to provide an organizational and technical solution for the comprehensive mapping and processing of changes between production planning and operations. The aim of this document is to uniformly capture and track change measures, and to sensibly forecast and coordinate the capacities required for change processes in the planning and production departments. This document presents a data-oriented view for implementation of MCM. The most important aspect of the data-oriented view is that the central change element is linked to the objects of the digital factory (i.e. the process, the product and the resource). The basis for MCM and the different views presented in this document are production planning processes. ISO/TR 18828‑1 gives an overview of the ISO 18828 series and links the MCM to the other parts of ISO 18828, focussing on production planning processes, as well as information flows and key performance indicators. The following aspects are covered within this document: — processes of MCM; — roles in MCM; — data-oriented view of MCM; — workflow of MCM.

This document contains descriptions for the practical use for applying formulae as specified in ISO 22400-2 for key performance indicators for production control and monitoring. This document is intended to be applied in conjunction with the content of ISO 22400-2.

This document specifies a framework for describing an automation solution in terms of a set of capabilities provided by a set of manufacturing software units. The framework also defines a set of capability elements and composition rules to represent the interoperability criteria in terms of the automation system capability requirements of an enterprise application.

This document specifies a formal logic-based concept specialization approach to support the development of manufacturing reference models that underpin the necessary business specific knowledge models needed to support the configuration of global production networks. This document specifies the following: — the formal sematic model approach; — hierarchical levels for property specialization; — contexts for each level; — key properties at each level; — property relationships; — property axioms; — applicability rules. The following are within the scope of this document: — production networks for discrete product manufacture; — formal semantics for the configuration of global production networks; — system level formal semantics; — designed system formal semantics; — manufacturing business system formal semantics; — global production systems network formal semantics. The following are outside the scope of this document: — in-factory formal semantics; — formal semantics for the operation of global production networks.

This document specifies particular elements of a maturity model. These elements conform to ISO/IEC 33004. Organizations can use these elements in combination with their own assessment indicators to determine the maturity level of processes for data quality management as specified by ISO 8000‑61. The following are within the scope of this document: - some of the elements of a model for assessing organizational process maturity; - identifying those elements that exist in other standards (process capability levels, process attributes, ordinal scale for measuring process attributes and the scheme for derivation of process capability levels from process attribute rating); - specifying six maturity levels and process profiles to indicate when organizations have achieved each of the maturity levels; - providing guidance on how to assess the maturity level of an organization. Methods or procedures to improve organizational maturity are outside the scope of this document. This document can be used by the organization itself or by another party (including certification bodies) to perform assessment of the maturity. This document can be used in conjunction with, or independently of, quality management systems standards.

This document defines the detailed interface services and protocols used in a matching method based on multiple capability class structures. This document also defines a CPTI (Capability Profile Template Interface) Service Group, an Extended CPI (Capability Profile Interface) Service Group and an Extended Matcher Interface Service Group, which is extensions of the Type 1, Type 2 and Type 3 services, respectively, specified in ISO 16100-3:2005,5.4. This document also defines the CCSI (Capability Class Structure Interface) Service Group, an additional service group used to create, register, access and modify a capability class structure for the reference manufacturing domain models specified in ISO 16100-5:2009, Clause 6. This document also specifies detailed contents of the specific part of a capability profile template defined in ISO 16100-5:2009, Clause 7.