I also haven't gotten into the business and logistics costs of pulling this off, but consider the fact that there is not even a RFP for such a device in existence.
I also haven't gotten into the business and logistics costs of pulling this off, but consider the fact that there is not even a RFP for such a device in existence.
Reliability is obviously a concern, but the procurement process should force contractors to open their designs to qualified competitors after a certain period of monopoly profits to recoup their research expenses, sort of like the same way that brand name drugs are eventually forced to compete with generics. Just because these designs are generally national security secrets doesn't mean that the original developer should own the equivalent of an infinite patent on the technology.
Imagine today you have that device in your table. Ok. What is your next step. Just show up at the Pentagon with it in your bag?
A lot of that costs money (unfairly probably) and that is one of the reasons soldiers sometimes end with crappy hardware that costs some astronomical amounts.
No, where you're really going to get burned in dev is hooking the bomb up to the aircraft's targeting system. That's a world of pain right there. The best solution might probably involve making a Bluetooth widget that hooks up to the aircraft and then talks to the bomb via radio. They could be pre-paired in the factory. Not ideal though. You're also going to need to spend a ridiculous sum of money on sales, just to get your foot in the door.