According to the Oregon Portland Office of Transportation (PDOT), in 2002, the PDOT began replacing the city’s 7,100 singlespace parking meters with multispace, solar-powered SmartMeters. The parking meters accept with coins, credit/debit cards, or prepaid Smart Cards. They have a wireless capability that allows each to notify the PDOT of technical problems, as well as have their software upgraded. The city now has over 1,350 SmartMeters in operation.

Last week, some 300 of the SmartMeters were on fritz and refused to accept anything but cash. According to this news report on OregonLive.com, the PDOT said the problem was due to "'multi layers' of failed server connections and software limitations in the aging machines."

The PDOT was also quoted of saying, "In terms of why it's happening to some machines and not others, it could come down to high use."

Huh?

Well, apparently the SmartMeters wait until the end of the day to upload their credit/debit cards or prepaid Smart Cards payment information to servers. However, if the connection to the servers fail, the meter holds unto its information in its memory. In addition, if the memory is full, it will stop accepting anything but coins.

An enhancement is planned to allow for more information to be stored in memory when connections are lost. The PBOT isn't interested in improving the wireless network - which is the root cause -  because the SmartMeters are old, increasingly need repairs, and Portland wants to replace the SmartMeters with newer, "smarter"  meters anyway.

However, I might be a little concerned if I had paid for my parking with a credit or debit card on a machine that did not send the billing information to the bank, especially if I was near my spending limit.

As this New York Timesstory notes, banks are making a fortune on inadvertent overdraft fees. An unlucky person could find that their parking in Portland costs a lot more than they initially thought.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}