Evolution of Indian Railways’ Passenger Reservation System

Booking a train ticket in India today takes just a few taps on a smartphone. But four decades ago, it meant standing in long queues, filling out forms in triplicate, and hoping the clerk behind the counter could find you a berth. The transformation of this experience is one of the most remarkable e-governance stories of our time, and it all began with a modest pilot project that would eventually become one of the world’s largest computerized reservation networks.

The pre-computerization era and the need for change 🔗

Before automation arrived, Indian Railways ran its reservation process entirely by hand. Clerks maintained giant ledgers, passengers queued for hours, and a single booking often required multiple signatures and manual cross-checks across different counters. This system was not just slow, it was error-prone and vulnerable to corruption. Ticket touts thrived, and ordinary travellers often faced confusion about seat availability until the very last moment.

The scale of the challenge was staggering. Indian Railways carries over 22 million passengers every single day, making it one of the largest passenger rail networks on the planet. Handling reservations for a fraction of those travellers through paper-based methods was simply not sustainable. The push for computerization was driven by the need to reduce human error, curb unauthorized transactions, optimize capacity, and improve the overall experience for millions of people who depended on trains for their daily lives.

The 1985 pilot and the early years 🔗

The story of the Passenger Reservation System (PRS) begins on 18 October 1985, when the first computerized reservation system was launched at New Delhi station on an HP 1000 mini-computer. This was a genuine pilot, covering only a handful of trains to test whether the software could match the accuracy of manual bookings. For safety, every computerized transaction was also verified manually during those early months.

The pilot worked. Within two years, the system expanded to three other major metros. Mumbai came online in June 1987, Calcutta in July 1987, and Chennai in October 1987. A fifth node was added at Secunderabad in July 1989, though it ran on a Cyber computer system while the other four used VAX/VMS machines. This formative stage gave birth to an application called IMPRESS (Integrated Multi-train Passenger Reservation System), built in FORTRAN to handle the complex logic of berth allocation, fare calculation, and waitlist management.

A fragmented network 🔗

There was, however, a significant limitation. The five PRS centres operated as independent islands. Each had its own local database, and they could not exchange information with one another. If you were in Delhi and wanted to book a ticket on a train originating in Chennai, you were out of luck unless that train passed through Delhi. This geographical fragmentation created artificial barriers for passengers and was inefficient for the Railways themselves.

The 1999 breakthrough: CONCERT and the unified network 🔗

The watershed moment arrived in 1999. Following years of development by the Centre for Railway Information Systems (CRIS), an autonomous organization under the Ministry of Railways established in 1986, the five PRS nodes were finally networked together. The system that achieved this feat was called CONCERT, short for Country-wide Network for Computerized Enhanced Reservation and Ticketing.

CONCERT had actually been in the works since January 1995, when its first prototype was developed and tested at Secunderabad. But the full nationwide interconnection of the five PRS systems was completed on 18 April 1999. This was accompanied by a hardware upgrade from VAX/VMS servers to Alpha/VMS servers, giving the network the processing muscle it needed to handle transactions from across the country as a single, unified system.

Why this mattered 🔗

For the first time in history, a passenger in any computerized counter could book a ticket for any train running anywhere in India. The artificial regional boundaries that had restricted the system dissolved overnight. This was not just a technical achievement; it was a transformation in how a billion-strong country could access a public service. It laid the foundation for everything that followed, from internet ticketing to mobile apps.

Technical architecture: hardware, software, and networks 🔗

Understanding the PRS requires a look under the hood. The system is built on a three-tier client-server architecture, with server clusters connected through a core network of leased lines. The regional centres at Delhi, Mumbai, Kolkata, Chennai, and Secunderabad form the backbone, and each of them handles transactions for the stations in its territory.

The hardware foundation 🔗

The backbone of the PRS infrastructure has been HP Alpha Servers, chosen for their reliability and ability to process massive transaction volumes. Over time, these have been complemented and gradually upgraded with blade servers running 64-bit Itanium 9340 processors, using the OpenVMS 8.4 operating system with an in-house CRIS proprietary database and HP Reliable Transaction Router (RTR) as middleware. The network uses CISCO routers on 2 Mbps DOT lines arranged in a mesh topology, running on TCP/IP and DECNET protocols.

Multi-layered connectivity 🔗

To ensure reliability across a country as diverse as India, the PRS relies on a multi-layered network. Primary connectivity comes through dedicated leased lines between the major nodes. For remote locations where wired connections are difficult, VSAT (Very Small Aperture Terminal) satellite links provide coverage. ISDN lines serve as tertiary backup in case the primary and secondary networks fail simultaneously. This layered design is what allows even stations in remote corners of the country to maintain reliable links to the central reservation databases.

Services beyond ticketing 🔗

Modern PRS is far more than a ticket booking engine. It has grown into a comprehensive passenger information platform accessible through multiple channels.

Core functions 🔗

The system handles reservation for confirmed, RAC (Reservation Against Cancellation), and waitlisted tickets. RAC was introduced as an integral component of the computerized PRS in the 1980s to manage overbooking and buffer against cancellations, allowing passengers to board a train with a partial berth allocation that could be upgraded if a confirmed ticket was cancelled. Beyond booking, the PRS provides cancellation services, PNR status enquiry, journey planning, fare enquiries, and seat availability checks.

Multiple access channels 🔗

Passengers interact with the PRS through a variety of interfaces designed for different levels of technology access. Physical counters remain available at over 8,000 locations across the country. Interactive Voice Response Systems (IVRS) allow enquiries over the phone, with the Integrated Railways Helpline and Enquiry System accessible at the number 139. Touch-screen kiosks at major stations and, most significantly, the internet have brought the PRS directly into the hands of passengers.

The internet revolution and IRCTC 🔗

The next great leap came with the web. Indian Railway Catering and Tourism Corporation (IRCTC) was incorporated in 1999, and online ticketing was launched on 3 August 2002. Suddenly, the need to visit a counter became optional. Over the years, IRCTC became the consumer-facing digital arm of the PRS, even though the underlying reservation engine continued to be operated by CRIS.

The scale today is extraordinary. The e-ticketing system was upgraded to the Next Generation e-Ticketing (NGeT) platform on 28 April 2014, capable of handling more than 30,000 ticket bookings per minute, and on 12 March 2025 it set a record by booking 30,155 tickets in a single minute. During financial year 2024-25, digital platforms accounted for 86.38% of all reserved tickets booked on Indian Railways, a dramatic shift from the counter-dominated world of just two decades ago.

The PRS today: scale and reach 🔗

The numbers tell a story of extraordinary scale. According to a November 2021 report by the Standing Committee on Railways, the PRS processes over one crore transactions per day involving about five crore passengers on average, with a maximum capacity of 28,000 transactions per minute. These figures place the PRS among the largest online transaction processing systems anywhere in the world.

Reservations can now be made up to 60 days in advance, with various quotas such as ladies, senior citizen, tatkal, and premium tatkal catering to different passenger needs. The system supports over 50 categories of fare concessions as part of the Railways’ social service obligations.

Continuing evolution 🔗

The PRS continues to evolve. Indian Railways has been upgrading its telecom backbone with IP MPLS technology, which supports the Passenger Reservation System alongside other mission-critical applications, and has been commissioned at 1,396 railway stations. The movement toward a cloud-native, microservices-based next-generation ticketing platform is also underway, reflecting modern software engineering practices.

From a single HP 1000 mini-computer at New Delhi in October 1985 to a cloud-era platform serving hundreds of millions, the PRS illustrates how thoughtful technology adoption can transform a public service. It also shows that successful e-governance is not just about the latest tools; it is about making the service work for everyone, from the digitally fluent youngster booking on an app to the pensioner who still prefers a counter.

What do you think? Considering that nearly 86% of reserved tickets are now booked digitally, should Indian Railways eventually phase out physical counters, or should they remain to serve those without digital access? And what lessons from the PRS journey can other large public sector systems learn when undertaking their own digital transformations?

References

1. https://en.wikipedia.org/wiki/Indian_Railways
2. https://sathee.iitk.ac.in/sathee-railway-exams/student-corner/railway-gk/operations/reservation-system/
3. https://www.railnewscenter.com/how-are-computerized-reservations-done-what-are-concert-prs-impress-poet-and-uts/railway-employee/
4. https://en.wikipedia.org/wiki/Centre_for_Railway_Information_Systems
5. https://www.quora.com/What-is-the-software-and-IT-infrastructure-behind-Indian-Railways-Ticket-Reservation-System-of-IRCTC
6. https://grokipedia.com/page/Reservation_against_Cancellation
7. https://www.irctc.com/contact-us.php
8. https://en.wikipedia.org/wiki/Indian_Railway_Catering_and_Tourism_Corporation
9. https://irctc.com/internet-ticketing.php
10. https://prsindia.org/policy/report-summaries/passenger-reservation-system-of-indian-railways
11. https://www.pib.gov.in/PressReleasePage.aspx?PRID=2252124&reg=3&lang=1