UNUS London  —  Compliance Architecture Division  |  UNCLASSIFIED // REGULATED INDUSTRIES
Home Solutions Legal & Professional Financial Services Manufacturing Healthcare Academy Blogs Ebooks About Book Discovery Call UNUS Govern
05
🏭 Manufacturing & Engineering
← View All Solutions

Downtime Data. OEE Calculated. Root Causes Evidenced.

The Equipment Downtime and Root Cause Log captures every unplanned downtime event, calculates OEE (Overall Equipment Effectiveness) in real-time, and enables Pareto analysis of root causes — giving you the data to make the continual improvement argument that ISO 9001 §10.1 requires.

The Problem This Solves
Downtime events are recorded in shift logbooks or verbal handovers with no structured root cause taxonomy, no OEE calculation, and no ability to identify whether the same root cause is recurring. ISO 9001 continual improvement requirements cannot be evidenced.
Regulatory Basis
ISO 9001:2015, §10.1 · ISO 9001:2015, §9.1
ISO 9001 §10.1 requires organisations to improve processes based on analysis of data. §9.1 requires monitoring, measurement, analysis, and evaluation of process performance. Downtime data is the primary performance input.
🏭 Manufacturing & Engineering
MS 05
Equipment Downtime & Root Cause Log
£1,397
ONE-TIME · FULL CODE OWNERSHIP · NO LICENCE FEE
Production-ready PostgreSQL schema
n8n automation workflow (JSON export)
HTML / JavaScript frontend
Immutable audit trail built in
Build guide — step-by-step setup
Sub-30-second evidence retrieval
ISO 9001:2015, §10.1 aligned
Delivered and live within 14 days or money back

Six Production-Ready Deliverables

Every component is built, tested, and transferred to you on day one of deployment. No dependencies. No ongoing licence fees. Full code ownership from the moment it goes live.

🗄️
downtime_events table
Core table: event_id, equipment_id, start_time, end_time, downtime_minutes, downtime_type (breakdown/setup/changeover/maintenance/quality), production_lost_units.
🔍
root_cause_log table
Root cause records: cause_category (mechanical/electrical/operator/material/process/external), cause_description, immediate_action, corrective_action_raised, ncr_reference.
📊
vw_oee_by_equipment
OEE view: calculates Availability × Performance × Quality for each equipment item by period. Sub-scores displayed alongside composite OEE. World-class threshold (85%) flagged.
📉
vw_downtime_pareto
Pareto view: downtime events ranked by duration and frequency by root cause category. Top three root causes responsible for 80% of downtime highlighted for management review input.
⏱️
MTTR Calculation
Mean Time To Repair calculated per equipment item and per downtime_type. Trend view shows MTTR direction (improving/stable/deteriorating) over rolling 13-week period.
🔗
NCR Auto-Link
Trigger fires when a downtime event exceeds the defined threshold (default: 4 hours). Automatically creates an NCR record in the NCR Tracker (MS 02) and links the event_id.

Built to Run. Not to Demo.

Every UNUS London mini solution is a production system — not a prototype. The schema runs on PostgreSQL 17.4 with full referential integrity, Row-Level Security, and an immutable audit trail from day one. The n8n workflow handles every user interaction end-to-end.

The evidence view below is representative of the live data structure you will have in your system. Every record shown reflects the actual column names, data types, and status logic in the deployed schema.

DatabasePostgreSQL 17.4 (Supabase)
Tables2 (downtime_events, root_cause_log)
Views3 (oee_by_equipment, downtime_pareto, mttr_trend)
OEE CalculationReal-time via database view
StandardISO 9001:2015 §10.1 · §9.1
NCR Auto-LinkEvents > 4 hours (configurable)
Code Ownership100% — transferred Day 1
Live Compliance Report
Equipment Downtime & Root Cause Log
CNC-Mill-01OEE: 88.4%A: 94.1% · P: 96.2% · Q: 97.7%
Lathe-03OEE: 74.2%⚠ Below 85% — Mechanical: 62% of downtime
Press-02OEE: 91.3%✓ Above world-class threshold
CMM-01OEE: 99.1%✓ Measurement system — no production loss

Get the Equipment Downtime & Root Cause Log
live in your firm.

A 30-minute discovery call is enough to scope this system for your firm, walk through the schema live, and confirm the delivery timeline. No obligation. A genuine technical conversation.