System
Production and factory management system
A block, its slabs, and every metre that leaves the yard.
Factories usually know their revenue and rarely know their yield. Material enters as one unit and leaves as many, transformed by machines that each waste a different amount, and the reconciliation happens monthly, in a spreadsheet, by one person.
We model the transformation itself. In a stone works, a block becomes slabs becomes finished pieces, each carrying its parentage — so yield, wastage, and the true cost of a finished square metre are properties of the system, not of somebody's memory.
- Core model
- Order · Batch · Unit · Process · Dispatch
- Traceability
- Parent-child lineage through every transformation
- Yield
- Wastage recorded per process and per machine
- Measurement
- Piece, area, weight, or length by material
- Floor capture
- Phone and scanner, tolerant of poor signal
- Machines
- Utilisation, downtime, and maintenance schedule
- Stock
- Raw, work in progress, and finished, valued
- Costing
- Material, process, and labour rolled to unit cost
- Deployment
- On-premise or cloud
How it runs
Every stage, in order.
Each stage produces something the next one needs. Where a stage can fail, it fails visibly rather than passing bad data forward.
- 01
Intake
Raw material is received, graded, measured, and labelled with an identity it keeps for life.
- 02
Transform
Each process records what went in, what came out, and what was lost — the only honest source of yield.
- 03
Trace
Every finished piece can be walked back to the block it came from, and forward to the customer it went to.
- 04
Stock
Finished inventory is tracked by real dimensions and grade, because that is how it is sold.
- 05
Dispatch
Loading against an order updates stock and triggers the invoice from what physically left.
Scope
In detail.
Modules
15- Customer orders and specifications
- Raw material intake and grading
- Batch and lot identity with labelling
- Process routing between machines
- Per-process wastage and yield capture
- Work in progress by stage
- Machine utilisation and downtime
- Maintenance schedule and history
- Operator shift logging
- Quality inspection and rejection
- Finished stock by dimension and grade
- Reservation and allocation to orders
- Dispatch notes and loading
- Unit costing and margin reporting
- Supplier and purchase orders
Deliverables
What you get.
Written into the scope document before work starts, and used as the acceptance test when it finishes.
- 01Configured system covering the processes and materials in scope
- 02Labelling and scanning setup for the floor
- 03Import of current stock and open orders
- 04Supervisor and operator training in the working language
- 05Documentation and handover
- 06Support agreement with a defined response time
Questions
Asked before.
Our floor staff are not office workers. Will they use it?
Only if it is faster than what they do now, which is the design constraint. Capture is scan-first, in the working language, with as few taps as the step allows.
Can it tell us our real wastage?
Yes, per process and per machine, because wastage is captured at the point of transformation rather than inferred at month end.
What if the network is unreliable on the floor?
Capture tolerates a poor connection and reconciles when it returns. On-premise deployment is available where connectivity is genuinely bad.
Does this work for materials other than stone?
The model fits any operation where one unit becomes many through measurable processes — timber, glass, textiles, and metal fabrication share the shape.
Also in Systems
Next step
Scope it before you commit to it.
The first step is a short written scope: fields, volume, schedule, delivery, and acceptance criteria. It is quick, it is concrete, and it tells you whether this is worth doing at all.