Vulnerability Lethality Server High Level Architecture Hla Interface Control Document
Download Vulnerability Lethality Server High Level Architecture Hla Interface Control Document PDF/ePub or read online books in Mobi eBooks. Click Download or Read Online button to get Vulnerability Lethality Server High Level Architecture Hla Interface Control Document book now. This website allows unlimited access to, at the time of writing, more than 1.5 million titles, including hundreds of thousands of titles in various foreign languages.
Vulnerability/Lethality Server High Level Architecture (HLA) Interface Control Document
The U.S. Army Research Laboratory (ARL) vulnerability/lethality table look-up server has gone through several iterations of development since first introduced in 1997 introduced in 1997 (then as the distributed interactive simulation DIS lethality communications server). These development iterations represented migration from its original transmission control protocol/internet protocol client/server communication form based in DIS, to combined DIS-high level architecture (HLA) form used during the 2001 Research, Development, and Engineering Center (RDEC) Federation "CalEx" (calibration experiments) and onto this current form that is all HLA and was designed for the RDEC command "1stApp" (First Application) experiment 2003 and presented in this report. This interface control document (ICD) describes the current state of exposed interface control components of the ARL vulnerability/lethality table look-up server (the server). The ICD describes the interface to an existing implementation of the server (with its look-up table capability). The interface described in this report includes an area that provides for further expansion, allowing delivery of damage descriptions from near real-time physics-based vulnerability modes (future dynamic calculation capability).
Lethality/Vulnerability Server Functional Description and Interface Control Document for MATREX V0.5
This report describes the lethality/ vulnerability server's interface control. That is it describes how other high level architecture (HLA) simulations can interact with the lethality/ vulnerability server. The use of war game simulations to conduct weapon systems analysis has an established history. With the advancement of computer and network capabilities, it became practical and efficient to segment simulated systems across various computer platforms. This advancement in distributed simulation also brought with it new dilemmas such as how to ensure a "fair fight". For example, when a set of heterogeneous simulations is brought together, each simulation may treat the data (vulnerability data, terrain, or other synthetic environment representations) with subtle differences that create an unfair advantage for some simulated weapons. Distributing applications also increases the risk of having incorrect or stale data configurations on one or more of the systems. The lethality/ vulnerability server is a tool that was designed to overcome some of these obstacles and help ensure a valid weapon system assessment. It allows diverse applications to draw from the same vulnerability description data set during a simulation run. The server can increase simulation preparation efficiency because configuring vulnerability damage is done once for all serviced applications. The lethality server currently delivers data descriptions in terms of standard fully damaged "mobility," "firepower," and "catastrophic" states. With relatively minor modifications, the server can be expanded to deliver partial (or degraded) damage and other types of data. This document is a functional description of the server with an emphasis on its HLA interface for the Modeling Architecture for Technology and Research EXperience (MATREX) VO.5 release, January 2004.
A Toolkit for Building RTI Independent HLA Interfaces for Simulations
"This document describes the design for a software framework that will make development of High Level Architecture (HLA) federates faster, and much easier for programmers new to HLA. The motivation for this comes out of our own experience here at Defence Research and Development Canada - Atlantic (DRDC Atlantic), and while supporting various units of the Canadian Armed Forces. The design concept is multi-layered, with two fundamental modules providing a foundation for federate development. The first is an abstraction layer that appears to developers as if it were an HLA evolved compliant run time infrastructure (RTI). While not an RTI this layer translates from HLA evolved to older versions of HLA, and hides vendor implementation quirks. The second module is a Federation Object Model (FOM) library design which is meant to form the basis for code generated automatically from extensible mark-up language (XML) FOM files. This design is the basis for the code being implemented by the open source HLAgile project on SourceForge"--Abstract, page i.