Runtime Status

Runtime status is the live operational state of an asset — Running, Setup, Idle, Down, Maintenance. It's the single most-checked datapoint in the whole Equipment suite: the Equipment Hub status board, work-center rollup, capacity calculation, and KPIs all read from it.

This page covers how the value changes (operator action, work-order operations, automatic maintenance updates), how it rolls up from a machine to its work center, and the permission tier designed specifically for floor operators.

The five states

When a parent asset or work center rolls up the status of its children, the worst status wins: Down outranks Maintenance, which outranks Setup, which outranks Idle, which outranks Running. So a single Down child brings the whole rollup to Down, while one child in Setup does not.

How status gets set

1. Operator action (the status chip's menu)

The fastest path. Available wherever an asset's status chip appears — the Equipment Hub status board, and the Equipment Detail page header.

The menu shows all five states. Picking Down opens an inline reason prompt — the text is recorded automatically as a breakdown event, so the context isn't lost in the moment you flip the chip.

Flipping the status requires a separate, lighter permission from editing the asset's own record — a floor operator can be granted the ability to mark equipment Down without also being able to edit its accounting fields.

2. Maintenance events

Starting a maintenance event automatically flips the asset to Maintenance, remembering whatever status it was in before. Completing or cancelling the event restores that prior status (typically Running or Idle). You never need to manually flip the chip before starting planned maintenance — starting the event does it for you.

3. Work-order operations

When a routing operation starts on an asset's work center, the system can flip the asset to Running (or Setup for the setup phase) if it was previously Idle, and back to Idle when the operation completes. This is an opt-in behavior per company — shops that don't want automatic status changes on every operation start/end can leave it off and use the status chip's menu instead.

4. Background rollups

Every few minutes, the system recomputes two things: a parent asset's status from the worst of its children, and a work center's status from the machines flagged as critical to it. These passes never change a leaf machine's own status — only the derived rollups on parents and work centers. The leaf status only ever comes from an operator, a maintenance event, or a work-order operation.

How status propagates

A leaf machine's status rolls up through any sub-assembly above it, then up to the machine's work center, and from there to the Equipment Hub status board and the Capacity Planner. Every step updates live — no page refresh needed.

A non-critical asset's downtime stops at the asset level; it does not bubble up to its work center. This is the lever that decides which assets are line-stopping and which are bypassable — mark an asset critical to its work center only when its downtime should actually stop that work center's capacity.

The status chip menu

• Click the chip's menu icon to open it.
• The current state is highlighted.
• A reason prompt appears only for Down — optional, but recommended, since it's what creates the breakdown event automatically.
• A brief toast confirms the change (e.g., "Heidelberg Press 1 → Down").
• The chip pulses in its new color for a couple of seconds after the change, visible to everyone watching the same board.

Permission tiers

The split exists so an operator can mark equipment Down without also being able to change its acquisition cost or dispose of it, and a maintenance lead can log events and flip status without accounting access. Only finance or admin roles typically get full asset-editing rights. The Equipment Detail page shows all the relevant actions but disables the ones a user isn't granted.

Recipes

Tablet operator workflow when a press jams

1. The operator opens the status menu on the press's chip.
2. Picks Down → types "feeder jam" as the reason.
3. The asset flips to Down, the chip pulses red, and the work center rolls up to Down — everyone watching the status board sees it update instantly.
4. A breakdown maintenance event is created automatically with the reason attached.
5. The maintenance lead sees the alert and responds.
6. After fixing it, they open the event from the Maintenance Hub, fill in when it ended and what parts were used, and mark it Complete.
7. The asset automatically returns to its prior status (Running), the chip pulses green, and the work center rolls up accordingly.

Taking a press down for planned maintenance

Don't manually flip the chip to Maintenance first. Instead:

1. Open the planned maintenance event (auto-created on schedule, or create one manually).
2. Press Start on the event.
3. The asset flips to Maintenance automatically, and the work center rolls up.
4. On Complete, the asset restores to its prior status.

This way the downtime is captured on the maintenance event itself, not just in an audit trail.

Troubleshooting

Related

• Asset Management — where runtime status lives on the asset record
• Work Centers for CAPA — what "critical for capacity" and the rollup mean
• Maintenance Events — how planned and unplanned events change status
• Permissions — the three-tier permission model