Modular Design

Overview

Modular design allows for modifications to systems, recombination of existing capabilities and upgrade of system elements, to enable competition, innovation, rapidly responding to a changing environment, etc.(see also Systems Engineering (SE) Guidebook, Section 2.2.5 Modular Open Systems Approach). Designing for modularity is a key technical principle for implementing a modular open systems approach (MOSA) and is a complementary piece to the open system practices in contracting. The major tenet of a modular design strategy is to develop loosely coupled modules, where modules can be decoupled, separated or even re-arranged in a major system platform and major system components developed under the program, as well as major system components developed outside the program that will be integrated into the Major Defense Acquisition Program (MDAP). When designing for modularity, the system should be appropriately partitioned into discrete, scalable, self-contained functional elements by decomposing and decoupling the functions of a system. This functional partitioning results in elements that can now be composed into modules that can be reconfigured or even replaced.

Acquisition programs implementing a modular design provide flexible system designs, which allow for the replacement or recombination of subsystems and components. It is important for the program management to understand the expected benefit from modular design as part of implementing a MOSA strategy. This understanding provides guidance to the system realization, on which enabling elements (e.g., standards, contract clauses, engineering tools, etc.) to use. MOSA benefits are usually categorized into six individually useful areas, which often overlap: risk reduction; cost savings/cost avoidance; increased competition; enhanced interoperability; application of innovative elements; and ability to realize technology upgrade opportunities easily.

Role of the PM and SE

Program Managers (PMs) should understand both the positive and negative outcomes from implementing a modular design and determine if the realization of a particular benefit outweighs the potential negative consequence. When scoping where the system should implement modular design, the PM, Systems Engineer and Lead Software Engineer should consider multiple factors, such as anticipated Diminishing Manufacturing Sources and Material Shortages (DMSMS) issues, technical innovation, preplanned product improvements to meet performance, etc. These circumstances will vary across systems. System engineers should conduct design trades to support the PM in deciding where to implement modularity into the system design, including how to organize system components, where to put interfaces and which interface specifications and standards to select. (MOSA-enabling standards are identified and accessible in Acquisition Streamlining and Standardization Information System (ASSIST).)

Products and Tasks

Product Tasks
10-15-1: Develop and document an open systems architecture strategy
  1. Identify open system standards for commercial, industrial, international and government independent acquisition of system components applicable to the program / system.
  2. Direct the development of modular designs based on standards that allow for independent acquisition of system components.
  3. Determine and institute enterprise investment best practices that maximize reuse of proven system designs and increase return on investment.
  4. Direct the strategic use of data rights to ensure a level competitive playing field and access to alternative solutions and sources, across the life cycle.
  5. Implement life cycle sustainment practices through proven technology insertion and product upgrades.
  6. Verify system designs are available and shared between system development activities and program management.
  7. Using the results from peer reviews of system designs; determine risks and opportunities for open systems architecture application.
  8. Document applicable open system architecture standards, best practices, system design processes, and technical management processes for the program / system, and incorporate into the open system architecture strategy.

Source: AWQI eWorkbook

Resources

Key Terms

Policy and Guidance

DAU Training Courses

DAU Media

DAU Communities of Practice

On this page

  1. Overview
  2. Role of the PM and SE
  3. Resources
Back to top