Downtime log template

Download the Downtime log template (CSV). Opens in spreadsheet applications; no email or signup required. Fields and an explicitly labeled example row are included. Replace the example before use.

Use one row per observed event. Keep the original event ID when correcting a cause. Start and end timestamps should include an explicit offset; calculated duration must match them. The example row is illustrative and should be removed from a live log.

FIG. 03At the inspection gate

Define the boundary first

Agree what counts as downtime, the microstop threshold, the line or asset boundary, and whether planned setup is included. Keep automatic stop detection separate from the operator's symptom and maintenance's confirmed cause. Leave unknown causes visible until investigated.

Review the record

Reconcile run time and stopped time against planned production time. Overlapping machine stops cannot simply be summed into line downtime. Build separate frequency and duration views, then assign an owner and an observable action to the leading cause.

Use with

• Downtime Pareto and reason codes
• Downtime cost calculator
• OEE loss tree

Included fields

event_id, asset_id, product_or_order, start_iso8601, end_iso8601, duration_minutes, initial_reason, confirmed_cause, owner, action, verification, status.