Shop-floor challenges in Indian manufacturing

Four recurring problems commonly described in small and mid-sized plants. For each one: what happens, why it matters to the business, how plants cope today, and what this research is trying to find out.

Challenge 01

Production visibility

Knowing what has been produced against plan while the shift is still running.

Problem description

Output is counted at the machine but compiled only at shift end or the next morning. A supervisor may know a machine is behind, but the production manager and owner usually see the gap after it can no longer be recovered.

Business implications

  • Missed or partial dispatches discovered late.
  • Unplanned overtime approved under pressure.
  • Customer commitments made on uncertain capacity.
  • Reviews focus on explaining shortfalls instead of preventing them.

Current methods

  • Supervisor rounds and verbal updates.
  • Hourly boards or whiteboards at some machines.
  • Shift registers summarised into Excel by the office.
  • Phone calls and WhatsApp messages to managers.

Research questions

  • How long does a shift's output figure take to reach decision-makers?
  • Which decisions would change if a gap were visible two hours earlier?
  • Is hourly visibility at the bottleneck machine sufficient for most plants?

Potential technology approaches

  • Hourly planned vs actual entry by the operator on a shared tablet or phone.
  • Part counting from machine signals where controllers allow it.
  • A simple shift view for supervisors and a daily summary for management.

Challenge 02

Machine downtime

Understanding when machines stop, for how long, and why — consistently enough to act on it.

Problem description

Breakdowns are usually remembered, but short stoppages, setup overruns and waits for material, tools or inspection are often missed or written as a single total with a vague reason such as "maintenance" or "problem".

Business implications

  • Repeat losses stay hidden because they are never grouped by reason.
  • Maintenance effort targets the most visible failure, not the largest loss.
  • Capacity planning assumes more available machine time than exists.

Current methods

  • Breakdown registers maintained by the maintenance team.
  • Downtime totals noted in the shift production register.
  • Memory and discussion in morning meetings.

Research questions

  • What share of stoppages is captured with a usable reason?
  • How short can a reason-code list be while still being useful?
  • Does recording the start time of each stoppage change what gets fixed?

Potential technology approaches

  • One-tap stoppage logging with a fixed list of reasons.
  • Automatic run/stop detection from machine signals, with the reason added by the operator.
  • Weekly downtime-by-reason summaries for the production manager.

Challenge 03

Manual reporting

The effort, delay and errors created when production data is written, rewritten and retyped.

Problem description

A typical chain moves the same figure from the operator's slip to the shift register, then into an Excel sheet, then into a summary for management. Each step adds delay and a chance of error, and nobody owns the whole chain.

Business implications

  • Staff time spent compiling rather than improving.
  • Transcription errors that undermine trust in reports.
  • Multiple versions of the same sheet in circulation.

Current methods

  • Paper shift registers and production slips.
  • Excel workbooks maintained by a data-entry person or supervisor.
  • Photos of registers shared on WhatsApp.

Research questions

  • How many times is a single production figure written or typed?
  • Which parts of Excel-based reporting work well and should be kept?
  • What would make direct digital entry acceptable to operators?

Potential technology approaches

  • Single point of entry, as close to the machine as possible.
  • Mobile-friendly forms in the local language with minimal typing.
  • Export to Excel so existing analysis habits continue to work.

Challenge 04

Data and management visibility

Giving owners and plant heads trends and reasons, not just totals.

Problem description

Management usually receives a daily total — parts produced, perhaps rejections — without the context of plan, downtime reasons or trends across weeks. Questions are answered by calling the plant, which depends on who is available and what they remember.

Business implications

  • Investment decisions (new machines, extra shifts) made without loss data.
  • Difficulty quoting delivery dates confidently for new orders.
  • Improvement efforts are hard to evaluate over time.

Current methods

  • Daily production summary by message or email.
  • Monthly MIS reports compiled from Excel.
  • Periodic plant visits and review meetings.

Research questions

  • Which three or four measures do owners actually use to make decisions?
  • How much detail helps, and when does it become noise?
  • Does trend data change investment or capacity decisions?

Potential technology approaches

  • A weekly one-page summary: achievement, top losses, rejection trend.
  • Exception alerts only when a measure moves outside an agreed range.
  • Drill-down from plant to machine for occasional investigation.

Recognise one of these in your plant?

Tell us which challenge costs you the most. Real examples — even partial ones — help turn these questions into useful findings.

Share your experience