1. The ENR's Delay's system server is actually  hosting the eT3 trains' delay control application in addition to the data base storing all the application's data, and is connected to the Intranet network via a high speed leased line.

2. ENR's system administrator will be responsible of maintaining the data base master tables such as the users, the train/trip, delay causes tables in addition to the normal administration functions such as back-up and restore the database.

3. In the first implementation phase, the trains' monitoring process is centrally (at Ramses main Hub) performed by Supervision and Planning Group known as SPG agents who are currently responsible of monitoring the several train/trips performed by ENR and inputting the actual departure/arrival time of each train/trip and recording the delay's causes when ever applicable using eT3 application.

4. ENR's top management is now capable at any time of the day to follow time table accuracy from eT3 application and accordingly take immediate appropriate corrective actions avoiding future delays.

5. Future phases will be to deploy the application in all railways station covering each ENR's region.

Application Features

            The following bullet points are summarizing eT3 application features: -

Dual Language Feature

 Dual language capability in eT3 application is providing all screens in either Arabic or English according to the user selection who is actually free to select the interface language at any point of time in the application; the following picture example is representing the same screen shot in both the two languages;

Delay Concepts Feature

  Upon train departure time the actual time entered by SPG's agent is compared with the ENR's schedule time stored into the data base if they are different the agent will be prompted to select one or more of the main delay reasons and accordingly one of the sub-reasons related to the main reason .

   During the train trip, SPG's agent will type the arrival actual time to the first stopping station and this time will be compared with the schedule time stored for this stopping station once again if they are different the agent will be prompted to select one or more of the main delay reasons and accordingly one of the sub-reasons related to the main reason and so on for all the stopping stations of the trip.

    The same process will be performed for the departure time on each stopping station.

    If the departure time on one of the stopping stations was correct (Actual time = Schedule Time) but the arrival actual time was greater than the schedule time in the next stopping station it means that the delay was between the two stations and of course the delay main reason as well as its related sub-reason will be documented.

    Finally at arrival station the process is performed for the last time on this train/trip.

Calculated Schedule Time Feature

eT3 application is calculating a field called "Calculated Schedule Time" as appearing on the following pictures' example;

Legend: ST= Scheduled Time,   AT= Actual Time

A- Upon departure SPG agent will input the departure A.T.  the system will compare it with the S.T. and calculate the delay time if ever applicable, in the picture's example the train was departed with a delay of 19 minutes, therefore SPG agent will be forced by the system to select at least one main reason for this delay and accordingly a matching sub-reason.

B- Arrival A.T. at Giza station (next train stop) will be recorded by the agent in charge, in the picture's example "07:24" and compared with a calculated S.T. by the system (S.T. + previous cumulative delay time = calculated S.T.) in the picture's example S.T. ►07:05 + Previous Delay ►00:19 = calculated S.T.►07:24 which is exactly the same A.T. recorded by the agent, therefore the system will not allow recording of same delay time and reasons twice.

C- Arrival A.T. on the next stopping station (El Wasta in the example) is as usual recorded by the agent "08:23" and compared with the calculated S.T. "08:21" the system detect a delay of 00:02 and enforce the agent to select at least one main reason for this delay and accordingly a matching sub-reason to document this delay. This process will performed for each stopping station until destination.

Shift Concept Feature

As monitoring trains is a "24x7" job eT3 has designed an automated process which is running every 8 hours responsible of checking that all trains/trips scheduled to operate during the shift's time slice of the day has been successfully inputted and verified into the application and therefore successfully updated into the database, meanwhile this program will prepare the required records for next shift according ENR's train/trip standard schedules.

The following picture is illustrating eT3 shifts auto mechanism.

Fulfilling ENR' Special Requirements

eT3 designed the delay control application to fulfill ENR's technical requirements as the following points are completely covered by the application: -

    Trains are linked with lines and regions.

    Directions are linked with trains and lines; direction are usually "Upper" to specify that the train is going up from Mediterranean sea level to any other destination within the same line, while "Lower" will be used to specify that the train within this line is returning back to the original destination of this line.

    Train types are also kept into the database, such Air condition, sleeping cars, 2^nd class, mixed, or other trains

 Page Top

<<Back