Awarded to cxpartners

Start date: Wednesday 1 September 2021
Value: £250,000
Company size: large
Public Health England (PHE)

PHE Talk to FRANK website technical development

17 Incomplete applications

13 SME, 4 large

15 Completed applications

13 SME, 2 large

Important dates

Published
Tuesday 20 April 2021
Deadline for asking questions
Tuesday 27 April 2021 at 11:59pm GMT
Closing date for applications
Tuesday 4 May 2021 at 11:59pm GMT

Overview

Off-payroll (IR35) determination
Summary of the work
To deliver technical development of the Talk to FRANK web site including performing user testing and user research, maintenance and providing new functionality where appropriate based on user needs; in order to support the Government Drug Strategy: https://www.gov.uk/government/publications/drug-strategy-2017
Latest start date
Monday 21 June 2021
Expected contract length
Up to 24 months
Location
No specific location, for example they can work remotely
Organisation the work is for
Public Health England (PHE)
Budget range
Up to £100,000 excluding VAT for 1st year. 2nd year budget will be subject to approval

About the work

Why the work is being done
The existing FRANK programme supports Public Health England’s strategic priority in “ensuring every child has the best start in life” and is a key part of the reducing demand and reducing harm strands of the Government Drug Strategy.
The current FRANK website is built on Contentful CMS and conforms to the Government Digital Services (GDS) standards, passing the live assessment in February 2020
There is an opportunity to build on existing research and knowledge to explore the digital component of the FRANK programme and deliver a better service to the public.
Problem to be solved
• To provide technical development for the Talk to Frank website and undertake user testing and user research to maintain this PHE digital service, to the existing standard, in line with the GDS service standard.
• To undertake user testing and user research to inform ongoing website updates to meet evolving user needs.
• To provide new content updates in line with legalisation, policies and Home Office and/or other governmental requirements.
PHE staff will lead on content changes in the CMS and will take on the role of Product Management/Ownership and SEO expertise. We expect the supplier to provide a full team, including but not limited to UX designer(s), developers, content designers, service team, branding and strategy.
Future work may include but not be limited to:
• identifying gaps in content (based on search results);
• designing a user journey for school children;
• increasing organic search by improving tool design;
• exploring and building new features to keep the service at the cutting edge (match other government drug sites).
Who the users are and what they need to do
The site receives approximately 500,000 active users per month. These include:
Drug users 14 – 65+ who take drugs: The site is used to seek (honest) information on drugs e.g. how long will a certain drug be in my system, what does it look like, what happens if I get caught, how do I deal with peer pressure?
Concerned others 14 – 65+: who are worried about those taking drugs around them (family or friends). These users would want to find out how to talk to and help their child/friend. They also want to be better informed about drugs and to seek information on where to get help and support for their friends and family and information about drugs and drug use.
PHE staff and drug stakeholders including those working in local authorities, health programs and cross-government departments use the service as a ‘fact-checking’ tool.
Early market engagement
N/A
Any work that’s already been done
The website has gone through the Discovery, Alpha and Beta phases passing the required assessments. It has also passed the Live assessment.
Some outputs of previous phases will be provided to the shortlisted suppliers. This will be detailed in the Request for Proposal.
Existing team
The work will be with the PHE Digital team (for hosting infrastructure), PHE staff more broadly and a national network of stakeholders.
PHE staff will manage the relationship with external stakeholders, which includes cross-agency work with Serco and Wavemaker. Also includes, cross-government work with Home Office.
Current phase
Live

Work setup

Address where the work will take place
Due to COVID-19, work will need to be predominantly undertaken remotely. If travel permits, there may be some attendance at workshops or other meetings at PHE offices.
Working arrangements
Work may be carried out remotely. Attendance at PHE offices may be required, within COVID-19 restrictions and after a risk assessment and subject to current guidance and legislation. Should the situation change the successful supplier will be advised accordingly.
Security clearance
N/A

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
  • For Essential and Nice to Have skills/experience stating “recent experience”, please provide the year of the project within your answer. Insert n/a in the corresponding response field for this guidance
  • Recent experience (within 3 years) of taking over the support, maintenance and development of a website developed by another supplier.
  • Recent experience (within 3 years) of applying the principles of user centred design to the development of digital solutions in line with GDS Standards.
  • Recent experience (within 3 years) of designing digital tools to attract/engage with, meet the needs of and influence behavioural change, for a diverse range of users especially teenagers/young adults
  • Recent experience (within 3 years) of working with organisations to change their ways of working including introducing service design, innovation, or user-centred design methodologies.
  • Recent experience (within 3 years) of creating and producing digital applications and information that supports digital inclusion and content types that optimise engagement
  • Recent experience (within 3 years) of working within environments with complex hierarchal decision-making structures and where multiple stakeholders have differing levels of digital awareness
Nice-to-have skills and experience
  • Recent experience (within 3 years) of working with stakeholders including healthcare experts, healthcare providers, digital development teams, and the general public. Working in the drugs landscape is highly desired.
  • Recent experience (within 3 years) of working with interdisciplinary and cross disciplinarily project teams including clinical and policy teams.
  • Recent experience (within 3 years) of engagement with hard-to-reach groups (for example, drugs being illegal)
  • Recent experience (within 3 years) of engagement with and inclusion of users with limited digital skills (for older concerned others) but also for more experienced users (using incognito browsers).

How suppliers will be evaluated

All suppliers will be asked to provide a written proposal.

How many suppliers to evaluate
5
Proposal criteria
  • Proposed approach to applying the principles of user centred design; user insights; policy/legislation and scientific evidence to the development of digital solutions. (max score: 30)
  • Approach to DevOps and other aspects of management of a digital website (max score 20)
  • Approach to taking over an existing digital website project (max score 10)
Cultural fit criteria
  • The shortlisted suppliers will be required demonstrate cultural fit through a presentation to a panel that should summarise their proposal for clarity and demonstrate how they propose to:
  • Work within the constraints of public sector organisations including budgets, timescales and change (max score 3);
  • Work with a range of stakeholders including ones that have little knowledge of agile or user-centred design (max score 3);
  • Work with stakeholders that from a range of disciplines including science, technology and policy that have apparently opposing interpretations of project goals (max score 4); and
  • Please give details of how this contract may result in employment, training or education that may reduce the disability employment gap (max score 10)
Payment approach
Capped time and materials
Additional assessment methods
  • Case study
  • Work history
  • Presentation
Evaluation weighting

Technical competence

60%

Cultural fit

20%

Price

20%

Questions asked by suppliers

1. What is the technology stack of existing website?
Talk to Frank is hosted on AWS and the following technologies are used:

CMS: Contentful (https://www.contentful.com)
Front-End: ReactJS
Emails: MailGun
CI: Buddy
Search: AWS Elasticsearch provide the search capability
Logs: Server-side logging via Sentry (https://sentry.io)
Framework & Languages: NodeJs, JavaScript
Hosted: AWS Elastic Beanstalk
2. How many and what type of resources are required?
PHE staff will take on the role of Product Management/Ownership and SEO expertise. We expect the supplier to provide a full agency team, including UX designer(s), developers, client service team, branding, strategy. In the past the supplier core team consists of a Project Manager/Account director and a Principal Service designer/Design Lead. When in sprint, the team may grow to include designer, content writer, developer, researcher and/or tester, as needed.
3. We assume that resources can work from outside UK also. Please confirm.
Yes however, it is expected that any meetings and work will be conducted within normal UK working hours. Additionally, although we are currently remote working, there may be a need for face to face meetings during the lifetime of the contract and expenses would need to be met by the supplier.

In addition, BPSS clearance is a requirement for UK based staff. BPSS does not apply to overseas suppliers therefore, overseas suppliers would need the equivalent and the onus is on the supplier to establish this. Please refer to the embedded link for rules for working outside the UK: https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/714002/HMG_Baseline_Personnel_Security_Standard_-_May_2018.pdf
4. Are PHE looking to move away from Contentful as a CMS?
No. The CMS currently in place is sufficient for our needs. The focus of the work will be on the front facing website and UX.
5. Do you want suppliers to use any specific technology?
We expect the supplier to be proficient with the existing tech stack.
6. Is there any post production support time in scope?
The budget is intended to cover continuous improvement of the existing product and to cover ongoing maintenance.
7. Can international supplier apply to this project?
Yes however, it is expected that any meetings and work will be conducted within normal UK working hours. Additionally, although we are currently remote working, there may be a need for face to face meetings during the lifetime of the contract and expenses would need to be met by the supplier.

In addition, BPSS clearance is a requirement for UK based staff. BPSS does not apply to overseas suppliers therefore, overseas suppliers would need the equivalent and the onus is on the supplier to establish this. Please refer to the embedded link for rules for working outside the UK; https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/714002/HMG_Baseline_Personnel_Security_Standard_-_May_2018.pdf
8. Is there an incumbent?
There is no incumbent but the previous phases of the project were delivered by CXPartners. We have no way of knowing if they or any other supplier are applying for this opportunity but a handover will take place should this be needed.
9. Do you wish to continue with Contentful CMS, such that the successful supplier would be developing within Contentful?
Yes, Contentful is sufficient for the existing needs of the product.
10. If you are willing to look at alternative CMSs, must they be headless CMSs?
Contentful is sufficient for the existing needs of the product. We are not looking to change the CMS.
11. Is this brief to iterate on the existing Talk to Frank website or to create a completely new site?
Iterate on the existing Talk to Frank website
12. Is the expectation to deliver the site using Wavemaker’s locode platform?
The site had already been delivered and we expect continuous improvement to the user experience using the existing tech stack.
13. Will the maintenance of the site include the maintenance of the underlying cloud infrastructure or will that be managed by PHE Digital Team?
The underlying infrastructure will be managed by PHE Digital.
14. What is the reason for moving away from the current provider?
Previous DOS contract expired therefore going out to tender
15. What objectives and Key Performance Indicators (KPIs) are guiding the Talk To Frank website redevelopment?
Previous DOS contract expired therefore going out to tender. We are not requesting website redevelopment but rather continuous improvement based on user needs.
16. Is there an existing roadmap for development for the website?
There is an existing backlog and we expect the supplier to work with us to build out the roadmap.
17. When would the shortlisted providers be notified and when would the delivery window for the RFP be?
The expected timeline is as follows:

Shortlisting Exercise: 04/05/21 to 10/05/21
RFP sent to shortlisted suppliers: 11/05/21
RFP Question Deadline: 18/05/21
RFP Q & A Sent: 24/05/21 (It is the Intention of PHE to issue this sooner)
RFP Deadline: 25/05/21 12pm
18. Can you provide any more details of the technology stack involved besides Contentful CMS and React? Inc. what license level the site uses for Contentful?
Talk to Frank is hosted on AWS and the following technologies are used:

CMS: Contentful (https://www.contentful.com)
Front-End: ReactJS
Emails: MailGun
CI: Buddy
Search: AWS Elasticsearch provide the search capability
Logs: Server-side logging via Sentry (https://sentry.io)
Framework & Languages: NodeJs, JavaScript
Hosted: AWS Elastic Beanstalk
19. Do you have any existing user persona’s for the different audiences or will these need to be designed as part of the development process?
We have existing user personas for different audiences. There will be a small piece of work around developing one new user persona.
20. For the user testing, is the supplier expected to lead on recruitment of participants for user testing? Or do you have an existing recruitment or market research supplier that the supplier will be expected to work with?
The supplier is expected to lead on recruitment of participants. PHE will be able to support this process where needed.
21. Will the UX designers and developers be working with fixed brand guidelines? Or is a refresh of the Frank brand identity part of this scope?
We have existing brand guidelines and the Frank brand is well established. A refresh is not expected though we are open to small improvement suggestions.
22. Do you require any form of marketing strategy or recommendations to support the engagement of the Frank website technical development?
TBC. This is likely to be covered within the RFP to shortlisted suppliers.