Public Health England

National Tuberculosis Surveillance System: Beta and Live

Incomplete applications

17
Incomplete applications
15 SME, 2 large

Completed applications

24
Completed applications
19 SME, 5 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Thursday 4 April 2019
Deadline for asking questions Thursday 11 April 2019 at 11:59pm GMT
Closing date for applications Thursday 18 April 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work PHE wishes to replace two legacy TB surveillance systems. Discovery and Alpha have been completed and PHE is now seeking a supplier to build and deploy a replacement system which will deliver some extensible components for reuse in other systems, and to migrate existing data
Latest start date Monday 1 July 2019
Expected contract length 24 months (2 Years)
Location No specific location, eg they can work remotely
Organisation the work is for Public Health England
Budget range £500,000 - £850,000 excluding VAT

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done All cases of active TB must be notified to PHE within 72 hours of diagnosis. This allows for timely public health action to be taken by a multi-disciplinary team of NHS and PHE staff. Information on TB cases is used to monitor UK trends, to report internationally and to support the prevention of transmission of TB.

PHE hosts two systems to monitor cases of active TB. These are at end-of-life. PHE wishes to replace these with a single, modern system which will continue to be hosted by PHE.

Completion Date 31/03/2020
Problem to be solved The existing systems used to perform surveillance on cases of active TB in England, Wales and Northern Ireland have reached end of life. PHE wishes to replace these systems with a single one, built on a modern technology stack and which will provide a number of extensible components which can be reused by other PHE surveillance programmes in due course.
Who the users are and what they need to do TB nurses, respiratory doctors, administrative staff in NHS clinics: adding and updating the surveillance record for each case of active TB;

Laboratory staff: providing test results for new and existing cases;

PHE Field Service and Health Protection teams: analysing surveillance data, managing TB incidents, multi-disciplinary TB cohort review, ensuring high level of data quality, investigating outbreaks of TB, advising local staff on appropriate measures;

National TB surveillance team: data quality monitoring and production of statistics on TB trends including indicators to support national TB strategy, annual report & annual dataset submitted to international bodies including World Health Organisation
Early market engagement None
Any work that’s already been done Discovery, Alpha and initial phase of Beta (small reporting release using ETS data)

Discovery included:
- personas
- user needs & pain points
Alpha included:
- proof of concept data migration
- clickable mock-ups for a number of areas of the new system
- release plan for NTBS development
Reporting release included:
- identity and single sign-on solution using PHE's Windows AD
- reusable permissions solution, limiting which records a user can view
- auditing of record-level access
- prototype data model
- a suite of six reports
Existing team The supplier will be working with:
- PHE Product Owner for TB surveillance
- full-time Scientific Subject Matter Expert
With additional input from:
- national and London TB surveillance teams
- project assurance leads for National Infection Service
- PHE ICT team
There will be further input from stakeholders across the NHS and PHE.

Much of the reporting functionality required by the new system will be developed in-house, and the supplier will work alongside reporting specialists from the National Infection Service at PHE.
Current phase Beta

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place It is anticipated that the successful bidder will be able to work from their own location in the UK. However, the supplier should expect regular travel to PHE's office at 61 Colindale Ave, London NW9 5EQ. The supplier will be reimbursed for reasonable travel costs.

Expenses must be included within the contract sum and must be in line with PHE policy.
Working arrangements The supplier will be expected to work using Scrum and all ceremonies will be open to the PHE project team, with a wider set of stakeholders expected to attend Show and Tell. The supplier will follow a 'one team' approach with the Product Owner and Scientific SME attending all daily stand-ups and participating fully in the work of the team.
Security clearance Not required, DBS checks may be required.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions None

Skills and experience

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

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • E1) Recent experience (within 3 years) of developing and delivering systems for 600+ users based in different geographies and organisations
  • E2) Recent experience (within 3 years) of developing and delivering systems using Microsoft technology stack including .NET and SQL Server
  • E3) Recent experience (within 5 years) of supporting systems deployed on customer infrastructure where access to the environment is limited
  • E4) Recent experience (within 3 years) of delivering multi-release software development projects using the Agile methodology
  • E5) Recent experience (within 5 years) of migrating complex person-level data (c. 100,000 records)
  • E6) Recent experience (within 5 years) of delivering loosely coupled solutions to allow modules to be reused by other systems
  • E7) Recent experience (within 5 years) of building on existing user research and continuing user research as part of the development process
Nice-to-have skills and experience
  • N1) Experience of working on solutions for disease surveillance
  • N2) Experience of working on solutions for healthcare and/or a national scope
  • N3) Experience of embedding Agile within an organisation with low Agile maturity
  • N4) Experience of working in teams encompassing development staff from customer organisation
  • N5) Experience of PDS mini-service
  • N6) Recent experience of building on a Discovery and/or Alpha delivered by another organisation
  • N7) Experience of making software open source

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 6
Proposal criteria
  • P1) Proposed approach to project (15)
  • P2) Project plan and methodology (15)
  • P3) Proposal has identified risks and dependencies and offered approaches to manage them (10)
  • P4) Proposed approach to project handover and implementation activities (10)
  • P5) Approach to data analysis, transformation and migration (10)
Cultural fit criteria
  • The shortlisted suppliers will be invited to demonstrate cultural fit in in the following:
  • C1) Examples of previous experience of working with UK Government, local authorities or large organisations with a range of different stakeholders (2.5)
  • C2) Communicating effectively and being responsive to client needs (2.5)
  • C3) Understanding and respecting client's internal governance and procedures (2.5)
  • C4) Working within the constraints of public sector organisations, including budgets, timescales and change (2.5)
  • Cultural fit will solely be assessed at the presentations i.e. a written response will not be required
Payment approach Capped time and materials
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Presentation
Evaluation weighting

Technical competence

60%

Cultural fit

10%

Price

30%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Have the discovery and alpha phases for this opportunity been delivered in-house or by an incumbent supplier? The Discovery and Alpha phases were completed by a joint team of in-house staff and an external supplier (Aire Logic). Relevant outputs from discovery and alpha phases will be made available to short-listed suppliers.
2. Aire Logic appear to have a suitable technology called Forms4Health – why are you tendering this opportunity if there is already a preferred provider that has the appropriate solution and you have an existing commercial relationship with? PHE has carried out an options analysis which determined that a custom solution built for and wholly owned by PHE is the most appropriate option.
3. In your essential requirements, you say:
"PHE wishes to replace these systems with a single one, built on a modern technology stack and which will provide a number of extensible components which can be reused by other PHE surveillance programmes in due course."
.Net does not represent a 'modern technology stack'. Modern outfits develop in opensource languages (as recommended by GDS). Are you open to a modern stack?
PHE hosts and runs systems which are predominantly delivered using Microsoft technologies. .NET is the preferred technology stack for PHE.
4. Regarding the essential item "E2) Recent experience (within 3 years) of developing and delivering systems using Microsoft technology stack including.NET and SQL Server". Is this a requirement because the new system will need to be built in.NET or that it might need to integrate with.NET systems or that.NET is the specified tech stack for PHE? .NET is the preferred tech stack for PHE.
5. The contract term is specified as 24 months but the delivery date is stated as 31st March 2020. Can you clarify whether there is therefore an expectation of ongoing support post delivery of the system? The initial contract is for the build of the system only but options for support will be discussed with shortlisted suppliers. 24 months is the standard maximum length of DOS contracts within which specific milestones can be agreed and this duration is also used to allow for any unforeseen delays.
6. Can you clarify what expectation you have regarding a PDS mini service which is listed within the nice to have element? The NTBS will integrate with PDS using the PDS mini service interface. A supplier with experience of the PDS mini service would be beneficial but not essential.
7. Has the current stages been undertaken against GDS standards and is that expected to continue with the full Beta to live cycle? We have followed the GDS Service Manual for Discovery and Alpha and will be for remaining phases. However, the project is not being formally assessed by GDS.
8. Clarification for question E7: The question asks about "building on existing user research and continuing user research as part of the development process". What does user research mean in this context? We expect to broadly follow the approach to Beta user research given in the GDS Service Manual: https://www.gov.uk/service-manual/user-research/user-research-in-beta In addition we would expect to iterate over some of the prototyping work done during Alpha https://www.gov.uk/service-manual/user-research/user-research-in-alpha
9. Can we have access to the work that has previously been done, including GitHub repositories for the Alpha and Betas. A range of outputs from the previous phases will be made available to shortlisted suppliers. Full access to all previous content will be made available to the appointed supplier.
10. It's mentioned that the supplier could work remotely. Also, in the work setup section is written down that the supplier should expect regular visits to your office. So, is it possible the supplier to be located in other country not in UK? We anticipate regular face-to-face contact with the supplier. The reference to remote working refers not being full-time co-located with the team in a PHE building, rather than the supplier team being based overseas. Furthermore, travel expenses need to be in line with PHE policy.
11. Would you be willing to host the solution in Azure using PaaS functions or is this strictly an on-premise solution? PHE's Cloud strategy is still developing. It is possible that we will opt for Azure hosting but it is more likely we will opt to host on-premise.