"The glitch on the morning of the rollout was an issue with the database for the legacy Clipper. Cubic resolved the bug after nearly 5 hours."
"Some members of the Clipper board said they appreciated Cubic's 'candor' in its update, despite previous criticisms regarding the handling of next generation Clipper."
"Cubic described some of the defects with the next generation Clipper integration and how it's addressing them, ending the presentation with a pledge to fully migrate the two versions of Clipper."
Bay Area transit officials launched Clipper 2.0 on December 10, allowing debit and credit card payments. However, a major glitch occurred shortly after launch, causing system delays for hours. Cubic Transportation Systems reported that the issue stemmed from the legacy Clipper database and was resolved after nearly five hours. In the first three months, Clipper 2.0 experienced ten incidents. Despite previous criticisms, board members expressed appreciation for Cubic's transparency. Cubic committed to resolving integration defects and pledged to complete fixes by May 30.
Read at SFGATE
Unable to calculate read time
Collection
[
|
...
]