At the highest level, requirements flow from:
National Strategy
Joint Strategy
Service-Specific Guidance
Formal Requirements Approval
Navy Requirements Oversight Council (NROC)
This internal OPNAV body validates and approves critical Navy requirements documents (ICD, CDD, CPD).
Chaired by the Deputy CNO for Warfighting Requirements (N9), the NROC serves as the final Navy gate before submitting to the Joint Capabilities Integration and Development System (JCIDS) or Joint Requirements Oversight Council (JROC).
Navy Capabilities Development Process (NCDP)
The NCDP is the Navy’s comprehensive internal framework for defining, assessing, and validating its future capability needs.
Aligned with JCIDS, this process is primarily driven by OPNAV N9, with essential support from N7 (Concepts) and N8 (Resourcing) to ensure strategic alignment and feasibility.
Integration with PPBE
Effective integration with the Planning, Programming, Budgeting, and Execution (PPBE) process is paramount.
OPNAV N8 collaborates closely with N9 to ensure that validated requirements are properly aligned with Program Objective Memorandum (POM) and budget submissions.
Simply put, "no budget line, no fielding," making timely entry into the POM cycle critical for any new capability.
Upstream Players – Strategic & Requirements Shaping
These actors influence the "what" and "why" before a formal requirement is written:
Downstream Players – Execution & Resourcing
These actors turn requirements into funded programs and fielded capabilities:
BD & GTM Implications
Don't just pitch PEOs.
You need upstream buy-in from OPNAV N9 or fleet commands to shape requirement language early.
Map your tech to the NAVPLAN or DMO.
Aligning with known future force concepts builds credibility.
Target dual-advocate entry.
Get an operational pull (from fleet/TYCOM) and a programmatic push (from SYSCOM/PEO).
Timing matters.
Align your pursuit with the POM cycle (2 years out), or use OTAs/RDT&E to wedge in early.
Navy Requirements-101