Awarded to Softwire Technology Limited

Start date: Monday 19 March 2018
Value: £150,000
Company size: SME
Department of Health and Social Care

Fleming Fund Website/Digital Platform

16 Incomplete applications

11 SME, 5 large

10 Completed applications

9 SME, 1 large

Important dates

Thursday 25 January 2018
Deadline for asking questions
Thursday 1 February 2018 at 11:59pm GMT
Closing date for applications
Thursday 8 February 2018 at 11:59pm GMT


Summary of the work
Team to work with the current supplier for hand over of website. Work closely with product manager, internal service manager and DHSC Digital Team to deliver Fleming Fund Website from Beta to live.
This includes Improving user satisfaction towards the application, based on user needs identified in user research.
Latest start date
Monday 19 March 2018
Expected contract length
2 years with the option to extend by a further 2 years
Organisation the work is for
Department of Health and Social Care
Budget range

About the work

Why the work is being done
In 2016 the UK government announced the development of the Fleming Fund – a £265 million project to improve laboratory capacity for diagnosis as well as surveillance of antimicrobial resistance (AMR) in low and middle income countries. This budget is taken from Official Development Assistance (ODA), and will support those countries that will be most acutely impacted by the spread of AMR. Project was assigned to the Department of Health who are working collaboratively with relevant United Nations agencies and other development Partners. Currently we are working towards an MVP website to be launched at the end of January 2018.
Problem to be solved
DHSC needs a website to act as a communication vehicle for the dissemination of information on the project and all of its components to a specialist audience;

To also demonstrate transparency of project objectives.

Currently discovery, alpha and beta journeys have demonstrated the user experience is suboptimal and also not meeting government digital standards
Who the users are and what they need to do
Potential grantees in Low and Middle Income Countries (LMICs)- eligibility to apply for a grant
Potential Fellows- see above user needs.
Regional Co-ordinators-to direct Government officials to a site with an over view of the Fleming Fund/to be able to visually see progress across the Regions
Delivery Partners- See News & updates of the FF/understand how their organisation fits into the/See progress on UK tackle AMR/To showcase their good news.
One Health Community- Understand aims and objectives of the Fleming Fund/News and updates on AMR/access to resources/understand what the UK is doing to tackle AMR/Align their own research and activity
Early market engagement
Any work that’s already been done
Discovery and Alpha. Beta phase in progress up to MVP for the website launch produced a series of user stories and a prioritised list of user journeys.
Guerrilla user research and usability user testing. Identified expectations, needs and explored how users navigate through the website
In collaboration with the Departments digital team, collated data and transcripts to draw out actionable insight from the user research. This includes potential user needs and or areas of the prototype website that can be changed/stripped back.
Basic wireframes have been created with limited content.
We are currently creating, editing and publishing content.
Existing team
The existing team consists of a DHSC Service Manager and Product Manager and some support from the DHSC Digital Team. On the current supplier’s side there is a Technical Architect, Digital Assistant, Designer, Front End Developer and performance analyst who will be handing over the project.
Current phase

Work setup

Address where the work will take place
DHSC team based in Victoria, London. The supplier can work remotely
Working arrangements
Suppliers must comply with DH travel and subsistence policy. There is a possibility of travel for user research purposes, which could be anywhere in the United Kingdom or internationally. Weekly meetings either in person or teleconference; Fortnightly show n tells. Travel to London should be expected.
The supplier will need to take a lead by being a role model in agile ways of working, and invest time in knowledge sharing and coaching to increase the capability of the digital team. The supplier may be responsible for recruiting user research participants as part of the bid.
Security clearance
Baseline Personnel Security Standard (BPSS) clearance required

Additional information

Additional terms and conditions

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Essential skills and experience
  • To deliver a public beta
  • Highly skilled, collaborative team with experience in delivering digital services that meet user needs and in line with the GDS Digital Service Standards.
  • Deliver digital services that meet the GDS Digital Service Standard criteria and pass GDS service assessments and how this will ensure the successful delivery of this service.
  • Show that your governance is agile, based on clear and measurable goals, and has a clear focus on managing change and risk in real time.
  • Build a service that can be iterated and improved on a frequent basis and make sure that you have the capacity, resources and technical flexibility to do so.
  • Develop prototypes iteratively by user testing/research and how this will ensure the successful delivery of this service.
  • Prioritise key content and features using metrics, analytics, and user feedback and how this will ensure the successful delivery of this service
  • Prioritise product and programme delivery using effective estimation and sizing techniques and how this will ensure the successful delivery of this service.
  • Follow GDS design patterns where appropriate; meet accessibility standards and how this will ensure the successful delivery of this service
  • Use automated (testing) environments and implement continuous integration, delivery & deployment and how this will ensure the successful delivery of this service.
  • To be able to explain ideas and thought process to those with limited digital/ technical background.
  • Show demonstrable evidence of previous projects or a process for handing over of website for client to manage self-sufficiently.
  • To have plenty of enthusiasm and passion. To clearly understand our vision, wants and aims.
  • To be proactive to ensure a good delivery of service
  • Explain how you’ll have a team that can keep improving the service after it goes live and demonstrate how you’ll monitor the status of your service.
Nice-to-have skills and experience
  • Demonstrate experience of successful delivery of digital services from Beta to Live.
  • Have experience upskilling client staff.
  • To have experience working with Government Depts. in similar projects.
  • To come with innovative, creative ideas and be able to advise on what good looks like.
  • Experience of taking over a project from incumbent supplier

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Approach and methodology
  • Technical solution
  • How the approach or solution meets user needs
  • Estimated timeframes to complete the work
  • Team structure (with roles and responsibilities)
  • Value for money
  • How risks and dependencies are identified and approaches to manage them
  • Approach to maintaining control, transparency and quality
Cultural fit criteria
  • Work as a team with our organisation and other suppliers
  • Transparent and collaborative when making decisions
Payment approach
Capped time and materials
Assessment methods
  • Written proposal
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Are you planning on holding a supplier engagement day to share your requirements and allow suppliers to engage with you directly to understand the needs and prepare their responses
Yes, the details of this are already on the advert - Wednesday 31st January 10-11am
2. The details of the supplier meeting:
Supplier Meeting - Wednesday 31st January 10am - 11am

Connecting directly from a room system?

1) Dial: or
2) Enter Meeting ID: 912 753 319

Just want to dial in on your phone?

1) Direct-dial with my iPhone or
+44.203.608.5256 (United Kingdom)
(Global Numbers)
2) Enter Meeting ID: 912 753 319
3) Press #
3. Can you please share the Discovery, Alpha output and GDS assessment report so that we understand the challenges you are facing and any gaps in the service being provided by the incumbent?
There is no formal GDS assessment report. However please see attached presentation slides
4. Can you please confirm who the current supplier is for the MVP in Beta?
Our current supplier are not digital delivery experts and hence took this work as part of a larger piece of delivery where it was decided they should focus
5. What platform/CMS has the Beta MVP been built on or has a solution not been selected yet?
Current website has been developed using an open source framework in DotNetNuke. We are open to suggestions for the most suitable platform/CMS as we move to a Live site
6. Why is the current supplier not contracted to complete the project?
Current supplier are not resourced to meet the expectations of DHSC on GDS assessment and of the policy team to explore innovative communications methods through the website
7. What budget has been approved for this work?
A budget envelope has been agreed of up to £180,000 inc VAT over a period of 4 years. This will include hosting maintenance and a reasonable amount of expenses for the service. On the understanding that the costing here is negotiable if there are issues with delivery.
8. Will the project require further user research or has this phase already been completed to your satisfaction?
user research has been conducted to get us to MVP stage. To meet GDS standards, suppliers will have to demonstrate how this will be built on by conducting further user research at different events and arising opportunities. Members of the team will be attending a workshop in Malaysia this March, suppliers will be expected to come up with a user research plan with the product manager to gather intel from a priority user group who we have not yet addressed in great detail.
9. When will the results of this Discovery phase be made available?
The project did not go through a traditional digital standard phase. Please see presentation slides . Further user research will be required.
10. Are any particular continuous integration technologies established fro the project?
No, nothing has been established and we will be happy to take advice from the appointed supplier
11. How long a hand-over do you anticipate?
Current supplier will provide a zipped copy of the application files and also a database backup of the site, with basic documentation to allow restoration of the site. We anticipate a week to get the new supplier up to speed.
12. Do you have a tech stack preference?
No, nothing has been established and we will be happy to take advice from the appointed supplier
13. Would you be looking to have potential grantees apply for grants through your website?
Yes, but that will be via Mattsoft. So potential grantes will be directed to that from the website.
14. You mention “We are currently creating, editing and publishing content.” – what is the url for the site?
We are currently working towards an MVP which is not ready to be published
15. You say that “the user experience is suboptimal and also not meeting government digital standards” despite having stated that some user research, design, wireframing, etc. has been completed. Do you foresee a need for this to be repeated or supplemented, and if so does your proposed budget include this?
No need repeat user research that has already taken place, however we expect the supplier to come up with innovative ways in planning user research as part of the iteration process as part of the website's continous development
16. Besides the “user experience is suboptimal and also not meeting government digital standards” what other aspects of the work so far have been less than satisfactory?
We are seeking a supplier who has the right resources in place to be able to meet DHSC aims and objectives as well as GDS standards. Someone who will share our passion and to be engaging with a lot of energy.
17. Can you please confirm that the project is already in beta, and that the new supplier will be required to continue the beta/MVP to take into live?
Yes, that is correct
18. Approximately how many pages are anticipated for the final site?
Difficult to say at this stage however anything that is developed will be expected to go on
19. Will the new supplier be expected to maintain content?
20. Is content personalisation in scope for this build?
Not at present, however we are open to suggestion based on user research requirements
21. Do you have a preferred CMS in mind for this project? Will you be open to re-evaluating the CMS choice if the supplier makes a recommendation?
No preference on CMS and Yes, we are open to suggestions.
22. How many languages will the site need to support?
This will depend on next stages of user research
23. Can you outline the DH travel and subsistence policy, especially in relation to travel outside of London and internationally (as mentioned for possible user research)?
This will be in the generally attachment folder
24. Integration with systems: (a) Can you list any systems the site will need to integrate with e.g. any CRM system, or data feeds, and give a thumbnail sketch of the level of integration?
There are no integrations with systems at present
25. Will the site have to undergo formal GDS service assessment or do you just need to “work towards” the GDS standards as a guide?
DHSC policy is that we undergo GDS service assessment
26. Where and how is the site hosted and will the new supplier be expected to be responsible for providing hosting for the live site?
Currently hosted on DotNetNuke. Supliers will be responsible for hosting and maintenance.
27. Will the supplier be expected to provide SLA based support for the site?
28. Will the site need to be responsive and to what accessibility standard must it comply?
Yes. GDS accessibilty standards apply
29. What interactive features are needed on the site? Maps, event feeds, etc.
Currently Maps and interactive learning products. More will be dependent on user research
30. Security clearance: Is the buyer willing to consider applicants willing to undergo clearance for its staff after being chosen, or must all staff which we intend to place on the project already hold clearance?
As this is not a transactional website, Preference is that staff have already passed clearance but DHSC are content for supplier's staff to undergo security clearance after being chosen after being chosen.
31. Attached are:
Presentation Slides from engagement
Alpha presentation
Discovery Presentation
DHSE Expenses Policy
32. what programming language is used
The website is built on a Content Management System called Dot Net Nuke (DNN) using the out of the box framework and modules. The current supplier has customised the HTML and CSS elements of this and have created some bespoke modules predominantly in C# and VB. The database is SQL.
33. As an extension on the question on Budget
DHSC recognise this is an international project and although we expect suppliers to make use of opportunities for user research internationally, we are willing to be flexible in regards to expenses and recognise this may increase the budget envelope, which we are willing to consider. Please note that research can also be conducted remotely via Skype or other screen sharing software.
34. Question 25: GDS Assessments
This will be an internal DHSC interview process, most likely, and not full GDS Assessment