RailInfra Projects Intelligence · Signalling & Telecom

Kavach: India’s indigenous train protection system, explained for commercial teams

A practical briefing on how Kavach works, what Version 4.0 changes, and why signalling, telecom and safety suppliers should track deployment as a multi-year demand signal—not a one-line news item.

---

Why this matters

Kavach (“armour”) is Indian Railways’ indigenous Automatic Train Protection (ATP) system. It is a safety overlay on existing signalling: it does not replace interlockings or lineside signals. It supervises movement authority and can apply brakes if the crew does not respond in time.

For commercial teams, Kavach is not only a safety story. Each commissioned route-kilometre packages trackside electronics, radio/OFC infrastructure, station interfaces, locomotive fitment and long-cycle maintenance—exactly the kind of filtered project signal RailInfra Projects is built to surface under Signalling & Telecom.

Problems Kavach is designed to reduce

• Signal Passed at Danger (SPAD) — intervention when a train approaches or passes a restrictive aspect without correct authority
• Overspeed — enforcement of permanent and temporary speed limits
• Collision risk — head-on, rear-end and selected side conflicts when both trains and the section are equipped
• Low-visibility operations — in-cab information that reduces dependence on reading lineside signals in fog

The system is specified against a high safety integrity target (SIL-4), aligned with railway safety standards in the CENELEC / EN 50126–50129 family.

Architecture in three layers

1. Trackside / wayside
RFID tags on sleepers, stationary Kavach units at stations, remote interface units, radio towers and antennas, and optical fibre. These provide location references and a live link to interlocking data (signals, points, occupancy).

2. Onboard (locomotive / trainset)
A vital computer, RFID readers, radio, odometry and speed sensors, a Driver Machine Interface (DMI), and a Brake Interface Unit (BIU). The onboard stack knows position and speed, displays limits, and can command service or emergency braking.

3. Network and operations support
Station-to-station links, monitoring and key-management style functions support soft handover between stations, logging, fault handling and SOS messaging.

RFID tags (often duplicated) carry track identification and absolute location. The onboard unit interpolates between tags using wheel/speed sensors and corrects drift. Radio—historically UHF, with Version 4.0 strengthening modern radio / LTE-R pathways and station-to-station OFC interfaces—carries movement authority and live signalling data. GPS is used heavily for time synchronisation, not as the sole safety position source.

A typical supervision cycle

1. Interlocking / stationary Kavach knows signal aspects, points and occupancy.
2. Onboard Kavach fuses RFID, odometry and radio packets to know where the train is and which track it occupies.
3. The system computes permitted speed against distance to the next constraint (restrictive signal, speed restriction, conflicting movement).
4. The DMI warns the pilot; if the speed profile is violated, progressive braking is applied via the BIU.
5. Equipped locomotives can exchange information for collision-avoidance logic when within radio range. Public feature lists also include auto-whistle near level crossings, SOS and central monitoring.

Exact alarm and brake thresholds vary by version and configuration; treat published numbers as indicative, not universal operating rules.

Version 3.2 to Version 4.0

Version 3.2 delivered early large field experience, notably on South Central Railway (on the order of about 1,465 route-km of deployment experience cited in official material).

Version 4.0 is the RDSO-approved specification oriented to India’s dense, multi-line, large-yard network. Publicly highlighted improvements include better location accuracy, richer signal-aspect information in large yards, station-to-station Kavach interface over OFC, and a more direct interface to electronic interlocking. Radio evolution toward LTE-R is part of the 4.0 narrative. The version is positioned for large-scale national rollout and higher-speed contexts where infrastructure permits (often described in the ~160 km/h class).

Why rollout is “telecom-scale”

A Kavach section is not only software on the locomotive. Full supervision requires trackside RFID and equipment, stationary Kavach with interlocking interface, optical fibre and towers, station data centres, and Loco Kavach on every locomotive (and equivalent onboard fitment on trainsets) that must run under full supervision on that route.

Coverage is therefore only as strong as the weakest layer. Mixed fleets and gaps between equipped and unequipped trains limit protection until both the route and the traction units are live.

Deployment signal (order of magnitude)

Specification 4.0 was approved in mid-2024. High-profile 4.0 stretches on high-density corridors (including sections on the Delhi–Mumbai axis) followed through 2024–26. Commissioning batches of several hundred route-kilometres in a single package have been reported. Parliament and ministry updates cite multi-thousand route-kilometre programmes, large locomotive fitment drives and multi-thousand-crore cumulative spend. Exact kilometre and locomotive counts move with each official release—use the latest PIB or Railway Board table as the authoritative snapshot.

A recent commercial-intelligence example: sanction for Kavach 4.0 on the remaining about 712 route-km of Moradabad Division (Northern Railway) at roughly ₹170 crore, consistent with the wider 4.0 expansion pattern tracked in the RailInfra Projects database.

Kavach versus ETCS (commercial intuition)

Kavach is optimised for Indian Railways’ diverse legacy signalling, with RFID-heavy location and a national IR stack. ETCS is the European interoperability baseline (balises, GSM-R / Euroradio, Levels 1/2/3). Indian official messaging positions Kavach as lower cost at domestic scale while meeting high integrity targets. Interoperability with ETCS appears in longer-term roadmaps rather than as current day-one reality on the network.

Limits that matter to buyers and suppliers

• Full protection needs an equipped route and equipped traction.
• Kavach does not by itself fix broken track, road vehicles at crossings, or every yard-shunting edge case; isolation and staff-responsible modes exist for operational flexibility.
• Rollout is constrained by capital programmes, loco-shed capacity, OFC and tower works, multi-vendor interoperability testing and certification—not only by “installing boxes.”

How RailInfra Projects tracks this

Under the Signalling & Telecom package, Kavach implementation is treated as a live project stream: sanctions, zone packages, locomotive fitment, OFC/tower works, awards and commissioning milestones. That is the same discipline applied to track construction, electrification, rolling stock and station programmes—filter noise, keep commercial signals.

This article is a public briefing. Project-level records, cost fields and milestone timelines remain available inside the RailInfra Projects intelligence service.