ERP Enrichment Schemas

The ERP enrichment schemas bridge operational data from ERP/EAM systems (work orders, inventory, procurement) and SCADA alarm analytics into ODS-E. Together, these seven schemas give O&M teams a unified view of equipment identity, maintenance history, spare parts availability, failure patterns, and alarm escalation — the data foundation for maintenance event triage and predictive workflows.

Architecture

The seven schemas form a tightly coupled system linked by three shared keys: equipment_id, part_id, and failure_code.

                          ┌─────────────────────┐
                          │  Equipment ID Map    │
                          │  (identity linchpin) │
                          └──────────┬──────────┘
                                     │ equipment_id
                    ┌────────────────┼────────────────┐
                    │                │                 │
                    ▼                ▼                 ▼
        ┌───────────────┐  ┌─────────────────┐  ┌──────────────────────┐
        │  Equipment     │  │  Maintenance    │  │  Alarm Frequency     │
        │  Register      │  │  History        │  │  Profile             │
        │                │  │                 │  │  (derived)           │
        └───────────────┘  └────────┬────────┘  └──────────────────────┘
                                    │
                           failure_code    part_id
                           ┌────────┴────────┐
                           │                 │
                           ▼                 ▼
                ┌───────────────┐  ┌───────────────┐
                │  Failure      │  │  Spare Parts  │
                │  Taxonomy     │  │               │
                └───────────────┘  └───────┬───────┘
                                           │ part_id
                                           ▼
                                   ┌───────────────┐
                                   │  Procurement  │
                                   │  Context      │
                                   └───────────────┘

Equipment ID Map

The identity linchpin. Maps a canonical ODS-E equipment_id to its native identifiers across ERP, SCADA, and monitoring systems. Every other enrichment schema references equipment through this canonical ID.

Schema type: array (each item is one equipment entry)

Required Fields (per item)

Source Object Fields (required)

Example

[
  {
    "equipment_id": "KRG-INV-001",
    "sources": [
      { "system": "ifs-cloud", "type": "erp", "native_id": "EQ-10045" },
      { "system": "sma-monitoring", "type": "monitoring", "native_id": "SMA-9801234" },
      { "system": "site-scada", "type": "scada", "native_id": "INV-001-SCADA" }
    ]
  }
]

Equipment Register

Equipment hierarchy and technical attributes for a single piece of site equipment, sourced from ERP/EAM systems.

Required Fields

equipment_type values: site, array, inverter, combiner, string, module, transformer, tracker, meter

Optional Fields

Example

{
  "equipment_id": "KRG-INV-002",
  "site_id": "KARIEGA-SOLAR",
  "equipment_type": "inverter",
  "equipment_subtype": "string_inverter",
  "parent_equipment_id": "KRG-ARR-A",
  "source_equipment_id": "EQ-10046",
  "manufacturer": "SMA",
  "model": "Sunny Tripower 25000TL",
  "serial_number": "SMA-9801235",
  "install_date": "2023-06-15",
  "warranty_expiry": "2028-06-15",
  "design_capacity_kw": 25.0,
  "cost_center": "CC-KRG-SOLAR"
}

Maintenance History

Work order record capturing corrective, preventive, or condition-based maintenance activity on a piece of equipment.

Required Fields

Optional Fields

Example

{
  "equipment_id": "KRG-INV-002",
  "work_order_id": "WO-2026-0142",
  "wo_type": "corrective",
  "wo_status": "closed",
  "reported_date": "2026-01-15T08:30:00Z",
  "completed_date": "2026-01-15T14:45:00Z",
  "downtime_hours": 6.25,
  "failure_code": "GRID_FAULT",
  "cause_code": "FUSE_BLOWN",
  "total_cost": 1250.00,
  "parts_consumed": [
    { "part_id": "SP-FUSE-60A", "qty": 2 }
  ]
}

Spare Parts

Spare part inventory record including stock levels, reorder thresholds, and equipment applicability.

Required Fields

Optional Fields

Example

{
  "part_id": "SP-FUSE-60A",
  "description": "60A DC string fuse, 1000V",
  "equipment_types_served": ["inverter", "combiner"],
  "qty_on_hand": 24,
  "qty_reserved": 4,
  "qty_available": 20,
  "reorder_point": 10,
  "supplier_lead_time_days": 14,
  "last_unit_cost": 18.50
}

Procurement Context

Procurement and supply chain context for a spare part, including preferred supplier, lead times, and open purchase orders.

Required Fields

Optional Fields

Example

{
  "part_id": "SP-FUSE-60A",
  "preferred_supplier": "Phoenix Contact SA",
  "avg_lead_time_days": 12,
  "avg_unit_cost": 17.80,
  "last_po_date": "2026-01-20",
  "open_po_qty": 50,
  "open_po_eta": "2026-02-10"
}

Failure Taxonomy

Failure and root cause classification record from the ERP/EAM failure coding system, including historical repair statistics.

Required Fields

Optional Fields

Example

{
  "failure_code": "GRID_FAULT",
  "failure_description": "Grid voltage or frequency excursion causing inverter trip",
  "cause_code": "FUSE_BLOWN",
  "cause_description": "DC string fuse failure due to thermal cycling",
  "recurrence_rate": 0.35,
  "typical_mttr_hours": 4.5,
  "typical_cost": 1200.00
}

Alarm Frequency Profile

Derived alarm frequency analytics for a specific equipment-alarm pair, computed from SCADA alarm logs enriched with maintenance context. This schema is not extracted directly from any ERP — it is a derived computation. See the alarm frequency computation spec for the full algorithm.

Required Fields

Optional Fields

Example

{
  "equipment_id": "KRG-INV-002",
  "alarm_code": "GRID_FAULT_UV",
  "source_equipment_id": "INV-002-SCADA",
  "count_7d": 12,
  "count_30d": 18,
  "count_90d": 25,
  "mean_time_between_alarms_hours": 86.4,
  "escalation_rate": 2.86,
  "prior_wo_count_same_alarm": 2,
  "prior_resolution": "recurring"
}

The escalation_rate of 2.86 means this alarm is firing nearly 3x faster in the last 7 days compared to the 30-day baseline — a strong signal for dispatch priority.

IFS Cloud Reference Implementation

The first reference transform maps IFS Cloud OData projections to ODS-E enrichment schemas. See erp-transforms/ifs-cloud.yaml for the full specification.

The alarm frequency profile is not extracted from IFS — it is a derived computation that joins SCADA alarm logs with ERP maintenance history. The equipment ID map is maintained as a configuration artifact, not extracted.

Cross-Schema Relationships

Three linking keys connect the seven schemas:

Common Query Patterns

1. Alarm triage — Start from an alarm frequency profile, join maintenance history on equipment_id, check failure taxonomy for recurrence rate, verify spare parts availability by part_id
2. Inventory optimization — Aggregate parts_consumed from maintenance history, compare against spare parts qty_on_hand and reorder_point, check procurement open_po_eta for incoming stock
3. Equipment risk scoring — Combine alarm escalation_rate, failure recurrence_rate, and maintenance downtime_hours per equipment to rank dispatch priority
4. Cascade analysis — Traverse parent_equipment_id in the equipment register to identify upstream/downstream equipment affected by a failure

Related Docs

• Schema Overview — Design principles and how to read the spec
• Energy Timeseries — Interval energy records
• Asset Metadata — Site and equipment context
• Maintenance Event Triage — Pattern using these schemas for O&M decision-making
• Schema Validation — Structural correctness checks