Incident Reason

oee reason glossary

An Incident Reason categorizes non-downtime issues logged against machines and/or stations. Incidents are notable events that don’t necessarily stop production (e.g., quality observations, safety near-misses) but need to be tracked for analysis.

Database Tables

`oee_incident_groups`

Column	Type	Description
`id`	UUID (PK)	Auto-generated
`site_id`	UUID (FK)	References Site
`name`	VARCHAR(100)	Group name (e.g., “Quality”, “Safety”, “Maintenance”)
`sort_order`	INTEGER	Display ordering

`oee_incident_reasons`

Column	Type	Description
`id`	UUID (PK)	Auto-generated
`group_id`	UUID (FK)	References `oee_incident_groups`
`code`	VARCHAR(50)	Reason code (e.g., “INC001”), unique per group
`name`	VARCHAR(255)	Reason name (e.g., “Surface Defect Observed”)
`description`	TEXT	Optional details
`is_active`	BOOLEAN	Whether reason is selectable
`sort_order`	INTEGER	Display ordering

Usage

Referenced by oee_machine_events.incident_reason_id when event_type = 'incident'
Incidents have additional tracking fields on oee_machine_events:
- troubleshooting_started_at/by — When investigation began
- troubleshooting_notes — Investigation details
- resolved_at/by — When resolved
- resolution_notes — How it was fixed

Codebase Paths

Tables: database/sql_scripts/tables/oee_incident_groups.sql, database/sql_scripts/tables/oee_incident_reasons.sql

See Also