Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
The relationship between an incident and an order should be explicit. Retain order, operation, equipment and batch identifiers where available. One incident can affect several orders, while one order can experience several incidents. Do not copy the same lost time onto every relationship and later sum the copies as independent events.
Illustrative example
Illustrative example: a forty-minute breakdown interrupts two consecutive orders. Record one event and allocate the affected time using an explained rule. Each order view shows its impact, while the line total remains forty minutes rather than doubling to eighty simply because two links exist.
Acceptance check
Test rescheduled orders, incidents without a known order and corrected relationships. Preserve assignment history and distinguish association from confirmed causation. Accept the model when operational totals reconcile and users can navigate from an incident to its affected orders without losing the original evidence or counting it twice.
Key takeaways
- Accept the model when operational totals reconcile and users can navigate from an incident to its affected orders without losing the original evidence or counting it twice.