Cross-module workflow
Plan to Production
A bill of materials becomes a work order; release is blocked on component shortage; every material issue and finished-goods receipt posts a real stock movement.
- 01
Trigger
- 02
Work
- 03
Govern
- 04
Outcome
What it is
Plan to Production is Vercentlabs ERP's real, cited sequence connecting Manufacturing and Stock — a released work order snapshots its bill of materials and cannot proceed without proven component availability, then posts real stock movements as it runs.
Execution sequence
- Steps
- 05
- Modules
- 02
- Approvals
- 01
The real sequence, step by step
The runbook shows trigger, participants, each module handoff, approvals, automated actions, exceptions, visibility and business value in one continuous operating document.
Trigger
An active bill of materials exists and a work order is created against it.
Participants
Production planner · Shop-floor supervisor · Work-center operator
- Activate the BOMManufacturing
One active bill of materials per item is enforced — there's no ambiguity about which structure a work order will snapshot from.
- Create the work orderManufacturing
Materials and operations are snapshotted from the active BOM and routing at creation time, not re-read live from a structure that could change mid-order.
- ReleaseManufacturing
Release is blocked if proven component availability can't be shown — a work order can't start against materials that aren't there.
- StartManufacturing
The work order moves to in-progress on the shop floor.
- Post productionManufacturing
Material issue and finished-goods receipt post as real, auditable stock movements in the same transaction as the production event.
Approvals
- 01A released work order cannot proceed without proven component availability — the closest thing to an approval gate in this workflow, enforced structurally rather than by sign-off.
Automated actions
- 01The release-blocking component-shortage check runs automatically, not as a manual pre-flight checklist.
- 02Every state transition writes to an event-sourced audit trail.
- 03Policy toggles control whether overproduction is allowed and whether component issue is manual or backflushed.
Exceptions & honest limits
- 01Overproduction is blocked by default unless an organisation's policy explicitly allows it.
- 02Material requirements planning runs are triggered manually — there's no background scheduler running them on a cadence today.
Visibility
- 01A single dashboard shows active, planned, and completed work order counts and live material shortages.
Business value
- 01A released work order cannot proceed without proven component availability — not a paper work-order tracker sitting beside a separately managed inventory.
- 02Every material issue and finished-goods receipt is a real, auditable stock movement, posted in the same transaction as the production event.
Handoff map
Every module involved, in operating order.
The workflow is deliberately shown as a chain of responsibility rather than a bag of features.
Buyer questions
Questions buyers ask about this runbook
Direct answers about how the sequence behaves, where controls sit and what a real deployment should expect.
What happens if a work order is released without enough raw material?
It can't be — release is blocked outright if proven component availability can't be shown against the snapshotted BOM. This isn't a warning a planner can dismiss; it's a hard gate.
Is capacity planning automatic, or does someone run it?
Material and capacity planning runs produce recommended purchase, manufacture, transfer, or expedite actions, but they're triggered manually today — there's no automatic scheduler running MRP on a cadence.
Can more than one bill of materials be active for the same item at once?
No — one active BOM per item is enforced, so a work order always snapshots from a single, unambiguous structure.