Cubic meets CTA Ventra standards; full transition to new pay system to resume next month

For the first time, Cubic has met the three specific performance standards established by the CTA in November. If this good performance continues, the CTA anticipates announcing in February a new timeline to fully transition the remaining 25 percent of CTA customers to Ventra.

The CTA have demanded that Ventra:

  • Lower average call wait times to Ventra customer service of five minutes or less to speak to an operator.
  • Process all Ventra readers taps in 2.5 seconds or less, 99 percent of the time.
  • Achieve a 99 percent availability or “uptime” on vending machines and card readers on both buses and at rail stations.

All these standards were met in the first week of January. Also during the first week of January, three of every four CTA rides were taken with Ventra.

So be warned – if you aren’t yet using the Ventra card, you better get on board. The magnetic-stripe and Chicago Cards will be history very soon.


Leave a comment
  • There's still no answer as to whether failed taps before a successful tap counts in the time period.
    I got on a 151 today & there were three "STOP" taps before a "GO".
    Every single tap was almost instantaneous, but the total of the four taps was easily 10 seconds, what with having to repeat the functions.

  • In reply to ScooterLibbby:

    I'd have to assume it's 2.5s per tap. My suspicion is that the local end just defaults to STOP if it gets close to the threshold and doesn't have a response back

  • In reply to whateva:

    Yup, that would be my assumption. It would be fairly easy to implement a timer in the client/reader side that simply displays a 'STOP' message at the 2.4 second mark.

    Look, if the reader can't read the card, it should display a message saying so. If the card is read, then why on earth would it respond with a 'STOP' on a valid card, and then magically start working on the next tap? I'm calling bullsh*t on Ventra.

  • fb_avatar

    Will see what call center times are on mon and tue when peoples upass aren't turned on

  • On the plus side, they did auto-reload my card correctly last time. So that finally works...

  • In reply to chris:

    Hmm, my monthly pass expires on Wednesday, so I'll keep an eye on the auto-reload function. I have a note to take a screenshot of my account showing the auto-load (enabled), so I won't have to argue with customer support again when they claim I didn't have it enabled.

  • The standards were established when? November? As in two months ago? After the rollout, not before? Why were they not established prior to the rollout?

  • In reply to CCWriter:

    Supposedly they were in the contract, but you would have to FOIA the contract to find out.

  • In reply to jack:

    I don't have to FOIA anything. I just have to cut through the smokescreen with inconvenient questions about who's supposed to be doing what, and call for any and all overpaid slackers to be thrown out. (Or at least be sentenced by a court of law to a pie in the face.)

  • This morning I got on the bus, tapped the reader and was in a seat before it said Go. I would guess that's more than 2.5 seconds.

Leave a comment