PHE CUSTOMER REQUIREMENTS SPECIFICATION

Request for Proposal (RFP)
DSF01-009
Public Health England – Website Transition
APPENDIX A – CUSTOMER REQUIREMENTS
SPECIFICATION
This document forms Appendix A to the Request for Proposal (RFP) for Digital Services Framework
Agreement – RM1043, along with Pricing Matrix (Appendix B) and an Award Questionnaire (Appendix C).
What’s included?
PROJECT START DATE AND TIMEFRAME
CURRENT SITUATION/ BACKGROUND INFORMATION
SUMMARY OF REQUIRED OUTCOMES AND USER NEEDS
CAPABILITIES AND ROLES
PRICING MODEL
CUSTOMER LOCATIONS
TEST & DEVELOPMENT REQUIREMENTS
Digital Services Framework Agreement - RM1043
Customer Requirement Specifications
Appendix A
1
Request for Proposal
Digital Services Framework Agreement – RM1043
PROJECT START DATE AND TIMEFRAME
Key delivery dates
PROJECT PHASES
Discovery
START DATE
April 2014
COMPLETION DATE
Late July 2014
CURRENT SITUATION / BACKGROUND INFORMATION
Public Health England's (PHE) mission is to protect and improve the nation’s health and to address
inequalities. PHE is an executive agency of the Department of Health and was formed in April 2013. PHE is
committed to going ‘digital first’ as set out in the Department of Health Digital Strategy.
PHE are in the Discovery phase of their digital programme and looking to source a co-located digital strategy.
The Potential Provider will explore and provide PHE’s needs for a digital strategy. The strategy development
will include, but is not limited to, the agile delivery of:

explaining how digital can help PHE achieve its objectives

reviewing PHE’s existing digital products and services, and identifying gaps

defining how this will be implemented
Current artifacts
● Prototype digital strategy
● List of senior internal stakeholders and input from them about digital
● List of external stakeholders
● Audit of our 150 websites
● Content strategy and user needs for PHE publishing (in development)
Current Roles and Responsibilities of the Customers digital team
Deputy Director for Digital
Responsible for the digital strategy and website
transition
PHE digital team
The PHE digital team operates the PHE website and
is developing its content strategy. Over the next 1824 months the team will be transitioning PHE’s 150
websites to GOV.UK and NHS Choices. This team
has capability in technical standards and delivery,
and runs the PHE intranet.
Current Technologies and Languages
N/A
Digital Services Framework Agreement - RM1043
Customer Requirement Specifications
Appendix A
2
Request for Proposal
Digital Services Framework Agreement – RM1043
SUMMARY OF REQUIRED OUTCOMES AND USER NEEDS
Cross Functional
requirements:
PHE requires the development of a digital strategy.
Volumetrics:
PHE has 150 websites. The largest are PHE and HPA, which together receive
500,000+ monthly visits.
Technologies and
Design Approach
The strategy should be designed and developed in iterations, in line with the
Government Service Design Manual.
Project Dependencies
The successful delivery of the project has dependencies with:
Policy
The strategy must be written by the end of July 2014.
It must benefit users while following:
i.
PHE’s priorities
ii.
Department of Health’s Digital Strategy, which commits PHE to going
‘digital first’
iii.
Government Digital Strategy
Intention
The strategy must be based on the needs of PHE users.
Building PHE’s digital capability is also a priority. The strategy much be
actionable and contain a roadmap of activity. The Potential Provider must work
closely with PHE colleagues to help them to learn more about digital.
Stakeholders
Securing stakeholder support for a ‘digital first’ PHE. This includes but is not
limited to: internal and external stakeholders, working level stakeholders and
senior stakeholders. The Potential Provider must provide a balance between
departmental needs and a functional solution.
Digital Services Framework Agreement - RM1043
Customer Requirement Specifications
Appendix A
3
Request for Proposal
Digital Services Framework Agreement – RM1043
SUMMARY OF CUSTOMERS PROJECT OUTCOMES:
Digital strategy

identify what digital can do to help PHE achieve its objectives and meet its user needs – ie. how it can
go ‘digital first’

engage in depth across the organisation and externally

review digital products and services


advise on the best course to develop these products and services
provide a plan of how this can be implemented
SUMMARY OF BUSINESS OUTCOMES
Digital strategy

outline specification

mapping and analysis of users and their needs

light-touch reporting of key findings from stakeholders

analysis as required

digital strategy including delivery plan
SUMMARY OF USER NEEDS
This is a strategy development project and at this stage the user needs have not been defined. User needs
which are currently being developed for the PHE content strategy may be re-used in the digital strategy. User
needs for particular products may be developed as part of the strategy development.
Digital Services Framework Agreement - RM1043
Customer Requirement Specifications
Appendix A
4
Request for Proposal
Digital Services Framework Agreement – RM1043
CAPABILITIES AND ROLES
Roles sought under this RFP
The Potential Providers are required to propose the roles/ numbers that will be required to deliver the
Discovery Phase. Please refer to the Pricing Matrix (Appendix B)
The Potential Providers should consider, but is not limited to the following within their submission::

a the team will be very integrated with PHE’s digital programme

team members will be co-located on PHE site for at least half of their time

a team will report to the Deputy Director for Digital

a team which has experience working in health, central government and/or the public sector
CAPABILITY
CUSTOMERS REQUIRED OUTCOME
Product Development & Service Design
Include, but are not limited to expertise of
 Product Management
 Business Analysis
 Project and Business Outcomes as specified
above, specifically related to this Capability
and development of a digital strategy
Please note that PHE anticipates a team equivalent to 2/3 people, but is flexible on the make-up of the team
and seniority of team members.
PRICING MODEL
Customer’s preferred pricing model or models, for Schedule of Works (SOWs) that may be awarded as a
consequence of this Further Competition, are shown in the following table:
PRICING MODEL
PROJECT PHASES
Fixed price
Discovery phase
CUSTOMER LOCATIONS
UK REGION
CUSTOMER LOCATIONS: CITIES OR TOWNS
London
London, multiple sites
TEST & DEVELOPMENT REQUIREMENTS
N/A
Digital Services Framework Agreement - RM1043
Customer Requirement Specifications
Appendix A
5