Apparently NS back on line. Different trains took various delays with 29 the worse.
So, the main NS computer system crashed?
Greetings from Alberta
-an Articulate Malcontent
SD70Dude So, the main NS computer system crashed?
It was a planned outage. Amtrak should have known about it.
An "expensive model collector"
If it was planned - it was royally screwed up by all concerned.
Never too old to have a happy childhood!
From other threads------------- Appears that this was a planned outage of less than an hour to apparently up date the NS dispatching system. Well as usual anytime anyone decides to update their IT system(s) they better watch out. Murphy is hidding around the corner. As well interrogate the IT persons on how the update may go wrong.
The whole outage appears to have lasted just over 3 hours? We will never know for sure. Evidently some Amtrak train dispatchers had long segments of their planned route set up so they could continue on until they finally hit a stop at a CP. Others were not so lucky. From Amtrak listed delays Pennsylvanian and Piedmonts went along for quite a distance. Crescent and Capitol not so.
Question to NS did chief dispatcher transmit to all dispatchers for them to set up routes as far as possible ?
I don't know about NS. CSX would have a scheduled Main Frame outage every Sunday morning starting at 0045 until 0200, sometimes, depending on what IT had to update Dispatching would be told that there would be a extended outage. These shut downs affected CADS getting data from the Mainframe and CADS ability to send Train Messages to printers at crew signup locations, during the outages Train Messages would be faxed to locations by CADS. Operationally, these shut downs weighed heaviest on the Crew Callers, as they had to revert to 'paper' lists to continue to perform their functions.
The architecture of the CADS system permitted various elements of it programs to updated 'on the fly'. Notice would be issued through the CADS suystem that X function would not be available starting at Y time - after the update was made notice would be sent that all elements of the system were usable. These updates were normally to applications that monitored and enforece 'book of rules' compliance in their operation.
The lining of switches and signals was the bed rock of the CADS system - updates would be applied when implementing a new control point, eliminating a old control point or changing the configuration of a control point. These changes could be implemented, tested and rolled back if necessary in a short period of time.
I have no idea what NS was trying to accomplish and how it failed and why it took so long to recover.
blue streak 1 From other threads------------- Appears that this was a planned outage of less than an hour
From other threads------------- Appears that this was a planned outage of less than an hour
The outage was planned for longer than an hour.
Our community is FREE to join. To participate you must either login or register for an account.