Standard

This document provides an overview of Digital Twin, describes the capabilities, range, characteristics and requirements, and establishes a well-defined conceptual model, reference model and reference architectural views including usage view, functional view, and network view. This document is applicable to all types of organizations (e.g., commercial enterprises, government agencies, not-for-profit organizations).

The document defines a conceptual model for the building of use cases; specifies a use case template ontology, i.e. vocabulary as well as conventions for describing and representing use case contents; provides guidance on building use case templates and on extending a use case ontology to cover the targeted standard; provides examples of use case templates and use cases; and specifies an implementation scheme that will allow use cases to be stored and shared in a repository.

This document provides a collection of representative use cases of Digital Twin applications in a variety of domains.

This document defines a structured description method, which describes the functionalities of IoT devices, including what functionalities an IoT device can provide, and how to use the functionalities of IoT device. In details, the contents: 1. Define concept of IoT Device Model: what is IoT Device Model, and how it works with underlying IoT communication protocols; 2. Specify structure of IoT Device Model: define the elements of Status, Profile, and Resource; Furthermore, specify the structure of Resource element, to describe the functionalities of IoT devices through Property, Service, and Event; 3. Specify construction method of IoT Device Model: how to build IoT device functionalities based on IoT Device Model; 4. Describe the device interoperability based on the IoT Device Model: IoT Device Model discovery, remote query, remote controlling, subscription and data uploading.

This document provides system life cycle processes to implement and maintain trustworthiness in an IoT system or service by applying and supplementing ISO/IEC/IEEE 15288:2015. The system life cycle processes are applicable to IoT systems and services common to a wide range of application areas.

This International Standard, within the context of methods and tools for MBSSE: (1) Provides terms and definitions related to MBSSE; (2) Defines MBSSE-specific processes for model-based systems and software engineering; the processes are described in terms of purpose, inputs, tasks, and outcomes; (3) Defines methods to support the defined tasks of each process; and (4) Defines tool capabilities to automate/semi-automate tasks or methods.

ISO/PAS 19450:2015 specifies Object-Process Methodology (OPM) with detail sufficient for enabling practitioners to utilise the concepts, semantics, and syntax of Object-Process Methodology as a modelling paradigm and language for producing conceptual models at various extents of detail, and for enabling tool vendors to provide application modelling products to aid those practitioners.

The document describes the common concepts, terminologies, characteristics, use cases and technologies (including data management, coordination, processing, network functionality, heterogeneous computing, security, hardware/software optimization) of edge computing for IoT systems applications. This document is also meant to assist in the identification of potential areas for standardization in edge computing for IoT. The document describes several use cases from different domains: Smart elevator, Smart video monitoring, Intelligent transport systems, Process control in smart factory, Virtual power plant, Automated crop monitoring and management system, Smart lightning system.

ISO/IEC 21823-3:2021 provides the basic concepts for IoT systems semantic interoperability, as described in the facet model of ISO/IEC 21823-1, including: (1) requirements of the core ontologies for semantic interoperability; (2) best practices and guidance on how to use ontologies and to develop domain-specific applications, including the need to allow for extensibility and connection to external ontologies; (3) cross-domain specification and formalization of ontologies to provide harmonized utilization of existing ontologies; (4) relevant IoT ontologies along with comparative study of the characteristics and approaches in terms of modularity, extensibility, reusability, scalability, interoperability with upper ontologies, and so on; and (5) use cases and service scenarios that exhibit necessities and requirements of semantic interoperability.

How Uniform Resource Name (URN) values are allocated in IEEE 802(R) standards is described in this amendment to IEEE Std 802(R)-2014.

Under development

IEC TR 62541-1:2020 which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.<br /> <br /> IEC 62541-1:2020 presents the concepts and overview of the OPC Unified Architecture (OPC UA). Reading this document is helpful to understand the remaining parts of this multi-part document set. Each of the other parts of IEC 62451 is briefly explained along with a suggested reading order.