Joint Modeling and Simulation System JMASS Transition from Development to Sustainment

1
Joint Modeling and Simulation System
(JMASS)Transition from Development to Sustainment
Briefer Bob Meyer, JMASS JPO
Navy Senior Engineer Date 2 April 2003
2
Joint Modeling and Simulation System
(JMASS)Transition from Development to Sustainment
Briefer Bob Meyer, NAWCWD Ops
Research Analyst Date 2 April 2003
3
Joint Modeling and Simulation System
(JMASS)Transition from Development to Sustainment
Briefer Bob Meyer, US citizen
Professional Iconoclast Date 2 April 2003
4
Purpose of this Presentation
Provide a brief status of JMASS products and plans
Review the "truths," implications and their
meaning to the JMASS modeling and simulation
(MS) "paradigm shift."
Highlight the common dependence of all DoD
combat-related MS on the existence and
maintenance of a stable, consistent, well-managed
set of system and phenomena models.
Contend that JMASS customer base is
diverse/growing and that customers are pleased so
far with the product and want more.
Conclude that JMASS provides prototypical
composability for all DoD MS, and JMASS is
fielded and scratching a lot of itches!
5
Joint Modeling and Simulation System

• JMASS is a systems-level software architecture
  that supports MS analysis across the entire
  acquisition cycle - in short, JMASS embodies the
  SBA concept
• Model Standards
• Software Structural Model for Reuse
• Model Application Programming Interface
• Simulation Support Environment
• Simulation Engine
• Model Development Tools
• Analysis Tools
• COTS Legacy Tool Interface
• Model Library Repository
• Local Model and Data Library
• Modeling and Simulation
• Resource Repository

The ability to reuse and interchange
high-fidelity, physics-based models is perhaps
the most visible and important of the many
benefits of JMASS The JMASS customer base
continues to expand and includes a wide variety
of applications supporting acquisition, TE and
operational activities JMASS is currently
supporting Operation Iraqi Freedom
6
JMASS History
1990
1999
1994
1992
1996
2000
1991
1993
1995
1997
1998
JMASS 6.1 JMASS Enters Sustainment
Army/ Navy Withdrawal
Joint Program
Ada/ C JMASS
MSIC
Ada JMASS
JMASS 6.0 alpha
0.3b
3.0
2.0
1.0
3.1
3.2
JMASS 5.0
AF ASC/EN
Army/ Navy Return

PC Prototype
JMASS 98
AETAW

Dynetics IRD
JMASS Prototype
7
Where We Are Now JMASS 6.1

• Primary New Features
• File formats converted to industry standard XML
  and XMI
• All new configuration tool
• Graphical CDF editor (model design and
  development tool)
• SEDRIS support
• Automated installation
• JMASS v6.0 Alpha released 14 Jun 02
• JMASS v6.1 Beta released 16 Sep 02
• JMASS v6.1 Final released 28 Jan 03
• JMASS v6.1.1 scheduled for release in Apr 03
• Primarily bug fixes found with final release

8
Where We Are Headed JMASS 6.x

• JMASS v6.1 is the final development release
• Met over 90 of its JORD requirements 1 year
  ahead of schedule and 5M (20) under budget
• JMASS is on track to enter sustainment phase
• Initially March through November 2003 under same
  contract used for the development phase
• New contract vehicle for subsequent years
• Sustainment will to be jointly funded/managed,
  under ESC oversight and DAC control
• Organic JPO morphed to "Virtual" JPO on 31 Mar 03
• ESC/CXE will manage sustainment with tri-service
  participation
• Conduit for common and service-specific
  enhancements

9
"Truths of JMASS"

• JMASS is NOT a simulation
• All JMASS action is player-based
• JMASS is interface ignorant
• Compliant is NOT interoperable
• JMASS is NOT "plug and play"

10
Views/aspects of a (SAM) simulation

• Legacy
• Monolithic code
• Functional style
• Structured language
• Skewed fidelity
• Do-loop sim engine
• Inter-player interface hidden/convoluted
• Single developer
• Integration occurs "automatically"

• JMASS
• Modular code
• Object-based style
• OO language
• Balanced fidelity
• Separate sim engine
• Inter-player interface visible/concise
• Multiple developers
• Integration requires separate activity

SIMULATION
Model Interfaces
Simulation Engine
Acq Radar
Track Radar
Missile
Aircraft
ECM Sys
RF Env
11
Views/aspects of a (SAM) simulation
Code Generation
Port Mechanism

• Legacy
• Monolithic code
• Functional style
• Structured language
• Skewed fidelity
• Do-loop sim engine
• Inter-player interface hidden/convoluted
• Single developer
• Integration occurs "automatically"

• JMASS
• Modular code
• Object-based style
• OO language
• Balanced fidelity
• Separate sim engine
• Inter-player interface visible/concise
• Multiple developers
• Integration requires separate activity

SIMULATION
Model Interfaces
Simulation Engine
Acq Radar
Track Radar
RF Signal Data Structure
Missile
Aircraft
ECM Sys
RF Env
12
Matrix view of the JMASS system
13
Implications of JMASS paradigm

• JMASS is (supports/needs) distributed development
• Threat models from DIA, blue models from SPOs,
  etc.
• Orthogonal view gives user and developer
  perspectives
• JMASS is (promotes/defines) simulation
  integration
• Simulation integration begins with problem
  decomposition
• Application functionality player list model
  requirements
• JMASS is (enables/benefits from) software reuse
• Software reuse in MS can/does occur at all
  levels
• Debate rages over optimum level of software reuse
• JMASS reuse currently focused at the player level

14
The meaning of what JMASS implies

• Distributed development, simulation integration
  and software reuse focus on two common themes
• Decomposition of analysis problems into system
  and environment players, including model
  requirements, as illustrated by the rows on the
  matrix view of JMASS
• Development, "ownership" and management of system
  and environment models, as illustrated by the
  columns on the matrix view of JMASS

Essential to JMASS a stable, reusable,
well-managed, interface-based set of system and
environment models
15
Matrix view of the JMASS system
16
Relationship to JSIMS/JWARS

• Joint Simulation System (JSIMS) Joint Warfare
  Simulation (JWARS) - DoD MS programs
• JSIMS focused on training, JWARS on campaign
  analysis
• More aggregate (than JMASS) system/environment
  models
• Models aggregated from engagement (JMASS) results
  
• Future may include direct use of JMASS, if
  meaningful

Important to both a stable, well-managed,
consistent, interface-based set of system and
environment models
17
JVB/JSB/JBE/etc. Connections

• Joint Virtual Battlespace (JVB - the Army
  approach) Joint Synthetic Battlespace (JSB -
  the Air Force term) Joint Battlespace
  Environment (JBE - the JFC entry) FEX (the Navy
  entry?) others (JDEP, etc.?)
• Synthetic (simulated) arena of weapon systems
  interacting with each other and natural/man-made
  physical environment
• Goal is to "immerse" warfighter in this simulated
  battle arena
• Focus on System Under Test or Training (SUT),
  with other systems and physical environment
  represented appropriately

Essential to all a stable, well-managed,
consistent, interface-based set of system and
environment models
18
Has anyone addressed this?

• Mr. Jim O'Bryon, former Deputy Director for Live
  Fire Test in the OSD/DOTE office, has suggested
  in many fora over many years that a (collection
  of) consortium (ia) of subject matter experts
  might be the best way to manage MS resources.
• Mr. O'Bryon's exact words were
• "Program Managers would initially describe their
  .. MS requirements to a consortium which would
  then .. make the decisions as to which MS tools
  best suit the PMs needs and subsequently ..
  upgrade extant models where available and
  originate MS only when absolutely necessary."

19
A matrix view of DoD MS
X
20
The DoD MS Iceberg?
System/Phenomenon
Aircraft
Tanks
etc
Ships
Atmosphere
Campaign
Acquisition / TE
Analysis/Experimentation
Force
Training / Education
Aggregation Level
Mission
Engagement
Application
Engineering
21
Looking closer at this Ice Cube
System Models
Model levels of abstraction
Aircraft Representation
Characteristics
Motion RF Signature
..
Campaign
Location changes
Single value RCS
Force
Waterline RCS
3 DOF point mass
Mission
5 DOF motion
Single table RCS
Engagement
Full 6 DOF motion
Multiple table RCS
Engineering
N-point scatter RCS
Dynamic drag/propulsion
Verification and Validation
Accreditation
22
The (JMASS) tip of the Iceberg ?
System/Phenomenon
Aircraft
Missile
Gun
Radar
ECM
Campaign
Acquisition / TE
Surface-to-Air Analysis
Force
Training / Education
Aggregation Level
Mission
Engagement
Application
Engineering
23
Diverse, Growing User Community

• Current user community very diverse, includes
  agencies/companies working these problems
• Dismounted infantry conducting urban warfare
• Aero design/development, operator training,
  hardware in the loop, survivability assessment
  for UAV platform
• DIS-compliant simulation of networked
  communications
• Anti-helicopter acoustic mine susceptibility
  studies
• Naval defense against air-to-surface missile
  threats
• Torpedo engagements as part of undersea warfare
• Modeling support to ESM system development
• Open air range simulation of threat kill
  mechanisms
• Hardware in the loop missile simulation
  capability
• Oh yes, airborne EW/EC the original customer!

24
A real success story

• At a recent user forum, these praises were heard
• Standard and extensible interfaces and services
• Stable, fielded, cross-platform, open source
  software
• Distinct, flexible division between architecture
  and models
• Rapid, well-GUI'd, modular MS development tool
• On the other hand, dislikes were cries for
• More extensive and automatic documentation
• Massively parallel and distributed processing
  capability
• More features in all areas tools, models, GUI's
• In general, improvements in existing capability
  the sort of stuff that sustainment is made for/of

25
In summary...

• JMASS has highlighted the DoD corporate need for
  a stable, consistent, well-managed,
  interface-based set of system and environment
  models.
• JMASS doesn't melt the DoD MS "Iceberg," but it
  does reveal a tip, complete with lessons learned.
  
• Composable simulations before composability was
  cool!
• Ability to compose simulations requires
  well-ordered mix of common (joint) MS standards
  and specific applications.
• JMASS is an existing, extensible infrastructure.
• Current release (v6.1) is very stable, capable,
  usable.
• User community very diverse and continues to
  expand.

26
To contact JMASS Program Office

• http//www.redstone.army.mil/amrdec/jmass
• [phone] (DSN 478-)
• Lt Denise Herrera, Deputy Program Manager
• E-mail Denise.Herrera_at_hanscom.af.mil
• ESC/CXES
• 15 Eglin Street, Bldg 1607
• Hanscom AFB, MA 01731-2100