Catalogue governance
Govern item control attributes, immutable item revisions, Assembly BOMs, typed specifications and managed serialized-instance definitions without creating stock.
Screen orientation
Catalogue, BOM, specification and managed-instance permissions apply with classification scope. Independent decisions remain server-enforced.
Select a catalogue identity to inspect stock context and revision history, prepare controls, govern a BOM/specification or register managed-instance lifecycle evidence.
Field reference
The entries below describe the current screen controls and read-only values. They do not relax server-side validation, site scope, classification handling or required independence in a governed decision.
| Field or value | Control | Required or shown when | How to use or read it | Result |
|---|---|---|---|---|
| Catalogue identity · Item | Select | Required for item-specific work. | Choose the stable item and exact revision context. | Scopes all following definition panels. |
| Category · Nature · Usage · Tracking · Precision | Controlled selects | Required for catalogue controls. | Set the definition rules that downstream records will enforce. | Updates draft definition controls only. |
| Human-confirmed revision code | Text | Required for a new immutable revision. | Enter the approved business revision; Moduvio assigns UUID and sequence. | Creates a separately addressable revision draft. |
| Review note | Long text | Required for an attributable catalogue decision. | Explain the exact definition review. | Becomes decision evidence. |
| Parent assembly · Revision · Output quantity · Effective from · Effective to · Notes | BOM header | Required as applicable. | Define one immutable Assembly BOM revision and effectivity. | Creates a definition with zero inventory effect. |
| Line · Component · Quantity · Entered UOM · Scrap % | BOM line controls | At least one complete component is required. | Pin exact component revisions and conversions. | Freezes component structure. |
| Category · Key · Label · Type · Required · Enum options | Specification template controls | Required according to type. | Define typed category metadata rather than free-form columns. | Creates the governed specification template. |
| Tool or asset item · Serial number · Asset code · Serviceability · Maintenance interval days | Managed-instance controls | Required as applicable. | Register a definition-side managed instance without asserting stock custody. | Creates lifecycle identity/context only. |
| Instance · Event · Occurred on · Reference · Holder · Next maintenance | Lifecycle event controls | Required according to event. | Record an attributable definition-side event. | Appends lifecycle history without moving stock. |
Actions and effects
When to use: For a draft item definition.
What it does: Updates the draft control contract; it creates no quantity.
When to use: When an approved definition changes.
What it does: Preserves the old revision and governs a separately addressable successor.
When to use: After exact parent/component revisions are selected.
What it does: Releases design structure only; Product Engineering must perform the later PLM handoff.
When to use: For managed definition evidence.
What it does: Creates managed-instance context without receiving, moving or issuing stock.
Lists and states
- Immutable item-revision register: sequence, business code, state, checksum and actors distinguish draft/current/superseded definitions.
- BOM and serialized-instance registers: show retained definition versions and lifecycle evidence, not physical balances.
Authority boundary
Catalogue governance owns definitions. It does not create stock, physical custody, receipt, inspection, EBOM/MBOM handoff, maintenance execution or ledger movements.