1000166778-Extensible Software Framework to Support CBR Modelling

Tender description

Summary of the work Development of a framework to link software models and tools and integration of existing CBR models and tools. Expected Contract Length 1 year contract with a further 1 year optional extension Latest start date Friday 1 October 2021 Budget Range Year 1 £100k, Optional Year 2 £200k Why the Work is Being Done The Chemical, Biological and Radiological (CBR) division within Dstl have, over the last 20 years, developed, or gained access to a set of CBR models and tools. It is often necessary to link multiple, diverse models and tools together to perform analysis. This is not always practical or desirable to do manually. Building on a previous requirements capture, a new system needs to be implemented that enables the linking of the required models and tools. Problem to Be Solved The mathematical modelers need to be able to link together software models and tools. Who Are the Users The users are the mathematical modelers and supporting staff at Dstl. The users need a system to be able to link together software models and tools to meet requirements described in a previously produced initial requirements document. Work Already Done Through a previous contract, a set of requirements have been produced that describe the key user and system requirements. Existing Team The supplier will have access to the in-house statistical, mathematical, software and wider expertise within the CBR division at Dstl. Current Phase Discovery Skills & Experience • Experience of development of software systems combining multiple different components • Experience of developing extensible and modular software systems • Experience of producing high quality and robust Application Programmers Interfaces (APIs) • Experience of producing high quality and robust testing for software systems • Experience of producing high quality user experiences for software • Experience of producing high quality, succinct software documentation • Experience of communicating technical software information to non-software technical staff • Experience of working in complex scientific domains • Experience in working with software and tools written in C++ and Java • Experience of using code control systems appropriately • Experience of working using Agile methodologies Nice to Haves • Knowledge of Chemical, Biological and Radiological (CBR) systems • Experience of working with software and tools written in Fortran, Python, R, Matlab, Mathematica • Experience of working with systems that use OSGi Work Location Development anywhere in UK. Final delivery / acceptance meeting either at Porton Down, or via video conferencing. Working Arrangments An agile approach is suggested for this 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. Dstl will consider the adaptation of existing software if the contractor wishes to bid using this approach. Security Clearance N/A No. of Suppliers to Evaluate 5 Proposal Criteria • Suitability of the provided outline work-plan, identifying relevant tasks, staffing, and technical and management approaches. • Evidence that the proposed staff have the requisite expertise and work experience to undertake their identified tasks. • How well risks and dependencies have been identified and whether offered approaches to manage them are appropriate. • The suitability of proposed deliverables and clarity of their definition; including evaluation of their compliance with specified requirements. Deliverables must include: an implemented framework that delivers the must priority requirements. Cultural Fit Criteria • Work as a team with our organisation and other suppliers • Be transparent and collaborative when making decisions • Have a fail-fast and no-blame culture that encourages people to learn from their mistakes. • Used to providing "government-source" software, with sufficient documentation such that others can enhance/maintain it. Payment Approach Fixed price Evaluation Weighting Technical competence 60% Cultural fit 10% Price 30% Questions from Suppliers 1. With reference to the timeframes and fees (£100k yr1), is the customer looking for resource for the full year? Alternatively, if a supplier can deliver the requirement in a shorter timeframe with a team is this acceptable? ‘Yes, although the technical team will need to be satisfied that the proposed shorter timeframe will be suitable for the project.’ 2. Dear Project Team, Some of the points ask about experience in multiple areas, particularly the ones on ‘Experience of working in complex scientific domains’ and ‘Experience of working with software and tools written in Fortran, Python, R, Matlab, Mathematica’. Are we permitted to provide more than one example to cover these? Yes, multiple examples is acceptable