Driver and Vehicle Standards Agency (DVSA)

Creation of a centralised data integration platform - Date Extension

Incomplete applications

7
Incomplete applications
2 SME, 5 large

Completed application

1
Completed application
1 SME, 0 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Tuesday 13 August 2019
Deadline for asking questions Tuesday 20 August 2019 at 11:59pm GMT
Closing date for applications Tuesday 27 August 2019 at 11:59pm GMT

Overview

Overview
Opportunity attribute name Opportunity attribute value
Summary of the work **REPUBLISHED DUE TO ISSUES RELATING TO RESPONDING TO PUBLISHED QUESTIONS**

This project is to create a central data ecosystem for the DVSA, and set up the system integrations that are predefined (confirmed prior to project kick off). This will not include security consultancy as that is being handled separately.
Latest start date Monday 16 September 2019
Expected contract length 3 to 4 months in this initial phase
Location East Midlands
Organisation the work is for Driver and Vehicle Standards Agency (DVSA)
Budget range The limit on this part of the project is £200k, which does not include licensing or infrastructure charges, as they are already covered. This is only for the standing up of the environment and creation of integrations.

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done We are moving away from our current approach to decentralised management of data and data assets. This piece of work will be focused on creating a centralised data ecosystem, specifically building integration between internal systems and ensuring that data quality is maintained across all pipelines.
Problem to be solved Currently our data is in silos, and this work will enable us to move to a centralised data ecosystem that can be used by all projects and services across the DVSA. Using Informatica and AWS we will begin to work on a Master Data Management (MDM) approach, with specific focus on data quality.
Who the users are and what they need to do As a developer I need to access data in a central data ecosystem so that I can ensure that I am accessing data that is the same as that used across the organisation.
As a CRM developer I need to be able to access and share data with other applications across the DVSA so that we can improve our interaction with our end users.
As a Data Scientist I need to access data that is of high enough quality to produce meaningful output.
Early market engagement We have been working with AWS and Informatica to come up with the best theoretical approach to this problem.
Any work that’s already been done We have defined a target architecture and high level design for the data environment. Research between projects has been undertaken and all potential issues have been resolved. This project will be the setup of an environment in accordance with our well defined requirements.
Existing team Our existing team is small, and consists of a Head of Data, Data Architect, Data Business Analyst, Project Manager and a small team of MI Analysts and Data Scientists.
Current phase Alpha

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place The work will predominantly be undertaken in the Nottingham offices of the DVSA, although there will be a need for the successful team to work in Bristol and Swansea as and when the project dictates.
Working arrangements We will have daily stand ups, and our internal PM will act as the Scrum Master. All travel and accommodation should be covered within the quote.

There will be at least 4 days on site each week given the nature of the project and the data and system access that will be required.
Security clearance SC will be required by all of the team that come in.

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions Standard terms and conditions apply.

Skills and experience

Buyers will use the essential and nice-to-have skills and experience to help them evaluate suppliers’ technical competence.

Skills and experience
Opportunity attribute name Opportunity attribute value
Essential skills and experience
  • have experience of integrating a data platform using Informatica
  • have experience of building connectors between systems using Informatica
  • have experience of creating API's and working with API Gateways
  • have experience of building data models within AWS (Aurora / Redshift)
  • have experience of working with Informatica DQ (Data Quality) / ETL
  • have experience of setting up and building Informatica MDM (Master Data Management)
  • have experience of building connections between Dynamo DB and informatica
  • have experience of working within an Agile environment
Nice-to-have skills and experience
  • prove that they have delivered ecosystems like the one in our plans
  • prove they have integrated Informatica within AWS previously
  • show previous approaches to building fully functional / operational data models

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 5
Proposal criteria
  • How close the timelines are to our requirements
  • How well their plan fits in with our overall strategy
  • How well they have displayed they know the technologies at play
  • Who they propose will carry out the work
  • How well defined the sprint planning is
Cultural fit criteria
  • be able to blend into the internal DVSA data team
  • be prepared to assist DVSA team members where their skill set isn't as well developed as the external supplier
  • ensure that delivery updates are honest, allowing transparency throughout the DVSA
  • be able to provide technical guidance when it doesn't exist internally
Payment approach Capped time and materials
Assessment methods Written proposal
Evaluation weighting

Technical competence

75%

Cultural fit

5%

Price

20%

Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Can you confirm whether all team members need to have full Security Clearance? We would like to use some offshore resources who have completed full background checks however will not have security clearance. We have had issues with SC for offshore teams, so this will need to be UK based and SC should be handled in advance of the project commencing by the supplier.
2. The selection criteria suggests that you will choose a supplier based on a number of elements including meeting timelines, cultural fit, team members – however nowhere in the responses can we add this information. Is there a section missing or will this information be provided at a later stage? These questions will be answered once we are down to creating the shortlist of suppliers. We will assume that all applications believe they are a good fit across all three elements mentioned above.
3. Please can you confirm the Security Clearance requirement – will you expect people to be holding current SC level security clearance at present, or will you potentially sponsor clearance applications for people with suitable backgrounds and/or lapsed clearance. Thank you. SC must be up to date / current. We will not be supporting SC process in any way.
4. For organisations applying for the 'Creation of Data Models and Output with AWS' based at Swansea, this is also an opportunity of interest. Would there be any scope for this to run primarily from Swansea? Delivery is the important part here and as long as the team is UK based there is some flexibility in location. Swansea may not be the perfect place, as the projects that we are initially supporting are Nottingham / Birmingham based.
5. Can you confirm that the detailed design phase has already completed with an approved design which can be utilised for construction or that it will be complete prior to the construction phase? Design phase is in progress and we will have the relevant designs agreed and in place prior to the construction phase.
6. Are you able to provide further details on the number and types of different data sources that will be included within the ecosystem? This will be like most integrations, with 3 or 4 data types and potentially 9 or 10 different data sources. There will be some systems that need to be tightly coupled and the systems that have a smaller data output that will simply need API config or maybe even an ODBC link between them.
7. In the "Nice to Have Skills and Experience" section you have asked for proof from suppliers that they have delivered ecosystems like the one in your plans. Would it be possible to share further detail on your plans? (E.g. the target architecture and high level design mentioned in the "Any work that's already been done" section). There will not be any plans released in advance. The important part is the work with Informatica and AWS and the proven ability of building a working ecosystem using these platforms / infrastructure. We are building an integration layer between source data systems and trying to ensure the use of consistent data across all systems, using an MDM hub.
The deadline for asking questions about this opportunity was Tuesday 20 August 2019.