An accountable Shop Owner, the people who estimate and run work, representative source records and access to the systems being connected. Include drawings, travelers, stock and certificate evidence, open obligations and actual device requirements. The implementation scope should identify who validates each opening balance and operating decision.
Implementation
Bring the shop onto a reviewed operating plan, from quoting and travelers to the first reconciled close.
Start with the work that must be dependable on the floor. Timing depends on the shop’s data, devices, connections and chosen cutover scope.
Implementation phases
- Agree the operating rulesShop Owner
- Prepare masters and instructionsShop Supervisor
- Reconcile materialPlant and ERP.ai
- Prove the working pathPlant and ERP.ai
- Choose the cutoverPlant and ERP.ai
- Accept and supportShop Owner
Phase 1 · Shop Owner
Agree the operating rules
Map quoting, purchasing, job release, inspection and close to the people responsible. Review margin and purchase thresholds, permitted owner exceptions, rates, calendars and customer certificate requirements. Confirm the functional currency and tax/accounting ownership.
| Field | Type | Required | Definition / allowed values |
|---|---|---|---|
| WorkCenterCode | text | Yes | — |
| Description | text | Yes | — |
| WorkCenterType | select | Yes | Machine, Manual, Assembly, Inspection, Outside |
| MachineRate | decimal | Yes | USD per occupied machine hour, including approved setup, run and rework; rate/policy snapshot retained |
| LaborRate | decimal | Yes | USD per allocated labour hour; employee override only under policy and protected visibility |
| BurdenRate | decimal | Yes | USD per hour on the approved LaborHours or MachineHours burden basis |
| CapacityHoursPerDay | decimal | Yes | Summary only; actual available capacity comes from WorkResources calendars |
| NumberOfMachines | number | Yes | Number of active eligible WorkResources, not an extra multiplier on their summed calendars |
| Supervisor | reference | No | → Employees; the Shop Supervisor who approves tickets and sequences this queue |
| Active | boolean | Yes | — |
| Policy | reference | Yes | → ShopPolicies. Rate/calendar policy version |
| RateVersion | text | Yes | Immutable approved rates and effective interval; new version cannot rewrite posted tickets |
| RateHistoryJSON | longtext | Yes | Reviewed effective-rate intervals; only Shop Owner/Admin prepare changes under protected policy |
Phase 2 · Shop Supervisor
Prepare masters and instructions
Load customers, suppliers, employees and work centers with stable identifiers. Resolve supervisor and identity links, then check materials, conversions, part revisions and routings against actual drawings and setup sheets.
| Field | Type | Required | Definition / allowed values |
|---|---|---|---|
| WorkCenterCode | text | Yes | — |
| Description | text | Yes | — |
| WorkCenterType | select | Yes | Machine, Manual, Assembly, Inspection, Outside |
| MachineRate | decimal | Yes | USD per occupied machine hour, including approved setup, run and rework; rate/policy snapshot retained |
| LaborRate | decimal | Yes | USD per allocated labour hour; employee override only under policy and protected visibility |
| BurdenRate | decimal | Yes | USD per hour on the approved LaborHours or MachineHours burden basis |
| CapacityHoursPerDay | decimal | Yes | Summary only; actual available capacity comes from WorkResources calendars |
| NumberOfMachines | number | Yes | Number of active eligible WorkResources, not an extra multiplier on their summed calendars |
| Supervisor | reference | No | → Employees; the Shop Supervisor who approves tickets and sequences this queue |
| Active | boolean | Yes | — |
| Policy | reference | Yes | → ShopPolicies. Rate/calendar policy version |
| RateVersion | text | Yes | Immutable approved rates and effective interval; new version cannot rewrite posted tickets |
| RateHistoryJSON | longtext | Yes | Reviewed effective-rate intervals; only Shop Owner/Admin prepare changes under protected policy |
Phase 3 · Plant and ERP.ai
Reconcile material
Count stock by material, heat, ownership and location. Record usable remnant dimensions and available certificates. Customer-owned receipts and returns need their own history; a supplier purchase order is not a substitute for that evidence.
Phase 4 · Plant and ERP.ai
Prove the working path
Rehearse an offered quantity alternative, an exception approval, a released traveler, a material return and a partial outside-processing receipt. Check first-article release separately from completed quantity, then partial shipment, milestone billing, a cash correction and job close. Use the shop's actual role assignments and devices.
Phase 5 · Plant and ERP.ai
Choose the cutover
A new-job cutover lets old work finish in the previous system. An in-flight transfer needs a reviewed baseline for operation lots, outside custody, material claims, cost, shipping and remaining billing. Reconcile open receivables and effective cash applications at the same cutoff.
Phase 6 · Shop Owner
Accept and support
Verify opening totals and role access before enabling new operational messages and accounting delivery. Agree exception owners, recovery procedures and support. Review actual job results before changing standard estimates or rates.
| Role | Screens |
|---|---|
| Shop Owner | 9 |
| Estimator | 4 |
| Production Manager | 11 |
| Shop Supervisor | 6 |
| Operator | 2 |
| Buyer | 4 |
| Quality Inspector | 4 |
| Office Manager | 5 |
Role permissionsRoles and permissions →
Use Proto to prepare configuration changes on a branch for review before release. Changes to a rate, approval rule or traveler must preserve the basis of work already approved or posted. Agree validation and rollout for the affected process; changing configuration does not retroactively authorize a commercial or quality decision.
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.