Tractor & Farm Machinery Homologation in India — End-to-End Guide

Homologation is the formal process of demonstrating that a vehicle complies with the applicable Indian standards and regulations before it can be registered and sold in India. For tractors and farm machinery, the process is governed primarily by the Central Motor Vehicles Rules, 1989 (particularly Rule 126) and a network of test agencies notified under that framework.^[1]

This guide is the full reference. It is written to be used by an engineering project manager and a regulatory lead working together; the calendar section is the part commercial leaders usually read first.

1. The CMVR framework

The Motor Vehicles Act, 1988 and the Central Motor Vehicles Rules, 1989 collectively govern the type-approval of all motor vehicles in India, including tractors. Rule 126 is the specific rule that requires every motor vehicle, before being offered for sale, to be tested for compliance with the provisions of the Act and the Rules, by one of the notified test agencies.^[1]

The CMVR Type Approval (TAP) framework defines:

• The structure of type-approval — three test levels (Type-I, Type-II, Type-III).
• The notified test agencies — ARAI (Pune), ICAT (Manesar), FMTII (Budni), VRDE (Ahmednagar), ICV (Chennai), and a small number of others.
• The administrative procedure — how applications are filed, samples submitted, reports generated, and approvals issued.
• Variant and version approvals — how changes to a previously-approved vehicle family are handled.
• Conformity of Production (CoP) — how the production line continues to demonstrate conformity after initial approval.

2. The three test-approval types

Under CMVR Rule 126, type-approval falls into three categories, with associated administrative procedures specified in the CMVR TAP documents:^[1]

Type	Scope	Typical timeline
Type I	Documentary review only — for minor changes to an already-approved model where no physical test is required	10 working days from complete submission
Type II	Partial test — selected tests are conducted where the change affects specific parameters	30 working days from sample acceptance
Type III	Full vehicle test — complete test regimen for a new model	45 working days from sample acceptance

These are the procedural timelines defined in the TAP document. In practice, slot availability, sample completeness, retest cycles on failed sub-tests, and the quality of submitted documentation all push real-world cycles further. Plan from a realistic 8-14 week baseline for a Type-III tractor approval, excluding sample shipping from a foreign facility.

3. The test agencies — picking the right one

ARAI (Automotive Research Association of India) — Pune

Established 1966. The first and most fully-equipped CMVR notified test agency. For tractors and farm machinery, ARAI handles the majority of type-approval work for Indian OEMs. It is the default choice where continuity with prior approvals matters and the OEM has an existing Pune-based engineering interface.^[2]

ICAT (International Centre for Automotive Technology) — Manesar

Established 2006 under the National Automotive Testing and R&D Infrastructure Project (NATRiP). The second full-scope CMVR test agency. Scope overlaps extensively with ARAI; OEMs routinely split their type-approval programme between the two based on slot availability and geographic convenience.^[3]

FMTII (Farm Machinery Training & Testing Institute) — Budni, MP

Predates ARAI. Under the Ministry of Agriculture & Farmers Welfare. The primary test institute for agricultural machinery, including PTO and drawbar performance testing under AIS-017 Part 2.^[4] For tractors, FMTII testing is typically required for state subsidy eligibility and is a practical prerequisite for dealer-channel trust. For non-road self-propelled machinery (combines, self-propelled sprayers), FMTII is usually the primary test agency.

VRDE, ICV, others

Vehicle Research & Development Establishment (VRDE, Ahmednagar, under DRDO) and Indian Centre for Vehicle Engineering & Certification (ICV, Chennai) are also notified under CMVR but are less commonly used for tractor homologation.

4. The emission track — TREM norms

TREM stands for Tractor Emission, India's adaptation of stage-equivalent off-road diesel emission norms. The timeline:

• TREM-I / II / III / IIIA — earlier stages, progressively tightened on HC, CO, NOx, and PM.
• TREM-IV — in force from October 2023 for tractors above 50 HP; aligned broadly with Stage IV off-road norms. Implementation added an estimated ₹1-1.3 lakh per unit to tractor manufacturing cost in the affected HP band, a 10-15 percent increase.
• TREM-V — on the near horizon, with detailed notification expected ahead of the implementation cutover.

Emission testing is handled at ARAI and ICAT; FMTII does not conduct regulatory emission certification. For OEMs re-homologating engines for TREM transitions, planning continuity with the same agency as the prior approval is the practical default.

5. The AIS framework — where BIS and ARAI meet

Automotive Industry Standards (AIS) are the technical standards referenced by CMVR Rule 126. AIS are drafted by committees hosted at ARAI and approved by the MoRTH Standards Committee. Most AIS are aligned with ISO/ECE/UNECE standards but with Indian amendments.

Relevant AIS for tractors and farm machinery:

• AIS-017 Part 2 — Test method for agricultural tractors (the core performance-testing specification).^[5]
• AIS-112, AIS-036, AIS-034 series — tyres, lighting, safety components.
• AIS-139 — roll-over protective structures (ROPS) for agricultural tractors.

Component-level approvals under the AIS framework are typically handled in parallel with the assembled-vehicle approval. Planning component approvals ahead of the assembled-vehicle submission is one of the cleanest calendar-savings levers available to OEMs.

End-to-end journey map — from engineering sign-off to first dispatch

The following is the chronological sequence we've run most successfully on tractor-family homologation engagements. It collapses sub-tasks that can run in parallel and shows the gating dependencies explicitly.

Phase 0 — Programme kickoff (weeks 0-2). Regulatory strategy aligned with commercial calendar. Agency selection (ARAI / ICAT). Authorised Indian Representative appointed where foreign. Initial slot enquiries opened with the chosen agency on an anticipated Q-end submission. Master variant tree drawn up — this single document typically saves 4-8 weeks across the programme.

Phase 1 — Documentation build (weeks 2-6). Technical documentation compiled: BOM against AIS mappings, variant boundaries defined in writing, quality-control plan drafted against Conformity of Production requirements, sample-specification dossier prepared. Engineering reviews for completeness. Parallel: component-level approval submissions (tyres, lights, ROPS) opened with the respective vendors and filed with the agency.

Phase 2 — Sample preparation and shipping (weeks 4-10). Sample built from production-complete line, not a one-off engineering build. Pre-dispatch inspection by internal QC against the declared spec. For foreign-origin samples, shipping and India customs clearance add 2-4 weeks.

Phase 3 — Agency submission and initial review (weeks 8-14). Formal application with documentation and fee. Agency scrutiny and deficiency observations if any — typically 2-4 weeks of iteration on documentation before sample is accepted for testing. This is where a well-prepared documentation package saves the most calendar.

Phase 4 — Testing (weeks 12-22). Full CMVR Rule 126 test series. Emission testing under TREM. Chassis and safety-critical component tests. Where a test fails, corrective action and retest cycles apply — plan for one retest cycle in a realistic calendar even when you expect clean passes.

Phase 5 — FMTII parallel track (weeks 10-22). AIS-017 Part 2 commercial testing at Budni, run in parallel with the CMVR track. Sample for FMTII can be the same unit used at ARAI/ICAT (after CMVR dispatches) or a second sample, depending on test-schedule alignment. Parallel execution is worth 6-10 weeks over sequential.

Phase 6 — CoP readiness (weeks 16-24). Quality-control plan finalised with line-level process controls. Internal CoP audit dry-run. Identification of the QC team member who will be the day-to-day CoP owner.

Phase 7 — Approval and registration readiness (weeks 20-28). CMVR type-approval grant. Registration preparation with the priority-state RTO. First dealer briefing on product specifications and registration process.

Phase 8 — First dispatch (weeks 24-32). Production ramp to initial dispatch volume, CoP first-cycle audit, first registrations at dealer locations. Commercial launch formally begins.

The first four-to-five months are where calendar is saved or lost. Teams who rush through documentation and sample preparation then wait in test queues typically end up 10-12 months all-in. Teams who invest thoroughly in the first 12 weeks and then maintain parallel tracks through testing close out at 8-9 months.

6. The full working calendar — 9 to 12 months

For a new tractor model family, the realistic working calendar from engineering sign-off to ready-for-dispatch is 9-12 months. A compressed calendar:

1. Month 0-2 — Planning and paperwork. Engineering documentation, BOM, variant plan, AIS mapping, agency selection, slot booking. AIR / regulatory agent appointment if foreign.
2. Month 2-4 — Component approvals. Tyres (AIS-112), lights (AIS-034 series), ROPS (AIS-139), safety-critical cab components. These can and should run in parallel with preparing assembled-vehicle samples.
3. Month 3-6 — Sample preparation and shipping. Lead time for engineering samples, in particular for foreign-sourced samples. Allow for inspection at origin, shipping, customs, and on-arrival PDI.
4. Month 4-8 — Assembled-vehicle type-approval at ARAI or ICAT. Type-III tests. Emission testing for TREM compliance. Retest cycles where required.
5. Month 5-8 — FMTII commercial testing in parallel. AIS-017 Part 2 testing at Budni. For subsidy-eligibility relevance.
6. Month 6-9 — CoP (Conformity of Production) setup. Line audits, QC plan, CoP sample selection and testing.
7. Month 8-10 — Grant of approval. Registration preparation. Final documentation, state RTO liaison, dealer readiness.
8. Month 9-12 — First-dispatch readiness. Bulk production, CoP first-cycle, post-grant monitoring.

Fast-tracking below 9 months is possible with exemplary preparation and favourable slot availability, but carries compounding risk if any sub-test fails.

7. Fees and budget lines

BIS, ARAI, ICAT, and FMTII each publish fee schedules. For planning purposes, the order of magnitude for a single tractor Type-III approval programme:

• CMVR type-approval fees (ARAI or ICAT): in the range of ₹10-30 lakh per model family, depending on variant count and test scope.
• Emission testing (TREM-IV or V): additional line item, typically ₹4-10 lakh per engine family.
• FMTII commercial testing: typically ₹2-5 lakh per tractor.
• Component-level approvals (tyres, lights, ROPS etc.): ₹50,000-₹2 lakh each, depending on supplier and component.
• Sample preparation, shipping, and engineering time: the largest internal cost line, highly OEM-specific.

These figures are indicative for planning; formal quotes are required at the point of agency engagement.

8. Variant and family-approval strategy

Homologation cost per unit drops sharply when variant and family planning is done well. A well-structured variant plan:

• Defines the variant boundaries at type-approval stage — which parameters can vary without triggering fresh approval (colour, trim, non-safety options) versus which trigger Type-I, Type-II, or Type-III (hardpoints, engine configuration, weight class).
• Files the base variant at Type-III; files sibling variants as Type-II or Type-I as the change set allows.
• Documents the parameter ranges approved so subsequent variants can be filed quickly.

Foreign OEMs with global platforms often carry a strong variant discipline already; the Indian homologation plan should mirror it, not redo it.

Parallel testing strategy — running ARAI or ICAT alongside FMTII

Tractor-family homologation has two independent testing tracks that most OEMs treat as sequential. Running them in parallel can compress the overall calendar by 6-10 weeks without any incremental risk.

Why it works. CMVR and FMTII cover different regulatory scopes (on-road type-approval versus agricultural-performance testing) but test different aspects of the same sample. Engine emissions, brake performance, lighting, and safety-structure tests happen at ARAI/ICAT. PTO performance, drawbar pull, hydraulic-lift capacity, and field-performance tests happen at FMTII. Different benches, different teams, different test schedules.

When it gets blocked. The most common blocker is a single-sample approach — the OEM sends one unit to ARAI/ICAT, and that unit is under test there for 6-10 weeks before it can be released to FMTII. If the OEM builds two production-complete samples, both tracks can begin in parallel week.

Second-sample economics. A second sample costs the marginal production cost of one tractor plus sample-movement logistics. On a programme that saves 6-10 weeks by going parallel, the sample cost is almost always recovered in avoided revenue-deferral.

Documentation alignment. The CMVR application and the FMTII application reference the same specification dossier. Preparing the documentation for both simultaneously, with consistent nomenclature and BOM references, is routine once programmes are set up for it; OEMs doing this for the first time sometimes generate inconsistencies that cause re-work.

Slot synchronisation. Both agencies maintain slot calendars. Getting slot dates coordinated within a 2-3 week window of each other is the operational work of parallel execution. Doing this well requires a named programme manager who owns the calendar view for both.

Parallel testing is not always available — some variant-approval paths under CMVR reference FMTII test reports in a specific order, and the regulatory partner should confirm the dependency pattern for the specific model family. For most tractor-family programmes we've run, full parallel execution has been feasible.

9. Conformity of Production (CoP)

CoP is the continuous evidence that the production line continues to match the approved sample. Obligations include:

• Regular line audits by the test agency.
• Periodic sample testing of production units.
• Process controls for any critical-to-approval parameters (torque, emission-related settings, hydraulic performance, brake performance).
• Prompt notification of any manufacturing changes.

CoP economics: setting it up at first approval is materially cheaper than retrofitting six months after launch. OEMs who have retrofitted CoP typically report 2-3× the calendar cost and a higher risk of corrective-action observations.

Selecting a regulatory consulting partner — five criteria

The difference between a strong and a weak regulatory partner compounds across an 8-12 month programme. Criteria that matter:

Direct, not sub-contracted, relationship with the test agency. The partner's own people should have worked approvals at ARAI and ICAT within the last 24 months. Sub-contracting to a freelancer for the agency-facing work produces inconsistent results and breaks down at the first deficiency observation.

Named programme manager, not a generic account manager. Homologation programmes have hundreds of micro-decisions (which IS applies, how to sequence a component approval, how to respond to a specific deficiency letter). The best programme managers are engineers by training with 5+ years of direct test-agency interaction; they are not sales people. Ask to meet the named programme manager before engagement, not just the partnership lead.

Fluency in both CMVR and FMTII, plus BIS where relevant. A partner whose practice is CMVR-only will sub-contract FMTII and BIS work, which reintroduces the fragmentation the engagement was meant to solve. For full-scope programmes, end-to-end coverage under one roof is almost always the operationally cleaner choice.

Transparent fee model. Fixed-fee-per-milestone pricing with clear definitions of "milestone achieved" is easier to manage than time-and-materials billing. Hybrid models (fixed for agency interaction, time-and-materials for engineering support) can work where the engagement scope is uncertain.

Willingness to name risks. Good regulatory partners tell you about the risks of your programme at the engagement stage — slot availability, sample-preparation concerns, CoP gaps. Partners who describe everything as on-track from day one are either unrealistic or not reading the programme closely.

10. Common homologation pitfalls

After approval — the first 12 months of post-approval life

Type-approval is a milestone, not a finish line. The first 12 months after grant require specific operational discipline that many OEMs discover the hard way.

Month 0-1 — First production under the approval. Initial production run is typically watched closely by the agency's CoP team. Any batch-to-batch variance on critical-to-approval parameters triggers a question. Having the QC team dry-run CoP procedures before the approval lands is a material de-risker.

Month 2-4 — First CoP audit. A formal CoP audit visits the plant, reviews recent production records, samples production units for testing, and verifies that the manufacturing process continues to match the approved sample. Passing the first CoP audit cleanly sets a pattern for ongoing surveillance.

Month 4-8 — Variant filings begin. Most tractor families have sibling variants that were planned but not submitted at the initial Type-III approval. These file now as Type-II or Type-I, referencing the baseline. Variant filings are faster than first-approval filings — 4-8 weeks typical — provided the baseline is clean.

Month 6-10 — State RTO rollout completes. The initial approval is accepted by the priority-state RTO first; other states accept it on a rolling basis, sometimes with a small internal-process lag. OEMs aiming at national dispatch by month 12 should test registration readiness in each priority state early in the 12-month period.

Month 8-12 — Surveillance-cycle preparation. The first annual surveillance cycle approaches. Preparing for it — documentation review, internal audit of the quality-control plan, verification of records retention — is cheaper than responding to surveillance observations.

Surveillance and renewal economics

CMVR type-approval does not have a fixed "renewal" date the way BIS licences do. The approval stays valid as long as Conformity of Production is maintained and no material product change is unreported. Economically, the ongoing cost is:

• CoP audit cycle costs (agency fee + internal preparation time)
• Periodic testing of production samples (either at the agency or at an accredited lab, per the CoP plan)
• Variant approvals as the product line evolves
• Re-homologation when standards shift (TREM-IV to TREM-V, future safety-standard updates, component-AIS updates)

Planning for the sustained cost of CMVR homologation is something foreign OEMs routinely under-budget in their first year. A reasonable planning estimate: 10-15 percent of the initial homologation cost as annual ongoing burden for an actively-selling tractor family.

Sample logistics — from origin to test agency

For foreign OEMs, the physical movement of the engineering sample from the origin plant to the CMVR test agency in India is routinely the most mis-estimated line item in the calendar. Planning assumptions:

• Origin pre-despatch inspection. Allow 1-2 weeks at the origin plant for final inspection, documentation compilation, and carrier booking. Samples despatched to a CMVR agency without proper internal sign-off tend to generate deficiency observations on documentation consistency.
• International freight. Sea freight from Europe or North America to Mumbai or Chennai is 4-6 weeks. Air freight is 1 week but 5-8x the cost — worth doing for final-push programmes, not for the default.
• Customs clearance in India. 3-7 working days for a well-prepared import, provided the bill of entry lists the correct HS code for a regulatory test sample and any duty exemptions (temporary import for testing, if applicable) are pre-filed. Poor documentation extends this to 2-3 weeks.
• Ground transit to the test agency. Mumbai to Pune (ARAI) is 3-4 hours plus handling. Chennai or Mumbai to Manesar (ICAT) is 3-5 days by trailer. Mumbai or Chennai to Budni (FMTII) is 2-3 days.

An OEM who plans a 9-month total programme and budgets 3 weeks for "sample ship and reach" usually overruns. A realistic planning budget for origin-to-test-bench is 8-10 weeks door-to-door.

11. When to engage a regulatory partner

Foreign OEMs entering India, multi-variant programmes, and re-homologation programmes (TREM transitions, safety-standard updates) are the scenarios where a regulatory consulting partner earns their fee quickly. The partner owns the interface with the test agencies, sequences parallel tracks, manages CoP from day one, and keeps the engineering team focused on product rather than on MoRTH correspondence.

AgPro's regulatory practice has closed CMVR approvals across ARAI and ICAT and commercial testing at FMTII for Indian and international OEMs. Our working mode is a named programme manager owning the full regulatory calendar, and an escalation path into MoRTH, BIS, and the state RTOs as approvals land.

Explore our regulatory & homologation service →

Frequently asked questions

Do all tractors need CMVR type-approval?

Tractors intended for on-road registration require CMVR type-approval under Rule 126. Non-road self-propelled agricultural machinery (combines, self-propelled sprayers for enclosed use) routes through FMTII under AIS rather than CMVR.

What is the difference between ARAI and ICAT?

Is FMTII testing required for all tractors?

How long does a new tractor model take to homologate?

What is CoP?

What are TREM norms?

Do foreign OEMs need an authorised Indian representative?

Can I run ARAI and FMTII testing in parallel?

How often does a CMVR type-approval need to be renewed?

What does the first CoP audit check?

What happens if production shifts to a new plant?

Sources & references(8), 8 items

Written by

Devendra K Jha· Director, AgPro Consulting

Founding Director of AgPro Consulting. Agricultural engineer with 28+ years across agri inputs, mechanization, and enterprise leadership roles.

• B.Tech Agricultural Engineering
• 28+ years agri-enterprise leadership

LinkedIn