CMVR & TREM-IV compliance for Indian tractors — a 2026 operating guide.

Rule 126 of the Central Motor Vehicles Rules requires every manufacturer (other than of trailers and semi-trailers) to submit a prototype of each motor vehicle, including agricultural tractors and power tillers, to a notified testing agency for type approval. The notified list is finite: VRDE (Ahmednagar), ARAI (Pune), CFMTTI Budni, IIP (Dehradun), CIRT (Pune), ICAT (Manesar), and NRFMTTI (Hisar)^[2]. Foreign labs are not on this list — their reports are not directly acceptable for the Type Approval Certificate.

The technical content of the type-approval cycle for tractors is set out in AIS-017 Part 2^[3] (procedure) and AIS-114^[4] (specifications). The emission portion of the cycle is governed by AIS-137 Parts 1–7 — Part 7 carries the TREM Stage IV test method^[5]. Conformity of Production is governed by AIS-149^[6]. Together these four AIS documents define the test stack for an Indian tractor; together they take 6–10 months to clear when run in parallel and 12–14 months when run in sequence.

The Type Approval Certificate is typically valid for five years. CoP runs continuously across the validity period; it is the audit thread that connects the certificate to the production line. Manufacturers that treat CoP as an afterthought end up with the most expensive failure mode in the regime — a CoP suspension that interrupts despatch.

The technical step from TREM-IV to TREM-V is non-trivial. Stage V tightens NOx and PM limits to the level of EU Stage V; for tractors above 56 kW the practical implication is integration of a diesel particulate filter (DPF) and selective catalytic reduction (SCR) with urea (AdBlue) dosing. The packaging changes — exhaust after-treatment volume, cooling reroute, ECU emission strategy — ripple through chassis design. Programmes that begin TREM-V engineering only after the gazette lands have routinely been late to market.

For the 25–50 HP volume segment, the draft path through TREM IIIAA before TREM-V (1 April 2028 first, 1 April 2032 second) gives manufacturers a longer engineering runway but also creates two separate compliance gates instead of one. We recommend treating both as one engineering programme with two release windows — the alternative is an expensive re-design between 2028 and 2032.

AIS-149 sets out the procedure for Conformity of Production: the periodic verification by the type-approval agency that production units conform to the originally approved prototype^[6]. CoP audits are conducted by the agency that issued the original approval — ARAI, ICAT, or FMTTI Budni — and cover production-line sample drawal, retest of critical parameters from AIS-017 and AIS-137, and a factory-side check of quality control infrastructure^[10].

The factory-side CoP infrastructure must be in place before grant: sample retention with a defined cabin, in-house test capability for at least the routine drift-prone parameters, a calibrated ECU read interface for emission strategy verification, and documented quality plans for line-side inspection. Programmes that try to retro-fit CoP infrastructure post-grant get caught in the first surveillance audit — the cost of failing CoP is suspension of the Type Approval Certificate, which suspends the marking authority and stops despatch.

1. Emission cycle non-conformance discovered late. AIS-137 cycles run only at ARAI or ICAT; failures discovered late in development trigger a rebuild of after-treatment calibration that pushes the entire programme by 8–12 weeks. Pre-cycle dyno work at the factory de-risks this.
2. CoP infrastructure not factory-ready at grant. The Type Approval Certificate is granted without verifying CoP readiness; the first surveillance audit catches the gap; marking suspension follows. Pre-audit CoP at engagement start.
3. TREM gazette movement assumed static. Programmes plan against a fixed TREM-V date and rebuild the plan when the gazette shifts — losing 4–6 weeks each shift. Track the gazette weekly; build the plan with two scenarios.
4. Sequential routing of AIS-017 and AIS-137. AIS-017 at FMTTI Budni first, AIS-137 at ARAI later; each adds slot-queue calendar. Run them in parallel from the same prototype build.
5. Insufficient prototype units.Three prototypes can’t cover four parallel test streams; programmes wait for more units or serialise the tests. Plan for 5 units at the engineering build, not 3.

CMVR and BIS run on different calendars at different agencies, but the underlying engineering data overlaps. Pump certifications under the Pumps QCO 2023, hydraulic-sprayer certifications under IS 11313, implement specifications under various FAD-21 IS standards — these all sit alongside the AIS work without sharing test slots, and the costliest sequencing mistake is to wait until CMVR is granted before starting BIS. Run them from week one as one regulatory programme.

For the full procedural detail, see the pillar guide Tractor & Farm-Machinery Homologation in India. For the BIS-side specifics, see BIS Certification for Farm Machinery.

The CMVR side of an Indian tractor is stable; the TREM side is not. AgPro’s engagement model treats gazette-tracking as part of the regulatory project, not a side concern — each engagement has a named regulatory lead who tracks MoRTH, MoEF&CC, and PIB notifications weekly and rebuilds the programme plan when the rule shifts. The Pune team works at ARAI / CIRT proximity; the New Delhi team is across the road from MoRTH’s Transport Bhawan.

For multi-product portfolios — a tractor family, plus implements, plus engine platform variants — we structure CMVR / AIS-137 / AIS-149 work as one programme, BIS Scheme I work for the implements as a parallel programme, and the export-readiness OECD-code work at FMTTI Budni as a third. Three programmes, one engagement lead, one gazette tracker.