Original practice scenario: A hypothetical field technician records a repair and spare-part usage without connectivity. Another team changes the work order before synchronization. Design conflict handling.
Read model answer +
Keep technician observations separate from centrally authorized work-order state. Offline entry should preserve useful evidence without silently overwriting changes that the technician could not have seen.
Work through it
Assign stable work-order, task and local-operation identities, recording the version viewed by the technician and the time of each observation.
Merge independent observations where valid, but route conflicting task closure, replacement or quantity decisions through an explicit review state.
Reconcile spare-part consumption and work completion idempotently, retaining the source operation and any later correction rather than replaying the same offline action twice.
Tradeoffs to discuss
Local capture improves field continuity but delays conflict discovery; strict online authorization reduces ambiguity while limiting offline usefulness.
Common pitfalls
A successful sync acknowledgment must distinguish stored evidence from approved completion.
Device clock time is not enough to decide whose edit should win when teams worked concurrently.
Original practice scenario: A hypothetical fleet dashboard divides accumulated operating hours by calendar time. Machines have meter replacements, missing readings and different scheduled availability. Define a reliable calculation.
Read model answer +
Define utilization relative to an explicit availability denominator and preserve meter generations. Raw counter differences can cross replacements or observation gaps and do not automatically describe continuous operation.
Work through it
Partition readings by equipment and meter generation, deduplicate observations and calculate valid consecutive increments with event-time ordering and reset checks.
Allocate increments to supported reporting intervals under a stated assumption, flagging gaps too large for defensible allocation instead of inventing detailed activity.
Compare observed operating hours with scheduled available hours, separating maintenance, unscheduled downtime and unknown coverage at the intended fleet grain.
Tradeoffs to discuss
Coarse intervals reduce interpolation assumptions but hide short idle periods; fine-grained reporting needs correspondingly strong telemetry.
Common pitfalls
Do not allow utilization above the plausible interval without investigating counter or scheduling errors.
Calendar hours and scheduled productive hours answer different questions and must not be mixed silently.
