Skip to main content
Final NotificationEV Regulations

AVAS requirement for electrified M and N category vehicles

The Central Motor Vehicles (First Amendment) Rules, 2026 introduce Acoustic Vehicle Alerting System requirements for electrified M and N category vehicles, using AIS-173 until corresponding BIS specifications are notified.

Notification numberG.S.R. 07(E)
Date2 January 2026
Vehicle categoryElectrified vehicles of categories M and N
Effective date1 October 2026 for new models; 1 October 2027 for existing models

Applicability

Applies to new and existing electrified passenger and goods vehicle models in M and N categories according to the phased dates stated in the notification.

Key requirements

  • Fit an Acoustic Vehicle Alerting System on applicable electrified vehicles.
  • Demonstrate audibility compliance with AIS-173, as amended from time to time.
  • Apply the new-model requirement from 1 October 2026.
  • Apply the existing-model requirement from 1 October 2027.
  • Maintain type-approval evidence for the AVAS installation and vehicle configuration.

OEM impact

  • Add AVAS hardware, control logic and diagnostics to affected vehicle programs.
  • Update homologation plans, variant matrices, drawings, software baselines and compliance declarations.
  • Plan separate readiness gates for new models and carry-over models.

Supplier impact

  • AVAS suppliers need production-intent hardware, acoustic performance data and change-control evidence.
  • Software and body-control suppliers may need interface, diagnostic and calibration updates.
  • Component capacity and PPAP timing must support both implementation phases.

Testing / homologation impact

  • Vehicle-level audibility testing is required against AIS-173 conditions and limits.
  • Installation position, sound characteristics, software strategy and variant coverage require review with the test agency.
  • Changes affecting emitted sound may need extension or revalidation assessment.

Action points

  • Identify every M and N electrified model within the two implementation windows.
  • Freeze the AVAS sourcing and vehicle-integration concept.
  • Book test-agency capacity and align approval evidence with launch milestones.
  • Add AVAS conformity checks to production control and change management.

Open questions

  • Which carry-over variants can be covered through extension rather than a new approval?
  • How will future BIS specifications transition from AIS-173 for approvals already granted?
  • Which software or sound-file changes will trigger revalidation?

Official references

Disclaimer

This update is an educational engineering summary, not legal advice. Always verify the current Gazette text, amendments, corrigenda, implementation circulars and test-agency interpretations before making a compliance decision.