Skip to content
Operating model

Control plan

What is checked, how often, and what happens on a miss?

ProcessCharacteristicSpecificationSampleReaction
Machine the seat faceRev matchTraveler matches Rev C.every lotStop and call Mara Ellison on a mismatch.
Machine the seat faceRa sample32 µin Ra maximum.1 of 5Stop and call Priya Shah over 32 µin.
Confirm the shipmentDocknote and Ledgerline agreeDocknote and Ledgerline agree.before Helen Ward writes to Ruth AdeyemiHelen does not write to Ruth until they agree.
Checks, frequency, and reaction for the seat-face lot and for the shipment confirm.
How this sheet sits with the others

On every lot, Devon matches the traveler to Rev C and stops to call Mara if it does not match. He samples Ra on 1 of 5 and stops to call Priya if the reading is over 32 µin. At confirm, Docknote and Ledgerline have to agree before Helen writes to Ruth. The plan names the checks. It does not show that they were done.

What it makes visible
The rev check and the Ra sample on the machine, and the confirm check before Helen writes to Ruth.
When it is useful
When a failure mode needs a named check, a frequency, and a reaction.
Who uses it
Devon Cho on the rev and the sample. Priya Shah when Ra is over 32. Mara Ellison on a mismatch. Helen Ward when the confirm does not agree.
What it takes
The checks the plant already says it runs, and the reaction on a miss.
What it leaves
Rev match every lot, stop and call Mara on a mismatch. Ra sample of 1 of 5, stop and call Priya over 32 µin. Docknote and Ledgerline agree before Helen writes to Ruth.
The underlying record
Rev match and the Ra sample on the machined lot, the call to Mara Ellison or Priya Shah on a miss, and agreement between Docknote and Ledgerline before Helen Ward writes to Ruth are the checks the other response sheets expect.

Where these facts go next

What this sheet still leaves out

It has no proof the checks happened.