The Industrial Asset Event Standard — a minimal, vendor-neutral JSON format that gives every industrial system a common language for describing what happens to equipment.
IAES is a JSON vocabulary that names what happens to industrial equipment.
Measurements, diagnoses, failures, work orders, completions — one format, any transport, any vendor.
// A pump reports a health event. That's it. { "event_type": "asset.health", "asset": { "asset_id": "pump-401A" }, "data": { "health_index": 0.42, "status": "warning" } }
Industrial facilities run dozens of systems that generate equipment data: SCADA, CMMS, historians, PLCs, vibration analyzers, thermal cameras, energy meters. Each speaks its own language.
When a pump bearing degrades, the vibration sensor logs an alarm in one format, the CMMS creates a work order in another, and the historian records process data in a third. There is no common event language that connects them.
The result: data silos, manual re-entry, delayed responses, and lost context. Integrators spend months building custom bridges that break at every version upgrade.
IAES defines a minimal JSON envelope plus typed event payloads. Any system can produce and consume IAES events without vendor lock-in or proprietary protocols.
currency. Citation is not conformance.IAES does not replace existing standards. It occupies a different layer.
| Standard | Layer | Defines | Format | Asset Events? |
|---|---|---|---|---|
| OPC UA | Communication | How machines talk to each other | Binary / XML | No |
| MQTT | Transport | How messages are delivered (pub/sub) | Any (opaque bytes) | No |
| Sparkplug B | Telemetry model | How devices report metrics over MQTT | Protobuf | Metrics only |
| AAS | Digital twin | How to model an asset digitally | JSON / XML / RDF | No |
| IAES | Event semantics | What happened to an asset, why, and what to do | JSON | Yes |
OPC UA moves bytes. MQTT delivers messages. Sparkplug B structures telemetry. AAS models digital twins. IAES names what happened to the asset — and that layer didn’t exist before.
Every IAES event is a JSON object with a standard envelope wrapping a typed payload. The envelope identifies what happened, where, and when — the payload carries the domain-specific data.
{
"event_type": "asset.health",
"spec_version": "2.0",
"event_id": "evt-a1b2c3d4",
"timestamp": "2026-03-14T08:30:00Z",
"source_system": "vibration-monitor",
"asset_id": "pump-401A",
"site_id": "plant-monterrey",
"payload": {
"health_index": 0.42,
"status": "warning",
"condition_trend": "worsening",
"diagnosis": "Bearing inner race defect detected",
"confidence": 0.89
}
}
The envelope fields (event_type, asset_id, timestamp) are always present. The payload structure varies by event type.
Each event type has a JSON Schema, example payloads, and clear field definitions.
Raw sensor readings — vibration, temperature, pressure, current. Includes units, sampling rate, and acquisition parameters.
Computed health status for an asset — health index (0–1), status level, diagnosis text, confidence, and condition trend.
A request to create a work order — priority, description, recommended action. Bridges monitoring to CMMS.
Work completed on an asset — what was done, duration, technician, parts used. Closes the maintenance loop.
Organizational structure — site, area, line, asset relationships. Defines where equipment lives.
A new sensor or gateway coming online — type, location, communication protocol, linked asset.
Parts consumed during maintenance — part number, quantity, cost, linked work order.
IAES references established industrial standards where they provide context or an external vocabulary. The specification states explicitly when a reference is normative for meaning.
Condition monitoring guidance. IAES borrows the vocabulary of units_qualifier and the acquisition fields. Context, not conformance.
Machine 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.
Asset management systems. IAES events provide the data foundation for lifecycle visibility, risk assessment, and evidence-based decision making.
Connect SCADA, historians, and CMMS platforms with a standard event format instead of building custom point-to-point bridges for every combination.
Standardize event data across vibration, thermal, and electrical monitoring systems. One format for all condition data feeding into work order decisions.
Build interoperable tools that consume events from any IAES-compliant source. Reduce integration cost and expand your addressable market.
Industrial telemetry generates millions of data points. Most of it is noise. Events are the signal.
A single vibration sensor generates 10,000+ readings per second. No human or system can act on raw data at that volume. You need interpretation.
An IAES event says: “Pump 401A bearing is degrading, health index 0.42, condition worsening.” One JSON object replaces millions of raw samples.
That same event can create a work order in SAP, trigger an alert in Grafana, update a digital twin, and feed an AI model — all without custom integration per system.
Garza, G. (2026). Industrial Asset Event Standard (IAES) v2.0. Zenodo.
https://doi.org/10.5281/zenodo.22663498
Licensed under CC BY 4.0. DOI resolves permanently via Zenodo (CERN).