
DEPARTMENT OF THE NAVY
OFFICE OF THE CHIEF OF NAVAL OPERATIONS
2000
NAVY PENTAGON
W
ASHINGTON, DC 20350-2000
OPNAVINST 3500.42
N2/N6/USFF N7
12 Dec 2014
OPNAV INSTRUCTION 3500.42
From: Chief of Naval Operations
Subj: MARITIME OPERATIONS CENTER STANDARDIZATION
Ref: (a) OPNAV M-3500.42, Maritime Operations Center
Standardization Manual, November 2014
(b) Maritime Strategy: A Cooperative Strategy for 21
st
Century Seapower, Oct 2007
(c) NDP 1, Naval Warfare, Mar 2010
(d) Maritime Security Cooperation Policy: An Integrated
Navy-Marine Corps-Coast Guard Approach, Jan 2013
(NOTAL)
(e) NWP 3-32, Maritime Operations at the Operational
Level of War, Oct 2008
(f) NTTP 3-32.1, Maritime Operations Center, Apr 2013
(g) Navy Cyber Power 2020, Nov 2012
1. Purpose. To issue policy guidance and delineate
responsibilities to implement the Navy’s maritime operations
center (MOC) standard per reference (a). Reference (a)
describes the application and execution of the MOC standard,
which is a complete revision and should be reviewed in its
entirety.
2. Cancellation. OPNAVINST 3500.40A.
3. Scope. This instruction applies to fleet headquarters (HQ)
MOCs as the operational level (OL) HQ warfighting capability
within the Navy to employ the maritime force.
4. Background. Fleet HQ MOCs were developed as a warfighting
capability belonging to the Navy component commander (NCC) and
numbered fleet commander (NFC), to be organized, trained,
manned, and equipped to support commander’s decision-making and
set conditions for operational command and control (C2) of
naval, joint, interagency and combined forces, per reference
(a), chapter 1. The complexity of C2 in an operational
environment demands pronounced interoperability between the MOC
and higher operational and strategic HQs, with peer
organizations and mission partners, with other MOCs, and with