Why Indian Manufacturers Still Do Root Cause Analysis on Paper

Picture a familiar composite, not a real client. An auto-parts plant in Punjab or Pune, sixty people, three shifts. A press trips at 2 a.m. The supervisor calls the senior technician, who has been there twenty years. He resets it, writes "done" in the register, and goes home.

Three weeks later the same press trips for the same reason. He is on leave. The register entry says nothing useful. The team starts again from zero.

The software vendors' explanation for why this plant has no RCA tool is price. That is rarely the real reason, and a vendor or investor who believes it will misread the market.

01Five reasons, and only one is money

The cost is invisible. A repeat breakdown does not appear in the accounts as a repeat breakdown. It shows up as lower output, overtime, a little more scrap and a delayed dispatch, each absorbed into a different line. Nobody adds them up, so nobody knows what the problem costs. Our piece on what downtime really costs an Indian plant shows how to put a rupee figure on it.

The knowledge lives in a person. Every plant has its senior technician whose memory is the failure database. While he is there, the system appears to work, which is exactly why nobody invests in replacing it. The risk only becomes visible when he retires, falls ill or joins a competitor.

The habit does not exist yet. Software records investigations. It does not make people investigate. A plant that does not already hold a short review after significant failures will buy a tool, fill in a few forms and let it lapse within a quarter. We have seen this with CMMS and ERP rollouts too.

The data is scattered. Production counts sit in one spreadsheet, maintenance in a register, quality in another file, costs in Tally. An RCA tool that cannot see any of it becomes one more place to type. The systems question is set out in which systems RCA must connect to.

Price, and price opacity. Specialist RCA vendors such as TapRooT, Sologic and EasyRCA mostly quote on request, and enterprise quality suites are priced for large plants. An MSME owner who cannot find a price assumes it is too high. That is a real barrier, but a smaller one than the four above.

Software records investigations. It does not make people investigate.

03What the standards actually require

It matters to be exact here, because "the standard mandates RCA software" is a sales line, not a fact.

• Automotive (IATF 16949). Clause 10.2.3 requires a documented problem-solving process that finds root causes, covers containment and verifies that the fix worked. It is one of the most frequently cited nonconformities in IATF audits. OEM customers add their own 8D formats on top.
• Pharmaceuticals (revised Schedule M). India's updated good manufacturing practice rules took effect for larger firms from January 2025. MSMEs that filed upgrade plans had until 31 December 2025, and CDSCO has since asked state regulators to begin inspections. Deviations and complaints must be investigated and corrective actions tracked.
• Aerospace and defence (AS9100). Nonconformity and corrective action requirements similar in spirit to IATF, with customer flow-down on top.
• Electronic records. Rules such as the US FDA's 21 CFR Part 11 do not require RCA; they govern how records are controlled once they are kept electronically. They add work when you move to software.

None of these requires a software product. They require a record that is complete, findable and shows the fix worked. Paper can meet that at low volume. It fails when investigations run into the hundreds a year, when several plants share learning, or when an auditor asks for every investigation on one part number from the last three years.

The standards require a record that shows the fix worked. Software becomes necessary when paper can no longer produce that record on demand.

05What to do

For MSME owners and plant heads:

• Start a repeat-failure count this month. It is the single number that tells you whether problem solving works.
• Get what your senior technician knows onto paper while he is still there: the ten most common failures on the bottleneck asset, their causes and their fixes.
• Hold a fifteen-minute review after every stoppage above a threshold you set. The habit is the asset, and it is free.
• When you buy, prefer the RCA module in the quality or maintenance system you will need anyway over a separate tool.
• Ask every vendor for the price in writing, the integrations it supports with your actual systems, and two Indian reference customers of your size.

For CFOs: fund the first software purchase against a measured number, the cost of repeat failures on the bottleneck, and review it after two quarters on that number alone. This is ordinary FP&A discipline applied to the plant floor, and the same numbers feed the revenue and margin picture described in RevenueOS for manufacturing.

For vendors and investors: the Indian market will be won by whoever sells the habit with the tool, publishes a price, and connects to Tally-and-spreadsheet plants as they actually are. The low adoption is real. It is a sales and onboarding problem more than a market-readiness problem.