Speaking with a Commonality Language: A Lexicon for System and Component Development
Abstract
In recent years, the Army, and the U.S. Department of Defense (DoD) more broadly, has become increasingly interested in commonality the sharing of common parts across different entities. Commonality has implication for procurers, designers, developers, trainers, logisticians, and operators. Commonality offers many advantages and disadvantages; the trade-offs are sometimes difficult to discern and implement. To gain an understanding of the potential benefits and burdens (full life-cycle costs, training, and sustainment) of commonality, the U.S. Army Capabilities Integration Center asked RAND Arroyo Center to assess the consequences of "system and component commonality." Consequences are difficult to discern when there is confusion about the subject. As we began to examine existing literature on commonality, we realized that there is considerable confusion about what commonality is and why it matters. This report recommends a new, more rigorous lexicon for describing system commonality and component commonality and presents a common language for the Army and other services to share. This report provides definitions for common and eight related concepts.
Document Details
- Document Type
- Technical Report
- Publication Date
- Jan 01, 2007
- Accession Number
- ADA470927
Entities
People
- Bruce Newsome
- Matthew W. Lewis
- Thomas Held