Professional Documents
Culture Documents
hkluho;iuj;pojipokpojoihoihoih;oij;pojpoij;o
ihyi9hn
CONCERT - COUNTRY-WIDE NETWORK FOR COMPUTERIZED ENHANCED
RESERVATION AND TICKETING :
It is a fully automated passenger reservation system. It allows passengers to
do a booking from anywhere for a journey in any train in any class from
anywhere to anywhere across counter. Concert handles reservations,
modifications, cancellation/ refunds, 39 supervisory on-line functions ,and 30
on-line enquiries. It handles 265 concessions, 165 coach types and 40 types
of quotas
In current PRS network has more than 2600 POPs (points of presence i.e.
booking locations) spread across the country with around 9100 POS (points
of sale i.e. terminals).
Concert System makes fare calculation and accounting easy. Easy Enquiry
Distributed Architecture of PRS.
4 Sites (Delhi, Mumbai, Chennai, Kolkata) which maintains data of different
trains
5th site is also included for disaster recovery.
Data is divided into two parts.
1) Static data: data which changes rarely. Such as fare data, train data etc.
This data is kept on each server
2) Dynamic data: data which changes continuously e.g. Passenger data, PNR
data. Current booking data. This data kept on single server. Location of
data is decided by train starting station. Or first digit of PNR Number.
RTR (Reliable Transaction Router) as Middleware: RTR is used to transfer
request to server.
Reservation based on the TDRC (Train, date, Route, Class): to do reservation
in particular train, one must know train number, Journey Date, Route (i.e.
Source and destination) and class.
ARP (advanced Reservation Period) Rules: Currently you can book ticket 120
days prior to date of journey.
Different Quota & Classes: there are 40 types of quotas and 7 classes.
Database: Oracle
Java
JRTR to communicate with PRS
SERVERS
Sys Mgmt
Monitor
TP MANAGER
RTR
Accounting
Allocation
PNR
Performance
SECURITY WALL
Event log
BUS ARCHITECTURE
CLIENT
Archival
CLIENTS
Ext Interface
Reservation
IVRS
Cancellation
RAPID
Modification
MHS
Booking Flow :
Flow of booking process is as shown in diagram.
First user(i.e Counter Person) will fill the form with details Passenger name,
train no. Date of journey, source destination, class etc. System will validate
form. Is train running on given date. Source and destination belongs to
given train etc. If everything is ok, then system will generate PNR for given
transaction and calculate fare. After this transaction will start which includes
berth allocation and PNR updation. In berth allocation it will set bit of given
berth as 1 means allocated and in PNR updation it writes passenger details
in file. In this process it will lock records of file till both process finished. All
other restrictions are checked here e.g. passenger wants upper berth. Book
only if confirmed berth. Book in same coach.
After that it will commit all data. Here 2 phase commit is used i.e. if both
writes are successful then final commit will be processed else any commit
fails then both transactions will be rolled back.
Now details of tickets are displayed to user i.e. fare and berth. Now user is
asked to proceed or flush. If flush is selected then PNR is flushed and berth
is released.
Else accounting is done and ticket is printed. If ticket is not printed then
again PNR is flushed and berth is released and accounting is done. And if
ticket is printed successfully then control is returned to booking page. And
another booking will start.
File Structure:
File structure for booking process is as shown fig.
There are three file used for booking process.
1) Maintaining TDRC information and sequence of bits. TDRC is train number,
Date of journey, source and destination, and class. number of bits
corresponds to number of berths for given TDRC. If bit is set then berth is
booked else it is vacant. Here searching of record is done in O(1)
T D R C - PNR
T D R C - PNR
T D R C PNR
.
.
.
.
.
Introduction to NGeT
The main purpose of NGeT website is book ticket from website. NGeT is
complete interface software between the IRCTC front-end server and the back
end Alpha server. Complete e-reservation and enquiries back end
servers. Ticket printing and reset facilities in existing client. Accounting
reports for the IRCTC transactions. Next Generation e-Ticketing System. It is
one client to PRS. User Can book ticket from any location at any time. Easy to
generate reports for NGeT transactions Paperless ticket