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 daniel. zazworsky@navy. mil Statement A: Approved for public release; distribution is unlimited (26 April 2004) 1
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 Control, Platforms and Weapons Into a Networked, Distributed Combat Force, Scalable Across the Spectrum of Conflict From Seabed to Space & Sea to Land. ” * *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) 2
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 3
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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
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 (v 2. 1 Dated 13 Feb 04) Statement A: Approved for public release; distribution is unlimited (26 April 2004) 5
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 6
Implementation Database • Checklist From Joint Architecture & Standards Determines Compliance: E L P M A S System 1 System 2 System 3 System 4 System 5 System 6 System 7 Example Platform Integration Report (Notional Data) Complete Baseline of All Programs’ Level of Compliance Due 30 SEP 04 Statement A: Approved for public release; distribution is unlimited (20 April 2004) 7
Pilot and Pathfinder Programs • Phase I Pilots – PEO C 4 I: Common Link Integrated Processor (CLIP) • JAN ’ 04 EXCOMM Nominated Pilots – CFFC N 6: Data Distribution Services – DRPM DCGS-N: DCGS-N – USMC: C 2 Logistics • FORCEnet Pathfinder Forcing Functions – CVN-21 – LCS – BAMS UAV Execution of Pilot Programs Represents the Initial Implementation Phase Statement A: Approved for public release; distribution is unlimited (20 April 2004) 8
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 9
Assessment Activities • COTP Assessment • Data Links Assessment • N 81/N 70/N 61 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 • N 70 SYSCOM Assessment for POM-06 issues – ISR Way Ahead (JFN, DCGS, etc. ) – Blue Force Situational Awareness • N 70 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) 10
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 11
Certification FORCEnet Certification Plan Under Development Statement A: Approved for public release; distribution is unlimited (26 April 2004) 12
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 13
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) 14
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, 27 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) 15
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 16
Joint TST Architecture Integration Product Delivery Contract Vehicle Mapping Army AAIC USAF C 2 C AV-1 AV-2 OV-1 OV-2 OV-3 OV-4 OV-5 OV-6 c SV-1 SV-2 SV-4 SV-5 SV-6 TV-1 TV-2 Ö Ö Ö Ö Ö USAF C 2 C Army External Dependencies: Ö Ö - JIA - JBMC 2 - C 2 C - Army Network Fires - MCCDC TST - Navy OV-5, OV-6 c (C 2 C) Ö Ö Joint Statement A: Approved for public release; distribution is unlimited (20 April 2004) 17
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) 18
Pulling It All Together Compliance Checklist / Questionnaire FORCEnet Arch & Stds Version 1. 0 (Jun 03) RAPTOR 04 -1 RAPTOR 04 -2 Implementation Database / Pilots Assessments FORCEnet Arch & Stds Version 1. 1 (Nov 03) RAPTOR 04 -3 RAPTOR 04 -4 Certification FORCEnet Arch & Stds Version 2. 0 (Apr 05) RAPTOR 04 -5 Joint Arch Products 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) 19
Joint Rapid Architecture Experimentation (JRAE) USAF C 2 Constellation JTRS Testbeds JTEL DISA Terrestrial USA LAND WARnet GIG-BE Test Segments GIG Testbed • Optical Core (NRL) • ATD Net • BOSSnet DISA Teleport Test Locations USN / USMC FORCEnet TSAT Testbed (MIT/LL) NSA/IC Network Testbeds • Optical Comm Testbed • RF Testbed • Network Testbed Joint & Service Initiative to Ensure and Promote Tactical Interoperability Between Services Architectures 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: delores. washburn@navy. mil) Statement A: Approved for public release; distribution is unlimited (20 April 2004) 20
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 SCHEDULE • • • Program Start • Provide timely integrated information to the Standup Development Lab decision maker across services Initial Planning Conference • Reduce the cost of providing tactical Mid Planning Conference information to the Joint warfighter Final Planning Conference • Present required Joint data (Blue Force Position / Brevity Codes / HPAC / JWARN Final Software Build Overlay etc) between services Integration & Test • Joint interface using XML / SOAP enhances Exercise Practice Joint Interoperability • Provide timeliness/accuracy in displaying Final Exercise Demonstration interfaced data Lead: Charlie Fike (619 977 3050; cfike@polexis. com) Statement A: Approved for public release; distribution is unlimited (26 April 2004) 10/01/03 10/10/03 12/02/03 01/28/04 02/25/03 03/01/04 03/02/04 03/23/04 03/31/04 21
Joint RAPTOR 04 -1 Quick Look Findings • Requirement for a Do. D 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 Statement A: Approved for public release; distribution is unlimited (20 April 2004) 22
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 Statement A: Approved for public release; distribution is unlimited (26 April 2004) 23
Trident Warrior OV for TW 04: – TW 04 Initial Planning Conference Conducted 18 -19 Feb 04 / Event Scheduled for Oct 04 – Initiatives & Objectives in Work to Complete Installation and Finalize Test Plan –TW 05 Data Call Out in July 04 Statement A: Approved for public release; distribution is unlimited (26 April 2004) 24
Pulling It All Together Human Systems Integration Co-Evolution of Concepts, Architecture, Experiments and POR Execution Statement A: Approved for public release; distribution is unlimited (26 April 2004) 25
A Dynamic Model of Situated Cognition Perceptual and Cognitive Systems Technological Systems Lenses consist of local situation, OPORD, doctrine, experience A B C 4 3 2 1 All data in the environment Data detected by sensors Data available on local system Data perceived by decision maker 5 Comprehension of decision maker © Miller and Shattuck, 2003 Statement A: Approved for public release; distribution is unlimited (26 April 2004) 6 Projection of decision maker 26
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 Operational Environment Warfighter – Trident Warrior Analyses • Provides Operational Context • Highlights the Need for CONOPS – HSI Analysis of OIF Issues • Training and Collaboration Were Two Biggest Areas Identified Mission Tasks Statement A: Approved for public release; distribution is unlimited (26 April 2004) Displays/ Interfaces 27
FORCEnet POCs Office of the Chief Engineer Executive Secretary Architecture & Standards (619) 524 -7209 (619) 524 -7237 FORCEnet Implementation (619) 524 -7894 Assessments (619) 524 -7416 Technical Authority (619) 537 -7529 Joint Engagement (619) 524 -2010 Human System Integration (858) 537 -0475 Experimentation (858) 537 -0147 Test/Evaluation/Certification (858) 537 -8652 Statement A: Approved for public release; distribution is unlimited (20 April 2004) 28
Questions? 29
Скачать презентацию FORCEnet Status Today Briefing to the Strike Land
45b173bb6a8548dc08a2cab3a479e1dd.ppt