A  A

LVCAR Enhancements for Using Gateways

The Live Virtual Constructive (LVC) Architecture Roadmap (LVCAR) report, sponsored by the Modeling and Simulation (M&S) Steering Committee, recommended several actions to promote the reuse of common M&S capabilities and to foster common formats and policy goals to promote LVC interoperability. One of these recommended actions pertained to the development of common gateway capabilities. The first phase of this effort reviewed the gateway needs of users and developers to develop strategies to support more effective LVC integration using gateways. The current LVCAR phase is focused on the implementation of the selected "Enhance" strategy, which emphasizes improvements to the native methodologies and practices LVC engineers follow to select and configure gateways for their specific applications. This paper describes the products intended to support using gateways.

The two products are the Gateway Mapping Language (GML) and Gateway Configuration Language (GCL). These products are intended to support the end user in getting more value out of the gateways they use as well as making it easier to switch gateway implementations. GML is a formal language for mapping the required translations between Simulation Data Exchange Models (SDEMs). This mapping is required for all multi-architecture events but there is currently no way to formally specify the required translations. In most events creating the required translations is done by trial and error with no resulting documentation. GML provides the format for this documentation and allows users and providers to agree on the required translations. GML also produces formal documentation that makes it easier to use the same translations with other gateways in the future. GCL is a formal language for specifying common gateway configuration parameters. In addition to common parameters, GCL includes support for many exercise management features such as data filtering. GCL allows a federation to document these key parameters in a gateway implementation independent format. This defined format supports reuse of the information in future events.