Module
Production
Routings describe each product once, orders are made from them, and a dispatch list queues the work on every work centre. What the floor confirms comes back to the order as it happens, and what the order made is booked into stock.
What it does
Routings built once
Describe a product once: its operations in order, the work centre each runs on, setup time, run time per unit and units per cycle. A standard operation is written once and copied into every routing that needs it.
Orders from a routing, a spreadsheet or the ERP
Make an order from its routing in a few fields, import a batch from a spreadsheet, or receive it from the ERP over the REST API. Each order copies its operations, so a change for one order stays on that order.
A dispatch list per work centre
Every operation that is ready, running or paused, in one column per work centre. Drag a card to set the order it is worked in, or move it to another work centre when a machine is down. Everyone sees the same queue.
Progress against plan
Good, scrap and rework come back from the terminal against the order quantity, and the time worked against the time planned. The projected finish follows the real pace, and an order that will miss its due date is flagged late before it does.
OEE and the losses behind it
Stops under planned and unplanned reasons, the ideal cycle time of each work centre and the good and scrap counts are what OEE is made of. Production turns them into OEE per work centre and shift, with the stop reasons ranked by the time they cost.
Output booked into stock
Completing the last operation books the good quantity into inventory as a production receipt, linked back to the order. The warehouse knows what the floor made without anyone typing it in.
How it works
Describe the plant once
Set up the work centres: one machine, a line of several or a bench with none. The machines under a work centre are the same devices maintenance looks after. Then write the standard operations and the routings built from them.
Plan and release
Make the order from its routing, import it or let the ERP send it, and change anything while it is planned. Release hands it to the floor, and its first operation is ready at its work centre.
Follow it on the floor
The dispatch list shows every queue, the terminal reports starts, pauses, quantities and stops, and the order shows what is made, what is left and when it will finish.
Close it with its record
The finished order books what it made into stock and keeps every confirmation with who entered it, every correction with who made it, and its history from creation to close.
Dispatch list
The shop floor at a glance
One column per work centre, holding every operation that is ready, running or paused, and above them what needs somebody now: the calls for help and the day's stops.
Worked from the top
Until somebody arranges it, a queue follows the due dates. Drag a card to put it where this work centre should work it, and the change is there for everyone.
Moved when a machine is down
Send an operation to another work centre when its machine is down or its queue is long. The order's history records the move.
Calls answered in the open
A call from a terminal appears with the work centre, the order and how long it has waited, longest first, until somebody says they are on the way.
The day's stops, reviewed
Every stop of the day with its reason, the machine it named, the order and how long it lasted. The night shift's stops are there in the morning, and a wrong reason or time is corrected with a record of who changed it.
With a machine connected, each column also shows whether the machine is running and what its counter says.
Machine signals
Machines that report for themselves
A small gateway at the machine watches two signals, whether it is running and a pulse per piece, and sends them to Mesonify every minute or so. Nothing here is required: a floor that records by hand gets the same records.
Stops open by themselves
Standing still past the threshold you set becomes a stop, and anything shorter is a pause between pieces. A stop the machine reports waits for its reason from the operator.
Counts per hour
Pieces land in the hour they were made in, with the cycle times that made them, so a shift can be read back hour by hour.
A count, not a confirmation
The terminal offers what the machine has counted as the good quantity. The operator confirms it, with the scrap and rework the machine knows nothing about.
One machine at a time
Connect machines one by one, and try it all first with a reference gateway and a simulator instead of a machine.
The gateway reads the run contact and the cycle pulse most machines already have, and posts them to the documented REST API. Mesonify works out the rest.
See Production running on your own plant.
Ask for a demo with your own devices, parts and jobs.