Every machine, live — and the real reason it stopped.
MOS reads the machine itself — its controller, its PC or the files it writes — and shows running, idle and alarm time per machine and per shift. Availability, performance and quality are worked out from what the machine reports, not from what someone remembers at the end of the shift. Stops carry their true cause, so the morning meeting talks about facts.
At the end of a shift someone writes down what ran and why it stopped. The machine knew the real answer every second, and nobody asked it.
“MOS reads the machine itself — its controller, PC or files — and shows running, idle and alarm time, counts and cycle times, rolled up by shift, day and month, with the true reason for every stop.”
Drawn, not promised: the top row is how a stop reaches the morning meeting today — written on a sheet at the end of the shift. The bottom row is the same stop read from the machine the moment it happens, with its duration and its reason.
Hover or tap a stage to see what is captured there.
Not a standalone tool — a product on the MOS platform, sharing one login, one set of people and roles, and one database with every other module. The lit layers are the ones this product uses; the signal path shows how data moves through them.
The honest map, drawn as one thread. Filled nodes are in the product today; outlined nodes are other MOS modules on the same platform; dotted nodes are roadmap and never represented as available until built. Hover a node.
Each card ends with the thing itself as it appears in MOS — not a description of it.
Step through it or let it play. Each step: who does it, on what, what is captured, and the check that guards it.
MOS Connect reads the machine the way it already talks — controller over the network, its PC, or the files it writes.
Running, idle, alarm and planned stops are mapped once per machine with the plant's own stop reasons.
States, counts and cycle times are recorded continuously and buffered if the network drops.
When a machine stops, the operator picks a reason once; the duration and time come from the machine.
OEE, availability, performance and quality by shift, day and month; losses ranked by reason.
A machine down beyond its limit raises an alert; the shift report reaches the plant head by e-mail.
MOS Central shows every plant on one screen with the same numbers.
| Your ERP / Tally typically gives | OEE & Machine Monitoring adds |
|---|---|
| A shift sheet filled at the end | Machine states recorded every second |
| Downtime from memory | Stop duration and reason from the machine |
| OEE estimated monthly | OEE by shift, day and month, live |
| Breakdowns counted by hand | MTTR / MTBF from real stop times |
Controller over the network (Modbus TCP, OPC UA), the machine PC, or the files it writes
MOS Connect on the machine network; buffering if the link drops
MOS Edge in the plant; MOS Central for every plant in one view
For a machine with no readable state, a simple signal tap
What it connects to, where it runs and what it gives you — the short version your IT and your plant head both want.
Machine states, counts, OEE, stop reasons, alerts, shift & monthly reports.
MOS Energy (kWh per machine/part) on the same gateway; Vision Poka-Yoke at the same station.
Which protocol each machine speaks is confirmed at site; most expose state somewhere.
Predictive maintenance — not represented as available.
Capabilities depend on the plant's process and what is connected at site. Nothing on this page is represented as available until it is built and running.
Their machine's state and the reason prompt for each stop
Which machine is down right now, and why
Breakdown history, MTTR and MTBF from real stop times
Shift and monthly OEE across lines
Nothing changes. Its controller, PC or log files are read as they are.
The MOS gateway on the machine network, buffering if the link drops.
The MOS plant server — screens open in any browser on the network.
One machine connected and its states on screen.
Stop reasons agreed with production; shift report starts.
All machines on the floor view; trends and losses running.
Most machines expose their state somewhere — a controller, a PC, a file or a signal. The gateway reads whichever one is there; for a machine with none, a simple signal tap is added.
The operator picks a reason once when the machine stops; the duration and time come from the machine.
Every unit scanned at every station. Nothing skips a stage.
See the module →kWh per machine, per shift and per part — read from the meters, not the bill.
See the module →Every part judged by camera in under a second, defect circled.
See the module →Tell us about your plant and what you want to see. We visit, connect one machine or station, and you watch your own data in MOS before anything is quoted.