Capturing inspection results
The capture flow step by step: pick the released plan, operation and characteristic, record samples, and get instant in-spec or out-of-spec feedback.
Capture is direct measurement capture against released control plan context. It lives under VoraControl at /control/capture. You choose what was measured, enter the readings, and the result is judged instantly against the specification limits carried by the released plan.
Choosing what was measured
Start by picking the part and plan (only released plans are offered), then the operation, then the characteristic. As you narrow down, the context panel confirms the customer, part, operation and characteristic, and the entry screen shows the spec, the method, the gauge and the plan frequency as an instruction. Then choose Enter measurements to open the entry.
Traceability and samples
The inspection can carry optional traceability: shift, machine, job number, lot number and route reference. Enter each sample reading (with an optional comment per sample), then save. A measured value is compared to the tolerance; a pass or fail characteristic is judged by you at entry. Fill in every sample before saving.
Instant feedback and the Resolve hand-off
On save you see the result immediately: in spec, out of spec, or review required. An out-of-spec result raises a signal and hands off to Resolve, where the follow-up is reviewed, owned and closed alongside the measurement. Capture itself only shows the hand-off; the response workflow lives in Resolve.
History, corrections and voiding
The History register opens to a recent window (the last 90 days by default) and can be filtered further. Every record keeps an immutable snapshot of the plan context it was measured against: part, revision, characteristic and limits, exactly as released at the time. A submitted sample can be corrected with a required reason, and an inspection can be voided with a required reason; both leave the original values visible in the trail.
Capture is not a production schedule, a run tracker, an operator work list or a due engine. Nothing queues work or enforces frequency. The plan frequency you see on the entry screen is instruction-only context from the released plan; when to measure remains an operational decision on the floor.
Still stuck? Get support or contact the team. Support replies personally, typically within one business day.