Understand the IAES model before diving into the specification. Events, envelopes, lifecycle, condition trends, and how IAES aligns with existing industrial standards.
Every IAES event shares a common envelope that provides traceability, deduplication, and interoperability across all producers and consumers.
IAES v2.0 covers the full lifecycle from physical observation to maintenance closure and inventory impact.
Raw or normalized sensor readings from industrial assets. Vibration, temperature, current, pressure, flow, speed.
AI or expert interpretation of asset condition. Health score, fault classification, remaining useful life, and recommended action.
Declares the intent to create a work order. The consumer decides whether and how to act — IAES doesn't prescribe.
Acknowledges work order completion with outcome details, duration, checklist status, and failure confirmation.
Synchronizes the asset tree — organizations, plants, areas, and equipment — across systems.
Tracks sensor discovery, registration, calibration, and decommissioning across the asset fleet.
Records spare parts consumed during maintenance. Linked to work orders for cost tracking and inventory planning.
From raw industrial telemetry to operational workflow — IAES events bridge the gap between physical signals and business actions.
PLC, sensor, meter
AI, rules, expert
asset.health
onset → recovery
CMMS, ERP, BI
Added in v1.3, the condition_trend field on asset.health events tracks whether an asset's condition is getting worse, holding steady, or recovering.
A complete incident from detection to resolution. Four IAES events tell the full story — no human intervention needed to close the alert.
IAES does not replace existing standards, and it does not certify against them. It borrows vocabulary where one already exists.
Condition monitoring guidelines. IAES borrows the vocabulary of units_qualifier and the acquisition fields. Context, not conformance.
Condition monitoring data processing. iso_13374_status carries IAES’s own seven values; the ISO attribution was withdrawn in 2.0.
Equipment reliability data. The iso_14224 object carries failure mode, mechanism and cause codes. IAES asserts no conformance to the standard.
| Standard | Scope | Relationship to IAES |
|---|---|---|
| ISO 55000 | Asset management system | IAES events feed ISO 55000 decision processes — the standard says what to manage, IAES carries the signals. |
| AAS (I4.0) | Digital twin shell | AAS describes asset structure. IAES describes asset events. They are complementary — events can flow into AAS submodels. |
| CCOM / IDO | Equipment data ontology | CCOM defines equipment taxonomy. IAES defines what happens to that equipment. IAES events can reference CCOM class IDs. |
| OPC UA | Machine-to-machine protocol | OPC UA moves raw data from PLCs. IAES carries interpreted events above that layer. An OPC UA subscriber can produce IAES events. |
| ISA-95 | Enterprise-control integration | ISA-95 defines levels (L0–L4). IAES events flow across those levels — from shop-floor intelligence to enterprise systems. |
IAES fills a specific gap: a minimal, vendor-neutral event vocabulary for industrial assets. Existing standards define structure, taxonomy, protocols, and management frameworks. IAES defines the events — what happened, to which asset, with what severity.
IAES events can be produced by any source — sensor, AI engine, or human expert — and consumed by any operational system.