AMC RDEC Federation Collaborative Biome Proof Of Principal Demonstration CBPOP

1
AMC RDEC FederationCollaborative Biome Proof Of
PrincipalDemonstration (CBPOP)

• Tom Strelich

2
Briefing Agenda

• Introduction
• Background/Business Case
• Problem Characteristics
• Simulation Integration Architecture
• Conceptual Elements
• Architecture
• Core Technologies
• Simulation Integration Infrastructure
• Approach
• Collaborative Environment
• Questions

3
The Army Transformation
System of Systems
. . . The Army is transforming itself and the AMC
RDEC Federation can play a major role
4
AMC RDEC Federation
Integrated Data Environment
AMC COE ERDC
5
Design-Collaborate-Evaluate (DCE) CyclesBridge
between Static and Dynamic
Dynamic Interoperation
Static Integration
Design
Evaluate
Collaborate
Integrated Data Environment
6
Candidate CBPOP Use / Case Models

• Static Parts
• Element(s) can have multiple static DCE cycles
• Static results carry over to dynamic
• Dynamic Whole
• Performance models
• Mission Evaluation

7
Nested Static and Dynamic Cycles

• Use Case 1- Sensor Design Trade
• Two different 3G FLIR prototypes
• Detection Range/Sensitivity Analysis
• Sensor - ATR Engine Interface/Design

• Use Case 2- Sensor/C3/FCS
• Timeline Analysis -
• Sensor-C3-FCS Vs Sensor-FCS
• Network Traffic/Loading
• Analysis

• Use Case 3- Sensor/C3/FCS/Munitions/Target
• Kill Ratio Analysis - Vehicle dynamics Vs
  munitions performance
• Lethality Analysis - Warhead design Vs Target
  damage
• Timeline Analysis - Overall Sensor-Shooter
  performance due to improved Comm

8
SMART/SBA Business Case

• Develop and operate the system in the computer
• Phase-specific assessments
• Requires integration and interoperation of
  simulations, models, tools, utilities,
  applications, and databases
• Defines the problem

OPERATIONAL EMPLOYMENTS
Deployable Definition
Lessons Learned
TRAINING, PLANNING REHEARSALS
WARFARE ANALYSES/ ASSESSMENTS
Operational Definition
Require- Ments
RESEARCH DEVELOPMENT
VIRTUAL PRODUCT MODEL
TEST EVALUATION
Design Definition
Product Definition
MANUFACTURING
9
Problem Characteristics

• Integration - new/legacy software
• Simulations, Models, and Tools
• Utilities, Applications, Databases
• Heterogeneous6
• Interoperation - new/legacy software
• Simulations, Models, and Tools
• Utilities, Applications, Databases
• Heterogeneous6
• Distributed
• Developer
• User
• Evolving
• Technology
• Requirements

Common characteristics drive a plug-and-play
integration architecture
10
Simulation Integration/Interoperation (I2)
Architecture
Interoperation
Integration
Data Space
User Interface Space
DataObject a
SimulationObject Proxies
DataObject b
DataObject c

ModelObject Proxies
DataObject z
Applet
ToolObject Proxies

• Objects distributed over multiple, heterogeneous
  platforms
• PC/Windows/NT
• PC/Linux
• Unix
• IBM Mainframe

ORB/RMI/RTI
html
Analysis Space
ToolObject Proxy Servers
ToolObjects
Applets
ORB/RMI/RTI
ModelObject Proxy Servers
ModelObjects
Control Space
SimulationObject Proxy Servers
SimulationObjects
Common architecture based on core software
technologies
11
Core Integration Technologies

• Internet
• Platform-independent world-wide access to
  static/dynamic content
• CORBA
• Common Object Request Brokering Architecture
• Standard software backplane/bus
• Platform/language-independent interoperability
• Allows programs written in different languages at
  different times on different machines to
  interoperate
• Java
• Platform-independent data/database connectivity
• Spontaneous networking
• Portable reusable data and behavior

Display Integration
Control Integration
/Jini/XML
Data Integration
Technology confluence that finally makes software
plug-and-play a reality
12
Jini -- Spontaneous Networking
What is it? Set of Java APIs and network
protocols

• Creation of service federations
• Service is anything that can be connected to a
  network
• All services are equal peers
• All services provide mobile proxies allowing
  clients to use the service
• Network-resident runtime infrastructure
• Find, access, add, and remove services
• Leasing and transaction services for recovery
• OS and network protocol independent
• Architecture/programming model addressing a new
  distributed computing scenario
• Heterogeneous mix of networked desktop and
  embedded devices

Same scenario facing SBA Client and service are
both simulations
13
Jini -- Implications

• Concept Focus
• Device Federations
• Wireless and wirednetwork links

• Focus Expansion
• Device simulation
• Service Device GPS Satellite Constellation
  Simulation
• Registered via Jini LS
• Client Device Aircraft Simulation
• Finds, downloads proxy via Jini LS
• Executes service via proxy
• Proxy hides complexity
• Proxy Federate Ambassador
• Proxy Development Challenge
• Open-ended complexity

• No magic
• Intuitive Concept
• Clean Architecture
• Industry Momentum

14
XML eXtensible Markup Language

• Universal schema defining portable data
• Structure, Content, and Presentation
• Eventual HTML replacement
• Extensible
• User-defined tags
• Domain and market-specific dialects and languages
• Industry Interest and Momentum
• World Wide Web Consortium (W3C) approval
• Microsoft, Oracle, IBM, and others adopting
• Application Domains
• Data warehousing/mining
• Electronic Data Interchange (EDI)
• Enterprise Application Integration (EAI)

• Same domains as SBA
• Simulation integration and interoperation

15
I2 Infrastructure Approach

• Recognize difference between Integration and
  Interoperation
• Building vs running an engine
• Exploit commercial-sector Integration
  technologies
• Java, CORBA, Jini, XML
• Proxies encapsulate underlying MS complexity
• Exploit HLA Interoperation technologies
• High fidelity formal semantics
• Runtime dynamics
• Best of both worlds

Java/Jini/XML Integration
Static
HLA Interoperation
Dynamic
16
Collaborative Environment

• User view
• Bridges static integration with dynamic
  interoperation
• Java/Jini/XML provide connection and integration
  mechanism
• HLA provides interoperation and transaction
  mechanism

Collaborative Environment
17
Collaborative Environment(s)

• Q What's Collaborative Environment?
• A
• A room with a whiteboard...
• LotusNotes and a phone
• A full-blown tool for assembling/executing ad hoc
  simulations out of simulation building blocks
• All of the above
• There won't be one Collaborative Environment
• There will be multiple Collaborative Environments
  and they'll interact in a Collaborative Biome

18
Collaborative Biome

• Biome a complex biotic community characterized
  by distinctive species and maintained under
  climatic conditions of the region largest
  ecological unit containing many interacting
  ecosystems
• Examples Tundra, Desert Scrub, Temperate
  Grasslands

• Conceptual Mapping
• Distinctive species models and simulations
• Climate Aviation, Communication, etc.
• Ecosystem ACR, RDA, TEMO
• Concept Value
• Identify and accept the undeniable -- multiple,
  heterogeneous, interacting Collaborative
  Environments
• Identify opportunities -- integration and
  interoperation infrastructure

19
SimClient

• Filter visibility/access to local and remote
  models, simulations, DBs, and tools

• Drag-and-drop simulation, model, tool, and DB
  proxies into the SimulationSandbox
• Define interactions
• Specify pre/post-conditions
• Set in/output parameters and runtime
  configurations
• Run the Sandbox
• SimulationSandbox -- as formal as an HLA Federate
  or as informal as an ad hoc prototype integration

20
Collaborative Biome Components - RDEC Federation

• Runtime Infrastructure (RTI)
• HLA cornerstone
• Emphasis on Runtime
• Integration Time Infrastructure
• The missing piece
• Commercial integration technologies
• Collaborative Biome provides the bridge
• RDECs create, execute, and evolve their own CEs

Integration Time Infrastructure
Runtime Infrastructure
21
Summary Of Our Approach
Common Integration Characteristics
Advanced Core Technologies
Common Architecture

• Innovative
• Proliferating
• Stable
• Standard

• Legacy
• Heterogeneous
• Distributed
• Evolving

• Flexible
• Scalable
• Evolvable
• Practical

22
PAS Integration Architecture

• Web-based WAAS performance information
• Near Real Time Event-Based OO application
• Objects distributed over multiple platforms
• Specialized Simulation Integration Architecture

23
Saab VTB Integration Architecture

• Provides web access to distributed services
• Simulations, models, tools, utilities,
  databases...
• Assemble and execute simulation federation

Data Space

DataObject a
Simulation Proxies
DataObject b
Model Proxies
DataObject c
Tool Proxies
Database Proxies
SimClient
ORB/RMI/HLA
Analysis Space
Control Space
SimServer
html
ToolObjects
SimClient Applet
ORB/RMI/HLA
ModelObjects
ProxyServers
SimulationObjects
Currently modifying to exploit Jini/XML
24
Questions
25
SimServer Integration N-tier Implementation
Clients - Tier 1

• Tier 1 - Client
• SimClient -- GUI
• Simulation sandbox
• Client-side proxies supporting remote component
  setup, execution, and data disposition
• Non-GUI clients
• Federate ambassadors
• Tier 2 - Proxy Servers
• Finds all available Proxy objects based on
  filtering criteria
• Manages/coordinates all distributed component
  connections and interactions
• Tier 3 - Resource Servers
• CORBA-based wrappers providing access to local
  implementations and databases
• Supports remote access to local implementations
  and databases

Proxy Servers - Tier 2
ORB
SimServer
Resource Servers - Tier 3
ORB