1. High Level Architecture for Simulation
Mr. Robert C. Turrell
HLA Program
Defense Modeling and
Simulation Office
French MOD
Cite’ de l’Air
Jan 01

2. Outline What is HLA and why did the DoD develop it?
HLA technical approach
Supporting Services
Sample HLA applications

3. What is HLA?
HLA is a flexible, reusable software architecture for creating component-based distributed simulations
Developed to allow reuse of Defense simulations in different applications
Conceived as general purpose architecture applicable beyond defense
Now in process of industry standardization and application

4. Modeling and Simulation in the DoD
Continuing squeeze on DoD resources
shrinking, dispersed force structure
competition for funds limits field exercises
need to carefully examine every investment
More demanding operational requirements
new, more complex missions
vastly expanding mission space
increased complexity of systems and plans
increasing demand for joint training
security challenges (e.g., information warfare)
Much more technical capability at less cost
communications
computers
software technology
displays/human-machine interfaces
data storage and management
Advanced
M&S can
offer a cost-effective
and affordable
solution

5. Recent DoD M&S History Technical progress spurs management response
Limited scope simulations, little interoperability prior to 1988
SIMNET
DSB: Computer Applications to Training and Wargaming Study for CJCS
High Level Architecture (HLA) begun
DARPA-SACEUR Distributed Wargaming System ACE-89
DIS Standards begun
ALSP: linking of Service wargames
New programs
(JSIMS, JWARS)
HLA policy
established
DoD Simulation Policy Study
DEPSECDEF Memo: EXCIMS formed and DMSO established
DoD Dir M&S Management
DoD P M&S Master Plan
DoD VV&A Instruction
DoD M&S Executive Agents
All Services’ M&S offices in place
SBA Task Force
Architecture Management Group
Management
HLA Transition
Plan approved
EXCIMS Functional Area Councils
No formal management structure
Management structure stand-up
Management
structure in place

6. US Defense-wide M&S Master Plan
Objective 1
Objective 2
Objective 3
Objective 4
Objective 5
Objective 6
Develop a common technical framework for M&S
Provide timely and authoritative representations of the natural environment
Provide authoritative representations of systems
Provide authoritative representations of human behavior
Establish a M&S infrastructure to meet developer and end-user needs
Share the benefits of M&S
Sub-objectives
Sub-objectives
Sub-objectives
5-1 Field systems
5-2 VV&A
5-3 Repositories
5-4 Communications
5-5 Coordination Center
Sub-objectives
Sub-objectives
1-1 High-level architecture
1-2 Conceptual models of the mission space
1-3 Data standardization
2-1 Terrain
2-2 Oceans
2-3 Atmosphere
2-4 Space
4-1 Individuals
4-2 Groups and organizations
6-1 Quantify impact
6-2 Education
6-3 Dual-use
DoD P, Modeling and Simulation Master Plan, October 1995

7. M&S Master Plan Objective 1-1
Establish a common high-level simulation architecture to facilitate the interoperability of all types of models and simulations among themselves and with C4I systems, as well as to facilitate the reuse of M&S components
Simulations developed for particular DoD Components or Functional Areas must conform to the High Level Architecture
Further definition and detailed implementation of specific simulation system architectures remain the responsibility of the developing Component

8. US Defense M&S Vision
Defense modeling and simulation will provide readily-available, operationally-valid environments for use by DoD components
to train jointly, develop doctrine and tactics, formulate operational plans, and assess war fighting situations
as well as to support technology assessment, system upgrade, prototype and full scale development, and force structuring.
Furthermore, common use of these environments will promote a closer interaction between the operations and acquisition communities in carrying out their respective responsibilities. To allow maximum utility and flexibility, these modeling and simulation environments will be constructed from affordable, reusable components interoperating through an open systems architecture.
DoD Executive Council on Modeling and Simulation (EXCIMS), March 13, 1992

9. Why HLA Now?
M&S Vision
“ ...common use of these environments will promote a closer interaction between the operations and acquisition communities in carrying out their respective responsibilities. To allow maximum utility and flexibility, these modeling and simulation environments will be constructed from affordable, reusable components interoperating through an open systems architecture.”
Embarking on development of new generation of simulations
Current technology does not provide tools necessary to achieve M&S Vision (i.e., ALSP and DIS)

10. Scope of HLA
Applicable to broad range of functional areas (e.g., training, contingency planning, analysis, and acquisition)
Applicable to simulations involving pure software representations, man-in-the-loop simulators, and interfaces to live components (e.g., instrumented-weapon systems and C3 systems)

11. Rationale for HLA Design
Basic premises:
No single, monolithic simulation can satisfy the needs of all users
All uses of simulations and useful ways of combining them cannot be anticipated in advance
Future technological capabilities and a variety of operating configurations must be accommodated
Consequence: Need composable approach to constructing simulation federations

12. US Defense HLA Policy DoD Policy:
“Under the authority of [DoD Directive ], and as prescribed by [the DoD Modeling and Simulation Master Plan], I designate the High Level Architecture as the standard technical architecture for all DoD simulations.”
HLA supersedes Distributed Interactive Simulation (DIS) and ALSP
“No Can” Dates
“No Can Pay” - first day of FY99
no funds for developing/modifying non-HLA-compliant simulations
“No Can Play” - first day of FY01
retirement of non-HLA-compliant simulations
Waivers must be decided on a corporate basis
Dr. Paul Kaminski, USD(A&T) September 1996

13. DoD HLA Policy Reaffirmation
DoD Transition Policy
“ We must foster broad simulation interoperability and reuse if the Department is to cost-effectively harness the potential of simulation to improve DoD operations.”
“ All new simulations will be built in accordance with the HLA. To reap the full benefits of simulation interoperability and reuse in the near-term, it is also important to quickly transition our legacy simulations to the HLA, … I encourage our industry partners to follow suit”
Dr. J.S. Gansler, USD(A&T) 7 April 1998

14. J. S. Gansler, USD (A&T) 03 November 2000
Continued Use - HLA MoA
“… This agreement attests to the fact that the HLA has gained the Department’s simulation stakeholders’ acceptance and strong support through tried and proven technical performance, capability, maturity and potential. Furthermore, the wide spread adoption of HLA is contributing not only to the military capability and readiness of US forces but also to a growing number of allied and friendly nations as well, laying a firm foundation for international interoperability…”
J. S. Gansler, USD (A&T) November 2000
Within the MOA:
“…Establishes the HLA as the technical architecture for interoperability and reuse among the signatories…”
“… any other alternative must be justified…”
“…DoD components shall establish their own policies and procedures for transitioning their simulations to HLA or excluding them based on requirements, resources, Component priorities, or security. All exclusions from HLA shall be documented, justified by the DoD Component…”

15. HLA Development DoD-wide Architecture Management Group (AMG) Mar 95
DoD Policy
Issued
10 Sept 1996
Checkpoints
IEEE P1516
Drafts
Approved for
Balloting
3/99
Spec
v1.1
2/97
Spec
v1.2
8/97
Spec
v1.3
2/98
IEEE Vote
for Approval
9/00
Industry Solicitation
Mar 95
Aug 96
Previous DoD architecture efforts
Evolution
Prototypes
MOA work
begun
We’re Here!
DoD Policy
Reaffirmed
7 April 1998
Initial
definition
of HLA
Baseline
definition
of HLA
IEEE Standardization
Process begun 6/97
DoD-wide Architecture Management Group (AMG)
16 members members members
Phase 1
Initial
Definition
Phase 2
Baseline
Development
Phase 3
Technical
Transition
Phase 4
Implementation

16. Outline What is HLA and why did the DoD develop it?
HLA technical approach
Supporting Services
Sample HLA applications

17. Prototyping During HLA Baseline Development
Over 25 different simulations
One Runtime Infrastructure (RTI) implementation
Training, analysis, and acquisition applications
Unit, platform, and weapon system component level granularity
Hardware-in-the-loop, human-in-the-loop, and closed-form simulations (live, virtual, and constructive)
Both real-time and fast-as-possible discrete event simulations
Both classified and unclassified federations
Local and wide area networks Run on Sun, Silicon Graphics, HP, and IBM workstations

18. Some Terminology
Federation: a set of simulations, a common federation object model, and supporting RTI, that are used together to form a larger model or simulation
Federate: a member of a federation; one simulation
Could represent one platform, like a cockpit simulator
Could represent an aggregate, like an entire national simulation of air traffic flow
Federation Execution: a session of a federation executing together

19. Some More Terminology
Object: An entity in the domain being simulated by a federation that
Is of interest to more than one federate
Is handled by the Runtime Infrastructure
Interaction: a non-persistent, time-tagged event generated by one federate and received by others (through RTI)
Attribute: A named datum (defined in Federation Object Model) associated with each instance of a class of objects
Parameter: A named datum (defined in Federation Object Model) associated with each instance of a class of interactions

20. The High Level Architecture (HLA)
Architecture calls for a federation of simulations
Architecture specifies
Ten Rules which define relationships among federation components
An Object Model Template which specifies the form in which simulation elements are described
An Interface Specification which describes the way simulations interact during operation
Live
Participants
Interfaces to Live Players
Support Utilities
Simulations
C++
Ada 95
CORBA IDL
Java
Interface
Runtime Infrastructure (RTI)
Federation Management Declaration Management
Object Management Ownership Management
Time Management Data Distribution Management
The HLA is not the RTI; the HLA says there will be an RTI that meets
HLA requirements but it doesn’t specify a particular software implementation

21. Federation Rules
1 Federations shall have an HLA Federation Object Model (FOM), documented in accordance with the HLA Object Model Template (OMT).
2 In a federation, all representation of objects in the FOM shall be in the federates, not in the runtime infrastructure (RTI).
3 During a federation execution, all exchange of FOM data among federates shall occur via the RTI.
4 During a federation execution, federates shall interact with the runtime infrastructure (RTI) in accordance with the HLA interface specification.
5 During a federation execution, an attribute of an instance of an object shall be owned by only one federate at any given time.

22. Federate Rules
6 Federates shall have an HLA Simulation Object Model (SOM), documented in accordance with the HLA Object Model Template (OMT).
7 Federates shall be able to update and/or reflect any attributes of objects in their SOM and send and/or receive SOM object interactions externally, as specified in their SOM.
8 Federates shall be able to transfer and/or accept ownership of attributes dynamically during a federation execution, as specified in their SOM.
9 Federates shall be able to vary the conditions (e.g., thresholds) under which they provide updates of attributes of objects, as specified in their SOM.
10 Federates shall be able to manage local time in a way which will allow them to coordinate data exchange with other members of a federation.

23. HLA Object Models and OMT
Object Model Template (OMT)
Provides a common framework for HLA object model documentation
Fosters interoperability and reuse of simulations via the specification of a common representational framework
Federation Object Model (FOM)
A description of all shared information (objects, attributes, and interactions) essential to a particular federation
Simulation Object Model (SOM)
Describes objects, attributes and interactions in a particular simulation which can be used externally in a federation

24. Object Model Template (1.3)
Routing Space Table
Parameter Table
Attribute Table
Interaction Class Structure Table
Object Class Structure Table
Object Model Identification Table

25. Object Model Template (1516)

26. Object Model Template (1516) (cont’d)

27. Interface Specification
Provides a specification of the functional interfaces between federates and the RTI
Interfaces are divided into six service groups
Each service specification includes:
Name and Descriptive Text
Supplied Arguments
Returned Arguments
Pre-conditions
Post-conditions
Exceptions
Related Services
Application Programmer Interfaces (APIs)
CORBA IDL, C++, Ada ’95 and Java

28. What does the Interface Specification include?
Six HLA RTI Service Groups
Federation Management (20 services)
Declaration Management (12 services)
Object Management (17 services)
Ownership Management (16 services)
Time Management (23 services)
Data Distribution Management (13 services)
The Interface Specification also includes:
Support Services (29 services)
Management Object Model
Federation Execution Data (FED)
Application Programmers Interfaces (APIs)
Harel state charts

29. HLA RTI Services Categories
Category
Functionality
Create and delete federation executions
Federation Management
Join and resign federation executions
Control checkpoint, synchronization
Establish intent to publish and subscribe
Declaration Management
to object attributes and interactions
Create and delete object instances
Control attribute and interaction
Object Management
publication
Create and delete object reflections
Ownership Management
Transfer ownership of object attributes
Coordinate the advance of logical time
Time Management
and its relationship to real time
Data Distribution Mgmt
Supports efficient routing of data

30. Outline What is HLA and why did the DoD develop it?
HLA technical approach
Supporting Services
Sample HLA applications

31. HLA Evolution: Architecture Management Group (AMG)
AMG continues with responsibility for technical application and HLA evolution
New AMG members have been added as new programs begin HLA implementation
HLA members are technical implementers
A disciplined issue identification/resolution process, a Technical Support Team, and experimentation are in place to ensure measured, professional evolution
Six month “checkpoints”
HLA specification version 1.3 released in Feb 98
Continues as operative HLA specification

32. Applying HLA: Federation Development and Execution Process
Execute
Federation
and
Prepare
Results 6
Develop
Conceptual
Model 2
Design 3 4
Define
Objectives 1
Available
Resources
Program
Statement
Requirements
Scenario
Initial Planning
Documents
Allocated
Federates
Development
Plan
FOM
FED file
Modified
Instance
RTI RID File
Tested
Testing
Data
Test
Evaluation
Criteria
Reusable
Products
User
Feedback
Integrate 5

33. HLA Education/Outreach
Integrated DMSO HLA training/outreach program is underway
no cost to recipients other than travel expenses
Regional -- Comprehensive introduction to HLA offered monthly
Focused Training -- Half day focused sessions as adjuncts to Regionals or standalone offerings
HLA Compliance Testing
Adapting Your Simulation to HLA
Federation Development and Execution
Configuring your Federation for Performance
Hands-on Practicum -- twice a month offerings for implementer-level training in use of HLA
CD education materials to supplement HLA live training
HLA Video

34. HLA User Services: Regional HLA User Groups
Regional HLA User Groups are forming across the country.
Made up of Government, Industry, and Academia
DMSO Fosters User Groups by:
Providing expert speakers
Offering focused training sessions
Maintaining information sharing links
Provide forums for:
Sharing experiences & lessons learned
Influencing evolving community-wide standards & practices
Discussing technical management and user requirements
Starter Kit available for those wishing to form new groups
San Diego
Colorado Springs
Tennessee Valley
(Northern Alabama &
Southern Tennessee)
FL High Tech Corridor
Washington, DC
Boston
Dayton
Eglin AFB
Pax River
User Group Information:

35. HLA Academic Outreach Goals
Educate undergraduate and graduate students about HLA
Create job opportunities for students
Create talent pool for HLA community
Inform academic researchers about HLA research opportunities
Open new research areas for researchers
Tap into pool of experienced simulation researchers to generate “next generation” solutions
Partner with an academic organization established in simulation
Society for Computer Simulation McLoed Institute

36. Approach Develop initial course materials
Fundamentals and advanced topics
Provide access to tools and tools information
Freeware tools and discounted commercial tools
Initiate university contact network
Growing number of current universities doing work in HLA
Establish an open online information repository (

37. McLeod Institute Home Page
Downloadable curriculum materials
Lecture notes
Labwork with software
Searchable bibliography
Access to tools

38. HLA Supporting Software Philosophy
HLA is an architecture, not software
however, to facilitate implementation of HLA, DMSO is developing an initial suite of HLA supporting software
DMSO facilitates open distribution of supporting tools in the public domain
Open access to specifications (e.g., Object Model Template data interchange format) to foster development of commercial software to support HLA
Information source: HLA Online (subscribe at
Open mailing list for updates on HLA and information on HLA supporting software (over 1,000 subscribed)

39. Supporting Software Current free software 1516 Upgrades in progress
RTI-NG 1.3v3
Obj Model Development Tool
Fed Exec Planners Workbook
RID Editor
Federation Verification Tool
Federation Mgt Tool
Data Collection Tool
1516 Upgrades in progress
OML
Runtime Infrastructure
Moon Rovers
STEALTH
FVT
DCT
FMT
RID Editor
OMDD
OMDT
FEPW

40. HLA Supporting Software: Runtime Infrastructure (RTI) Software
RTI software is available now and can be ordered from DMSO homepage ( under topic “HLA Software Distribution Center”
User accounts approved by DMSO
user account approved following one-time submission of registration data
Reverse DNS lookup required
registered users may access and download any products not previously downloaded
Currently ten ports for RTI are available
each port includes RTI software; Installation guide; User documentation; Test federate; Sample applications
once registered you will be automatically notified of new releases
RTI software is freely distributed

41. Supported Platforms for DMSO RTI
21 *
Solaris 7 / SPRO 5.1 (FORTE)
(underway)
Solaris 8 / SPRO 5.1 (FORTE)
(replaces previous)
IRIX n32 MIPS3 / MIPS Pro C
(completed)
IRIX n64 MIPS4 / MIPS Pro C 9
VxWorks / Green Hills C
126
Windows 2000 / MSVC++ 6.0 91
Windows 98 / MSVC++ 6.0
(waiting for HW)
Digital UNIX
(evaluating)
HP-UX
(interim release)
IBM AIX
73 (replace in next release)
IRIX n32 MIPS3 / MIPS Pro C 71
IRIX n32 MIPS4 / MIPS Pro C
102
Red Hat Linux 6.1 / EGCS 1.1.2
39 (potential for retire)
Solaris 2.6 / SPRO 4.2
22 *
Solaris 7 / SPRO 5.0 18
Solaris 7 / GCC
201
Windows NT / MSVC++ 6.0
RTI-NG 1.3 v3.2 Downloads
Platform

42. RTI 1.3NG Download Statistics

43. RTI NG Port Requests AIX port SGI IRIX 6.5 / n64 RedHat Linux 7.0
Delivered first version v3.1, upgrading to v3.2 now
HLA re-engineering effort has been cancelled
SGI IRIX 6.5 / n64
Changes for 64 bit operations are completed
RedHat Linux 7.0
Will not release for this platform due to problems encountered, will wait for 7.1
Solaris 8 / Sun Forte 6.0
Just added port, will release with v4, port overcome by other events

44. RTI Performance Benchmarks
Standard benchmark metrics and supporting software to support measurement of performance of HLA federations
Helps users compare implementations of RTI
Helps users design federations
Current suite includes 5 benchmarks
DDM - Throughput
Latency - Time Advance
Ownership
Suite is being augmented to
Address more federation designer needs
Cover more of the I/F Spec
Updated to the anticipated IEEE 1516 standard
Benchmark software is available from DMSO Software Distribution Center

45. Cooperation with Commercial Developers
DMSO developments are intended to help create a market for commercial tools (not compete with commercial developments)
Commercial developments are beginning both in the US and overseas
Workshops for commercial tool developers and cooperative ventures initiated
Commercial involvement in beta testing
Bulletin board for commercial tools hosted on the HLA home page

46. Compliance Testing
High Level Architecture
Certificate of Compliance
This is to certify that
<Fed Name> Version <Fed Version>
(Federate Name) (Federate Version )
successfully completed HLA conformance on
<IF Test Date> ,
and is certified to be HLA-compliant in accordance
with the HLA Specification v. 1.3.
Kenneth C. Konwin
Colonel, USAF
Director, Defense Modeling
and Simulation Office
HLA Specification v. 1.3
Support
Utilities
HLA Test
Logger
Runtime Infrastructure
<Fed Name>
On-line federate compliance testing system on-line in 98
Over 161 federates are now tested
Includes commercial and international, as well as DoD
Compliance costs average less than six staff months of effort
New Test Suite to be provided to NATO MSCO in Spring of 01

47. HLA Federate Costs for Compliance
“How much will it cost to transition to HLA?”
Numerous mitigating factors
After Action Review with the development team to identify
HLA migration strategy used
Technical approach to develop RTI Interface
HLA and non-HLA related tasks performed
Average cost to adapt a federate to use HLA is less than 6 staff months

48. RTI Verifier
RTI testing will be conducted to verify that RTI implementations comply with the HLA Specification
Level One Testing
Small, publicly available set of tests
An RTI developer must pass Level One testing before they submit their software for Level Two testing
Level Two Testing
Ensure all RTIs used by the DoD behave the same with respect to the I/F Specification

49. HLA Standardization Beyond DoD
Object Management Group
Adopted HLA Runtime Services as Distributed Simulation Facility in November 1998
NATO
Adopted HLA in NATO M&S Master Plan in December 1998
IEEE
Standardization process began in May 1998
HLA IEEE 1516 now in balloting

50. Outline What is HLA and why did the DoD develop it?
HLA technical approach
Supporting Services
Sample HLA applications

51. Support Military Exercises
HLA is designed to support interfaces between simulations and live systems
Military staff operate their real world command and control systems
Interact with ‘synthetic’ subordinate units who fight the war in simulation
Operational systems and simulations representing warfighters are all federates in an HLA federation

52. System Acquisition -- Test and Evaluation
Link test hardware and live systems with simulation
Early testing of ‘conceptual systems’ or ‘virtual prototypes’
DoD ‘JADS’ program links F-16 in anecodic chamber in Maryland with enemy air defense systems in Houston and test control in New Mexico
European Union project ‘EDISON’ linked space station hardware facilities
SADS VI
SADS III
FEBA
IADS TARGET
ASSIGNMENTS
SADS VIII
WEST X
JADS EW environment to be replicated

53. Top Level View of VPG Blueprint
Micro Met Data
Chem. / Bio. Agent Densities
Macro Met Data
Cultural Objects
Smoke / Obscurants
Radiance Map
Electromagnetic Properties
Ground-Cover Materials
Terrain Elevation
Map / Visible Spectrum
Top Level View of VPG Blueprint
Within and Across Test Centers
VPG Tools
Distributed Test Control
Test Planning
Visualization
etc.
Architecture
Integrated Information
Systems
Stimulators
Tactical & Simulated
Ranges
Unit
Under
Test (UUT)
Synthetic Test Environments
Placed in Motion With Common Computing and Communications Backbone

54. TENA Services TENA Middleware
“Mission Space” Objects
“Provider Space” Objects
Range Resource Application Software
RangeWare type of concept
This is where work on other network object protocols such as DCOM or CORBA would take place.
Work in these other areas, however, requires us to re-visit the issue of testing the TENA Connection and Message services.
TENA Object Services
TENA Distribution Services
HLA Interface
IP Interface
CORBA Interface
DCOM Interface
TENA Middleware
TENA Middleware
Standard API to manipulate Range Data
HLA RTI
HLA RTI
Protocols
DCOM
CORBA

55. Distributed Mission Training
Link high performance flight simulators with simulations
Train and do mission rehearsal with distributed forces
Capitalize on simulation hardware collocated with distributed peace and wartime forces

56. DiMuNDS 2000
Purpose: Build skills within NATO countries in the development of HLA federates and federations
Technical skills with Run-Time Infrastructure software and services
Procedural skills in applying the HLA Federation Development and Execution Process (FEDEP)
Independently funded by participating nations (FR, GE, NL, UK, & US)
Cooperatively developed by federating national simulations & tools from participating nations
Demonstrations: Jul - Sep 2000
DiMuNDS = Distributed Multi-National Defense System

57. Experimentation/Analysis
Assessment of future doctrine and systems requires new combinations of emeny and friendly systems and force structures
HLA is support US Atlantic command in experimentation for new systems in the year 2010
NTM
RC135 Rivet Joint
DSP/SBIRS
Global Hawk
UAV
DD963
TLAM
F16HTS
HARM
SA2
Scud
SA6
SA10
E3 AWACS
CTOC
F15E
JAOC
E8 JSTARS
FLOT
JSOW
ATACMS
Clutter

58. Loop, Virtual Interaction
JSAF Federation
Entity Based Simulation
Explicit Modeling
Physics Based Interactions
Probability Distributions
Environment
Modified SWA
New Roads, Cities, Forests
Multi-Resolution Terrain DB
Day/Night
2007 Modeling
Model & Integrate J9-defined, 2007 systems in a Joint Battlespace
Sensors
Sensor Feedback
Multi-service Platforms
Munitions
Clutter & Background Traffic
Decision Support Tools
Forces
Red - TBM Battalions and
protective measures
Blue - fighters, bombers, ship launched munitions, ATACMS, cruise missiles, satellites, airborne sensors, SOF, UGS
Red/Blue, Human In The
Loop, Virtual Interaction
Technical
Support
Virtual/Constructive/HLA/DIS Multiple Resolution Entities White Cell
PC Network (LAN/WAN) Centralized Control After Action Tools
Secret (Fastlane) Network RTI Logger 2D/3D Visualization

59. Distributed Learning Environments
HLA is providing an environment for distributed virtual environments for education
Franklin Institute’s CIMBLE program is experimenting with HLA as an alternative to traditional VRML server approach

60. Distributed Virtual Environments
HLA is being applied as the infrastructure for supporting distributed virtual environments in both DoD and civil applications
Distributed Virtual Command Post links various media in 3D immersive environment for the DoD and commercial uses
Lionhearth and SRI International

61. Distributed Gaming Applications
HLA is being also being applied to support distributed interactive gaming in both peer to peer and server configurations
Mak’s new release of ‘Spearhead’
Cybernet’s Open Skies
Perceptronics ‘Intergame’ environment provides HLA based platform game development
Open Skies
Cybernet
Mak
Spearhead

62. For More Information on HLA