This work is distributed under a Creative Commons Attribution License (http://creativecommons.org/licenses/by/3.0/).
Industry 4.0 Knowledge Graph
A Knowledge Graph to describe standards and standardization frameworks related to Industry 4.0 and Smart Manufacturing
Description may include but is not limited to: an abstract, a table of contents, a graphical representation, or a free-text account of the resource.
An account of the resource.
Description
A second property with the same name as this property has been declared in the dcterms: namespace (http://purl.org/dc/terms/). See the Introduction to the document "DCMI Metadata Terms" (http://dublincore.org/documents/dcmi-terms/) for an explanation.
A name given to the resource.
Title
A related resource that is a version, edition, or adaptation of the described resource.
Has Version
This term is intended to be used with non-literal values as defined in the DCMI Abstract Model (http://dublincore.org/documents/abstract-model/). As of December 2007, the DCMI Usage Board is seeking a way to express this intention with a formal range declaration.
Date of formal issuance (e.g., publication) of the resource.
Date Issued
A legal document giving official permission to do something with the resource.
A legal document giving official permission to do something with the resource. In this ontology denotes the license of a Standard.
Represent the license document for a given Standard
has License
Date on which the resource was changed.
Date Modified
alternative label
definition
note
preferred label
Family Name
mbox
name
Instance's DBpedia Resource
has DBpedia Resource
Examples of a Creator include a person, an organization, or a service.
An entity primarily responsible for making the resource.
has Creator
has unit
Represents Standards that are component of other Standards. This relation is not transitive
is Component Of
A relation between collections and entities, e.g. 'the Night Watch by Rembrandt is in the Rijksmuseum collection'; 'Davide is member of the Pen Club', 'Igor is one the subjects chosen for the experiment'.
is member of
è membro di
isPartOf
Standard A has influences in Standard B. For example, IEC_61499 hasInfluenceIn IEC_61804-2(EDDL)
was Generated By
indicates that some Standard Classification entity has a similar scope as another. This property most probably is symmetric but not transitive.
alignes With
Languages in which the document of the Standard is available, e.g., English, French, Spanish
Points to Languages in which the standard document is available, e.g., English, French, etc. Defined as subProperty of dcterms:language
hasAvailableLanguage
Links the Standardization Frameworks with the Dimensions.
has Dimension
Links the Dimensions with Layers.
has Dimension Layer
Describes the domain, in which the Publication is used, particularly, standards.
has Domain
Serves as a catalogue of International Classification For Standards
has ICS
Links the Standardization Frameworks with the Layers
has Layer
Indicates the list of Standards that are previous versions of a Standard. For example,IEC 60038:2009 has IEC 60038:1983+AMD1:1994+AMD2:1997,IEC 60038:1983/AMD2:1997,IEC 60038:1983/AMD1:1994,IEC 60038:1983,IEC 60038:1975/AMD1:1977,IEC 60038:1975,IEC 60038:1967,IEC 60038:1954,IEC 60038:1938,IEC 60038:1927 as previous versions.
has Previous Version
Specifies the Technical Committee or a Sub-Committee that is responsible for creation and maintenance of a standard
has Technical Committee
ISO 42010 relation between an architecture description on the on hand and stakeholders and concerns on the other.
identifies
Links the Standarization Frameworks with the Classification of Standards
is Described in
specifies that one publication is a part or a section of another publication. Mostly used to indicate that a sto:Standard is a part of standard familiy or group of standards.
is part of
An Standard is concerned with Relevant Subjects
is Relevant for
General property to represent any type of relation that connects two standards.
related To
has Associated Standard
Standard A uses the structure of Standard B. For example, OPC UA uses Structure Of IEC_61804 (EDDL)
use Structure Of
Defines that Standard A uses Standard B. For example, IEC_62714(AML) uses MathML.
uses
A relation specifying that a vewpoint regards a Concern.
frames
The relation declaring that a standard is relevant for a certain concern.
has Target Concern
A relation between two different concerns where dealing with the subject Concern supports in achieving the object concern
has numerical value
Abbreviated name of the thing.
has Abbreviated Name
Points the Standard with the name of the Industrial Domain
has Domain Name
Formation date of the Organization
has Formation Date
Indicates the current Edition/Version number of the document.
has Edition
Describes the name of the implementation or serialization format of the Publication, e.g., XML, Document, binary, batch
has Implementation Format
has Motivation
Specifies the objectives for the different ISA 95 levels.
has Objective
Point to the URL of a recognized Ontology representation of the Standard
has Ontology
Indicates the number of pages in the document.
has Pages
Publication date of the Publication
has Publication Date
Stability date of a publication. Publications are valid for a certain period, i.e., the Stability Period. This property defines the end of the stability period.
has Stability Date
The data specified is not actually a Date but an Year
Publication status of the Standard, e.g., Valid, Revised, Published, under preparation, Released
has Status
Specifies the tasks for the different ISA 95 levels.
has Task
Name of the Organization
Org Name
Name of the standard part.
std Part Name
A legal document giving official permission to do something with a Resource.
License Document
A Reference Architecture describes the structure of a system with its element types and their structures, as well as their interaction types, among each other and with their environment. Describing this, a Reference Architecture defines restrictions for an instantiation (concrete architecture). Through abstraction from individual details, a Reference Architecture is universally valid within a specific domain. Further architectures with the same functional requirements can be constructed based on the reference architecture. Along with reference architectures comes a recommendation, based on experiences from existing developments as well as from a wide acceptance and recognition by its users or per definition. [ISO/IEC42010] Note: It is important to distinguish the Reference Architecture from a Reference Architecture Description. While the first refers to a mental model or shared concept, the second is potentially only one of several different documents describing this model.
ISO 42010 definition of an Architecture Description
Term
Describes the class term. It refers to the terms that are in the standards documents
definedInStandard
Links the terms and the standards
Suply Chain Management Business Cycle.
Business Cycle SCM
Edgecross Layer
Describes the ISA95 levels to classify the industry Standards according to those levels. Eg., Device, SCADA, etc. It has strong relation to the RAMI Hierarchy levels
ISA 95 Level
Describes the layers of the standardization frameworks. In some cases, the layers are connected to dimensions of the frameworks.
Layer
PLM is the process of managing the entire lifecycle of a product from inception, through engineering design and manufacture, to service and disposal of manufactured products. Related areas are PLMManagement, Modeling Practice, Product Model Data exchange, Manufacturing Model Data, Product Catalog Data.
Product Development Life-Cycle Phase
Product Development Life Cycle
Collections of machines, equipment, and auxiliary systems organized to create goods and services from various resources.
Production System Life Cycle
Specifies a Publication. E.g., International Standards,Technical Specifications,Publicly Available Specifications,Amendments Technical Corrigenda,Interpretation Sheets,Technical Reports,Guides
Publication
Describes the Administration Shell concept to organize/classify standards into submodels
Admin Shell Sub Model
RAMI Hierarchy Level
RAMI IT Layer
RAMI Life Cycle Layer
It describes the different Life Cycle and Value Stream layers for the RAMI model according to the IEC 62890 Standard.
Represents the Domains in which the Standards can be used
RelevantDomain
A subject that is relevant in the context of a standard (IEC standards in specific). As specified in IEC Website .
Relevant Subject
A stakeholder is an individual, team, organization or classes thereof,having an interest in a concern and by extension an interest in the viewpoint and system.
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '4.1 STAKEHOLDERS' 'Page 20'
Define the standards organizations that develop and publish industry standards
StandardOrganization
Typically Standards are divided into parts. E.g., ISA 95 has part Part 1: Models and Terminology, Part 2: Object Model Attributes, etc.
Specifies that a given Publication is a Technical Specification
Technical Specifications are often published when the subject under question is still under development or when insufficient consensus for approval of an International Standard is available.Technical Specifications approach International Standards in terms of detail and completeness, but have not yet passed through all approval stages either because consensus has not been reached or because standardization is seen to be premature.
Technical Specification
A Stakeholder Group is a party of people who have common interests and concerns.
A stakeholder is everyone with an interest in a system.
This class contains types of stakeholders who share a common interest or task.
Stakeholder Group
Stakeholders are interpreted in the same manner as outlined by ISO 42010: '<system> individual, team, organization, or classes thereof, having an interest in a system'
Subclass of http://voag.linkedmodel.org/voag#StakeholderGroup (vocabulary not accessible).
Refers to a place called Washington D.C.
Washington D.C
Refers to a place called Beijing.
Beijing
Refers to a place called Berlin.
Berlin
Refers to a place called Boston.
Boston
Refers to a place called Chicago.
Chicago
Refers to a Country called China.
China
Refers to a place called Cologne.
Cologne
Refers to a place called Eumseong.
Eumseong
Refers to a place called Frankfurt.
Frankfurt
Refers to a place called Geneva.
Geneva
Refers to a Country called Germany.
Germany
Refers to a place called Hoehenkirchen-Siegertsbrunn.
Hoehenkirchen-Siegertsbrunn
Refers to a place called New York City.
New_York_City
Refers to a place called Paris.
Paris
Refers to a Country called South Korea.
South Korea
Refers to a Country called Switzerland.
Switzerland
Refers to a Country called United_States.
United States
Refers to a place called Valbonne.
Valbonne
Refers to a place called Arizona.
Arizona
Refers to a place called California.
_California
Refers to a place called Georgia.
Georgia
Refers to a place called Maryland.
Maryland
Refers to a place called Massachusetts.
Massachusetts
Refers to a place called Michigan.
Michigan
Refers to a place called New York.
New York
Refers to a place called North Carolina.
North Carolina
Refers to a place called Texas.
_Texas
Deu
The industrial internet of things (IIoT): An analysis framework
A survey on Internet of Things architectures
Artificial intelligence (AI) is intelligence exhibited by machines. In computer science, an ideal "intelligent" machine is a flexible rational agent that perceives its environment and takes actions that maximize its chance of success at some goal. Colloquially, the term "artificial intelligence" is applied when a machine mimics "cognitive" functions that humans associate with other human minds, such as "learning" and "problem solving". (source: wikipedia)
Artificial Intelligence
AMQP (Advanced Message Queuing Protocol): An open standard application layer protocol for message-oriented middleware. The defining features of AMQP are message orientation, queuing, routing (including point-to-point and publish-and-subscribe), reliability and security. (source: https://www.postscapes.com/internet-of-things-protocols/)
AMQP
ANSI
American National Standards Institute
The American National Standards Institute is a private non-profit organization that oversees the development of voluntary consensus standards for products, services, processes, systems, and personnel in the United States. The organization also coordinates U.S. standards with international standards so that American products can be used worldwide. ANSI accredits standards that are developed by representatives of other standards organizations, government agencies, consumer groups, companies, and others. These standards ensure that the characteristics and performance of products are consistent, that people use the same definitions and terms, and that products are tested the same way. ANSI also accredits organizations that carry out product or personnel certification in accordance with requirements defined in international standards.
ANT is a proprietary wireless sensor network technology featuring a wireless communications protocol stack that enables semiconductor radios operating in the 2.4 GHz Industrial, Scientific and Medical allocation of the RF spectrum (ISM band) to communicate by establishing standard rules for co-existence, data representation, signalling, authentication and error detection. (source: https://www.postscapes.com/internet-of-things-protocols/)
ANT
American Production and Inventory Control Society
APICS
Represents the classifications of the standards according to the submodels of the administration shell.
Administration Shell
Aeron - Efficient reliable UDP unicast, UDP multicast, and IPC message transport. (source: https://www.postscapes.com/internet-of-things-protocols/)
Aeron
AII Data Classification
AII Network Classification
AII Security Classification
The AllSeen Alliance is a nonprofit consortium dedicated to enabling and driving the widespread adoption of products, systems and services that support the Internet of Everything with an open, universal development framework supported by a vibrant ecosystem and thriving technical community' (source: https://www.postscapes.com/internet-of-things-protocols/)
AllSeen Alliance
Alliance Industrie du Futur
Alliance of Industrial Internet
工业互联网产业联盟
Alljoyn - An open source software framework that makes it easy for devices and apps to discover and communicate with each other. (source: https://www.postscapes.com/internet-of-things-protocols/)
Alljoyn
Association for Standardization of Automation and Measuring Systems
Association for Standardization of Automation and Measuring Systems or ASAM is an incorporated association under German law. Its members are primarily international car manufacturers, suppliers and engineering service providers from the automotive industry. The association coordinates the development of technical standards, which are developed by working groups composed of experts from its member companies. ASAM pursues the vision that the tools of a development process chain can be freely interconnected and allow a seamless exchange of data. The standards define protocols, data models, file formats and application programming interfaces (APIs) for the use in the development and testing of automotive electronic control units. A large amount of popular tools in the areas of simulation, measurement, calibration and test automation are compliant to ASAM standards. Compliance shall guarantee interoperability of tools from different vendors, allow data exchange without the need for converters, and facilitate the exchange of unambiguous specification between customers and suppliers.
Set up a test data management system on top of test systems that produce measured or calculated data from testing activities
ASAM ODS
Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' '2.2.2. Middleware enablement' 'Page 300'
RAMI Identification
Lifecycle Status
American Society of Mechanical Engineers
The American Society of Mechanical Engineers (ASME) is a professional association that, promotes the art, science, and practice of multidisciplinary engineering and allied sciences around the globe via continuing education, training and professional development, codes and standards, research, conferences and publications, government relations, and other forms of outreach.
ASME Y14.41 establishs requirements for model-based definition upon CAD software and those who use CAD software to create product definition within the 3D model.
ASME Y14.41
Process planning frames everything related to model, plan and manage business workflows and processes.
Process planning
RAMI Safety
RAMI Security
Automatic Id Data Capture Techniques
Automatic Id Data Capture Techniques domain
Technology with which a process or procedure is performed with minimal human intervention
Automation
B2MML or Business To Manufacturing Markup Language is an XML implementation of the ANSI/ISA-95 family of standards (ISA-95)
Business To Manufacturing Markup Language
IEC 62264
Broadband Forum
The Broadband Forum is a non-profit industry consortium dedicated to developing broadband network specifications. Members include telecommunications networking and service provider companies, broadband device and equipment vendors, consultants and independent testing labs (ITLs). Service provider members are primarily wire-line service providers (non-mobile) telephone companies.
CPE WAN Management Protocol
Digital Enhanced Cordless Telecommunications (DECT) is the ETSI standard for short-range cordless communications, which can be adapted for many applications and can be used over unlicensed frequency allocations world-wide.
BBF TR-069
The Federation of German Industries
The Federation of German Industries represents a large proportion of the German manufacturing industry.
BPEL
The Web Services Business Process Execution Language (WS-BPEL), commonly known as BPEL Business Process Execution Language, is a standard executable language for specifying actions within business processes with web services.
Business Process Execution Language
BPMN
Business Process Model and Notation is a graphical representation for specifying business processes in a business process model.
Business Process Model Notation
The Cloud and High Performance Computing (HPC): Effective Big Data processing and data management might imply the effective usage of Cloud and High Performance Computing infrastructures. This area is separately elaborated further in collaboration with the Cloud and High Performance Computing (ETP4HPC) communities.
BDVA Cloud and High Performance Computing
Effective communication and connectivity mechanisms are necessary in providing support for Big Data. This area is separately further elaborated, along with various communication communities, such as the 5G community.
BDVA Communication and Connectivity
Big Data often need support to maintain security and trust beyond privacy and anonymisation. The aspect of trust frequently has links to trust mechanisms such as blockchain technologies, smart contracts and various forms of encryption.
BDVA Cybersecurity and Trust
Data analytics to improve data understanding, deep learning and the meaningfulness of data.
BDVA Data Analytics
Principles and techniques for data management
BDVA Data Management
Optimised and scalable architectures for analytics of both data-at-rest and data-in-motion, with low latency delivering real-time analytics.
BDVA Data Processing Architectures
Privacy and anonymisation mechanisms to facilitate data protection. This is shown related to data management and processing as there is a strong link here, but it can also be associated with the area of cybersecurity.
BDVA Data Protection
Data sharing and trading are seen as important ecosystem enablers in the data economy, although closed and personal data present particular challenges for the free flow of data. The following two conceptual solutions – Industrial Data Platforms (IDPs) and Personal Data Platforms (PDPs) – introduce new approaches to addressing this particular need to regulate closed proprietary and personal data.
BDVA Data Sharing Platforms
Engineering and DevOps for building Big Data Value systems: This topic will be elaborated in greater detail along with the NESSI Software and Service community.
Data Visualisation and User Interaction
BDVA Engineering and DevOps
BDVA Strategic Research and Innovation Agenda
This Strategic Research and Innovation Agenda (SRIA) defines the overall goals, main technical and non-technical priorities, and a research and innovation roadmap for the European Public Private Partnership (PPP) on Big Data Value. The SRIA has been developed by the Big Data Value Association (BDVA), an industry-led organisation representing large businesses, small and medium-sized enterprises (SMEs), and research organisations in Europe.
BDVA SIRA
Standardisation of Big Data technology areas to facilitate data integration, sharing and interoperability
BDVA Standards
IoT, CPS, Edge and Fog Computing: A main source of Big Data is sensor data from an IoT context and actuator interaction in Cyber Physical Systems. In order to meet real-time needs it will often be necessary to handle Big Data aspects at the edge of the system. This area is separately elaborated further in collaboration with the IoT (Alliance for Internet of Things Innovation (AIOTI)) and CPS communities
BDVA IoT CPS and Edge Computing
The term Blockchain refers to a set of technologies for distributed databases.
Blockchain
Bluetooth works in the 2.4 GHz ISM band and uses frequency hopping. With a data rate up to 3 Mbps and maximum range of 100m. Each application type which can use Bluetooth has its own profile. (source: https://www.postscapes.com/internet-of-things-protocols/)
Bluetooth
Computer-Aided Design
CAD
A key group of international partners representing Europe, the USA, China, Japan and Korea who has joined a strategic EU funded 7th Framework initiative that will look at global standards, regulatory and other issues concerning RFID and its role in realising an Internet of Things. (source: https://www.postscapes.com/internet-of-things-protocols/)
CASAGRAS
Content-Centric Networking (CCN). Next-gen network architecture to solve challenges in content distribution scalability, mobility, and security. CCN directly routes and delivers named pieces of content at the packet level of the network, enabling automatic and application-neutral caching in memory wherever it’s located in the network. The result? Efficient and effective delivery of content wherever and whenever it is needed. Since the architecture enables these caching effects as an automatic side effect of packet delivery, memory can be used without building expensive application-level caching services. (source: https://www.postscapes.com/internet-of-things-protocols/)
CCN
Specification for Energy Management
CGMES: Common Grid Model Exchange Specification
Cloud Computing
Cloud computing is the on-demand availability of computer system resources, especially data storage and computing power, without direct active management by the user.
Protection of Computer Systems from damage of all kinds
Cyber Security
DDS (Data-Distribution Service for Real-Time Systems): The first open international middleware standard directly addressing publish-subscribe communications for real-time and embedded systems. (source: https://www.postscapes.com/internet-of-things-protocols/)
DDS
DIN
Deutsches Institut für Normung
Deutsches Institut für Normung e.V. (DIN; in English, the German Institute for Standardization) is the German national organization for standardization and is the German ISO member body. DIN is a German Registered Association (e.V.) headquartered in Berlin. There are currently around thirty thousand DIN Standards, covering nearly every field of technology
German Institute for Standardization
Lifecycle record of technical objects - Part 1: Structural and content-related specifications
Die EN 50128 ist eine Europäische Norm für sicherheitsrelevante Software der Eisenbahn, sowohl strecken- als auch zugseitig. Zusammen mit der EN 50129 für die Hardware und den Zulassungsprozessen ist die EN 50128 eine Spezialisierung der EN 61508. Die EN 50128 ist eine Prozessnorm. Sie stellt dar, welche Verfahren, Prinzipien und Maßnahmen anzuwenden sind, damit die Software als sicher gilt.
DIN EN 50128
Railway applications - Communications, signalling and processing systems - Safety related electronic systems for signalling
Für alle Eisenbahnsignalsysteme, -Teilsysteme und -Einrichtungen sind jedoch Gefährdungsanalyse und Risikobewertungsprozesse, wie in DIN EN 50126 und in dieser Norm definiert, notwendig, um die Sicherheitsanforderungen zu identifizieren.
Specifies risk analysis for railway systems
DIN EN 50129
Railway applications - Rolling stock - Electronic equipment
Diese Norm wird bei der Konstruktion, Fertigung und Prüfung von auf Schienenfahrzeugen eingebauten elektronischen Betriebsmitteln verwendet. Sie beschreibt außerdem die elektrischen sowie die Umweltbedingungen für den Betrieb. Die Norm gilt für alle elektronischen Betriebsmittel für die Steuerung, die Regelung, den Schutz, die Diagnose, die Versorgung und so weiter, die auf Schienenfahrzeugen installiert sind. Als ein elektronisches Betriebsmittel gilt dabei ein Betriebsmittel, das hauptsächlich aus Halbleiterbauelementen und üblicherweise zugehörigen Bauelementen aufgebaut ist. Auch Sensoren (Strom, Spannung, Geschwindigkeit und so weiter) und bestückte Leiterplatten von Zündeinheiten für leistungselektronische Geräte sind von dieser Norm umfasst. Vollständige Zündeinheiten und leistungselektronische Schaltkreise sind in EN 61287-1 enthalten. Die Norm umfasst die Betriebsbedingungen, die Konstruktionsanforderungen, die Dokumentation und die Prüfung der elektronischen Betriebsmittel sowie die grundlegenden Hardware- und Softwareanforderungen, die für ein leistungsfähiges, zuverlässiges Betriebsmittel als erforderlich erachtet werden. Zuständig ist das DKE/UK 351.1 "Fahrzeuge" der DKE Deutsche Kommission Elektrotechnik Elektronik Informationstechnik in DIN und VDE.
EN 50155:2017 is an international standard covering electronic equipment used on rolling stock for railway applications. The standard covers aspects of this electronic equipment, including temperature, humidity, shock, vibration, and other parameters. A copy of the standard may be purchased from authorised standards agencies, e.g. BSI in the UK.
DIN EN 50155
Railway applications - Communication, signalling and processing systems - Safety-related communication in transmission systems
This European Standard is applicable for safety-relevant electronic systems which use a transmission system for digital communication purposes which has not been necessarily designed for safety-relevant applications and which - remains under the control of the designer and does not change during the life cycle, or - which is partly unknown and also does not remain constant, for which unauthorized access can be excluded, however, or - which is not under control of the designer and where unauthorized access shall also be considered. The responsible Committee is Subcommittee UK 351.3 "Bahn-Signalanlagen" ("Signalling systems for railways") of the DKE (German Commission for Electrical, Electronic and Information Technologies) at DIN and VDE.
DIN EN 50159
Functional safety - Safety instrumented systems for the process industry sector - Part 1: Framework, definitions, system, hardware and software requirements
This standard gives requirements for the specification, design, installation, operation and maintenance of a safety instrumented system (SIS), so that it can be confidently entrusted to achieve or maintain a safe state of the process. This standard has been developed as a process sector implementation of IEC 61508.
DIN EN 61511
ISO 13849 is a safety standard which deals with safety-related design principles of employed control systems to establish different safety Performance Levels (PL). It replaced EN 954-1 in December 2011. Part 1 defines the general principles for design. Part 2 describes the validation.
DIN EN ISO 13849
General requirements for the competence of testing and calibration laboratories
DIN EN ISO/IEC 17025 legt allgemeine Anforderungen an die Kompetenz, an die Unparteilichkeit und für die einheitliche Arbeitsweise von Laboratorien fest. Die Norm ist auf alle Organisationen anwendbar, die Labortätigkeiten durchführen, unabhängig von der Anzahl der Mitarbeiter. Sie reiht sich in die Normenreihe DIN EN ISO/IEC 17000 ein. Kunden von Laboratorien, Behörden, Organisationen und Programme, die eine Begutachtung unter Gleichrangigen anwenden, Akkreditierungsstellen und andere können diese Norm zur Bestätigung oder Anerkennung der Kompetenz von Laboratorien nutzen.
ISO 17025 specifies general requirements for laboratories.
DIN EN ISO/IEC 17025
Geometrical product specifications (GPS) - Matrix model (ISO 14638:2015); German version EN ISO 14638:2015
DIN EN ISO 14638:2015-12
Combining OPC Unified Architecture and Automation Markup Language.
DIN SPEC 16592
RM-SA - Reference Model for Industrie 4.0 Service Architectures - Part 1: Basic Concepts of an Interaction-based Architecture; Text in English
DIN SPEC 16593-1:2018-04
Reference architecture of a security gateway for the exchange of industry data and services
security gateway for data protection of personal data
DIN SPEC 27070
Document
Reference Architecture Model Industrie 4.0 (RAMI4.0) English translation of DIN SPEC 91345:2016-04
DIN SPEC 91345:2016-04
Reference Model for Industrial Cloud Federation
ensuring interoperability and communication of IT systems in cloud scenarios
DIN SPEC 92222
Data & Marketing Association
The Data & Marketing Association (formerly, Direct Marketing Association), also known as the DMA, is a trade organization for marketers which seeks to advance and protect responsible data-driven marketing.
DMA
Dimensional Metrology Standards Consortium (DMSC) is to identify urgently needed standards in the field of dimensional metrology, and to promote, foster, and encourage the development and interoperability of these standards, along with related and supporting standards that will benefit the industry as a whole.
Dimensional Metrology Standards Consortium
Datagram Transport Layer - The DTLS protocol provides communications privacy for datagram protocols. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery. The DTLS protocol is based on the Transport Layer Security (TLS) protocol and provides equivalent security guarantees. (source: https://www.postscapes.com/internet-of-things-protocols/)
DTLS
Data Market Austria
The Data Transfer Project (DTP) extends data portability beyond a user’s ability to download a copy of their data from their service provider (“provider”), to providing the user the ability 1 to initiate a direct transfer of their data into and out of any participating provider. The Data Transfer Project is an open source initiative to encourage participation of as many providers as possible. The DTP will enhance the data portability ecosystem by reducing the infrastructure burden on both providers and users, which should in turn increase the number of services offering portability. The protocols and methodology of the DTP enable direct, service-to-service data transfer with streamlined engineering work.
Data Transfer Project
The Data Transfer Project Whitepaper provides a brief overview on the intends of the Data Transfer Project and the targeted approach.
Data Transfer Project Whitepaper
Data Transfer Project Overview and Fundamentals
These are business Decision makers
Decision maker
Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15' 'Priyanka'
DigiMesh is a proprietary peer-to-peer networking topology for use in wireless end-point connectivity solutions. (source: https://www.postscapes.com/internet-of-things-protocols/)
DigiMesh
DMA Architecture
This document presents the DMA Data Technology Specification and Development Roadmap regarding the ongoing work in WP6 of the DMA project. The document relates to deliverable D2.2 “D2.2 Community-driven Data-Services Ecosystem Requirements (1st version)” which formulates the requirements of the DMA community. It will be explained in what way the requirements formulated in D2.2 are going to be addressed. The document gives an overview about the components which are going to be developed in WP6 and how these components are planned to be employed to provide DMA core services. The expected outputs of these services are described and a procedure of describing a 3rd party service for DMA platform is addressed.
DMA Service Technology Specification and Development Roadmap
The architecture description of the Data Transfer Project has not yet been published in a sufficient manner.
Data Transfer Project Architecture
DTP Deployment
DTP Ecosystem
DTP Security & Privacy
DTP System
European Union Agency for Network and Information Security
ENISA provides recommendations on cybersecurity, supports policy development and its implementation, and collaborates with operational teams throughout Europe.
ENISA
Cloud Computing - Benefits, risks and recommendations for information security
ENISA, supported by a group of subject matter expert comprising representatives from Industries, Academia and Governmental Organizations, has conducted, in the context of the Emerging and Future Risk Framework project, an risks assessment on cloud computing business model and technologies. The result is an in-depth and independent analysis that outlines some of the information security benefits and key security risks of cloud computing. The report provide also a set of practical recommendations.Produced by ENISA with contributions from a group of subject matter expert comprising representatives from Industry, Academia and Governmental Organizations, a risk assessment of cloud computing business model and technologies. This is an in-depth and independent analysis that outlines some of the information security benefits and key security risks of cloud computing. The report provide also a set of practical recommendations. It is produced in the context of the Emerging and Future Risk Framework project.
ENISA Cloud Computing
ETSI
European Telecommunications Standards Institute
The European Telecommunications Standards Institute (ETSI) is an independent, not-for-profit, standardization organization in the telecommunications industry (equipment makers and network operators) in Europe, headquartered in Sophia-Antipolis, France, with worldwide projection. ETSI produces globally-applicable standards for Information and Communications Technologies (ICT), including fixed, mobile, radio, converged, broadcast and internet technologies.
Digital Enhanced Cordless Telecommunications
Low Throughput Networks
Machine-to-Machine communications and the Internet of Things (IoT) involve the connection of potentially billions of connected objects which need only low throughput connectivity. The anticipated benefits of creating new dedicated IoT Low Throughput Networks (LTN) include lower costs, the creation of new applications, a reduction in electromagnetic radiation by improving data transmission efficiency LTN are expected to be crucial to the success of IoT standardization and implementation, and to provide the basis for many new and innovative applications.
ETSI LTN
ETSI ULE
DECT Ultra Low Energy (DECT ULE) is a technology based on DECT, and intended for Machine-to-Machine communications such as Home and Industrial automation. The main characteristics of the technology are ultra-low power consumption (much lower than IEEE 802.11) and wider coverage (much wider than IEEE 802.15 and Bluetooth Low Energy).
Ultra Low Energy
EC-GSM-IoT (Extended Coverage-GSM-IoT): Enables new capabilities of existing cellular networks for LPWA (Low Power Wide Area) IoT applications. EC-GSM-IoT can be activated through new software deployed over a very large GSM footprint, adding even more coverage to serve IoT devices. (source: https://www.postscapes.com/internet-of-things-protocols/)
EC-GSM-IoT
The scope of the Paho project is to provide open source implementations of open and standard messaging protocols that support current and emerging requirements of M2M integration with Web and Enterprise middleware and applications. It will include client implementations for use on embedded platforms along with corresponding server support as determined by the community. (source: https://www.postscapes.com/internet-of-things-protocols/)
Eclipse Paho Project
Eddystone - A protocol specification that defines a Bluetooth low energy (BLE) message format for proximity beacon messages. (source: https://www.postscapes.com/internet-of-things-protocols/)
Eddystone
Edgecross Architecture
Edgecross Consortium
Edgecross Edgecomputing Layer
Edgecross FA
Edgecross IT Systems Layer
Edgecross Whitepaper
Edgecross Consortium to Address Edge Integration in IIoT-enabled Architectures
Electrotechnical
Electrotechnical domain
EnOcean is a an energy harvesting wireless technology which works in the frequencies of 868 MHz for europe and 315 MHz for North America. The transmit range goes up to 30 meter in buildings and up to 300 meter outdoor. (source: https://www.postscapes.com/internet-of-things-protocols/)
EnOcean
In product development, an end user (sometimes end-user) is a person who ultimately uses or is intended to ultimately use a product. (source: wikipedia)
End User
EnterpriseIntegration
Enterprise Integration deals primarily with system interconnection, electronic data interchange, product data exchange and distributed computing environments.
Enterprise Control
Enterprise Control Domain
Information System Authority of Estonia
BDV SRIA European Big Data Value Strategic Research and Innovation Agenda version 4.0 October 2017
The FIWARE platform contains market-ready open source software, combining components that enable the connection to IoT with Context Information Management and Big Data services in the Cloud.
FIWARE Architecture
Internet of Things – Architecture IoT-A Final architectural reference model for the IoT v3.0
Internet of Things – Architecture IoT-A Deliverable D1.5 – Final architectural reference model for the IoT v3.0
The Generic Enablers (GEs) from the Advanced Web-based User Interface (WebUI) chapter cover a set of GEs that provide an advanced user experience using HTML-5 and a Web-based UI approach. The objective of the Advanced Web-based UI GE is to significantly improve the user experience for the Future Internet by adding new user input and interaction capabilities, such as interactive 3D graphics, immersive interaction with the real and virtual world via Augmented Reality, virtualizing the display and driving them over the network, and many more.
FIWARE Advanced Web-based User Interface
The Generic Enablers (GE) for the Apps Chapter together build an ecosystem of applications, services and data that is sustainable and fosters innovation as well as cross-fertilization. In particular the Apps Generic Enablers supports managing applications, services and data in a business framework across the whole service life cycle from creation through composition of applications and data to monetization and revenue sharing. A couple of basic GEs are important to realize the vision of such an applications, services and data business framework, which enables new business models in an agile and flexible way. Among them: a store, a marketplace, a revenue sharing engine, an application composer through mashup and a data visualization and analysis component. The Business Framework is heavily relying on USDL as common uniform description format for services which does not only focus on technical aspects of service, but also on business aspects as well as functional and non-functional service attributes. The Application Mashup GE aims at allowing end users without programming skills to quickly compose beautiful web applications and dashboards/cockpits mashing up widgets, operators and data sources from a shared catalogue. The Data Visualisation GE aims at creating agile, beautiful visualizations and meaningful reports useful to present the large variety of datasets. Data stakeholders will bring in the play as well as providing customisable data analytics.
FIWARE Applications Services and Data Delivery
The Cloud Chapter offers Generic Enablers (GEs) that comprise the foundation for designing a modern cloud hosting infrastructure that can be used to develop, deploy and manage Future Internet applications and services. Provided hosting capabilities are of several kinds and at several levels of resource abstraction -- aiming at the needs of different applications hosted on the cloud. The IaaS Data Center Resource Management (DCRM) GE is offering provisioning and life cycle management of virtualized resources (compute, storage, network) associated with virtual machines. The Object Storage GE offers provisioning and life cycle management of object-based storage containers and elements. The Job Scheduler GE offers the application to submit and manage computational jobs in a unified and scalable manner. The Edgelet Management GE offers the capability to host lightweight application components, called edgelets. Moreover, the IaaS Service Management (SM) GE provides the means to host complex applications. Lastly, the PaaS Management GE uses the above capabilities to offer provisioning and management of complete PaaS environments, leveraging also the Software Deployment and Configuration (SDC) GE which offers a flexible framework for installation and customization of software products (via Chef recipes) within individual virtual machines.
FIWARE Cloud Hosting
The Data/Context Management FIWARE chapter aims at providing outperforming and platform-like GEs that will ease development and provision of innovative Applications that require gathering, publication, processing and exploitation of information and data streams in real-time and at massive scale. Combined with GEs coming from the Apps Chapters, Application Providers will be able to build innovative business models based on exploitation of massive data provided by end users. FIWARE Data/Context Management GEs allow to gather information from context and other sources (Context Broker), mediate metadata among GEs and applications (Metadata pre-processor) query stored information through an homogeneous layer (Query Broker), , annotate existing information (Semantic Annotation), store and manage semantic information (Semantic Application Support), generate new knowledge from big data stores using a Map & Reduce paradigm (Big Data analysis) and react to different types of scenarios (Complex Event Processing). It also provides GEs for media management, as easy creation of advanced video applications (Stream Oriented GE) and specifically, video analysis in the compressed domain (CDVA).
FIWARE Data/Context Management
The deployment of the architecture of the IoT Service Enablement chapter is typically distributed across a large number of Devices, several Gateways and the Backend. A device is a hardware entity, component or system that either measures properties of a thing/group of things or influences the properties of a thing/group of things or both measures/influences. Sensors and actuators are devices. IoT Resources are computational elements (software) that provide the technical means to perform sensing and/or actuation on the device. The resource is usually hosted on the device. IoT GEs have been spread in two different domains: Gateway and Backend. While IoT Gateway GEs provide inter-networking and protocol conversion functionalities between devices and the IoT Backend GEs, the IoT Backend GEs provide management functionalities for the devices and IoT domain-specific support for the applications.
FIWARE IoT Services Enablement
The Future Internet services will always be exposed to different types of threats that can lead to severe misuse and damage. Creating secured and trusted services without sacrificing much of the desired functionality, usability, performance and cost efficiency is a great challenge, especially in a dynamic environment where new threats and attack methods emerge on a daily basis. The overall ambition of the Security Architecture of FIWARE is to demonstrate that the Vision of an Internet that is "secure by design" is becoming reality. Based on achievements to date and/or to come in the short-term (both from a technological but also a standardization perspective) we will show that "secure by design" is possible. Security, Privacy and Trust in FIWARE is mainly focusing on delivering tools and techniques to have the above-mentioned security needs properly met. Furthermore a decision making support and the automation of countermeasures allow alleviating the workload of users and administrators while raising their security awareness. The high-level Reference Architecture is formed by four main blocks of GEs: Cybersecurity, Identity and Access Management (and Enforcement), Privacy, Trust and Trustworthiness.
FIWARE Security
Functional Safety
Published under Open Content License.
GNU General Public License
todo
HTML
HTTP is the most widely used protocol for internet communication.
HTTP
HTTP/2 - Enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. (source: https://www.postscapes.com/internet-of-things-protocols/)
HTTP/2
HyperCat - An open, lightweight JSON-based hypermedia catalogue format for exposing collections of URIs. (source: https://www.postscapes.com/internet-of-things-protocols/)
HyperCat
International Business Machines Corporation
International Business Machines Corporation (commonly referred to as IBM) is an American multinational technology and consulting corporation, with corporate headquarters in Armonk, New York. IBM manufactures and markets computer hardware, middleware and software, and offers infrastructure, hosting and consulting services in areas ranging from mainframe computers to nanotechnology.On August 6, 2015, IBM announced that it will buy Merge Healthcare Inc for $1 billion.
Natural and applied sciences (Vocabularies)
This is ICS for Natural and applied sciences (Vocabularies)
Information technology. Office machines (Vocabularies)
This is ICS for Information technology. Office machines (Vocabularies)
Quantities and units
This is ICS for Quantities and units
ICS 01.060
Colour coding
This is ICS for Colour coding
ICS 01.070
Research and development
This is ICS for “Research and development ”
Quality in general
This is ICS for “Quality in general ”
Safety of machinery
This is ICS for Safety of machinery
ICS 13.110
Alarm and warning systems
This is ICS for Alarm and warning systems
ICS 13.320
Metrology and measurement in general
This is ICS for “Metrology and measurement in general ”
ICS 17.020
Test conditions and procedures in general
This is ICS for “Test conditions and procedures in general
ICS 19.020
Electrical and electronic testing
This is ICS for “Electrical and electronic testing”
ICS 19.08
Industrial automation systems in general
This is ICS for Industrial automation systems in general
Industrial process measurement and control
This is ICS for industrial process measurement and control
Wind turbine energy systems
This is ICS for “Wind turbine energy systems”
ICS 27.180
Electrical engineering in general
This is ICS for Electrical engineering in general
ICS 29.020
Relays
This is ICS for Relays
This is ICS for “Relays”
Power transmission and distribution lines
This is ICS for “Power transmission and distribution lines”
Electronic components in general
This is ICS for Electronic components in general
ICS 31.020
Mechanical structures for electronic equipment
This is ICS for Mechanical structures for electronic equipment
ICS 31.240
Data communication networks
This is ICS for “Data communication networks”
Receiving and transmitting equipment
This is ICS for Receiving and transmitting equipment
Emission
This is ICS for “Emission”
Immunity
This is ICS for “Immunity”
Telecontrol. Telemetering Including Supervising, Control and Data Acquisition System (SCADA)
This is ICS for Telecontrol. Telemetering Including Supervising, Control and Data Acquisition System (SCADA)
ICS 33.200
Languages used in information technology
This is ICS for “Languages used in information technology”
ICS 35.060
IT applications in industry
This is ICS for IT applications in industry
ID4me is a federated digital identity service that aims to provide two main functions: (1) Authorization of a user for access to any third party accepting ID4me identifiers (“single sign-on” on an Internet scale); (2) Controlled communication of the user’s personal information to the third parties accessed by the user.
ID4me
International Data Spaces Association
IDSA ensures that the special economic interests of business are specifically integrated into the research work of Industrial Date Space.
IDSA
IDS RAM Business Layer
IDS RAM Certification Perspective
IDS Data Market
IDS RAM Functional Layer
IDS RAM Governance Perspective
IDS RAM Information Layer
IDS Interoperability
IDS RAM Process Layer
Industrial Data Space Reference Architecture Model
IDS RAM
The IDS Security Architecture provides means to identify participants, protect communication and data exchange transactions between them, and control the use of data after it has been sent.
IDS RAM Security Perspective
IDS RAM System Layer
IDS REFERENCE ARCHITECTURE MODEL INDUSTRIAL DATA SPACE VERSION 2.0
Commission électrotechnique internationale
International Electrotechnical Commission
Is a non-profit, non-governmental international standards organization that prepares and publishes International Standards for all electrical, electronic and related technologies – collectively known as "electrotechnology". IEC standards cover a vast range of technologies from power generation, transmission and distribution to home appliances and office equipment, semiconductors, fiber optics, batteries, solar energy, nanotechnology and marine energy as well as many others. The IEC also manages three global conformity assessment systems that certify whether equipment, system or components conform to its International Standards.
Information technology -- General-Purpose Datatypes (GPD)
ISO/IEC 11404
IEC 14443
The ISO/IEC 14443 standard is a four-part international standard for contact-less smart cards operating at 13.56 MHz in close proximity (~10cm) with a reader antenna. This ISO standard describes the modulation and transmission protocols between card and reader to create interoperability for contact-less smart card products. There are two main communication protocols supported by the ISO/IEC 14443 standard, they are addressed as Type A and Type B. Most High Frequency (13.56 MHz) proximity tags are using these guidelines for their communication.
ISO/IEC 14443
The Common Criteria for Information Technology Security Evaluation (referred to as Common Criteria or CC) is an international standard (ISO/IEC 15408) for computer security certification
IEC 15408
Common Criteria
Information technology -- Automatic identification and data capture techniques -- Unique identification
ISO/IEC 15459-1:2014 specifies a unique string of characters for the identification of individual transport units. The character string is intended to be represented in a bar code label or other AIDC media attached to the entity to meet management needs. To address management needs, different types of entities are recognized in the various parts of ISO/IEC 15459, which allows different requirements to be met by the identities associated with each type. The rules for the unique identification for individual transport units, to identify physical logistical transfers, with the identity relevant for the duration of one or more items in the load being held or transported as part of that load, are defined and supported by example.
IEC 15459
ISO/IEC 24760: it defines terms for identity management, and also specifies core concepts of identity and identity management and their relationships. It is applicable to any information system that processes identity information. A bibliography of documents describing various aspects of identity information management is provided.
IEC 24760
ISO/IEC 27018:2014 establishes commonly accepted control objectives, controls and guidelines for implementing measures to protect Personally Identifiable Information (PII) in accordance with the privacy principles in ISO/IEC 29100 for the public cloud computing environment.
Business Continuity
ISO/IEC 27031:2011 describes the concepts and principles of information and comunication technology (ICT) readiness for business continuity, and provides a framework of methods and processes to identify and specify all aspects (such as performance criteria, design, and implementation) for improving an organization's ICT readiness to ensure business continuity.
ISO/IEC 27031
ISO/IEC 27036-4:2016 provides cloud service customers and cloud service providers with guidance on a) gaining visibility into the information security risks associated with the use of cloud services and managing those risks effectively, and b) responding to risks specific to the acquisition or provision of cloud services that can have an information security impact on organizations using these services.
ISO/IEC 27036
‘Privacy framework’1 provides a guideline that specifies a common privacy terminology, defines actors and roles in processing PII, describes privacy safeguarding considerations, and includes references to known privacy principles for Information technology. source: IIC SF
ISO/IEC 29100
Information technology -- Security techniques -- Entity authentication assurance framework
ISO/IEC 29115:2013 provides a framework for managing entity authentication assurance in a given context. In particular, it: - specifies four levels of entity authentication assurance; - specifies criteria and guidelines for achieving each of the four levels of entity authentication assurance; - provides guidance for mapping other authentication assurance schemes to the four LoAs; - provides guidance for exchanging the results of authentication that are based on the four LoAs; and - provides guidance concerning controls that should be used to mitigate authentication threats.
IEC 29115
Information technology -- Data structure -- Unique identification for the Internet of Things
ISO/IEC 29161:2016 establishes a unique identification scheme for the Internet of Things (IoT), based on existing and evolving data structures. This International Standard specifies the common rules applicable for unique identification that are required to ensure full compatibility across different identities. The unique identification is a universal construct for any physical object, virtual object, or person. It is used in IoT information systems that need to track or otherwise refer to entities. It is intended for use with any IoT media.
IEC 29161
ISO/IEC 29182-1: provides a general overview of the characteristics of a sensor network and the organization of the entities that comprise such a network. It also describes the general requirements that are identified for sensor networks.
IEC 29182-1
‘Privacy capability assessment model’ provides high-level guidance to organizations about assessing their capability to manage privacy-related processes.
IEC 29190
ISO/IEC/IEEE 42010
ISO/IEC/IEEE 42010:2011 defines requirements on the description of system, software and enterprise architectures. It aims to standardise the practice of architecture description by defining standard terms, presenting a conceptual foundation for expressing, communicating and reviewing architectures and specifying requirements that apply to architecture descriptions, architecture frameworks and architecture description languages.
IEC 42010
The IIRA is based on this standards
IEC 60027 (formerly IEC 27) is a technical international standard for letter symbols.
IEC 60027
Valid
Letter symbols to be used in electrical technology - Part 6: Control technology
This part of IEC 60027 is applicable to control technology. It gives names and symbols for quantities, signals and functions, and their units.
IEC 60038 specifies standard voltage values which are intended to serve as preferential values for the nominal voltage of electrical supply systems, and as reference values for equipment and system design.
IEC 60038
IEC standard voltages
IEC 60038:2009 specifies standard voltage values which are intended to serve as preferential values for the nominal voltage of electrical supply systems, and as reference values for equipment and system design. This seventh edition supersedes the sixth edition (1993), its Amendment 1 (1994) and its Amendment 2 (1997). It constitutes a technical revision. The significant technical changes are: -the addition of the values of 230 V (50 Hz) and 230/400 V (60 Hz) to Table 1;-the replacement of the utilization voltage range at LV by a reference to the relevant standard and an informative annex;- the addition of the value of 30 kV to Table 3;- the replacement of the value of 1 050 kV by 1 100 kV in Table 5. It has the status of a horizontal standard in accordance with IEC Guide 108.
The International Electrotechnical Vocabulary (IEV) serves to promote the global unification of terminology in the field of electrotechnology, electronics and telecommunications.
IEC 60050
Electropedia
Replaced
International Electrotechnical Vocabulary - Part 101: Mathematics
It has the status of a horizontal standard in accordance with IEC Guide 108.
International Electrotechnical Vocabulary - Part 351: Control technology
IEC 60050-351:2013 gives the general terminology used in control technology, as well as general terms pertaining to specific applications and associated technologies. This new edition reviews and complements the previous one. It has the status of a horizontal standard in accordance with IEC Guide 108.
International Electrotechnical Vocabulary. Chapter 371: Telecontrol
Terms on telecontrol, teleprotection and associated telecommunications for electric power systems. It has the status of a horizontal standard in accordance with IEC Guide 108.
Basic and safety principles for man-machine interface, marking and identification - Coding principles for indicators and actuators
Establishes general rules for assigning particular meanings to certain visual, acoustsic and tactile indications. It has the status of a Basic Safety Publication in accordance with IEC Guide 104.
Standard battery nomenclature describes portable dry cell batteries that have physical dimensions and electrical characteristics interchangeable between manufacturers.
IEC 60086
IEC 60204-1 / EN 60204 Safety of machinery – Electrical equipment of machines
Applies to the electrical and electronic equipment and systems of machines, including a group of machines working together in a coordinated manner, but excluding higher level system aspects (i.e. communications between systems).
IEC 60204
Withdrawn
Safety of machinery - Electrical equipment of machines - Part 11: Requirements for HV equipment for voltages above 1 000 V a.c. or 1 500 V d.c. and not exceeding 36 kV
IEC 60255
Measuring relays and protection equipment
Rules and requirements applicable to measuring relays and protection equipment.
Measuring relays and protection equipment - Part 127: Functional requirements for over/under voltage protection
IEC 60255-127:2010 specifies minimum requirements for over/under voltage relays. The standard includes specification of the protection function, measurement characteristics and time delay characteristics.
Measuring relays and protection equipment - Part 149: Functional requirements for thermal electrical relays
IEC 60255-149:2013 specifies minimum requirements for thermal protection relays. This standard includes specification of the protection function, measurement characteristics and test methodologies. The object is to establish a common and reproducible reference for evaluating dependent time relays which protect equipment from thermal damage by measuring a.c. current flowing through the equipment. Complementary input energizing quantities such as ambient, coolant, top oil and winding temperature may be applicable for the thermal protection specification set forth in this standard. This standard covers protection relays based on a thermal model with memory function.
Measuring relays and protection equipment - Part 151: Functional requirements for over/under current protection
IEC 60255-151:2009 specifies minimum requirements for over/under current relays. It includes a specification of the protection function, measurement characteristics and time delay characteristics. Defines the influencing factors that affect the accuracy under steady state conditions and performance characteristics during dynamic conditions.
Measuring relays and protection equipment - Part 1: Common requirements
IEC 60255-1:2009 specifies common rules and requirements applicable to measuring relays and protection equipment including any combination of devices to form schemes for power system protection such as control, monitoring and process interface equipment in order to obtain uniformity of requirements and tests. Covers all measuring relays and protection equipment used for protection within the power system environment.
Measuring relays and protection equipment - Part 27: Product safety requirements
IEC 60255-27:2013 describes the product safety requirements for measuring relays and protection equipment having a rated a.c. voltage up to 1 000 V with a rated frequency up to 65 Hz, or a rated d.c. voltage up to 1 500 V. Above these limits, IEC 60664-1 is applicable for the determination of clearance, creepage distance and withstand test voltage. This standard details essential safety requirements to minimize the risk of fire and hazards caused by electric shock or injury to the user. This new edition includes the following significant technical changes with respect to the previous edition:- the removal of tables and diagrams which are from other standards and referring instead directly to the source standard;- all aspects of IEC 60255-5 have been covered and this standard will be withdrawn.
Packaging of components for automatic handling.
In electrical engineering, IEC 60269 is a set of technical standards for low-voltage power fuses.
IEC 60286
Packaging of components for automatic handling - Part 3: Packaging of surface mount components on continuous tapes
IEC 60286-3:2013 is applicable to the tape packaging of electronic components without leads or with lead stumps, intended to be connected to electronic circuits. It includes only those dimensions that are essential for the taping of components intended for the above-mentioned purposes. This standard also includes requirements related to the packaging of singulated die products including bare die and bumped die (flip chips). This fifth edition cancels and replaces the fourth edition, published in 2007, as well as IEC 60286-3-1, published in 2009 and IEC 60286-3-2, published in 2009. It constitutes a full layout revision. In addition, this edition includes the following significant technical changes with respect to the previous edition:a) IEC 60286-3:2013 is applicable to the tape packaging of electronic components without leads or with lead stumps, intended to be connected to electronic circuits. It includes only those dimensions that are essential for the taping of components intended for the above-mentioned purposes. This standard also includes requirements related to the packaging of singulated die products including bare die and bumped die (flip chips). This fifth edition cancels and replaces the fourth edition, published in 2007, as well as IEC 60286-3-1, published in 2009 and IEC 60286-3-2, published in 2009.It constitutes a full layout revision. In addition, this edition includes the following significant technical changes with respect to the previous edition:a) integration of IEC 60286-3-1:2009 as type 1b (Packaging of surface mount components on continuous pressed carrier tapes);b) integration of IEC 60286-3-2:2009 as type 2b (Packaging of surface mount components on blister carrier tapes 4 mm in width).ntegration of IEC 60286-3-1:2009 as type 1b (Packaging of surface mount components on continuous pressed carrier tapes);b) integration of IEC 60286-3-2:2009 as type 2b (Packaging of surface mount components on blister carrier tapes 4 mm in width).
Packaging of components for automatic handling - Part 4: Stick magazines for electronic components encapsulated in packages of different forms
IEC 60286-4:2013 is applicable to stick magazines (including end stoppers) intended to be used for storage of electronic components, for transport from the manufacturer to the customer and for in-house use in the manufacturing plant. They are also used to feed automatic placement machines for surface mounting as well as for through-hole mounting of electronic components. This edition includes the following significant technical changes with respect to the previous edition: Clause 4 describes the guidelines for customer specific stick magazine design. It replaces the magazine design rules for IEC outlined components and rules for orientation of components in stick magazines which have been moved to Annexes A to D.
RLV-Redline version
Packaging of components for automatic handling - Part 5: Matrix trays
IEC 60286-5:2018 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.IEC 60286-5:2018 describes the common dimensions, tolerances and characteristics of the tray. It includes only those dimensions that are essential for the handling of the trays for the stated purpose and for placing or removing components from the trays. This edition includes the following significant technical changes with respect to the previous edition: - The generic rules for the design of matrix trays are given in this document. Newly developed trays which follow these rules will not be listed individually. Only those trays which conform to the design rules set forth herein are classified as 'standard trays' and are thus preferred for use.- An update of the matrix trays, which do not conform to the design rules set forth herein, are considered as 'non-standard trays' and are not preferred for use, is listed in Annex A.
Electrical Installations for Buildings is the International Electrotechnical Commission's international standard on electrical installations of buildings
IEC 60364
Analogue signals for process control systems.
Applicable to analogue direct current signals used in industrial-process measurement and control systems to transmit information between elements of systems. Does not apply to signals used entirely within an element.
IEC 60381
Analogue signals for process control systems. Part 1: Direct current signals
Analogue signals for process control systems. Part 2: Direct voltage signals
Applicable to analogue direct voltage signals used in industrial process measurement and control systems. lt specifies ranges of analogue direct voltage signals and the signal common; it also deals with ripple content. The analogue direct voltage signal, unlike the analogue direct current signal specified in IEC 60381-1, is not intended for transmission over long distances. This standard does not apply to signals used entirely within an element.
Analogue pneumatic signal for process control systems
Applies to analogue pneumatic signals used in process control systems to transmit information between the elements of systems and gives definitions, units and the recommended value of the range of the analogue pneumatic signal.
Alarm and electronic security systems
General equipment requirements for the performance, reliability, resilience, security and safety characteristics of supervised premises transceiver (SPT) installed in supervised premises and used in alarm transmission systems (ATS).
IEC 60839
Alarm and electronic security systems - Part 5-2: Alarm transmission systems - Requirements for supervised premises transceiver (SPT)
IEC 60839-5-2:2016 specifies the general equipment requirements for the performance, reliability, resilience, security and safety characteristics of supervised premises transceiver (SPT) installed in supervised premises and used in alarm transmission systems (ATS). A supervised premises transceiver can be a stand-alone device or an integrated part of an alarm system. These requirements also apply to the SPT sharing means of interconnection, control, communication and power supplies with other applications. The alarm transmission system requirements and classifications are defined within IEC 60839-5-1. This new edition includes the following significant technical changes with respect to the previous edition: reflects the current technological state of art (IP networks) ,harmonizes with the ATS categories introduced in IEC 60839-5-1:2014; introduces test requirements.
Alarm systems - Part 7-1: Message formats and protocols for serial data interfaces in alarm transmission systems – General
Describes the requirements for standard serial data interfaces in alarm transmission systems. Gives an outline of how alarm transmission systems are connected and the various types of serial data interfaces that might be employed.
Alarm systems - Part 7-2: Message formats and protocols for serial data interfaces in alarm transmission systems - Common application layer protocol
Specifies a common application layer protocol (message structure, formats and transmission procedures) to be used at standard interfaces in alarm transmission systems. Should be used at all such interfaces where equipment from one supplier is intended to inter-work with equipment from other suppliers.
Alarm systems - Part 7-3: Message formats and protocols for serial data interfaces in alarm transmission systems - Common data link layer protocol
Specifies the data link layer message structure, formats and transmission procedures which should be used at standard serial data interfaces in alarm transmission systems where the transmission network employed does not offer a standard protocol. Is necessary in order to ensure compatibility of equipment from different suppliers.
Alarm systems - Part 7-4: Message formats and protocols for serial data interfaces in alarm transmission systems - Common transport layer protocol
Specifies the transport layer message structure, formats and transmission procedures to be used at standard interfaces in alarm transmission systems. Should be used at all such interfaces where equipment from one supplier is intended to inter-work with equipment from other suppliers, and where the underlying system architecture does not provide the necessary facilities to support the common application layer.
Alarm systems - Part 7-5: Message formats and protocols for serial data interfaces in alarm transmission systems - Alarm system interfaces employing a two-wire configuration in accordance with ISO/IEC 8482
Specifies the requirements for standard interfaces using a two-wire connection employing ISO/IEC 8482 signalling for use between the control and indicating equipment of an alarm system and one or more alarm system transceivers connected to alarm transmission systems.
Alarm systems - Part 7-6: Message formats and protocols for serial data interfaces in alarm transmission systems - Alarm system interfaces employing ITU-T Recommendation V.24/V.28 signalling
Specifies the requirements for standard interfaces employing ITU-T V.24/V.28 signalling for communications between the control and indicating equipment of an alarm system and transmission equipment used for remote communications, where the transmission equipment is general purpose equipment. Is intended to be used as interfacing to standard modems, packet switching networks, X.25 PADs, etc.
Alarm systems - Part 7-7: Message formats and protocols for serial data interfaces in alarm transmission systems - Alarm system interfaces for plug-in alarm system transceivers
Specifies the requirements for standard interfaces between the control and indicating equipment (CIE) of an alarm system and an alarm system transceiver where the alarm system transceiver is intended to plug into a standard space inside the CIE of the alarm system.
GRAFCET specification language for sequential function charts
IEC 60848:2013 defines the GRAFCET specification language for the functional description of the behaviour of the sequential part of a control system. It specifies the symbols and rules for the graphical representation of this language, as well as for its interpretation and has been prepared for automated production systems of industrial applications. This third edition cancels and replaces the second edition published in 2002 and constitutes a global technical revision with the extended definition of the concept of variables introducing: internal variable, input variable and output variable.
Standardization of interconnections between broadcasting transmitters or transmitter systems and supervisory equipment.
Applies to all classes of transmitters for sound and television broadcasting. Deals with the interface between a transmitter (or system of transmitters) and the supervisory equipment which is intended to remotely monitor and/or control the transmitter(s).
IEC 60864
Standardization of interconnections between broadcasting transmitters or transmitter systems and supervisory equipment. Part 1: Interface standards for systems using dedicated interconnections
Applies to all classes of transmitters for sound and television broadcasting. Deals with the interface between a transmitter (or system of transmitters) and the supervisory equipment which is intended to remotely monitor and/or control the transmitter(s). Details the interconnections and facilities to be provided with a view to achieving compatibility between different types and makes of transmitters and supervisory equipment.
Standardization of interconnections between broadcasting transmitters or transmitter systems and supervisory equipment - Part 2: Interface standards for systems using data bus type interconnections
Deals with the interface between a transmitter (or system of transmitters) and the supervisory equipment which is entended to remotely monitor and/or control the transmitter(s). It details the interconnections and facilities to be provided with a view to achieving compatibility between different types and makes of transmitters and supervisory equipement.
Deals with the itnerface between a transmitter (or system of transmitters) and the supervisory equipment which is entended to remotely monitor and/or control the transmitter(s). It details the interconnections and facilities to be provided with a view to achieving compatibility between different types and makes of transmitters and supervisory equipement.
In electrical engineering and power system automation, the IEC 60870 series define systems used for telecontrol (supervisory control and data acquisition)
IEC 60870
Telecontrol equipment and systems - Part 2: Operating conditions - Section 1: Power supply and electromagnetic compatibility
Specifies classes for environmental conditions under which telecontrol equipment has to operate.
Telecontrol equipment and systems - Part 2: Operating conditions -Section 2: Environmental conditions (climatic, mechanical and othernon electrical influences)
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and control of geographically wides pread processes. Specifies classes for environmental conditions under which the various components of the systems have to operate.
Telecontrol equipment and systems - Part 5-101: Transmissionprotocols - Companion standard for basic telecontrol tasks
IEC 60870-5-101:2003+A1:2015 Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. Defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. The defined telecontrol companion standard utilizes standards of the IEC 60870-5 series of documents. This publication is of high relevance for Smart Grid. This consolidated version consists of the second edition (2003) and its amendment 1 (2015). Therefore, no need to order amendment in addition to this publication.
IEC 60870-5-101:2003+A1:2015 Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. Defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. The defined telecontrol companion standard utilizes standards of the IEC 60870-5 series of documents. nThis publication is of high relevance for Smart Grid. This consolidated version consists of the second edition (2003) and its amendment 1 (2015). Therefore, no need to order amendment in addition to this publication.
Telecontrol equipment and systems - Part 5: Transmission protocols - Section 102: Companion standard for the transmission of integrated totals in electric power systems
Standardizes the transmission of integrated totals representing the amount of electrical energy transferred between power utilities, or between a power utility and independent producers on a high voltage or medium voltage network. This publication is of high relevance for Smart Grid.
Standardizes the transmission of integrated totals representing the amount of electrical energy transferred between power utilities, or between a power utility and independent producers on a high voltage or medium voltage network.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5-103: Transmission protocols - Companion standard for the informative interface of protection equipment
Applies to protection equipment with coded bit serial data transmission for exchanging information with control systems. Defines a companion standard that enables interoperability between protection equipment and devices of a control system in a substation. This publication is of high relevance for Smart Grid.
Applies to protection equipment with coded bit serial data transmission for exchanging information with control systems. Defines a companion standard that enables interoperability between protection equipment and devices of a control system in a substation.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5-104: Transmission protocols - Network access for IEC 60870-5-101 using standardtransport profiles
IEC 60870-5-104:2006+A1:2016 Defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. This publication is of high relevance for Smart Grid. This consolidated version consists of the second edition (2006) and its amendment 1 (2012). Therefore, no need to order amendment in addition to this publication.
IEC 60870-5-104:2006+A1:2016 Defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. nThis publication is of high relevance for Smart Grid. This consolidated version consists of the second edition (2006) and its amendment 1 (2012). Therefore, no need to order amendment in addition to this publication.
Telecontrol equipment and systems. Part 5: Transmission protocols - Section One: Transmission frame formats
Covers asynchronous data transmission with half duplex and duplex link protocols operating with window size one for message transfers. Specifies the basic requirements for services to be provided by the link plus physical layers, for telecontrol applications. In particular it specifies standards on coding, formatting and synchronizing data frames of variable and filed lengths which meet specified data integrity requirements.
Telecontrol equipment and systems - Part 5: Transmission protocols - Section 2: Link transmission procedures
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. This publication is of high relevance for Smart Grid.
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5: Transmission protocols - Section 3: General structure of application data
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes; specifies rules for structuring application data units in transmission frames of telecontrol systems. This publication is of high relevance for Smart Grid.
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes; specifies rules for structuring application data units in transmission frames of telecontrol systems.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5: Transmission protocols - Section 4: Definition and coding of application information elements
Gives rules for defining information elements and presents a set of information elements, in particular of digital and analog process variables frequently used in telecontrol applications. This publication is of high relevance for Smart Grid.
Gives rules for defining information elements and presents a set of information elements, in particular of digital and analog process variables frequently used in telecontrol applications. nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5: Transmission protocols - Section 5: Basic application functions
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. It defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. This publication is of high relevance for Smart Grid.
Applies to telecontrol equipment and systems with coded bit serial data transmission for monitoring and controlling geographically widespread processes. It defines a telecontrol companion standard that enables interoperability among compatible telecontrol equipment. nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 5-6: Guidelines for conformance testing for the IEC 60870-5 companion standards
IEC 60870-5-6:2006 Specifies methods for conformance testing of telecontrol equipment, amongst substation automation systems and telecontrol systems, including front-end functions of SCADA. Facilitates interoperability by providing a standard method of testing protocol implementations. Is expected to minimize the risk of non-interoperability.
Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 2: Use of basic standards (OSI layers 1-4)
Considers the standards related to layers 1-4 of the OSI reference model and describes the role and the functions carried out by each layer. This publication is of high relevance for Smart Grid.
Considers the standards related to layers 1-4 of the OSI reference model and describes the role and the functions carried out by each layer.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 501: TASE.1 Service definitions
Defines the services provided by a telecontrol specific application-service-element - the Telecontrol Application Service Element No. 1 (TASE.1) - for the exchange of process data in telecontrol systems. This publication is of high relevance for Smart Grid.
Defines the services provided by a telecontrol specific application-service-element - the Telecontrol Application Service Element No. 1 (TASE.1) - for the exchange of process data in telecontrol systems.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Section 502: TASE.1 Protocol definitions
Specifies the protocol for the services provided by an application-service-element - the Telecontrol Application Service Element No. 1 (TASE.1) - to support the exchange of process data between telecontrol systems. This publication is of high relevance for Smart Grid.
Specifies the protocol for the services provided by an application-service-element - the Telecontrol Application Service Element No. 1 (TASE.1) - to support the exchange of process data between telecontrol systems.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 6-503: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - TASE.2 Services and protocol
IEC 60870-6-503:2014 specifies a method of exchanging time-critical control centre data through wide-area and local-area networks using a full ISO compliant protocol stack. It contains provisions for supporting both centralized and distributed architectures. This standard includes the exchange of real-time data indications, control operations, time-series data, scheduling and accounting information, remote program control and event notification. This new edition includes the following significant technical changes with respect to the previous edition: - certain objects were made informative; - services associated with the informative objects were made informative; - certain TASE.2 conformance blocks were made out-of-scope.
IEC 60870-6-503:2014 specifies a method of exchanging time-critical control centre data through wide-area and local-area networks using a full ISO compliant protocol stack. It contains provisions for supporting both centralized and distributed architectures. This standard includes the exchange of real-time data indications, control operations, time-series data, scheduling and accounting information, remote program control and event notification. This new edition includes the following significant technical changes with respect to the previous edition:n- certain objects were made informative;n- services associated with the informative objects were made informative;n- certain TASE.2 conformance blocks were made out-of-scope.
Telecontrol equipment and systems - Part 6: Telecontrol protocol s compatible with ISO standards and ITU-T recommendations - Sect ion 601: Functional profile for providing the connection-oriente d transport service in an end system connected via permanent acc ess to a packet switched data network
Defines the functional profile which provides the connection-oriented transport service in an end system connected via permanent access to a packet switched data network.nThis publication is of high relevance for Smart Grid.
Telecontrol equipment and systems - Part 6-701: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.1 application service in end systems
Describes the functional profile which defines the provision of the TASE.1 communication services between two control centre end systems.nThis publication is of high relevance for Smart Grid
Telecontrol equipment and systems - Part 6-702: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - Functional profile for providing the TASE.2 application service in end systems
IEC 60870-6-702:2014 is a functional profile (FP) and defines the provision of the TASE.2 communications services between two control centre end systems. It is supported by the transport services implemented in accordance with transport-profiles defined for the type of network that interconnects the control centre end systems. The main changes with respect to the previous edition are listed below: - certain objects were moved from being normative to informative - certain TASE.2 conformance blocks have been made out-of-scope.
Telecontrol equipment and systems - Part 6-802: Telecontrol protocols compatible with ISO standards and ITU-T recommendations - TASE.2 Object models
IEC 60870-6-802:2014 specifies a method of exchanging time-critical control centre data through wide-area and local-area networks using a full ISO compliant protocol stack. It contains provisions for supporting both centralized and distributed architectures. The standard includes the exchange of real-time data indications, control operations, time series data, scheduling and accounting information, remote program control and event notification. This new edition includes the following significant technical changes with respect to the previous edition: -certain objects have been changed from informative to normative; - certain TASE.2 conformance blocks have been made out of scope.
Photovoltaic devices
IEC 60904
Binary direct voltage signals for process measurement and control systems
Applies to non-multiplexed two wire binary direct voltage signals of nominal 24 V level that are used in industrial-process measurement and control systems to transmit information between elements of systems.
Electromagnetic compatibility (EMC)
Terms of basic importance to concepts and practical applications in the design and evaluation of electromagnetically compatible systems.
Redline version
Electromagnetic compatibility (EMC) - Part 6-2: Generic standards - Immunity standard for industrial environments
IEC 61000-6-2:2016 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document. IEC 61000-6-2:2016 for EMC immunity requirements applies to electrical and electronic equipment intended for use in industrial locations, as described below. Immunity requirements in the frequency range 0 Hz to 400 GHz are covered. No tests need to be performed at frequencies where no requirements are specified. This generic EMC immunity standard is applicable if no relevant dedicated product or product-family EMC immunity standard exists. This third edition cancels and replaces the second edition published in 2005. This edition constitutes a technical revision.
Safety requirements for electrical equipment for measurement, control, and laboratory use
IEC 61010 specifies safety requirements for electrical equipment and their accessories .
IEC 61010
Safety requirements for electrical equipment for measurement, control, and laboratory use - Part 2-012: Particular requirements for climatic and environmental testing and other temperature conditioning equipment
IEC 61010-2-012:2016 specifies safety requirements for electrical equipment and their accessories within the categories a) through c), wherever they are intended to be used, whenever that equipment incorporates one or more of the following characteristics:- A REFRIGERATING SYSTEM that is acted on or impacted by an integral heating function such that the combined heating and cooling system generates additional and/or more severe HAZARDS than those for the two systems if treated separately.- The materials being treated in the intended application introduce significant heat into the REFRIGERATING SYSTEM that the cooling system in the application yield additional and/or more severe HAZARDS than those for the cooling system if operated at the maximum RATED ambient alone.- An irradiation function for the materials being treated presenting additional HAZARDS.- A function to expose the materials being treated to excessive humidity, carbon dioxide, salt mist, or other substances which may result in additional HAZARDS.- A function of MECHANICAL MOVEMENT presenting additional HAZARDS.- Provision for an OPERATOR to walk-in to the operating area to load or unload the materials being treated.It has the status of a group safety publication in accordance with IEC Guide 104. This publication is to be read in conjunction with IEC 61010-1:2010.
Safety requirements for electrical equipment for measurement, control, and laboratory use - Part 2-201: Particular requirements for control equipment
IEC 61010-2-201:2017 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.IEC 61010-2-201:2017 specifies safety requirements and related verification tests for any product performing the function of control equipment and/or their associated peripherals. In addition, these products have as their intended use the command and control of machines, automated manufacturing and industrial processes, e.g. discrete and continuous control.This second edition cancels and replaces the first edition published in 2013. This edition constitutes a technical revision. This second edition includes the following significant technical changes with respect to the previous edition;a) clarify, change, delete definitions which were causing confusion,b) change and clarify the temperature testing methodology,c) change documentation methodologies allowed,d) change some terminal markings,e) add clarity to some of the informative annexes,f) add Annex E with changes,g) add Annexes AA – FF.
IEC 61010-2-201:2017 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.nnIEC 61010-2-201:2017 specifies safety requirements and related verification tests for any product performing the function of control equipment and/or their associated peripherals. In addition, these products have as their intended use the command and control of machines, automated manufacturing and industrial processes, e.g. discrete and continuous control.nThis second edition cancels and replaces the first edition published in 2013. This edition constitutes a technical revision. This second edition includes the following significant technical changes with respect to the previous edition;na) clarify, change, delete definitions which were causing confusion,nb) change and clarify the temperature testing methodology,nc) change documentation methodologies allowed,nd) change some terminal markings,ne) add clarity to some of the informative annexes,nf) add Annex E with changes,ng) add Annexes AA – FF.
Safety requirements for electrical equipment for measurement, control and laboratory use - Part 2-202: Particular requirements for electrically operated valve actuators
IEC 61010-2-202:2016 specifies the safety requirements for electric ACTUATORs and SOLENOIDs, as applied to valves, intended to be installed in an industrial process or discrete control environment. This publication is to be read in conjunction with IEC 61010-1:2010.
IEC 61131 is an IEC standard for programmable controllers. It was known as IEC 1131 before the change in numbering system by IEC. The parts of the IEC 61131 standard are prepared and maintained working group 7, programmable control systems, of subcommittee SC 65B of Technical Committee TC65 of the IEC.
IEC 61131
Fieldbus
Fieldbus is the name of a family of industrial computer network protocols used for real-time distributed control, standardized as IEC 61158. A complex automated industrial system such as manufacturing assembly line usually needs a distributed control system an organized hierarchy of controller systems to function. In this hierarchy, there is usually a Human Machine Interface (HMI) at the top, where an operator can monitor or operate the system. This is typically linked to a middle layer of programmable logic controllers (PLC) via a non-time-critical communications system (e.g. Ethernet). At the bottom of the control chain is the fieldbus that links the PLCs to the components that actually do the work, such as sensors, actuators, electric motors, console lights, switches, valves and contactors
IEC 61158
Design review
This International Standard makes recommendations for the implementation of design review as a means of verifying that the design input requirements have been met and stimulating the improvement of the product's design. The intention is for it to be applied during the design and development phase of a product's life cycle.
Safety of machinery - Indication, marking and actuation
Specifies requirements for visual, acoustic and tactile methods of indicating safety-related information
IEC 61310
Safety of machinery - Indication, marking and actuation - Part 1: Requirements for visual, acoustic and tactile signals
Specifies requirements for visual, acoustic and tactile methods of indicating safety-related information, at the human-machine interface and to exposed persons. It specifies a system of colours, safety signs, markings and other warnings, intended for use in the indication of hazardous situations and health hazards and for meeting certain emergencies. It also specifies ways of coding visual, acoustic and tactile signals for indicators and actuators to facilitate the safe use and monitoring of the machinery. It includes the following significant technical changes with respect to the previous edition: Adapted to the basic standards IEC 60073, IEC 60417, ISO 3864-1, ISO 7000 and ISO 7010
Safety of machinery - Indication, marking and actuation - Part 2: Requirements for marking
It gives general rules on marking for identification of machinery, for safe use related to mechanical and electrical hazards, and for the avoidance of hazards arising from incorrect connections. Includes the following significant technical changes with respect to the previous edition: Annex A: additional safety signs included and updated.
Safety of machinery - Indication, marking and actuation - Part 3: Requirements for the location and operation of actuators
Specifies safety-related requirements for actuators, operated by the hand or by other parts of the human body, at the human-machine interface. It gives general requirements for the standard direction of movement for actuators; the arrangement of an actuator in relation to other actuators; the correlation between an action and its final effects. It includes the following significant technical changes with respect to the previous edition: Table 1, Table 2 and Table A.1 have been revised editorially.
IEC 61334 , known as Distribution automation using distribution line carrier systems, is a standard for low-speed reliable power line communications by electricity meters, water meters and SCADA.
IEC 61334
Distribution automation using distribution line carrier systems - Part 3-1: Mains signalling requirements - Frequency bands and output levels
Applies to electrical equipment used in distribution line carrier systems on both medium-voltage and low-voltage distribution networks. Specifies requirements such as frequency bands, output levels, spurious emissions, etc. This publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 3: Mains signalling requirements - Section 21: MV phase-to-phase isolated capacitive coupling device
Establishes definitions, requirements, methods of testing and rated values for phase-to-phase isolated capacitive coupling devices to be used in medium-voltage (MV) distribution line carrier systems. This publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 3-22: Mains signalling requirements - MV phase-to-earth and screen-to-earth intrusive coupling devices
Establishes definitions, requirements, methods of testing and rated values for phase-to-earth capacitive and screen-to-earth intrusive inductive coupling devices to be used in medium voltage DLC systems. This publication is of high relevance for Smart Grid.
Establishes definitions, requirements, methods of testing and rated values for phase-to-earth capacitive and screen-to-earth intrusive inductive coupling devices to be used in medium voltage DLC systems.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 1: Reference model of the communication system
Provides a basic description of the communication system based on a three layer model. Application examples are control and monitoring of the distribution network, order broadcast, control of user interfaces, public lighting, automatic meter reading, etc. This publication is of high relevance for Smart Grid.
Provides a basic description of the communication system based on a three layer model. Application examples are control and monitoring of the distribution network, order broadcast, control of user interfaces, public lighting, automatic meter reading, etc.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 32: Data link layer - Logical link control (LLC)
Covers the services required of, or by, the DCP Logical Link Control (LLC) sublayer entity at the logical interfaces with the application layer and the MAC sublayer. This publication is of high relevance for Smart Grid.
Covers the services required of, or by, the DCP Logical Link Control (LLC) sublayer entity at the logical interfaces with the application layer and the MAC sublayer.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4-33: Data communication protocols - Data link layer - Connection oriented protocol
Covers the services required by the data communication protocol (DCP) logical link control (LLC) sublayer entity at the logical interfaces with the LLC -user layer and the MAC sublayer, using the connection-oriented LLC procedures.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4: Data communication protocols - Section 41: Application protocol - Distribution line message specification
Defines the distribution line message specification (DLMS) within the OSI application layer. This publication is of high relevance for Smart Grid.
Defines the distribution line message specification (DLMS) within the OSI application layer.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems -Part 4: Data communication protocols - Section 42: Applicationprotocols - Application laye
Describes the rules used to design an application service element, the ISO connectionless ACSE (Application Control Service Element), and the DLMS Application Service Element. This publication is of high relevance for Smart Grid.
Describes the rules used to design an application service element, the ISO connectionless ACSE (Application Control Service Element), and the DLMS Application Service Element.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4-511: Data communication protocols - Systems management - CIASE protocol
Specifies the data communication protocol (DCP) management requirements. Describes the management services in an abstract way as well as the underlying protocol. This publication is of high relevance for Smart Grid.
Specifies the data communication protocol (DCP) management requirements. Describes the management services in an abstract way as well as the underlying protocol.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4-512: Data communication protocols - System management using profile 61334-5-1 - Management Information Base (MIB)
Specifies the Management Information Base (MIB), which is used for the management of the communication profile defined by the following standards: IEC 61334-5-1, IEC 61334-4-32, IEC 61334-4-42, and IEC 61334-4-41. This publication is of high relevance for Smart Grid.
Specifies the Management Information Base (MIB), which is used for the management of the communication profile defined by the following standards: IEC 61334-5-1, IEC 61334-4-32, IEC 61334-4-42, and IEC 61334-4-41.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 4-61: Data communication protocols - Network layer - Connectionless protocol
Covers the services required by the data communication protocol (DCP) network layer (N) sublayer entity at the logical interfaces with the N user layer and the LLC sublayer, using the connectionless N procedures. This publication is of high relevance for Smart Grid.
Covers the services required by the data communication protocol (DCP) network layer (N) sublayer entity at the logical interfaces with the N user layer and the LLC sublayer, using the connectionless N procedures.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 5-1: Lower layer profiles - The spread frequency shift keying (S-FSK) profile
Describes the requirements of S-FSK (frequency shift keying modulation) in conjunction with the services provided by the physical layer entity and the MAC sublayer. The transmission medium is assumed to be the distribution network on both MV or LV level. To be used in conjunction with IEC 61334-4-32. This publication is of high relevance for Smart Grid.
Describes the requirements of S-FSK (frequency shift keying modulation) in conjunction with the services provided by the physical layer entity and the MAC sublayer. The transmission medium is assumed to be the distribution network on both MV or LV level. To be used in conjunction with IEC 61334-4-32.nThis publication is of high relevance for Smart Grid.
Distribution automation using distribution line carrier systems - Part 6: A-XDR encoding rule
Defines a set of encoding rules that may be used to derive the specification of a transfer syntax for values of types defined in the DLMS core standard using the ASN.1 notation (see IEC 61334-4-41). This publication is of high relevance for Smart Grid.
Defines a set of encoding rules that may be used to derive the specification of a transfer syntax for values of types defined in the DLMS core standard using the ASN.1 notation (see IEC 61334-4-41).nThis publication is of high relevance for Smart Grid.
Standard data elements (properties) are used as elements in administration shell
IEC Common Data Dictionary
IEC Common Data Dictionary (IEC CDD) is a common repository of concepts for all electrotechnical domains based on the methodology and the information model of IEC 61360 series. Standard data elements types with associated classification scheme for electric items.
IEC 61360
IEC 61400
Wind energy generation systems - Part 25-1: Communications for monitoring and control of wind power plants - Overall description of principles and models
IEC 61400-25-1:2017 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document. IEC 61400-25-1:2017 gives an overall description of the principles and models used in the IEC 61400-25 series, which is designed for a communication environment supported by a client-server model. Three areas are defined, that are modelled separately to ensure the scalability of implementations: wind power plant information models, information exchange model, and mapping of these two models to a standard communication profile. This new edition includes the following significant technical changes with respect to the previous edition: general harmonization of text and overview models with the other parts of the IEC 61400-25 series, harmonization of definitions in other related standards.
IEC 61400-25-1:2017 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.nnIEC 61400-25-1:2017 gives an overall description of the principles and models used in the IEC 61400�25 series, which is designed for a communication environment supported by a client-server model. Three areas are defined, that are modelled separately to ensure the scalability of implementations: wind power plant information models, information exchange model, and mapping of these two models to a standard communication profile. This new edition includes the following significant technical changes with respect to the previous edition: general harmonization of text and overview models with the other parts of the IEC 61400�25 series, harmonization of definitions in other related standards.
Wind turbines - Part 25-2: Communications for monitoring and control of wind power plants - Information models
IEC 61400-25-2:2015 specifies the information model of devices and functions related to wind power plant applications. In particular, it specifies the compatible logical node names, and data names for communication between wind power plant components. This includes the relationship between logical devices, logical nodes and data. The names defined in the IEC 61400-25 series are used to build the hierarchical object references applied for communicating with components in wind power plants. Main changes with respect to the previous edition consist of: - harmonization with newer editions of IEC 61850 standards; - reduction of overlap between standards and simplification by increased referencing, - extension of data objects for operation of smart grids, - extended and enhanced semantics for existing data objects, etc.
IEC 61400-25-2:2015 specifies the information model of devices and functions related to wind power plant applications. In particular, it specifies the compatible logical node names, and data names for communication between wind power plant components. This includes the relationship between logical devices, logical nodes and data. The names defined in the IEC 61400-25 series are used to build the hierarchical object references applied for communicating with components in wind power plants. Main changes with respect to the previous edition consist of:- harmonization with newer editions of IEC 61850 standards;- reduction of overlap between standards and simplification by increased referencing,- extension of data objects for operation of smart grids,- extended and enhanced semantics for existing data objects, etc.
Wind turbines - Part 25-3: Communications for monitoring and control of wind power plants - Information exchange models
IEC 61400-25-3:2015 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document. IEC 61400-25-3:2015 specifies an abstract communication service interface describing the information exchange between a client and a server for: - data access and retrieval, - device control, - event reporting and logging, - self-description of devices (device data dictionary), - data typing and discovery of data types. Main changes with respect to the previous edition consist of: - harmonization with newer editions of IEC 61850 standards; - reduction of overlap between standards and simplification by increased referencing, etc.
IEC 61400-25-3:2015 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.nIEC 61400-25-3:2015 specifies an abstract communication service interface describing the information exchange between a client and a server for:n- data access and retrieval,n- device control,n- event reporting and logging,n- self-description of devices (device data dictionary),n- data typing and discovery of data types.nMain changes with respect to the previous edition consist of:n- harmonization with newer editions of IEC 61850 standards;n- reduction of overlap between standards and simplification by increased referencing, etc.
Wind energy generation systems - Part 25-4: Communications for monitoring and control of wind power plants - Mapping to communication profile
IEC 61400-25-4:2016 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document. IEC 61400-25-4:2016 specifies the specific mappings to protocol stacks encoding the messages required for the information exchange between a client and a remote server for: data access and retrieval, device control, event reporting and logging, publisher/subscriber, self-description of devices (device data dictionary), data typing and discovery of data types. The mappings specified in this part of IEC 61400-25 comprise: - a mapping to SOAP-based web services, - a mapping to OPC/XML-DA, - a mapping to IEC 61850-8-1 MMS, - a mapping to IEC 60870-5-104, - a mapping to DNP3. The main technical changes with regard to the previous edition are as follows: - general harmonization with information models in IEC 61400-25-2 and information exchange services in IEC 61400-25-3; - reduction of overlap between standards and simplification by increased referencing.
IEC 61400-25-4:2016 RLV contains the International Standard and its Redline version. The Redline version is available in English only. The Redline version provides you with a quick and easy way to compare all the changes between this standard and its previous edition. The Redline version is not an official IEC Standard, only the current version of the standard is to be considered the official document.nnIEC 61400-25-4:2016 specifies the specific mappings to protocol stacks encoding the messages required for the information exchange between a client and a remote server for: data access and retrieval, device control, event reporting and logging, publisher/subscriber, self-description of devices (device data dictionary), data typing and discovery of data types. The mappings specified in this part of IEC 61400-25 comprise:n- a mapping to SOAP-based web services,n- a mapping to OPC/XML-DA,n- a mapping to IEC 61850-8-1 MMS,n- a mapping to IEC 60870-5-104,n- a mapping to DNP3.nThe main technical changes with regard to the previous edition are as follows:n- general harmonization with information models in IEC 61400-25-2 and information exchange services in IEC 61400-25-3;n- reduction of overlap between standards and simplification by increased referencing.
Wind energy generation systems - Part 25-5: Communications for monitoring and control of wind power plants - Compliance testing
IEC 61400-25-5:2017 specifies standard techniques for testing of compliance of implementations, as well as specific measurement techniques to be applied when declaring performance parameters. The use of these techniques will enhance the ability of users to purchase systems that integrate easily, operate correctly, and support the applications as intended. This part of IEC 61400-25 defines: the methods and abstract test cases for compliance testing of server and client devices used in wind power plants; the metrics to be measured in said devices according to the communication requirements specified in IEC 61400-25 (all parts). This new edition includes the following significant technical changes with respect to the previous edition: - harmonization with structure and test cases in IEC 61850-10:2012; - reduction of overlap between standards and simplification by increased referencing to the IEC 61850 standard series.
IEC 61400-25-5:2017 specifies standard techniques for testing of compliance of implementations, as well as specific measurement techniques to be applied when declaring performance parameters. The use of these techniques will enhance the ability of users to purchase systems that integrate easily, operate correctly, and support the applications as intended. This part of IEC 61400-25 defines: the methods and abstract test cases for compliance testing of server and client devices used in wind power plants; the metrics to be measured in said devices according to the communication requirements specified in IEC 61400-25 (all parts). This new edition includes the following significant technical changes with respect to the previous edition:n- harmonization with structure and test cases in IEC 61850-10:2012;n- reduction of overlap between standards and simplification by increased referencing to the IEC 61850 standard series.
Wind energy generation systems - Part 25-6: Communications for monitoring and control of wind power plants - Logical node classes and data classes for condition monitoring
IEC 61400-25-6:2016(E) specifies the information models related to condition monitoring for wind power plants and the information exchange of data values related to these models. This standard is to be used with other standards of the IEC 61400-25 series. This new edition includes the following significant technical changes with respect to the previous edition: - major restructuring of the data model to accommodate flexibility; removal of UFF58 format; - access to data using the standard reporting and logging functions; - recommendations for creating data names to accommodate flexibility.
IEC 61400-25-6:2016(E) specifies the information models related to condition monitoring for wind power plants and the information exchange of data values related to these models. This standard is to be used with other standards of the IEC 61400-25 series. This new edition includes the following significant technical changes with respect to the previous edition:n- major restructuring of the data model to accommodate flexibility; removal of UFF58 format;n- access to data using the standard reporting and logging functions;n- recommendations for creating data names to accommodate flexibility.
Functional description, informational representation and communication mapping of application functionality. This standard describes how a distributed control application is composed of functional units (FB), which are executed in different context. It may help to describe how functions are distributed between different I40-Components and how the execution of the functions between the different I40-Components is controled.
FBs distributed systems
Function Blocks - Architecture Related Applications http://www.eclipse.org/4diac/ (sourceforge.net/projects/oooneida-fbench/) http://timeme.io/ not accepted by the Industry yet. http://www.holobloc.com/Proposed for IEC to overcome the restricctions of IEC 61131
IEC 61499
Industrial-process measurement and control - Documentation ofapplication software
Defines the requirements for the documentation of software in industrial process measurement and control systems.
Defines the functional safety requirements established by IEC 61508 in process industry sector terminology
Functional Safety of Electrical/Electronic/Programmable Electronic Safety-related Systems
Functional safety is a concept applicable across all industry sectors. It is fundamental to the enabling of complex technology used for safety-related systems. It provides the assurance that the safety-related systems will offer the necessary risk reduction required to achieve safety for the equipment. The oil and gas industry, nuclear plants and the machinery sector, to name but a few, all rely heavily on functional safety to achieve safety for the equipment giving rise to the hazards.
IEC 61508
Functional safety - Safety instrumented systems for the process industry sector
IEC 61511 is a technical standard which sets out practices in the engineering of systems that ensure the safety of an industrial process through the use of instrumentation.
The standard sought to address the following problems: lack of a universal model for batch control, difficulty in communicating user requirement, integration among batch automation suppliers, difficulty in batch control configuration.
ISA-88
Batch control - Models and terminology
IEC 61512
IEC 61508 is intended to be a basic functional safety standard applicable to all kinds of industry. It defines functional safety as: “part of the overall safety relating to the EUC (Equipment Under Control) and the EUC control system which depends on the correct functioning of the E/E/PE safety-related systems, other technology safety-related systems and external risk reduction facilities."
IEC 61513
Electronic design interchange format (EDIF)
IEC 61690 defines the syntax and semantics for EDIF
IEC 61690
Electronic design interchange format (EDIF) - Part 1: Version 3 0 0. (This publication is available in electronic HTML format only)
IEC 61690-1:2000 defines the syntax and semantics for EDIF Version 3 0 0. EDIF Version 3 0 0 addresses EDIF Level 0 and Level 1. EDIF Version 3 0 0 completely addresses the Connectivity and Schematic views, including at Level 1 the ability to represent frames. It includes capabilities formerly found in the Document and Graphics views. A series of releases is planned in the near future to address those views not completely addressed in this version.
Electronic design interchange format (EDIF) - Part 2: Version 4 0 0. (This publication is available in electronic HTML format only)
IEC 61690-2:2000 defines the syntax and semantics for EDIF Version 4 0 0. EDIF Version 4 0 0 addresses EDIF Level 0 and Level 1. EDIF Version 3 0 0 provides support for Connectivity and Schematics; EDIF Version 4 0 0 offers additional capability by providing support for the representation of Printed Circuit Boards (PCBs) and Multi-chip Modules (MCMs) including technology rules and assembly drawings.
Behavioural languages
Revises and enhances the VHDL language reference manual (LRM) by including a standard C language interface specification. The VHDL language was defined for use in the design and documentation of electronics systems.
IEC 61691
Behavioural languages - Part 6: VHDL Analog and Mixed-Signal Extensions
IEC 61691-6:2009(E) Defines IEC 61691-6/IEEE Std 1076.1 language, a hardware description language for the description and the simulation of analog, digital, and mixed-signal systems. The language, also informally known as VHDLAMS, is built on the IEC 61691-1-1/IEEE 1076 (VHDL) language and extends it to provide capabilities of writing and simulating analog and mixed-signal models.
Information description and communication mapping for fieldbus profiles
IEC Fieldbus (Profibus)
Industrial communication networks - Profiles - Ethernet-real-time-enabled
IEC 61784
EDDL
Function blocks (FB) for process control - Overview of system aspects
IEC 61804
Function Blocks (FB) for process control and Electronic Device Description Language (EDDL) - Part 3: EDDL syntax and semantics
IEC 61804-3:2015 specifies the Electronic Device Description Language (EDDL) technology, which enables the integration of real product details using the tools of the engineering life cycle. It specifies EDDL as a generic language for describing the properties of automation system components. This third edition cancels and replaces the second edition published in 2010. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: Builtins and their profiles removed and relocated into IEC 61804-5. The following extensions are integrated in the EDDL specification to meet FDI requirements: - new contructs BLOB, PLUGIN; - component construct for communication server requirements (additional attributes); - extension of the class attribute; - new attributes PRIVATE, VISIBILITY, WRITE_MODE
Function blocks (FB) for process control and electronic device description language (EDDL) - Part 4: EDD interpretation
IEC 61804-4:2015 specifies EDD interpretation for EDD applications and EDDs to support EDD interoperability. This document is intended to ensure that field device developers use the EDDL constructs consistently and that the EDD applications have the same interpretations of the EDD. It supplements the EDDL specification to promote EDDL application interoperability and improve EDD portability between EDDL applications. This first edition cancels and replaces IEC TR 61804-4 published in 2006. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: - New paragraph: EDDL data description; - EDDL METHOD programming and usage of builtins; - Edit session; - Offline and online configuration; - EDDL communication description and Enhancements in paragraph EDDL user interface descriptions.
Function blocks (FB) for process control and electronic device description language (EDDL) - Part 5: EDDL Builtin library
IEC 61804-5:2015 specifies the EDDL Builtin library and provides the profiles of the various fieldbuses.
Function blocks (FB) for process control - Electronic device description language (EDDL) - Part 6: Meeting the requirements for integrating fieldbus devices in engineering tools for field devices
IEC/TR 61804-6:2012(E) provides an evaluation and assessment of electronic device description language (EDDL) technology. It provides guidance to device and system manufacturers for how EDDL technology can help them meet user requirements. It provides guidance to system integrators, as well as instrumentation and maintenance practitioners at end-user companies, on how EDDL technology can help them integrate systems and incorporate device management in their work processes. It gives examples of requirements from the NAMUR NE 105 recommendation. It's intent is to illustrate how EDDL technology and products based on EDDL technology meet these requirements.
Electromechanical elementary relays
Electromechanical elementary relays.
IEC 61810
Electromechanical elementary relays - Part 2: Reliability
IEC 61810-2:2017 covers test conditions and provisions for the evaluation of endurance tests using appropriate statistical methods to obtain reliability characteristics for relays. This document applies to electromechanical elementary relays considered as non-repaired items (i.e. items which are not repaired after failure). This document does not cover procedures for electromechanical elementary relays where enhanced requirements for the verification of reliability apply. This edition includes the following significant technical changes with respect to the previous edition: - not only graphical but also numerical methods are added; - reduction of number of samples in specified cases; - new subclauses of confidence intervals are added; - the WeiBayes approach is added to facilitate compliance tests (routine test) with lower effort; - annexes have been restructured into an Annex A for data analysis (normative) and Annex B (informative) where various examples of the data analysis are given; - the former Annex C has been incorporated into the modified Annex B; - a new Annex C replaces the old Annex D.
IEC 61810-2:2017 covers test conditions and provisions for the evaluation of endurance tests using appropriate statistical methods to obtain reliability characteristics for relays.nThis document applies to electromechanical elementary relays considered as non-repaired items (i.e. items which are not repaired after failure).nThis document does not cover procedures for electromechanical elementary relays where enhanced requirements for the verification of reliability apply.nThis edition includes the following significant technical changes with respect to the previous edition:n- not only graphical but also numerical methods are added;n- reduction of number of samples in specified cases;n- new subclauses of confidence intervals are added;n- the WeiBayes approach is added to facilitate compliance tests (routine test) with lower effort;n- annexes have been restructured into an Annex A for data analysis (normative) and Annex B (informative) where various examples of the data analysis are given;n- the former Annex C has been incorporated into the modified Annex B;n- a new Annex C replaces the old Annex D.
Electromechanical elementary relays - Part 7: Test and measurement procedures
IEC 61810-7:2006 Lays down the test and measurement procedures for electromechanical elementary relays. Covers basic considerations which are common to all types of electromechanical elementary relays. Supplementary requirements may be necessitated by specific designs or application.
IEC 61850 is a standard for vendor-agnostic engineering of the configuration of Intelligent Electronic Devices for electrical substation automation systems to be able to communicate with each other..
IEC 61850
Communication networks and systems in substations - Part 10: Conformance testing
Specifies standard techniques for testing of conformance of implementations, as well as specific measurement techniques to be applied when declaring performance parameters. The use of these techniques will enhance the ability of the system integrator to integrate IEDs easily, operate IEDs correctly, and support the applications as intended.This publication is of core relevance for Smart Grid..
Communication networks and systems for power utility automation - Part 10: Conformance testing
IEC 61850-10:2012 specifies standard techniques for testing of conformance of client, server and sampled value devices and engineering tools, as well as specific measurement techniques to be applied when declaring performance parameters. The use of these techniques will enhance the ability of the system integrator to integrate IEDs easily, operate IEDs correctly, and support the applications as intended. The major technical changes with regard to the previous edition are as follows:- updates to server device conformance test procedures;- additions of certain test procedures (client device conformance, sampled values device conformance, (engineering) tool related conformance, GOOSE performance)..
Communication networks and systems for power utility automation - Part 4: System and project management
Describes the requirements of the system and project management process and of special supporting tools for engineering and testing.This publication is of core relevance for Smart Grid.
IEC 61850-4:2011 applies to projects associated with process near automation systems of power utilities (UAS, utility automation system), like e.g. substation automation systems (SAS). It defines the system and project management for UAS systems with communication between intelligent electronic devices (IEDs) in the substation respective plant and the related system requirements. This second edition constitutes a technical revision to align the document more closely with the other parts of the IEC 61850 series, in addition to enlarging the scope from substation automation systems to all utility automation systems.This publication is of core relevance for Smart Grid.
Communication networks and systems for power utility automation - Part 7-1: Basic communication structure - Principles and models
Provides an overview of the architecture for communication and interactions between substation devices such as protection devices, breakers, transformers, substation hosts, etc. Uses simple examples of functions to describe the concepts and methods applied in the IEC 61850 series. Also describes the relationships between other parts of the IEC 61850 series and defines how inter-operability is reached.This publication is of core relevance for Smart Grid.
IEC 61850-7-1:2011 introduces the modelling methods, communication principles, and information models that are used in the various parts of the IEC 61850-7 series. The purpose is to provide - from a conceptual point of view - assistance to understand the basic modelling concepts and description methods for:- substation-specific information models for power utility automation systems,- device functions used for power utility automation purposes, and- communication systems to provide interoperability within power utility facilities. Compared to the first edition, this second edition introduces:- the model for statistical and historical statistical data,- the concepts of proxies, gateways, LD hierarchy and LN inputs,- the model for time synchronisation,- the concepts behind different testing facilities,- the extended logging function. It also clarifies certain items.
Communication networks and systems in substations - Part 7-2: Basic communication structure for substation and feeder equipment - Abstract communication service interface (ACSI)
Applies to the ACSI communication in substations and feeder applications. The ACSI provides the abstract interface describing communications between a client and a remote server; and the abstract interface for fast and reliable system-wide event distribution between an application in one device and many remote applications in different devices and for transmission of sampled measured values.
Communication networks and systems for power utility automation - Part 7-2: Basic information and communication structure - Abstract communication service interface (ACSI)
IEC 61850-7-2:2010(E) applies to the ACSI communication for utility automation. The ACSI provides the following abstract communication service interfaces:- abstract interface describing communications between a client and a remote server;- and abstract interface for fast and reliable system-wide event distribution between an application in one device and many remote applications in different devices (publisher/sub-scriber) and for transmission of sampled measured values (publisher/subscriber).This publication is of core relevance for Smart Grid
Communication networks and systems in substations - Part 7-3: Basic communication structure for substation and feeder equipment - Common data classes
Specifies common attribute types and common data classes related to substation applications. Specifies particularly: common data classes for status information, for measured information, for controllable status information, for controllable analogue set point information, for status settings, for analogue settings and attribute types used in these common data classes. Is applicable to the description of device models and functions of substations and feeder equipment. This publication is of core relevance for Smart Grid.
Communication networks and systems for power utility automation - Part 7-3: Basic communication structure - Common data classes
IEC 61850-7-3:2010 is applicable to the description of device models and functions of substations and feeder equipment. It specifies constructed attribute classes and common data classes related to substation applications. In particular, it specifies common data classes for status information, common data classes for measured information, common data classes for control, common data classes for status settings, common data classes for analogue settings and attribute types used in these common data classes. This second edition defines new common data classes used for new standards defining object models for other domains based on IEC 61850 and for the representation of statistical and historical data. This publication is of core relevance for Smart Grid.
Communication networks and systems for power utility automation - Part 7-420: Basic communication structure - Distributed energy resources logical nodes
IEC 61850-7-420:2009(E) defines IEC 61850 information models to be used in the exchange of information with distributed energy resources (DER), which comprise dispersed generation devices and dispersed storage devices, including reciprocating engines, fuel cells, microturbines, photovoltaics, combined heat and power, and energy storage. Utilizes existing IEC 61850-7-4 logical nodes where possible, but also defines DER-specific logical nodes where needed.
Communication networks and systems in substations - Part 7-4: Basic communication structure for substation and feeder equipment - Compatible logical node classes and data classes
Specifies the information model of devices and functions related to substation applications. Specifies in particular the compatible logical node names and data names for communication between Intelligent Electronic Devices, which includes the relationship between Logical Nodes and Data..
Communication networks and systems for power utility automation - Part 7-4: Basic communication structure - Compatible logical node classes and data object classes
IEC 61850-7-4:2010 specifies the information model of devices and functions generally related to common use regarding applications in systems for power utility automation. It also contains the information model of devices and function-related applications in substations. In particular, it specifies the compatible logical node names and data object names for communication between intelligent electronic devices (IED). This includes the relationship between logical nodes and data objects. Major technical changes with regard to the previous edition are as follows:- corrections and clarifications according to technical issues raised by the users' community; extensions for new logical nodes for the power quality domain;- extensions for the model for statistical and historical statistical data;- extensions regarding IEC 61850-90-1;- extensions for new logical nodes for monitoring functions according to IEC 62271;- new logical nodes from IEC 61850-7-410 and IEC 61850-7-420 of general interest.This publication is of core relevance for Smart Grid.
IEC 61850-8-1:2011 specifies a method of exchanging time-critical and non-time-critical data through local-area networks by mapping ACSI to MMS and ISO/IEC 8802-3 frames. Defines a standardized method of using the ISO 9506 services to implement the exchange of data. For those ACSI services defined in IEC 61850-7-2 that are not mapped to MMS, this part defines additional protocols. It describes real utility devices with respect to their external visible data and behaviour using an object oriented approach. The objects are abstract in nature and may be used to a wide variety of applications. The use of this mapping goes far beyond the application in the utility communications. The main changes with respect to the previous edition are listed below: - the support of gigabit Ethernet, - the link layer redundancy, - the extension of the length of the object reference, - the extension of the reason for inclusion type for comprehensive logging, - the mapping of the tracking services, - a second mapping of the objectReference when used in the tracking services, or as linking, - the extension of the AdditionalCause enumeration, - the simulation of GOOSE telegram, - the so-called fixed-length encoded GOOSE, - the removal of the SCL Control Block.
Application integration at electric utilities - System interfaces for distribution management
IEC 61968 is a series of standards under development that will define standards for information exchanges between electrical distribution systems.
IEC 61968
Application integration at electric utilities - System interfaces for distribution management - Part 3: Interface for network operations
Specifies the information content of a set of message types that can be used to support many of the business functions related to network operations. Typical uses of the message types defined in this part include data acquisition by external systems, fault isolation, fault restoration, trouble management, maintenance of the plant, and the commissioning of the plant. This publication is of core relevance for Smart Grid.
IEC 61968-3:2017 defines a Network Operations function which provides utilities the means to supervise main substation topology (breaker and switch state) and control equipment status. It also provides the means for handling network connectivity and loading conditions. Finally, it makes it possible for utilities to locate customer telephone complaints and supervise the location of field crews. IEC 61968-3 specifies the information content of a set of message payloads that can be used to support many of the business functions related to network operations. Typical uses of the message payloads defined in IEC 61968-3 include data acquisition by external systems, fault isolation, fault restoration, trouble management, maintenance of plant, and the commissioning of plant. This edition includes the following significant technical changes with respect to the previous edition: replacement of certain function names, addition of other function names.
Application integration at electric utilities - System interfaces for distribution management - Part 4: Interfaces for records and asset management
IEC 61968-4:2007 Specifies the information content of a set of message types that can be used to support many of the business functions related to records and asset management. Typical uses of the message types include network extension planning, copying feeder or other network data between systems, network or diagram edits and asset inspection.This publication is of core relevance for Smart Grid.
Pre release version (PRV)
IEC 61968-4:2018 PRV
This Final Draft International Standard is an up to 6 weeks' pre-release of the official publication. It is available for sale during its voting period: 2018-12-14 to 2019-01-25. By purchasing this FDIS now, you will automatically receive, in addition, the final publication.IEC 61968:2019 specifies the information content of a set of message types that can be used to support many of the business functions related to records and asset management. Typical uses of the message types defined in this document include network extension planning, copying feeder or other network data between systems, network or diagram edits and asset inspection. Message types defined in other parts of IEC 61968 may also be relevant to these use cases.This second edition cancels and replaces the first edition published in 2007. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:a) removal of edition 1 profiles whose functionality has been superseded by other parts of IEC 61970 and IEC 61968 standards. In particular, NetworkDataSet and ChangeSet have been superseded by standards such as CDPSM (IEC 61968-13) and other ongoing efforts such as change modelling; and Presentation has been superseded by Diagram Layout Profile (IEC 61970-453);b) revision of the edition 1 profiles AssetList, AssetCatalogue and TypeAssetCatalogue to realign with current use cases and the latest CIM UML release. These profiles are based on an old version of CIM UML and many of the classes in these profiles are no longer in the recent CIM UMLs;c) addition of several new profiles to enable the exchange of asset condition data, analytics results and alerts, assets' physical, functional and lifecycle details, and assets' work;d) informative annexes on how this document can be used to enable strategic asset management;e) informative annexes with illustrative examples for the application of this document;f) scope coordinated with IEC 61968-13 where applicable;g) use cases in IEC 62559-2 use case template;h) traceability of use cases to IEC 62913-2-1 use cases.
Application integration at electric utilities - System interfaces for distribution management - Part 6: Interfaces for maintenance and construction
IEC 61968-6:2015 specifies the information content of a set of message types that can be used to support business functions related to maintenance and construction. Typical uses of the message types defined in this part of IEC 61968 include planned maintenance, unplanned maintenance, conditional maintenance, work management, new service requests, etc. Message types defined in other parts of IEC 61968 may also be relevant to these use cases.
Application integration at electric utilities - System interfaces for distribution management - Part 8: Interfaces for customer operations
IEC 61968-8:2015 specifies the information content of a set of message types that can be used to support many of the business functions related to customer support. Typical uses of the message types include service request, customer agreement, and trouble management. The purpose is to define a standard for the integration of customer support (CS), which would include customer service, trouble management and point of sale related components integrated with other systems and business functions within the scope of IEC 61968. The scope of this standard is the exchange of information between a customer support system and other systems within the utility enterprise.
Application integration at electric utilities - System interfaces for distribution management - Part 9: Interfaces for meter reading and control
IEC 61968-9:2009(E) specifies the information content of a set of message types that can be used to support many of the business functions related to meter reading and control. Typical uses of the message types include meter reading, meter control, meter events, customer data synchronization and customer switching. Although intended primarily for electrical distribution networks, IEC 61968-9 can be used for other metering applications, including non-electrical metered quantities necessary to support gas and water networks. This publication is of core relevance for Smart Grid..
IEC 61968-9:2013 specifies the information content of a set of message types that can be used to support many of the business functions related to meter reading and control. Typical uses of the message types include meter reading, controls, events, customer data synchronization and customer switching. The purpose of IEC 61968-9 is to define a standard for the integration of metering systems (MS), which includes traditional manual systems, and (one or two-way) automated meter reading (AMR) systems, and meter data management (MDM) systems with other enterprise systems and business functions within the scope of IEC 61968. The scope of IEC 61968-9 is the exchange of information between metering systems, MDM systems and other systems within the utility enterprise. This new edition includes the following significant technical changes with respect to the previous edition:- changes to and addition of new profiles to support PAN and UsagePoints;- extensions to support PAN devices generically as EndDevices;- extensions to the MeterReading model and profiles to support richer descriptions of metered quantities and to accommodate coincident readings..
Energy management system application program interface (EMS-API)
Provides a set of guidelines and general infrastructure capabilities required for the application of the EMS-API interface standards.
IEC 61970
Energy management system application program interface (EMS-API) - Part 1: Guidelines and general requirements
Provides a set of guidelines and general infrastructure capabilities required for the application of the EMS-API interface standards. Describes typical integration scenarios where these standards are to be applied and the types of applications to be integrated. Defines a reference model and provides a framework for the application of the other parts of these EMS-API standards.This publication is of core relevance for Smart Grid.
Energy management system application program interface (EMS-API) - Part 301: Common information model (CIM) base
Defines the Common Information Model Base set of packages which provide a logical view of the physical aspects of Energy Management System information. Is part of the IEC 61970 series, which defines an Application Program Interface (API) for an Energy Management System (EMS).
IEC 61970-301:2009(E) defines the Common Information Model (CIM) base set of packages which provide a logical view of the physical aspects of an energy management system including SCADA (Supervisory Control and Data Acquisition). Whilst there are multiple IEC standards dealing with different parts of the CIM, there is a single, unified normalized information model comprising the CIM behind all these individual standards documents. This second edition contains the following main changes with respect to the previous edition:- change of the naming hierarchy,- replacement of several classes,- addition of several new classes,- many editorial corrections to resolve issues included in the first edition. This publication is of core relevance for Smart Grid.
IEC 61970-301:2011 deals with the common information model (CIM), an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. The object classes represented in the CIM are abstract in nature and may be used in a wide variety of applications. The use of the CIM goes far beyond its application in an EMS. This standard should be understood as a tool to enable integration in any domain where a common power system model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation. Major changes from the second edition include the following:- Addition of regulation control models;- new (OperationalLimits) package for equipment ratings;- addition of partial ownership specification;- enhancement of LoadResponseCharacteristic;- change from non-SI units to SI units.
IEC 61970-301:2013 deals with the common information model (CIM), an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. The object classes represented in the CIM are abstract in nature and may be used in a wide variety of applications. The use of the CIM goes far beyond its application in an EMS. This standard is to be understood as a tool to enable integration in any domain where a common power system model is needed to facilitate interoperability and plug compatibility between applications and systems independent of any particular implementation. Major changes from the third edition include the following:- extensions have been added to support UCTE exchange;- the transformer regulation model has been expanded to support phase shifting transformer models needed by ENTSO-E;- zero and negative sequence impedance terms have been added;- new StateVariables package has been added;- additional classes have been added.
IEC 61970-301:2013 defines the Common Information Model (CIM), that is an abstract model representing all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of Energy Management System (EMS) applications developed independently by different vendors, between entire EMS systems developed independently, or between an EMS system and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modeled to the extent necessary to support power system simulation and inter-control center communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. Major changes from the fourth edition include the following:- transformer models have been modified to be consistent for use by distribution and transmission purposes;- a more general and clear naming approach was added and several ambiguous attributes related to naming were dropped;- phase component wires models have been enhanced to describe internal phase specific attributes and connections;- addition of diagram layout models to facilitate the exchange of diagram layout information.
IEC 61970-301:2016 is available as IEC 61970-301:2016 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 61970-301:2016 lays down the common information model (CIM), which is an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of network applications developed independently by different vendors, between entire systems running network applications developed independently, or between a system running network applications and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modeled to the extent necessary to support power system simulation and inter-control centre communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. This new edition includes the following significant technical changes with respect to the previous edition:- new model for grounding including Petersen coils;- models for HVDC; addition of Static Var Compensation models;- phase shift transformer updates;- short circuit calculations based on IEC 60909;- addition of non-linear shunt compensator;- addition of model for steady state calculation inputs, Steady State Hypothesis;- addition of base frequency model;- Annex A with custom extensions added.
IEC 61970-301:2016 RLV Redline version
IEC 61970-301:2016 RLV contains both the official IEC International Standard and its Redline version. The Redline version is not an official document, it is available in English only and provides you with a quick and easy way to compare all the changes between the official IEC Standard and its previous edition.IEC 61970-301:2016 lays down the common information model (CIM), which is an abstract model that represents all the major objects in an electric utility enterprise typically involved in utility operations. By providing a standard way of representing power system resources as object classes and attributes, along with their relationships, the CIM facilitates the integration of network applications developed independently by different vendors, between entire systems running network applications developed independently, or between a system running network applications and other systems concerned with different aspects of power system operations, such as generation or distribution management. SCADA is modeled to the extent necessary to support power system simulation and inter-control centre communication. The CIM facilitates integration by defining a common language (i.e. semantics) based on the CIM to enable these applications or systems to access public data and exchange information independent of how such information is represented internally. This new edition includes the following significant technical changes with respect to the previous edition:- new model for grounding including Petersen coils;- models for HVDC; addition of Static Var Compensation models;- phase shift transformer updates;- short circuit calculations based on IEC 60909;- addition of non-linear shunt compensator;- addition of model for steady state calculation inputs, Steady State Hypothesis;- addition of base frequency model;- Annex A with custom extensions added.
Energy management system application program interface (EMS-API) - Part 452: CIM Static transmission network model profiles
IEC 61970-452:2013 rigorously defines the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. This international standard is intended for two distinct audiences, data producers and data recipients, and may be read from two perspectives.
Energy management system application program interface (EMS-API) - Part 452: CIM model exchange specification
IEC 61970-452:2015 rigorously defines the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. These requirements are based on prior industry practices for exchanging power system model data for use primarily in planning studies. This standard is intended for two distinct audiences, data producers and data recipients, and may be used from these two perspectives..
IEC 61970-452:2017 defines the subset of classes, class attributes, and roles from the CIM necessary to execute state estimation and power flow applications. This standard is intended for two distinct audiences, data producers and data recipients, and may be read from two perspectives. From the standpoint of model export software used by a data producer, the document describes a minimum subset of CIM classes, attributes, and associations which must be present in an XML formatted data file for model exchange. This new edition includes the following significant technical changes with respect to the previous edition: the Equipment profile has been split into three separate profiles, CoreEquipment, Operation and ShortCircuit; the HVDC model has been replaced with the new model defined in Edition 6 of 61970‑301.
Properties and LOPs as an informational representation of the features of measuring equipment. The referenced standards define general principles (e.g. part 11) as well as specific LOPs for specific device types. These international standards also may serve as examples for description of products.
LOPs in PA
Industrial-process measurement and control - Data structures and elements in process equipment catalogs - Measuring equipment with analogue and digital output
IEC 61987_X
provides requirements that are applicable to the system level design of all types of machinery safety-related electrical control systems and also for the design of non-complex subsystems or devices.
IEC 60061
Live working - Insulating hoses with fittings for use with hydraulic tools and equipment.
IEC 62237
Informational representation of MES and ERP models.
Enterprise control systems
Enterprise-control system integration
Enterprise-control system integration - Models and terminology
IEC 62264 is an international standard for enterprise-control system integration. This standard is based upon ANSI/ISA-95.
IEC PAS 62264-6:2016
Enterprise-control system integration - Part 6: Messaging Service Model
IEC PAS 62264-6:2016(E) defines a model of a set of messaging services for information exchanges across Levels 3 and 4, and within Level 3, between applications performing business and manufacturing activities. It defines a standard interface for information exchange between systems.
IEC 62279:2015 specifies the process and technical requirements for the development of software for programmable electronic systems for use in railway control and protection applications. It is aimed at use in any area where there are safety implications. These systems can be implemented using dedicated microprocessors, programmable logic controllers, multiprocessor distributed systems, larger scale central processor systems or other architectures.
IEC 62279
Commissioning of electrical, instrumentation and control systems in the process industry - Specific phases and milestones.
IEC 62337
CAEX
CAEX (Computer Aided Engineering Exchange) is a neutral data format that allows storage of hierarchical object information, e.g. the hierarchical architecture of a plant. On a certain abstraction level, a plant consists in modules or components that are interconnected. CAEX allows storage of those modules or components by means of objects. Object oriented concepts as encapsulation, classes, class libraries, instances, instance hierarchies, inheritance, relations, attributes and interfaces are explicitly supported. CAEX bases on XML and is defined as XML schema (xsd file). The original intention of developing CAEX was the industrial lack of a common and established data exchange between process engineering tools and process control engineering tools. However, CAEX can be applied to all types of static object information, e.g. plant topologies, document topologies, product topologies, petri nets, but also for non-technical applications like phylogenetic trees.
IEC 62424
Cyber attacks threat the industry and can cause damage to property and personal injury and affect the image of companies. The Standard allows to define procedures for implementing electronically secure Industrial Automation and Control Systems (IACS). This guidance applies to end-users, system integrators, security practitioners, and control systems manufacturers responsible for manufacturing, designing, implementing, or managing industrial automation and control systems
Electronically secure Industrial Automation and Control Systems. Defines procedures for implementing electronically secure Industrial Automation and Control Systems.
ISA/IEC-62443 is a series of standards, technical reports, and related information that define procedures for implementing electronically secure Industrial Automation and Control Systems (IACS). This guidance applies to end-users (i.e. asset owner), system integrators, security practitioners, and control systems manufacturers responsible for manufacturing, designing, implementing, or managing industrial automation and control systems.
IEC 62443
ISA 99
FDT is an interface for integration of devices into a system (e.g. control system or engineering system). The standard supports factory automation as well as process automation with a wide range of fieldbus protocols. The interface defines fieldbus-independent mechanisms for accessing data and functions of the devices.
FDT
Field device tool (FDT) interface specification - Overview and guidance
IEC 62453
OPC UA
OPC Unified Architecture (OPC UA) is an industrial M2M communication protocol for interoperability developed by the OPC Foundation. It is the successor to Open Platform Communications (OPC). Although developed by the same organization, OPC UA differs significantly from its predecessor. The Foundation's goal for this project was to provide a path forward from the original OPC communications model (namely the Microsoft Windows only process exchange COM/DCOM) to a cross-platform service-oriented architecture (SOA) for process control, while enhancing security and providing an information model.
IEC 62541
Industrial networks - Wireless communication network and communication profiles.
IEC 62591
Specifies the logical structure for a set of spreadsheets, used as data parcels, to define, transfer and register product ontologies
IEC 62656
AML
AutomationML
Engineering data exchange format for use in industrial automation systems engineering - Automation markup language - Architecture and general requirements
IEC 62714
Field device integration (FDI)
IEC 62769 describes the concepts of the Field Device Integration (FDI) specifications.
IEC 62769
Field device integration (FDI) - Part 1: Overview
IEC 62769-1:2015 describes the concepts and overview of the Field Device Integration (FDI) specifications. The detailed motivation for the creation of this technology is also described. It helps to understand the other parts of this multi-part standard.
The standards for Digital Factory define methods and information models, which are required for self description of I40-components.
DF/TR
Industrial-process measurement, control and automation - Reference model for representation of production facilities (digital factory)
IEC TR 62794
Industrial-process measurement, control and automation - Digital factory framework - Part 1: General principles
Provides to the technical committees a framework for the development and adaptation of documents in order to improve energy efficiency in manufacturing, process control and industrial facility management.
IEC 62837
Stations need to describe their operational state and performance parameters towards superior I4.0-Components
IEC 62890
Defines standards for lifecycle management for systems and products used in industrial process measurement, control and automation
MES KPIs
ISO/IEC 81714 Design of graphical symbols for use in the technical documentation of products -- Part 3: Classification of connect nodes, networks and their encoding-- specifies requirements concerning the classification of connect nodes assigned to graphical symbols, being a representation of functional and product concepts.
IEC 81714
IEC PAS 63088:2017(E) describes a reference architecture model in the form of a cubic layer model, RAMI model
IEC PAS 63088
The standards for Digital Factory define methods and information models, which are required for self description of I40-components. IEC TS 62832 defines methods, which allow to validate or plan connections between assets.
DF/TS
Digital Factory Reference model TS
IEC TS 62832
IEEE
Institute of Electrical and Electronics Engineers
IEEE and its members inspire a global community to innovate for a better tomorrow through highly cited publications, conferences, technology standards, and professional and educational activities. IEEE is the trusted “voice” for engineering, computing, and technology information around the globe.
IEEE Standard for Utility Industry Metering Communication Protocol Application Layer (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 1377-2012
The IEEE 1451, a family of Smart Transducer Interface Standards, describes a set of open, common, network-independent communication interfaces for connecting transducers (sensors or actuators) to microprocessors, instrumentation systems, and control/field networks. (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 1451
Standard for Intelligent Electronic Devices Cyber Security Capabilities
The functions and features to be provided in intelligent electronic devices (IEDs) to accommodate critical infrastructure protection programs are defined in this standard. Security regarding the access, operation, configuration, firmware revision and data retrieval from an IED are addressed. Communications for the purpose of power system protection (teleprotection) are not addressed in this standard.
IEEE 1686
DNP3
IEEE Standard for Electric Power Systems Communications-Distributed Network Protocol (DNP3)
Standard Framework for Prognostics and Health Management of Electronic Systems (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 1856
- IEEE Standard for Ubiquitous Green Community Control Network: Security (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE Standard for a Convergent Digital Home Network for Heterogeneous Technologies (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE P2413 - Standard for an Architectural Framework for the Internet of Things (IoT) (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 2413
IEEE 802.15.4 is a standard which specifies the physical layer and media access control for low-rate wireless personal area networks (LR-WPANs). It is maintained by the IEEE 802.15 working group. It is the basis for the ZigBee,ISA100.11a, WirelessHART, and MiWi specifications, each of which further extends the standard by developing the upper layers which are not defined in IEEE 802.15.4. Alternatively, it can be used with 6LoWPAN and standard Internet protocols to build a wireless embedded Internet. (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 802.15.4
IEEE Standard for Air Interface for Broadband Wireless Access Systems (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE 802.16p-2012
Standard for Systems With Virtual Components (source: https://www.postscapes.com/internet-of-things-protocols/)
IEEE P1828
IETF
Internet Engineering Task Force
TODO: complete annotations etc.
Founded in 2014 to further development, adoption and wide-spread use of interconnected machines, intelligent analytics and people at work. (source: https://www.postscapes.com/internet-of-things-protocols/)
IIC
Industrial Internet Consortium
Industrial Internet Connectivity Framework
IICF
IICF Framework Layer
IICF Framework Layer an instance of the IICF Connectivity Layer
IICF Link Layer
IICF Network Layer
IICF Transport Layer
IIC Vocabulary
The Industrial Internet of Things Volume G1: Reference Architecture IIC:PUB:G1:V1.80:20170131
The IIRA addresses the need for a common architecture framework to develop interoperable IIoT systems for diverse applications across a broad spectrum of industrial verticals in the public and private sectors to achieve the true promise of IIoT.
Industrial Internet Reference Architecture
Publications referred: 1. The Industrial Internet of Things Volume G1: Reference Architecture (IIC:PUB:G1:V1.80:20170131)
IIRA Application Domain
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.4 THE APPLICATION DOMAIN' 'Page 34'
IIRA Business Domain
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.5 THE BUSINESS DOMAIN' 'Page 34'
The business viewpoint frames economic aspects and business relations regarded by the IIC Reference Architecture.
IIRA Business Viewpoint
Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.1 BUSINESS VIEWPOINT' 'Page 15'
IIRA Connectivity
IIRA Control Domain
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.1 THE CONTROL DOMAIN' 'Page 27'
IIRA Distributed Data Management
The IIRA Functional Viewpoint contains the IIRA Domains in order to describe technical relations and communications between the several dimensions of IoT devices.
IIRA Functional Viewpoint
Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.3 FUNCTIONAL VIEWPOINT' 'Page 16'
IIRA Implementation Viewpoint
Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.4 IMPLEMENTATION VIEWPOINT' 'Page 16'
IIRA Information Domain
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.3 THE INFORMATION DOMAIN' 'Page 32'
There is a renewed movement to distribute computational capability toward the network peripheries, away from concentrated computation centers, to benefit from a reduction in movement of data and communication latency, and enhancement in local intelligent control and, more importantly, resilience. source: Industrial Internet Reference Archietcture
IIRA Intelligent and Resilient Control
IIRA Operation Domain
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.2 THE OPERATIONS DOMAIN' 'Page 30'
Computational capabilities ranging from very limited (e.g. in a smart sensor) to reasonably rich (e.g. a cluster of servers) are placed in, attached to or collocated with physical systems (e.g. in smart sensors, devices or machines). These capabilities are connected through a variety of connectivity technologies including wireless.
IIRA Physical Systems
IIRA Privacy
IIRA Reliability
Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>' '3.4 RELIABILITY' 'Page 18'
IIRA Resilience
IIRA Safety
IIRA Scalability
IIRA Security
IIC Security Framework
Publications referred: '<https://www.iiconsortium.org/pdf/IIC_PUB_G4_V1.00_PB-3.pdf IIC:PUB:G4:V1.0:PB:20160926>'
IIRA Usage Viewpoint
Publications referred: '(IIC:PUB:G1:V1.80:20170131' '3.5.2 USAGE VIEWPOINT' 'Page 16'
The Alliance is a global non-profit organization serving the various communities seeking to establish the Internet Protocol as the network for the connection of Smart Objects by providing coordinated marketing efforts available to the general public. (source: https://www.postscapes.com/internet-of-things-protocols/)
IPSO
Communication with non-IPv6 networks must be possible (IPv4, others).
IPv4 Support
System Architect
IPv6, is an Internet Layer protocol for packet-switched internetworking and provides end-to-end datagram transmission across multiple IP networks. (source: https://www.postscapes.com/internet-of-things-protocols/)
IPv6
A system built using the ARM shall use/support common-addressing-schemes such as IPv6.
IPv6 Support
International Society of Automation
The International Society of Automation (www.isa.org) is a nonprofit professional association that sets the standard for those who apply engineering and technology to improve the management, safety, and cybersecurity of modern automation and control systems used across industry and critical infrastructure. Founded in 1945, ISA develops widely used global standards; certifies industry professionals; provides education and training; publishes books and technical articles; hosts conferences and exhibits; and provides networking and career development programs for its 40,000 members and 400,000 customers around the world.
ANSI/ISA-95, or ISA-95 as it is more commonly referred, is an international standard from the International Society of Automation for developing an automated interface between enterprise and control systems. This standard has been developed for global manufacturers. It was developed to be applied in all industries, and in all sorts of processes, like batch processes, continuous and repetitive processes.There are 5 parts of the ISA-95 standard.ISA-95 Models
ISA 95
ISA100.11a is a wireless networking technology standard developed by the International Society of Automation (ISA). The official description is Wireless Systems for Industrial Automation: Process Control and Related Application. (source: https://www.postscapes.com/internet-of-things-protocols/)
Describes the ISA95 as a Standarization Initiative that classifies Standards
Describes the cross-level according to the ISA95 level classification. It means standards that are used at more than one level, e.g., manufacturing system security, etc
Cross Level
Describes the device level according to the ISA95 level classification.
Device Level
Describes the Enterprise level according to the ISA95 level classification.
Enterprise Level
Describes the MOM level according to the ISA95 level classification.
MOM Level
Manufacturing Operation Management Level according to ISA 95
Security for industrial automation and control systems
International Organization for Standardization
Internationale Organisation für Normung
Organisation internationale de normalisation
The International Organization for Standardization
Международная организация по стандартизации
Is an independent, non-governmental organization, the members of which are the standards organizations of the 162 member countries. It is the world's largest developer of voluntary international standards and facilitates world trade by providing common standards between nations. Nearly twenty thousand standards have been set covering everything from manufactured products and technology to food safety, agriculture and healthcare.
The International Organization for Standardization (ISO) is an international standard-setting body composed of representatives from various national standards organizations.
Standard for the Exchange of Product model data. ISO 10303 can represent 3D objects in Computer-aided design (CAD) and related information.
ISO 10303
TODO - Split properly and classify it - check the NIST paper
Geometrical product specifications (GPS) -- Geometrical tolerancing -- Tolerances of form, orientation, location and run-out
ISO 1101
ISOBUS
ISO 11783, known as Tractors and machinery for agriculture and forestry—Serial control and communications data network is a communication protocol for the agriculture industry based on the SAE J1939 protocol (which includes CANbus).
ISO 11783
CAN Bus
Used mainly for Road vehicles Controller area network (CAN) Data link layer and physical signalling.
ISO 11898-1
Geometrical product specifications Standards
ISO 1302
Condition monitoring and diagnostics of machines -- Data processing, communication and presentation
ISO 13374
Medical devices -- Quality management systems -- Requirements for regulatory purposes.
ISO 13485
Industrial automation systems and integration
ISO 13584 is a series of International Standards for the computer-sensible representation and exchange of parts library data. The objective is to provide a mechanism capable of transferring parts library data, independent from any particular system. The nature of this description makes it suitable not only for the exchange of files containing parts libraries, but also as a basis for implementing and sharing databases of parts library data, and archiving
ISO 13584
Provides safety requirements and guidance on the principles for the design and integration of safety-related parts of control systems (SRP/CS), including the design of software.
ISO 13849
It provides the description of the structure and content for a binary file having the extension of .jt. A binary file with the .jt extension is generally referred to as a JT file. The JT format described in ISO 14306:2012 is used primarily in industrial use cases as the means for capturing and repurposing lightweight 3D product definition data
ISO 14306
ISO 14443 Identification cards -- Contactless integrated circuit cards -- Proximity cards is an international standard that defines proximity cards used for identification, and the transmission protocols for communicating with it
ISO 14443
Document management -- 3D use of Product Representation Compact (PRC) format-ISO 14739-1:2014 describes PRC 10001 of a product representation compact (PRC) file format for three dimensional (3D) content data. This format is designed to be included in PDF (ISO 32000) and other similar document formats for the purpose of 3D visualization and exchange.
ISO 14739-1
STEP
Common Criteria for Information Technology Security Evaluation
The Common Criteria for Information Technology Security Evaluation (abbreviated as Common Criteria or CC) is an international standard (ISO/IEC 15408) for computer security certification
ISO/IEC 15408
MANDATE
This Standard models manufacturing management data such as, Resources management data (Resource model); Time related features (Time model); Flow management data in manufacturing (Flow management model).
ISO 15531
Production data for external exchanges. refering to the representation of product information to be exchanged with the external environment (customers and suppliers), with the aim to model the main production information exchanged between industrial companies, in order to improve exchanges and integration through the use of EDI protocols.
ISO 15531 2x series
Manufacturing resource usage management data sto: refering to the way of managing the use of resources, such as resource configuration and capabilities, operation management of manufacturing devices, installations and facilities.
ISO 15531 3x series
Manufacturing flow management data sto: refering to the material flow control and aiming at the representation of data and elements supporting the control and monitoring of the flow of materials in manufacturing processes.
ISO 15531 4x series
Identifies requirements for enterprise-reference architectures and methodologies
ISO 15704
Automation systems and integration -- Integration of advanced process control and optimization capabilities for manufacturing systems.
ISO 15746
Industrial automation systems and integration -- Integration of life-cycle data for process plants including oil and gas production facilities.
ISO 15926
Industry Foundation Classes (IFC) for data sharing in the construction and facility management industries.
ISO 16739
ISO 16792 Technical product documentation -- Digital product definition data practices-It supports two methods of application: model-only and model and drawing in digital format.
ISO 16792
PSL
ISO 18629-1:2004 provides a general overview of the different series of parts of ISO 18629, which defines a process specification language aimed at identifying, formally defining and structuring the semantic concepts intrinsic to the capture and exchange of process information related to discrete manufacturing.
ISO 19629
Industrial automation systems and integration -- Standardized procedures for production systems engineering.
ISO 18828-2
Provides a unified conceptual basis for model-based enterprise engineering that enables consistency, convergence and interoperability of the various modelling methodologies and supporting tools.
ISO 19439
Enterprise integration -- Constructs for enterprise modelling-specifies the characteristics of the core constructs necessary for computer-supported modelling of enterprises conforming to ISO 19439..
ISO 19440
Information technology — Software asset management
International standards in the ISO/IEC 19770 family of standards for IT asset management (ITAM) address both the processes and technology for managing software assets and related IT assets. Broadly speaking, the standard family belongs to the set of Software Asset Management (or SAM) standards and is integrated with other Management System Standards.
ISO/IEC 19770
Cloud Computing - Interoperability and Portability
Description of the ecosystem of devices and cloud services and the related flows of data between cloud services, cloud service customers, cloud service users and their devices. These are necessary to provide guidance about how data is used on the devices in the context of the cloud computing ecosystem and the associated location and identity issues that emerge from such use.
ISO/IEC 19941:2017
Energy Efficiency
Automation systems and integration -- Evaluating energy efficiency and other factors of manufacturing systems that influence the environment
ISO 20140-5
Automation systems and integration -- Evaluating energy efficiency and other factors of manufacturing systems that influence the environment -- Part 1: Overview and general principles
Evaluating the energy efficiency of a manufacturing system and other factors, e.g. energy consumption, waste and release, etc., that influence the environment. The evaluation method provides guidelines to analyse the usage of energy by the manufacturing system and the effects of the manufacturing system on the environment. ISO 20140 systematically evaluates the environmental influence through analysing the manufacturing activities and the manufacturing system. (source: iso.org)
Big data -- Overview and vocabulary
TODO: check with other reference architecture standards
ISO/IEC 20546
Big data reference architecture -- Part 3: Reference architecture
TODO: how is this standard related to other reference architecture description formats?
under development (as from 2018-07-23)
ISO/IEC DIS 20547-3
Big data reference architecture -- Part 4: Security and privacy
TODO: check with other reference architecture description frameworks
ISO/IEC AWI 20547-4
MQTT
Message Queue Telemetry Transport
ISO/IEC 20922:2016 is a Client Server publish/subscribe messaging transport protocol. It is light weight, open, simple, and designed so as to be easy to implement. These characteristics make it ideal for use in many situations, including constrained environments such as for communication in Machine to Machine (M2M) and Internet of Things (IoT) contexts where a small code footprint is required and/or network bandwidth is at a premium.
ISO 20922
Automation systems and integration -- Key performance indicators (KPIs) for manufacturing operations management.
ISO 22400
ISO 22745-11:2010 provides guidelines that are recommended for the development of terminology for concepts in an open technical dictionary (OTD).Compliance with these guidelines is not required in order for a term or definition to be included in an OTD. These guidelines are provided as a framework for developers of industrial terminology to ensure that definitions are consistent and understandable. Terminology that complies with these guidelines will be marked as such in the OTD. This will allow a user to perform a search that filters terminology based on compliance with ISO 22745-11:2010.
ISO/IEC 24760-1:2011 defines terms for identity management, and specifies core concepts of identity and identity management and their relationships. It is applicable to any information system that processes identity information. A bibliography of documents describing various aspects of identity information management is provided.
ISO 24760
Road vehicles – Functional safety
ISO 26262, titled "Road vehicles – Functional safety", is an international standard for functional safety of electrical and/or electronic systems in production automobiles defined by the International Organization for Standardization (ISO) in 2011.
ISO 26262
Provides best practices for information security management. A critical issue for Industry 4.0
Information Security Management Systems
The ISO/IEC 27000 family of standards helps organizations keep information assets secure. Using this family of standards will help your organization manage the security of assets such as financial information, intellectual property, employee details or information entrusted to you by third parties.
IEC 27000
ISO/IEC 27000
ISO/IEC 27001 is an information security standard, part of the ISO/IEC 27000 family of standards.
ISO 27001
ISO/IEC 27001
Code of practice for information security controls based on ISO/IEC 27002 for cloud services
The ISO/IEC 270172 standard provides guidance on the information security elements of cloud computing. It assists with the implementation of cloud-specific information security controls, supplementing the guidance in ISO 27000 series standards.
ISO/IEC 27017
Information technology -- Security techniques -- Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors
IEC 27018
Guidance for information security management of power supply control systems based on ISO/IEC 27002
The specification serves as a guidance for introducing ISO/IEC 27002 into the energy domain.
ISO 27019
Guidelines for information and communication technology readiness for business continuity
ISO 27031
Information security for supplier relationships
ISO 29002 is an interoperability standard, which provides a repository to be used in various ISO XML formats. It is used in ontoML.
ISO 29002
Privacy framework
Privacy architecture framework
Privacy impact assessment–Guidelines
Code of practice for protection of personally identifiable information (PII) in public clouds acting as PII processors
ISO/IEC 29101
ISO/IEC 29115
‘Privacy impact assessment–Guidelines’ proposes a methodology to conduct assessments on the impact of privacy.
ISO/IEC 29134
ISO/IEC 29161:2016 establishes a unique identification scheme for the Internet of Things (IoT), based on existing and evolving data structures.
Privacy capability assessment model
ISO/IEC 29190
Reference Architecture Description
Systems and software engineering — Architecture description
ISO/IEC/IEEE 42010:2011 defines requirements on the description of system, software and enterprise architectures. It aims to standardise the practice of architecture description by defining standard terms, presenting a conceptual foundation for expressing, communicating and reviewing architectures and specifying requirements that apply to architecture descriptions, architecture frameworks and architecture description languages. Following its predecessor, IEEE Std 1471, the standard makes a strict distinction between Architectures and Architecture Descriptions. The description of ISO/IEC/IEEE 42010 in this article is based upon the standard published in 2011.
ISO/IEC 42010
Energy management systems – Requirements with guidance for use is a specification created by the International Organization for Standardization (ISO) for an energy management system.
ISO 50001
Geometrical product specifications (GPS) -- Geometrical tolerancing -- Datums and datum systems--ISO 5459:2011 specifies terminology, rules and methodology for the indication and understanding of datums and datum systems in technical product documentation
ISO 5459
ISO 61508
Automation systems and integration
Geometrical product specifications (GPS) -- Dimensional and geometrical tolerances for moulded parts -- General tolerances for castings using profile tolerancing in a general datum system
ISO 8062-4
The ISO 9000 family of quality management systems standards is designed to help organizations ensure that they meet the needs of customers and other stakeholders while meeting statutory and regulatory requirements related to a product or program.
ISO 9000
ISO/IEC 9594-8:2017 addresses some of the security requirements in the areas of authentication and other security services through the provision of a set of frameworks upon which full services can be based. Specifically, this Recommendation | International Standard defines frameworks for: - public-key certificates; and - attribute certificates.
ISO/IEC 9594
Information technology -- Open Systems Interconnection -- The Directory -- Part 8: Public-key and attribute certificate frameworks
ISO/IEC 9594-8
ISO ASTM 52915:2016 provides the specification for the Additive Manufacturing File Format (AMF), an interchange format to address the current and future needs of additive manufacturing technology.
ISO ASTM 52915
COLLADA
ISO-PAS 17506-2012 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.
SO/PAS 17506:2012 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 ISO/PAS 17506:2012 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. ISO/PAS 17506:2012 covers the initial design and specifications of the COLLADA schema, as well as a minimal set of requirements for COLLADA exporters.
ISO PAS 17506
SO/TS 14649-201:2011 specifies the technology-specific machine tool description data elements needed as process data for manufacturing and machine characteristics. The machine tool descriptions covered in this schema are, initially, milling machines, machining centres, turning machines and multi-tasking machines.ISO/TS 14649-201:2011 is not intended to replace existing machine tool description standards, but to cover the specific needs of manufacturing resource description for manufacturing needs in the technologies described in ISO 14649.
ISO TS 14649-201
IT Security
Information Security Management
The Reference Architecture (IVRA) of the Industrial Value Chain Initive (IVI) proposes a system architecture for the manufactoring domain targeting interoperability and communicational aspects.
Industrial Value Chain Reference Architecture
IVRA
The concern how to identify a participant (client, endpoint etc.) in the internet.
Identification
Publications referred: '<https://doi.org/10.1016/j.jksuci.2016.10.003>' 'Survey on domain specific IoT architectures' 'Page 299'
The Trusted Connector is an Apache Karaf-based platform for the Industrial Internet of Things (IIoT). It supports Docker and trust|me as containerization environments and provides the following features: - Message routing and conversion between protocols with Apache Camel - Apps in isolated containers - Data flow- and data usage control - An Apache Camel component for secure communication and remote attestation between Connectors.
Trusted Connector
Industrial Automation
Industrial automation deals primarily with the automation of manufacturing, quality control and material handling processes. General purpose controllers for industrial processes include Programmable logic controllers, stand-alone I/O modules, and computers. Industrial automation is to replace the decision making of humans and manual command-response activities with the use of mechanized equipment and logical programming commands. One trend is increased use of Machine vision to provide automatic inspection and robot guidance functions, another is a continuing increase in the use of robots. Industrial automation is simply done at the industrial level.
AII Industrial Internet Architecture
Industrial Internet involves all industrial segment and all entities of industry field and ICT field, and it’s forming a complicated and total new ecological system. With industrial system networking and collaboration increasing, lots of new standardization requirements rise. While considering about the problems for Industrial Internet such as standard lacking, standard lagging, and standard duplicated, under the guidance of the Ministry of Industry and Information Technology (MIIT), Alliance of Industrial Internet (referred to as AII hereinafter) launched the study on the Industrial Internet standard system. Based on Industrial Internet Architecture (Version 1.0) and research on Industrial Internet standard requirements, AII drafted the Report on Industrial Internet Standard System (Version 1.0). In this Report, we propose the general idea, basic principles, standard system framework, key standardization directions and promotion suggestions. It aims to provide a systemized guidance of Industrial Internet standardization for the industrial communities, to provide references and basis for development and amendment of Industrial Internet national standards, industrial standards and group standards, and to provide support for Industrial Internet development.
Industrial Internet Standard System
Industrial Internet Architecture Version 1
Industrial Internet of Things Volume G4: Security Framework
Industrial Internet of Things Volume G4: Security Framework IIC:PUB:G4:V1.0:PB:20160926
Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative
Industrial Value Chain Reference Architecture (IVRA)
Industrial Value Chain Reference Architecture (IVRA)- Next
Industrial Value Chain Reference Architecture (IVRA) Industrial Value Chain Initiative Next
The GEs in the I2ND chapter provide three sets of functionalities. The first is an advanced integration middleware to be used by all FIWARE GEs with high performance communication needs Open networking elements enable cloud network application developers to build value-added services in private, enterprise and public settings. The third set of functionalities enables the management of robots by means of platform components and interfaces towards other FIWARE GEs, allowing users to develop smarter and faster robotic applications.
FIWARE Interface to Networks and Devices
ICS
IoT Architecture
After much discussion about the core concepts of the IoT for several years, in 2009 a group of researchers from more than 20 large industrial companies and research institutions joined forces to lay the foundation for the much needed common ground or a common “architecture” for the Internet of Things: the IoTArchitecture project (IoT-A) was born. IoT-A has become the European Commission’s flagship project in the European Union’s Seventh Framework Program for Research and Development with respect to establishing an architecture for the Internet of Things.
IoT-A
IoTivity is an open source project hosted by the Linux Foundation, and sponsored by the OIC. (source: https://www.postscapes.com/internet-of-things-protocols/)
IoTivity
IoT-A Availability and Resilience
IoT-A Deployment and Operation
IoT-A Evolution and Interoperability
IoT-A Functional Viewpoint
One of the main purposes of connected and smart objects in the IoT is the exchange of information between each other and also with external systems. Therefore the way how to define, structure, store, process, manage and exchange information is very important. The information view helps to generate an overview about static information structure and dynamic information flow. (source: Bassi et al.: Enabling Things to Talk)
IoT-A Information Viewpoint
IoT-A Performance and Scalability
IoT-A Reference Architecture
IoT-A Trust Security and Privacy
IPSO Application Framework (PDF): This design defines sets of REST interfaces that may be used by a smart object to represent its available resources, interact with other smart objects and backend services. This framework is designed to be complementary to existing Web profiles including SEP2 and oBIX. (source: https://www.postscapes.com/internet-of-things-protocols/)
IPSO App Framework
Industrial Value Chain Initiative
The Industrial Value Chain Initiative (IVI) is a forum to design a new society by combining manufacturing and information technologies, and for all enterprises to take an initiative collaboratively.
IVI
The activity layer has a view point of activities actually conducted at various places in manufacturers. People and machines acting voluntarily, human activity, machine processes, and information as an object og such activities and processes are brought up for discussion. In every production site of every manufacturer, concrete manufacturing activities are conducted in a different way. (source: IVRA-Next)
IVI Activity Layer
IVI Activity View
IVI Asset View
In the business layer, from a perspective of enterprise management, the focus of discussions is placed on the fundamentel structure of manufacturing, organization forms for manufacturing, presence of essential perspectives and axes as well as a philosophy and concept of values underpinning the big picture. (source: IVRA-Next)
IVI Business Layer
IVI Management View
In the specification layer, the following will be considered: Specific operations based on human activities and machine processes and the things and information items that are their subjects, as well as the data and their attributes that are the subject of the processes executed by logic in software. (source: IVRA-Next)
IVI Specification Layer
JMS (Java Message Service) - A Java Message Oriented Middleware (MOM) API for sending messages between two or more clients. (source: https://www.postscapes.com/internet-of-things-protocols/)
JMS
KATS
Korean Agency for Technology and Standards
Korean Agency for Technology and Standards is the government standards organization for South Korea. It is part of the Ministry of Knowledge Economy. It is authorized to regulate and manage the legal measures of South Korea by the current Measures Act.
LLAP (lightweight local automation protocol): is a simple short message that is sent between inteligent objects using normal text, it's not like TCP/IP, bluetooth, zigbee, 6lowpan, WiFi etc which achieve at a low level 'how' to move data around. This means LLAP can run over any communication medium. The three strengths of LLAP are, it'll run on anything now, anything in the future and it's easily understandable by humans. (source: https://www.postscapes.com/internet-of-things-protocols/)
LLAP
LWM2M (Lightweight M2M) is a system standard in the Open Mobile Alliance. It includes DTLS, CoAP, Block, Observe, SenML and Resource Directory and weaves them into a device-server interface along with an Object structure. (source: https://www.postscapes.com/internet-of-things-protocols/)
LWM2M
LoRaWAN - Network protocol intended for wireless battery operated Things in regional, national or global network. (source: https://www.postscapes.com/internet-of-things-protocols/)
LoRaWAN
6LoWPAN is an acronym of IPv6 over Low power Wireless Personal Area Networks. It is an adaption layer for IPv6 over IEEE802.15.4 links. This protocol operates only in the 2.4 GHz frequency range with 250 kbps transfer rate. (source: https://www.postscapes.com/internet-of-things-protocols/)
6LoWPAN
LsDL (Lemonbeat smart Device Language) - XML-based device language for service oriented devices. (source: https://www.postscapes.com/internet-of-things-protocols/)
LsDL
LTE-MTC (LTE-Machine Type Communication) - Standards-based family of technologies supports several technology categories, such as Cat-1 and CatM1, suitable for the IoT. (source: https://www.postscapes.com/internet-of-things-protocols/)
LTE-MTC
Machine to machine Communication
Machine to machine refers to direct communication between devices using any communications channel, including wired and wireless
Machine to Machine
Manufacturing Enterprise Solutions Association
The Manufacturing Enterprise Solutions Association International is a global community of manufacturers, producers, industry leaders, and solution providers who are focused on driving business results from manufacturing information.
Ministry of Industry and Information Technology
Ministry of Industry and Information Technology (MIIT) of the Chinese government, established in March 2008, is the state agency of the People's Republic of China responsible for regulation and development of the postal service, Internet, wireless, broadcasting, communications, production of electronic and information goods, software industry and the promotion of the national knowledge economy.
MTConnect
MTConnect is a protocol designed for the exchange of data between shop floor equipment and software applications used for monitoring and data analysis. MTConnect is referred to as a read-only standard, meaning that it only defines the extraction (reading) of data from control devices, not the writing of data to a control device. Freely available, open standards are used for all aspects of MTConnect. Data from shop floor devices is presented in XML format, and is retrieved from information providers, called Agents, using Hypertext Transfer Protocol (HTTP) as the underlying transport protocol. MTConnect provides a RESTful interface, which means the interface is stateless. No session must be established to retrieve data from an MTConnect Agent, and no logon or logoff sequence is required (unless overlying security protocols are added which do). Lightweight Directory Access Protocol (LDAP) is recommended for discovery services.
MTConnect Institute
MTConnect Institute is a collaborative effort to develop technical standards and specifications intended to foster greater interoperability between automation/control applications, field systems/devices, and business/office applications in the manufacturing industry ("MTConnect Specifications"), as well as schema, prototype software examples, and related documentation in order to facilitate the implementation of the MTConnect Specifications in compliant applications, drivers, and other services
MathML is a low-level specification for mathematical and scientific content on the Web and beyond
MathML
Mihini/M3DA: The Mihini agent is a software component that acts as a mediator between an M2M server and the applications running on an embedded gateway. M3DA is a protocol optimized for the transport of binary M2M data. It is made available in the Mihini project both for means of Device Management, by easing the manipulation and synchronization of a device's data model, and for means of Asset Management, by allowing user applications to exchange typed data/commands back and forth with an M2M server, in a way that optimizes the use of bandwidth (source: https://www.postscapes.com/internet-of-things-protocols/)
Mihini
Modbus
Modbus is a serial communications protocol to be used in Programmable logic controllers (PLCs).
ModBus
Muhammad Usman
NERC
North American Electric Reliability Corporation
The North American Electric Reliability Corporation (NERC) is a not-for-profit international regulatory authority whose mission is to assure the effective and efficient reduction of risks to the reliability and security of the grid. NERC develops and enforces Reliability Standards; annually assesses seasonal and long‐term reliability; monitors the bulk power system through system awareness; and educates, trains, and certifies industry personnel. NERC’s area of responsibility spans the continental United States, Canada, and the northern portion of Baja California, Mexico. NERC is the electric reliability organization (ERO) for North America, subject to oversight by the Federal Energy Regulatory Commission (FERC) and governmental authorities in Canada. NERC's jurisdiction includes users, owners, and operators of the bulk power system, which serves more than 334 million people.
Based on the standard ISO/IEC 18092:2004, using inductive coupled devices at a center frequency of13.56 MHz. The data rate is up to 424 kbps and the rangeis with a few meters short compared to the wireless sensornetworks. (source: https://www.postscapes.com/internet-of-things-protocols/)
NFC
Next Generation Service Interface
The FIWARE NGSI (Next Generation Service Interface) API defines - a data model for context information, based on a simple information model using the notion of context entities - a context data interface for exchanging information by means of query, subscription, and update operations - a context availability interface for exchanging information on how to obtain context information (whether to separate the two interfaces is currently under discussion).
NGSI
National Institute of Standards and Technology
The National Institute of Standards and Technology (NIST) is a measurement standards laboratory, and a non-regulatory agency of the United States Department of Commerce.
Describes Business Process Execution concept.
Business Process Execution
Privacy Risk Management for Federal Information Systems
This document provides an introduction to the concepts of privacy engineering and risk management for federal information systems. These concepts establish the basis for a common vocabulary to facilitate better understanding and communication of privacy risk within federal information systems, and the effective implementation of privacy principles. This publication introduces two key components to support the application of privacy engineering and risk management: privacy engineering objectives and a privacy risk model.
NIST Internal Report (NISTIR) 8062
NISTIR 8062
Describes the NIST Initiative
NISTIR_8107
TODO - improve this classification
Describes the National Institute of Standards and Technology Initiative, i.e., NIST which provides a standard landascape
NIST Initiative
Manufacturing Model Data Standards define the data needed to manufacture a product from a design.
Manufacturing Model Data
Modeling practice standards define digital product-definition data practices for both two-dimensional (2D) drawings and three-dimensional (3D) models.
Modeling Practice
These standards capture the representation of product and engineering information to enable data exchange between CAD software from different vendors.
Product Model Data Exchange
NIST Cloud Computing Standards Roadmap
The NIST Cloud Computing Standards Roadmap Working Group has surveyed the existing standards landscape for security, portability, and interoperability standards/models/studies/use cases, etc., relevant to cloud computing. Using this available information, current standards, standards gaps, and standardization priorities are identified in this document. The NIST Definition of Cloud Computing identified cloud computing as a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction.
NIST 500-291
NIST Cloud Computing Reference Architecture
The adoption of cloud computing into the Federal Government and its implementation depend upon a variety of technical and non-technical factors. A fundamental reference point, based on the NIST definition of Cloud Computing, is needed to describe an overall framework that can be used government-wide. This document presents the NIST Cloud Computing Reference Architecture (RA) and Taxonomy (Tax) that will accurately communicate the components and offerings of cloud computing.
NIST 500-292
US Government Cloud Computing Technology Roadmap
The National Institute of Standards and Technology (NIST), consistent with its mission, has a technology leadership role in support of United States Government (USG) secure and effective adoption of the Cloud Computing model to reduce costs and improve services. This role is described in the 2011 Federal Cloud Computing Strategy as “... a central one in defining and advancing standards, and collaborating with USG Agency CIOs, private sector experts, and international bodies to identify and reach consensus on cloud computing technology & standardization priorities.” This NIST Cloud Computing program and initiative to develop a USG Cloud Computing Technology Roadmap is one of several complementary and parallel USG initiatives defined in the broader Federal Cloud Computing Strategy referenced above. The Federal Cloud Computing Strategy characterizes cloud computing as a “profound economic and technical shift (with) great potential to reduce the cost of federal Information Technology (IT) systems while … improving IT capabilities and stimulating innovation in IT solutions.” In the technology vision of Federal Cloud Computing Strategy success, USG agencies will be able to easily locate desired IT services in a mature and competitive marketplace, rapidly procure access to these services, and use them to deliver innovative mission solutions. Cloud services will be secure, interoperable, and reliable. Agencies will be able to switch between providers easily and with minimal cost, and receive equal or superior service.
NIST 500-293
Guidelines on Security and Privacy in Public Cloud Computing
Cloud computing can and does mean different things to different people. The common characteristics most interpretations share are on-demand scalability of highly available and reliable pooled computing resources, secure access to metered services from nearly anywhere, and displacement of data and services from inside to outside the organization. While aspects of these characteristics have been realized to a certain extent, cloud computing remains a work in progress. This publication provides an overview of the security and privacy challenges pertinent to public cloud computing and points out considerations organizations should take when outsourcing data, applications, and infrastructure to a public cloud environment.
NIST 800-144
Cloud Computing Synopsis and Recommendations
This document reprises the NIST-established definition of cloud computing, describes cloud computing benefits and open issues, presents an overview of major classes of cloud technology, and provides guidelines and recommendations on how organizations should consider the relative opportunities and risks of cloud computing.
NIST 800-146
NanoIP, which stands for the nano Internet Protocol, is a concept that was created to bring Internet-like networking services to embedded and sensor devices, without the overhead of TCP/IP. NanoIP was designed with minimal overheads, wireless networking, and local addressing in mind. (source: https://www.postscapes.com/internet-of-things-protocols/)
NanoIP
NB-IoT (Narrow-Band IoT) A technology being standardized by the 3GPP standards body. (source: https://www.postscapes.com/internet-of-things-protocols/)
NB-IoT
NGSI-LD API Operation
NGSI-LD Architecture
NGSI-LD Data Representation
The FIWARE data models have been harmonized to enable data portability for different applications including, but not limited, to Smart Cities. They are intended to be used together with FIWARE NGSI version 2. If you want to contribute and create additional data models, please have a look at our repository of data models and the data model development guidelines. (source: https://www.fiware.org/developers/data-models/)
NGSI-LD Information Model
Open Applications Group Integration Specification
The Open Applications Group Integration Specification (OAGIS) is an effort to provide a canonical business language for information integration. It uses XML as the common alphabet for defining business messages, and for identifying business processes (scenarios) that allow businesses and business applications to communicate.
OAGIS
Open Applications Group
The Open Applications Group is a not-for-profit standards development organization. Founded in 1994, is focused on building enterprise ready process-based data exchange standards for both B2B and A2A integration.
OAGi
Organization for the Advancement of Structured Information Standards
The Organization for the Advancement of Structured Information Standards (OASIS) is a global nonprofit consortium that works on the development, convergence, and adoption of standards for security, Internet of Things, energy, content technologies, emergency management, and other areas.
OCF Core Specification VERSION 2.0.1 | February 11, 2019
The Open Digital Rights Language (ODRL) is a policy expression language that provides a flexible and interoperable information model, vocabulary, and encoding mechanisms for representing statements about the usage of content and services. The ODRL Information Model describes the underlying concepts, entities, and relationships that form the foundational basis for the semantics of the ODRL policies. Policies are used to represent permitted and prohibited actions over a certain asset, as well as the obligations required to be meet by stakeholders. In addition, policies may be limited by constraints (e.g., temporal or spatial constraints) and duties (e.g. payments) may be imposed on permissions.
ODRL
Open Digital Rights Language
ODVA, Inc
Founded in 1995, ODVA is a global association whose members comprise the world’s leading automation companies. ODVA’s mission is to advance open, interoperable information and communication technologies in industrial automation. ODVA recognizes its media independent network protocol, the Common Industrial Protocol or “CIP” — and the network adaptations of CIP — EtherNet/IP, DeviceNet, CompoNet and ControlNet — as its core technology and the primary common interest of its membership. For future interoperability of production systems and the integration of the production systems with other systems, ODVA embraces the adoption of commercial-off-the-shelf (COTS) and standard, unmodified Internet and Ethernet technologies as a guiding principle wherever possible. This principle is exemplified by EtherNet/IP — the world’s number one industrial Ethernet network.
The agility pillar addresses business operational decisions for an OpenFog RA deployment. It is not possible for humans alone to analyze the data generated at the scale predicted by IoT as the basis for rapid, sound business and operational decisions. The agility pillar focuses on transforming this volume of data into actionable insights. Agility also deals with the highly dynamic nature of fog deployments and the need to respond quickly to change. source: OpenFog Reference Architecture
OpenFog Agility Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.7 Agility Pillar' 'Page 31'
The autonomy pillar enables fog nodes to continue to deliver the designed functionality in the face of the external service failures. In this architecture, autonomy is supported throughout the hierarchy. Decision making will be made at all levels of a deployment’s hierarchy including near the device or higher order layers. Centralized decision-making in the cloud is no longer the only option. Autonomy at the network edge means intelligence from local devices and peer data can be used to fulfill the business’ mission at the point where it makes the most business sense.
OpenFog AutonomyPillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.4 Autonomy Pillar' 'Page 27'
OpenFog Data Analytics and Control Perspective
How fog software and fog systems are deployed to address a given scenario is also very important. There are many deployment types ranging from embedded to large clustered systems that are fully interconnected. The deployment type(s) chosen are scenario specific, but key aspects of the architecture remain visible regardless of deployment type. However, some may grow or shrink in importance. source: OpenFog Reference Architecture
OpenFog Deployment Viewpoint
The functional viewpoint of the architecture shows how we apply the OpenFog architectural elements and views to address the various concerns of the stakeholders to satisfy a given scenario. Each scenario chosen will focus on a different aspects and market opportunities for fog computing. We fully expect that the architectural description, views, and perspective may change over time. This change and refinement should be driven from testbeds and application of the OpenFog RA to multiple different markets we see as important to fog computing. source: OpenFog Reference Architecture
OpenFog Functional Viewpoint
OpenFog RA computing resources can be seen as a logical hierarchy based on the functional requirements of an end-to-end IoT system. Depending on the scale and nature of the scenario being addressed, the hierarchy may be a network of smart and connected partitioned systems arranged in physical or logical layers, or it may collapse into a single physical system (scalability pillar). source: OpenFog Reference Architecture
OpenFog Hierarchy Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.8 Hierarchy Pillar' 'Page 31'
Fog applications and services should have the flexibility to span and interoperate with various levels in a fog hierarchy. This is a foundational aspect of fog computing that enables a multi-vendor ecosystem. In addition, the data that is collected or generated by one fog node should be shareable with other nodes in the hierarchy. The figure below shows a cross-fog application spanning east to west nodes (it would also be able to span north to south). source: OpenFog Reference Architecture
OpenFog IT Business and Cross-fog Applications Perspective
Many fog computing deployments involve machine vision, and associated human-like functions. As such, they have the ability to see, respond, remember, move, and make autonomous decisions in order to participate in other fog services. This range of actions requires a higher level of manageability than a traditional static model. In addition, fog nodes may be deployed in a wide range of locations: remote, fixed and non-fixed, and environmentally harsh conditions. source: OpenFog Reference Architecture
OpenFog Manageability Perspective
The node view is the lowest level view we currently utilize in the architectural description. The stakeholders involved in formulating the viewpoint (and subsequently this view) are the system on a chip designers, silicon manufacturers, firmware architects, and system architects. source: OpenFog Reference Architecture
OpenFog Node View
Openness is essential for the success of a ubiquitous fog computing ecosystem for IoT platforms and applications. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on system cost, quality and innovation. The openness pillar importance is highlighted in our desire for fully interoperable systems, supported by a vibrant supplier ecosystem. source: OpenFog Reference Architecture
OpenFog Opennes Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.3 Openness Pillar' 'Page 26'
Performance and Scale Perspective
The programmability pillar enables highly adaptive deployments including support for programming at the software and hardware layers. This means that re-tasking a fog node or cluster of fog nodes for accommodating operational dynamics, can be completely automated. The re-tasking can be done with the help of the fog nodes inherent programmability interfaces which we describe using general purpose compute or accelerator interfaces. source: OpenFog Reference Architecture
OpenFog Programmability Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.5 Programmability Pillar' 'Page 29'
The scalability pillar addresses the dynamic technical and business needs behind fog deployments. Elastic scalability cuts across all fog computing applications and verticals. The hierarchical properties of fog and its location at logical edges of networks add additional scaling opportunities. source: OpenFog Reference Architecture
OpenFog Scalability Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.2 Scalability Pillar' 'Page 24'
OpenFog Security Perspective
Security implementations have many different descriptions and attributes such as privacy, anonymity, integrity, trust, attestation, verification, and measurement. These are key attributes for the OpenFog RA. Achieving the foundational elements for security requires an approach to discover, attest, and verify all smart and connected “things” before trust can be established source: OpenFog Reference Architecture
Security in the OpenFog RA is not a one-size-fits-all architecture. Rather, it describes all of the mechanisms that can be applied to make a fog node secure from silicon to software application. Business case, target market, and vertical use case, as well as the location of the node itself, will all create a set of requirements for that node. However, there are certain foundational parts of the architecture, which must be in place in order to build a secure execution environment. source: OpenFog Reference Architecture
OpenFog Security Pillar
Publications referred: ' <https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.1 Security Pillar' 'Page 23'
OpenFog Software Architecture View
The software view of the OpenFog RA is composed of software running on a platform that is comprised of one or more node views coupled with other components to create a system addressing a given scenario. The stakeholders of the software view include the system integrators, software architects, solution designers, and application developers of a fog computing environment. The software running on fog platforms is used to satisfy a given deployment scenario. A robust fog deployment requires that the relationship between a fog node, fog platform, and fog software are seamless. source: OpenFog Reference Architecture
The system view of the OpenFog RA is composed of one or more node views coupled with other components to create a platform. The stakeholders which typically create these systems to facilitate a fog deployment comprise the concerns of this viewpoint. Subsequently this view is intended to address the concerns of the system architects, hardware OEMs, and platform manufacturers. They also need to understand the Node view such that the systems they create can be deployed to address a given scenario. source: OpenFog Reference Architecture
OpenFog System Architecture View
Reliability, availability, and serviceability (RAS) is resident throughout successful system architectures and, as such, takes on great importance in the OpenFog RA. Hardware, software, and operations are the three main areas of the RAS pillar. source: OpenFog Reference Architecture
OpenFog RAS Pillar
Publications referred: '<https://www.openfogconsortium.org/wp-content/uploads/OpenFog_Reference_Architecture_2_09_17-FINAL.pdf> OPFRA001.020817' '4.6 Reliability, Availability, and Serviceability (RAS)Pillar' 'Page 29'
OMA (Open Mobile Alliance) is the Leading Industry Forum for Developing Market Driven, Interoperable Mobile Service Enablers (source: https://www.postscapes.com/internet-of-things-protocols/)
Open Mobile Alliance
The motivation of LightweightM2M is to develop a fast deployable client-server specification to provide machine to machine service. LightweightM2M is principly a device management protocol, but it should be designed to be able to extend to meet the requirements of applications. LightweightM2M is not restricted to device management, it should be able transfer service / application data. (source: https://www.postscapes.com/internet-of-things-protocols/)
Lightweight M2M v1.0
Object Management Group
The Object Management Group (OMG) is an international, open membership, not-for-profit technology standards consortium. OMG Task Forces develop enterprise integration standards for a wide range of technologies and industries. OMG modeling standards enable visual design, execution and maintenance of software and other processes. Originally aimed at standardizing distributed object-oriented systems, the company now focuses on modeling (programs, systems and business processes) and model-based standards.
Data Distribution Service for real-time systems
The Data Distribution Service for real-time systems (DDS) is an Object Management Group (OMG) machine-to-machine (sometimes called middleware) standard that aims to enable scalable, real-time, dependable, high-performance and interoperable data exchanges using a publish–subscribe pattern. DDS addresses the needs of applications like financial trading, air-traffic control, smart grid management, and other big data applications. The standard is used in applications such as smartphone operating systems, transportation systems and vehicles, software-defined radio, and by healthcare providers. DDS was promoted for use in the Internet of things.
OMG DDS
OPC Foundation
Is an industry consortium that creates and maintains standards for open connectivity of industrial automation devices and systems, such as industrial control systems and process control generally
OPC XML-DA builds on the OPC Data Access specifications to communicate data in XML. Incorporates SOAP and Web services
OPC_XML-DA
Open Trust Protocol (OTrP) - A protocol to install, update, and delete applications and to manage security configuration in a Trusted Execution Environment (TEE). (source: https://www.postscapes.com/internet-of-things-protocols/)
Open Trust Protocol
Ocean Protocol Business Viewpoint
Ocean Protocol Marketplace Viewpoint
Ocean is a decentralized protocol and network of artificial intelligence (AI) data/services. It incentivizes for a vast supply of relevant AI data/services. This network helps to power AI data/service marketplaces, as well as public commons data. The heart of Ocean’s network is a new construction: a Curated Proofs Market. CPMs bridge predicted relevance with actual relevance of each AI service, by having curation markets for cryptographic proofs (e.g. proof of data availability). (source: https://oceanprotocol.com/tech-whitepaper.pdf)
Ocean Protocol
Ocean Protocol is supported by a Singapore based non-profit foundation, whose mandate is to ensure open access to the protocol and platform, provide data governance, encourage the network ecosystem growth and take measures to ensure that the platform becomes ever more decentralized with time.
Ocean Protocol Foundation
Ocean Protocol System Viewpoint
Ocean Protocol: A Decentralized Data Exchange Protocol,powered by blockchain technology and a cryptotoken. Business Strategy. Oct 2017
Ocean Protocol: A Decentralized Data Exchange Protocol to Unlock Data for Artificial Intelligence. Reference Marketplace Framework. Feb 2019
Ocean Protocol: A Decentralized Substrate for AI Data & Services . Technical Whitepaper. Apr 2019
OCF Core Framework
OCF Data Models
OCF Framework
OCF L2 Connectivity
OCF Networking
OCF Security
The OpenAPI Specification (originally known as the Swagger Specification) is a specification for machine-readable interface files for describing, producing, consuming, and visualizing RESTful web services. A variety of tools can generate code, documentation and test cases given an interface file. Development of the OpenAPI Specification (OAS) is overseen by the Open API Initiative, an open source collaborative project of the Linux Foundation. (source: wikipedia)
OpenAPI
The Open Connectivity Foundation (OCF) is an industry group whose stated mission is to develop specification standards, promote a set of interoperability guidelines, and provide a certification program for devices involved in the Internet of Things (IoT). It has become one of the biggest industrial connectivity standards organizations for IoT, including in its membership Samsung Electronics, Intel, Microsoft, Qualcomm and Electrolux. Currently, there are more than 300 member companies. source: wikipedia
OpenFog Architecture Overview
The OpenFog Architecture is a system-level architecture that extends elements of compute, networking and storage across the cloud through to the edge of the network. This approach is particularly suited to IoT systems and accelerates the decision-making velocity. This architecture serves a specific subset of business problems that can’t be successfully implemented using “cloud only” based architectures or relying solely on intelligent edge devices. OpenFog should be thought of as complementary to, and an extension of the traditional cloud based model where implementations of the architecture can reside in multiple layers of a network’s topology. The goal of the OpenFog architecture is to facilitate deployments which highlight interoperability, performance, security, scalability, programmability, reliability, availability, serviceability, and agility. Proprietary or single vendor solutions can result in limited supplier diversity, which can have a negative impact on market adoption, system cost, quality and innovation.
The OpenFog Consortium work is done by committees and workgroups focused on specific tasks aligned to our mission. This work includes technical work; influencing standards development through liaisons with other organizations; testbed; promoting innovation and industry interest in fog computing; and industry education.
OpenFog Consortium
The OpenFog Reference Architecture (OpenFog RA) is intended to help business leaders, software developers, silicon architects, and system designers create and maintain the hardware, software and system elements necessary for fog computing.
OpenFog Reference Architecture
OpenFog Reference Architecture for Fog Computing
Open or Free License
OpenWSN Serves as a repository for open-source implementations of protocol stacks based on Internet of Things standards, using a variety of hardware and software platforms. (source: https://www.postscapes.com/internet-of-things-protocols/)
OpenWSN
ORION Context Broker
Physical Web - The Physical Web enables you to see a list of URLs being broadcast by objects in the environment around you with a Bluetooth Low Energy (BLE) beacon. (source: https://www.postscapes.com/internet-of-things-protocols/)
Physical Web
Platform Industry 4.0
Plattform Industrie 4.0
Published under a Private License.
Private License
Priyanka Nanjappa
Product catalog data standards support the description of particular instances of products or parts in a uniform, vendor-neutral way.
Product Catalog Data
Product lifecycle data management focuses on the needs of long-term retention and access to data consistently throughout the product lifecycle.
Production Life Cycle Management
A product manager communicates product vision from the highest levels of executive leadership to development and implementation teams. The product manager is often called the product CEO. The product manager investigates, selects, and drives the development of products for an organization, performing the activities of product management. (source: wikipedia)
Product Manager
Production lifecycle data management standards define general models of data integration, sharing, exchange, and hand-over for lifecycle support of production facilities.
Production Life Cycle Data Management
Standards can interconnect engineering tools from different disciplines, e.g., system engineering, mechanical plant engineering, electrical design, process engineering, process control engineering, Human Machine Interface (HMI) development, PLC programming, and robotic programming.
Production System Engineering
Classifies standards define data processing, communication, and presentation standards for condition monitoring and diagnostics of machines, for maintaining the adequate performance of the system, and for searching ways to improve performance
Production System Maintenance
Provide information models for factory and production system design. They enhance information exchange among stakeholders, and enable virtual commissioning, which can improve manufacturing agility and reduce manufacturing cost.
Production System Model Data
Published under a Public License.
Public License
Quality Information Framework (QIF) standard defines an integrated set of information models which enable the effective exchange of metrology data throughout the entire manufacturing quality measurement process
Quality Information Framework
Is implemented in XML
QUIC (Quick UDP Internet Connections, pronounced quick) supports a set of multiplexed connections between two endpoints over User Datagram Protocol (UDP), and was designed to provide security protection equivalent to TLS/SSL, along with reduced connection and transport latency, and bandwidth estimation in each direction to avoid congestion. (source: https://www.postscapes.com/internet-of-things-protocols/)
QUIC
RAML (RESTful API Modeling Language) - Makes it easy to manage the whole API lifecycle from design to sharing. It's concise - you only write what you need to define - and reusable. (source: https://www.postscapes.com/internet-of-things-protocols/)
RAML
REST (Representational state transfer) - RESTful HTTP (source: https://www.postscapes.com/internet-of-things-protocols/)
REST
Requirements for Internet Hosts -- Communication Layers
This is one RFC of a pair that defines and discusses the requirements for Internet host software. This RFC covers the communications protocol layers: link layer, IP layer, and transport layer; its companion RFC-1123 covers the application and support protocols.
RFC 1122
The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred.
HTTP/1.1
RFC 2616
This memo describes how to use TLS to secure HTTP connections over the Internet. Current practice is to layer HTTP over SSL (the predecessor to TLS), distinguishing secured traffic from insecure traffic by the use of a different server port. This document documents that practice using TLS. A companion document describes a method for using HTTP/TLS over the same port as normal HTTP [RFC2817].
HTTPS
RFC 2818
Lightweight Directory Access Protocol
LDAP
This document specifies Version 1.2 of the Transport Layer Security (TLS) protocol. The TLS protocol provides communications security over the Internet. The protocol allows client/server applications to communicate in a way that is designed to prevent eavesdropping, tampering, or message forgery.
RFC 5246
This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a "bearer") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport.
RFC 6750
OAuth2.0
The Constrained Application Protocol
The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for use with constrained nodes and constrained (e.g., low-power, lossy) networks. The nodes often have 8-bit microcontrollers with small amounts of ROM and RAM, while constrained networks such as IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) often have high packet error rates and a typical throughput of 10s of kbit/s. The protocol is designed for machine-to-machine (M2M) applications such as smart energy and building automation.
RFC 7252
CoAP
JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.
JSON Web Token
RFC 7519
This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP), referred to as HTTP version 2 (HTTP/2). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.
RFC 7540
SCIM Use Cases
This document provides definitions and an overview of the System for Cross-domain Identity Management (SCIM). It lays out the system's concepts, models and flows, and includes user scenarios, use cases, and requirements.
RFC 7642
SCIM Core Schema
This document provides a platform neutral schema and extension model for representing users and groups and other resource types in JSON format. This schema is intended for exchange and use with cloud service providers.
RFC 7643
SCIM API
The System for Cross-Domain Identity Management (SCIM) specification is an HTTP based protocol that makes managing identities in multi domain scenarios easier to support through a standardized service. Examples include but are not limited to enterprise to cloud service providers, and inter-cloud based scenarios. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. SCIM's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document.
RFC 7644
User Datagram Protocol (UDP)
In computer networking, the User Datagram Protocol (UDP) is one of the core members of the Internet protocol suite. The protocol was designed by David P. Reed in 1980 and formally defined in RFC 768. With UDP, computer applications can send messages, in this case referred to as datagrams, to other hosts on an Internet Protocol (IP) network. Prior communications are not required in order to set up communication channels or data paths.
RFC 768
TRANSMISSION CONTROL PROTOCOL
This document describes the DoD Standard Transmission Control Protocol (TCP). There have been nine earlier editions of the ARPA TCP specification on which this standard is based, and the present text draws heavily from them. There have been many contributors to this work both in terms of concepts and in terms of text. This edition clarifies several details and removes the end-of-letter buffer-size adjustments, and redescribes the letter mechanism as a push function.
RFC 793
CoAP (Constrained Application Protocol) is an application layer protocol that is intended for use in resource-constrained internet devices, such as WSN nodes. CoAP is designed to easily translate to HTTP for simplified integration with the web, while also meeting specialized requirements such as multicast support, very low overhead, and simplicity. The CoRE group has proposed the following features for CoAP: RESTful protocol design minimizing the complexity of mapping with HTTP, Low header overhead and parsing complexity, URI and content-type support, Support for the discovery of resources provided by known CoAP services. Simple subscription for a resource, and resulting push notifications, Simple caching based on max-age. (source: https://www.postscapes.com/internet-of-things-protocols/)
ROLL / RPL (IPv6 routing for low power/lossy networks) (source: https://www.postscapes.com/internet-of-things-protocols/)
ROLL
RPMA (Random phase multiple access) A technology communication system employing direct-sequence spread spectrum (DSSS) with multiple access. (source: https://www.postscapes.com/internet-of-things-protocols/)
RPMA
Describes the RAMI model
Describes the Reference Architecture Model for Industry 4.0, i.e., the RAMI Initiative.
RAMI 4.0
RAMI Asset Layer
TODO: Find better class assignement
Administration Shell Body
RAMI Business Layer
RAMI Communication Layer
RAMI Functional Layer
Administration Shell Header
find better class assignment
RAMI Information Layer
Instance Maintenance
Instance Production
RAMI Integration Layer
RAMI Station
Type Development
Type Maintenance
RAMI Work Center
A standard for asynchronous stream processing with non-blocking back pressure on the JVM. (source: https://www.postscapes.com/internet-of-things-protocols/)
Reactive Streams
Bringing electricity into remote areas
Rural Electrification
Describes the SCADA level according to the ISA95 level classification.
SCADA Level
Supervisory control and data acquisition according to ISA 95
IETF System for Cross-domain Identity Management (SCIM) 2.0
The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.
SCIM
Describes Plan-Source-Make-Deliver-Return cycle for managing the manufacturing supply chain.
Supply Chain Management
SCOR
APICS Supply Chain Operations Reference.
Schneider Electric
Schneider Electric SE is a European multinational corporation that specializes in energy management and automation solutions, spanning hardware, software, and services.
SENML (Media Types for Sensor Markup Language) - A simple sensor, such as a temperature sensor, could use this media type in protocols such as HTTP or CoAP to transport the measurements of the sensor or to be configured. (source: https://www.postscapes.com/internet-of-things-protocols/)
SENML
SMCP — A C-based CoAP stack which is suitable for embedded environments. Features include: Support draft-ietf-core-coap-13, Fully asynchronous I/O, Supports both BSD sockets and UIP. (source: https://www.postscapes.com/internet-of-things-protocols/)
SMCP
SOAP (Simple Object Access Protocol) (source: https://www.postscapes.com/internet-of-things-protocols/)
SOAP (abbreviation for Simple Object Access Protocol) is a messaging protocol specification for exchanging structured information in the implementation of web services in computer networks.
SOAP
SSI (Simple Sensor Interface) is a simple communications protocol designed for data transfer between computers or user terminals and smart sensors. (source: https://www.postscapes.com/internet-of-things-protocols/)
SSI
Semantic Sensor Net Ontology - W3C This ontology describes sensors and observations, and related concepts. It does not describe domain concepts, time, locations, etc. these are intended to be included from other ontologies via OWL imports. (source: https://www.postscapes.com/internet-of-things-protocols/)
SSN
STOMP - The Simple Text Oriented Messaging Protocol (source: https://www.postscapes.com/internet-of-things-protocols/)
STOMP
Safety of Machinery
Safety of Machinery domain
SensorML provides standard models and an XML encoding for describing sensors and measurement processes. (source: https://www.postscapes.com/internet-of-things-protocols/)
SensorML
A city that collects data which is used for better Maintenance of it's resources
Smart City
Intelligent technologies in value chain of energy industry
Smart Energy
An electrical grid having smart appliances
Smart Grid
A software architect is a software expert who makes high-level design choices and dictates technical standards, including software coding standards, tools, and platforms. The leading expert is referred to as the chief architect. (source: wikipedia)
Software Architect
Copyright © 2016 IEC Geneva, Switzerland.
The OMG Systems Modeling Language (OMG SysML) is a general-purpose graphical modeling language for specifying, analyzing, designing, and verifying complex systems that may include hardware, software, information, personnel, procedures, and facilities. In particular, the language provides graphical representations with a semantic foundation for modeling system requirements, behavior, structure, and parametrics, which is used to integrate with other engineering analysis models. It represents a subset of UML 2 with extensions needed to satisfy the requirements of the UML for Systems Engineering RFP as indicated in Figure 1. SysML leverages the OMG XML Metadata Interchange (XMI®) to exchange modeling data between tools, and is also intended to be compatible with the evolving ISO 10303-233 systems engineering data interchange standard.
Systems Modeling Language
The systems architect is a professional figure in ICT. Systems architects define the architecture of a computerized system (i.e., a system composed of software and hardware) in order to fulfill certain requirements. Such definitions include: a breakdown of the system into components, the component interactions and interfaces (including with the environment, especially the user), and the technologies and resources to be used in the design. (source: wikipedia)
Systems engineering is an interdisciplinary field of engineering that focuses on how to design and manage complex engineering systems over their life cycles. At its core systems engineering utilizes systems thinking principles to organize this body knowledge. Issues such as requirements engineering, reliability, logistics, coordination of different teams, testing and evaluation, maintainability and many other disciplines necessary for successful system development, design, implementation, and ultimate decommission become more difficult when dealing with large or complex projects. (source: wikipedia)
System Engineer
Terminology
To sanction the terms and definitions used in the different electrotechnical fields and to determine the equivalence of the terms used in the different languages. As a consequence, to prepare an International Electrotechnical Vocabulary aiming at the standardization and coordination of the terms relating to electrical sciences and techniques for use in the technical language and literature, in teaching, in technical specifications and in commercial exchanges, and at giving their equivalents in the different languages.
TC 1
Transmitting equipment for radiocommunication
Standardization of transmitting equipment for radiocommunications purposes and electronic devices employing similar techniques. The standardization work deals with methods of measurement, safety requirements and transmitter control and Interconnection
TC 103
To prepare international standards on quantities and units to be used in electrical technology. Such standards may relate to their definitions, names, letter symbols and use; to the relations in which they appear; and to the signs and symbols used with them.
TC 25
Information structures and elements, identification and marking principles, documentation and graphical symbols
To prepare standards for the electrotechnical and related fields regarding:1) methods and rules associated with the human interpretation of information. This refers to:- presentation of information in technical documentation,- graphical symbols for use in technical documentation,- graphical symbols for the human interaction with equipment,2) methods and rules associated with the handling of information in computer sensible form. This refers to:- information models for the purpose of technical documentation and the exchange of technical information, and the identification of further needs for such models,- definition of data element types and data sets for use in information models and technical documentation, and for exchange of technical information.It includes definition and co-ordination of the information required during the whole life cycle of a device, system, or plant.3) General and safety application concerning the man-machine interface, marking and identification in electrical installations and equipment, marking systems and general rules for:- the meanings of colours and alternative means, when used for marking and identification,- the arrangement of indicating devices and actuators,- coding principles for indicating and actuating devices,- terminal designation of electrical and electronic components, apparatus and equipment,- the termination designation of certain designated conductors,- marking of electrical and electronic equipment with ratings related to supply and to its properties,- marking of bare and insulated conductors.These standards are principally intended for use by technical committees in the preparation of standards in accordance with the principles laid down in IEC Guide 104: Guide to the drafting of Safety Standards, and the role of committees with Safety Pilot Functions and Safety Group Functions, and in ISO/IEC Guide 51: Guidelines for the inclusion of safety aspects in standards.
TC 3
Capacitors and resistors for electronic equipment
To prepare international standards for:a) Capacitors, resistors, thermistors and varistors intended for use in electronic equipment.b) Capacitors, resistors and inductors and complete electromagnetic interference (EMI) suppression filter units for EMI suppression (see note).c) Passive integrated circuits or networks containing resistors, capacitors, inductors or their combinations. For the dimensional standardization of the final package, requirements laid down by TC 47 shall be adopted whenever possible.d) Packaging of electronic components for automatic handling, which is an activity undertaken on behalf of all relevant component technical committees.e) Electric double layer capacitors for use in electric and electronic equipment.Note: In this work, use has to be made as far as possible of any relevant work of TC 51 on inductors, the CISPR on the measurement of EMI suppression characteristics and TC 77 on electromagnetic compatibility (EMC). Liaison has also to be maintained with TC 61, TC 66, TC 108 and other appropriate IEC Technical Committees on the safety aspects of EMI suppression components and filter units.
TC 40
Safety of machinery - Electrotechnical aspects
Standardization in the field of the application of electro-technical equipment and systems to machinery (including a group of machines working together in a coordinated manner, excluding higher-level systems aspects) not portable by hand while working, but which may include mobile equipment. The equipment covered commences at the point of connection of the electrical supply to the machinery.Standardization of interfaces (excluding local area networks and fieldbus) between control equipment and the electro-technical equipment of machinery.Standardization of electrotechnical equipment and systems relating to the safeguarding of persons from hazards of the machinery, its associated equipment and the environment.To coordinate with ISO all matters concerning the safety of machinery..
TC 44
Dependability
To prepare international standards in the field of dependability, in all appropriate technological areas, including those not normally dealt with by IEC Technical Committees. Dependability covers the availability performance and its influencing factors: reliability performance, maintainability performance and maintenance support performance (including management of obsolescence). The standards provide systematic methods and tools for the dependability assessment and management of equipment, services and systems throughout their life cycles. The standards cover generic aspects on reliability and maintainability programme management, testing and analytical techniques, software and system dependability, life cycle costing, technical risk analysis and project risk management. This includes standards related to product issues from component reliability to guidance for engineering dependability of systems, standards related to process issues from technological risk analysis to integrated logistics support and standards related to management issues from dependability program management to managing for obsolescence. The application of these standards may raise safety related issues, though the standards themselves do not cover safety. They may be applied to business risk analysis but these risk areas are not dealt with by TC 56.
TC 56
Power systems management and associated information exchange
To prepare international standards for power systems control equipment and systems including EMS (Energy Management Systems), SCADA (Supervisory Control And Data Acquisition), distribution automation, teleprotection, and associated information exchange for real-time and non-real-time information, used in the planning, operation and maintenance of power systems. Power systems management comprises control within control centres, substations and individual pieces of primary equipment including telecontrol and interfaces to equipment, systems and databases, which may be outside the scope of TC 57. The special conditions in a high voltage environment have to be taken into consideration. Note 1: Standards prepared by other technical committees of the IEC and organizations such as ITU and ISO shall be used where applicable. Note 2: Although the work of TC 57 is chiefly concerned with standards for electric power systems, these standards may also be useful for application by the relevant bodies to other geographical widespread processes. Note 3: Whereas standards related to measuring and protection relays and to the control and monitoring equipment used with these systems are treated by TC 95, TC 57 deals with the interface to the control systems and the transmission aspects for teleprotection systems. Whereas standards related to equipment for electrical measurement and load control are treated by TC 13, TC 57 deals with the interface of equipment for interconnection lines and industrial consumers and producers requiring energy management type interfaces to the control system.
TC 57
Industrial-process measurement, control and automation
To prepare international standards for systems and elements used for industrial-process measurement and control concerning continuous and batch processes.
TC 65
Safety of measuring
control and laboratory equipment
To prepare safety standards for test and measurement equipment, industrial-process control equipment, and laboratory equipment wherever they are used. Such equipment includes: a) equipment and systems to measure, test, generate, and analyse, simple and complex electromagnetic quantities and equipment that by electromagnetic means measure physical quantities. Note: Aspects of this equipment other than safety are covered by other technical committees. b) equipment and systems for industrial-process measurement and control. Note: Aspects of this equipment other than safety are covered by TC 65 except that SC 65A has a Horizontal Safety Function relating to the functional safety of electrical/electronic/ programmable electronic systems and SC 65B is responsible for the functional safety of programmable controllers. c) laboratory equipment for analysis, handling and preparation of materials. Note: This equipment includes measuring instruments, systems and their accessories, for preparation, treatment and analysis of materials in the fields of research, medicine, industry and education, and for environmental monitoring. TC 66 has a Group Safety Function in accordance with IEC Guide 104 for the equipment in categories a) to c) above.
TC 66
Electromagnetic compatibility
Standardization - to prepare standards and technical reports - in the field of electromagnetic compatibility (EMC), with particular emphasis on general application and use by product committees. (Horizontal function). The scope covers the following aspects of EMC: - Immunity and related items, over the whole frequency range: basic and generic standards, - emission in the low frequency range (f <= 9 kHz, e.g. harmonics and voltage fluctuations): basic, generic and product (family) standards, - emission in the high frequency range (f > 9 kHz): disturbances not covered by CISPR 10 (1992), in co-ordination with CISPR (e.g. mains signalling). Product immunity standards are not included. However, at the request of product committees, TC 77 may also prepare such standards under the co-ordination of ACEC. Horizontal Safety Function: Electromagnetic compatibility in so far as safety aspects are involved.
TC 77
To prepare international standards for the protection of buildings, persons, areas and properties against fraudulent actions having the purpose to enter in a place or to take or to use something without permission and other threat related to persons.The scope includes, but is not limited to equipment and systems, either used by ordinary persons or by trained people in the following residential and non residential applications:- Access control systems- Alarm transmission systems- Video surveillance systems- Combined and/or integrated systems even including fire alarm systems*- Fire detection and fire alarm systems*- Intruder and hold-up alarm systems- Remote receiving and/or surveillance centres- Social alarm systems.These systems can be used for providing a local or remote alarm; they can be used for calling private guards, social assistance, fire brigade or police force. They can be used for recording and transmission of dated or undated information, sounds, pictures of places and people for surveillance purposes. The standards cover:- terminology;- technical characteristics regarding performance criteria, reliable operation, installation, maintenance;- testing for detection, monitoring, recording, triggering an alarm and transmission to a remote centre including procedures and protocols for communication.Electrical safety, environmental conditions and behaviour of alarm systems regarding electromagnetic compatibility are also considered with reference to the appropriate standards (e.g. Guide ISO/IEC 51).* ISO/TC21/SC3 is in charge of the production of standards for "Fire detection and alarm systems".
TC 79
Systems aspects of electrical energy supply
To prepare and coordinate, in co-operation with other TC/SCs, the development of international standards and other deliverables with emphasis on overall system aspects of electricity supply systems and acceptable balance between cost and quality for the users of electrical energy. Electricity supply system encompasses transmission and distribution networks, generators and loads with their network interfaces.
TC 8
Wind energy generation systems
TC 88 standardization in the field of wind energy generation systems including wind turbines, wind power plants onshore and offshore and interaction with the electrical system(s) to which energy is supplied. These standards address site suitability and resource assessment, design requirements, engineering integrity, modeling requirements, measurement techniques, test procedures, operation and maintenance. Their purpose is to provide a basis for design, quality assurance and technical aspects for certification. The standards address site-specific conditions, all systems and subsystems of wind turbines and wind power plants, such as mechanical, and electrical systems, support structures, control and protection as well as communication systems for monitoring, centralized and distributed control and evaluation, implementation of grid connection requirements for wind power plants, and environmental aspects of wind power development. The TC 88 standards will be developed based on and in agreement with appropriate IEC/ISO standards.
TC 88
Electronics assembly technology
To prepare international standards on design, manufacturing and testing of electronic assemblies including the requirements and tests for materials and components used to manufacture circuit boards and electronic assemblies, as well as the formats of electronic data and libraries for describing these products and processes.
TC 91
All-or-nothing electrical relays
To prepare international standards applicable to all-or-nothing electrical relays used in the various fields of Electrical Engineering covered by the IEC, normally produced in very large numbers as components of electromechanical or electronic equipment and eventually submitted to Quality Assurance requirements based on sampling techniques.
TC 94
Standardisation of measuring relays and protection equipment used in various fields of electrical engineering covered by IEC, taking into a ccount combinations of devices to form schemes for power system protection including the control, monitoring and process interface equipment used with those systems.Excluded are the following:All devices covered by standards prepared by other IEC Technical Committees, for example instrument transformers (TC 38).
TC 95
HTTP Protocol Binding
The present document will cover the protocol specific part of communication protocol used by oneM2M compliant systems as RESTful HTTP binding. The scope of the present document is (not limited to as shown below): • Binding oneM2M Protocol primitive types to HTTP method. • Binding oneM2M response status codes (successful/unsuccessful) to HTTP response codes. • Binding oneM2M RESTful resources to HTTP resources. The present document is depending on Core Protocol specification (oneM2M TS-0004) for data types.
Time Synchronized Mesh Protocol (TSMP): A communications protocol for self-organizing networks of wireless devices called motes. TSMP devices stay synchronized to each other and communicate in timeslots, similar to other TDM (time-division multiplexing) systems. (source: https://www.postscapes.com/internet-of-things-protocols/)
TSMP
Telehash - JSON+UDP+DHT=Freedom: A secure wire protocol powering a decentralized overlay network for apps and devices. (source: https://www.postscapes.com/internet-of-things-protocols/)
Telehash
The Industrial Internet of Things Volume G5: Connectivity Framework
The Industrial Internet of Things Volume G5: Connectivity Framework IIC:PUB:G5:V1.0:PB:20170228
Thread - Built on open standards and IPv6 technology with 6LoWPAN as its foundation. (source: https://www.postscapes.com/internet-of-things-protocols/)
Thread
The advent of the Industrial Internet of Things (IIoT) also raises challenges with respect to security and privacy of sensitive and personal data that is created by sensors and processed by services hosted in different administrative domains. The Industrial Data Space initiative addresses these challenges and proposes a secure edge gateway platform named "Trusted Connector". In this report, we introduce the main security building blocks of the Trusted Connector and point out how they help protecting business-critical data and preserving the user's privacy.
IDS Trusted Connector
UDP (User Datagram Protocol) - A simple OSI transport layer protocol for client/server network applications based on Internet Protocol (IP). UDP is the main alternative to TCP and one of the oldest network protocols in existence, introduced in 1980. UDP is often used in applications specially tuned for real-time performance.
UDP
United Nations Centre for Trade Facilitation and Electronic Business
UN/CEFACT is the United Nations Centre for Trade Facilitation and Electronic Business. It was established as an intergovernmental body of the United Nations Economic Commission for Europe (UNECE) in 1996 and evolved from UNECE’s long tradition of work in trade facilitation.
UPnP (Universal Plug and Play) - Now managed by the Open Connectivity Foundation is a set of networking protocols that permits networked devices to seamlessly discover each other's presence on the network and establish functional network services for data sharing, communications, and entertainment.(source: https://www.postscapes.com/internet-of-things-protocols/)
UPnP
private
IT-security for industrial automation
Informationssicherheit in der industriellen Automatisierung
This guideline describes how specific measures can be implemented in order to guarantee the IT security of automated machines and plant; aspects of the automation devices, automation systems, and automation applications used are considered. A uniform, feasible procedure for ensuring IT security throughout the entire life cycle of automation devices, systems, and applications is described, based on common terms and definitions agreed by the manufacturers of automation devices and systems and their users (e.g., machine manufacturers, integrators, operators). The life cycle covers the development, integration, operation, migration, and decommissioning phases.This guideline defines a simple procedure model for the development and description of IT Security. The model consists of eight steps.
VDI/VDE 2182
VDI
Association of German Engineers
Verein Deutscher Ingenieure
Verein Deutscher Ingenieure (VDI) (English: Association of German Engineers) is an organization with over 150,000 engineers and natural scientists. More than 12,000 honorary experts process the latest findings every year to promote the technology location. Established in 1856, the VDI is today the largest engineering association in Western Europe. The role of the VDI in Germany is comparable to that of the American Society of Civil Engineers (ASCE) in the United States or Engineers Australia (EA) in Australia barring the broader field of work of the VDI. The VDI is not a union. The association promotes the advancement of technology and represents the interests of engineers and of engineering businesses in Germany.
Mechanical Engineering Industry Association
Verband Deutscher Maschinen- und Anlagenbau
The Mechanical Engineering Industry Association (Verband Deutscher Maschinen- und Anlagenbau – VDMA) has its headquarters in Frankfurt am Main, Germany, and represents around 3,200 members, making it the largest industry association in Europe. The Association represents the interests of the predominantly medium-sized companies in the mechanical engineering industry towards policymakers and society, as well as towards business, the scientific community, public authorities and the media. With more than one million employees and a turnover of around EUR 218 billion (2015), mechanical and plant engineering is Germany’s largest employer in the industrial sector.In addition, VDMA sees itself as a platform that provides its member companies with various networks where they can discuss technological challenges, interdisciplinary issues and many other topics.
Fieldbus neutral reference architecture for Condition Monitoring in production automation
VDMA 24582
World Wide Web Consortium
The World Wide Web Consortium (W3C) is the main international standards organization for the World Wide Web (abbreviated WWW or W3). Founded and currently led by Tim Berners-Lee, the consortium is made up of member organizations which maintain full-time staff for the purpose of working together in the development of standards for the World Wide Web. As of 4 November 2015, the World Wide Web Consortium (W3C) has 408 members. The W3C also engages in education and outreach, develops software and serves as an open forum for discussion about the Web.
W3C
DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogs published on the Web. This document defines the schema and provides examples for its use. By using DCAT to describe datasets in data catalogs, publishers increase discoverability and enable applications easily to consume metadata from multiple catalogs. It further enables decentralized publishing of catalogs and facilitates federated dataset search across sites. Aggregated DCAT metadata can serve as a manifest file to facilitate digital preservation.
DCAT
OWL
The W3C Web Ontology Language (OWL) is a Semantic Web language designed to represent rich and complex knowledge about things, groups of things, and relations between things. OWL is a computational logic-based language such that knowledge expressed in OWL can be exploited by computer programs, e.g., to verify the consistency of that knowledge or to make implicit knowledge explicit. OWL documents, known as ontologies, can be published in the World Wide Web and may refer to or be referred from other OWL ontologies. OWL is part of the W3C’s Semantic Web technology stack, which includes RDF, RDFS, SPARQL, etc.
Web Ontology Language
RDF
RDF is a standard model for data interchange on the Web. RDF has features that facilitate data merging even if the underlying schemas differ, and it specifically supports the evolution of schemas over time without requiring all the data consumers to be changed.
Resource Description Framework
RIF
The Rule Interchange Format (RIF) is a W3C Recommendation. RIF is part of the infrastructure for the semantic web, along with (principally) SPARQL, RDF and OWL. Although originally envisioned by many as a rules layer for the semantic web, in reality the design of RIF is based on the observation that there are many rules languages in existence, and what is needed is to exchange rules between them.
Rule Interchange Format
SPARQL
The SPARQL Protocol and RDF Query Language (SPARQL) is a query language and protocol for RDF. This document specifies the SPARQL Protocol; it describes a means for conveying SPARQL queries and updates to a SPARQL processing service and returning the results via HTTP to the entity that requested them. This protocol was developed by the W3C SPARQL Working Group, part of the Semantic Web Activity as described in the activity statement .
A communications platform for IoT devices that enables device setup, phone-to-device-to-cloud communication, and user interaction from mobile devices and the web. (source: https://www.postscapes.com/internet-of-things-protocols/)
Weave
The WebSocket specification — developed as part of the HTML5 initiative — introduced the WebSocket JavaScript interface, which defines a full-duplex single socket connection over which messages can be sent between client and server. The WebSocket standard simplifies much of the complexity around bi-directional web communication and connection management. (source: https://www.postscapes.com/internet-of-things-protocols/)
WebSocket
Weightless is a proposed proprietary open wireless technology standard for exchanging data between a base station and thousands of machines around it (using wavelength radio transmissions in unoccupied TV transmission channels) with high levels of security. (source: https://www.postscapes.com/internet-of-things-protocols/)
Weightless
WiFi
WiMax is based on the standard IEEE 802.16 and is intended for wireless metropolitan area networks. The range is different for fixed stations, where it can go up to 50 km and mobile devices with 5 to 15 km. WiMAx operates at frequencies between 2.5 GHz to 5.8 GHz with a transferrate of 40 Mbps. (source: https://www.postscapes.com/internet-of-things-protocols/)
WiMax
The Wi-SUN Alliance seeks to advance seamless connectivity by promoting IEEE 802.15.4g standard based interoperability for global regional markets. (source: https://www.postscapes.com/internet-of-things-protocols/)
Wi-SUN Alliance
WirelessHART technology provides a robust wireless protocol for the full range of process measurement, control, and asset management applications. (source: https://www.postscapes.com/internet-of-things-protocols/)
WirelessHart
A symbolic representation of each device. Then there are a standard set of Wolfram Language functions like DeviceRead, DeviceExecute, DeviceReadBuffer and DeviceReadTimeSeries that perform operations related to the device. (source: https://www.postscapes.com/internet-of-things-protocols/)
Wolfram Language
Standard for public key infrastructure (PKI) to manage digital certificates and public-key encryption. A key part of the Transport Layer Security protocol used to secure web and email communication. (source: https://www.postscapes.com/internet-of-things-protocols/)
XMPP (Extensible Messaging and Presence Protocol): An open technology for real-time communication, which powers a wide range of applications including instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data. (source: https://www.postscapes.com/internet-of-things-protocols/)
XMPP
XMPP-IoT: In the same manor as XMPP silently has created people to people communication interoperable. We are aiming to make communication machine to people and machine to machine interoperable. (source: https://www.postscapes.com/internet-of-things-protocols/)
XMPP-IoT
X-Road Architecture Technical Specification Version: 1.0 18.09.2015 15 pages Doc. ID: ARC-G
German Electrical and Electronic Manufacturers' Association
Zentralverband Elektrotechnik- und Elektronikindustrie
The ZVEI is one of the most important manufacturers' associations in Germany. It represents the interests of a high-tech branch with a very widely varied and extremely dynamic product portfolio.
ZVEI
The ZigBee protocol uses the 802.15.4 standard and operates in the 2.4 GHz frequency range with 250 kbps. The maximum number of nodes in the network is 1024 with a range up to 200 meter. ZigBee can use 128 bit AES encryption. (source: https://www.postscapes.com/internet-of-things-protocols/)
ZigBee
Bundesverband Informationswirtschaft, Telekommunikation und neue Medien
German Association for IT, Telecommunications and New Media
Bitkom
Global identification, semantic description and automatic product classification
eCl@ss is the cross-industry product data standard for classification and clear description of products and services.
eClass
eCl@ss e. V.
Der eCl@ss e. V. ist eine Non-Profit-Organisation, die den gleichnamigen Klassifikationsstandard branchenübergreifend international definiert, weiterentwickelt und verbreitet. Der Verein wird getragen von ordentlichen und fördernden Mitgliedern aus Unternehmen, Verbänden und Institutionen.
ebXML
Electronic Business using eXtensible Markup Language, commonly known as e-business XML, or ebXML is a family of XML based standards whose mission is to provide an open, XML-based infrastructure that enables the global use of electronic business information in an interoperable, secure, and consistent manner by all trading partners.
iSHARE is a uniform set of agreements or a scheme for identification, authentication and authorization. All companies that join the iSHARE Scheme comply with the set of agreements. They all use the same methods to both provide and gain access to data. (source: iShare: 'It is not a platform…')
iShare
It is a guide intended for those who want to acquaint themselves more thoroughly with the X-tee (e.g. theose who are working for an organisation which will soon join the X-tee). It introduces the X-tee’s complex terminological system slowly and in a comprehensible way, so that the reader can painlessly achieve the preliminary familiarity with the X-tee necessary to engage with more explicitly technical and complex manuals. (source: https://www.ria.ee/en/state-information-system/x-tee/introduction-x-tee.html)
Introduction of X-tee
mDNS (multicast Domain Name System) - Resolves host names to IP addresses within small networks that do not include a local name server. (source: https://www.postscapes.com/internet-of-things-protocols/)
mDNS
The purpose and goal of oneM2M is to develop technical specifications which address the need for a common M2M Service Layer that can be readily embedded within various hardware and software, and relied upon to connect the myriad of devices in the field with M2M application servers worldwide. A critical objective of oneM2M is to attract and actively involve organizations from M2M-related business domains such as: telematics and intelligent transportation, healthcare, utilities, industrial automation, smart homes, etc.
oneM2M
Im Open Source Projekt „openAAS“ – die Abkürzung „AAS“ steht für den englischen Begriff „Asset Administration Shell“, zu Deutsch „Verwaltungsschale“ – arbeitet der ZVEI gemeinsam mit der RWTH Aachen und Unternehmen aus Maschinenbau und Elektroindustrie daran, Industrie 4.0 in die Praxis umzusetzen. Die Veranschaulichung und Erprobung einer Industrie-4.0-konformen Verwaltungsschale stehen im Mittelpunkt. Dies ist Voraussetzung für eine international erfolgreiche Technologieverifikation und Standardisierung.
openAAS is an open source project to establish a Platform Industry 4.0 conform Administration Shell with open software.
openAAS
The uIP is an open source TCP/IP stack capable of being used with tiny 8- and 16-bit microcontrollers. It was initially developed by Adam Dunkels of the 'Networked Embedded Systems' group at the Swedish Institute of Computer Science, licensed under a BSD style license, and further developed by a wide group of developers. (source: https://www.postscapes.com/internet-of-things-protocols/)
uIP
x-road Deplyoment View
x-road Protocols and Interfaces
x-road System Components
x-road Technology Matrix
x-Tee
Alliance of Industrial Internet Architecture Classification
The BDV Reference Model distinguishes between two different elements. On the one hand, it describes the elements that are at the core of the BDVA; on the other, it outlines the features that are developed in strong collaboration with related European activities. The BDV Reference Model is structured into horizontal and vertical concerns. Horizontal concerns cover specific aspects along the data processing Vertical concerns address cross-cutting issues, which may affect all the horizontal concerns. In addition, vertical concerns may also involve non-technical aspects.
BDVA Concern
A business manager is responsible for the running of the business and to make large profits.
Business Manager
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '1.5 AUDIENCE' 'Page 7'
This class frames all organizations with the main intend to create, specify and implement a data sharing concept with according interfaces, components, data descriptions, and retrieval algorithms.
Data Sharing Initiative
Following is a description of the Reference Architecture linked to the different chapters of FIWARE. A description of FIWARE Generic Enablers (GEs) being supported in each chapter is provided, including the high-level description of the APIs that each FIWARE Generic Enabler (GE) exposes to application developers or it uses to connect to another FIWARE GEs.
Fiware Chapter
IDS RAM Layer
IIRA Crosscutting Function
Publications referred: 'IIC:PUB:G1:V1.80:20170131' '6.6 CROSSCUTTING FUNCTIONS AND SYSTEM CHARACTERISTICS' 'Page 34'
Often these enabling functions, the so-called crosscutting functions, need to be made available across many of the system functional components. For Reference Architecture 6: Functional Viewpoint example, system functions need to be connected so they can interact with each other to complete functionality at the system level.
IIRA Functional Domain
Class of all System Characteristics as defined by the IIRA.
IIRA System Characteristic
IT Manager
An IT manager is responsible for the functioning of the IT services of an organisation.
IDS RAM Perspective
Connectivity Layer of the Internet Connectivity Framework
Connectivity Layer
IICF Connectivity Layer
International Classification For Standards
Serves as a structure for catalogues of international, regional and national standards and other normative documents, and as a basis for standing-order systems.
IoT-A Perspective
A IVI Layer describes one of three layers of smart manufactoring as proposed by the Industrial Value Chain Initiative (IVI).
IVI Layer
The section of the FIWARE specification about the NGSI API.
NGSI Context Information Management API
A plant manager is responsible for the functioning of a plant/facility.
Plant Manager
Facility Manager
RAMI Control Device
Standard
A document, established by consensus and approved by a recognized body, that provides, for common and repeated use, rules, guidelines or characteristics for activities or their results, aimed at the achievement of the optimum degree of order in a given context.
Standard Classification
Describes categorization areas that the different Standardizations Initiatives use to category Standards.
A category or section of a standard or reference framework. StandardClassification reflects views and viewpoints as defined by ISO 42010.
Reference Architecture
Describes existings Standardizations Initiatives, e.g, RAMI, NIST.
A framework is conventions, principles and practices for the description of architectures established within a specific domain of application and/or community of stakeholders.
A property explaining that TC and SC are managed by SMB (Standardization Management Board) needs to be added
Technical Committee
Specifies the representitive code name of the Technical Committee that covers a Standard for e.g, TC 1, SC 3C. Many thousand experts carry out standardization work in the IEC in TCs (technical committees) and SCs (subcommittees), in hundreds of working groups, project and maintenance teams. They represent the national electrotechnical needs of IEC Member countries and of many Affiliates at the global level in the IEC. These technical experts are sent by industry, governments, test and research laboratories, academia and even consumer groups to work on the global, neutral and independent platform of the IEC. That's where they develop globally relevant, voluntary, consensus based IEC International Standards.
Technical Reports contain collected data of a kind different from that normally published as an International Standard, for example data obtained from a survey carried out among national committees, data of work in other international organizations or data on "the state of the art" in relation to standards of national committees on a particular subject.Technical Reports are entirely informative in nature and shall not contain matter implying that they are normative
Technical Report
Specifies that a given Publication is a Technical Report
Technology
A Technology is an implementation of one or many standards in order to achieve a goal.
ISO 42010 definition of a Viewpoint
belongs To
A Standard Organization that belongs to the country
An Standard is isCategorizedBy a given Categorization Area which is connected to a specific Standarization Initiative
has Classification
has Developer
The organization that developed this Standard
Links the Standard Organization that developed the Publication with the specific type of publication, e.g., Standard, Technical Report
has Headquater In
Denotes the countries in which the Headquarter of the organization who publishes the Standart
Points to the URL of the official website from which published the document
has Official Resource
has Open Resource
points to the URLs of the resources(documents) openly available for the standard
has Publisher
The organization that published this Standard
Subproperty of http://voag.linkedmodel.org/voag#hasStakeholder (vocabulary not accessible).
This property links entities to the typical stakeholder which is interested in the topic.
has Tag
Points to the identification of the standards
has Wikipedia Article
Wikipedia Article about the Standard
is Implementation Of
Represent the relation that connects two standards when standard A is the implementation of standard B, e.g., B2MML isImplementationOf ISA-95.
x-road Section
Class of all parts of the xRoad specification.