1. Strike, Land Attack and Air Defense Marine Corps Systems Command
FORCEnet
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
Purpose: Discuss Marine Corps FORCEnet and our view of achieving and implementing CMC’s and CNO’s vision.
Discuss our use of integrated architectures in realizing FORCEnet.
Highlight our partnership with the Army where applicable.
I want to talk to you all about where the MC is headed with Fn, how we intend to achieve the CMC’s and CNO’s vision for net-centric Warfare, the tools we will use to get there and progress made integrating our work with ARMY LandWarNet efforts.

2. FORCEnet: EMW Enabler Provides
Common Operational and Tactical Pictures
Provides
Intelligence, Surveillance and Reconnaissance
Provides Communication and Data Networks
FORCEnet is a key Expeditionary Warfare enabler, focused on Command and Control.
It provides these functions to the Naval forces as they operate in the transforming Joint environment.
We view FORCEnet as including the entire Naval enterprise, garrison, in route, warfighting, and as the Naval component of the GIG. The draft FORCEnet Vision document clearly states that FORCEnet includes the warfighting domain, then business or non-warfighting domain and the information infrastructure that supports both domains
... and Enterprise Services invisible to the user 2

3. What Is FORCEnet? FORCEnet
FORCEnet is a naval process designed to deliver on the promise of net centric operations.
It enables the delivery of combat power via distributed systems connected by the network.
Encompasses DOTMLPF capabilities, requirements, and processes, all informed by integrated architectures.
Another way of thinking about FORCEnet is that it will enable the delivery of Combat Power via distributed combat systems connected through the network. It is not a single process, but it has process implications. It is a collection of processes such as requirements generation, architecture and design standards, innovation and experimentation, human system engineering, certification and compliance, and others, all created under a common vision and with common authority in the Marine Corps and Navy aimed at delivering this capability.
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.
”Command centric, network-enabled “
We need to ensure that the role of the Commander is not usurped by the needs of the Net.
“Control” should not burden the commander. CMC: “In command, but out of control.” It must not increase the burden of the Warfighter, but rather be transparent to the user.
DOTMLPF perspective and approach. Can’t just apply new technology on existing structures, need holistic approach. As we transform, there will necessarily be organization and doctrinal changes.
We must remain mindful of fundamental Warfighting principals-such as train as we fight and the primacy of the Commander.

5. CAPABILITIES Expanded Collaborative Planning Enhanced Decision-making
FORCEnet
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
FORCEnet capabilities:
“Right Format” presented to the commander most conducive to assimilation. Usable in the foxhole as well as the Command Center. It must also address the needs of other commanders such as the commander of the logistics base in CONUS that is supporting the warfighter forward, or the base commander who is the home to the warfighter and where the warfighter trains and from which we project power. Without those commanders, deployments can not take place. While those commanders may not be the primary focus of our efforts, their needs must also be addressed.
Collaborative planning and COA test/rehearse-as-you-plan are the goals
Smart agent incorporation. By “routine” we mean linear functions such as calculation of flight times, MSR throughput capacity, etc.

6. Concept-Based Development
FORCEnet
Concept-Based Development
Guidance
Concepts
Macro Functional
Orientation
Integrated Architectures
Capabilities List
Anticipated JCIDS requirements and instituted the Expeditionary Force Development System approximately two years ago.
You can see the pivotal role of Integrated Architectures (IA) within this framework.
IA is used to conduct gap and seam analysis, inform investment and divestment decisions, etc., and to provide migratory pathways toward future capabilities.
We will achieve these capabilities through concept based development. Moving from top-level Visions and guidance to concepts like EMW, then through analysis of those concepts to required capabilities. OA is the tool we will use to conduct the detailed analysis required to convert required capabilities into fielded ones. OA will also allow disciplined insertion of emerging S&T developments and more rigorous planning and mapping of conversion or retirement of legacy systems
Capabilities
Technology Insertion
S&T Investment
Experimentation

7. USMC Architecture Agencies
FORCEnet
USMC Architecture Agencies
- Process and agency coordination
- Operational views
- Systems and technical views
- Architecture engineering infrastructure
MC has a fairly mature Architecture Development process.
OVs at MCCDC, SVs and TVs at MCSC, Policy and Standards compliance at HQMC C4 (CIO)
Applied to the combat development process, including FORCEnet.
MCIAP enables gap and seam analysis and informs acquisition trade-offs
Supports quantifying costs of redundancy and risks of allowing gaps to remain

8. Expeditionary Maneuver Warfare
FORCEnet
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
eXNET= Expeditionary Net, the tactical data network (TDN)
MCEITS= Marine Corps Enterprise Information Technology Services
How does this relate to the Joint world?
Sea Base
Sea Trial
Sea Enterprise
FORCEnet
NMCI
eXNET (TDN)
MCEITS

9. “Netting” the Joint Force”
FORCEnet
Gap and seams exist today. Integrated architectures assist in their identification.
Comparing current capabilities to desired, future capabilities (EMW ECLs) and the associated architectures, we start to see a pathway emerge leading us from the present partially netted environment, into the seamless fully integrated fighting force of the future.
Architecture Key to Integration

11. BACK UP SLIDES

12. Army / USMC Common Efforts
FORCEnet
MC02 MCS / TCO Interface
Feb 03 - Operational Architecture effort to identify common IERs
JROCM 128 and to achieve a single joint capability (BFSA/CID)
C2PC / FBCB2 Alignment
The Marine Corps share many similar requirements with Army. The sense of shared responsibility makes them great colleagues in developing an integrated networking capability for the joint land campaign. We are pressing ahead with these integration efforts
During Millennium Challenge 02 Army Maneuver Control System and Marine Corps Tactical Control Operations System successfully exchanged 8 variable message format (VMF) messages. This was the beginning of the current effort to develop a common capability for JBFSA.
This slide illustrates briefly the Army / Marine efforts for a common network solution.
Recently, JROCM directed the Army and Marines assume responsibility to develop a way ahead to achieve a single joint capability. A series of meetings and conferences have resulted in formalizing Army and Marine Corps joint requirements, architectures, and acquisition strategies – and agreement to continue evolving service Programs of Records (C2PC, Data Automated Communications Terminal (DACT), MCS, Force 21 Battle Command Bde and Below (FBCB2)) to a common system.
Bottom line: Common capability development between our two Services can become a template for Joint community to follow!
OV-1 JBFSA (DRAFT)
Defining information network requirements

13. Army / USMC Common Architecture Efforts
FORCEnet
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
Supporting architectures can make the single integrated network a reality. As this slide indicates, we are working closely with the ARMY to integrate our common requirements.
Acronyms:
BOS: Battlefield Operating Systems
BSF: Battle Space Functions
IER: Information Exchange Requirement
Exploring architecture development MOA!

14. “Netting” the Joint Force”
FORCEnet
G I G
Joint Battle Management Command & Control
Air Force
C2 Constellation
Army
LANDWARNET
Marine Corps
FORCEnet
Navy
FORCEnet
By enabling a disciplined capture of the present partially netted environment, into the seamless fully integrated fighting force described in that vision
Overlaps exist today, seams exist today. Architecture can inform our processes to realize the goal
Architecture Key to Integration

15. LEADERSHIP Command Philosophy Command by Direction Command by Plan
FORCEnet
LEADERSHIP
Command Philosophy
Command by Direction
Centralize uncertainty
Command by Plan
Prioritize uncertainty
Command by Influence
Distribute uncertainty
Again the proimacy of the needs of the commanders must prevail. We must develop systems that are useable by all commanders independent of the philosophy of that commander.
Command By Direction: Primarily used witihin the Army where the commander seeks to control uncertainty by carefully directing the actions of his subordinate form a central location or common net.
Command by Plan: Uncertainty is analyzed and plans made to meet that uncertainty based on priorities. This is exemplified by the Air Force where sorties are planned well ahead based on the scheme of maneuver and an estimate as to how it will unfold on the battlefield. The highest priorities of targets are given the highest weight in allocating resources.
Command By Influence: The cornerstone of the Marine Corps’ maneuver warfare. Commanders intent is clearly stated and subordinate commanders have the latitude to deal with uncertainty when, where and as they find it so long as they act within the intent of their commander. The overall fog of war is therefore distributed among all elements and dealt with locally.
The requirements for C2 systems varies with each philosophy. Any C2 system developed for joint operations must allow for each style and be adaptable by each commander based on the situation.
Network must be Adaptable to the Commander

16. GIG Overlay
BEA – BMMP (6 Business Areas)
JBMC2 - JFCOM
JC2 - STRATCOM
FCB – Warfighting (5 Warfighting Areas)
LANDWARNET ?
FORCENET
C2 CONST
AF BEA
IT-21 ?
NMCI
eXNet
INFOSPACE
MCEITS
MCEN
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
Concepts
Information
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
With these issues resolved, FORCEnet can provide the networked capabilities required by Sea Power 21 and by Marine Corps Strategy 21.
In addition, FORCEnet is based on the cornerstone of network centric warfare (or net centric warfare) which is the basis of the transformation of DoD. By creating the construct of FORCEnet, we are creating an end-to-end process that is designed to identify capability requirements to support NCW, design an architecture based on NCW, establish a continuous experimentation and innovation series that demonstrates the tenants of NCW and an acquisition and spiral development process that delivers these capabilities to the warfighter faster and with more assurance than ever before.
Full coalition interoperability
COTP to all users
Shared common undersea picture
Ironclad network defense-in-depth 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 Commander’s intent Shared awareness
Decentralized operations
Tempo
Surfaces and gaps
Warfare with hardware