OEE Configuration

Configuring OEE for an asset tells Rela what counts as good production, how long a shift lasts, how a micro-stop is measured and which event indicates a defect. Without this the platform can't distinguish a planned stop from one hitting availability.

What is it for?

• Translate the asset's operational reality into the 3 canonical OEE components.
• Pick the source events that feed each component (cycle, stop, defect).
• Define ideal cycle time and planned hours — the two pieces without which nothing can be calculated.

Prerequisites

Before configuring OEE you need:

• At least one asset created in Rela
• A connected event source that sends production data
• Know the ideal cycle time of your equipment (seconds per part)

Configure OEE for an asset

From the Dashboard

1. Go to Assets and select the equipment
2. In the edit section, enable OEE
3. Configure the parameters:

From the API

PATCH /api/v1/assets/{asset_id}
{
  "oee_enabled": true,
  "oee_config": {
    "ideal_cycle_time_seconds": 2.5,
    "planned_hours_per_shift": 8,
    "shifts_per_day": 2,
    "count_metric": "parts_count",
    "reject_metric": "rejected_count",
    "status_metric": "running",
    "status_running_value": true
  }
}

How Rela calculates each component

Availability

Rela automatically detects when the equipment is running or stopped based on the status metric:

• Operating time: Sum of periods where status_metric = running value
• Planned time: Planned hours per shift x shifts
• Downtime: Automatically classified as planned or unplanned if you have work orders registered

Performance

Calculated using parts count and ideal cycle time:

• Parts produced: Sum of the count_metric field in the period
• Ideal parts: Operating time / Ideal cycle time
• Performance: Parts produced / Ideal parts

Quality

Calculated using parts produced minus rejects:

• Good parts: Parts produced - Rejected parts
• Quality: Good parts / Parts produced

Calculation periods

OEE is calculated automatically for:

• Per shift: At the end of each shift
• Daily: At midnight (organization timezone)
• Weekly: Sunday at midnight
• Monthly: Last day of the month

Real-time data is updated each time a new event arrives.

Required events

Your event source must send at least:

{
  "parts_count": 150,
  "rejected_count": 3,
  "running": true,
  "timestamp": "2026-03-30T14:30:00Z"
}

The recommended frequency is every 1-5 minutes for good calculation granularity.

Key benefits

• A single config feeds Availability + Performance + Quality — no triple mapping.
• Reuses the same event_source already feeding the predictive pipeline — no duplication.
• Per-asset ideal cycle time — supports plants with heterogeneous equipment.
• Reconfigurable events without rebuilding the asset every layout change.
• Configurable granularity (1-5 min) for precision-vs-volume trade-off.