What MOSA Actually Requires
Part of the Open Architecture Field Guide. All information is derived from unclassified, publicly releasable (Distribution A) sources.
MOSA, the Modular Open Systems Approach, is a requirement written into U.S. law (10 U.S.C. §§4401–4403). It directs defense programs to build with modular designs and open interfaces, but it names no specific standard. Programs satisfy MOSA through the standards and reference architectures in this collection. It is owned by the Office of the Under Secretary of Defense for Research and Engineering.
What it is, and what it is not
MOSA is often spoken of as something a program builds. It is more accurate to say it is something a program satisfies. MOSA is codified at 10 U.S.C. sections 4401 through 4403, and it directs that major programs use modular open systems, with interfaces that follow widely supported, consensus-based standards. The statute does not specify which standard or which architecture. It requires that the interfaces be modular, documented, and open, and it leaves the choice of how to a program.
That distinction matters for reading the rest of this landscape. SOSA, FACE, OMS, the Government Reference Architectures, and the others are not derived from MOSA in a chain. They are independent standards a program selects to satisfy the MOSA requirement. A program can meet MOSA through a reference architecture, or through open standards without a formally named one.
The five pillars
DoD frames MOSA as five pillars: establish an enabling environment, employ modular design, designate key interfaces, select consensus-based open standards, and certify conformance. The fifth is easy to overlook and is treated as co-equal: a design that claims to be open is verified against the standard, not taken on assertion.
Where it sits
MOSA sits above the standard families as a requirement, not as a layer that generates them. It is one of two top-level drivers. The other is JADC2, an operational vision. Neither issues a technical specification. Standards bodies and program offices produce the specifications; MOSA is the legal reason a program adopts them.
Where this fits
- SOSA: The Sensor Open Systems Architecture — a standard a program uses to satisfy MOSA
- FACE: The Standard for Portable Avionics Software — a standard a program uses to satisfy MOSA
- Open Mission Systems (OMS): The Mission-System Abstraction Layer — a standard a program uses to satisfy MOSA
- AMS-GRA: The Air Force's Modular Mission-Systems Reference Architecture — a reference architecture a program can adopt toward MOSA compliance
- A-GRA: The Air Force's Autonomy Reference Architecture — a reference architecture a program can adopt toward MOSA compliance
FAQ
- Is MOSA an architecture?
- No. MOSA is an acquisition and design requirement. A program satisfies it by using modular designs and open interfaces, drawn from the standards and reference architectures that do define specifications.
- Is MOSA required?
- Yes, by law, for major defense programs, and it is applied to other programs to the maximum extent practicable.
- Can a program satisfy MOSA without a reference architecture?
- Yes. A program can meet MOSA through modular design, designated interfaces, and open standards alone. Adopting a Government Reference Architecture is one option, not a requirement.
- Who owns MOSA?
- The Office of the Under Secretary of Defense for Research and Engineering.