The procedure carries a risk analysis and a review
Four separate documents or one that grows as the test goes: the organization's choice
What Each One Owes the Last
Figure 1.9. Requirement, procedure, result, report, and what each one owes the last. The review sits on the procedure with the risk analysis feeding it. The dashed loop from the report back to the requirement is labeled "next program's heritage."
The Requirement: What to Prove, and What Good Is
The step, the purpose, the profile, the standard
Pass is a definition, not a feeling
Profile within tolerance for the duration; functional checks named, before, during and after
No visible damage, with the inspection named; signature surveys agree within a stated shift, if called for
Which deviations are acceptable without a re-run
The Procedure: How, and Where Safety Lives
Which machine, fixture and channels, which one controls, the limits and aborts, who signs
Where the standard's silence gets filled
What the article is, and what happens if it comes off the fixture
Who stands where, the exclusion zone, which interlocks protect people
Who has the authority to stop the test
The Risk Analysis
Written before the review, by the procedure's author; usually a page
Risks to people, to the article, to the machine, to the program
Each one: likelihood, consequence, what the procedure does, who accepts the residual risk
The review reads the risk analysis first and the procedure second
The Result and the Report
The result is the data and the log, not the controller's end-of-test summary
The report is the argument that the result proves the requirement
It carries the requirement and its pass definition, the procedure as run, the result, and every deviation
It is the only one of the four anyone reads a year later
Deviations and Witnesses
No test runs exactly to its plan: notch, limit, abort, restart, level change
Each one is recorded when it happens, with who decided and why
A deviation recorded on the day is a fact; one reconstructed a week later is a story
Settle witnesses before the low-level run: who watches, who signs, what they need to see
Three Ideas for the Volume
A test is a partnership: the designers, the lab, the customer, the analyst
Who does what is decided before the test, or badly on the day
The record, photographs included, settles the argument a year later
Decide
If a step cannot be written down, it cannot be defended
The log header opens before the low-level run: purpose, profile source, standard, configuration, who is in the room
No pass definition in the requirement: the procedure writes one, and the customer agrees before the low-level run
The procedure and risk analysis are reviewed by someone other than the author before mounting, risk analysis first
This page is part of the KCSC Training course and is licensed to one named reader for viewing. It does not print. Lab kit pages print from the Lab Kit menu.