I just passed my four-year mark working in parking. After nearly nineteen years in banking, it took me a while to really understand. Don't get me wrong, I'm still a long, long way from being prepared to sit for the CAPP test, but I think I can honestly say "I get it" when taking about Parking Access and Revenue Control, Parking Garage Software, Handheld Ticket Writers, and a lot of what goes into managing them.
For me, all that complexity translates back to computing systems that talk to all of those advanced parking solutions that are out there in the world dealing with all of the parkers. Even in the summer when many of T2's customers that use our software as a campus parking solution are at a relatively low volume of parkers, we're seeing around 20,000 transactions a day amounting to around a million dollars and that's just for our customers that use our hosted parking system software. A similar number run their own computer systems running T2's parking software.
Each of those transactions generated has a "footprint" on the servers that we use to host. They translate to memory usage, CPU usage, and disk reads/writes. As a geek and a numbers guy, it is absolutely fascinating to watch the metrics as the complex transactions are processed and completed. The main reason we monitor everything that goes on in our Hosting Environment so that we can make sure there's enough hardware to support all of our customers efficiently and well, but I still think all of those metrics are just plain cool.
Happy Parking.
For me, all that complexity translates back to computing systems that talk to all of those advanced parking solutions that are out there in the world dealing with all of the parkers. Even in the summer when many of T2's customers that use our software as a campus parking solution are at a relatively low volume of parkers, we're seeing around 20,000 transactions a day amounting to around a million dollars and that's just for our customers that use our hosted parking system software. A similar number run their own computer systems running T2's parking software.
Each of those transactions generated has a "footprint" on the servers that we use to host. They translate to memory usage, CPU usage, and disk reads/writes. As a geek and a numbers guy, it is absolutely fascinating to watch the metrics as the complex transactions are processed and completed. The main reason we monitor everything that goes on in our Hosting Environment so that we can make sure there's enough hardware to support all of our customers efficiently and well, but I still think all of those metrics are just plain cool.
Happy Parking.
Powered by Compendium
Comments for Parking is Complicated