dod-mosa
DoD MOSA — Implementing a Modular Open Systems Approach in DoD Programs
Source: OUSD(R&E), Implementing a MOSA in DoD Programs (Feb 2025, DOPSR 25-T-1210) — US Government work, public domain | Chapters: 7
When to use
Use this skill when a U.S. defense program must adopt, plan, write into contract, assess, or sustain a Modular Open Systems Approach: framing MOSA against the statute and DFARS, working the five pillars and the interface lifecycle, making the technical decisions (WBS taxonomy, standards profiling, software/cybersecurity), levying MOSA requirements across the AAF pathways, and tying it all to data rights, assessment metrics, and roadmaps. This is the DoD acquisition-policy companion to the SE-process packs (dau-se-guidebook, nasa-npr-7123) and the SE canon (sebok).
Prerequisites: none — plain Markdown; no MCP server, API key, or licence tier needed at runtime.
How to Use This Skill
- Without arguments — load the core frameworks below: the statutory chain, the five OUSD(R&E) pillars, the interface lifecycle, and how MOSA is assessed and contracted.
- With a topic — ask about a pillar (e.g. "certify conformance"), an interface-lifecycle step, a statute or DFARS clause, an assessment tool (PART, OAAT, KOSS, SEAM, MAUT), an acquisition pathway, data rights, DMSMS, or roadmaps.
- With a chapter —
ch01(statute/policy),ch02(pillars/benefits),ch03(program-management/interface lifecycle),ch04(technical considerations),ch05(assessment/technology change/roadmaps),ch06(acquisition pathways),ch07(implementation appendices/tools/contracting).
Supporting files: glossary.md, patterns.md, cheatsheet.md.
One discipline, two architectures. MOSA is a technical architecture (modular components behind open interfaces) and a business architecture (contracting, IP, data rights). A clean interface the Government cannot legally exploit is not, in MOSA terms, a success.