RM1043.8-1-Defence Science and Technology Laboratory- Software tools for CB hazard prediction modelling

Description

About adding context and requirements test Which phase the project is in Discovery Existing team The supplier will have access to the in-house statistical, mathematical, software and wider expertise within the CBR division at Dstl. Further details will be shared during the implementation phase. Address where the work will be done DSTL Porton Down, Salisbury, Wiltshire, SP4 0JQ Working arrangements An agile approach is suggested for each requested task to be able to explore any uncertainty on either side with regards to the requirements. There should be a kick-off meeting to agree the approach and discuss the work plan. A sprint kick-off and completion meeting are required, with additional sprint progress reviews as agreed during the kick-off meeting. Code should be made available at the end of each Sprint to allow Dstl to review and provide feedback. Provide more information about your security requirements: Security Check (SC) Latest start date 2023-11-30 Enter the expected contract length: 2 years Write the term or acronym: UDM Write the term or acronym: SPT Write the term or acronym: STE2 Write the term or acronym: HPAC Write the term or acronym: CBFac Write the term or acronym: SLOPS Write the term or acronym: TOF Write the term or acronym: SoR Explain the term or acronym: Urban Dispersion Model Explain the term or acronym: Sensor Placement Tool Explain the term or acronym: Source Term Estimation Explain the term or acronym: Hazard Prediction and Assessment Capability Explain the term or acronym: CB Facility Explain the term or acronym: Spills of Liquid On Porous Surfaces. Explain the term or acronym: Tasking Form Explain the term or acronym: Statement of Requirement Are you prepared to show your budget details?: Yes Indicative maximum: 600000 Confirm if you require a contracted out service or supply of resource Contracted out service: the off-payroll rules do not apply Summary of work The CBR Division at Dstl develop and use models to predict and understand the hazards posed by deliberate (malicious) or accidental release of CB material. Software support is required to update and enhance existing tools, and to develop new tools to provide additional functionality. This overarching requirement comprises a number of smaller, discrete software tasks. Dstl has a number of specific requirements broadly covering: • Updating existing tools/systems to take advantage of the modernisation of software systems and IT infrastructure within Dstl; • Developing tools/scripts to enable the automation of data handling along modelling chains; • The extension of existing tools to add functionality. Where the supplied staff will work No specific location (for example they can work remotely) Why the work is being done The CBR Division at Dstl develop and use models to predict and understand the hazards posed by deliberate (malicious) or accidental release of CB material. Software support is required to update and enhance existing tools, and to develop new tools to provide additional functionality. This overarching requirement comprises a number of smaller, discrete software tasks. The business problem you need to solve Over the last 20 years, Dstl has developed a suite of computer models relating to predicting the airborne dispersion of, and hazards generated by, chemical and biological (CB) materials. This includes the Urban Dispersion Model (UDM), Sensor Placement Tool (SPT), Source Term Estimation (STE2), as well as frameworks to integrate models. Dstl has a number of specific requirements broadly covering: • Updating existing tools/systems to take advantage of the modernisation of software systems and IT infrastructure within Dstl; • Developing tools/scripts to enable the automation of data handling along modelling chains; • The extension of existing tools to add functionality. First user type: Dstl Enter more details about this user type: Need the software in order to conduct modelling simulation so that Dstl can carry out the required research and provide advice based off of the data Questions and Clarifications 0. 1) For initial application (11/09/2023) do we just fill in Attachment 3? 2) Is the 750 character count including spaces? 3) Will all software development work be completed at DSTL Porton Down, Salisbury, Wiltshire, SP4 0JQ? 4) Will we be given access to the systems, build environments and code before providing our proposal (29/09/2023)? 5) Will the system only be available in the client environment, or will the software be distributed (perhaps in Docker or VM?) 6) What languages are each of the systems written in? 7) Do we need to provide a fixed price quote for tasks 1-6? Or are these intended as examples? 8) Task 1 – build system a. What are the current build and test systems? b. what are the specific requirements to provide “Compatibility with Dstl version control (Dstl Armoury) and file storage systems (e.g. Dstl Technical Asset Register (TAR) folders)”. 9) Task 2 – Data Transforms a. Can we get examples outputs that need translating (from and to) b. Are these translation all manually kicked off? c. Can we have further detail on “harnessing existing HPAC tools such as the HHS (HPAC batch runner) and ScipuffToHPAC.” 10) Task 3 – HPAC Runner a. Is the HPAC runner currently able to run on JPMS java platform? 11) Task 5 – SLOPS a. Can we have example inputs for scenario input, meteorology and material data b. Can we have example outputs to pass to HPAC 12) Task 6 – Update to UDM Validation Toolkit a. What are the current issues in running the UDM Validation toolkit and Visualiser against the most recent development of UDM? 1) Please complete an excel or word doc listing the skills and evidence you have against the criteria, attachment 3 does not have an area to complete this 2) Yes, this does include spaces 3) Software development will be at suppliers premises. Acceptance will depend on successful build and test on Dstl systems. 4) Access to Dstl systems will not be provided for preparation of proposals. 5) Systems to be built on the client infrastucture. 6) Languages include C++, C, C#, Java, Fortran, python 7) Yes, please provide a Firm price quote for tasks 1-6 8) The current build, test, configuration system includes tools and procedures designed for legacy versions of Visual Studio and Subversion. The requirement must work with BitBucket, JIRA and networked storage. 9) Data transforms generally receive input data in text format (e.g. json or csv) and output in similar formats to provide linkage between models within a chain of models. Examples will not be provided before the contract commences. 10) Existing HPAC runner works on OSGI only. 11) Scenario input includes variables such as date ,time, location, spill volume, spill rate, spill material. Precise met data format is subject to change due to ongoing updates, but will consist of structured numeric data on a regular 3-dimensional grid, likely in human readable (text) format. The material data is static physical properties data. More details available here: https://www.icheme.org/media/16859/hazards-30-paper-05-batt.pdf 12) The UDM validation toolkit and visualiser interface with different versions of UDM via a Facade. The Facade needs to be updated to work with the latest versions of UDM and GEDIS. Last Updated: <strong>04 September 2023, 15:21</strong> 1. Software Tools SOR document, section 2 (2.1) for Quality Control and Assurance. Is it mandatory to hold the ISO9001 certificate or is it acceptable if we can demonstrate we meet or working towards the governance controls and/ or we work to the same or exceed the processes set out within the ISO certificate? ISO9001 is required. TickITPlus desirable Last Updated: <strong>04 September 2023, 15:23</strong> 2. Will the buyer sponsor the SC clearance process for supplier staff? Not any requirement for sponsoring of clearances in the proposal. Last Updated: <strong>04 September 2023, 15:24</strong> 3. Please can the authority confirm the location this work is required to be carried out? In bid pack 1, page 3, the “Location” is stated as “No specific location (for example they can work remotely)” whereas on page 4 the “Address where the work will take place” is noted to be “DSTL Porton Down, Salisbury, Wiltshire, SP4 0JQ”. Is remote delivery acceptable, with industry visits to Porton Down for meetings and final integration support? The Authority confirms that the work can take place remotely however some site visits may be required, this can be discussed with the project team during the implementation phase. Last Updated: <strong>04 September 2023, 15:24</strong> 4. Please can the authority confirm the contractual mechanism they would like to use for this task. I.E. an agile, Dstl task led, call off contract or firm priced bespoke development based on the tasks outlined in the EMR SOR? The Authority confirms that the contractual mechanism will be an agile, task led, call-off contract. Last Updated: <strong>04 September 2023, 15:25</strong> 5. Please can the authority confirm whether the 750 character count in bid pack 3 includes spaces? The Authority confirms that this does include spaces Last Updated: <strong>04 September 2023, 15:25</strong> 6. In the clarification answers you state that the total stage 2 bid should not exceed 5000 words. This seems overly restrictive given the requirement to provide a technical approach, solution and costing for 6 defined tasks and two optional tasks, in addition to the request for information relating to cultural and social fit. Could I request that the Authority consider doubling the word count limit to 10,000 words to enable sufficient technical detail to be provided against each task? The Authority confirms that the word count will be increased to 10,000 words in order to allow suppliers to provide sufficient detail Last Updated: <strong>12 September 2023, 09:31</strong>