Table Design question
I'm working on a production recording database for our plant.
One of the metrics I need to measure is downtime. Downtime
can fall into 3 different buckets:
1) Unplanned - Related to the production run
2) Unplanned - Not related to the production run
3) Planned - Not related to the production run
Unplanned could be a mechanical breakdown, while planned would be
something like a safety meeting.
Production runs are supplied a unique run number, so some of my downtime will be assigned to a run number, and some of it won't.
I'm thinking of a table like this:
RunNumber (allow nulls)
Where date, shift, and reason code would be composite key.
For some reason I feel like I'm missing something, though. Does anyone
see a better way to do it?
Inspiration Through Fermentation