Open Systems Architecture (OSA)
Develop and drive the adoption of enterprise-level business and technical open system approaches to rapidly field new capabilities, lower total-ownership costs, reduce cycle times, and enhance interoperability and access to innovation.
An open systems architecture (OSA) is defined as a technical architecture that adopts open standards supporting a modular, loosely coupled and highly cohesive system structure that includes publishing of key interfaces within the system and design disclosure. The key enabler for OSA is the adoption of an open business model which requires doing business in a transparent way that leverages the collaborative innovation potential of numerous participants across the enterprise permitting shared risk, maximized asset reuse, and reduced total ownership costs (TOC). The combination of an open architecture and business model permits the successful acquisition of an OSA.
OSA yields modular, interoperable systems which more easily support component addition, modification, or replacement by different vendors throughout the lifecycle, driving opportunities for enhanced competition and innovation. OSA is composed of six fundamental principles:
1. Modular designs based on standards, with loose coupling and high cohesion, that allow for independent acquisition of system components;
2. Competition and collaboration through development of alternative solutions and sources;
3. Focus on those components that will provide the best return on investment (ROI), that is, components changing most often due to technology upgrades or parts obsolescence and have the highest associated life cycle cost;
4. Enterprise investment strategies that maximize reuse of system designs and reduce TOC;
5. Continuous design disclosure and enhanced transparency of system designs via Government, academia, and industry peer reviews;
Following an Executive Committee Meeting (EXCOMM), the Assistant Secretary of the Navy for Research, Development, and Acquisition (ASN RD&A) published an Open Architecture (OA) Policy on 5 August 2004 which established a cross-Warfare Domain OA Enterprise Team with clear goals for establish OA principles consistently throughout the Naval Enterprise.
The primary challenge faced by the OSA program is gaining acceptance of new processes and procedures over the traditional methodologies bolstered by current risk and reward mechanisms. There are several goals that will facilitate the accomplishment of this objective:
• Change government acquisition community internal interaction (Government-to-Government) to develop and support OSAs.
• Change government acquisition community interaction with industry (Government-to-Business) to develop and support OSAs.
• Facilitate rapid fielding of capabilities through shared technologies, tools, and standards.
|Point Of Contact|
Office of Corporate Communication (SEA 00D)
Naval Sea Systems Command
Washington, D.C. 20376
|Last Update: 24 October 2012|