Heavy industry
The plant exists twice: on the floor and on screen
The system you run a plant with, built like the plant: every machine, every work order and every scrap piece has its place and its record. It isn't a dashboard watching from outside; it's where the work happens. Scroll down and drag a whole shift.
The shift runs well and records badly
On the floor everyone knows what happened: the press was down forty minutes, that batch came out needing rework, nine pieces went to the scale. By the time any of it reaches a system —if it does— it's a round number typed by someone who wasn't there.
So you end up with two truths: the floor's and the report's. When they disagree, the written one wins, and next month's decisions rest on it. Nobody bought bad software. They bought software that found out late.
Planta Norte · demo
This shift already happened. Drag it.
Eight hours of a metalworking plant, compressed. Drag the shift line to any moment, click a machine to see what it had in hand, and watch the two counters: what stock on hand says it holds, and what it really holds.
Bringing the plant up…
The plant
Click a machine to see what it answers for
- Delivered
- —
- Scrap
- —
- In stock
- —
- Work orders
- 3
Latest entries
None of this was keyed in by hand. Every figure —the OEE, the scrap, the pieces, what's left in stock— comes from the entries the shift left behind, which is why you can rewind it and everything still adds up. A video can't rewind like this; you only skip its frames. Here it recalculates.
What ends up on the record
- Every work order — its progress, its station and the part that came off it
- Every stoppage — with its time, its length and its cause, not as a gap in a chart
- Every scrap and every rework — at the station where it happened, not at month end
- OEE per machine — computed from its three factors, not typed in by hand
- Inventory from entries — it follows from what happened; there are no two figures to reconcile
- Part genealogy — which heat it came from and who it shipped to: that's the next layer, and it goes in once the record is there
What we can build
What a plant gets built
On the floor
- Shop floor
- Work orders, stations and where every part stands. Downtime with its hour and its cause, not as a gap in a chart. OEE calculated, not typed in.
- Maintenance
- Preventive by machine hours instead of by calendar, corrective with its history, and spare parts with a minimum that trips before you run out.
- Quality
- Inspection plans, non-conformities with their corrective action, and the certificate your customer asks for pulled from the record instead of written by hand.
In the numbers
- Inventory from entries
- What you have is deduced from what happened: every issue, every receipt, every piece of scrap. No two figures to reconcile, no Sunday count.
- Cost per part
- Material, machine hours and real scrap. So you quote with the plant's numbers instead of whatever the estimator remembers.
- Purchasing
- Requisition, order, receipt against that order. And every supplier with a delivery record, which is what decides the next order.
Facing out
- Part traceability
- Which heat it came from, which stations it passed, who it shipped to. The day a claim arrives, the answer is already there.
- Shipping
- Dock, packing list, waybill and proof of delivery, out of the same record that made the part.
- Customer portal
- Let them see their order's progress, their certificates and their shipments without calling anyone.
And what almost always goes around it: connecting to what's already there — ERP, scales, scanners, tax stamping —, screens on the floor for the operator, and reports that write themselves.
None of this is a catalog module
Off-the-shelf systems serve an average company that doesn't exist: you pay for modules nobody opens and you bend the operation to the software instead of the other way around.
A plant has its own way of counting inventory, its own way of moving a part, and its own reports. Custom work starts there, not from a feature list.
- 7 to 14 weeks
- From scope to delivery, on committed dates.
How we work
All of this comes
from one place.
A plant doesn't need six vendors blaming each other. The system, the model of the building, the server, the reports and everything you see above come from the same team, and there's one person to call when something breaks.
- DesignIdentity, grid, type.
- EngineeringThe system on the inside.
- 3D and motionWhat you touch and what moves.
- InfrastructureWhere it lives and how it holds.
- DataReports that write themselves.
- OperationsAfter delivery.
One system, one owner.
Tell us what doesn't add up at shift close
The form builds a live brief: what you type is, word for word, what reaches us.