The category · Engineering assurance
Engineering assurance is the practice of validating engineering handoffs against the requirements, standards, specifications, drawings and data that govern them. In one line: checking whether the requirement survived.
The definition
Nothing in industrial engineering is built from one document. A governing requirement passes through sizing, engineering, the bill of materials, manufacturing and turnover, and at every handoff it is re-read, translated and re-entered by someone new.
Every document can be internally correct and still contradict the one before it. Engineering assurance is the discipline of checking that it did not.
Validating engineering handoffs against the requirements, standards, specifications, drawings and data that govern them.
Not whether the process ran, and not whether the document exists. Whether what it says still meets what was required.
Why it needed a name
Each is mature, widely deployed and good at its job. None of them reads the engineering content and measures it against the clause that governs it.
Captures requirements, versions them, allocates them to deliverables and holds the traceability matrix.
What it leavesIt is a record of intent. Whether the intent was honoured downstream is outside what it holds.
Route deliverables through review, hold the record of issue, and manage a nonconformance once it has been raised.
What it leavesThey manage a document's journey. What the document states is never measured against anything.
Pull values out of several documents at once and point at the ones that do not match.
What it leavesIt stops at the flagged conflict, without ruling on which requirement governs.
What makes it a practice
Any one of them alone is a feature. Together they are a category, and the reason the existing tools cannot simply add it.
Who it is for
The industries differ, the document names differ, and the failure is identical. Something was required, something was produced, and nobody checked the second against the first at the moment it mattered.
Read further
The category rests on two claims and three distinctions.
FAQ
Engineering assurance is the practice of validating engineering handoffs against the requirements, standards, specifications, drawings and data that govern them. It establishes that a deliverable meets what was required, rather than that a review process was followed.
Quality assurance asks whether the process was carried out correctly. Engineering assurance asks whether the content is correct against the documents that govern it. One deliverable can satisfy the procedure entirely and still breach the standard.
Compliance usually means meeting an external code or regulation. Engineering assurance works primarily against your own standards and project specifications, which are generally stricter and always more specific to the job.
The volume of engineering documents has grown faster than the number of people qualified to review them, and the senior judgement needed to rule on a finding does not scale by hiring.
Between them. Requirements tools hold what was asked for, document and quality systems govern the process around a deliverable, and engineering assurance checks the content of the deliverable against the requirement.
A finding for each check performed, carrying the verdict, the governing clause, the extracted fact and the evidence source, with a named engineer ruling on every one.
Next step
The argument is only worth as much as the findings. Bring a standard and a deliverable, and judge them.