Workflow

Flow 11 — Product configuration and baseline release

Define a product family/model/variant, capture multidisciplinary configuration items, independently release an effectivity-controlled baseline and register a serialized product unit.

Overview

Inventory meaning

Every Engineering action in this preview is configuration-only. Approved items, released BOMs, CLEAN documents and existing physical instances are referenced; no receipt, reservation, issue, movement, balance or stock-ledger row is created.

Responsible roles

Product Engineer → different Configuration Manager → Product Engineer → Auditor

Process

1
Product hierarchy
Create site-scoped family, model and variant identities.
Product definition · Inventory: 0
2
Configuration items
Reference exact approved hardware, software, firmware, documents and interfaces.
As-designed sources · Inventory: 0
3
Baseline draft
Snapshot selected configuration and explicit effectivity.
Immutable draft · Inventory: 0
4
Independent release
A different Configuration Manager verifies and releases the snapshot.
Released design · Inventory: 0
5
Serialized product unit
Assign an effective baseline and optional existing physical assembly.
Configuration identity · no custody change
6
Designed vs built
Compare captured BOM identity without treating missing evidence as a match.
Read-only comparison
READ ONLY

Role handoff

Product Engineer → different Configuration Manager → Product Engineer → Auditor

Detailed reference chapters

Product configuration and released baselines Item catalogue modelling, review and assembly BOMs Controlled documents and evidence Serialized identities, physical containers and governed lot data

Detailed steps

1
As Product Engineer, open Engineering → Product configuration and create the product family at its design-owning site, followed by a model and variant. Confirm these are product definitions, not item or stock records.
2
Add configuration items. For hardware select the current approved item revision and, when applicable, its released BOM. For document configuration select the exact CLEAN controlled document version. Enter explicit identifiers and versions for software, firmware and interfaces.
3
Create a baseline draft for the selected variant, choose its configuration items, enter each hardware quantity per product unit in that item's base unit, and select ALL, DATE or SERIAL RANGE effectivity. Moduvio assigns the next version in that baseline lineage and snapshots the resolved source identities and quantities.
4
Submit the baseline. Confirm the originator cannot release it even if they hold approval permission, then sign in as a different Configuration Manager and verify the source records, immutable snapshot and effectivity before Release or Reject.
5
Register one serialized product unit. Assign only a released baseline that is effective for its serial/date. Optionally link an existing active physical assembly identity at the same site; this link must not move its stock.
6
Review As designed versus As built. BASELINE UNASSIGNED, PHYSICAL INSTANCE UNLINKED and AS BUILT UNAVAILABLE are explicit incomplete-evidence states; MATCH appears only when the captured completed-assembly BOM identity exists in the released baseline snapshot.
7
As Auditor, reconcile the baseline events, audit actors, outbox facts and current stock/stock ledger before and after the flow. They must remain unchanged.

Field-by-field practice data

Use a disposable training tenant

Create a training product family, model and variant, then draft a date-effective baseline. The page shows sample set A; the workbook includes independent A, B and C values.

Download all workflow samples (.xlsx)

Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.

Product Engineer

Create the product structure

Open /product-configuration

Create the family first, then its model and variant before adding configuration items and a baseline.

Exact field name	Requirement	Sample value A	How to use it
Design-owning site	Select existing	`COM-01`	Select the Engineering authority site.
Family code	Required	`TRAIN-A-UAV`	Use a unique product-family code.
Family name	Required	`Training unmanned aircraft A`	Use the controlled product-family name.
Classification	Required	`RESTRICTED`	Match the product definition sensitivity.
Purpose and scope	Required	`Training product configuration for controlled workflow practice.`	State the governed design scope.
Model code	Required	`TRAIN-A-UAV-M1`	Create under the training family.
Variant code	Required	`TRAIN-A-UAV-M1-V1`	Create under the training model.
Baseline number	Required	`TRAIN-A-BL-001`	Use a unique controlled baseline reference.
Quantity per product unit	Required	`1`	Enter a positive base-unit quantity for every hardware configuration item selected into the baseline.
Effectivity	Required	`DATE`	Choose the approved applicability mechanism.
Effective from	Required	`2026-10-01`	Use the authorised effective date.

Expected result: Definitions are versioned and remain zero-stock; a different Configuration Manager releases the baseline.

End state

One serialized product unit has an attributable released as-designed baseline and an honest comparison to available as-built evidence, with no inventory side effect.