No official Railway Board PDF has been traced for this entry yet. The text below was read from the document held in the library.
| Type | Commercial Circular |
|---|---|
| Topic | reservation |
Facility available to send the actual train consist to PRS, before actual train departure.
<!-- Slide number: 1 -->
Integrated Coaching Management Systems
(ICMS)
<!-- Slide number: 2 -->
# PAM Module
<!-- Slide number: 3 -->
# PAM-Integration Amongst Systems
COA
PAM
Train Running Data
COA
NTES
Dynamic Caution Orders
Exceptional Information
Exceptions:
Rescheduling
Cancellation
Origin Change
Diversion
Destination Change
PRS
TMS
Train Running Data
<!-- Slide number: 4 -->
# Current Approach of Integration
ICMS Web Server
COA User
Pam Application Execute Web service for integration.
PAM calculate train start date based on train schedule date send by COA.
Then PAM calculate delay based on actual date and time send by COA
PAM checks authorization of the division
Punctuality calculations and population of various tables.
COA Divisional Server
Running J2EE based PAM applications
ICMS App Server
COA Central Server
COA User
Central Server checks the data based on flag if it is required for PAM, then invokes web services
Oracle Database
COA Divisional Server
INTREGATION BETWEEN ICMS-COA
### Notes:
<!-- Slide number: 5 -->
# PAM- Interchange
Interchange reporting is made by division level user.
Capturing of actual train running timings at source, destination and interchange stations.
Back up option used when timings are not updated from COA.
As soon as actual timings are received at interchange station or destination, punctuality is calculated automatically at Division and Zone level. Board level punctuality calculated after arrival reporting at destination.
<!-- Slide number: 6 -->
# PAM- Detention
Detention reporting is made by division level user.
New User Interface to capture train running delay reasons.
There are 34 standard causes along with sub causes.
One of the cause has to be defined as primary cause at division level, that is treated as responsible cause at division level.
Responsibility fixing at zone and board level taken care by the system automatically and later on that can be changed manually.
<!-- Slide number: 7 -->
# PAM- Exceptions
New User Interface to capture exceptions.
Captured exceptions are transferred to COA and NTES.
Already marked exception can be removed by super user.
Cancellation, Rescheduling and Origin change can be marked before actual departure reporting.
Diversion can be marked before actual diversion takes place from diversion starting point.
Short termination can be marked before actual arrival at regular destination.
System allows and handles marking of Multiple diversions.
<!-- Slide number: 8 -->
# PAM- Asset Failures and Unusual
New User Interface to capture Asset Failures and Unusual.
Logging allowed for passenger carrying and goods trains.
Editing allowed up to next 7 days.
Any logged entry can be removed by super user within 7 days.
MIS reports are available at Board, Zone and Division level.
<!-- Slide number: 9 -->
# PAM- Caution Order
PAM receives Caution Orders marked in COA through integration.
MIS reports to display imposed cautions are available at Zone, Division and station level.
Station level MIS report reflect imposed caution in the order of given route.
Caution Order can be system generated and issued to driver & guard of trains from Notice station using this utility.
<!-- Slide number: 10 -->
# Train Running Comparative Graph
<!-- Slide number: 11 -->
# Train Running Delay Graph
<!-- Slide number: 12 -->
# Detention Reporting Interface
<!-- Slide number: 13 -->
# COIS Module
<!-- Slide number: 14 -->
# COIS-Integration Amongst Systems
COA
COA
Unplanned Enroute At/Dt Loco Information
CO
Extract shown above; the full text is available in the search app.
Open this circular in the search app · Search all 4,025 documents