Engineering changes

A substituted component or revised assembly requirement needs a reason people can inspect. An engineering change request connects that reason to a revision, requester and approver. Request date provides request timing. Status distinguishes Draft, Review, Approved, Rejected and Implemented, so the team can separate a request from the decision and from the work needed to apply it.

The change workflow resolves the revision, requester and approver and requires a recorded reason before moving Draft to Review once. It does not approve the change. The approver reference identifies the intended deciding person, while the approval action itself needs a permission and an actual human decision. Manager owns the engineering decision.

• Requested scope. Select the revision under discussion and explain the change in the reason. The revision’s product and status show parent context for the reviewer.
• Accountable people. Select the requester and approver from people records linked to their user accounts. A similarly named person or a role title typed into reason cannot replace the intended reference.
• Decision and application. Submit to Review, decide Approved or Rejected, and use Implemented only after the agreed change has actually been applied. The submission workflow stops at Review and cannot establish the later outcomes.

During setup, configure approval and rejection actions for the person acting as Manager, plus the planner’s implementation update. Agree what the reviewer inspects in the revision and component lines before deciding. Keep signed design documents in the engineering source your team uses, and agree how the requester directs the reviewer to the applicable instructions. Rehearse an accepted change and a rejected request with that person.

Configure My engineering requests using the requester’s linked user account. Test it with different people and confirm that direct record access follows the same assigned scope. A current-user filter helps a requester find work; it must not grant permission to approve that work or reveal another person’s restricted requests.

Use a demonstration request to replace a component on an assembly. Production Planner records the target revision, explains the reason and names the deciding person. Try submission without reason and with an unresolved approver reference. The workflow should reject those cases, leaving no successful Review transition to imply that the packet is complete.

With the references resolved, submit the request and verify Review. Ask Manager to reject one request and approve a corrected request through the decision actions. Check that an operator cannot make those decisions with ordinary production access. When applying the accepted change, prepare an editable revision, keep the old released structure available and set Implemented only after the planner can show what changed. Include a work order already underway and discuss its instructions separately, so its operator receives the instructions agreed for that run.

• Engineering review — Submitted requests with reason and deciding person visible.
• My engineering requests — Requests belonging to the authenticated requester.
• Approved change follow-up — Decisions awaiting their agreed implementation work.

Engineering change review covers the decision. Continue with revision preparation and release, and rehearse access using roles.