Know exactly where production time goes.
Linesense OEE records every run, stop and count on every machine, then shows which machine, which shift and which reason cost you the most, in minutes and in money.
Example numbers: availability 88%, performance 85%, quality 97%.
OEE, in one shift
OEE asks how much of the time you planned to produce was spent making good product at full speed. Time leaks out in three ways, and each one has a name.
Jams, changeovers, waiting for material. The machine was not running.
Running, but below its ideal speed. Micro-stops live here.
Time spent on product that was scrapped or reworked.
The only time that earned money.
396 of 450 minutes running
33,660 made against 39,600 at ideal speed (100 a minute)
32,650 good out of 33,660
327 of 450 minutes
Example numbers to show the arithmetic, not a benchmark. Planned stops such as breaks are taken out before anything is counted, so they never count against the machine.
What you get
Everything on this page runs from the same recorded stops and counts, so every screen agrees with every other.
Live floor view and TV mode
Every machine green, amber or red, with its count and current OEE. Put it on a TV in the hall and open it on supervisors' phones. A stopped machine shows how long it has been stopped.
Downtime with reasons, in two taps
Linesense records the stop the moment it happens. The operator picks the reason on a tablet from a short tree, in English or Urdu, instead of writing "other" at the end of the shift. Power cuts are tagged automatically and kept apart from breakdowns.
Micro-stops
Short stops of a minute or two never make it into a register, yet they add up to hours. Linesense counts every one and shows the total per machine and shift.
Changeovers per product
Each product has its own ideal speed, so a slow product is not mistaken for a slow machine. Changeover time is measured for every switch and compared across shifts.
Planned stops and shift targets
Breaks, cleaning and maintenance windows are scheduled and left out of the OEE calculation. Set a target per shift and machine and see who is ahead or behind while the shift is still running.
Shift reports by email or WhatsApp
At the end of every shift, a report goes to the people who need it: output, OEE, the biggest stops and how the shift compared with its target. Exports to CSV and Excel are always available.
Loss Pareto in money
The top reasons for lost time, ranked by minutes and by what those minutes cost, using the cost per minute you set. Start the morning meeting with the biggest loss, not the loudest complaint.
Energy per unit
Electricity per carton, meter or kilo, and what a machine burns while it idles between jobs. Finance recognises this number immediately.
Alerts with escalation
A message when a machine stops for longer than you allow or OEE drops. If nobody responds, it goes to the next person on the list.
Numbers you can trust
An OEE figure is only useful if the plant manager believes it. Here is how Linesense keeps the counts honest, shown on a few example readings.
What the device sends, and what is counted
| Time | Reads | Linesense counts |
|---|---|---|
| 10:00:00 | 4,210 | Starting point |
| 10:00:10 | 4,262 | 52 units |
| 10:00:10 | 4,262 | Sent twice, ignored |
| 10:00:20 | 4,309 | 47 units |
| 10:00:30 | 18 | Counter reset after a power cut: 18 units, not minus 4,291 |
| 10:00:40 | 71 | 53 units |
A reading that is physically impossible for the machine is held for review instead of being counted.
The device reports a running total, not single pulses. If one message is lost, the next one still carries the full count.
When a counter drops back to zero after a power cut, Linesense starts again from zero instead of inventing a huge number. A message that arrives twice is counted once.
Every reading is filed by when it happened, not when it arrived. After an internet outage, the backlog lands in the shift it belongs to and the totals update.
How changeovers, planned stops and very short stops are treated is set once for your site, in writing, and versioned. Everyone reads the same OEE.
Open any OEE number and see the stops, counts and reasons behind it.
We compare Linesense's counts with your production records every day. If they differ, we fix that before anything else.
Three tiers, one product
Start with what you need and move up without changing hardware or losing history.
| Feature | Essentials | Professional | Enterprise |
|---|---|---|---|
| Live status, counts and OEE | |||
| Shift and daily reports, exports, TV mode | |||
| Downtime capture and reasons | Operator tablet, simple reason list | Operator tablet, your own reason tree | Operator tablet, your own reason tree |
| Alerts | Plus WhatsApp and SMS, with escalation | Plus WhatsApp and SMS, with escalation | |
| Planned stops, schedules and targets | Not included | ||
| Ideal speed per product, changeovers | One speed per machine | ||
| Micro-stops and the six big losses | Not included | ||
| Energy per unit | Not included | ||
| Reject reasons and rework | Manual count | ||
| REST API, webhooks, Power BI | Not included | ||
| Single sign-on with Entra ID or Active Directory, SCIM | Not included | Not included | |
| SAP integration | Not included | Not included | |
| Multi-site roll-ups, audit trail | Not included | Not included | |
| Where it runs | Cloud | Cloud | Cloud, dedicated cloud, your cloud account or in your plant |
| Support | Email and WhatsApp, business hours | Plus a monthly OEE review call | Named engineer, service levels, quarterly review |
Pricing is per line per month, from PKR 12,000 in Pakistan. See all prices.
See how a pilot worksQuestions about OEE
How is the ideal speed set?
From the machine's rated speed, checked against how it actually runs in the first weeks. We agree the number with your production team, set it per product, and you can change it later. Performance is only as fair as this number, so we do not guess it.
What if a machine makes different products?
Give each product its own ideal speed. When the product changes, the machine's target changes with it, and the changeover itself is timed. A slow product is then shown as a slow product, not a poor shift.
Can we edit downtime?
Yes. Supervisors can change a reason or correct a wrong tag. If two people edit the same stop, the second is asked to reload rather than silently overwriting the first. Enterprise adds an audit trail of every change.
Do you replace our MES or SCADA?
No. Linesense reads from what you have, or from sensors where there is nothing to read, and adds loss analysis on top. On Enterprise it can also send production confirmations into SAP.
What about power cuts?
They are tagged automatically and counted separately from breakdowns, so a crew is not blamed for the grid. The device keeps counting through cuts and syncs when the link returns.
See your own shift in Linesense.
A 30-minute call, or an hour on your floor. We will tell you honestly whether it would pay for itself.