๐Ÿ“– This is a static documentation page. Open the interactive version with live canvas demos โ†’

Control Plan

A Control Plan is a structured quality specification attached to an operation. It defines what to inspect, how to measure it, how often to sample, and what to do when a measurement falls outside limits. Every operation can carry multiple control plan items โ€” together they form the operation's quality gate.

Structure of a Control Plan Item

Each control plan item describes a single inspection checkpoint:

Basic Information

  • Code โ€” short identifier (e.g. CP-001) used to reference the item in reports and shop-floor documentation
  • Title โ€” localized description of what is being controlled
  • Physical Sense โ€” the physical dimension being measured: Dimension, Angle, Mass, Force, Torque, Temperature, Pressure, Voltage, Current, Resistance, Viscosity, Hardness, Roughness, or other
  • Unit โ€” measurement unit corresponding to the physical sense (mm, kg, Nยทm, ยฐC, etc.)
  • Document โ€” reference to the applicable specification or standard

Value Type

Each item specifies how the acceptable value is expressed:

  • Interval โ€” a nominal value with upper and lower bounds (e.g. 12.00 ยฑ 0.05 mm)
  • Deviation โ€” a nominal with asymmetric tolerances (e.g. 12.00 +0.02 / โˆ’0.01)
  • Range โ€” an acceptable band without a named nominal (e.g. 5.0 โ€ฆ 7.0)
  • List โ€” a set of discrete acceptable values (e.g. "Red", "Blue", "Green")
  • Boolean โ€” pass / fail check (e.g. "Surface defect present: Yes/No")

Sampling Strategy

Sampling defines how often the inspection is performed:

Sampling Frequency

  • Every N Pieces โ€” inspect every Nth unit (e.g. every 10th piece)
  • Per Shift โ€” inspect once per shift
  • Continuous โ€” inspect every unit
  • At Start โ€” inspect at the beginning of a run
  • Custom โ€” user-defined frequency with description

Sample Size

Specified as either:

  • Pieces โ€” absolute number (e.g. 5 pieces per check)
  • Percent โ€” relative to batch (e.g. 2% of batch)

First-Piece Check

A boolean flag that, when enabled, mandates inspection of the very first piece after setup or changeover โ€” regardless of the normal sampling frequency.

Rejection Number

The maximum number of non-conforming units in a sample before the batch is rejected. Follows standard acceptance sampling logic.


Evaluation Method

Describes how the measurement is performed:

  • Measuring Instrument โ€” caliper, micrometer, CMM, etc.
  • Visual Inspection โ€” trained operator assessment
  • Go/No-Go Gauge โ€” limit gauges for quick pass/fail
  • Functional Test โ€” operate the part to verify function
  • Checklist Audit โ€” structured checklist verification
  • Barcode Verification โ€” scan and compare to expected value
  • Statistical Analysis โ€” SPC chart evaluation
  • Simulation Model โ€” digital twin comparison

Each method carries a localized instruction note โ€” free text where the engineer explains the exact tools, setup, or procedure.


Reaction Plan

Defines what happens when a non-conformance is detected:

  • Stop Production โ€” halt the line immediately (boolean flag)
  • Notify โ€” send notification to one or more roles: Operator, Quality Inspector, Engineer, Production Manager, Shift Leader, Process Engineer, Maintenance
  • Recheck Quantity โ€” how many additional units to inspect
  • Rework โ€” whether rework is permitted for the defective unit
  • Escalation โ€” which role to escalate to if the problem persists
  • Note โ€” localized free-text instructions for the reaction procedure

Risk Assessment (FMEA)

Each control plan item includes a built-in FMEA (Failure Mode and Effects Analysis) block:

Failure Description

  • Failure Mode โ€” what can go wrong (e.g. "Diameter out of tolerance")
  • Cause โ€” why it happens (e.g. "Tool wear after 500 cycles")
  • Effect โ€” consequence if it reaches the customer (e.g. "Assembly interference")

Risk Scores

  • Severity (S) โ€” impact of the failure, 1โ€“10
  • Occurrence (O) โ€” likelihood of the failure, 1โ€“10
  • Detection (D) โ€” chance of detecting before shipment, 1โ€“10
  • RPN โ€” Risk Priority Number = S ร— O ร— D (legacy metric, kept for trending)

Action Priority

The primary decision metric โ€” replaces RPN for decision-making per AIAG/VDA 2019:

  • H โ€” High priority, immediate action required
  • M โ€” Medium priority, action planned
  • L โ€” Low priority, monitoring

The method can be set to AIAG_VDA_2019 or CUSTOM, with an optional rationale field for audit trail.


Traceability

Each control plan item tracks:

  • Responsible Role โ€” who is accountable for this inspection
  • Audit Flags โ€” markers for internal/external audit relevance

Revision History

Every change to a control plan item is logged with a timestamp and user identifier. This creates an audit trail showing when parameters were added, modified, or disabled.

Enabled/Disabled State

Control plan items can be toggled on and off. The state change history is preserved โ€” showing when an item was activated or deactivated and by whom.


Where Control Plans Live

Control plans are attached to Operations. Each operation has a `.core.cp` array containing all its control plan items. When the operation is saved, the control plan data is serialized and stored alongside the process data.

To add a control plan item, select an Operation and open the control plan section in the properties panel.