Awarded to Valtech Ltd.

Start date: Wednesday 20 December 2017
Value: £396,050
Company size: SME
NHS Digital

HCON01414 Bloomreach Digital Experience Platform for NHS Digital

2 Incomplete applications

0 SME, 2 large

2 Completed applications

2 SME, 0 large

Important dates

Wednesday 11 October 2017
Deadline for asking questions
Wednesday 18 October 2017 at 11:59pm GMT
Closing date for applications
Wednesday 25 October 2017 at 11:59pm GMT


Summary of the work
NHS Digital wishes to recreate their website ( on a new content management platform. New platform will be built using Hippo (, an open source CMS platform and involves the deployment of the enterprise edition (Bloomreach Experience) to extend functionality. This MUST be deployed by Febraury 2018.
Latest start date
Monday 4 December 2017
Expected contract length
6 months
Yorkshire and the Humber
Organisation the work is for
NHS Digital
Budget range
Maximum budget of £250,000 for the Bloomreach experience module, perpetual Bloomreach experience license and access to Bloomreach training.

Maximum budget of £400,000 for the migration from the existing CMS system in to Bloomreach.

About the work

Why the work is being done
The existing CMS that NHS Digital serves the website has reached the end of its contracted lifecycle. The license to use the legacy CMS expires in March 2018.

NHS Digital is responding to an audit of our products and services. We know that we must make it simpler and easier for our customers to access the information, services and data that they require. For this reason we wish to utilise a platform that can assist us in the curation and orchestration of user experiences across our organisational silos.
Problem to be solved
Web delivery:
Delivery of a new NHS Digital website on the chosen platform including:
- Front and back end build
- Testing
- Perpetual licence to chosen platform

Data export:
Export of all data, metadata, content, media in JSON format (where applicable) from the two existing NHS Digital websites (both on versions of GOSS iCM):

Data import:
- The import of identified data from the JSON data in to the new website instance
- The creation of navigation architecture as in the existing website
Who the users are and what they need to do
As NHS Digital website Service Manager, I need to replatform NHS Digital website to a new CMS to ensure service continuity for all internal and external users, stakeholders and commissioners

As NHS Digital website Product Owner I need to ensure that training is provided on CMS so internal users can contribute content to the website

As NHS Digital Solutions Architect I need to have put in place an architecural footprint that allows services and content to be integrated into the CMS / DXP so that the website becomes a portal for our users to access the services they need.
Early market engagement
Any work that’s already been done
Existing team
The NHS Digital Website team are responsible for the digital presence. We are Product Owners, Content Authors, UX Architect, IA Architect, Visual Designer and a Service Head. For this work you will be working with the website team and will have access to subject matter experts from accross our portfolio of work. You will also have access to the teams in connected projects and the third party suppliers engaged in the connected projects.
Current phase

Work setup

Address where the work will take place
1 Trevelyan Square, Boar Lane, Leeds, LS1 6AE
Own office space / home working
Working arrangements
Onsite and offsite as needed, based on the approach that the vendor selected promotes. We imgine that you will need to spend 50% of time allocated on site learning about our challenges, this is best completed at our Leeds, London and Southampton office bases.
Security clearance

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
  • Have experience of deploying the Hippo / Bloomreach Java-based CMS for client projects, being able to show successful delivery [100 points]
  • Be able to stand up multi-functional agile teams to deliver the project, including full-stack (front and back end) development in Java [100 points]
Nice-to-have skills and experience
Faciliates for NHS Digital staff to work on supplier site in Leeds, Manchester or London [20 points]

How suppliers will be evaluated

How many suppliers to evaluate
Proposal criteria
  • Technical solution [25 points]
  • Approach and methodology [25 points]
  • How the approach or solution meets our project goals [50 points]
  • Estimated timeframes for the work [50 points]
  • Team structure [50 points]
  • Value for money (VFM) [50 points]
Cultural fit criteria
  • Be transparent and collaborative when making decisions [10 points]
  • Experience of successful collaborative working as part of a multi supplier delivery team sharing knowledge within the team [50 points]
  • Take responsibility for their work [25 points]
  • Can work with clients with low technical expertise [10 points]
  • Able to challenge the status quo and use persuasion skills to achieve business buy-in [50 points]
  • Bring agile mindset and principles into a developing organisation [10 points]
  • Have a no-blame culture and encourage people to learn from their mistakes [25 points]
Payment approach
Fixed price
Assessment methods
  • Written proposal
  • Case study
  • Work history
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

1. Instruction document and terms and conditions are available for this opportunity via Delta:
Please click this link:

and use access code: J3B6787V7Y
2. You state as an essential requirement that suppliers must have experience of deploying the Hippo / Bloomreach Java-based CMS for client projects. Can we ask why you have selected that specific CMS and if you would consider alternative products? We have plenty of Drupal experience and capability we could offer at the moment which is a stronger rated solution by the market in general, is a more modern framework with a larger development and support community, and is similarly open source so equivalent price point. Would this alternative capability be acceptable?
Our CMS and digital experience requirements match closely to that of the Bloomreach product. We also selected the Bloomreach product based on the core Hippo CMS open source / open standards platform. Architecturally the Bloomreach product meets our corporate strategy for Java based platform. Aquia (a Drupal product) was considered and discounted along with other COTs CMS products.
3. While we understand that you have done a product selection exercise, if we can provide evidence of an alternative approach using a more cost effective Drupal based CMS product, would you be interested in understanding why we think there may be a better way of delivering your outcomes?
Drupal does not fit with our business strategy at this time and has been discounted as a platform by our architectural boards. We do not wish to develop on a Drupal platform. It's important that we stick to our choice of development language. This is Java, and therefore is part of the reason why we have chosen Bloomreach as the platform to move forward with.
4. You have also asked for a perpetual license and training to be included. Do you have an estimated plan for a post-implementation phase, for which further training, support, and maintenance would be required?
There is not a post implementation training plan yet. This is a plan that will be drawn up with the business, winning vendor and Bloomreach. We understand that in order to access Bloomreach training we must have purchased the Bloomreach Experience module or PaaS. This is partially why this requirement is in scope of the migration effort.
5. The project duration is listed as 6 months. Are we right in assuming that the expiry of the existing CMS license in March is in part driving this end date? Or is it based on an estimated size of the effort required? If the latter, are you able to share any 'working' please?
The legacy CMS contractual end date is driving the migration timescale.
6. You have stated that the payment approach is fixed price. Whilst this would fit with the Bloomreach licensing model, it appears to be at odds with your aspiration to deliver the project through Agile methods. Would you therefore be open to other commercial approaches for the development and migration scope, such as Capped Time & Materials?
In principle it’s OK to suggest a capped T&M approach, however we reserve the right to exclude providers on this basis should the Capped T&M approach suggested be deemed unsuitable for the organisational needs.