Production evidence

Each production log records start date, end date, good units and scrap units against the work order and operator. The operator links to a staff record and its authenticated platform account. The record lets the team explain which work produced an interval result and who submitted it without accepting a typed operator name as identity.

Production Operator ends an interval through the production interval action for a work order in Released or In progress. The action requires end date after start date and nonnegative output values. It rejects a repeated interval or a repeated log name. The production action creates the batch identity here; the planner’s earlier release does not create it.

The saved interval is evidence used by the quality release checks. It also supports an operational output review by work order and operator. Shift evidence remains the separate shift population linked to a production target, so the same production must not be added from both sources into a headline total.

• Eligible work. Check the exact work order reference and its Released or In progress lifecycle state.
• Resolved operator. The production interval action validates the actor through the staff record’s linked user account and saves the linked operator from that resolution.
• Completed interval. Require ordered interval boundaries and valid output values before the log becomes usable evidence.

Map active staff records to their user accounts and test the actor resolution using ordinary operator sessions. Define how the My production logs filter resolves the authenticated user to the corresponding staff record. Never compare display names or trust an operator reference provided by the caller to expand access.

Agree the stored precision and timezone of start date and end date with the pilot team. Rehearse the stored boundaries with the operator and confirm that the returned interval matches the work they completed. Agree which production review uses these quantities, and keep that population distinct from the shift summary.

An operator completes work on an eligible released instruction. They submit the interval boundaries with good and scrap quantities through the production interval action, then inspect the saved work order and resolved operator. Quality Reviewer follows that completed evidence when reviewing the linked batch.

Try an interval whose end precedes its start. The action must reject it before usable production evidence is saved. Repeat with a negative good-unit value and then a negative scrap value. Rejection should preserve the prior records so the team can correct the inputs without rewriting accepted evidence.

Resubmit the successful interval and try reusing its log name. Confirm the duplicate checks prevent another production result. Then sign in as another operator and check the configured personal view. Identity mapping should constrain the result to that person’s authorized work; a filter is useful presentation, while server permissions enforce access.

Configure the evidence views around the acting person’s scope:

• My production logs — Let Production Operator review their own completed intervals using the staff record linked to their signed-in account.
• Production interval history — Let planning and quality accounts inspect the work order, operator and reported quantities.
• Work order board — Follow the recorded lifecycle without assuming that a log alone completes the order.

Use material issue to production log for capture rehearsal and batch evidence to release for the quality handoff. Review identity controls under roles.