I'm often asked why the military doesn't develop and deploy things faster. "Wouldn't it be cheaper/easier/quicker," I'm asked, "to just buy something commercially available? Why does the military try to make its own equipment instead of just buying an existing product? Why Nett Warrior and not just an off-the-shelf Android phone?"
Well, lots of reasons -- military unique capability, for starters. That's obvious. But I had an experience the other day that demonstrates why military specifications are often required that drive up time of procurement, cost, and complexity:
I left my smartphone (brand to remain nameless) in my car for the day, by accident. It was in the glove compartment, not in direct sunlight or plain view. The car was parked in a shady area that would be in sunlight by noon. Peak air temperature for the day was about 80 F at around 1600. When I got to my car after work, it was hot inside, but not so hot that it ws uncomfortable to sit on the black seats or touch the black steering wheel.
The phone, however, did not function -- "Temperature error" was all it said when I turned it on. It had overheated and took a good 15 minutes to cool down before it functioned again. Not a big deal for a commercial device, but imagine that you needed that phone to call for artillery fire or medical evacuation, on a 110 degree day in southern Afghanistan, when the radio had been sitting inside an armored truck baking in direct sunlight so that it reached 140 F inside. You want the phone to work when you turn in on regardless of temperature. And of course you want it to work when cold, if it gets wet, if you drop it, if you accidently smack it with your rifle ...
It doesn't take long to see why it is hard to use commercial technology standards in a lot of military applications.