ITEP0731E - RIS3 Chief Data Office (CDO) - Package 5: CDO cross-capability

Award

Value

£35,000,000

Suppliers

Classifications

  • Data analysis services

Tags

  • award

Submission Deadline

2 months ago

Published

3 weeks ago

Description

CROSS-CUTTING DELIVERY ACROSS THE CHIEF DATA OFFICE (CDO)

Within National Highways we continue to see the change in focus and benefit across the 
organisation of consolidating digital and data services culminating in the formation of the Digital 
Services Directorate and the Chief Data Office we see today. 

In today's digital age, data is the lifeblood of effective governance, enabling evidence-based 
decision-making, enhancing customer services and driving innovation across various areas of our 
business. Recognising the critical importance of data management and governance we propose 
to continue in our investment of services and capability of a high functioning and fit for purpose 
Chief Data Office.

Whilst the data maturity of National Highways has increased, it has held steady at its current 
level since 2020. To ensure our data is fit for our future purposes and can enable our digital 
ambitions, we identified the need to invest in building data capability across the organisation, 
embedding a data operating model into our business operating model and building data literacy 
and professionalisation of data specialists.

The core elements of a Chief Data Officer (CDO) role typically include a combination of 
responsibilities, skills, and competencies aimed at driving effective data management, 
governance, and utilisation within organisations. We have identified the core elements as:
- Data Strategy
- Capacity Building and Awareness
- Stakeholder Engagement
- Innovation and Continuous Improvement

Documents

Premium

Bypass the hassle of outdated portals. Get all the information you need right here, right now.

  • Contract Agreement

    The official contract terms, conditions, and scopes of work.

    Download
  • Award Notice

    Details on the tender award and selected suppliers.

    Download

Similar Contracts

Open

2024-747 Meat Foodservice Data requirements

AHDB currently source GB Foodservice data, quarterly, through Kantar Worldpanel, this contract is due to expire and therefore we are going back out to tender. HDB core Foodservice data requirements 1. The basic measures required will consist of the following as a minimum: • Spend • Servings/packs • Price • Buyer numbers i.e. penetration • Servings/packs per buyer i.e. frequency and volume per trip 2. Data must be split by method including the following as a minimum: • Dine out - Eating in or on the go • Takeaways – Collected or delivered 3. Data must be split by channel (we are open to agencies proposing different channel coding approaches): • Quick service retail e.g. coffee shops, fast food, cafes, bakery/sandwiches • Full service restaurants e.g. restaurants, diners • Pubs and bars • Contract catering e.g. workplace canteens, hospitals, schools etc • Travel & leisure e.g. train, ferries, events etc • Multiples including forecourts e.g. supermarkets, convenience stores etc 4. Data must be split by product type/meal, with the protein identifiable (beef, lamb, pork, chicken, fish, vegetarian, vegan) and key cuts (e.g. steaks, burgers, roasting joints, sausages etc) specified or obvious. Please detail robustness of these in your proposal. A read of meat-free/alternatives is also beneficial. Please detail dish and protein coding in proposal in detail. 5. Data must be able to be split by day part and demographics to help analysis 6. It would be beneficial for data to be split by operator for volume estimate purposes (see below) – please detail if possible 7. Our standard requirement is quarterly data delivery but we are asking for the costs for bi-annual as well. The proposal should also provide guidelines as to the lead time for data delivery following the end of the data period. 8. We require access to 52, 24 and 12 week endings as a minimum, in addition the ability to run and export historic trends (2 years minimum). 4 week ending data is beneficial to look at custom events such as Christmas and please indicate if bespoke time periods can be created if required on an ad-hoc basis. 9. AHDB require 2 years of back data as a minimum. 10. We require an online platform to access results with the ability to manipulate, create custom tables and export data to PowerPoint and Excel. Training and technical support/help for all users is required on the use of all software programmes and is expected to be inclusive in data costs as standard. AHDB would prefer for the category definitions used in reporting to be available on the tool, for example the ability to see ‘total beef’ which would capture relevant dishes. Please be clear in your response as to what categories and measures will be available on the online platform/software versus other methods. 11. Compatibility with current datasets - To evaluate compatibility with current datasets, tenderers should provide their L52 w/e data in the following areas. Measures listed (Items and occasions/servings) are for indication only, suppliers should provide their standard measure(s). All information relevant to this opportunity can be found on the Central Digital Platform and Atamis eSourcing portal via the link https://defra-family.force.com/s/Welcome Closing date is NOON 11th August 2025.

Katy Reed

Published 2 weeks ago
Open

2024-747 Meat Foodservice Data requirements

AHDB currently source GB Foodservice data, quarterly, through Kantar Worldpanel, this contract is due to expire and therefore we are going back out to tender. HDB core Foodservice data requirements 1. The basic measures required will consist of the following as a minimum: • Spend • Servings/packs • Price • Buyer numbers i.e. penetration • Servings/packs per buyer i.e. frequency and volume per trip 2. Data must be split by method including the following as a minimum: • Dine out - Eating in or on the go • Takeaways – Collected or delivered 3. Data must be split by channel (we are open to agencies proposing different channel coding approaches): • Quick service retail e.g. coffee shops, fast food, cafes, bakery/sandwiches • Full service restaurants e.g. restaurants, diners • Pubs and bars • Contract catering e.g. workplace canteens, hospitals, schools etc • Travel & leisure e.g. train, ferries, events etc • Multiples including forecourts e.g. supermarkets, convenience stores etc 4. Data must be split by product type/meal, with the protein identifiable (beef, lamb, pork, chicken, fish, vegetarian, vegan) and key cuts (e.g. steaks, burgers, roasting joints, sausages etc) specified or obvious. Please detail robustness of these in your proposal. A read of meat-free/alternatives is also beneficial. Please detail dish and protein coding in proposal in detail. 5. Data must be able to be split by day part and demographics to help analysis 6. It would be beneficial for data to be split by operator for volume estimate purposes (see below) – please detail if possible 7. Our standard requirement is quarterly data delivery but we are asking for the costs for bi-annual as well. The proposal should also provide guidelines as to the lead time for data delivery following the end of the data period. 8. We require access to 52, 24 and 12 week endings as a minimum, in addition the ability to run and export historic trends (2 years minimum). 4 week ending data is beneficial to look at custom events such as Christmas and please indicate if bespoke time periods can be created if required on an ad-hoc basis. 9. AHDB require 2 years of back data as a minimum. 10. We require an online platform to access results with the ability to manipulate, create custom tables and export data to PowerPoint and Excel. Training and technical support/help for all users is required on the use of all software programmes and is expected to be inclusive in data costs as standard. AHDB would prefer for the category definitions used in reporting to be available on the tool, for example the ability to see ‘total beef’ which would capture relevant dishes. Please be clear in your response as to what categories and measures will be available on the online platform/software versus other methods. 11. Compatibility with current datasets - To evaluate compatibility with current datasets, tenderers should provide their L52 w/e data in the following areas. Measures listed (Items and occasions/servings) are for indication only, suppliers should provide their standard measure(s). All information relevant to this opportunity can be found on the Central Digital Platform and Atamis eSourcing portal via the link https://defra-family.force.com/s/Welcome Closing date is NOON 11th August 2025.

Katy Reed

Published 2 weeks ago

AI Bid Assistant

Our AI-powered tool to help you create winning bids is coming soon!

View Contract Source Save Contract

Timeline complete

Publish
Bid
Evaluate
Award
Complete