Naval Integration Marine Corps Systems Command

1
Naval IntegrationMarine Corps Systems Command
Mr. David LobikNaval Integration
MJIC/SIAT david.lobik_at_usmc.mil703.432.3778
SID Symposium 29-30 Sep 2009
2
Agenda

• Naval Integration (NI) Defined
• NI Branch Role
• Challenges
• The Need
• Transportability and Deployability DoD
  Instruction
• Way Ahead

2
3
Naval Integration (NI)

• Naval Integration is the systems engineering
  process in which Marine Corps expeditionary
  warfare systems that support of the full range of
  military and humanitarian/disaster relief
  operations are designed and developed with the
  shipboard operational environment considered.
• This includes not only the effective and
  efficient embarkation and debarkation of
  expeditionary systems but also its safe and
  effective operation, as required, once aboard.
• C4I system developers must consider the
  integration of Marine Corps communication systems
  into shipboard Tier 1N tactical network and RF
  architectures, leveraging Navy service-oriented
  capabilities
• Areas of HME design focus for NI include, as a
  minimum, equipment configuration, size, weight,
  power, HAZMAT, heat, ventilation and corrosion
  prevention as required.

NAVAL INTEGRATION IS NOT JUST TRANSPORTING
EQUIPMENT
3
4
NI Branch Role

• In working closely with the requirements
  developers, establish and maintain a
  well-defined, formalized process mandated by
  Marine Corps directive that ensures Naval
  Integration and Transportability activities,
  through Systems Engineering Technical and System
  reviews, support Marine Corps Expeditionary
  Warfare programs both afloat and ashore.

NI CONSIDERED FROM CRADLE TO GRAVE
6
5
Challenges

• C4I Integrations Issues
• Technology refresh rates/budget cycles/MarCorps
  task org nature
• Challenge to influence all afloat USN programs
  and initiatives IOT preserve USMC equities
• Need to influence/engage acquisition and
  modernization processes at key decision points
• MAGTF Afloat Baseline essential to maintaining
  requirements and modernization initiatives, but
  not formally recognized by N6, or USN in general
• Hull, Mechanical Electrical (HME) Integration
  Issues
• Most programs address NI requirements on their
  own. Programs spend valuable on task
  associated with attaining certification and
  assessment approvals.
• Most programs dont seriously consider NI until
  late in the program (near LRIP or FRP) based on
  perception that it may have significant cost,
  schedule and performance implications that
  werent budgeted for...
• Program offices will potentially commit more
  resources for ECPs late in their program than if
  engineering was addressed at early reviews.
• For larger ACAT programs, most GO-level review
  board (MRB/MROC) members are keenly aware of the
  importance of integrating their ExpWarfare
  programs with the Navy early in the development
  process and hold program managers accountable at
  each major review. We need to support these PMs
  as early as possible.
• MCOTEA Need NI specifications built early into
  TEMP and assessed at OTRRlatest

NEED TO PRESERVE RESOURCES WHILE MAINTAINING
WARFIGHTING CAPABILITY
4
6
The Need

• All elements of the MAGTF are out growing their
  lift capacity
• MOA for Naval Expeditionary Warfare IPT, signed
  Feb-Mar 1996, 8 signatories at DASN and Service
  GO/FO level.
• MOA between PEO Expeditionary Warfare and
  commander, MCSC signed 18 Jul 00
• to ensure Navy and Marine Corps Program
  Managers and their staffs coordinate their
  requirements and efforts throughout the
  acquisition process to ensure successful Naval
  Integration.
• Fall of 2006, ACMC added weight as additional
  Fingerprint of Lift.
• NAVSEA 21 Letter dtd 8 Jan 08
• MarCorps asked to provide listing of all current
  and planned POR vehicles and equip to be
  deployed aboard assault echelon ships
• Create loading envelopes for vehicle decks of
  amphibious ships based on generic vehicle load
  configuration
• To what degree does the increase in size/weight
  of MarCorps ground equipment affect the
  restricted stability status of amphibious ships?
• MCSC currently does not have the tools necessary
  to address implications of granting waivers that
  affect our lift capacity
• ABV coming in overweight by 500 to 1000 lbs.
• Waiver requested by requirement developers
• MDA to assess

SYSTEM OF SYSTEMS APPROACH NEEDED FOR DEVELOPING
WARFIGHTING CAPBILITY
5
7
Transportability Certification

• Current DoD direction specifically addresses
  Transportability for the Services
• DoDI 4540.7 tasking to MCSC via CMC
• Para. 5.6.3.2.  Execute the Marine Corps
  Engineering for Transportability and
  Deployability Program, obtain mode-specific
  transportability certifications from Component
  Transportability Agents, and review the
  transportability section of capabilities
  documents, specifications, and other appropriate
  materiel requirements documents.
• If applicable assure proper certifications for
  Air, Rail, Highway, External Air Transport,
  Internal Airlift, Airdrop, Common User Sealift
  and Amphibious shipping

ONLY POLICY DIRECTIVE ADDRESSING INTEGRATION OF
EQUIPMENT
7
8
Way Ahead

• Currently, no Navy or Marine Corps directive
  exists that supports requirement or equipment
  developers with addressing NI in the acquisition
  process
• The acquisition community is in general agreement
  that theres a need to
• Develop and Insert NI capability requirements in
  acquisition documentation at all phases
• Formalize NI in Expeditionary Force Development
  System (EFDS)
• Formalize NI process in DoN and DoD
• Policy directives that should support NI
• MCO 3900.15, EFDS
• DoDI 4540.7, Operation of the DoD Engineering for
  Transportability and Deployability Program
• New initiative NI Order for Expeditionary
  Warfare Requirements and System Development.
• Leverage DoDI on Transporatibilty
• NAVSEA and NAVAIR ship integration SMEs input is
  essential
• IPT established to develop the directive

MUST FORMALIZE PROCESS!
8
9

• Questions!

9