Kavach vs the World: India’s Overlay Safety System Gets a ₹483.65-Crore Push

Fleet Readiness: Upgrading 436 Locomotives at ₹373.82 Crore

The second—and larger—component of the proposal allocates ₹373.82 crore for the modification, upgradation, and programming of 436 locomotives under Western Railway. This covers a broad cross-section of the zone’s electric locomotive fleet, ensuring that engines operating on Kavach-equipped routes are fully compatible with the system.

The scope of work includes installing onboard Kavach units, integrating braking interfaces, upgrading control electronics, and embedding software that enables locomotives to continuously exchange safety-critical data with track-side equipment and nearby trains. These upgrades are essential because Kavach’s core safety logic—such as enforcing speed restrictions or initiating automatic braking—resides partly onboard the locomotive.

Without this fleet-level retrofit, route-level installation alone would leave safety benefits unrealised. The locomotive programme therefore represents the largest share of the capex, reflecting both the hardware intensity and the scale of integration required across hundreds of engines.

Kavach in Context: Indigenous Technology, Phased Expansion

Kavach is an indigenously developed train protection system, evolved through the Research Designs and Standards Organisation (RDSO) and Indian Railways’ signalling ecosystem, with the stated objective of reducing accidents arising from human error. It is designed to be interoperable across zones, enabling trains fitted with Kavach to operate safely on any Kavach-enabled section of the network.

Indian Railways has been rolling out Kavach in a phased manner, prioritising high-density routes and sections with complex operations. Experience from earlier deployments has underscored that partial implementation—either on track or rolling stock—creates operational bottlenecks. As a result, recent proposals, including Western Railway’s, increasingly bundle route coverage with locomotive readiness to ensure end-to-end functionality.

Kavach in Global Context: Overlay vs End-to-End Train Protection — and What That Means for Safety

Globally, modern train protection systems follow two distinct safety architectures, and understanding this distinction is critical to evaluating Kavach.

1) End-to-End Systems: Centralised, Network-Level Safety: Systems such as ETCS Level 2/3 (Europe) and Positive Train Control (PTC) in the United States are end-to-end train control systems. In these architectures, safety is enforced through a continuous, centrally supervised control loop:

• A central traffic management or radio block centre maintains a live, network-wide view of train positions.
• Continuous digital communication (GSM-R/FRMCS in Europe; radio back-office systems in the US) feeds movement authorities directly to locomotives.
• Trains are permitted to move only within centrally issued movement authorities, and braking curves are enforced end-to-end by the system.

From a pure engineering perspective, this model offers the highest theoretical level of systemic safety, because risk is managed at the network level rather than locally. However, it comes with very high costs and operational rigidity. Public disclosures indicate that PTC deployment in the US exceeded USD 15–20 billion nationally, driven by central servers, radio infrastructure, interoperability across multiple private railroads, and per-locomotive retrofits. ETCS Level 2 deployments in Europe routinely cost several crore rupees per kilometre, particularly where legacy signalling must be replaced.

2) Overlay Systems: Local Enforcement on Top of Existing Signalling: Kavach belongs to the overlay class, closer in concept to ETCS Level 1 overlays, though implemented with indigenous design choices. In an overlay system:

• Existing signalling, interlocking, and block systems remain intact.
• Safety enforcement is shifted closer to the train, through onboard computation and local radio exchange with track equipment.
• Instead of central movement authorities, the system continuously checks whether the train is about to violate a safety envelope—such as passing a red signal, overspeeding, or entering an occupied block—and automatically applies brakes if required.

This architecture does not eliminate central signalling; rather, it adds an independent safety layer that intervenes when human response fails.

Is End-to-End “Safer” Than Kavach?:

In abstract terms, yes—end-to-end systems offer stronger systemic control, especially on homogeneous, lower-density networks where traffic patterns are predictable and capital costs can be absorbed. But safety is not only a function of architecture; it is also a function of coverage, reliability, and implementation speed.

For a network the size of Indian Railways—with mixed traffic, extremely high density, legacy signalling diversity, and thousands of locomotives—an end-to-end rollout would take decades and absorb extraordinary capital. During that transition, large portions of the network would remain without advanced protection.

Kavach’s design trades maximum theoretical control for maximum practical coverage. By avoiding wholesale signalling replacement and centralised control, it enables faster deployment across large route-kilometres and locomotive fleets, raising the baseline safety level everywhere rather than creating pockets of very high safety amid vast uncovered stretches.

The Safety Logic Behind Kavach’s Design Choice:

Technically, Kavach concentrates on the accident classes that dominate Indian Railways’ risk profile—SPAD incidents, collisions within block sections, and overspeeding due to delayed human response. By enforcing braking locally and automatically, it addresses these failure modes directly, even if it does not manage traffic at a fully centralised network level.

In effect, Kavach reflects a deliberate engineering judgement: a slightly lower ceiling of control in exchange for faster, wider, and more reliable safety enforcement across a complex national network. In safety terms, that trade-off prioritises risk reduction at scale, rather than perfection on limited corridors.

Execution Risks and Bottlenecks: Why Safety Rollouts Often Slip

Railway safety systems rarely fail on design; they falter at execution scale. Experience from earlier Kavach deployments and comparable signalling upgrades shows that the most common bottlenecks arise not from hardware installation, but from operational integration.

One key constraint is locomotive availability. Retrofitting requires locomotives to be withdrawn from service for installation, testing, and certification—an inherently capacity-constrained process in high-utilisation fleets. Another challenge lies in interoperability during partial rollouts, where Kavach-equipped trains must safely coexist with non-equipped rolling stock and legacy signalling logic.

Training and standard operating procedures also matter. Drivers, signal maintainers, and control staff must adapt to new intervention protocols, especially where automatic braking overrides manual control. Delays in training or procedural harmonisation can slow commissioning even after physical installation is complete.

Western Railway’s proposal addresses some of these risks by bundling route-side installation with locomotive upgrades, reducing the mismatch between infrastructure readiness and fleet capability—a sequencing error that has constrained earlier safety programmes.

What the Numbers Reveal: Cost per Kilometre, Cost per Locomotive

Breaking down the ₹483.65-crore proposal into unit economics clarifies both scale and strategy. The ₹109.83-croreallocation for 307 route kilometres translates to an approximate ₹0.35–0.36 crore per route-km for track-side Kavach deployment. This includes hardware, integration with signalling, and communication systems.

The ₹373.82-crore earmarked for 436 locomotives implies an average upgrade cost of roughly ₹0.85–0.90 crore per locomotive. The higher per-unit cost reflects the concentration of technology onboard—computing units, braking interfaces, redundancy systems, and extensive testing—rather than linear infrastructure.

Together, these ratios illustrate why rolling-stock readiness dominates capex in safety modernisation. Track-side investments amortise across thousands of train movements, while each locomotive represents a self-contained safety system. Scaling Kavach nationally therefore hinges less on kilometres covered and more on fleet conversion velocity.

Why This Matters

Railway safety upgrades at scale require simultaneous investment in infrastructure and rolling stock, and the ₹483.65-crore proposal illustrates the capital intensity of moving from pilot deployments to operational coverage. By combining 307 km of track-side installation with 436 Kavach-ready locomotives, Western Railway’s plan addresses a key execution risk that has slowed earlier safety programmes.

If approved and implemented as proposed, the project would materially strengthen operational safety on an important Western Railway corridor and expand the pool of Kavach-equipped locomotives available for wider deployment. In the broader context of Indian Railways’ safety modernisation, the proposal signals a shift from selective trials toward systematic, zone-wide integration of indigenous train protection technology.