The Joint Strike Fighter JSF Strike Warfare Collaborative Environment SWCE

1
The Joint Strike Fighter (JSF) Strike Warfare
Collaborative Environment (SWCE) September, 2000
James E. Coolahan James.Coolahan_at_jhuapl.edu 240-22
8-5155
Frederic T. Case FT.Case_at_jhuapl.edu 240-228-8740
Lt Col Robert J. Hartnett, Jr. HartnettRJ_at_jast.mil
703-601-5650
Johns Hopkins University Applied Physics
Laboratory 11100 Johns Hopkins Road Laurel, MD
20723-6099
Joint Strike Fighter Program Office 1213
Jefferson Davis Highway Suite 600 Arlington, VA
22202
2000 Fall Simulation Interoperability Workshop
2
Presentation Outline

• Joint Strike Fighter (JSF) Background
• Review of SBA Architecture Concepts
• JSF Collaborative Environment Concepts
• The JSF Strike Warfare Collaborative Environment
  (SWCE)
• The JSF Resource Access System (RAS)
• The JSF SWCE Management Process
• Summary

3
Joint Strike Fighter Background

• The JSF program is the U.S. DoDs focal point for
  defining an affordable next-generation strike
  aircraft weapon system for the Navy, Air Force,
  Marines, and U.S. Allies
• An early commitment was made in the JSF program
  to modeling and simulation to provide a solid
  analytic foundation for evolving requirements,
  reducing costs, and performing tradeoff analyses
• The Virtual Strike Warfare Environment (VSWE),
  begun in 1994, has provided the virtual component
  of the JSF MS architecture during the Program
  Definition and Risk Reduction (PDRR) phase
• Seven VSWE experiments have been conducted since
  May 1998, culminating in VSWE 7 in the summer of
  2000
• The JSF program has developed, and is evolving, a
  Modeling and Simulation Support Plan (MSSP) for
  the Engineering and Manufacturing Development
  (EMD) phase

4
Simulation Based AcquisitionVision Statement and
Goals

• Vision An Acquisition Process in Which DoD and
  Industry Are Enabled by Robust, Collaborative Use
  of Simulation Technology That Is Integrated
  Across Acquisition Phases and Programs.
• Goals The Goals of Simulation Based Acquisition
  (SBA) Are to
• Substantially Reduce the Time, Resources, and
  Risk Associated With the Entire Acquisition
  Process
• Increase the Quality, Military Worth and
  Supportability of Fielded Systems, While Reducing
  Total Ownership Costs Throughout the Total Life
  Cycle
• Enable Integrated Product and Process Development
  (IPPD) Across the Entire Acquisition Life Cycle.

Source Acquisition Council of the DoD Executive
Council for Modeling and Simulation (approved 5
Dec 1997). The vision was also re-approved as a
concise definition of SBA by the Acquisition
Council on 21 Aug 2000.
5
Key SBA Architecture Constructsfrom the SBA
Roadmap

• Collaborative Environments (CEs)
• Within the context of SBA, a collaborative
  environment (CE) is an enduring collection of
  subject matter experts (SMEs) supported by
  interoperable tools and data bases, authoritative
  information resources, and product/process models
  that are focused on a common domain or set of
  problems.
• The Collaborative Environment Reference Systems
  Architecture (CERSA)
• Distributed Product Descriptions (DPDs)
• A Distributed Product Description (DPD) is a
  distributed collection of product-centric
  information that is interconnected via web
  technology into what appears (to the user) to be
  a single, logically unified product
  representation.
• The DoD/Industry Resource Repository (DIRR)
• Data Interchange Formats (DIFs)

6
Essential Elements of aCollaborative Environment
(CE)
Purpose

• A defined purpose for which the CE is intended to
  be used
• The involvement of subject matter experts (SMEs)
  from all functional disciplines that are
  stakeholders in the domain or set of problems
  upon which the CE is focused
• Availability of a set of interoperable models,
  simulations, tools, and data appropriate to the
  domain or problem set
• Systems to enable electronic collaboration over a
  distance for exchange of information, access to
  authoritative data, and execution of simulations
• A systems architecture framework for the CE,
  derived from a common reference, such as the
  CERSA
• An agreed upon set of standards, rules, and local
  conventions, to which all CE users and components
  adhere
• An agreed upon set of processes for configuration
  management and for Verification, Validation, and
  Accreditation (VVA)
• Coordinated policy, planning, and investment
  strategies to ensure continuing support of the CE

People
Tools
Standards
Processes
7
Top-Level View of the SBASystems Architecture
8
Collaborative Environment Reference Systems
Architecture (CERSA)

• Notes
• Intended as an overall framework
• Every component type need not be represented in
  every Collaborative Environment

8
9
Primary Uses of Joint Strike FighterMS Toolset
during EMD

• Assist the Weapon System Contractor in early and
  continuous weapon system trade studies
• Assess compliance with the Joint Operational
  Requirements Document and the performance-based
  Joint Model Specification
• Improve the planning and execution of
  developmental and operational testing
• Support warfighters in developing JSF Concepts of
  Operation
• Improve warfighter skill proficiency through
  high-fidelity mission rehearsal
• Allow inclusion of the JSF in CINC- and
  Service-sponsored Advanced Warfighting
  Experiments (AWEs) and Joint Force Exercises
  (JFXs)
• Support logistics and supportability, training,
  mission management, and operational employment
  requirements
• Orient and educate interested parties on JSF
  concepts and capabilities
• Support decision-making regarding JSF force
  structure requirements
• Support the implementation of timely, credible
  analyses regarding emerging issues
• Enable more direct and rapid translation of
  operational requirements into systems engineering
  process tools

10
Focus Areas for JSF Collaborative Activities
during EMD

• Mission Effectiveness Analysis
• Evaluation of effectiveness of JSF to perform its
  total set of missions
• Includes performance-oriented simulations
  primarily at the mission level, but also at the
  campaign and engagement levels
• Supportability Analysis
• Supportability requirements and capabilities
  throughout the life cycle
• Cost Analysis
• Determining total ownership cost (TOC)
• Engineering and Manufacturing Analysis
• Engineering and manufacturing by the Weapon
  System Contractor
• Includes requirements management and traceability
• Direct linkage to design and development tools,
  data products, and analysis of engineering and
  manufacturing processes

11
Focus Areas of JSFCollaborative Environments
The JSF Strike Warfare Collaborative Environment
(SWCE) is defined to be that Government-managed
CE that is used to support the collaboration
focus areas of mission effectiveness analysis,
supportability analysis, cost analysis, and
engineering and manufacturing analysis.
Mission Effectiveness Analysis
Afford- ability Analysis
Support- ability Analysis
Engineering and Manufacturing Analysis
JSF Engineering and Manufacturing Collaborative
Environment
JSF Strike Warfare Collaborative Environment
12
JSF Collaborative Environment Components and
Relationships
JSF Strike Warfare Collaborative Environment
(SWCE) Toolset
JSF Engineering Manufacturing Collaborative
Environment (EMCE) Toolset
JSF Suite of Models and Simulations (SoMS)
SWCE SoMS
EMCE SoMS
MSDB
MSDB
JSF Distributed Product Description (DPD)
Scenarios
Scenarios
Databases
Databases
Authoritative Systems Data Base (ASDB)
JSF Resource Access System (RAS)
13
Components of the JSF SWCESuite of Models and
Simulations

• ACQUIRE
• AFMSS/AR Air Force Mission Support System /
  Auto-Router
• ASM Aircraft Sustainability Model
• Brawler
• CALM Consolidated Air Load Manifest
• CFAM Combat Forces Assessment Model
• COVART Computational Vulnerability and Repair
  Time
• DIADS Digital Integrated Air Defense System
• DISAMS
• EADSIM Extended Air Defense Simulation
• ESAMS Enhanced Surface-to-Air Missile Simulation
• FASTGEN Fast Shotline Generator
• FLIR 92
• GIANT GPS Interference and Navigation Tool
• HITRAN
• JCCM Joint Common Cost Model
• JCORE Joint Services Cost Oriented Resources
  Estimating Model

JIMM Joint Interim Mission Model JOSTE JSF
Operating and Support Technologies Evaluation
Model JVS JSF Virtual Simulator LCOM Logistics
Composite Model LOWTRAN Low Spectral Resolution
Transmission MIL Man-in-the-Loop Air-to-Air
AASPEM-II System Performance Evaluation
Model MODTRAN Moderate Spectral Resolution
Transmission MOSAIC Modeling System for the
Advanced Investigation of Countermeasures RADGUNS
Radar-Directed Gun Simulation RCHEM Residual
Chemical Hazard Environment Model Shazam SPIRITS S
pectral In-Band Radiometric Imaging of Targets
and Scenes Thunder
14
JSF SWCE MS Component Usesby Collaboration
Focus Area
15
The JSF Resource Access System

• A web-accessible application, or set of
  applications, to provide JSF-authorized users
  with a means to access, explore, and download
  information
• Will provide access to
• The JSF Distributed Product Description (DPD)
• The JSF Authoritative Systems Data Base (ASDB)
• The Multi-spectral Data Base (MsDB)
• Scenario databases
• Other JSF software, documentation, etc.
• Authoritative non-JSF resources (with owner
  approval)
• May consist of a commercial Product Data Manager,
  augmented with additional functionality
• Implements functionality, for JSF, similar to
  that envisioned for the DoD/Industry Resource
  Repository (DIRR)

16
JSF Resource Access SystemDesired User Interface
Features

• Access controls, preferably using Public Key
  Infrastructure (PKI) technology
• An information map, search tools, and glossary to
  allow users to find and understand information
• A presentation of the various JSF versions and
  variants represented in the DPD, and the ability
  to search and select among them
• Parsing tools to allow user-tailored display and
  download
• Preferably, subscription and trigger mechanisms
  so users can elect to be alerted when specific
  information changes
• Preferably, depictions showing expected download
  time for a selected data set, and download
  progress while underway

17
The JSF SWCE ManagementProcess
The JSF Modeling and Simulation Support Plan
(MSSP) addresses the following MS management
functions conducted by or for the JSF Program
Office

• Configuration Management of the JSF MS Toolset
  to
• Evolve tools and databases to support Government
  and Weapon System Contractor needs
• Manage code and data distribution to JSF users
• Control configuration of the SWCE MS Toolset
  through semi-annual Configuration Control Boards
  (CCBs)
• JSF Data/Model Improvement Program
• Upgrades and updates to Government-owned models
  and databases
• JSFPO does not own any individual models
  supplies funding and requirements to model owners
• Verification, Validation, and Accreditation
  (VVA)
• JSF process based on DMSO Recommended Practices
  Guide
• Verification Validation (VV) normally done by
  model owner/manager
• Accreditation is the JSFPOs responsibility
  tailored approach developed by Joint
  Accreditation Support Activity (JASA)

18
Summary

• The Joint Strike Fighter program intends to
  enhance its ability to represent the JSF in
  realistic synthetic environments during EMD
• The JSF Strike Warfare Collaborative Environment
  (SWCE) will be developed and maintained by the
  JSF Program Office to support the focus areas of
• Mission effectiveness analysis
• Supportability analysis
• Cost analysis
• Engineering and manufacturing analysis
• The architecture of the JSF SWCE builds upon two
  key architecture concepts described in the SBA
  Road Map
• Collaborative environments
• The Distributed Product Description (DPD)
• The JSF Program Offices Modeling and Simulation
  Support Plan (MSSP) includes provisions for
• Configuration Management of the JSF MS Toolset
• Verification, Validation, and Accreditation
  (VVA)
• A Data/Model Improvement Program