Share Email Print

Proceedings Paper

Defining and using open architecture levels
Author(s): M. A. Cramer; A. W. Morrison; B. Cordes; J. R. Stack
Format Member Price Non-Member Price
PDF $17.00 $21.00

Paper Abstract

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.

Paper Details

Date Published: 3 May 2012
PDF: 8 pages
Proc. SPIE 8405, Defense Transformation and Net-Centric Systems 2012, 840502 (3 May 2012); doi: 10.1117/12.924347
Show Author Affiliations
M. A. Cramer, U.S. Navy (United States)
A. W. Morrison, Metron, Inc. (United States)
B. Cordes, Naval Surface Warfare Ctr. (United States)
J. R. Stack, Office of Naval Research (United States)

Published in SPIE Proceedings Vol. 8405:
Defense Transformation and Net-Centric Systems 2012
Raja Suresh, Editor(s)

© SPIE. Terms of Use
Back to Top
Sign in to read the full article
Create a free SPIE account to get access to
premium articles and original research
Forgot your username?