IAES standardizes what happens to industrial assets.
Not how you measure it. Not how you store it.
OPC UA moves data. Sparkplug B structures telemetry. IAES names what happened.
A minimal, vendor-neutral event language for industrial assets. IAES names what happens to equipment — measurements, diagnoses, failures, maintenance actions — so any system can produce, route, and consume asset events without custom integration.
Open standard. Vendor-neutral. Reference implementation by Wertek AI.
Who is this for?
For system integrators, OT engineers, and industrial developers who need to connect SCADA, CMMS, AI, and enterprise systems.
In every industrial plant, critical systems operate in isolation. Each one generates events about the same assets — but in completely different formats, APIs, and semantics.
There is no common language for asset events in industry. IAES provides one.
IAES doesn't compete with existing standards. It occupies a different layer.
| Standard | Purpose |
|---|---|
| ISO 55000 | Asset management principles |
| AAS (I4.0) | Digital twin structure |
| ISA-95 | Manufacturing operations architecture |
| OPC UA | Machine-to-machine communication |
| IAES | Event language for industrial assets |
IAES covers events across all industrial domains:
A sensor detects bearing wear. An AI model classifies the fault — or a technician records a diagnosis from a mobile app. Either way, IAES routes one event to three systems simultaneously.
12.4 mm/s RMS
156 Hz
bearing_inner_race
confidence: 0.94
asset.health
severity: critical
rul_days: 5
IW31 notification
Work order assigned
Alert panel fired
PLCs and sensors don't know IAES exists. The intelligence layer — AI models, rule engines, gateways — translates raw signals into standardized events.
A vibration sensor reads 12.4 mm/s on compressor C-12. An energy meter detects power factor dropping to 0.87. A thermal camera sees 94°C on a bearing housing.
An AI model, rule engine, or gateway interprets the raw data and emits a standardized IAES event with asset identity, severity, and recommended action.
The same event can simultaneously create a work order in SAP, trigger an alert in Grafana, update a digital twin, and feed an AI model for trending.
The PLC doesn't know IAES exists. An AI engine reads raw vibration data and emits an IAES event. A technician opens an app, records a diagnosis, and that's also an IAES event. IAES is the language of the intelligence layer — whether the intelligence is artificial or human.
A complete incident from detection to resolution. Four IAES events tell the full story — no human intervention needed to close the alert.
Already implemented in
Published on PyPI, npm, and Node-RED palette. Production-ready.
Any producer. One event format. Any consumer.
No vendor lock-in. Any system can produce or consume IAES events without proprietary dependencies.
Events are first-class citizens. Each event is self-contained, traceable, and independently meaningful.
IAES declares what should happen, not how. Consumers decide implementation — preserving autonomy and flexibility.
Licensed under CC BY 4.0. Free to use, implement, extend, and distribute. Open development on GitHub.
New versions add optional fields. Existing producers and consumers continue working without changes.
IAES is developed in the open. The specification, JSON schemas, examples, and reference implementations are all available on GitHub. Contributions, issues, and discussions are welcome.
Licensed under Creative Commons Attribution 4.0 (CC BY 4.0)
Normative: IAES_SPEC.md, GOVERNANCE.md and the JSON Schemas. The RFCs record why each change was made — rationale, not authority; IAES-RFC-001 is the original 1.x memo.
IAES 2.0: 10.5281/zenodo.22663498 · every release (resolves to the latest): 10.5281/zenodo.18973216
Permanent, citable identifier via Zenodo (CERN). Indexed by OpenAIRE and Software Heritage. Uses IETF conventions (MUST / SHOULD / MAY per RFC 2119).
If you use IAES in research, industrial systems, or procurement documents, please cite:
Garza, G. (2026).
Industrial Asset Event Standard (IAES) v2.0.
Zenodo.
https://doi.org/10.5281/zenodo.22663498
@software{garza_iaes_2026,
author = {Garza, Gilberto},
title = {Industrial Asset Event Standard (IAES)},
version = {2.0},
year = {2026},
publisher = {Zenodo},
doi = {10.5281/zenodo.22663498},
url = {https://doi.org/10.5281/zenodo.22663498}
}
DOI resolves permanently via Zenodo (CERN). Licensed under CC BY 4.0.
Side-by-side comparison of OPC UA, Sparkplug B, AAS, and IAES. Different layers, different purposes.
What IAES references, what it depends on, and what it does not claim.
How IAES reduces 10,000 alerts to 2 incidents with event correlation.
Code examples, consumer patterns, and integration scenarios for PLCs, SCADA, and CMMS.
Real-world integration patterns: PLC to SAP PM, n8n automation, alert reduction.
SDKs, bridges, CLI tools, and Node-RED nodes for building IAES integrations.