Prepare a configuration from approved kit specifications. Gather component identities and aliases, quantities, permitted alternatives, serial or lot requirements, evidence policies and source field definitions. Do not use a barcode or a model proposal to infer engineering equivalence.
Define the requirement
Open Configuration and select the intended draft. Check the complete configuration using the available editor and its Configuration JSON when needed. Save a new revision after a considered change.
Give each component unique aliases. Exact leading zeros, case and spaces matter. Aliases cannot use the reserved KP1: namespace. Decide explicitly whether a component requires a part scan or may accept a part or bin scan. A printed bin card is not automatically acceptable evidence.
For each family, declare its finite option catalogue and slots. Set the default for every slot and use rule priorities deliberately. Equal-priority conflicting outcomes block resolution; a missing lookup result does not fall back to a lower-priority rule.
Set quantities per individual kit. Define alternatives and their approval requirements. Serialised requirements cannot permit manual counts. Declare lot capture separately where it is needed. Review tables and mappings so that each selected lookup has an exact, typed answer.
Validate meaningful failures
An unknown family, missing option, wrong type, conflicting rule, missing lookup or empty kit must be investigated. Do not add dummy components or permissive defaults simply to make the plan ready. Requirements above the supported bounds are refused rather than truncated.
When saving, resolve all reported field or location errors. If the draft changed in another session, reload and compare it. Do not overwrite unseen edits from an older tab.
Prepare independent cases
Write complete expected components, aliases, alternatives, quantities and policy flags from the approved specification. Include different unit options, required-field failures, alternative outcomes and lookup misses where the reachable table is incomplete. Mark the exact example version reviewed as a separate action.
Freeze the intended saved revision and follow proof and activation. The Supervisor should review the resulting stored plans for the first approved job before station use. A calculated ready plan remains expected contents until an Operator records the required evidence and completes the kit.
Choose how to prepare a condition
Select the intended family and rule, then use Build it yourself for a structured condition. Where Describe in words is enabled, enter When does this rule apply? and use Propose condition. The displayed limits apply to each request even if it fails. Review Applies when, the proposed condition and every diagnostic against the approved kit specification.
Only a current, latest, compiled proposal for the unchanged revision offers Accept into revision followed by the next revision number. Acceptance saves that new revision. If another author changes the draft, reload and review it; do not treat an old proposal as approval for the new content. Continue the normal examples, proof and review process.
Prepare bin cards from the correct release
Under Bin cards for CardBench, use Download bin cards for the active release. A candidate also has its own Bin cards download, so check which release your stations use before distributing a file.
The download is a local CardBench project file. Open CardBench, use Choose local file and replace the project with that file as the screen instructs. No automatic transfer or physical printing follows from the download. Each barcode uses the component's bin identity, not its part alias. Only a requirement permitting part or bin scans can count it, and the recorded evidence is a bin scan. Printing or scanning a location card does not itself prove that the part was picked.