Translator Disclaimer
3 May 2012 Defining and using open architecture levels
Author Affiliations +
Open architecture (OA) within military systems enables delivery of increased warfighter capabilities in a shorter time at a reduced cost.i In fact in today's standards-aware environment, solutions are often proposed to the government that include OA as one of its basics design tenets. Yet the ability to measure and assess OA in an objective manner, particularly at the subsystem/component level within a system, remains an elusive proposition. Furthermore, it is increasingly apparent that the establishment of an innovation ecosystem of an open business model that leverages thirdparty development requires more than just technical modifications that promote openness. This paper proposes a framework to migrate not only towards technical openness, but also towards enabling and facilitating an open business model, driven by third party development, for military systems. This framework was developed originally for the U.S. Navy Littoral and Mine Warfare community; however, the principles and approach may be applied elsewhere within the Navy and Department of Defense.
© (2012) COPYRIGHT Society of Photo-Optical Instrumentation Engineers (SPIE). Downloading of the abstract is permitted for personal use only.
M. A. Cramer, A. W. Morrison, B. Cordes, and J. R. Stack "Defining and using open architecture levels", Proc. SPIE 8405, Defense Transformation and Net-Centric Systems 2012, 840502 (3 May 2012);


Back to Top