This document addresses the construction of buildings and other structures which provide accommodation for data centres based upon the criteria and classification for “physical security” within EN 50600 1 in support of availability.
This document specifies requirements and recommendations for the following:
a)   location and site selection (taking in to account natural environment and adjacencies);
b)   protection from environmental risks;
c)   site configuration;
d)   building construction;
e)   building configuration;
f)   provision of access;
g)   intrusion protection;
h)   physical fire protection;
i)   protection against damage from water;
j)   quality construction measures.
Safety and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by other standards and regulations. However, information given in this document can be of assistance in meeting these standards and regulations.
Conformance of data centres to the present document is covered in Clause 4.

  • Standard
    38 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Draft
    33 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides requirements and recommendations for the type of risk assessment to be employed concerning seismic activity and earthquakes in relation to data centres. In addition, it describes design concepts that can be employed as mitigation actions within the construction, and other elements of design, of data centres.

  • Technical specification
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The present document defines power feeding solutions for 5G, converged wireless and wireline access equipment and
network, taking into consideration their enhanced requirements on service availability and reliability, the new
deployment scenarios, together with the environmental impact of the proposed solutions.
The minimum requirements of different solutions including power feeding structures, components, backup, safety
requirements, environmental conditions are also defined.
The present document is applicable to powering of both mobile and fixed access network elements, in particular on
equipment that have similar configurations and needs.
The future development of 5G networks will create a new scenario in which the density of radio cells will increase
considerably, together with the increase of wireline network equipment that are going to be installed in the vicinity to
the users, thereby creating the need to define new solutions for powering that will be environmentally friendly,
sustainable, dependable, smart and visible remotely.
The -48 V DC, up to 400 V DC local and remote power solutions defined respectively in ETSI EN 300 132-2 [2],
ETSI EN 302 099 [i.10] and ETSI EN 300 132-3-1 [3] or Recommendation ITU-T L.1200 [i.13] will be considered as
the standards in force for power facilities, together with IEEE 802.3TM [i.18] (PoE).

  • Standard
    43 pages
    English language
    sale 15% off
  • Standard
    43 pages
    English language
    sale 15% off
  • Standard
    43 pages
    English language
    sale 15% off
  • Standardization document
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document defines Ethernet local area, access and metropolitan area networks. Ethernet is specified at selected speeds of operation; and uses a common media access control (MAC) specification and management information base (MIB). The Carrier Sense Multiple Access with Collision Detection (CSMA/CD) MAC protocol specifies shared medium (half duplex) operation, as well as full duplex operation. Speed specific Media Independent Interfaces (MIIs) provide an architectural and optional implementation interface to selected Physical Layer entities (PHY). The Physical Layer encodes frames for transmission and decodes received frames with the modulation specified for the speed of operation, transmission medium and supported link length. Other specified capabilities include: control and management protocols, and the provision of power over selected twisted pair PHY types.

  • Standard
    5139 pages
    English language
    sale 15% off
  • Draft
    5139 pages
    English language
    sale 15% off
  • Standard
    129 pages
    English language
    sale 15% off
  • Draft
    141 pages
    English language
    sale 15% off

ISO/IEC 30144:2020 (E) specifies intelligent wireless sensor network (iWSN) from the perspectives of iWSN's system infrastructure and communications internal and external to the infrastructure, and technical requirements for iWSN to realize smart electrical power substations.

  • Standard
    36 pages
    English language
    sale 15% off

This document is a compilation of recommended Practices for improving the energy management (i.e. reduction of energy consumption and/or increases in energy efficiency) of data centres. It is historically aligned with the EU Code of Conduct for Data Centre Energy Efficiency (CoC) scheme operated by the Directorate-General Joint Research Centre (DG JRC) of the European Commission (EC).
It is recognized that the Practices included might not be universally applicable to all scales and business models of data centres or be undertaken by all parties involved in data centre operation, ownership or use.

  • Technical report
    50 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies provision of connectionless user data confidentiality, frame data integrity, and data origin authenticity by media access independent protocols and entities that operate transparently to MAC Clients. NOTE—The MAC Clients are as specified in IEEE Std 802®, IEEE Std 802.1Q?, and IEEE Std 802.1X.2 To this end, it a) Specifies the requirements to be satisfied by equipment claiming conformance to this standard. b) Specifies the requirements for MACsec in terms of provision of the MAC Service and the preservation of the semantics and parameters of service requests and indications. c) Describes the threats, both intentional and accidental, to correct provision of the service. d) Specifies security services that prevent, or restrict, the effect of attacks that exploit these threats. e) Examines the potential impact of both the threats and the use of MACsec on the Quality of Service (QoS), specifying constraints on the design and operation of MAC Security entities and protocols. f) Models support of the secure MAC Service in terms of the operation of media access control method independent MAC Security Entities (SecYs) within the MAC Sublayer. g) Specifies the format of the MACsec Protocol Data Unit (MPDUs) used to provide secure service. h) Identifies the functions to be performed by each SecY, and provides an architectural model of its internal operation in terms of Processes and Entities that provide those functions. i) Specifies each SecY's use of an associated and collocated Port Access Entity (PAE, IEEE Std 802.1X) to discover and authenticate MACsec protocol peers and its use of that PAE's Key Agreement Entity (KaY) to agree and update cryptographic keys. j) Specifies performance requirements and recommends default values and applicable ranges for the operational parameters of a SecY. k) Specifies how SecYs are incorporated within the architecture of end stations, bridges, and two-port Ethernet Data Encryption devices (EDEs). l) Establishes the requirements for management of MAC Security, identifying the managed objects and defining the management operations for SecYs. m) Specifies the Management Information Base (MIB) module for managing the operation of MAC Security in TCP/IP networks. n) Specifies requirements, criteria, and choices of Cipher Suites for use with this standard.

  • Standard
    221 pages
    English language
    sale 15% off
  • Draft
    237 pages
    English language
    sale 15% off
  • Standard
    77 pages
    English language
    sale 15% off
  • Draft
    95 pages
    English language
    sale 15% off

This document specifies Bridges that interconnect individual LANs, each supporting the IEEE 802 MAC Service using a different or identical media access control method, to provide Bridged Networks and VLANs.

  • Standard
    1931 pages
    English language
    sale 15% off
  • Draft
    1931 pages
    English language
    sale 15% off
  • Standard
    52 pages
    English language
    sale 15% off
  • Draft
    67 pages
    English language
    sale 15% off

This EN specifies the so-called Energy Reuse Factor (ERF) as a KPI to quantify the reuse of the energy consumed in the data centre. The ERF does reflect the efficiency of the reuse process, however, the reuse process is not part of the data centre.

  • Standard
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This European Standard specifies requirements for the following aspects of information technology cabling:
a)   installation specification, quality assurance documentation and procedures;
b)   documentation and administration;
c)   operation and maintenance.
This European Standard is applicable to all types of information technology cabling including generic cabling systems designed in accordance with the EN 50173 series.

  • Amendment
    4 pages
    English language
    sale 10% off
    e-Library read for
    1 day

ISO/IEC 30143:2020 provides the guidelines for designing and developing new applications in the underwater environment such as fish farming, environment monitoring, harbour security, etc. This document also: • provides the components required for developing the application; • provides instructions for modelling the application with examples; • helps the user to understand the communication between the elements in the application for modelling the communication between elements; • guides the user with the design process of underwater applications.

  • Standard
    38 pages
    English language
    sale 15% off

ISO/IEC 30142:2020 provides the overview and requirements of a network management system in underwater acoustic sensor network (UWASN) environment. It specifies the following: – functions which support underwater network management system; – entities required for underwater network management system; – data about the communication between elements in underwater network management system; – guidelines to model the underwater network management system; – general and functional requirements of underwater network management system

  • Standard
    39 pages
    English language
    sale 15% off

ISO/IEC 30143:2020 provides the guidelines for designing and developing new applications in the underwater environment such as fish farming, environment monitoring, harbour security, etc. This document also:
• provides the components required for developing the application;
• provides instructions for modelling the application with examples;
• helps the user to understand the communication between the elements in the application for modelling the communication between elements;
• guides the user with the design process of underwater applications.

  • Standard
    38 pages
    English language
    sale 15% off

ISO/IEC 30142:2020 provides the overview and requirements of a network management system in underwater acoustic sensor network (UWASN) environment. It specifies the following:
– functions which support underwater network management system;
– entities required for underwater network management system;
– data about the communication between elements in underwater network management system;
– guidelines to model the underwater network management system;
– general and functional requirements of underwater network management system

  • Standard
    39 pages
    English language
    sale 15% off

This EN specifies the so-called Cooling Efficiency Ratio (CER), which is a key performance indicator for data centres, that indicates the effectiveness of a cooling system in a data centre.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

IEC 62056-8-8:2020 describes how the DLMS/COSEM Application layer and the COSEM object model, as specified in IEC 62056‑5‑3:2017, IEC 62056‑6‑1:2017 and IEC 62056‑6‑2:2017, can be used over the lower layers specified in the IEC 14908 series, forming a DLMS/COSEM ISO/IEC 14908 communication profile. This document is part of the IEC 62056 series. Its structure follows IEC 62056-1-0 and IEC TS 62056-1-1.

  • Standard
    208 pages
    English and French language
    sale 15% off

IEC 21823-2:2020 (E) specifies a framework and requirements for transport interoperability, in order to enable the construction of IoT systems with information exchange, peer-to-peer connectivity and seamless communication both between different IoT systems and also among entities within an IoT system. This document specifies:
• transport interoperability interfaces and requirements between IoT systems;
• transport interoperability interfaces and requirements within an IoT system

  • Standard
    18 pages
    English language
    sale 15% off

This document specifies the Cooling Efficiency Ratio (CER) as a Key Performance Indicator (KPI) to quantify the efficient use of energy to control the temperature of the spaces within the data centre. This document: a) defines the Cooling Efficiency Ratio (CER) of a data centre; b) describes the relationship of this KPI to a data centre’s infrastructure, information technology equipment and information technology operations; c) defines the measurement, the calculation and the reporting of the parameter; d) provides information on the correct interpretation of the CER. Annex A describes the correlation of CER and other KPIs. Annex B provides examples of the application of CER. Annex C introduces the parameters that affect CER. Annex D describes requirements and recommendations for derivatives of KPIs associated with CER.

  • Standard
    18 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This Technical Report describes the following:
a)   the functional elements and structure of the cabling, external to homes, supporting community antenna television (CATV) and master antenna television/satellite master antenna television (MATV/SMATV) networks in accordance with EN 60728-1;
b)   the location and accommodation of the home network interface (HNI) in accordance with EN 60728-1;
c)   requirements for additional cabling performance requirements (i.e. insertion loss slope between 47 MHz and 862 MHz) and necessary amendments of the reference implementations of generic cabling within the home in accordance with EN 50173-4 in order to support the CATV, MATV/SMATV networks in accordance with EN 60728-1

  • Technical report
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document addresses the mitigation and protection of telecommunications cabling from electromagnetic interference by describing:
a)   coupling mechanisms and possible countermeasures;
b)   assessment of the electromagnetic environment;
c)   filtering, isolation and surge protections measures.
Safety (electrical safety and protection, optical power, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by standards and regulations. However, information given in this document can be of assistance in meeting these standards and regulations.

  • Technical report
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document addresses the mitigation and protection of telecommunications cabling from electromagnetic interference by describing: a) coupling mechanisms and possible countermeasures; b) assessment of the electromagnetic environment; c) filtering, isolation and surge protections measures. Safety (electrical safety and protection, optical power, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by standards and regulations. However, information given in this document can be of assistance in meeting these standards and regulations.

  • Technical report
    21 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document describes the following: a) the functional elements and structure of the cabling, external to homes, supporting community antenna television (CATV) and master antenna television/satellite master antenna television (MATV/SMATV) networks in accordance with EN 60728 1; b) the location and accommodation of the home network interface (HNI) in accordance with EN 60728 1; c) requirements for additional cabling performance requirements (i.e. insertion loss slope between 47 MHz and 862 MHz) and necessary amendments of the reference implementations of generic cabling within the home in accordance with EN 50173 4 in order to support the CATV, MATV/SMATV networks in accordance with EN 60728 1. Safety (electrical safety and protection, optical power, fire, etc.) and electromagnetic compatibility (EMC) requirements are outside the scope of this document and are covered by standards and regulations. However, information given in this document could be of assistance in meeting these standards and regulations.

  • Technical report
    34 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This standard specifies unique per-device identifiers (DevID) and the management and cryptographic binding of a device to its identifiers, the relationship between an initially installed identity and subsequent locally significant identities, and interfaces and methods for use of DevIDs with existing and new provisioning and authentication protocols.

  • Standard
    59 pages
    English language
    sale 15% off

This part of the IEC 62443 series provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443‑1‑1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset.
As defined in IEC 62443‑1‑1 there are a total of seven FRs:
a) Identification and authentication control (IAC),
b) Use control (UC),
c) System integrity (SI),
d) Data confidentiality (DC),
e) Restricted data flow (RDF),
f) Timely response to events (TRE), and
g) Resource availability (RA).
These seven requirements are the foundation for control system capability SLs, SL-C (control system). Defining security capability at the control system level is the goal and objective of this standard as opposed to target SLs, SL-T, or achieved SLs, SL-A, which are out of scope.
See IEC 62443‑2‑1 for an equivalent set of non-technical, program-related, capability SRs necessary for fully achieving a control system target SL.

  • Corrigendum
    3 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Corrigendum
    3 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document describes ? the structure of wireless gas meter networks, and ? the application protocol of wireless gas meter networks.

  • Technical report
    28 pages
    English language
    sale 15% off

ISO/IEC TR 30148:2019 (E) describes:
– the structure of wireless gas meter networks, and
– the application protocol of wireless gas meter networks

  • Technical report
    28 pages
    English language
    sale 15% off

This document is a compilation of recommended practices for improving the environmental sustainability of both new and existing data centres. Environmental impacts consider not just those associated with electricity but also water usage and other pollutants.
It is recognized that the practices included are not universally applicable to all scales and business models of data centres or be undertaken by all parties involved in data centre operation, ownership or use.

  • Technical report
    23 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of IEC 61158 provides common elements for basic time-critical messaging communications between devices in an automation environment. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This standard defines in an abstract way the externally visible service provided by the Type 2 fieldbus data-link layer in terms of:
a) the primitive actions and events of the service;
b) the parameters associated with each primitive action and event, and the form which they take; and
c) the interrelationship between these actions and events, and their valid sequences.
The purpose of this standard is to define the services provided to:
• the Type 2 fieldbus application layer at the boundary between the application and data-link layers of the fieldbus reference model;
• systems management at the boundary between the data-link layer and systems management of the fieldbus reference model.
Type 2 DL-service provides both a connected and a connectionless subset of those services specified in ISO/IEC 8886.
1.2 Specifications
The principal objective of this standard is to specify the characteristics of conceptual data-link layer services suitable for time-critical communications and thus supplement the OSI Basic Reference Model in guiding the development of data-link protocols for time-critical communications. A secondary objective is to provide migration paths from previously-existing industrial communications protocols.
This specification may be used as the basis for formal DL-Programming-Interfaces. Nevertheless, it is not a formal programming interface, and any such interface will need to address implementation issues not covered by this specification, including:
a) the sizes and octet ordering of various multi-octet service parameters;
b) the correlation of paired request and confirm, or indication and response, primitives.
1.3 Conformance
This standard does not specify individual implementations or products, nor does it constrain the implementations of data-link entities within industrial automation systems.

  • Amendment
    6 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document specifies basic requirements for the installation of media for communication networks within and between the automation islands, of industrial sites. This document covers balanced and optical fibre cabling. It also covers the cabling infrastructure for wireless media, but not the wireless media itself. Additional media are covered in IEC 61784-5 (all parts). This document is a companion standard to the communication networks of the industrial automation islands and especially to the communication networks specified in IEC 61158 (all parts) and IEC 61784 (all parts). In addition, this document covers the connection between the generic telecommunications cabling specified in ISO/IEC 11801-3 and the specific communication cabling of an automation island, where an automation outlet (AO) replaces the telecommunication outlet (TO) of ISO/IEC 11801-3. NOTE If the interface used at the AO does not conform to that specified for the TO of ISO/IEC 11801-3, the cabling no longer conforms to ISO/IEC 11801-3 although certain features, including performance, of generic cabling may be retained. This document provides guidelines that cope with the critical aspects of the industrial automation area (safety, security and environmental aspects such as mechanical, liquid, particulate, climatic, chemicals and electromagnetic interference). This document does not recognise implementations of power distribution with or through Ethernet balanced cabling systems. This document deals with the roles of planner, installer, verifier, and acceptance test personnel, administration and maintenance personnel and specifies the relevant responsibilities and/or gives guidance.

  • Amendment
    4 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Amendment
    4 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 19 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible service provided by the different Types of fieldbus Application Layer in terms of: a) an abstract model for defining application resources (objects) capable of being manipulated by users via the use of the FAL service; b) the primitive actions and events of the service; c) the parameters associated with each primitive action and event, and the form which they take; and d) the interrelationship between these actions and events, and their valid sequences. The purpose of this document is to define the services provided to: a) the FAL user at the boundary between the user and the Application Layer of the Fieldbus Reference Model, and b) Systems Management at the boundary between the Application Layer and Systems Management of the Fieldbus Reference Model. This document specifies the structure and services of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

  • Standard
    26 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 4 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard specifies interactions between remote applications and defines the externally visible behavior provided by the Type 4 fieldbus application layer in terms of a) the formal abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining encoding rules that are applied to the application layer protocol data units; c) the application context state machine defining the application service behavior visible between communicating application entities; d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to 1) define the wire-representation of the service primitives defined in IEC 61158-5-4, and 2) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 4 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI application layer structure (ISO/IEC 9545).

  • Standard
    43 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The data-link layer provides basic time-critical messaging communications between devices in an automation environment. This protocol provides communication opportunities to all participating data- link entities a) in a synchronously-starting cyclic manner, and b) in a cyclic or acyclic asynchronous manner, as requested each cycle by each of those data-link entities. Thus this protocol can be characterized as one which provides cyclic and acyclic access asynchronously but with a synchronous restart of each cycle.

  • Standard
    145 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides basic time-critical data communications between devices in an automated environment. Type 21 provides priority-based cyclic and acyclic data communication using an internal collision-free, full-duplex dual-port Ethernet switch technology. For wide application in various automation applications, Type 21 does not restrict the cyclic/acyclic scheduling policy in the DLL.

  • Standard
    111 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides basic time-critical messaging communications between devices in an automation environment. This protocol provides communication opportunities to all participating data-link entities, sequentially and in a cyclic synchronous manner. Foreground scheduled access is available for time-critical activities together with background unscheduled access for less critical activities. Deterministic and synchronized transfers can be provided at cyclic intervals up to 1 ms and device separations of 25 km. This performance is adjustable dynamically and on-line by reconfiguring the parameters of the local link whilst normal operation continues. By similar means, DL connections and new devices may be added or removed during normal operation. This protocol provides means to maintain clock synchronization across an extended link with a precision better than 10 μs. This protocol optimizes each access opportunity by concatenating multiple DLSDUs and associated DLPCI into a single DLPDU, thereby improving data transfer efficiency for datalink entities that actively source multiple streams of data. The maximum system size is an unlimited number of links of 99 nodes, each with 255 DLSAPaddresses. Each link has a maximum of 224 related peer and publisher DLCEPs.

  • Standard
    385 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of the IEC 62443 series provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443‑1‑1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset.
As defined in IEC 62443‑1‑1 there are a total of seven FRs:
a) Identification and authentication control (IAC),
b) Use control (UC),
c) System integrity (SI),
d) Data confidentiality (DC),
e) Restricted data flow (RDF),
f) Timely response to events (TRE), and
g) Resource availability (RA).
These seven requirements are the foundation for control system capability SLs, SL-C (control system). Defining security capability at the control system level is the goal and objective of this standard as opposed to target SLs, SL-T, or achieved SLs, SL-A, which are out of scope.
See IEC 62443‑2‑1 for an equivalent set of non-technical, program-related, capability SRs necessary for fully achieving a control system target SL.

  • Standard
    83 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 3 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible behavior provided by the Type 3 fieldbus application layer in terms of a) the abstract syntax defining the application layer protocol data units conveyed between communicating application entities, b) the transfer syntax defining the application layer protocol data units conveyed between communicating application entities, c) the application context state machine defining the application service behavior visible between communicating application entities; and d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to a) define the wire-representation of the service primitives specified in IEC 61158-5-3, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 3 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

  • Standard
    381 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 26 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible behavior provided by the Type 26 of the fieldbus Application Layer in terms of: a) the abstract syntax defining the application layer protocol data units conveyed between communicating application entities; b) the transfer syntax defining the application layer protocol data units conveyed between communicating application entities; c) the application context state machine defining the application service behavior visible between communicating application entities; and d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to: a) define the wire-representation of the service primitives defined in IEC 61158-5-26, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 26 fieldbus Application Layer, in conformance with the OSI Basic Reference Model (see ISO/IEC 7498-1) and the OSI Application Layer Structure (see ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

  • Standard
    187 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-timecritical messaging communications between application programs in an automation environment and material specific to Type 25 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This document defines in an abstract way the externally visible behavior provided by the different Types of the fieldbus Application Layer in terms of: a) the abstract syntax defining the application layer protocol data units conveyed between communicating application entities, b) the transfer syntax defining the application layer protocol data units conveyed between communicating application entities, c) the application context state machine defining the application service behavior visible between communicating application entities; and d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to: a) define the wire-representation of the service primitives defined in IEC 61158-5-25, and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the IEC fieldbus Application Layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545). FAL services and protocols are provided by FAL application-entities (AE) contained within the application processes. The FAL AE is composed of a set of object-oriented Application Service Elements (ASEs) and a Layer Management Entity (LME) that manages the AE. The ASEs provide communication services that operate on a set of related application process object (APO) classes. One of the FAL ASEs is a management ASE that provides a common set of services for the management of the instances of FAL classes. Although these services specify, from the perspective of applications, how request and responses are issued and delivered, they do not include a specification of what the requesting and responding applications are to do with them. That is, the behavioral aspects of the applications are not specified; only a definition of what requests and responses they can send/receive is specified. This permits greater flexibility to the FAL users in standardizing such object behavior. In addition to these services, some supporting services are also defined in this document to provide access to the FAL to control certain aspects of its operation.

  • Standard
    127 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document provides common elements for basic time-critical and non-time-critical messaging communications between application programs in an automation environment and material specific to Type 10 fieldbus. The term “time-critical” is used to represent the presence of a time-window, within which one or more specified actions are required to be completed with some defined level of certainty. Failure to complete specified actions within the time window risks failure of the applications requesting the actions, with attendant risk to equipment, plant and possibly human life. This International Standard defines in an abstract way the externally visible behavior provided by the Type 10 fieldbus application layer in terms of: a) the abstract syntax defining the application layer protocol data units conveyed between communicating application entities, b) the transfer syntax defining the application layer protocol data units conveyed between communicating application entities, c) the application context state machine defining the application service behavior visible between communicating application entities, and d) the application relationship state machines defining the communication behavior visible between communicating application entities. The purpose of this document is to define the protocol provided to: a) define the wire-representation of the service primitives defined in IEC 61158-5-10 and b) define the externally visible behavior associated with their transfer. This document specifies the protocol of the Type 10 fieldbus application layer, in conformance with the OSI Basic Reference Model (ISO/IEC 7498-1) and the OSI Application Layer Structure (ISO/IEC 9545). 1.2 Specifications The principal objective of this document is to specify the syntax and behavior of the application layer protocol that conveys the application layer services defined in IEC 61158-5-10. A secondary objective is to provide migration paths from previously-existing industrial communications protocols. It is this latter objective which gives rise to the diversity of protocols standardized in IEC 61158-6. 1.3 Conformance This document does not specify individual implementations or products, nor does it constrain the implementations of application layer entities within industrial automation systems. Conformance is achieved through implementation of this application layer protocol specification.

  • Standard
    899 pages
    English language
    sale 10% off
    e-Library read for
    1 day

The data-link layer provides basic time-critical messaging communications between devices in an automation environment. This protocol provides communication opportunities to all participating data- link entities: a) in a synchronously-starting cyclic manner, according to a pre-established schedule, or b) in an acyclic manner, as requested by each of those data-link entities. Thus this protocol can be characterized as one which provides cyclic and acyclic access asynchronously but with a synchronous restart of each cycle.

  • Standard
    125 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This document is one of a series produced to facilitate the interconnection of automation system components. It is related to other standards in the set as defined by the three-layer fieldbus reference model described in IEC 61158-1. This International Standard contains material specific to the Type 21 communication protocol.

  • Standard
    58 pages
    English language
    sale 10% off
    e-Library read for
    1 day

This part of the IEC 62443 series provides detailed technical control system requirements (SRs) associated with the seven foundational requirements (FRs) described in IEC 62443‑1‑1 including defining the requirements for control system capability security levels, SL-C(control system). These requirements would be used by various members of the industrial automation and control system (IACS) community along with the defined zones and conduits for the system under consideration (SuC) while developing the appropriate control system target SL, SL-T(control system), for a specific asset.
As defined in IEC 62443‑1‑1 there are a total of seven FRs:
a) Identification and authentication control (IAC),
b) Use control (UC),
c) System integrity (SI),
d) Data confidentiality (DC),
e) Restricted data flow (RDF),
f) Timely response to events (TRE), and
g) Resource availability (RA).
These seven requirements are the foundation for control system capability SLs, SL-C (control system). Defining security capability at the control system level is the goal and objective of this standard as opposed to target SLs, SL-T, or achieved SLs, SL-A, which are out of scope.
See IEC 62443‑2‑1 for an equivalent set of non-technical, program-related, capability SRs necessary for fully achieving a control system target SL.

  • Corrigendum
    3 pages
    English language
    sale 10% off
    e-Library read for
    1 day
  • Corrigendum
    3 pages
    English language
    sale 10% off
    e-Library read for
    1 day