Yeah, seriously. I understand the physical implementation, but why not have the computer process it as once charge like the MassPike did? Or, if they insist on blowing up everyone's statements, at least give the gantries names to be consistent with the rest of the system! This is literally the stupidest possible way to implement the billing.
Particularly since as near as I can figure out, handling 25A requires some back-office post-processing as there is not a gantry at 25A for them to directly determine who entered or exited at 25A. I'm assuming it will work something like this:
- Scanned at the 24/25 gantry and charged.
- Scanned at the 25/25A gantry and charged.
- After some reasonable period of time, if not scanned at the 25A/26 gantry (start of the 25A to 34A VTS), assume car exited at 25A and refund the 24/25 and 25/25A tolls.
Even if entering at 25A, you'll probably be initially charged and then refunded as a delay in receiving a transaction from another gantry (it happens, at least here in Illinois), could cause the transactions to be received out of order. If that happens, just because the first scan received by the master system was just after 25A doesn't mean a before 25A scan isn't coming.
Anyway, due to the 25A issue, the system needs to put the scans together to determine where a car initially entered and finally left so why not put that altogether into one toll transaction on your statement.