"Issue: Contract compactor specifications on expected life of product vague and not supported by data.
"The contract included compactor specifications that included an expected life of 10 years. When questioned about data or research to support this expected life, the BigBelly Solar CEO stated the life expectancy was an estimate based on the type of products and materials used in the compactors. He further stated that the compactor had a life expectancy that was estimated similar to an automobile; in that some repairs and parts may need to be made during the normal life cycle, but full replacement may not need to be made for theyears. When asked if there was any testing data to support the 10 year life expectancy, he indicated that he was not aware of any specific data."
The main savings seems to be from being able to monitor when the cans are full, and only pickup when needed.
To me, it would be simple to write an app that read in a x daily image upload of the can which automatically calculated the level of fullness. It wouldn't require specialised can hardware and could drive most of the benefit (only emptying when required). You could double the size if more capacity was required.
Also, I would expect that these would fall into a very predictable pattern, with some cans requiring emptying 5 times a week, some 8 times a week, some twice a week. It seems some simple modelling would also give you many benefits for a very small upfront-cost.
I have visited many friends places that had compactors installed when their kitchens were new, and over time they just stop bothering with the compaction and use it as a regular disposal. Usually because the compaction is messy, faulty or just too much bother to use. I would expect public trash cans to have the same problems, but magnified.
The whole thing looks like a solution searching for a problem - bludgeoning a simple problem with too much technology.
I would have to check my numbers. It might be that garbage men total cost of salary and benefits is a (large) multiple of $30K/yr (getting into software engineer pay territory) in which case windshield time is even more incredibly expensive. Then it might work out that reducing labor cost by 10% or so would actually work out to 900K/yr.
Its like the mailman argument. If I don't get any mail today, my mailman can't magically teleport past my house. True he does save the time of opening a box and tossing some sorted mail in, but that action only takes a tiny fraction of the time of walking 100 feet past my property. A registered mail transaction takes a LONG time like 5 minutes and if more people got registered mail (or fewer got junk mail) then the ratio would flip and he'd save huge time.
No, but he can save a lot of time by not turning down your street at all.