DVSA (Driver & Vehicle Standards Agency)

DVSA MOT Service Data Quality and Migration (Revised Requirement)

Incomplete applications

Incomplete applications

Completed applications

Completed applications
14 SME, 4 large
Important dates
Opportunity attribute name Opportunity attribute value
Published Monday 23 May 2016
Deadline for asking questions Monday 30 May 2016 at 11:59pm GMT
Closing date for applications Monday 6 June 2016 at 11:59pm GMT


Opportunity attribute name Opportunity attribute value
Summary of the work DVSA require an experienced, specialist, multi-discipline Agile delivery capability to deliver data quality improvement outcomes for the MOT service, in line with DbD principles and a DevOps culture, supporting a successful Live DbD assessment outcome in Q1 2017 and successful integration and alignment with other agencies e.g. DVLA.
Latest start date 01/09/2016
Expected contract length We expect this engagement to run for between 6 and 9 months from start.
Location East Midlands
Organisation the work is for DVSA (Driver & Vehicle Standards Agency)
Budget range

About the work

About the work
Opportunity attribute name Opportunity attribute value
Why the work is being done The DVSA MOT Service supports high quality MOT testing for 30m MOT tests a year across 22,500 approved garages. It supports the managers of garages and their testers in achieving the right quality. It supports motorists in receiving a consistent MOT service and accessing MOT related data. It makes data available openly to users who provide further services to motorists. It supports DVSA in supervising and supporting garages - providing authorisation of businesses, premises, managers and testers and for enforcement activities. Data is also made available to other government users - notably to DVLA to support vehicle excise duty transactions.
Problem to be solved A specialist team is required to work on data quality improvement work for the DVSA MOT Service. MOT data is broadly grouped into Core, Vehicle and MOT Test data. Data was migrated from the legacy MOT 1 service that was retired in late September 2015. The migration work is largely complete (there is some remaining work, dependent on application improvements and additional features to use this data) but DVSA require ongoing work to improve quality of data within the service, and to align the data with other agencies (notably DVLA).
Who the users are and what they need to do (some examples) As an MOT tester: - I want to have assurance that only I can log a test against my details, to ensure that ‘dodgy’ MOTs cannot be logged against me As DVSA: - I want information presented to me that enables risk to be managed As an MOT garage manager: - I want my opportunity to do things wrong to be minimised – so I don’t get into trouble As a motorist: - I want to know when my MOT is due so I don’t get into trouble and so I know my vehicle is safe.
Early market engagement Nil.
Any work that’s already been done The service has passed both Alpha and Beta DbD assessments, and is preparing for a Live assessment. The service has a backlog. Work is progressing well across several workstreams, including: - service improvement (functional and non functional improvement work based on researched user need and insights from data) - Database re-architecting (to reduce tech debt) - API re-architecting (to reduce tech debt) - Data migration (migrating remaining legacy data, remediating data related defects and cleansing legacy data).
Existing team There is a mix of existing vendors including Kainos, BJSS and Valtech. Our delivery capability is based on multi-discipline, multi-vendor teams operating in accordance with DbD principles and a DevOps culture (i.e. able to output working software with every sprint). Our organisation is broadly aligned around several key workstreams: - application improvement - re-architecting key components (database and API) - web operations improvements.
Current phase Beta

Work setup

Work setup
Opportunity attribute name Opportunity attribute value
Address where the work will take place DVSA, The Axis, Upper Parliament Street, Nottingham, NG16LP. It is also possible that work may be required in other DVSA locations, and occasional attendance to other offices is expected to meet delivery requirements.
Working arrangements We expect a full time engagement from delivery teams to meet the required outcomes. We expect this to be a full time, 5 day per week basis (Monday to Friday). There is some scope for remote working (e.g. 4 days per week on-site, 1 day remote), however we value co-located, integrated teams and face to face dialogue in the spirit of the service standard.
Security clearance Basic

Additional information

Additional information
Opportunity attribute name Opportunity attribute value
Additional terms and conditions Standard framework and call off Ts and Cs. Expenses as per DfT T&S Policy.

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 successfully delivering complex, high transaction volume data migration projects involving legacy to cloud migration (>20million transactions p/a) (2%)
  • Have experience of working in blended, multi-discipline, multi-vendor team environments focused on meeting user needs using agile methodologies and delivering data quality improvement outcomes (1%)
  • Have significant experience of successful solution design and delivery for data migration and transformation work, including scripting, ETL, testing and data mapping (1%)
  • Have experience of working across a full lifecycle from concept to delivery for data migration and data quality improvement work (1%)
  • Have experience of working with Talend software (1%)
Nice-to-have skills and experience
  • Have experience of working with DfT Agency data sets (notably DVLA and DVSA) (1%)
  • Have experience of working on digital by default government services with high transaction volumes (>20million p/a) and meeting digital by default service standard criteria (1%)
  • Have experience of working with multiple cloud vendor technologies and tools (including AWS and Skyscape) (1%)
  • Have experience of evaluating data migration and profiling tools and delivering recommendations to support data related business transformation (1%)

How suppliers will be evaluated

How suppliers will be evaluated
Opportunity attribute name Opportunity attribute value
How many suppliers to evaluate 3
Proposal criteria
  • proposed approach and methodology - 10%
  • proposed team structure (including CVs of key members) - 10%
  • value for money justification - 10%
  • similar contract examples, case studies and references - 10%
  • On-site (Nottingham) presentation of above (1hr) - 10%
  • Team scalability, flexibility, deployment time, and pause capability - 10%
Cultural fit criteria Proposed approach for working with co-located, multi-vendor DVSA team - 10%
Payment approach Time and materials
Assessment methods
  • Written proposal
  • Case study
  • Reference
  • Presentation
Evaluation weighting

Technical competence


Cultural fit




Questions asked by suppliers

Questions asked by suppliers
Supplier question Buyer answer
1. Important Announcement: See Adjacent Comments. This requirement replaces a previous entry on the marketplace entitled "DVSA MOT Service Data Quality and Migration". That requirement is no longer valid and is replaced by this one. The difference is that the weightings and shortlist criteria have been revised after internal consultation with stakeholders and Crown Commercial Service.
2. 1. Are you able to advise of the dates/timescales for further evaluation and contract award? This will enable us to set the earliest possible start date for our team. As stated, the latest start date is 1st September. This will give DVSA enough time to carry out evaluation and contract award including internal governance processes. There are variables such as how many applications we receive that may influence the evaluation window, so it is difficult for us to say exactly when we will be in a position to announce award of contract. We will try and publish a timetable when we send out the proposal template after the shortlisting process.
3. The application asks: When can the supplier start work? Are we able to put a narrative in this field, rather than just a date? DVSA are not in a position to comment on the application process template as we have not seen or used it. Your question is better directed to enquiries@digitalmarketplace.service.gov.uk
4. We have three questions for this opportunity. 1)What is meant by "basic" SC? Would this be BPSS? 2) In the revised requirement, the technical competence essential skills and nice-to-have skills now have individual weightings of either 1% or 2%. Does this now mean that these elements will be scored separately from the remainder of the proposal criteria, such as proposed approach and methodology, proposed team structure etc., each of which carry 10%? It was our original understanding that these would be themes throughout the proposal and not scored in isolation. 1 & 2 Yes, BPSS. 3. When you submit your application, we review which applicants have met the Essentials and Nice To Haves in isolation in order to arrive at a shortlist of suppliers that we invite to the full evaluation which includes other technical criteria such as methodology etc. The overall technical evaluation weighting includes the essential and nice to haves scores carried forward from the shortlisting stage and so these need to be weighted as well and form part of the overall 70% technical weighting.
5. What is meant by a "pause" capability? Would this involve one or more members of the team temporarily suspending chargeable work at the request of DVSA for an unspecified length of time? If so, how likely is this scenario? How frequently and for how long might this occur? At this time we think there may be a need to stop some or all of the Discovery Activity when the first Discovery (Commercial Vehicles) ends and before the second Discovery (Drivers) starts. If we do this - it is likely to be a 'Pause' in activity for 1 week. No or little chargeable work would be necessary if we did invoke the 1 week 'Pause'. DVSA want the flexibility to Pause or not. It is likely to just be that one time between Discoveries, and we will only to be able to make a final judgement nearer the time.