Open Specification v1.0

Industrial Asset
Event Standard

A standard event model for industrial maintenance systems.

IAES is a vendor-neutral event specification that standardizes how signals, health assessments, and maintenance actions move across heterogeneous systems — AI engines, CMMS platforms, historians, dashboards, and enterprise tools.

Read the Specification Reference Architecture GitHub

Open standard. Neutral data model. Reference implementation by Wertek AI.

SignalsSensors, video, SCADA, gateways
↓
IntelligenceAI diagnosis, rules, human experts
↓
IAES StandardNeutral event model
↓
ConnectorsMapping, sync, retry, audit
↓
Enterprise SystemsSAP PM, PI System, Odoo, Fracttal, MaintainX

Industrial systems don't speak the same language

Maintenance data flows through dozens of incompatible systems. Each uses its own model, schema, API, and semantics — making it hard to turn observations into operational action.

Typical data sources

  • Vibration, temperature, and pressure sensors
  • Video and acoustic diagnostic systems
  • SCADA, PLC, and historian infrastructure
  • Inspection apps and technician inputs
  • AI models, rule engines, and expert analysis

Typical enterprise destinations

  • CMMS and EAM platforms (SAP, Odoo, MaintainX, Fracttal)
  • Historians and industrial data hubs (PI, AVEVA)
  • Dashboards and BI tools (Grafana, Power BI)
  • Digital twin and reliability applications
  • Maintenance planning and scheduling systems

Why IAES exists

Industrial systems integrate through custom mappings.

Sensor vendors, AI diagnostics, CMMS systems, and historians all use incompatible schemas. Every new connection requires a bespoke adapter, and every adapter is a maintenance burden.

IAES exists to provide a neutral event model that allows these systems to interoperate — without knowing anything about each other's implementation.

IAES introduces a neutral event layer

Instead of building custom integrations between every system, producers emit IAES events and consumers map them to their native format. One standard, many systems.

SignalsSensors, video, SCADA
→
IntelligenceAI, rules, human experts
→
IAES StandardNeutral event envelope
→
ConnectorsMap, sync, retry, audit
→
EnterpriseCMMS, historian, BI, apps

Three core event types

IAES v1 stays intentionally minimal. Three event types cover the full path from observation to operational intent.

asset.measurement

Physical observation

Raw or normalized sensor readings from industrial assets. Vibration, temperature, current, pressure, flow, speed.

measurement_type value unit sensor_id location
asset.health

Diagnostic assessment

AI or expert interpretation of asset condition. Health score, fault classification, RUL, and recommended action.

health_index anomaly_score severity failure_mode rul_days recommended_action
maintenance.work_order_intent

Operational intent

Declares the intent to create a work order. The consumer decides whether and how to act — IAES doesn't prescribe.

title description priority recommended_due_days triggered_by

Common event envelope

Every IAES event shares a common envelope for traceability, deduplication, and interoperability.

{ "spec_version": "1.0", "event_type": "asset.health", "event_id": "a9e3c4b2-9d3a-4a12-b1f3-2e44a1caa8a1", "correlation_id": "3b2f9d8c-1c33-4a8a-9b77-54d11b2efc12", "source_event_id": "f4ce4f8c-26fd-4f15-8b2f-2c9425ad1110", "timestamp": "2026-03-06T17:50:17Z", "source": "wertek.ai.diagnosis", "content_hash": "8a3f9c2e1b4d7e6f", "asset": { "asset_id": "MOTOR-001", "asset_name": "Pump Motor P-101", "plant": "Pesqueria", "area": "Turbines" }, "data": { "health_index": 0.16, "anomaly_score": 0.92, "severity": "critical", "failure_mode": "bearing_inner_race", "rul_days": 5, "recommended_action": "Replace bearing immediately" } }

Envelope fields

  • spec_version — IAES version (currently "1.0")
  • event_type — canonical event name
  • event_id — unique event identifier (UUID)
  • correlation_id — links related events in a flow
  • source_event_id — traces causal origin
  • timestamp — ISO 8601, when the event occurred
  • source — dot-notation producer identity
  • content_hash — SHA-256 prefix for deduplication
  • asset — neutral asset identity block
  • data — event-type-specific payload

Shared semantics

severity: info | low | medium | high | critical health_index: 0.0 – 1.0 anomaly_score: 0.0 – 1.0 rul_days: integer

Connecting the industrial ecosystem

IAES events can be produced by any source — sensor, AI engine, or human expert — and consumed by any operational system.

Producers

Vibration sensors Temperature sensors Acoustic systems Cameras / video Edge gateways AI diagnosis engines Rule engines Inspection apps Technician assessments Lab analysis SCADA / PLC

Consumers

SAP PM Odoo Maintenance MaintainX Fracttal PI System AVEVA Data Hub Grafana Power BI Digital Twin platforms Time-series databases MQTT brokers

Open specification

IAES is an open technical specification designed to enable interoperability across industrial maintenance systems and vendors.

Specification

Full documentation describing the event model, semantics, and implementation guidance.

Read the spec →

JSON Schema

Machine-readable schemas for validation, code generation, and API contracts.

Browse schemas →

Examples

Real event examples for measurements, health diagnostics, and work order intent flows.

View examples →

Reference implementation

The first reference implementation of IAES is developed within the Wertek AI platform, where IAES connects asset intelligence with enterprise operational systems across 6 connectors.

wertek.ai Integration SDK