Department for Transport - Data Delivery Partner

Description

Terms and acronyms GCP = Google Cloud Platform SOW = Statement of Work DAP = Data Action Plan Summary of the work: DfT requires a data delivery partner to support the central data team with GCP-based technical delivery and wider Chief Data Officer priorities. Work will be commissioned through individual SOWs, aligned to team business plans, internal governance, technical processes, GDS standards and accessibility requirements. Pricing model: Capped time and materials Provide further information: Other charging mechanisms may be used subject to agreement by both parties. Confirm if you require a contracted out service or supply of resource: Contracted out service: the off-payroll rules do not apply Organisation the work is for: The Department for Transport (DfT) works alongside our agencies and partners to support the transport network. DfT champions data and technology to drive the integrated, innovative and accessible transport system of the future. Latest start date: 2026-12-14 Expected contract length: 5-00-00 Expected contract structure: 3+1+1 Estimated contract value (excl VAT): 8000000 Budget details: DfT does not commit to spend the full contract value. Why the work is being done: The work is being done to support the growing demand for high-quality data both within the department and the wider sector. The work of the central data team support and range of activities across that provide data support across the department, ALBs and wider transport sector. This includes the delivery of the actions in the transport Data Action Plan (DAP) with an increased focus on how we can further support local authorities and transport organisations with greater devolution of the transport sector. This technical data work sits alongside research to support the DAP and our ambitious AI programme. The work is being specified as individual SOWs to ensure we align to the current priorities for government and to make the most of technology in a complex and evolving landscape. Problem to be solved: Following on from the transport DAP we are looking to deliver improved capacity and maturity of data projects across the DfT and greater collaboration across the wider sector. With a focus on both enhanced governance and communication while continuing to innovate as new technology is developed. This contract is design to compliment some of the research being undertaken for the action plan and the AI Delivery, Development, Research and Evaluation Support contract. This contract is designed to allow us to move quickly when new areas of work are identified and to support data projects across the wider DfT. Who the users are and what they need to do: The contract is to support analysts, engineers and data specialists in continuing to improve and modernise our internal data landscape. This is to support policy development, analysis and enhanced use of Google Cloud technology to meet our commitments in the transport Data Action Plan. Preliminary market engagement: A pre-market engagement call took place on 26th August. The slides and Q&A document are attached. Work done so far: We have existing data maturity assessments and governance but these need to evolve in light of changes in technology and the increased importance of data in the wider transport landscape. We have already undertaken a discovery on APIs for DfT which can be found here: Developing application programming interfaces at DfT - GOV.UK Following this, work has begun on building an API developer portal in Apigee to host and share the first wave of DfT APIs. Existing team: The existing central data team sits with the Chief Data Office in the Analysis Directorate. The central data team (D:ETLA) is around 20 experts covering: data engineering, data policy (inc. governance, maturity and standards), data transformation (delivering on the data action plan) and a crisis data function. We sit alongside the advanced analytics team who lead our internal AI programme and data science functions and the central stats team who has responsibility for our geospatial data strategy. We work alongside colleagues in our digital service function on a range of technical projects using GCP. Incumbent supplier: No Working arrangements: We expect the supplier to work in a blended way alongside the DfT team to deliver the priorities. With suppliers providing the project management and overseeing the day-to-day delivery for the work. We expect the governance model for each project to be agreed as part of the SoW and that technical projects to be delivered in an agile way. Where possible we expect the lead for each project to engage face to face at least once a month with the DfT lead. We have staff based in London, Birmingham, Leeds and Hastings. We expect invoices on a monthly basis to manage the spend against the fixed price contracts. We request suppliers to model the behaviours expected of the civil service and work in an inclusive way with the DfT teams. Security clearance: Security Check (SC) Additional information on security clearance: We expect any suppliers doing technical work in our GCP environment or with access to the DfT systems (including SharePoint) to hold a minimum of SC clearance. For those undertaking more general data management work that does not require access to our GCP environment then BPSS is sufficient.