Work Order Variance
Planned vs. actual quantity, time, and cost per work order; highlights scrap rate and labor efficiency.
Implementation
How a plant goes live: mapping the operating model, configuring, migrating, rehearsing, and launching one process at a time.
The authored specification is the starting point for configuring the application in the ERP.ai engine. Agree the plant’s scope, build any required extensions and rehearse the process before cutover. The schedule follows the data, integration and acceptance work identified during that review.
Implementation phases
- Map the operating modelPlant and ERP.ai
- Configure and load master dataApprover
- Rehearse real scenariosPlant and ERP.ai
- Load opening balancesPlant and ERP.ai
- Go live by processPlant and ERP.ai
- Stabilise and extendPlant and ERP.ai
Phase 1 · Plant and ERP.ai
Map the operating model
Products and product families, plants and warehouses, work centres and shifts, item policies (make or buy, lot sizing, lead times), approval thresholds, quality gates, cost method, chart of accounts and dimensions. This is a workshop and a spreadsheet, and it becomes configuration.
| Field | Type | Required | Definition / allowed values |
|---|---|---|---|
| WorkCenterCode | text | Yes | — |
| Description | text | Yes | — |
| Department | reference | Yes | → Departments |
| Supervisor | reference | No | → Employees |
| CapacityHoursPerDay | number | Yes | — |
| EfficiencyPercent | number | Yes | 0–100, default 85 |
| HourlyRate | currency | Yes | Labor + overhead burden |
| Active | toggle | Yes | — |
Phase 2 · Approver
Configure and load master data
Create the application from the reviewed specification, configure roles and workflow thresholds, and verify the document conflicts for Approver. Then load items, bills, routings, suppliers and customer contacts in the migration order on the data model page. Reconcile record totals and inspect representative references before loading open transactions.
| Role | Screens |
|---|---|
| Production Planner | 8 |
| Shop Floor Supervisor | 6 |
| Buyer | 4 |
| Quality Inspector | 2 |
| Accountant | 2 |
| Operator | 1 |
| Approver | 1 |
Role permissionsRoles and permissions →
Phase 3 · Plant and ERP.ai
Rehearse real scenarios
A normal week: orders in, MRP, releases, receipts, production, shipments, close. Then the exceptions: a short part, a failed inspection, a change order, a returned lot. Each role runs their own steps.
Phase 4 · Plant and ERP.ai
Load opening balances
Stock by lot, open orders in their current status, ledger balances by account, reconciled to the old system on the cutover date.
Approval conditions
Visible to: Accountant. Visibility does not establish approval authority.
Draft
- JE-33179 Issue to WIP 14 d
- JE-30548 Completion at standard 4 d
- JE-69432 Goods receipt 12 d
- JE-11285 Scrap 10 d
- JE-29785 Bill match 14 d
JE-33179
- Date
- 03 Sep
- Description
- Issue to WIP
- TotalDebit
- 11,718.45
- TotalCredit
- 11,718.45
- ReferenceType
- StockMovement
Approval conditions.
Phase 5 · Plant and ERP.ai
Go live by process
Usually purchasing and inventory first, then planning and production, then finance close. Each process goes live when its rehearsal passed, and the previous system is retired for that process only.
Phase 6 · Plant and ERP.ai
Stabilise and extend
Standards corrected from the first variances, reports tuned, integrations switched on one by one.
A process owner per area, the data extracts, decisions on thresholds and policies, and time for rehearsal. Customer and implementation team agree who configures extensions, validates integrations and signs off each process.
Fields, rules, approval steps and whole modules are changed with Proto, on a branch, reviewed, released. The implementation never ends with a frozen system.
1
Say what you need"Add a second approval above 10,000." Plain language.
2
Review the branchThe change lands on a branch with the diff and a test run.
3
ReleaseMerged into your workspace. Every user gets it.