Spectral Autonomy

MOSA: Modularity in design and acquisition

Part of the Open Architecture Field Guide.

The Modular Open Systems Approach (MOSA) combines technical design and acquisition practices to support competition and change over a system's life. It focuses attention on module boundaries, key interfaces, and the information needed to use them.

In this guide

Designing for the next replacement

Suppose a program expects to replace a processor during a platform's service life while retaining its sensors and applications. The design must establish which connections the replacement processor will provide, what information another supplier needs to build it, and how the program will determine whether it performs the required role.

These questions connect architecture to acquisition. A technical boundary makes the processor a distinct part of the system. Interface information allows a supplier to design against that boundary. The acquisition arrangements determine whether the program can obtain and use the information needed for replacement. A test provides evidence that the delivered component satisfies the required interfaces and behavior.

The Modular Open Systems Approach (MOSA) brings these activities together. It combines modular design with interface selection, standards, data rights, and conformance practices so that a program can manage change over the system's life. The Department of Defense (DoD) implementation guide describes this as a combined technical and business approach. Section 4401 of Title 10 establishes MOSA requirements for covered defense acquisition programs. [1] [2]

Choosing a boundary that serves the intended change

A module is a part of the system whose responsibilities and connections can be described separately. The location of its boundary affects how much work accompanies a later replacement. If processor-specific behavior is spread throughout the applications and sensor interfaces, changing the processor reaches into all of those components.

A more deliberate design identifies which services the processor supplies and which interfaces the retained components use. The replacement supplier can then implement the required side of those connections. The architecture still describes a complete system, but the intended replacement has a defined scope within it.

The same reasoning applies to software. An application can be separated from device access or operating-system services through defined interfaces. Updating the application and replacing the host then become distinct kinds of change, each associated with its own dependencies.

How the MOSA principles support that boundary

The implementation guide organizes MOSA around five pillars. Establishing an enabling environment supplies the planning, authority, and resources needed to carry the approach through acquisition and sustainment. Employing modular design identifies the system's parts and the responsibilities assigned to them. [1]

Designating key interfaces focuses attention on the boundaries that matter to the program's planned changes. Using open standards provides shared technical definitions where suitable specifications exist. Certifying conformance establishes whether the implemented interfaces meet the selected requirements. These activities connect the architectural intention to evidence about the delivered system.

In the processor example, the key interfaces are the connections that the replacement must preserve. A hardware standard may describe its module and slot connections, while software standards describe the services used by the retained applications. Conformance work then examines those selected requirements in the delivered component and its integration.

Connecting interface information to the supplier's work

A supplier needs enough information to design its contribution. The relevant material can include interface definitions, data models, expected behavior, and the evidence required for acceptance. The program also needs appropriate rights to use that information for the intended development, competition, and sustainment activities.

This is why data rights belong in the same discussion as modularity. A well-chosen boundary has limited acquisition value if the information needed to implement it is unavailable for the planned purpose. Conversely, a large collection of technical data is useful only when it describes the interfaces and responsibilities on which the intended replacement depends. The acquisition and engineering teams must connect the information being obtained to the actual work it will support. [1]

Selecting standards for the function being changed

MOSA provides the approach; the program selects technical specifications according to its design. OpenVPX can describe modular hardware connections. FACE can describe software interfaces for portability. A reference architecture such as AMS-GRA can organize mission-system functions and their procurable units.

The useful starting point is therefore the anticipated change. Replacing a processor, introducing a new processing service, and adding a navigation sensor affect different interfaces. Naming the change first allows the program to explain why each selected standard, information requirement, and test belongs in the design.

References

  1. OUSD(R&E), Implementing a Modular Open Systems Approach in DoD Programs, February 2025.
  2. 10 U.S.C. § 4401, Requirement for modular open system approach in major defense acquisition programs.