1. General Dynamics Advanced Information Systems
Importance of Web-Enabled Modeling & Simulation Applications Within the Global Information Grid with Current and Future Capabilities
Johnny Garcia
Chief Technologist
General Dynamics Advanced Information Systems
Suffolk, Virginia
(757)

2. “Possibly the single-most transforming thing in our forces will not be a weapons system, but a set of interconnections and a substantially enhanced capability because of that awareness.” —Secretary of Defense Donald Rumsfeld, August 9, 2001.

3. Presentation Outline Introduction M&S Transformation
Level of Conceptual Interoperability
Network-Centric Operations and Warfare
Global Information Grid (GIG)
M&S Common Architectural Frameworks
Summary
Technical level - exchange of bits and bytes - supposed to be solved,
IPv6 will take care of it, JTRS brings this to the places where no internet exists, etc. Need more information on IPv6, do you have a paper I can read

4. Introduction

5. M&S is undergoing a fundamental transformation
State-of-the-Art: DIS, HLA, ALSP are targeting the implementation level
System Centric view
Limited Extensibility, Reusability, and Composability
New: “Net Centricity” Software reconfigurable IP based computer
Networked system capable of supporting:
Extendible services, XMSF, XBML, XML
Advanced information/functionality sharing
Advanced (simulation based) applications for:
Data mining/sense-making tactical analysis
Decision support, planning and execution monitoring
Process improvement
Acquisition

6. Levels of Interoperability
Technical Level
Exchange of Bits and Bytes
Syntactic level
Protocols to exchange data
Data replication, federation object models
Semantic level
Data in context
Reference models
Pragmatic level
Conceptual models of Implementations
Platform Independent Models of the Model Driven Architecture
UML Version 2.0
Conceptual level
Agreement of the View of the World, Common Conceptual Model
Technical level - exchange of bits and bytes - supposed to be solved,
IPv6 will take care of it, JTRS brings this to the places where no internet exists.
Syntactic level - we have to agree on protocols to exchange data, mostly
taken care of. But this is just the data level, such as datareplications,
federation object models, etc.
semantic level - we start to talk about information, i.e. data in
context. We not only speak correct, we speak understandable. Reference models are needed. Here is still a way to go.
pragmatic level - how do I use the information, i.e. knowledge. We do
not have a real concept on how to deal with this. The MDA with the PIMs is a first pitch, so is UML Version 2.0, but is it sufficient? I don't think so, more information on PIM's
conceptual level - we have the same mindset when dealing with things. we
are in agreement about what and how we are doing something as well as
about what we are not doing. Beside very limited efforts on conceptual
modeling - such as the UML business model of the USNavy - there is
nothing available.
If we want web-enabled simulation, we have to work on all levels.

7. Net Centric Operations and Warfare (NCOW) will utilize Web based
Net Centric Operations and Warfare Force Characteristics
Physical Domain: All elements of the force are robustly networked achieving secure and seamless connectivity.
Information Domain: The force has the capability to collect, share, access, collaborate, analyze, and protect information, achieving an information advantage over an adversary.
Cognitive Domain: The force has the capability to develop shared knowledge of commanders' intent, share high-quality situational awareness, and self-synchronize its operations
Net Centric Operations and Warfare (NCOW) will utilize Web based
technologies to enable a force with these characteristics, and provide an
integrated framework to support the force using enterprise business practices

8. Network-Centric Operations and Warfare Value Chain
Data Quality
Data in the underlying Command and Control Systems
Information Quality
Completeness, currency, consistency, and precision of the items
Data in context, understanding of the data
Knowledge Quality
Procedural knowledge, embedded information
Agile data, understanding of the process
Awareness Quality
Degree of using the information
Cognitive domain
Based on D. Alberts, J. Garstka, R. Hayes, D. Signori: “Understanding Information Age Warfare,” CCRP Publication Service, August 2001

9. “DoD must move from an organization with a top-down approach to operations to one that distributes authority for action to ‘the edge,” --Assistant Secretary of Defense for Command, Control, Communications, and Intelligence (C3I) John Stenbit

10. Global Information Grid
Global “Info sphere” based on:
IP enabled flexible “ad hoc” networks:
IPv6
Web Based Enterprise Services (NCES/GES)
Platform/OS independent
Commercial base/Military specific COI functionality
Integrated Seamless Global Communications:
MILSAT/COMSAT
JTRS
Optical land networks
Business and process rules for management
IPV6

11. DOD Net-Centric Data Strategy
“The Core of the net-centric environment is the data that enables effective decisions. In this context, data implies all data assets such as system files, databases, documents, official electronic records, images, audio files, websites and, data access services….”
COI
Address organization and maintenance of data
Metadata
DOD Metadata registry
GES/NCES
Enable data tagging, sharing, searching and retrieving

12. Interoperability is the failure to integrate!
Common Architectural Frameworks For M&S
MDA Approach required for:
Architectures too complex for 2-D description:
Architectures as a collection of dynamic objects, and their interactions vice “wiring diagrams”
“Executable” architectures provide enhanced insight for Life cycle: design, procurement, deployment and management.
MDA approach in common architectures would yield the integration of
systems. This is crucial to meet the requirements of the future.
Interoperability is the failure to integrate!

13. Extensible M&S Framework
XMSF contributes to the transformation of the armed forces by helping to fulfill requirements for software systems derived from future military operations
The only software systems that composably scale to worldwide scope utilize Internet and web technologies
Web-based technologies applied within an extensible execution framework
are enabling a new generation of modeling and simulation applications to
emerge, develop, and interoperate in the commercial world

14. XMSF C4I Test Bed / Extensible Battle Management Language
Definition:
BML is the unambiguous representation of doctrine
applicable for C4ISR, M&S,
and robotics
Project Objective:
Transfer the Army Project Battle Management Language to a Joint and Combined Solution based on Open Standards

15. Leverage the work conducted by the community
TRM as a standard for development of SIMCI

16. Open Standards DOD mandated GD AIS and Multi-consortia
Importance
DOD mandated
GD AIS and Multi-consortia
Open standards bodies (SISO, OGC, W3D, W3C WEBSIM etc.)
Terrain
Visualization
Interoperable code
Data Standards

17. Web-Services for M&S What are Web-Services
Discrete web-based applications that interact dynamically with other web-services
Necessary sub-functions of web-services
Functionality self-description of the service
Publishing of service descriptions
Locating the service with the required functionality
Requesting the required data to initiate the service
Establishing the data exchange, including delivering the results

18. M&S Services in the GIG Long term goal
Full integration of M&S services into the GIG
Application domains and communities of interest (COI)
M&S kernel services as part of the GIG Enterprise Services (GES)
Example: RTI services, distributed FEDEP support, etc.
M&S Application COI
Example: Joint National Training Capability (JNTC), Distributed Continuous Experimentation Environment (DCEE), Joint Deployment Process Owner (JDPO) etc.
M&S Support as a Cross-Domain COI
Seamless interoperability between M&S and C4I systems
Work existing Interfaces to validate needed changes
Work with C4I Developers of DII COE/NCES software to build in M&S requirements
Alignment of M&S and C4I standards, architectures, and common C4I components.
Identification of requirements for simulations and C4I to support interoperability

19. GIG Enterprise Services
Support real-time & near-real-time warrior needs, and business users
DoD (Title 10)
IC (Title 50)
Business Domains
Warfighter Domains
National Intelligence Domain
Users
Users
COI’s
Installation
& Environment
Human Resource Management
Force Application IC
Org Spaces
Command & Control
Domain/ COI Capabilities
M&S
Cross Domain COI’s
COI’s
Protection
Strategic Planning
& Budget
Expedient COI’s
Acquisition
COI’s
Levels of Services Above Core Level
Focused Logistics
Battlespace Awareness
Accounting & Finance
Logistics
COI’s
ICSIS Community Space
User
Assistant
Storage
Messaging
IA/Security
Application
IA/Security
ESM
IA/Security
ESM
IA/Security
ESM
IA/Security
ESM
ESM
Discovery
Collaboration
Mediation
Enterprise
Service
Management
(ESM)
Technical Infrastructure Domain
IA/Security
ESM
IA/Security
ESM
IA/Security
ESM
IA/Security
Core Enterprise Services (CES)
Transformational Communications (TC) & Computing Infrastructure

20. Summary and Recommendations

21. Summary and Recommendations
DoD is shifting from system centric to network centric
M&S community must do the same
M&S functionality needs to evolve into an operational context
Legacy way of thinking must change, (M&S in not just for training anymore)
GIG is the technical framework
M&S based Web-Services are feasible
M&S Standards for Web-Service needed
Common MDA approach is needed
M&S Community must:
Harmonize the necessary M&S standardization efforts with the GIG Requirements
Transfer M&S requirements to the GIG Developers
Facilitate an understanding of M&S in the GIG