The Navy's Open Architecture Enterprise Team (OAET) this spring published a new Program Manager's Open Architecture Guidebook. Its goal? To help acquisition staffs refine business practices used for purchase of "open" hardware and software for Navy systems that enhance performance and ultimately reduce costs.
The guidebook supports the Navy Open Architecture (NOA) initiative, which aims at inserting new capability into ship, submarine, and aviation systems rapidly by establishing flexible processes that expand the field of qualified commercial suppliers of new technology.
In February, the Navy published its eighth quarterly report to Congress on open architecture (the first report was published in February 2008). This one describes plans for continuing the shift of acquisition and system development to flexible, adaptable "open" technology for Navy systems.
The report says that the Navy also will publish an Open Architecture Requirement Officer's Guidebook to help requirements staffs in the Office of the Chief of Naval Operations (OPNAV) incorporate OA technical needs and business priorities in OPNAV requirements documents.