Marine Corps FORCEnet

1
Marine Corps FORCEnet
Presentation to the 2004 Strike, Land Attack and
Air Defense Annual Symposium Mr. Robert
Hobart Marine Corps Systems Command April 29,
2004
2
FORCEnet EMW Enabler
Provides Common Operational and Tactical Pictures
Provides Intelligence, Surveillance and
Reconnaissance
Provides Communication and Data Networks
... and Enterprise Services invisible to the user
2
3
What Is FORCEnet?
Net-Centric Warfare Is the Theory. Net-centric
Operations Is the Concept. FORCEnet Is the
Process of Making the Theory and Concept a
Reality.
4

• TRANSFORMATION

• FORCEnet
• Flexible, responsive to the Commander
• Transparent technology
• More than technology
• Leadership, tactics-techniques-procedures (TTP),
  concepts, training, etc.

5

• CAPABILITIES

• Expanded Collaborative Planning
• Real-time, dispersed
• Enhanced Decision-making
• Right info, right time, right person, right
  format
• Modeling and Simulation
• Test and modify plan in real-time
• Self-organizing, Self-healing Network
• Automated routine decision-making

6
Concept-Based Development
Guidance
Macro Functional Orientation
Concepts
Integrated Architectures
Capabilities List
Technology Insertion
ST Investment Experimentation
7
USMC Architecture Agencies
- Process and agency coordination
- Systems and technical views - Architecture
engineering infrastructure
- Operational views
8
Strategic Framework
Military Transformation Net-Centric Operations
Warfare
NCOW

• Naval Transformation Naval Power-21
• Naval Operating Concept

Naval Power 21
Sea Power 21
Marine Corps Strategy 21
Service Transformation Sea Power-21 Marine
Corps Strategy 21
USMC Campaign Plans
Sea Strike Sea Shield Sea Warrior
Expeditionary Maneuver Warfare
Sea Base
Sea Trial Sea Enterprise
FORCEnet
NMCI
eXNET (TDN)
MCEITS
9
Netting the Joint Force
Architecture Key to Integration
10
(No Transcript)
11
BACK UP SLIDES
12
Army / USMC Common Efforts

• MC02 MCS / TCO Interface
  
• Feb 03 - Operational Architecture effort to
  identify common IERs
• JROCM 128 and 161- 03 to achieve a single
  joint capability (BFSA/CID)
• C2PC / FBCB2 Alignment

OV-1 JBFSA (DRAFT)
Defining information network requirements
13
Army / USMC Common Architecture Efforts

• Common Army BOS / USMC BSF maneuver IERs
• Examining remaining BOS/BSF alignment
• Shared operational architecture databases
• Common methodology for architecture based
  capabilities development

Exploring architecture development MOA!
14
Netting the Joint Force
G I G
Joint Battle Management Command Control
Air Force C2 Constellation
Army LANDWARNET
Marine Corps FORCEnet
Navy FORCEnet
Architecture Key to Integration
15

• LEADERSHIP

• Command Philosophy
• Command by Direction
• Centralize uncertainty
• Command by Plan
• Prioritize uncertainty
• Command by Influence
• Distribute uncertainty

Network must be Adaptable to the Commander
16
GIG Overlay
BEA BMMP (6 Business Areas)
JBMC2 - JFCOM
JC2 - STRATCOM
FCB Warfighting (5 Warfighting Areas)
FORCENET
LANDWARNET ?
C2 CONST
AF BEA
IT-21 ?
NMCI
eXNet
MCEN
INFOSPACE
MCEITS
CES TCA GIG BE JTRS IA COMPUTING PLANT
MARINE CORPS ENTERPRISE NETWORK (MCEN) Provides
USMC end-to-end IT capabilities, and is the
Marine Corps contribution to FORCENET and the
GIG. Supports both the warfighting and business
operations. Summary of BGen John R. Thomas
statement to House Armed Services Committee 2004
17
USMC Architecture Artifacts
OPERATIONAL
Information
Concepts
Functional Orientation
SYSTEMS
MCIAP Enterprise-Level
Platform System-Level
TECHNICAL
Standards Maps
18
A Conceptual Foundation
19
FORCEnet
Persistent, netted ISR optimum naval investment
within joint architecture
Ubiquitous communications
Robust links
Fully netted sensors
Flawless combat ID blue force tracking
Full coalition interoperability
COTP to all users
Ironclad network defense-in-depth
Shared common undersea picture
4
20
Management Philosophy Shift

• OSD/JCS Approach
• Improved analytical rigor to better define the
  capabilities needed and those we no longer needed
  eliminated.
• Capabilities-based planning counters threats that
  pose the greatest danger without predicting
  specific contingencies.
• Scenarios illuminate possible outcomes of
  potential contingencies and test capability
  needs.
• Resource constraints impact implementation plans,
  not capability needs determinations.
• Focusing leadership earlier in the decision
  process ensures a more coordinated implementation
  effort within resource constraints.

21

• MANEUVER WARFARE

• Commanders intent
• Shared awareness
• Decentralized operations
• Tempo
• Surfaces and gaps
• Warfare with hardware