Opening the book…
A process boundary identifies where the selected process begins and ends. Without clear boundaries, one team member may study the time needed to run a test while another measures the time from sample collection to final approval. Both measurements can be correct, but they answer different questions.
For the enzyme company, the selected process starts when QC first receives a submitted sample. It normally ends when QC issues a reviewed report to the authorized decision maker. If testing cannot proceed and the submission is formally closed under the applicable procedure, it ends with a documented closure notice. This boundary includes intake problems and waiting for missing information. Product release and shipping remain outside the map, although they use its outputs.
A requirement states a condition that an input, activity, or output must meet. A specification defines an established requirement or set of requirements, often including acceptance limits. A sample requirement might identify the needed amount, label information, container, and storage conditions. A report requirement might identify the batch, method version, results, and review status.
Requirements should be clear enough to check. “Send the sample promptly” leaves room for disagreement. “Record the collection and receipt times and deliver within the interval defined by the approved method” provides a clearer expectation. The actual interval must come from the applicable method or justified procedure. It should not be invented to make a diagram look complete.
When defining requirements, identify their source. Customer agreements, scientific evidence, internal procedures, and applicable regulations may all contribute. Distinguish a justified acceptance requirement from an improvement target. A report-turnaround target does not authorize shortcuts in identification, testing, or review.
Boundaries limit the investigation, but they should not prevent the team from examining important outside influences. If a report is late because samples repeatedly arrive without labels, the team needs to involve the sample supplier. Mark the connection and coordinate the response rather than silently expanding the project to cover the whole company.
This page titled 5.4: Defining process boundaries and requirements was last modified on Fri, 06 Nov 2026 11:28:28 GMT and is shared under a CC BY-SA 4.0 license and was authored, remixed, and/or curated by .
The book could not be loaded just now.