Engineering BOM and PLM release
Build the governed Requirements → CAD/PDM → EBOM → ECR/ECO → Manufacturing handoff thread. Each section retains exact source evidence and maker-checker decisions.
Screen orientation
Engineering authoring, configuration release and Quality verification are independently permissioned. Controlled sources are filtered by tenant/site/classification scope.
The numbered sections reflect the intended order. Open a section to create or revise a record, then use its action panel to submit, decide or release the exact version.
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 |
|---|---|---|---|---|
| Requirement ID / Requirement statement | Text | Required to create a requirement. | Use the controlled requirement identity and a clear verifiable statement. Do not use a document title in place of the requirement. | Creates a traceable design input. |
| Verification method / Acceptance criteria | Text | Required when defining requirement verification. | State how compliance will be proven and the measurable/pass condition before release. | Makes the requirement’s V&V expectation explicit. |
| Design record / Record type | Controlled document select and select | Required for CAD/PDM evidence. | Select the exact CLEAN controlled design version and classify its record type; do not upload an uncontrolled duplicate into this workflow. | Pins the design evidence in the PLM thread. |
| ECR number / Problem statement | Text | Required to open an engineering change request. | Use the controlled change identifier and describe the reason/defect without claiming a decision has already been made. | Creates the reviewable change request context. |
| ECO number / Impact summary | Text | Required when authoring an engineering change order. | State the approved implementation intent and cross-record impact. Use the specified effective date where required. | Creates controlled change execution evidence. |
| Released product source | Select | Required for Manufacturing handoff. | Select the exact released product/baseline source after all prerequisite PLM releases are complete. | Creates a pinned handoff source for Manufacturing; it cannot be edited by the receiving module. |
| Attributable note / Decision | Long text and select | Required for submit/review/release transitions. | Record the specific rationale and select the authorised decision. The original author cannot perform a required independent decision. | Adds immutable workflow evidence to the exact version. |
Actions and effects
When to use: When an engineering artefact needs controlled authoring or correction.
What it does: Creates a new version and preserves earlier released/draft evidence.
When to use: At the record’s current governed state.
What it does: Records attributable progression or independent approval/rejection; it does not change inventory.
When to use: Only after the exact PLM evidence is released.
What it does: Publishes the immutable source that Manufacturing may translate into an MBOM.
Lists and states
- Section registers show revision, source/evidence, status and author/decision attribution for each stage of the digital thread.
- EBOM lines express the as-designed structure; they are not a pick list or stock reservation.
Authority boundary
PLM releases as-designed authority. It does not create an MBOM, command a shop floor, issue material, post stock or make an independent Quality disposition.