Building a control plan

A control plan in VoraControl is generated from your source data rather than typed out as a document. The Plan library at /control/plan/library shows one row per plan or plan-ready part revision; from there you generate revisions, export the printable plan, attach the signed approval and open the revision history.

The operation spine

The plan is structured along the operations recorded for the part revision, in sequence order. Each operation carries the characteristics linked to it on the Characteristics page, with their class, tolerance, method and gauge. When source operations and characteristics are in place for a part revision, the library row shows a Needs generation status with a Generate button.

Sample rules

Plan rules, at /control/plan/rules, hold the sampling standards applied when a plan is generated. A standard set contains rules keyed on characteristic class, each with a sample frequency (chosen from a fixed list such as Each setup, Hourly, Every shift or 100% inspection), a sample size and an optional reaction plan text, plus a fallback default rule. One set is the default for generation, and sets can be duplicated and adjusted.

Generating and regenerating

Generate builds a control plan revision from the current source data and releases it. When the source data changes later (a new characteristic, a tolerance update, a new operation), regenerate the plan: a new revision is created and the previous one is superseded and kept in history. Combined plans covering a part set are marked with a Combined chip and behave the same way.

Export and the signed approval

Export / Print opens the formal printable control plan for the current revision. The signed, approved document usually comes back after review, so it is attached as a separate step: Upload approval accepts a PDF, PNG or JPG up to 15 MB and stores it as governed evidence against the revision. Once attached, the row shows Approval on file, and the document appears on the export header and in audit evidence.