Companion specification · Tier 2

Safety

Version1.05.04
Published2025-02-05
Namespacehttp://opcfoundation.org/UA/Safety
SectorFunctional safety

The OPC UA Safety model, at 1.05.04 from February 2025. It defines a safety communication layer for transmitting safety-relevant data over OPC UA, which is a fundamentally different engineering proposition from everything else on this site.

Where it sits in the stack

A core-versioned utility model. It is also packaged in the UAFX AutomationML bundles alongside the field exchange models.

The types that matter

TypeWhat it carries
(type inventory not confirmed)We have not verified the type inventory. Safety engineering is not something to learn from a summary page.

Using it on a real machine

  1. Involve a safety engineerFunctional safety is a regulated discipline with certification requirements. This is not an area to integrate on the strength of a reference page - ours or anyone's.
  2. Understand the separationSafety communication is a distinct layer with its own requirements. It is not ordinary OPC UA data with a label on it.
  3. Check certification requirementsSafety-relevant communication typically requires certified components end to end. Establish that before selecting anything.

What it gives you for OEE

None, and deliberately so. Safety data is not analytics data. Do not route safety-relevant communication through an analytics path, and do not derive availability from safety signals.

Try it free: No free public server exposes this model as far as we know. To see it you need a machine that implements it or a vendor demo. If you find a public endpoint, tell us and we will add it.

Gotchas

  • Functional safety is a regulated engineering discipline. A reference page is not adequate preparation, including this one.
  • Certified components are typically required end to end.
  • Never mix safety communication with analytics data paths.
Verify before you rely on this: We have deliberately kept this page short. Functional safety requires qualified engineering input and certified components, and the specific requirements depend on your application and jurisdiction. Treat this page as recognition of the model's existence, nothing more.
Concepts on this page

Once the machine speaks a companion spec, the OEE mapping is portable across vendors, which is the point at which analytics stops being a per-machine project.

See Jemba →

Last verified 7 September 2026 against OPC UA 1.05.07. Version and publication date read from the released nodeset. OPC UA Connect is an educational resource and is not affiliated with the OPC Foundation.

Free download
OPC UA Machine Data → OEE Mapping Kit
Which nodes to subscribe to, how they become Availability, Performance and Quality, and which companion specification already gives you the answer, so you stop inventing tags.
Get the free mapping kit →
Free, no course, no login