Notice Information
Notice Title
Scenario Design Tool
Notice Description
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 hlander@dstl.gov.uk. This does not form part of the bidding process.
Notice Details
Publication & Lifecycle
- Open Contracting ID
- ocds-b5fd17-66e5a1cb-6888-4cb4-881c-750013832baa
- Publication Source
- Contracts Finder
- Latest Notice
- https://www.contractsfinder.service.gov.uk/Notice/44ff9108-cc06-430c-8f8e-060e7b673f83
- Current Stage
- Planning
- All Stages
- Planning
Procurement Classification
- Notice Type
- Market Engagement Notice
- Procurement Type
- Standard
- Procurement Category
- Not specified
- Procurement Method
- Not Specified
- Procurement Method Details
- Not specified
- Tender Suitability
- SME
- Awardee Scale
- Not specified
Common Procurement Vocabulary (CPV)
- CPV Divisions
72 - IT services: consulting, software development, Internet and support
-
- CPV Codes
72232000 - Development of transaction processing and custom software
72262000 - Software development services
Notice Value(s)
- Tender Value
- Not specified
- Lots Value
- Not specified
- Awards Value
- Not specified
- Contracts Value
- Not specified
Notice Dates
- Publication Date
- 2 Sep 20241 years ago
- Submission Deadline
- Not specified
- Future Notice Date
- 6 Sep 2024Expired
- Award Date
- Not specified
- Contract Period
- Not specified - Not specified
- Recurrence
- Not specified
Notice Status
- Tender Status
- Planning
- Lots Status
- Not Specified
- Awards Status
- Not Specified
- Contracts Status
- Not Specified
Buyer & Supplier
Contracting Authority (Buyer)
- Main Buyer
- MINISTRY OF DEFENCE
- Contact Name
- Available with D3 Tenders Premium →
- Contact Email
- Available with D3 Tenders Premium →
- Contact Phone
- Available with D3 Tenders Premium →
Buyer Location
- Locality
- FAREHAM
- Postcode
- PO17 6AD
- Post Town
- Portsmouth
- Country
- England
-
- Major Region (ITL 1)
- TLJ South East (England)
- Basic Region (ITL 2)
- TLJ3 Hampshire and Isle of Wight
- Small Region (ITL 3)
- TLJ36 Central Hampshire
- Delivery Location
- TLJ South East (England)
-
- Local Authority
- Winchester
- Electoral Ward
- Southwick and Wickham
- Westminster Constituency
- Fareham and Waterlooville
Further Information
Notice Documents
-
https://www.contractsfinder.service.gov.uk/Notice/44ff9108-cc06-430c-8f8e-060e7b673f83
2nd September 2024 - Early engagement notice on Contracts Finder -
https://www.contractsfinder.service.gov.uk/Notice/8328b0af-59ab-4c0f-809b-476cd3d05ffb
22nd August 2024 - Early engagement notice on Contracts Finder -
https://contracts.mod.uk/esop/guest/go/opportunity/detail?opportunityId=58640
Defence Sourcing Portal Opportunity
Open Contracting Data Standard (OCDS)
View full OCDS Record for this contracting process
The Open Contracting Data Standard (OCDS) is a framework designed to increase transparency and access to public procurement data in the public sector. It is widely used by governments and organisations worldwide to report on procurement processes and contracts.
{
"tag": [
"compiled"
],
"id": "ocds-b5fd17-66e5a1cb-6888-4cb4-881c-750013832baa-2024-09-02T08:44:08+01:00",
"date": "2024-09-02T08:44:08+01:00",
"ocid": "ocds-b5fd17-66e5a1cb-6888-4cb4-881c-750013832baa",
"language": "en",
"initiationType": "tender",
"title": "Scenario Design Tool",
"planning": {
"milestones": [
{
"id": "1",
"title": "Engagement end date",
"type": "engagement",
"dueDate": "2024-09-06T23:59:59+01:00"
}
],
"documents": [
{
"id": "1",
"documentType": "marketEngagementNotice",
"description": "Early engagement notice on Contracts Finder",
"url": "https://www.contractsfinder.service.gov.uk/Notice/8328b0af-59ab-4c0f-809b-476cd3d05ffb",
"datePublished": "2024-08-22T15:04:29+01:00",
"format": "text/html",
"language": "en"
},
{
"id": "2",
"description": "Defence Sourcing Portal Opportunity",
"url": "https://contracts.mod.uk/esop/guest/go/opportunity/detail?opportunityId=58640"
},
{
"id": "3",
"documentType": "marketEngagementNotice",
"description": "Early engagement notice on Contracts Finder",
"url": "https://www.contractsfinder.service.gov.uk/Notice/44ff9108-cc06-430c-8f8e-060e7b673f83",
"datePublished": "2024-08-22T15:04:29+01:00",
"dateModified": "2024-09-02T08:44:08+01:00",
"format": "text/html",
"language": "en"
}
]
},
"tender": {
"id": "tender_461461/1397843",
"title": "Scenario Design Tool",
"description": "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 hlander@dstl.gov.uk. This does not form part of the bidding process.",
"status": "planning",
"classification": {
"scheme": "CPV",
"id": "72232000",
"description": "Development of transaction processing and custom software"
},
"additionalClassifications": [
{
"scheme": "CPV",
"id": "72262000",
"description": "Software development services"
}
],
"items": [
{
"id": "1",
"deliveryAddresses": [
{
"region": "South East",
"countryName": "United Kingdom"
},
{
"region": "South East",
"countryName": "United Kingdom"
}
]
}
],
"suitability": {
"sme": true,
"vcse": false
}
},
"parties": [
{
"id": "GB-CFS-186759",
"name": "Ministry of Defence",
"identifier": {
"legalName": "Ministry of Defence"
},
"address": {
"streetAddress": "Dstl Portsdown West",
"locality": "Fareham",
"postalCode": "PO17 6AD",
"countryName": "England"
},
"contactPoint": {
"email": "hlander@dstl.gov.uk"
},
"roles": [
"buyer"
]
}
],
"buyer": {
"id": "GB-CFS-186759",
"name": "Ministry of Defence"
}
}