17. Product configuration and released baselines
Create a governed as-designed product context and connect it to available as-built evidence without duplicating catalogue records or changing inventory.
Purpose
Create a governed as-designed product context and connect it to available as-built evidence without duplicating catalogue records or changing inventory.
Product Engineer, different Configuration Manager, Auditor
UAV-X family → UAV-X1 model → ISR variant; CI-HW-001 approved flight-vehicle item rev A / released BOM A; CI-DOC-001 specification v1; DESIGN baseline v1; product unit UAV-X-0001.
Before you begin
- Product Engineer and a different Configuration Manager have the same assigned design site and sufficient clearance
- Hardware items are active and catalogue-approved
- Any selected BOM is RELEASED
- Any selected document version is CLEAN and belongs to the product family's design site
PLM identity and authority boundaries
Family, model and variant describe the engineered end product. They do not replace part/item masters and contain no quantity.
References the current approved catalogue revision and optionally a released BOM belonging to that same hardware item. Moduvio stores the revision code in the CI and snapshots it again in each baseline.
Uses an explicit controlled reference and version, with an optional CLEAN document version as evidence. It is configuration metadata, not inventory.
References one exact immutable CLEAN controlled document version at the same design-owning site. A future document version does not rewrite a released baseline.
The baseline number identifies a lineage such as DESIGN. Each new draft receives the next version; release supersedes the prior released version in that lineage without rewriting it.
ALL applies to every unit; DATE requires an effective-from and optional effective-to; SERIAL RANGE requires inclusive product-unit serial limits. A product unit cannot be assigned an ineffective baseline.
The creator or submitter cannot release or reject the same baseline even if another assigned role grants approval permission.
The globally unique identity of one delivered or built end product. It is distinct from a component's OEM/internal serial aliases.
Optionally connects the product unit to an existing active assembly identity at the same site. The link never posts or changes custody.
MATCH requires an assigned released baseline, linked physical instance and completed assembly BOM identity present in the baseline. Missing baseline, link or captured build evidence stays explicit; a different BOM reports DIFFERENCE.
Engineering → Engineering BOM & PLM release consumes this released baseline for traced requirements/V&V, controlled CAD/PDM records, recursive EBOM, ECR/ECO and the independently released Manufacturing handoff.
Procedure
- 1
Build the family/model/variant hierarchy at the design-owning site.
- 2
Add multidisciplinary configuration items by selecting exact approved source records.
- 3
Create and submit an immutable effectivity-controlled baseline draft.
- 4
Have a different Configuration Manager release or reject it; confirm self-release fails.
- 5
Register a serialized product unit and optionally link a same-site physical assembly.
- 6
Review the explicit designed-versus-built comparison state and verify the stock register and ledger are unchanged.
Expected result
- Product definitions and baseline drafts create no inventory
- Family site and classification scope are enforced by the API
- Released baselines retain exact source snapshots
- Creator and submitter cannot decide their own baseline
- Only an effective released baseline can be assigned to a product unit
- A physical-instance link never moves custody
- Missing as-built evidence is never reported as MATCH
- Every create, submit and decision remains attributable and publishes a durable product-configuration fact