C omposable m ission s pace e nvironments
Download
1 / 14

C omposable M ission S pace E nvironments - PowerPoint PPT Presentation


  • 57 Views
  • Uploaded on

C omposable M ission S pace E nvironments. 101. Ms. Phil Zimmerman, Chris Turrell, Jim Heusmann, Doug Clark, Vic Dirienso, Kenn Atkinson. “As long as all things are created from scratch, growth can at most be linear”. Constrained Resources. National Military Strategy.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' C omposable M ission S pace E nvironments' - mannix-fitzpatrick


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
C omposable m ission s pace e nvironments

ComposableMissionSpaceEnvironments

101

Ms. Phil Zimmerman,

Chris Turrell, Jim Heusmann,

Doug Clark, Vic Dirienso,

Kenn Atkinson

“As long as all things are created from scratch, growth can at most be linear”


Constrained

Resources

National Military

Strategy

DoD Mission Environment: 2002+

Transformation

MOOTW

Information

Security

Weapons

Proliferation

International

Drug Trade

Increased

Requirements

Major Theater

Warfare

Weapons of

Mass Destruction

Effects-Based

Operations

Network-Centric

Warfare

Asymmetric Threats

FORCE STRUCTURE - READINESS - SUSTAINABILITY - MODERNIZATION


M s what do we have now
M&S: What Do We Have Now?

Stds

Policy

Processes

DoD M&S Strategy:An Analogy to City Planning

Common Technical Framework

Models, Simulations, Tools, Live Systems

Common Services Examples

KI/KE

We have the beginnings of a plan.

We have the initial common

technical framework.

We have many of the essential

common services.

We still need to understand how to

design the buildings and spaces.

SEDRIS

VV&A

HLA

Payoffs:

Interoperability and reuse = capability and cost-effectiveness


Modeling and simulation technology roadmap
Modeling and Simulation Technology Roadmap

Far Term

2010+

Mid Term

2006-9

Near Term

2002-5

  • Interoperable, composable synthetic mission- spaces

  • Rapidly configurable, adaptive human representations

  • Representations of the full spectrum of National Defense issues

  • Full Cultural Shift

  • Static environments

  • Standard architecture

  • Hi-Level Processes

  • IEEE 1516 standards

  • Natural environment standardization

  • Stovepipes

Analysis

Readily Available, Operationally Valid Models & Simulations

Experimentation

Training

Acquisition

Current

  • Rapidly Composable and Scalable Models & Simulations

  • Multi-resolution Model and Object Design

  • Automated Capture of Reasoning / Context

  • Flexible link of Decision Support Systems (DSS) and Simulations

  • Dynamic rather than static environments

  • Robust consistency between live and simulated assets

  • Validation down to algorithmic level


An M&S Application of Today

Product evolution creates user diversity

Initial capability: commonality

Different classes of experienced users

Some game commonality

across products

Interchangeable parts

Social dimension

Today’s Kids (tomorrow’s warfighters) will expect

Similar rapidly composable, transparent capabilities in their warfighting systems!


Where do we need to go
Where Do We Need to Go?

AND AT THE SAME TIME

From Childhood

Reality

To

Warfighter Reality

From Buildings

To

Building Blocks


And just how are we supposed to do all that
And Just How are WE Supposed to Do ALL That?

  • CMSE

    • Take the best of what’s available in:

      • M&S

      • Related disciplines

    • Build only what is necessary

    • Marry theory with current practice

    • When possible, develop broad solutions to specific needs

    • Support composability with applicable policy

    • BE DOMAIN INDEPENDENT


Composable Mission Space Environments

  • Facilitate M&S composability through:

    • Industry, DoD, National, International Stds

    • Best practices

    • Community consensus

Building Mission Space Environments Through Development of:

Use the best of what is available; build only what is needed

Policies

By Participating in Service Efforts to Determine:

  • Partner with related efforts to provide common tools and services for THEIR M&S domain application:

    • Joint Synthetic Battlespace

    • Joint Virtual Battlespace

    • JFCOM Continuous Experimentation Environment

    • Etc.

Requirements

Use current service M&S efforts as testbeds to determine applicability of current M&S technologies, ways to improve them, and areas where M&S technology needs to be fostered

And Still Satisfy the M&S Community’s Desire For:

Reusability

Allow Services and commands to do what they do best, and concentrate on hiding the seams when the different mission space environments are brought together

  • Some pieces already exist:

    • HLA

    • SEDRIS

    • FDMS

    • MSRR

Theory

Practice

Interoperability

Responsiveness

Look to Services for applicability, missing and modifiable components

Uses

Implementations

Goal: Flexibility and Rapid Composability

Technologies

Processes


Cmse at a glance
CMSE at a Glance

  • Program Objectives

  • 1. Determine common needs and applicable technologies for creating flexible synthetic battlespaces for CMSE from warfighter requirements

  • Determine state of the art in softwareand hardware composability, and if principles from other disciplines can be applied to composing modular battlespaces from basic components.

  • Provide missing tools and procedures to assure fitness for use of CMSE components

  • Establish relationships without establishing dependencies (will allow for provision of near term successes – for JSB, JVB, etc.)

  • Establish/use commercial standards

How do we know this is the right thing to do?

  • Multi-resolution and composable simulation environments

  • Link to C4I systems (with reach back)

  • Faster, less costly database development

  • Standardized (reusable) components

  • Reduced Overhead

Warfighter M&S Needs Assessment of the Unified Commands and Selected Supporting Commands

Final Report -17 November 2000

Revalidated – February 2002


Critical common understanding
CRITICAL:Common Understanding

  • Lexical

    • Common vocabulary, data types

      SEDRIS, UOB, FDMS

  • Syntactic

    • Common structures, data delivery

      RTI, STF

  • Semantic

    • Shared understanding

      OMT, FOM, SOM – just the beginning

    • Key to rapidly composable systems

    • Aided by readily accessed data

  • True Interoperability demands all three levels + delivery


Cmse determining direction
CMSE: Determining Direction

  • Where do we start?

    • CMSE Thread: Formal Specification

  • What is currently important to the Services and Commands?

    • CMSE Thread: Experimental Environments

  • How do we enable the collaboration within a mission space development?

    • CMSE Thread: Advanced Distributed Collaborative Environments

  • What is missing from the CMSE tool package?

    • Underlying Technical Challenges

REMEMBER: CMSE is NOT an end in itself – it is an interrelated collection of enabling M&S technologies, tools, and procedures…


Cmse component objectives
CMSE “Component” Objectives

  • Use the Services as willing victims by inserting component technologies into existing battlespace efforts

  • Systematically build CMSE capabilities using short term needs to keep the community interest, and allow real-time valid course correction

  • Demonstrate near-term successes; but with components that are viable in the future

  • Insight on the hypothesis that composability will make reuse, assembling, creating, selecting, recombining, and managing simulations easier

  • Define & bound the problem – establish legitimacy through formal definitions, developed standards and formalisms

  • Establish feasibility and identify implementation issues, technology leverage

Experimental Environments

Formal Specification

Underlying

Technical Challenges

Distributed

Collaborative Environments

  • Ensure CEE components and M&S components are easily integratable

  • Develop CEE standards that enable real-time project collaboration in a distributed environment

  • Evaluate use of SW agent to embed application into the CEE to run applications that are not available to the user locally

  • Develop a standard for the coding of “self-describing simulation components/modules”

  • Add the ability to utilize integrated component contracts for verifying composition integrity

  • Enable the coupling and integration of M&S and live systems


Cmse fy03 program
CMSE FY03 Program

  • Initiate independent study of CMSE to identify, bound and bin the problem

  • Conduct workshops on current state of the art of composability, to gain community consensus on definitions and applicable technologies

  • Develop formalisms which address critical aspects of composability, in order to build higher order tools on them (leverage ONR investment)

  • Design and initiate development of a functional decomposition and specification of composable M&S environments

  • Demonstrate a before and after look at a modified component framework illustrating the use and benefit of automated composability from contracts

Underlying

Technical Challenges

Formal Specification

Distributed

Collaborative Environments

Experimental Environments

  • Build common products to satisfy immediate needs in current M&S “synthetic battlespace” efforts

  • Complete work on current “common” components (e.g. IEEE 1516 acceptance, Sim-ADL formal process for linkage)

  • Establish a first look at using CEE to enable lifecycle reuse of M&S tools and data

  • Develop CEE standards that enable real-time project collaboration in a distributed environment, to include cost and process modeling, and scheduling


C omposable m ission s pace e nvironments1

ComposableMissionSpaceEnvironments

101

QUESTIONS?

“As long as all things are created from scratch, growth can at most be linear”


ad