IT in general

This document defines interfaces for device management of RFID systems. Interfaces are defined that provide for discovery, configuration, initialization and monitoring of RFID systems within the software system infrastructure (SSI).

This document only deals with devices that provide RFID related services. It does not distinguish the form factor of such RFID devices.

This document provides two distinct interface sets, one based on the GS1 EPCglobal DCI standard and the IETF SNMP RFCs and the other based on the Organization for the Advancement of Structured Information Standards (OASIS) DPWS standard. The definition of the Device Profile for RFID is referred to in this document as the RFID Device Management Profile, or RDMP.
Each interface option set provides interface definitions that provide ISO/IEC 24791-3 Client Endpoints and Services Endpoints with the mechanisms for:
— the discovery of the RFID devices and services on a local or remote subnet;
— a firmware upgrade service;
— a management service that implements configuration related functions;
— a monitoring service for reporting alerts, diagnostics, and performance information.
The two interface set definitions provided by this document allow for clients and services endpoints to implement and provide the services based on the specific characteristics of the RFID system to be implemented. Subclause 1.2 defines the Conformance requirements for systems that implement components of one or both of the interface sets.

ISO/IEC 11179-1:2015 provides the means for understanding and associating the individual parts of ISO/IEC 11179 and is the foundation for a conceptual understanding of metadata and metadata registries.
ISO/IEC 11179-1:2015 is applicable to the formulation of data representations, concepts, meanings and relationships to be shared among people and machines, independent of the organization that produces the data. It is not applicable to the physical representation of data as bits and bytes at the machine level.
In this part of ISO/IEC 11179-1:2015 (and all other parts), metadata refers to descriptions of data. It does not contain a general treatment of metadata.

An ISO/IEC 11179-based metadata registry (MDR) (hereafter referred to as a "registry") is a tool for the management of shareable data; a comprehensive, authoritative source of reference information about data. It supports the standardization and harmonization processes by recording and disseminating data standards, which facilitates data sharing among organizations and users. It provides links to documents that refer to data elements and to information systems where data elements are used. When used in conjunction with an information database, the registry enables users to better understand the information obtained.

A registry does not contain data itself. It contains the metadata that is necessary to clearly describe, inventory, analyze, and classify data. It provides an understanding of the meaning, representation, and identification of units of data. The standard identifies the information elements that need to be available for determining the meaning of a data element (DE) to be shared between systems.

The purpose of ISO/IEC TR 20943-1:2003 is to describe a set of procedures for the consistent registration of data elements and their attributes in a registry. ISO/IEC TR 20943-1:2003 is not a data entry manual, but a user's guide for conceptualizing a data element and its associated metadata items for the purpose of consistently establishing good quality data elements. An organization may adapt and/or add to these procedures as necessary.

The scope of ISO/IEC TR 20943-1:2003 is limited to the associated items of a data element: the data element identifier, names and definitions in particular contexts, and examples; data element concept; conceptual domain with its value meanings; and value domain with its permissible values.

There is a choice when registering code sets and other value domains in an ISO/IEC 11179 metadata registry. Some Registration Authorities treat these sets as value domains, and others treat them as data elements. For the purposes of ISO/IEC TR 20943-1:2003, the choice will always be to treat the sets as data elements unless explicitly stated. This choice is made to help illustrate the way to register many different kinds of data elements, including examples for registering standard code sets as data elements.

The purpose of this technical report is to describe a set of procedures for the consistent registration of value domains and their attributes in a registry. This technical report is not a data entry manual, but a user's guide for conceptualizing a value domain and its components for the purpose of consistently establishing good quality metadata. An organization may adapt and/or add to these procedures as necessary.

Specifies process requirements for the secure development of products used in industry automation and control systems. It defines a secure development life-cycle (SDL) including security requirements definition, secure design, secure implementation (including coding guidelines), verification and validation, defect management, patch management and product end-of-life. These requirements can be applied to new or existing processes for developing, maintaining and retiring hardware, software or firmware for new or existing products. These requirements apply to the developer and maintainer of the product, but not to the user of the product.

This document establishes the reference dictionary of the general description of low-voltage switchgear and controlgear classes based on defined properties.
This dictionary is used to facilitate the exchange in electronic format of data describing low-voltage switchgear and controlgear.
This document provides clear and unambiguous definitions of a limited number of properties and classes which are mainly used for presentation, selection and identification of products particularly in electronic catalogues.
Each property has an unambiguously defined meaning and naming, and, where relevant, a defined value list, a defined format and a defined unit.
The intention is not to cover manufacturer-specific features.

This document of IEC 63372 describes principles and methodologies, specifies requirements and provides guidance on quantification and communication of Carbon footprint (sum of GHG emissions and removals), emission reductions and avoided emissions from Electric and Electronic (EE) products and systems. This document is applicable to EE products and systems as a horizontal standard.

IEC 61406-2 complements IEC 61406-1 with specific rules for encoding characteristics of marked physical objects when relevant. This includes cases where the uniqueness of the Identification Link string is not limited to relating only to an individual item but may alternatively relate to a product type, lot or batch. 

IEC 63365:2022 applies to products used in the process measurement, control and automation industry. It establishes a concept and requirements for the digital nameplate and provides alternative electronically readable solutions (e.g. 2D codes, RFID or firmware) to current conventional plain text marking on the nameplate or packaging of products.
The digital nameplate information is contained in the electronically readable medium affixed to the product, the packaging or accompanying documents. The digital nameplate information is available offline without Internet connection. After electronic reading, all digital nameplate information is displayed in a human readable text format. The digital nameplate also includes the Identification Link String according to IEC 61406-1 which provides additional online information for the product.
This document does not specify the contents of the conventional nameplate, which are subject to regional or national regulations and standards.

This document defines an information meta model for the Asset Administration Shell. This information meta model will enable the access of information describing an asset.
This document focusses on Asset Administration Shells representing assets of manufacturing enterprises including produced products.
The Asset Administration Shell covers the entire life cycle of assets from conception to disposal.
This document focuses on the access of information of an Asset Administration Shell and its Submodels including SubmodelElements among two or more AAS user applications, potentially between different organizations including enterprises.
It defines an information meta model, including references and handling of identifiers, in an unambiguous way which is neutral to specific technologies or implementations.
The reference mechanisms will allow referencing entries (entities) in dictionaries and ontologies as well as asset related services.
The information meta model allows the association of asset services and asset related services to dedicated SubmodelElements.
This document does not describe, how implementation will implement the storage (persistence) or optimized retrieval of information.
This document does not describe technical interfaces (services) of the Administration Shell or other systems to exchange information, nor protocols or interaction patterns.
However, it is expected, that the principles of these technical interfaces (services), protocols or interaction patterns will follow the information meta-model of this document.
This document will allow to create data mappings to suitable technologies to be used in life cycle phases of an asset: XML, JSON, RDF, AutomationML (IEC 62714) and OPC UA (IEC 62541).
This document will define the information meta-model entities, which are to be mapped to suitable technologies.
This document does not describe individual data mappings.
This document does not describe, how Submodel templates guide the creation of Submodels.

This part 3 of the IEC 63278 series aims at the secure and interoperable exchange of information between stakeholders in value chains. This includes how integrity, authenticity, and confidentiality are realized within the AAS information model. It refines AAS security requirements from IEC 63278-1 affecting the structure of the information model as defined in IEC 63278-2 NP and defines the respective security information model complementary to IEC 63278-2.

This part of IEC 61360 series provides a formal model for data according to the scope as
given in IEC 61360-1 and ISO 13584-42, and thus provides a means for the computer-
sensible representation and exchange of such data.
The intention is to provide a common information model for the work of IEC SC3D and
ISO TC184/SC4, thus allowing for the implementation of dictionary systems dealing with data
delivered according to either of the standards elaborated by both committees.
The scope of this part of IEC 61360 is the common ISO/IEC dictionary schema based on the
intersection of the scopes of the two base standards IEC 61360-1 and ISO 13584-42.
The presented EXPRESS model represents a common formal model for the two standards
and facilitates a harmonization of both.
The IEC 61360-2 forms the master document. ISO 13584-42 contains a copy of the
IEC 61360-2 EXPRESS model in an informative annex
In a number of clauses, where the common EXPRESS model allows more freedom, IEC has
defined more restrictions which are found in the methodology part of IEC 61360-1.
Two schemas are provided in this part of IEC 61360 defining the two options that may be
selected for an implementation. Each of these options is referred to as a conformance class.
– The ISO13584_IEC61360_dictionary_schema2 provides for modelling and
exchanging technical data element types with associated classification scheme used in the
data element type definitions. It constitutes conformance class 1 of this part of IEC 61360.
– The ISO13584_IEC61360_language_resource_schema provides resources for permitting
strings in various languages. It has been extracted from the dictionary schema, since it
could be used in other schemata. It is largely based on the support_resource_schema from
ISO 10303-41:2000, and can be seen as an extension to that. It allows for the usage of one
specific language throughout an exchange context (physical file) without the overhead introduced
when multiple languages are used.
When used together with ISO 10303-21, each schema defines one single exchange format.
The exchange format defined by conformance class 1 is fully compatible with the ISO 13584
series.