35.100 - Open systems interconnection (OSI)
ICS 35.100 Details
Open systems interconnection (OSI)
Verbund offener Systeme (OSI)
Interconnexion des systemes ouverts (modele OSI)
Medsebojno povezovanje odprtih sistemov (OSI)
General Information
Frequently Asked Questions
ICS 35.100 is a classification code in the International Classification for Standards (ICS) system. It covers "Open systems interconnection (OSI)". The ICS is a hierarchical classification system used to organize international, regional, and national standards, facilitating the search and identification of standards across different fields.
There are 3275 standards classified under ICS 35.100 (Open systems interconnection (OSI)). These standards are published by international and regional standardization bodies including ISO, IEC, CEN, CENELEC, and ETSI.
The International Classification for Standards (ICS) is a hierarchical classification system maintained by ISO to organize standards and related documents. It uses a three-level structure with field (2 digits), group (3 digits), and sub-group (2 digits) codes. The ICS helps users find standards by subject area and enables statistical analysis of standards development activities.
e-Library Subscription
Create subscription and get permanent access to documents within 35.100 - Open systems interconnection (OSI)
Currently subscription includes documents marked with .We are working on making all documents available within the subscription.
IEC 62541-9:2026 specifies the representation of Alarms and Conditions in the OPC Unified Architecture. Included is the Information Model representation of Alarms and Conditions in the OPC UA address space. Other aspects of alarm systems like alarm philosophy, life cycle, alarm response times, alarm types and many other details are captured in standards such as IEC 62682 and ISA 18.2. The Alarms and Conditions Information Model in this document, is designed in accordance with IEC 62682 and ISA 18.2. Annex C specifies a recommended mapping between OPC Classic Alarm & Events (A&E) servers to the model described in this document. Annex A describes recommended localized names for Alarm states. Annex B describes examples (e.g. Event sequences, Alarm areas in AddressSpace). This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of "Comment" parameter to Alarm shelving methods;
b) addition of method that allows a client to get the members of a group, since it is possible that the AddressSpace does not expose instances of alarms;
c) addition of deadband properties for all limits in the limit AlarmType (from which all other types described in this issue are derived);
d) addition of text explaining the disabling of alarms is no longer supported in ISA 18.2 and that it is maintained in this document for backward compatibility, but that it is recommended that Alarm not be disabled;
e) addition of optional severities for limit alarms;
f) addition of new AlarmState variable type that can be used to collect alarm information for displays on graphics;
g) addition of SupportsFilterRetain property to improve Client filtering;
h) removal of ConditionSubClassId and ConditionSubClassNames from the conditiontype definition since they are now defined in BaseEventType.
- Standard337 pagesEnglish languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
- Standard330 pagesEnglish and French languagesale 15% off
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard156 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541-6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541-6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP.
Not all OPC UA Servers implement all of the defined Services. IEC 62541-7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile.
A BNF (Backus-Naur form) for browse path names is described in Annex A.
- Standard249 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture specification series and defines the information model associated with Aggregates.
Programmatically produced aggregate examples are listed in Annex A.
- Standard68 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 is part of the overall OPC Unified Architecture (OPC UA) standard series and defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour.
The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541-3. The services to detect and access data are specified in IEC 62541-4.
Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model.
- Standard96 pagesEnglish languagee-Library read for1 day
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard165 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs.
The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage
Programs are specified in IEC 62541-4.
An example for a DomainDownload Program is defined in Annex A.
- Standard46 pagesEnglish languagee-Library read for1 day
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition:
a) Annex B has been removed and used to create IEC 62451-16;
b) Annex C has been removed and used to create IEC 62451-20;
c) currency information model has been added;
d) information model for Interfaces and AddIns has been added;
e) information model for Method Metadata has been added;
f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities;
g) information model for ordered list of objects has been added;
h) PortableQualifiedName and PortableNodeId DataTypes have been added;
i) UriString DataType has been added;
j) SemanticVersionString DataType has been added;
k) AssociatedWith Reference Type has been added;
l) ConfigurationVersion Property has been added to NamespaceMetadataType;
m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added;
n) ModelVersion has been added to NamespaceMetadataType;
o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case;
p) BitFieldType and BitFieldDefinitionType have been added.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard193 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of the concept and modelling elements for Interfaces and AddIns;
b) addition of Currency;
c) addition of Method Meta Data to define additional attributes for Method Arguments;
d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType;
e) addition of a Non-Volatile Storage bit to AccessLevelExType;
f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType;
g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it;
h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node;
i) NamingRules have become deprecated;
j) addition of AssociatedWith ReferenceType.
- Standard143 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses.
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
This document consists of
• a general introduction of the PubSub concepts,
• a definition of the PubSub configuration parameters,
• mapping of PubSub concepts and configuration parameters to messages and transport protocols,
• and a PubSub configuration model.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Addition of a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) Addion of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• rules have been added when ValuePrecision has negative values.
- Standard320 pagesEnglish languagee-Library read for1 day
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 62541‑2, the abstract service definitions specified in IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols that can be used to implement the OPC UA specification.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of support for ECC to UA Secure Conversation;
b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists;
c) enhancement of JSON mapping of Unions;
d) addition of Decimal data type encoding.
e) description of ECC keyUsage rules;
f) addition of Media assigned by IANA to UANodeSet definition;
g) addition of requirements for user and issuer Certificates;
h) addition of rules which specify what happens when DateTime precision is lost;
i) addition of rules to allow for the truncation of strings containing embedded nulls.
J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping.
k) requirement that TAI times be converted to UTC;
l) new possibility to omit Symbol if unknown in JSON encoding;
m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard144 pagesEnglish languagee-Library read for1 day
This part of IEC 62541 belongs to the OPC Unified Architecture standards series and defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour.
The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541-3. The predefined Information Model is defined in IEC 62541-5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541-4.
This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541-13.
Conventions for Historical Access Clients are informatively provided in Annex A.
- Standard77 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses. PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems. This document consists of • a general introduction of the PubSub concepts, • a definition of the PubSub configuration parameters, • mapping of PubSub concepts and configuration parameters to messages and transport protocols, • and a PubSub configuration model. This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Addition of a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them. b) Addion of rules for ValuePrecision Property: • can also be used for other subtypes like Duration and Decimal. • rules have been added when ValuePrecision has negative values.
- Standard320 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of the concept and modelling elements for Interfaces and AddIns; b) addition of Currency; c) addition of Method Meta Data to define additional attributes for Method Arguments; d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType; e) addition of a Non-Volatile Storage bit to AccessLevelExType; f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType; g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it; h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node; i) NamingRules have become deprecated; j) addition of AssociatedWith ReferenceType.
- Standard143 pagesEnglish languagee-Library read for1 day
IEC 62541-11: 2025 defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour. The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541‑3. The predefined Information Model is defined in IEC 62541‑5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541‑4. This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541‑13. Conventions for Historical Access Clients are informatively provided in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) a functionality has been added to support retrieving of modified events; b) an Event has been added to indicate when a backfill occurred; c) a new ReferenceType that can be used to indicate an external node has been defined; d) the text has been improved to better explain the concept of annotation and remove conflicting explanations; e) a default historian configuration (and where to find it) has been defined; f) HistoricalEventConfigurationType, which provides general configuration information about the historical Event storage, has been added; g) the text has been updated and optional fields have been added to HA configuration object to allow configuration to be defined for periodic data collection, not just for exception-based collection; h) an ObjectType that can be used for external event collection has been provided as well as an example how historians can be configured.
- Standard77 pagesEnglish languagee-Library read for1 day
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 62541‑2, the abstract service definitions specified in IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols that can be used to implement the OPC UA specification. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of support for ECC to UA Secure Conversation; b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists; c) enhancement of JSON mapping of Unions; d) addition of Decimal data type encoding. e) description of ECC keyUsage rules; f) addition of Media assigned by IANA to UANodeSet definition; g) addition of requirements for user and issuer Certificates; h) addition of rules which specify what happens when DateTime precision is lost; i) addition of rules to allow for the truncation of strings containing embedded nulls. J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping. k) requirement that TAI times be converted to UTC; l) new possibility to omit Symbol if unknown in JSON encoding; m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard144 pagesEnglish languagee-Library read for1 day
IEC 62541-8:2025 defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour. The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541‑3. The services to detect and access data are specified in IEC 62541‑4. Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of a "Quantity Model" which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them. b) addition of rules for ValuePrecision Property: - can also be used for other subtypes like Duration and Decimal. - rules have been added when ValuePrecision has negative values.
- Standard96 pagesEnglish languagee-Library read for1 day
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition: a) Annex B has been removed and used to create IEC 62451-16; b) Annex C has been removed and used to create IEC 62451-20; c) currency information model has been added; d) information model for Interfaces and AddIns has been added; e) information model for Method Metadata has been added; f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities; g) information model for ordered list of objects has been added; h) PortableQualifiedName and PortableNodeId DataTypes have been added; i) UriString DataType has been added; j) SemanticVersionString DataType has been added; k) AssociatedWith Reference Type has been added; l) ConfigurationVersion Property has been added to NamespaceMetadataType; m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added; n) ModelVersion has been added to NamespaceMetadataType; o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case; p) BitFieldType and BitFieldDefinitionType have been added. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard193 pagesEnglish languagee-Library read for1 day
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows: • The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols. • The Device Communication Model adds Network and Connection information elements so that communication topologies can be created. • The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks. This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are: • Locking model – a generic AddIn to control concurrent access, • Software update model – an AddIn to manage software in a Device. This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType; b the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added. c) a new model for Software Update (Firmware Update) has been added; d) a new entry point for documents where each document is represented by a FileType instance has been specified; e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard156 pagesEnglish languagee-Library read for1 day
IEC 62541-4:2025 is available as IEC 62541-4:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) addition of new definitions to Method Call Service to allow optional Method arguments; b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios; c) enhancement of the general description of how determining if a Certificate is trusted; d) addition of support for ECC; e) addition of revisedAggregateConfiguration to AggregateFilterResult structure; f) addition of INVALID to the BrowseDirection enumeration data type; g) addition of INVALID to the TimestampsToReturn enumeration data type; h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional; i) addition of client checks has been added to be symmetric to the Server Certificate check has been added; j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME; k) addition of a definition for expiration behaviour of IssuedIdentityTokens; l) addition of status code Good_PasswordChangeRequired to ActivateSession; m) restriction of AdditionalInfo to servers in debug mode; n) addition of new status code Bad_ServerTooBusy; o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard249 pagesEnglish languagee-Library read for1 day
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture. OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document. Most OPC UA applications will conform to several, but not all of the Profiles. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard165 pagesEnglish languagee-Library read for1 day
IEC 62541-13:2025 is available as IEC 62541-13:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision. This edition includes the following technical changes with respect to the previous edition: a) Multiple fixes for the computation of aggregates • The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates. • Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source. • Missing tables have been added for DurationInStateZero and DurationInStateNonZero. • The value of zero has been removed for results with a StatusCode of bad. • Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates. • Rounding Error in TimeAverage and TimeAverage2 have been corrected. • The status codes have been corrected for the last two intervals and the value has been corrected in the last interval. • The wording has been changed to be more consistent with the certification testing tool. • UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified. • Values affected by percent good and percent bad have been updated. • PercentGood/PercentBad are now accounted for in the calculation. • TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation. • Partial bit is now correctly calculated. • Unclear sentence was removed. • Examples have been moved to a CSV. • The value and status code for Historian 3 have been updated. • TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes. • TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes. • Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes • Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes • Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes • MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes • Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes • MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag. • Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes. • Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard68 pagesEnglish languagee-Library read for1 day
IEC 62541-10:2025 is available as IEC 62541-10:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62541-10:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541-4. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: - StateMachine table format has been aligned.
- Standard46 pagesEnglish languagee-Library read for1 day
IEC 62541-14:2026 defines the PubSub communication model. It defines an OPC UA publish subscribe pattern which complements the client server pattern defined by the Services in IEC 62541-4. See IEC 62541-1 for an overview of the two models and their distinct uses.
PubSub allows the distribution of data and events from an OPC UA information source to interested observers inside a device network as well as in IT and analytics cloud systems.
This document consists of
• a general introduction of the PubSub concepts,
• a definition of the PubSub configuration parameters,
• mapping of PubSub concepts and configuration parameters to messages and transport protocols,
• and a PubSub configuration model.
This second edition cancels and replaces the first edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Addition of a “Quantity Model” which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) Addion of rules for ValuePrecision Property:
• can also be used for other subtypes like Duration and Decimal.
• rules have been added when ValuePrecision has negative values.
- Standard316 pagesEnglish languagesale 15% off
- Standard331 pagesFrench languagesale 15% off
- Standard647 pagesEnglish and French languagesale 15% off
IEC 62541-5:2026 This edition includes the following significant technical changes with respect to the previous edition:
a) Annex B has been removed and used to create IEC 62451-16;
b) Annex C has been removed and used to create IEC 62451-20;
c) currency information model has been added;
d) information model for Interfaces and AddIns has been added;
e) information model for Method Metadata has been added;
f) MaxSessions, MaxSubscriptions, and MaxMonitoredItems have been added to capabilities;
g) information model for ordered list of objects has been added;
h) PortableQualifiedName and PortableNodeId DataTypes have been added;
i) UriString DataType has been added;
j) SemanticVersionString DataType has been added;
k) AssociatedWith Reference Type has been added;
l) ConfigurationVersion Property has been added to NamespaceMetadataType;
m) AuditClientEventType and AuditClientUpdateMethodResultEventType have been added;
n) ModelVersion has been added to NamespaceMetadataType;
o) NoTransparentBackupRedundancyType has been added to support a Primary/Standby use case;
p) BitFieldType and BitFieldDefinitionType have been added.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
- Standard189 pagesEnglish languagesale 15% off
- Standard191 pagesFrench languagesale 15% off
- Standard380 pagesEnglish and French languagesale 15% off
IEC 62541-6:2025 specifies the mapping between the security model described in IEC 62541‑2, the abstract service definitions specified in IEC 62541‑4, the data structures defined in IEC 62541‑5 and the physical network protocols that can be used to implement the OPC UA specification.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of support for ECC to UA Secure Conversation;
b) use of the AuthorityKeyIdentifier extension in Certificate Revocation Lists;
c) enhancement of JSON mapping of Unions;
d) addition of Decimal data type encoding.
e) description of ECC keyUsage rules;
f) addition of Media assigned by IANA to UANodeSet definition;
g) addition of requirements for user and issuer Certificates;
h) addition of rules which specify what happens when DateTime precision is lost;
i) addition of rules to allow for the truncation of strings containing embedded nulls.
J) definition of a normative string representation for NodeId, ExpandedNodeId and QualifiedName for JSON mapping.
k) requirement that TAI times be converted to UTC;
l) new possibility to omit Symbol if unknown in JSON encoding;
m) addition of fields needed to support RolePermissions to the UANodeSet
- Standard138 pagesEnglish languagesale 15% off
- Standard150 pagesFrench languagesale 15% off
- Standard288 pagesEnglish and French languagesale 15% off
IEC 62541-11: 2025 defines the Information Model associated with Historical Access (HA). It particularly includes additional and complementary descriptions of the NodeClasses and Attributes needed for Historical Access, additional standard Properties, and other information and behaviour. The complete AddressSpace Model including all NodeClasses and Attributes is specified in IEC 62541‑3. The predefined Information Model is defined in IEC 62541‑5. The Services to detect and access historical data and events, and description of the ExtensibleParameter types are specified in IEC 62541‑4. This document includes functionality to compute and return Aggregates like minimum, maximum, average etc. The Information Model and the concrete working of Aggregates are defined in IEC 62541‑13. Conventions for Historical Access Clients are informatively provided in Annex A.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) a functionality has been added to support retrieving of modified events;
b) an Event has been added to indicate when a backfill occurred;
c) a new ReferenceType that can be used to indicate an external node has been defined;
d) the text has been improved to better explain the concept of annotation and remove conflicting explanations;
e) a default historian configuration (and where to find it) has been defined;
f) HistoricalEventConfigurationType, which provides general configuration information about the historical Event storage, has been added;
g) the text has been updated and optional fields have been added to HA configuration object to allow configuration to be defined for periodic data collection, not just for exception-based collection;
h) an ObjectType that can be used for external event collection has been provided as well as an example how historians can be configured.
- Standard73 pagesEnglish languagesale 15% off
- Standard229 pagesEnglish languagesale 15% off
- Standard78 pagesFrench languagesale 15% off
- Standard151 pagesEnglish and French languagesale 15% off
IEC 62541-8:2025 defines the information model associated with Data Access (DA). It particularly includes additional VariableTypes and complementary descriptions of the NodeClasses and Attributes needed for Data Access, additional Properties, and other information and behaviour. The complete address space model, including all NodeClasses and Attributes is specified in IEC 62541‑3. The services to detect and access data are specified in IEC 62541‑4. Annex A specifies how the information received from OPC COM Data Access (DA) Servers is mapped to the Data Access model. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of a "Quantity Model" which can be referenced from EngineeringUnit Properties. The model defines quantities and assigned units. In addition it provides alternative units and the conversion to them.
b) addition of rules for ValuePrecision Property:
- can also be used for other subtypes like Duration and Decimal.
- rules have been added when ValuePrecision has negative values.
- Standard92 pagesEnglish languagesale 15% off
- Standard281 pagesEnglish languagesale 15% off
- Standard94 pagesFrench languagesale 15% off
- Standard186 pagesEnglish and French languagesale 15% off
This document specifies the requirements of parameters for the physical and the link layer for systems using radio to remotely read meters. The primary focus is to use the Short Range Device (SRD) unlicensed bands. This document encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this document can be applied to various Application Layers.
- Standard104 pagesEnglish languagee-Library read for1 day
IEC 62541-3: 2025 describes the OPC Unified Architecture (OPC UA) AddressSpace and its Objects. This specification is the OPC UA meta model on which OPC UA information models are based. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of the concept and modelling elements for Interfaces and AddIns;
b) addition of Currency;
c) addition of Method Meta Data to define additional attributes for Method Arguments;
d) addition of ApplyRestrictionToBrowse bit to AccessRestrictionType;
e) addition of a Non-Volatile Storage bit to AccessLevelExType;
f) addition of a Constant bit and ConfigurationConstant bit to AccessLevelExType;
g) the View NodeClass has been changed to define the EventNotifier as an EventNotifierType in the same way the Object NodeClass defines it;
h) correctition of HasNotifier, HasEventSource, and Organizes, to include ObjectType as valid source node;
i) NamingRules have become deprecated;
j) addition of AssociatedWith ReferenceType.
- Standard138 pagesEnglish languagesale 15% off
- Standard427 pagesEnglish languagesale 15% off
- Standard147 pagesFrench languagesale 15% off
- Standard285 pagesEnglish and French languagesale 15% off
IEC 62541-100:2025 defines the information model associated with Devices. This document describes three models which build upon each other as follows:
• The (base) Device Model is intended to provide a unified view of devices and their hardware and software parts irrespective of the underlying device protocols.
• The Device Communication Model adds Network and Connection information elements so that communication topologies can be created.
• The Device Integration Host Model finally adds additional elements and rules required for host systems to manage integration for a complete system. It enables reflecting the topology of the automation system with the devices as well as the connecting communication networks.
This document also defines AddIns that can be used for the models in this document but also for models in other information models. They are:
• Locking model – a generic AddIn to control concurrent access,
• Software update model – an AddIn to manage software in a Device.
This second edition cancels and replaces the first edition published in 2015. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition:
a) a ComponentType that can be used to model any HW or SW element of a device has been defined and a SoftwareType has been added as subtype of ComponentType;
b) the new OPC UA interface concept and defined interfaces for Nameplate, DeviceHealth, and SupportInfo has been added.
c) a new model for Software Update (Firmware Update) has been added;
d) a new entry point for documents where each document is represented by a FileType instance has been specified;
e) a model that provides information about the lifetime, related limits and semantic of the lifetime of things like tools, material or machines has been added.
- Standard152 pagesEnglish languagesale 15% off
- Standard158 pagesFrench languagesale 15% off
- Standard310 pagesEnglish and French languagesale 15% off
IEC 62541-13:2025 defines the information model associated with Aggregates. Programmatically produced aggregate examples are listed in Annex A. This third edition cancels and replaces the second edition published in 2020. This edition constitutes a technical revision.
This edition includes the following technical changes with respect to the previous edition:
a) Multiple fixes for the computation of aggregates
• The Raw status bit is always set for non-bad StatusCodes for the Start and End aggregates.
• Entries in the Interpolative examples Tables A2.2 Historian1, Historian2, and Historian3 have been changed from Good to Good, Raw status codes when the timestamp matches with the timestamp of the data source.
• Missing tables have been added for DurationInStateZero and DurationInStateNonZero.
• The value of zero has been removed for results with a StatusCode of bad.
• Data Type was listed as "Status Code" when it is "Double" for both Standard Deviation and both Variance Aggregates.
• Rounding Error in TimeAverage and TimeAverage2 have been corrected.
• The status codes have been corrected for the last two intervals and the value has been corrected in the last interval.
• The wording has been changed to be more consistent with the certification testing tool.
• UsedSlopedExtrapolation set to true for Historian2 and all examples locations needed new values or status' are modified.
• Values affected by percent good and percent bad have been updated.
• PercentGood/PercentBad are now accounted for in the calculation.
• TimeAverage uses SlopedInterpolation but the Time aggregate is incorrectly allowed to used Stepped Interpolation.
• Partial bit is now correctly calculated.
• Unclear sentence was removed.
• Examples have been moved to a CSV.
• The value and status code for Historian 3 have been updated.
• TimeAverage2 Historian1 now takes uncertain regions into account when calculating StatusCodes.
• TimeAverage2 Historian2 now takes uncertain regions into account when calculating StatusCodes.
• Total2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Total2 Historian2 now takes uncertain regions into account when calculating StatusCodes
• Maximum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MaximumActualTime2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• Minimum2 Historian1 now takes uncertain regions into account when calculating StatusCodes
• MinimumActualTime2 Historian1 now has the StatusCodes calculated while using the TreatUncertainAsBad flag.
• Range2 Historian1 now looks at TreatUncertainAsBad in the calculation of the StatusCodes.
• Clarifications have been made to the text defining how PercentGood/PercentBad are used. The table values and StatusCodes of the TimeAverage2 and Total2 aggregates have been corrected.
- Standard64 pagesEnglish languagesale 15% off
- Standard235 pagesEnglish languagesale 15% off
- Standard64 pagesFrench languagesale 15% off
- Standard128 pagesEnglish and French languagesale 15% off
IEC 62541-7: 2025 specifies value and structure of Profiles in the OPC Unified Architecture.
OPC UA Profiles are used to segregate features with regard to testing of OPC UA products and the nature of the testing. The scope of this document includes defining functionality that can only be tested. The definition of actual TestCases is not within the scope of this document, but the general categories of TestCases are covered by this document.
Most OPC UA applications will conform to several, but not all of the Profiles.
This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) Profiles and ConformanceUnits are not part of this document, but are solely managed in a public database as described in Clause 1.
- Standard160 pagesEnglish languagesale 15% off
- Standard173 pagesFrench languagesale 15% off
- Standard333 pagesEnglish and French languagesale 15% off
IEC 62541-10:2025 defines the Information Model associated with Programs in OPC Unified Architecture (OPC UA). This includes the description of the NodeClasses, standard Properties, Methods and Events and associated behaviour and information for Programs. The complete AddressSpace model including all NodeClasses and Attributes is specified in IEC 62541-3. The Services such as those used to invoke the Methods used to manage Programs are specified in IEC 62541-4. An example for a DomainDownload Program is defined in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
- StateMachine table format has been aligned.
- Standard42 pagesEnglish languagesale 15% off
- Standard140 pagesEnglish languagesale 15% off
- Standard45 pagesFrench languagesale 15% off
- Standard87 pagesEnglish and French languagesale 15% off
IEC 62541-4:2025 defines the OPC Unified Architecture (OPC UA) Services. The Services defined are the collection of abstract Remote Procedure Calls (RPC) that are implemented by OPC UA Servers and called by OPC UA Clients. All interactions between OPC UA Clients and Servers occur via these Services. The defined Services are considered abstract because no particular RPC mechanism for implementation is defined in this document. IEC 62541‑6 specifies one or more concrete mappings supported for implementation. For example, one mapping in IEC 62541‑6 is to UA-TCP UA-SC UA-Binary. In that case the Services described in this document appear as OPC UA Binary encoded payload, secured with OPC UA Secure Conversation and transported via OPC UA TCP. Not all OPC UA Servers implement all of the defined Services. IEC 62541‑7 defines the Profiles that dictate which Services must be implemented in order to be compliant with a particular Profile. A BNF (Backus-Naur form) for browse path names is described in Annex A. This fourth edition cancels and replaces the third edition published in 2020. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) addition of new definitions to Method Call Service to allow optional Method arguments;
b)addition of reference to SystemStatusChangeEventType for event monitored item error scenarios;
c) enhancement of the general description of how determining if a Certificate is trusted;
d) addition of support for ECC;
e) addition of revisedAggregateConfiguration to AggregateFilterResult structure;
f) addition of INVALID to the BrowseDirection enumeration data type;
g) addition of INVALID to the TimestampsToReturn enumeration data type;
h) addition of definitions that make sure the subscription functionality works if retransmission queues are optional;
i) addition of client checks has been added to be symmetric to the Server Certificate check has been added;
j) clarification that ‘local’ top level domain is not appended by server into certificate and not checked by client when returned from LDS-ME;
k) addition of a definition for expiration behaviour of IssuedIdentityTokens;
l) addition of status code Good_PasswordChangeRequired to ActivateSession;
m) restriction of AdditionalInfo to servers in debug mode;
n) addition of new status code Bad_ServerTooBusy;
o) addition of definition for cases where server certificate must be contained in GetEndpoints response.
- Standard245 pagesEnglish languagesale 15% off
- Standard751 pagesEnglish languagesale 15% off
- Standard257 pagesFrench languagesale 15% off
- Standard502 pagesEnglish and French languagesale 15% off
This document specifies the requirements of parameters for the physical and the link layer for systems using radio to remotely read meters. The primary focus is to use the Short Range Device (SRD) unlicensed bands. This document encompasses systems for walk-by, drive-by and fixed installations. As a broad definition, this document can be applied to various Application Layers.
- Standard104 pagesEnglish languagee-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.
IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagee-Library read for1 day
This document specifies conformance tests in the form of an abstract test suite (ATS) for a system under test (SUT) that implements an electric-vehicle communication controller (EVCC) or a supply-equipment communication controller (SECC) for all common requirements specified in ISO 15118-20 that are independent of a particular charging type (AC, DC, ACD, WPT charging). These conformance tests specify the testing of capabilities and behaviours of an SUT, as well as checking what is observed against the conformance requirements specified in ISO 15118-20 and against what the implementer states the SUT implementation's capabilities are.
The capability tests within the ATS check that the observable capabilities of the SUT are in accordance with the static conformance requirements specified in ISO 15118-20. The behaviour tests of the ATS examine an implementation as thoroughly as practical over the full range of dynamic conformance requirements specified in ISO 15118-20 and within the capabilities of the SUT.
A test architecture is described in correspondence to the ATS. The abstract test cases in this document are described leveraging this test architecture and are specified in descriptive tabular format covering the ISO/OSI layer 3 to 7 (network to application layers).
In terms of coverage, this document only covers normative sections and requirements in ISO 15118-20. This document additionally refers to specific tests for requirements on referenced standards (e.g. IETF RFCs, W3C Recommendation, etc.) if they are relevant in terms of conformance for implementations according to ISO 15118-20. However, it is explicitly not intended to widen the scope of this conformance specification to such external standards, if it is not technically necessary for the purpose of conformance testing for ISO 15118-20. Furthermore, the conformance tests specified in this document do not include the assessment of performance nor robustness or reliability of an implementation. They cannot provide judgments on the physical realization of abstract service primitives, how a system is implemented, how it provides any requested service, or the environment of the protocol implementation. Furthermore, the abstract test cases specified in this document only consider the communication protocol and the system's behaviour specified in ISO 15118-20. Power flow between the EVSE and the EV is no prerequisite for the test cases specified in this document.
- Standard331 pagesEnglish languagee-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It • explains the structure and content of the IEC 62453 series (see Clause 5); • provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series; • describes the relationship to some other standards; • provides definitions of terms used in other parts of the IEC 62453 series. This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision. This edition includes the following significant technical changes with respect to the previous edition: a) introduction of a new implementation technology (defined in IEC TS 62453-43); b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard56 pagesEnglish languagee-Library read for1 day
IEC 62657-2:2025 specifies:
– the fundamental assumptions, concepts, parameters, and procedures for wireless communication coexistence;
– specifies coexistence parameters and how they are used in an application requiring wireless coexistence;
– provides guidelines, requirements, and best practices for wireless communication's availability and performance in an industrial automation plant; it covers the life‑cycle of wireless communication coexistence;
– helps the work of all persons involved with the relevant responsibilities to cope with the critical aspects at each phase of life-cycle of the wireless communication coexistence management in an industrial automation plant. Life-cycle aspects include: planning, design, installation, implementation, operation, maintenance, administration and training;
– provides a common point of reference for wireless communication coexistence for industrial automation sites as a homogeneous guideline to help the users assess and gauge their plant efforts;
– deals with the operational aspects of wireless communication coexistence regarding both the static human/tool-organization and the dynamic network self-organization.
This document provides a major contribution to national and regional regulations by supporting to fulfil the requirements using coexistence management.
This edition includes the following significant technical changes with respect to the previous edition:
a) alignment of some definitions and specifications of coexistence parameters in order to facilitate their future inclusion in the IEC Common Data Dictionary (IEC CDD) maintained by the IEC;
b) alignment of some definitions and specifications to be consistent with the new IEC 62657-3 and IEC 62657-4;
c) edition 3 of this document was published in June 2022. Some comments were made in the last development stages of this document asking for explanations on how the parts of the IEC 62657 series were structured and how they were related to each other. Resolution of these comments was deferred until a next edition, which means this edition.
- Standard118 pagesEnglish languagee-Library read for1 day
This document provides guidance on how to prepare new and old protocols for cryptographic algorithm migration and defines auxiliary cryptographic algorithms to be used for migration purposes. This document specifies a general wrapper protocol that provides authentication, integrity and confidentiality (encryption) protection for other protocols. This wrapper protocol includes a migration path for cryptographic algorithms allowing for smooth migration to stronger cryptographic algorithms as such requirements evolve. This will allow migration to quantum-safe cryptographic algorithms. Protected protocols can then be developed without taking security and cryptographic algorithms into consideration. This document also includes some protocols to be protected by the wrapper protocol primarily for support of public-key infrastructure (PKI). Other specifications, e.g., Recommendations or International Standards, may also develop protocols designed to be protected by the wrapper protocol.
- Standard120 pagesEnglish languagesale 15% off
This part 8 specifies the physical layer of an onboard data transmission bus between the different equipment for service operations and monitoring of the fleet. This applies to equipment installed on board vehicles that are operating as part of a public transport network, i.e. in operation under public service contracts. This equipment includes operation aid systems, automatic passenger information systems, fare collection systems, etc.
The use of IEEE 802.11 Wireless LAN communications is excluded from the scope of this Technical Specification; its use is not recommended for the service-based approach of CEN/TS 13149.
Equipment directly related to the safety-related functioning of the vehicle (propulsion management, brake systems, door opening systems, etc.) are excluded from the scope of this Technical Specification and are dealt with in other standardization bodies. Interfaces to such equipment or safety-critical networks can be provided through dedicated gateways.
This document covers the following:
— The link between equipment inside vehicles consisting of one carriage only, e.g. buses and trolleybuses, as well as a set of carriages, e.g. trams and trains;
— The Physical Layer for IP-communication networks onboard PT vehicles;
— The cables, connectors and other equipment including pin assignment and environmental requirements.
This document specifies wired communication networks onboard PT vehicles which are based on the Ethernet specification ISO/IEC/IEEE 8802-3-10 Base T, 100 Base Tx and 1000 Base T.
- Technical specification19 pagesEnglish languagee-Library read for1 day
- Technical specification20 pagesEnglish languagee-Library read for1 day
IEC 62453-1:2025 is available as IEC 62453-1:2025 RLV which contains the International Standard and its Redline version, showing all changes of the technical content compared to the previous edition.IEC 62453-1:2025 presents an overview and guidance for the IEC 62453 series. It
• explains the structure and content of the IEC 62453 series (see Clause 5);
• provides explanations of some aspects of the IEC 62453 series that are common to many of the parts of the series;
• describes the relationship to some other standards;
• provides definitions of terms used in other parts of the IEC 62453 series.
This third edition cancels and replaces the first edition published in 2016. This edition constitutes a technical revision.
This edition includes the following significant technical changes with respect to the previous edition:
a) introduction of a new implementation technology (defined in IEC TS 62453-43);
b) introduction of an OPC UA information model for FDT (defined in IEC 62453-71).
- Standard52 pagesEnglish languagesale 15% off
- Standard107 pagesEnglish languagesale 15% off
- Standard55 pagesFrench languagesale 15% off
- Standard107 pagesEnglish and French languagesale 15% off
- Standard2 pagesEnglish languagesale 15% off
- Standard42 pagesEnglish languagesale 15% off
- Standard34 pagesEnglish languagesale 15% off