Production Disruptions: Know in Minutes, Not at Shift-End

Many Indian factories learn a line stopped only at shift-end, when the loss is already locked in. A camera-based floor monitor watches every zone continuously and messages the right person on WhatsApp or Telegram within minutes — with the location, the problem, and how long it has been down.

Here is the part the dashboard vendors skip. A current sensor knows Line 3 drew no amps at 11:40. It has no idea why: whether the station is unmanned, the trolley never came, or a pallet is jamming the feed. A camera sees the circumstance around the stop, not just the symptom, and that is usually enough to send the right person first. This piece is about one variable: how many minutes pass between a stop starting and someone who can fix it knowing.

Why a camera, not another sensor

The tools you are actually comparing this to — MES/OEE software, clamp-on current sensors, vibration monitors, operator tablets — all read the machine. So they only ever know that a machine stopped, never why. Three gaps follow from that, and a camera closes them.

It sees the circumstance, not just the stop. A stopped line is a symptom. The camera shows the empty feed area, the unmanned station, the blocked chute. That is not a root-cause analysis, and a camera cannot tell you why a die change dragged on, but it tells the alert which person to wake: the material handler, the maintenance fitter or the line supervisor.

It needs zero machine integration. A PLC tap, a clamp-on sensor or an MES retrofit per machine is a hard sell on a floor of old, mixed-vintage, non-networked machines. One camera watches a whole zone, many machines and the space between them, with no per-machine wiring and no OEM cooperation.

It doesn't wait for someone to write it down. Operator- or supervisor-entered downtime arrives late, after the shift, and compressed. We cover why in the daily shift report an owner actually reads; this article is about the other half of the problem, the hours between the stop and the report.

The people-and-material stalls that machine telemetry cannot see at all, such as an unmanned station or a trolley that never arrived, matter most for delivery dates. That is covered in why your shipments slip. Here the question is narrower: once a stop has started, how fast does the right person hear about it?

And it isn't an Andon board. A wall scoreboard still needs someone looking at it, shows machine-state only, and is a capital install. You don't need another screen nobody watches. You need the ping to reach the one person who can fix it.

What a power cut looks like on camera

Take an illustrative case, not a measured one. The grid drops at 14:20 and every camera in a bay goes dark within a few seconds of the others. A system that watches each station separately would fire a stop alarm for every line in that bay. A system that looks at the whole floor sees one pattern, all feeds lost together, and sends one message: "Bay 2 dark since 14:20, looks like a power event." One message to the maintenance in-charge is useful. Thirty messages to everyone is how a group gets muted.

The same pattern shows up in your own records in a less obvious way. A server or recorder on a UPS can ride through the cut, so its own logs show no gap, while the floor stood still. If you want to know how often power actually stops your floor, count the zone-wide blackouts in the camera record. A machine that kept running on battery won't tell you.

Reactive vs proactive: same event, different bill

The event is identical. What changes is when you know.

Every minute you shave off time-to-know comes straight off the total stop. Before you weigh any of this, put a rupee figure on one downtime hour — our guide on the real cost of factory downtime and how to measure it gives you a formula and a worked ₹ example.

Worked example: the same 20-minute fix, three different bills

Assume one assembly line with 25 operators. Assume a loaded labour cost of ₹150 per worker-hour (wage plus PF, ESI and leave; replace it with your own figure, which starts from your state's minimum wage order and your pay register). Assume the line earns ₹6,000 of contribution per running hour, and that the fix takes 20 minutes once the right person arrives. All of these are assumptions for illustration, not benchmarks.

Arithmetic: 25 workers × ₹150 ÷ 60 = ₹62.5 per line-minute of idle labour; ₹6,000 ÷ 60 = ₹100 per minute of contribution. The fix is the same 20 minutes in every row. The only thing that changes is how long nobody knew. One caveat: contribution is truly lost only if this line is your constraint and you can't make the output up later. If you can, the cost moves to overtime instead. For a full method, see what one hour of downtime actually costs an Indian factory.

Two numbers frame the stakes:

Unplanned downtime costs the world's 500 largest companies almost US$1.4 trillion a year, about 11% of their revenue, by Siemens' estimate (Siemens/Senseye, True Cost of Downtime 2024) (source). You don't run a plant that size. The arithmetic is identical on a 300-worker floor: idle labour, dead overhead, nothing shipping.

In the World Bank Enterprise Survey, India 2022 country profile, 19.9% of Indian firms reported electrical outages. Among large firms (100+ employees), the share was 26.1%, averaging 1.9 outages in a typical month. That is far below the South Asia average in the same profile, but a quarter of large plants is not an edge case. An alert system has to handle a power cut sensibly from day one.

The five disruptions that quietly eat a shift

For two of these five, no machine-mounted sensor helps at all, and for a third it sees only half the picture. Those disruptions happen around the machine, not inside it.

What "in minutes" actually buys you

Real-time floor alerting is a management alert layer: it samples camera feeds on a short interval and flags a disruption within minutes — not a millisecond machine-safety trip. A genuine stop surfaces fast enough to matter for a stalled line, not for guard-level protection. For split-second safety you still need hard-wired interlocks and light curtains, never a camera.

Nor is a camera the best tool for machine cycle counts. Where a PLC signal exists, it wins on counting parts, and a camera should complement it rather than duplicate it. What we catch is the zone-level disruption where there is no machine signal to fuse with — the stockout, the empty station, the blocked aisle.

The India realities this has to survive

• Load-shedding and DG changeovers. As in the power-cut example above, a good system treats a zone-wide motion or feed drop as a single "power event" rather than firing dozens of confused alarms, and it tells a planned genset changeover apart from a line that died on its own.
• WhatsApp-first. Indian floors run on WhatsApp, not on enterprise dashboards nobody opens. Send the alert where the supervisor already looks. The mechanics are covered in getting camera alerts where you actually look: template categories and costs on the WhatsApp Business Platform, groups versus individuals, and the ERP downtime code. Keep alerts machine- and zone-level ("Line 3 idle 12 min"). Don't put clips of identifiable workers into a group, and tell workers what the cameras are for, with a worker CCTV privacy notice.
• Manual escalation stays. Alerting doesn't replace supervisors; it gives them a faster trigger. The chain still ends with a person deciding what to do. Route by role: the line supervisor first, the director only when a stop crosses a set threshold.

Where this breaks: coverage and false alarms

Two things decide whether this helps or annoys: what the cameras can see, and how often it cries wolf.

Coverage. The system can only flag what a camera frames. A cell in a blind corner, a machine behind a stacked pallet, a bay outside the shot — those stay invisible. Placement beats camera count. It is the same discipline behind production line monitoring with cameras in India: get the coverage right first.

False alarms. An untuned system that pings the director every time a line pauses for a tea break gets muted by day three, and then it is worthless. Getting to a signal you trust takes tuning — per-station idle thresholds, learned break and changeover patterns, alerts routed by severity. Expect a tuning-in period. Any vendor promising zero false alarms on day one is selling you something.

How Mama fits

This is the wedge Mama is built around. You leave an email or phone in the form below. We come back with a camera placement plan — how many cameras, where, ceiling turret vs wall bullet — aimed at the zones where disruptions actually happen. Then it reads those feeds and writes to you in plain language about machines and zones, never named people: "Line 3 idle 12 min, feeder station unmanned" or "Bay 2 dark, looks like a power event." On WhatsApp or Telegram, in minutes. If you want to try it, leave an email or phone in the form below.

It doesn't run the plant. You do. It just makes sure you are never the last person to know your own floor stopped. The same watching layer underpins near-miss and safety detection on the factory floor, so one placement plan earns its keep on both efficiency and safety.

Do this on Monday

1. Cost one downtime minute on your worst line, using the table above or the downtime-cost method. That number is your urgency.
2. Log time-to-know for one week. Record when each disruption actually started vs when you found out. The gap is your recoverable loss.
3. Check what a camera could see today. Walk your five disruption types. The ones a camera can't frame tell you where placement has to improve first.

The stop is going to happen either way. The only variable you control is how fast you hear about it.

FAQ

How fast can a camera system detect a stopped production line? In minutes. A floor-watching system samples the feeds on a short interval and flags a station that has gone quiet past its normal idle threshold. It is a management alert layer, not a millisecond safety trip; for split-second machine protection you still need hard-wired interlocks.

Why use a camera instead of a current or vibration sensor on the machine? A machine sensor knows that a line drew no power. A camera shows the circumstance: the station is unmanned, the trolley never came, a pallet is blocking the feed. That is often enough to send the right person first, though it is not a root-cause analysis. It also needs no per-machine wiring and catches stockouts and blocked aisles, which no machine-mounted sensor can see.

How do camera alerts handle power cuts in Indian factories? A well-designed system treats a zone-wide feed or motion drop as a single "power event" rather than dozens of confused alarms, and tells a planned DG changeover apart from a line that stopped on its own. All cameras in a zone going dark within seconds of each other is a distinctive signature; a single line stopping never looks like that.

Won't I just get flooded with false alarms? You will if it isn't tuned. The realistic path is a tuning-in period: per-station idle thresholds, learned break and changeover patterns, and alerts routed by severity so the director only hears about real stops. The goal is a signal you trust, not zero false alarms on day one.

Do I need to replace my supervisors? No. Alerting gives them a faster trigger; the escalation and the fix still end with a person. It watches every zone continuously — which no human can — so your people spend less time discovering problems and more time solving them.