1. FORCEnet Status Today
Briefing to the Strike, Land Attack & Air Defense (SLAAD) Division
29 April 2004
CAPT Dan Zazworsky
Director, Combatant Command Interoperability Program Office SPAWAR 054
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

2. Information Flows According to Publish & Subscribe Agreements
What Is FORCEnet?
Warfighting Capability Based on Information Availability Where Needed
The Enabler for Sea Strike, Sea Basing, and Sea Shield
“FORCEnet Is the Operational Construct and Architectural Framework for Naval Warfare in the Information Age Which Integrates Warriors, Sensors, Networks, Command and Control, Platforms and Weapons Into a Networked, Distributed Combat Force, Scalable Across the Spectrum of Conflict From Seabed to Space & Sea to Land.” *
FORCEnet is a set of war fighting capabilities made possible by information flow to enable Sea Strike, Sea Shield and Sea Basing, the pillars of Sea Power It is all about availability of information over networks connecting sensors, command and control, weapon systems, Naval platforms, and the warriors that touch these elements. The warrior’s efficiency increases since information flows automatically according to approved publish and subscribe agreements.
Warfighter Perspective—
Complex Battle Environment
Short response times
Non-integrated information systems
Hard-to-use interfaces
Greater reliance on warfighters for decision making and collaboration
Fewer personnel available
Greater need for multi-skilled personnel
Less time for formal training
*CNO’s Strategic Study Group - XXI definition from 22 July 02 CNO Briefing
Information Flows According to Publish & Subscribe Agreements
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

3. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

4. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

5. FORCEnet Compliance Checklist Development Schedule
Complete Baseline with Gen 2 Checklist - 2/15
Start drafting automated Questionnaire – 3/3
Report Formats complete – 3/9
Data Import and Questionnaire – 3/11
Complete Gen 3 Standards Cross Reference List – 3/15
Finalize Gen 3 Checklist Format – 3/17
Complete Gen 3 Checklist Content & Questions – 3/26
Core Team Reviews
Technical Team Reviews
Program Team Reviews
Deliver Gen 3 Checklist Draft – 3/31
Deliver Final Gen 3 Checklist – 4/30
FORCEnet Has Adopted ASD/NII Net-Centric Checklist
(v2.1 Dated 13 Feb 04)
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

6. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

7. Implementation Database
Checklist From Joint Architecture & Standards Determines Compliance:
System 1
System 2
System 3
System 6
System 4
System 5
System 7
SAMPLE
SPAWAR 05 is developing a FORCEnet Implementation Data Base (IDB) to show when FORCEnet compliant systems will be available for major platforms that comprise U.S. Naval Forces. This will be the key mechanism for planning and tracking the fielding of FORCEnet capability.
Example Platform Integration Report (Notional Data)
Complete Baseline of All Programs’ Level of Compliance Due 30SEP04
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

8. Pilot and Pathfinder Programs
Phase I Pilots
PEO C4I: Common Link Integrated Processor (CLIP)
JAN ’04 EXCOMM Nominated Pilots
CFFC N6: Data Distribution Services
DRPM DCGS-N: DCGS-N
USMC: C2 Logistics
FORCEnet Pathfinder Forcing Functions
CVN-21
LCS
BAMS UAV
The initial set of proposed Pilots does not include shore infrastructure, undersea warfare , expeditionary warfare (i.e. USMC) and special warfare. This list is simply a representative sample of possible additional candidates.
Execution of Pilot Programs Represents the Initial Implementation Phase
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

9. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

10. Assessment Activities
COTP Assessment
Data Links Assessment
N81/N70/N61 Interfaces for PR-07
POM 06 Assessment Data Calls
PR-07 Campaign Analysis Initial Data Call 24 March
PR-07 Campaign Analysis Participation
Delivery of PR-07 Campaign Analysis FORCEnet 2020 Modeling Architecture
N70 SYSCOM Assessment for POM-06 issues
ISR Way Ahead (JFN, DCGS, etc.)
Blue Force Situational Awareness
N70 Collaborative SYSCOM MCP Assessment on Fires and Maneuvers for POM-06
Led by NAVSEA
Three Weeks of Thread Evaluation by SME’s
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

11. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

12. FORCEnet Certification Plan Under Development
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

13. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

14. Architecture Products
What Is the Purpose of the FORCEnet Architecture?
To Identify an Effective and Efficient Migration Strategy That Moves Naval PORs From Their Current Platform/stovepipe Domain to a Future Joint Network Centric Domain
Statement A: Approved for public release; distribution is unlimited (13 Feb 2004)

15. A&S POA&M Key Dates* Deliver A&S POA&M to NETWARCOM 30 Jan 04
NETWARCOM and MCCDC approve POA&M 19 Feb 04
Deliver A&S Document, Volume 2, Standards, to NETWARCOM, Feb 04 - Preliminary 30 Apr 04 - Final
Deliver AV-1 to NETWARCOM & MCCDC 30 Apr 04
Deliver Final A&S Version 2.0 to NETWARCOM 29 Apr 05
* Per Campaign Plan
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

16. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

17. Joint TST Architecture Integration Product Delivery Contract Vehicle Mapping
AV-1
AV-2
OV-1
OV-2
OV-3
OV-4
OV-5
OV-6c
SV-1
SV-2
SV-4
SV-5
SV-6
TV-1
TV-2
Army AAIC
USAF C2C Ö
External Dependencies:
- JIA
- JBMC2
- C2C
- Army Network Fires
- MCCDC TST
- Navy OV-5, OV-6c (C2C) Ö
Army
USAF C2C
Joint
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

18. CSAIWG On-Going Efforts
Consolidated Operational Activity List (COAL)
Creates a Fully Integrated Cross Services Operational Activities List to Support the COCOM’s
Supports and Facilitates Joint Community Architecture Reuse and Rapid Prototyping
Army Lead
Common System Function List (CFSL)
Provides the Basis for Identifying and Assessing Operational Capability Overlaps and Gaps Between Legacy and Developmental Systems
Essential Element for Ensuring Integration and Interoperability Among Joint Systems and Architectures
Navy Lead
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

19. Pulling It All Together
Compliance Checklist / Questionnaire
Implementation Database / Pilots
Assessments
Certification
FORCEnet Arch & Stds
Version 1.0 (Jun 03)
FORCEnet Arch & Stds
Version 1.1 (Nov 03)
FORCEnet Arch & Stds
Version 2.0 (Apr 05)
Joint Arch Products
RAPTOR 04-1
RAPTOR 04-2
RAPTOR 04-3
RAPTOR 04-4
RAPTOR 04-5
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Metrics
(M&S)
TW 04
(Oct 04)
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (3 March 2004)

20. Joint Rapid Architecture Experimentation (JRAE)
Joint & Service Initiative to Ensure and Promote Tactical Interoperability Between Services Architectures
USAF
C2 Constellation
JTRS Testbeds
JTEL
DISA Terrestrial
GIG-BE Test Segments
USA
LAND WARnet
GIG Testbed
Optical Core (NRL)
ATD Net
BOSSnet
DISA Teleport
Test Locations
USN / USMC
FORCEnet
TSAT Testbed (MIT/LL)
Optical Comm Testbed
RF Testbed
Network Testbed
NSA/IC Network
Testbeds
Finally, experimentation is an important part of fielding FORCEnet capability. SPAWAR 05 is conducting lab and sea based experiments with other Services to investigate joint architectural issues. PORs use these experiments to spiral new FORCEnet compliant capability into the Fleet. SPAWAR 05 played a key role in planning and conducting Trident Warrior 03 as the first of yearly “Sea Trial” events (Part of Sea Power 21) that leave new and supported FORCEnet capability on Navy ships. (Normally isn’t done in sea tests)
Joint RAPTOR 04-1: Joint Distributed Services (Mar 04)
Joint RAPTOR 04-2: Joint Tactical Situational Awareness (May/June 04)
Joint RAPTOR 04-3: JEFX Air Force/Army Event (Close Air Support, BFT) (Aug 04)
Joint RAPTOR 04-4: GIG Transformation / Transition (Aug 04)
Joint RAPTOR 04-5: TST Inter-Service Interoperability (TST-PE SIMEX 04-02) (May 04)
(SPAWAR J-RAPTOR POC: Delores Washburn:
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

21. Joint RAPTOR 04-1 Distributed Services
DESCRIPTION
Examine inter-service use of distributed services to reduce the JOINT timeline to detect, decide, plan and act over a Joint IP based network
Achieve Joint interoperability using distributed services
Demonstrate hardware/operating system independence using distributed services
EXPECTED OUTCOME
Provide timely integrated information to the decision maker across services
Reduce the cost of providing tactical information to the Joint warfighter
Present required Joint data (Blue Force Position / Brevity Codes / HPAC / JWARN Overlay etc) between services
Joint interface using XML / SOAP enhances Joint Interoperability
Provide timeliness/accuracy in displaying interfaced data
SCHEDULE
Program Start 10/01/03
Standup Development Lab 10/10/03
Initial Planning Conference 12/02/03
Mid Planning Conference 01/28/04
Final Planning Conference 02/25/03
Final Software Build 03/01/04
Integration & Test 03/02/04
Exercise Practice 03/23/04
Final Exercise Demonstration 03/31/04
Lead: Charlie Fike ( ;
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

22. Joint RAPTOR 04-1 Quick Look Findings
Requirement for a DoD Wide Security Policy
Uniform Modification of Security Policies Across Services
Implementation of Distributed Services Technologies Will Significantly Alter CONOPS
Distributed Services Will Affect the Way We Fight Tomorrow
Network Management Policies Will Be Affected
A Move to Incorporate an ISP Model Should Be Investigated
Network Latency Must Be Considered to Prevent Timeouts
Quality of Service Is a Requirement for Tactical Use of Distributed Services
Central Registries and Repositories Will Be Necessary
Difficult to Identify Where to Find APIs and WSDLs
Code Sharing Significantly Reduced Development Time
Here are some of the findings from the experiment. First, this was a multi-service, multi-lab experiment that connected sites all over the country. What was interesting to see was that not only did each service have its own firewall policy, but each command in each service has its own firewall policy. The differing firewall policies prohibited seamless interoperability and work arounds had to be found. It is imperative to implement joint functional capabilities, there is a requirement for a DoD wide security policy.
Secondly, we can implement this capability technically, but the current CONOPS and policies do not support this type of environment. For example, who is going to control access to information, how do we authenticate users, what business templates to ensure the right information sources are available to the correct authenticated users.
Next, we found that network policies will be affected. For example, moving to this type of an environment suggests that we are moving to the model of the internet service provider and that we need to be able to ensure reliability through mirroring of authenticated data sources to allow for failover and meet the required reliability to fight wars in this environment.
Lastly, to move to this environment we had to ensure that the capabilities could exchange information in an interoperable fashion. This required getting the APIs from each other and many times the challenge was just knowing where to find the APIs. And once we develop a capability, such as a piece of middleware to wrap a legacy system, we need to have a repository where this code can be kept for reuse to save development time. We found that the Navy’s RAPIDs capability provided a repository for reusable software. And further the Navy and Air Force have combined efforts to form the Network Centric Enterprise Solutions for Interoperability (NESI) that provides a technical framework for reuse of software components that can easily be composed into new mission capabilities with minimal development effort
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

23. Trident Warrior Background
Trident Warrior Is:
The Major Annual FORCEnet Sea Trial Experiment
NETWARCOM Is the Operational Agent
The Trident Warrior Series Will…
…Provide a Rapid Fielding of Improved Warfighting Capability to the Fleet, With Full Supportability and Maintainability
Develop the Tactics/Techniques/procedures (TTP) and Concept of Operations (CONOPS) on How Best to Use This New Capability to Optimize the Execution of Naval Operations
Our Vision is to:
….provide a rapid fielding of improved warfighting capability to the Fleet, with full supportability and maintainability – this is key. When we install a system on a ship, it comes not only with the support and maintainability required,
We also deliver the TTP and CONOPS of how to best use this capability.
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

24. Trident Warrior OV for TW04:
TW04 Initial Planning Conference Conducted Feb 04 / Event Scheduled for Oct 04
Initiatives & Objectives in Work to Complete Installation and Finalize Test Plan
TW05 Data Call Out in July 04
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

25. Pulling It All Together
Human Systems Integration
"Fiscal year 04 is a very intense year for architecting and implementing Navy information technology on an enterprise level. Mr. Secretary, you may remember the plan of action and milestones slide we showed you when we first briefed you on the FORCEnet architecture efforts several months ago. This revised schedule includes all of the the original FORCEnet milestones, as shown in the Architecture and Assessments lines, as well as the other tenants of the enterprise solution we have added since our last meeting. In essence, this slide "ties it all together".
Flowing from the C4I technical authority vested in COMSPAWAR, we are implementing pilot programs this fiscal year to start achieving FORCEnet compliance via program contract language in programs under the purview of each Systems Command. We have established teams within the Chief Engineer's office to facilitate success of these pilots. Additionally, we have recommended a cadre of FORCEnet compliant systems to the resource sponsor for funding and fielding in the Fleet this year. In a later brief, you will see metrics to demonstrate how well these systems did in our at-sea demonstration, or Trident Warrior exercise held in October. This cadre of systems will represent FORCEnet Block 1.
Looking to the near future, we are tying in our Sea Trial, or experimentation, efforts in parallel with continued development of the architecture. The experimentation efforts for FY04 will culminate with Trident Warrior 04, which will demonstrate prototype FORCEnet systems in a realistic warfighting scenario. Success of these systems will then lead to spiraling into the PEOs for acquisition and fielding.
We are also vigorously pursuing our joint partnerships in developing our enterprise solutions. Navy has taken the lead in this arena, placing $1M each on the Army and Air Force enterprise architecture contracts. The goal here is to ensure common standards, and to eliminate gaps and overlaps while the architectures are being developed. The end result will be a seamless joint architecture designed to interoperate at every level. We have received enthusiastic support in this initiative from both the Army and the Air Force."
Co-Evolution of Concepts, Architecture, Experiments and POR Execution
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

26. A Dynamic Model of Situated Cognition
Technological
Systems
Perceptual and
Cognitive Systems
Lenses consist of local situation, OPORD, doctrine, experience A B C
Data perceived by decision maker 4
Data available on local system 3
Comprehension of decision maker 5
Data detected by sensors 2
All data in the environment 1
Projection of decision maker 6
© Miller and Shattuck, 2003
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

27. Human Systems Integration: Focus on the Warfighter
HSI Is an Integral Part of Every FORCEnet Product
HSI Technical Authority Defined
HSI in Compliance Checklists
HSI Representative on Each of the FORCEnet Pilot Teams
HSI Part of Architecture and Standards Documents (Volume I, Appendix E; Volume II Section 2.5)
Leveraging Industry (ISO) Standards
Capability Assessments
Kill Chain Time to Include
Warrior Activities
Cost Models to Include Manpower
and Training
Trident Warrior Analyses
Provides Operational Context
Highlights the Need for CONOPS
HSI Analysis of OIF Issues
Training and Collaboration
Were Two Biggest Areas Identified
Warfighter
Displays/
Interfaces
Mission
Tasks
Operational Environment
Statement A: Approved for public release; distribution is unlimited (26 April 2004)

28. FORCEnet POCs Office of the Chief Engineer Executive Secretary
Architecture & Standards
FORCEnet Implementation
Assessments
Technical Authority
Joint Engagement
(619)
(619)
(619)
(619)
(619)
(619)
Human System Integration
(858)
Experimentation
(858)
Test/Evaluation/Certification
(858)
Statement A: Approved for public release; distribution is unlimited (20 April 2004)

29. Questions?