NAVAIR IM

1
NAVAIR Process and Information Modeling for
Shipboard Systems Spring 2001 Simulation
Interoperability Workshop Paper
01S-SIW-075 Michael Malesich, NAVAIR Joseph
Stanco, SSAI Joseph Lacetera, Monmouth
University/MSTI
2
Outline

• Introduction and Background
• The WARCON JSB
• NAVAIR MS and the use of IDEF
• November 2000 I/ITSEC Demo
• Summary and Conclusions
• Key Points

3
Introduction

• This presentation describes the current
  development at NAVAIR, Lakehurst, New Jersey, of
  Nuclear Carrier Vessel (CVN) systems and
  operations models
• Process models
• Information Management (IM) models
• Internal MS requirements involve avionics
  operations aboard CVNs
• External MS requirements involve
• The Warfighting Concepts to Future Weapon System
  Design (WARCON) Joint Synthetic Battlespace
  (JSB)
• Navy Fleet Battle Experiments

4
Relevance to SISO

• Interfacing of COTS-tool developed models with
  the RTI
• IDEF as a supporting technology
• Cross-platform (Windows/Linux) model
  interoperability
• HLA/RTI as an enabler in distributed simulations

5
Warfighting Concepts to Future Weapon System
Design
Warfighters Requirements
Collaborative Engineering Reuse -
Networks/Models Interface Standardization
Integrated Design Environment
Joint Synthetic Battlespace
vs. Performance
Personnel Requirements Operational
Procedures Effectiveness

Hardware Design / Support Infrastructure
6
Mission Space

• Joint forces weapon systems and personnel
• CVNs
• Carrier Weapon Handling Systems (CWHS) and Flight
  Deck Operations (FDO)
• models in development at Newport News Shipyard
  (NNS)
• Information Management and Improved Information
  Management Systems
• models in development at NAVAIR, Lakehurst
• Time Critical Strike (TCS) scenarios
• Time Critical Target (TCT) Time-to-Launch (TTL)
  query

7
NAVAIR MS Approach

• The NAVAIR MS program supports the evolution
  from platform-centric to network-centric program
  operations and initiatives
• Concurrent modeling and simulation of both
  as-is IM and to-be I2M systems
• A standard modeling methodology and architecture
• an iterative, holistic approach that establishes
  the functional behavior of the whole system based
  on the interdependencies of its parts

8
I2M Development Approach

• NAVAIR first developed process models to show how
  weapons management operations are currently
  handled
• The process models were then used to develop the
  I2M models. The system to be modeled includes the
  following elements
• Operational processes and functions
• Information and communication processes
• Human operators and workstations
• Hardware and equipment systems
• Data and information requirements
• Show how operations might be improved if an I2M
  system were implemented aboard CVNs

9
NAVAIR Model Development

• NAVAIR process and information models are
  developed using a Commercial-off-the-Shelf (COTS)
  Integrated Definition (IDEF) tools which provide
  an IDEF0/IDEF1X modeling environment
• IDEF provides a standard architecture and set of
  definitions
• Captures the required knowledge of subject matter
  experts
• Provides a reusable framework
• product development
• testing various scenarios to determine the
  effectiveness of the identified opportunities for
  improvement

10
IDEF Syntax
11
Modular/Hierarchical Structure of IDEF
User controls level of detail and model
decomposition
12
Modeling Tools

• Meta Software WorkFlow Modeler
• builds the IDEF models
• Meta Software WorkFlow Analyzer
• simulates the IDEF model
• ProModel
• linked to the MetaSoftware environment
• used for rapid prototype development
• discrete event models
• only external interface is via a subroutine to
  external code that has been compiled into a
  Dynamically Linked Library (DLL)

13
Modeling the as-is system

• The IDEF0 tool is used to develop a process model
  of the as-is IM system based on the objectives
  and originating requirements as specified in the
  operational requirements
• The IM operation is simulated to establish and
  validate a system baseline against which
  subsequent studies are compared
• A set of information models and interfaces to
  support the data flow between the various
  portions of the system model development are then
  developed
• The information interface is based on the process
  model inputs, controls, outputs, and mechanisms,
  user-defined data fields, glossary entries, and
  information requirements

14
Modeling the to-be system

• The finished IM tool set is used to synthesize
  the I2M model which is optimized by performing
  the following tasks
• Simulate the to-be model
• Compare the results to the baseline
• Iteratively modify the to-be until maximum
  benefits are achieved or required results are
  obtained

15
Logical View of NAVAIR/JSB Federation
FDO and CWHS NNS federates provide real-time
ground truth to NAVAIR IM/I2M
NAVAIR Federate includes IM/I2M models which
receive TTL queries from JSAF
NAVAIR FOM supports internal MS requirements and
WARCON JSB
16
Interfaces developed for WARCON

• NAVAIR IM/I2M NNS FDO and CWHS models
• NAVAIR models receive real-time ground truth
  information related to weapons handling and
  flight deck operations being simulated by NNS
• NAVAIR IM/I2M JSAF
• TTL queries from JSAF

17
ProModel Interface

• To facilitate data transfer in an HLA
  environment, a ProModel Interface (PMI), has been
  developed by the BMH Corporation to provide a
  run-time interface to the RTI
• The PMI supports a subset of the DMSO HLA
  capability
• Joining and leaving an HLA federation
• Object publication and subscription
• Object reflection
• Interaction publication and subscription
• Time management

18
WARCON JSB Federation View
19
WARCON I/ITSEC DEMO OF TCT/IM PROCESS
20
I/ITSEC Demo

• Interfaces between the NAVAIR and the NNS models
• Two aircraft (F14A and F18C)
• Two types of munitions (MK-82 and MK-83)
• Ground-truth status provided by the NNS models
• Aircraft tail number, current location, munition
  load status, and fuel status
• Munition quantity, build status, and location
• The IM/I2M simulation
• Process of loading appropriate munitions and fuel
  onto appropriate aircraft for the mission
• TTL estimate sent to JSAF based on the weapons
  and aircraft status at the time of the request

21
Summary

• This presentation described the current
  development of discrete-event CVN models in a
  joint mission space involving TCS scenarios
• The models were developed in an IDEF0/IDEF1X,
  COTS modeling environment that allows efficient
  and rapid prototype development
• The simulation environment involved
• Windows and Linux platforms in an HLAenvironment
• linkage between discrete-event and aggregate
  models

22
Conclusions

• IDEF development approach supported
  object-attribute and interaction-parameter
  identification
• Cross-platform model interoperability was not a
  significant issue in the simulations
• Complications associated with interfacing the
  discrete-event models with the RTI was overcome
  by the development of the PMI by BMH

The RTI was found to be an enabler in distributed
simulations
23
Key Points

• Key Point 1 The special run-time interface to
  the RTI supports time-dependent data transfer
  between the COTS-model federate and other
  federates without latency issues
• Key Point 2 While the efforts on the part of
  the PMI developers and the NAVAIR modelers
  effected the required linkage, the success of
  this linkage demonstrated the strength of HLA/RTI
  as an enabler in distributed simulations