Scenario Definition Language for Modeling & Simulation (M&S) Navy SBIR FY2006.1 Sol No.: Navy SBIR FY2006.1 Topic No.: N06-018 Topic Title: Scenario Definition Language for Modeling & Simulation (M&S) Proposal No.: N061-018-0405 Firm: Gestalt, LLC 680 American Ave Suite 302 King of Prussia, Pennsylvania 19406-1310 Contact: Larry Esmonde Phone: (610) 994-2821 Web Site: www.gestalt-llc.com Abstract: The objective of this proposal is to begin the development of an extensible standard scenario definition language that could be used by Modeling and Simulation applications to exchange scenario data at the command and control (C2) level and below. Initializing multiple simulations via individually built scenario files is inefficient and inaccurate. Focusing on an extensible language, suitable for multiple services and branches is key to overcoming these inefficiencies. Additionally, simulations operate at various levels of fidelity and autonomy. Fidelity levels impact the definition language's scope in terms of level of detail and quantity of the data. The resultant vocabulary would need to be able to handle varying levels of fidelity, and be well documented so that it can be extended and useful. The focus of PHASE 1 will be to categorize the scenario definition language (SDL), investigate the feasibility of incorporating an ontology in order to provide semantics within the SDL and demonstrate it using existing scenarios and translating it to a Unit Order of Battle focused description. Benefits: The benefits of a common scenario definition language (CSDL) are threefold. First, a common scenario definition allows for more efficient data exchange during initialization and runtime of training and analysis exercises in which modeling and simulation applications are currently used. While several data exchange standards do exist, manual reproduction and translation of scenario data is still required in today's training and analysis exercises. A CSDL would make the scenario initialization and exchange more efficient across domains and services. Second, with a CSDL, an automated mechanism for data exchange could replace the potentially error-prone manual processes that are used now. Third, a CSDL would reduce the number of tools required for scenario generation and provide a competitive marketplace for producing new tools for data import, export, translation, modification, filtering, validation and for other functions in the scenario generation process. Return