Fare Hike Confusion – Bait and Switch?
MetroAccess riders appear to have been subject to a mailshot over the past week, with postcards arriving to explain the new fares. This explanatory blurb was on the cards:
In the meantime, MetroAccess will be upgrading its trip scheduling system to prepare for the second phase to be implemented this fall, in which fares will be based on twice the cost of the equivalent trip taken on Metrobus or Metrorail with a $7 maximum. When this change is made, MetroAccess will no longer serve locations that are more than 3/4 mile from existing regional bus and rail services. Existing users of MetroAccess who have traveled outside this boundary within the past year will be the only exception.
One MV Transit trainer’s solution to the MetroAccess budget crisis: Kill the riders?
You would think a "trainer" would understand that the proper place to secure wheelchairs on vehicles are the "hardpoints", the strongest attachment locations of a chair, wouldn't you?
On most wheelchairs, these hardpoints are the bars connecting the seat to the chassis cage. Usually 4 of them are to be found on wheelchairs, they are amongst the strongest components of any chair as they're designed to keep the seat connected to the wheelbase in motion.
MetroAccess IVR/GPS Problems?
While the database issues mentioned previously are continuing, with reports that the Silver Spring staff have been extremely busy today trying to work around unspecified problems performing trips, DC ParaTransit Info is wondering what could cause an IVR reminder call this evening (made to customers the night before to remind them of their upcoming trips) to abort at the beginning of the message, stating:
A GPS Error has occurred
We've asked MetroAccess for more information, but we're curious if this is related to the database issues, and more importantly - if this is indicative of a problem with IVR (and presumably, Trapeze) not being able to access/reference GPS data, what effect is this having on provisioning of trips?
How reliable is the MetroAccess Database?
Given the complexity and size of MetroAccess operations, the integrity of the databases that "power" it on a day to day basis is a critical issue.
We already witnessed the kind of chaos corrupted data can cause to the system - when MV Transit was importing data from the previous contractors, Logisticare, prior to taking over the contract, DC ParaTransit Info was sounding loud warnings to WMATA that there were major omissions and discrepancies in the database information being transferred. Unfortunately, these warnings went unheeded, but the flawed database migration was noted as one of the reasons for the abysmal transition period that gained such negative attention at the beginning of MV's term.
Omitted Paperwork
You have to love auto-mailer systems.
I received a letter today reminding me that I need to recertify for MetroAccess soon. The letter advised me to complete the enclosed application and return it to the office within 60 days of the date of their letter.
Except - no application form.
So I have to call them to tell them they forgot a rather important piece of information in their mailshot, and ask them to get it right.
Of course, their system probably has the 60-day clock started September 24th, the date on their letter (of which 7 days have already passed before I even received it).

