Examples

Real-world IAES events demonstrating every published event type — from sensor readings to AI diagnoses, work order intents, completion, hierarchy, sensor registration, and spare parts.

Sensor Reading

Vibration measurement from wireless sensor

asset.measurement

A Banner DXM100 gateway reports 4.2 mm/s vibration velocity from the drive-end bearing of a motor pump.

"source": "banner.dxm100" "asset": { "asset_id": "MOTOR-001", "plant": "Pesqueria" } "data": { "measurement_type": "vibration_velocity", "value": 4.2, "unit": "mm/s", "sensor_id": "SENSOR-045", "location": "bearing_drive_end" }

AI Diagnosis

Critical bearing fault detected by AI

asset.health

Wertek AI vibration analysis detects an inner race bearing defect with 87% confidence. Health index at 16%, RUL 5 days. Immediate action recommended.

"source": "wertek.ai.vibration" "data": { "health_index": 0.16, "anomaly_score": 0.92, "severity": "critical", "failure_mode": "bearing_inner_race", "fault_confidence": 0.87, "rul_days": 5, "recommended_action": "Replace bearing immediately", "estimated_downtime_hours": 4 }

Human Expert Assessment

Technician detects cavitation in centrifugal pump

asset.health

A field technician uses the same asset.health event type to report a pump cavitation issue found during a manual inspection. The source field identifies this as a human assessment, not an AI diagnosis.

"source": "operator.field_assessment" "asset": { "asset_id": "PUMP-042", "plant": "Monterrey Norte" } "data": { "health_index": 0.45, "severity": "high", "failure_mode": "cavitation", "fault_confidence": 0.70, "recommended_action": "Check suction line for air leaks, verify NPSH" }

Work Order Intent

AI-triggered emergency work order

maintenance.work_order_intent

Following the critical bearing diagnosis, the system declares intent to create an emergency work order. The consuming CMMS (SAP, Odoo, MaintainX) decides how to act.

"source": "wertek.ai.cmms" "source_event_id": "a9e3c4b2-..." // references the health event "data": { "title": "Bearing failure predicted — Motor Bomba P-101", "priority": "emergency", "recommended_due_days": 3, "triggered_by": "ai_diagnosis" }

IAES v1.1 Event Types

Work order completed with failure confirmation

maintenance.completion

A technician completes a bearing replacement, confirms the AI-predicted failure mode, and logs 2 hours of work with full checklist completion.

"source": "wertek.ai.cmms" "data": { "status": "completed", "work_order_id": "WO-2026-001", "actual_duration_seconds": 7200, "checklist_completion_pct": 100, "failure_confirmed": true, "failure_mode": "bearing_inner_race", "spare_parts_count": 1 }

Asset hierarchy — 4-level structure sync

asset.hierarchy

Four events define an asset tree: Organization → Plant → Area → Equipment. Each node declares its level, parent, and relationship type.

// 4 events, same batch_id and correlation_id { "hierarchy_level": "organization", "relationship_type": "parent_of" } { "hierarchy_level": "plant", "relationship_type": "child_of" } { "hierarchy_level": "area", "relationship_type": "child_of" } { "hierarchy_level": "equipment", "relationship_type": "child_of" }

MCSA current sensor registered

sensor.registration

A Teensy 4.1-based MCSA current transformer is registered on a motor asset, with firmware version, capabilities, and calibration date.

"source": "wertek.ai.sensors" "data": { "sensor_id": "MCSA-CT-001", "registration_status": "registered", "sensor_model": "Teensy 4.1 + SCT-013", "firmware_version": "1.0.3", "measurement_capabilities": ["current", "vibration_acceleration"], "communication_protocol": "mqtt" }

Bearing consumed during maintenance

maintenance.spare_part_usage

Records consumption of an SKF 6205 bearing during a work order, with unit cost and currency for inventory and cost tracking.

"source": "wertek.ai.cmms" "data": { "work_order_id": "WO-2026-001", "spare_part_id": "SP-SKF-6205", "quantity_used": 1, "part_number": "SKF 6205-2RS", "part_name": "Deep groove ball bearing", "unit_cost": 28.50, "currency": "USD" }

Complete Flow (3-Event Chain)

Measurement → Diagnosis → Work Order Intent

full-flow

Three events sharing the same correlation_id, demonstrating the core observation-to-action pipeline. Each event references its predecessor via source_event_id.

// All 3 events share correlation_id: 3b2f9d8c-1c33-... // Step 1: Sensor reading { "event_type": "asset.measurement", "source": "banner.dxm100" } // Step 2: AI diagnosis (source_event_id → measurement) { "event_type": "asset.health", "source": "wertek.ai.vibration" } // Step 3: Work order intent (source_event_id → health) { "event_type": "maintenance.work_order_intent", "source": "wertek.ai.cmms" }

Complete Flow v1.1 (5-Event Chain)

Measurement → Health → Work Order → Completion → Spare Part

full-flow-v1.1

Five events sharing the same correlation_id, demonstrating the complete lifecycle from sensor reading through maintenance closure and inventory impact. Uses batch_id for the measurement batch.

// 5 events, same correlation_id, batch_id on measurement // Step 1: Sensor reading (batch_id groups concurrent readings) { "event_type": "asset.measurement", "batch_id": "BATCH-001" } // Step 2: AI diagnosis { "event_type": "asset.health", "severity": "critical" } // Step 3: Work order intent { "event_type": "maintenance.work_order_intent", "priority": "emergency" } // Step 4: Completion (failure confirmed) { "event_type": "maintenance.completion", "failure_confirmed": true } // Step 5: Spare part consumed { "event_type": "maintenance.spare_part_usage", "quantity_used": 1 }