Scenario Design Tool

Dstl have a requirement for a tool which simplifies the process of designing scenarios and generating inputs to battle models. The overarching specification is for the supplier to create a Graphical User Interface (GUI) using Unreal Engine. The GUI would allow the user to generate and inspect battle scenarios, and simulate them using the battle models operated and supported by the Strategic Systems Group (SSG). The primary purpose of the Scenario Design Tool (SDT) is to simplify the process of interfacing with the battle models used at Defence Science and Technology Laboratory (Dstl). This is driven by the following needs which have been identified P-1. To increase the user community for battle models, stemming from an increasing requirement to conduct battle modelling studies and develop Suitably Qualified and Experienced Personnel (SQEP) for battle modelling. P-2. To reduce the time frames associated with developing battle modelling SQEP and familiarising new users with the battle modelling tools and capability at Dstl. P-3. To reduce the overheads involved with creating battle model scenarios, running battle models and viewing simulation results. P-4. To visualise and examine the battle scenario prior to using the battle model. P-5. To perform automatic checks on the validity of threat trajectories within the scenario prior to using the battle model. P-6. To ease the process of sharing output with expert and non-expert communities such as colleagues, customers and stakeholders. P-7. To create a single user interface which can format and pass scenario data to multiple battle models. A scenario is a representation of a battle containing any number of offensive and defensive platforms with specific configurations. As existing examples, in the Strategic Operational Analysis Tool (STOAT) scenarios are defined by a single Extensible Markup Language (XML) file, while in the Ballistic Missile Battle Model (BMBM) scenarios are defined using a collection of files. A platform is a vehicle or facility made up of collection of systems which forms part of a defensive or offensive architecture. A system is an element of a platform which performs a particular task or tasks. It is assumed that the following will be available to the SDT to facilitate its running and therefore not required as part of the SDT itself: A-1. A library, or libraries, of platform data sets. A-2. A trajectory model for generating threat trajectories included within the scenario. A-3. A battle model capable of simulating the scenario. A-4. External scripts to facilitate interfacing with necessary external models and data sets. A Software Requirements Specification has been written and will be supplied with the Invitation to Tender (ITT)

Additional information: This notice is to gauge market appetite only and does not constitute a formal request for expressions of interest. We request that any supplier who believes they may have the necessary capability, capacity and time to fulfil this requirement email [email protected]. This does not form part of the bidding process.