|
|
| Re: Entire IRT suspended (1519326) | |||
 |
|||
| Home > SubChat | |||
|
[ Read Responses | Post a New Response | Return to the Index ] |
|
||
|
Re: Entire IRT suspended |
|
|
Posted by Fine, Howard, and Fine on Wed Jul 24 08:19:21 2019, in response to Entire IRT suspended, posted by LA Scott on Fri Jul 19 14:19:11 2019. Evidently the same Siemens software that powers the ATS system is responsible for the Subchat outage of the past few days.MTA transit chief says software glitch caused Friday’s subway snafu, reports show system has been buggy for months The following day at around 6:50 a.m., as the Monday morning rush got underway, reports show that the servers supporting the ATS system also failed, leading to two hours of delays on the numbered lines. The reports show that an employee from Siemens, the technology provider for the system, was called to the Rail Control Center to help resolve the issue. MTA and Siemens employees worked together to switch the servers that supported the ATS system while they rebooted the faulty one. Does not compute: Subway problems need a reboot When you have to keep track of tracks with 8,000 trains a day, computers come in handy. And so the Transit Authority plunked down a bundle of money — nearly $230 million from 1997 through 2008 — for an information system to let them know where all those subways are. On the numbered lines, the old IRT, it’s called Automatic Train Supervision; it also operates the first generation of countdown clocks. Newer countdown clocks on other lines use a different technology. ATS is supposed to let the dispatcher see the location of all the trains. But computers rely on machines, or servers, and programming, or software. And besides the fact that both servers and software have both been failing, stranding commuters, it all works just great. Friday night’s total shutdown of the No. 1, 2, 3, 4, 5 and 6, and the Times Square shuttle was a server problem. Not as though that matters to the zillions of straphangers trapped during a roasting hot heat wave. Nor do suffering riders care that it was a coding problem on July 6 or a software glitch in March or a server issue in October. Siemens does the software; they claim no fault. Who runs the servers, Radio Shack? |
|
|
|