India Semiconductor Mission & PLI Schemes: What OSAT Operators Need to Know

The India Semiconductor Mission exists because the country consumes far more semiconductor content than it produces, and because electronics manufacturing that has already localised assembly of finished goods is still importing almost all of the silicon inside them. The policy intent is to close part of that gap by subsidising the capital cost of building semiconductor manufacturing capacity domestically, across fabrication, display, compound semiconductors, and assembly, packaging and test.

Two design choices matter for operators. First, support is weighted towards capital expenditure rather than operating subsidy, which suits a business whose first-year economics are dominated by equipment and facility cost. Second, central government support sits alongside state-level incentives, so the effective package for any given site is a stack rather than a single number. Two otherwise identical proposals in different states can have materially different economics.

The production-linked incentive logic that runs through India's wider manufacturing policy adds a second mechanism: reward measured against output or investment milestones actually achieved, rather than paid purely on announcement. For semiconductors and the electronics value chain around them, this pushes the commercial question away from securing approval and towards hitting the operational milestones that release the support.

The temptation with any incentive programme is to model it as a discount on capital cost and move on. That underestimates its effect on how the business must be run. Milestone-linked support converts schedule slippage into a direct financial event: a line that qualifies late does not merely earn revenue late, it can delay or complicate the support tied to that milestone. The internal implication is that the ramp plan becomes a financial commitment, not an operational aspiration.

Localisation expectations have a similar effect. Where support is associated with building domestic value — sourcing, employment, skills development, supplier development — those commitments have to be delivered by someone, on a timeline, with evidence. Operators who treat them as a compliance afterthought discover late that they need documented training programmes, verifiable local hiring and a supplier development effort that nobody was resourced to run.

The third operator-level implication is governance. Programmes structured around milestones and conditions generate reporting obligations. The organisations that handle this well build the evidence trail into normal operations — the same manufacturing execution and quality data that serves customers also serves the reporting — rather than assembling it manually each cycle.

Capital support reduces the cost of building capacity. It does not shorten the time required to produce a process engineer who can hold yield during a ramp, or an equipment technician who can restore a tool at three in the morning without escalation. When several sites are commissioning in the same window, the scarce input is not money or equipment. It is qualified people, and the incentive structure makes being short of them more expensive than it would otherwise be.

That produces a specific planning discipline. For each milestone the support is tied to, identify the roles that must be productive to hit it, the lead time to have those roles genuinely productive rather than merely hired, and the route by which each will be filled: built through structured training, mobilised from a mature semiconductor market, or recruited locally. Roles with the longest lead time should be started first, which in practice means beginning workforce work well before facility completion.

Skills-development commitments and the hiring plan should be the same programme rather than two. A structured pipeline that assesses, trains and mentors technical talent into process, test, quality, equipment and manufacturing-data roles satisfies the development expectation and produces the people the line needs. Running them separately doubles the cost and usually fails at both.

Because state-level support varies, site selection is often driven by the incentive stack, power and water reliability, and land availability. Those are the right first-order factors. The second-order factor that gets less attention is labour catchment: whether the location can supply and retain the technical profiles the plant needs, and how it competes with other employers nearby for the same people.

A location that is financially optimal but talent-thin shifts cost from capital to workforce. It raises reliance on relocation, increases attrition risk once a competing site opens nearby, and makes shift coverage fragile. This is not an argument against those locations. It is an argument for pricing the workforce consequence into the site decision rather than discovering it during the ramp.

Mobility planning belongs in the same analysis. Where experienced talent will be brought in from mature semiconductor markets for a defined period, the practical layer — work authorisation, documentation, relocation, family logistics, cross-border compliance — has real lead time and real cost. Treated as an afterthought, it becomes the reason a qualification date moves.

For an operator or investor assessing an India OSAT proposition, the incentive questions are necessary but not sufficient. The questions that separate a plan from a pitch are operational.

Alongside the financial stack, test the workforce and information layers with the same rigour applied to tooling and utilities. A plan that answers these credibly is usually a plan whose ramp dates mean something.

Incentives change the arithmetic of building assembly and test capacity in India, and they have made proposals viable that would not have been on their own. They do not change the physics of a ramp. Qualification still depends on process discipline, uptime, traceability and the experience of the people on the floor.

The operators who get the most out of the framework tend to be the ones who treat it as a schedule commitment and work backwards from it — building talent pipelines early, mobilising experienced engineers where local supply cannot answer fast enough, and scoping the plant's information layer as infrastructure rather than reporting. The companion articles in this series cover India's OSAT opportunity in full and the talent response in detail.