We shared in December that we're aiming to Go Live for MIAFTR users in Q4 2025.
We’re aiming for late October/early November and we’re taking into account school holidays which we know impacts teams.
But we want to be as certain as we possibly can be before we announce the date that it's deliverable and achievable by ALL our stakeholders.
Yes – the video will be shared in the new MIAFTR training section of our microsite and you can share the link internally. The link's here
We’ll let you know as soon as we possibly can and understand the impacts on you. We're already putting that into practice. For example, we consulted with customers to confirm that they can achieve timeframes for adopting the data submission methods we’ll support at launch.
The Motor Insurance Anti-Fraud and Theft Register (MIAFTR) is one of the MIB’s core data services alongside Navigate (formerly MID) and CUE. It houses c.10m records of loss events (claims) related to vehicles. The Motor Insurers' Bureau (MIB) is the data controller for MIAFTR data that is currently hosted by our technology partner, Solera.
MIAFTR was established in 1987 by the insurance industry as a way of sharing data to better identify and tackle fraud.
No. The public only interacts with the data through third party organisations that charge for checking a vehicle’s history, also called a provenance check.
MIAFTR was designed and developed to help monitor vehicles written off for insurance purposes, to help trace and recover stolen vehicles and to help detect fraud.
Navigate is a modern, cloud platform hosted in Microsoft Azure offering a unified portal for all enquiries on two core MIB data services, MID and MIAFTR.
It provides self-serve capability, enhanced reporting and insight delivery. It also drives data ingestion improvements and better fraud detection.
Having data in one place means we can continue to drive data quality improvements.
Following an industry consultation, we’re transforming our data services in a phased approach. In 2022, we set up our Navigate programme to replatform MID and MIAFTR, with the potential to host other data services in the future.
Replatforming MIAFTR during Phase 2 continues with the aim of replacing our aging technology and giving our customers what they need.
We’ve taken the time over the last couple of months to carry out a deep dive to ensure we learned lessons from the Navigate launch
Over the course of the last year, we've more than doubled the size of the programme team and restructured the way we work
We’ve also increased programme controls and governance
We’re working more closely with customers on the design and onboarding approach.
We’ve invested in our engagement team - all customers will have dedicated Engagement Leads to support them every step of the way.
All active MIAFTR portal users will be migrated onto Navigate and users with approved email domains will be sent an email with an activation link prior to Go-Live so they can set up two-factor authentication to be able to log in on Navigate from day 1.
If the user is already using Navigate, their access will be updated to include access to Vehicle Salvage & Theft Data within Navigate.
Our dedicated Engagement Team will support you through all the readiness steps you and your team will need to complete before Go-Live. Those readiness steps include:
Signing a legal agreement (if your organisation is required to do so – see our Legal FAQs for more about this)
Keeping informed about the changes that might impact your organisation by reading our monthly newsletter and email updates, using this microsite, and attending our regular informative webinars.
Carrying out testing for the methods that you use to interact with MIAFTR e.g. API and/or Portal.
Sharing training materials with your internal teams which will include user guides and demos.
When MIAFTR data goes live in Navigate in Q4 2025. After this you will need to find an alternative source for this information.
The layout of MIAFTR functions within Navigate will be familiar to MIAFTR users. However, Navigate is more intuitive and has a refreshed, more modern look and feel.
We'll be working closely with all our Data Recipient customers as the set ups are more bespoke, so timescales for things such as Legal Acceptance and Testing may differ slightly.
It is important to note whilst we refine your bespoke plans that the overall Go Live timeframe still applies to you.
API Testing will start from Q1 2025 & Portal Testing will start from Q2 2025. We're refining the approach and will share more information in early 2025.
Yes, if you have access to the portal today as an enquirer or data submitter you will be asked to test the platform. You will be asked to sign-off the successful completion of testing.
We’ll use a range of methods, including demos, training guides and virtual events.
As with Phase 1 when we replatformed the MID. we’ll share everything you need to get started on the Training Page of this microsite closer to Go Live.
We'll keep you regularly updated about progress throughout Go-Live weekend through via email, the microsite and our Engagement Leads.
A detailed migration plan and Go-Live itinerary will be shared with you in 2025.
Roll back plans will be prepared and shared closer to Go-Live.
Data from the legacy MID and MIAFTR databases will be hosted on the same new platform, Navigate.
Migrating the MIAFTR dataset onto Navigate does imply a risk to the performance of the platform. With that in mind, we're planning to conduct robust load testing, to assure ourselves that any performance impacts are mitigated, before we Go lLve. After launch, we will closely monitor service performance.
Please contact our engagement team at engagement@mib.org.uk to discuss available options.
No, MIB will not be building and providing an alternative CRU service in the next 12 months. CRIF is a commercial provider of CUE-CRU service as an alternative to Experian. MIB we will consider the CRU component of the CUE service as part of our wider future strategy.
We’ll be working with customers more closely during testing in smaller groups. We’ll share information with you directly on our support approach in the coming months.
Drop us an email at engagement@mib.org.uk and one of the team will be in touch.
We conducted a full lessons learned exercise at the end of Phase 1. We’ve made a significant number of changes, and we’re continuing to look at how we can further improve.
Over the last 12 months, we’ve more than doubled the size of the team. You can read more about our lessons learned review here.
We have a dedicated Navigate team working on service issues and development. We’ll continue to inform our former MID users now using Navigate of any updates or changes. This will be through targeted emails, notifications and via your dedicated Customer Relationship Manager.
Yes, we strongly encourage, and will be supporting, cross-platform testing for all API customers. We’ll be providing more information on this in the coming weeks along with recommended test scenarios, and information on how to obtain credentials for the Navigate portal test environment.
Delegated Authorities (DAs) who only supply data (and enquire) on behalf of insurers who have already signed up to the Navigate legal agreement will not need to sign a legal agreement.
However,DA organisations who only enquireon behalf of organisationswill need to sign a legal agreement, so if you haven’treceived a link to DocuSign, please contact engagement@mib.org.uk.
Other organisations working independently who enquire on MIAFTR datawill also need to sign a legal agreement so if this applies to you, please do reach out.
All types of claims that are currently entered on MIAFTR will be able to be entered onto Navigate. If you are referring to something specific, please reach out to us at engagement@mib.org.uk to clarify.
We've been working closely with our API customers with regards to build requirements. If this question relates to Robotics, please contact engagement@mib.org.ukand a member of the team will be in touch.
During the development of the Navigate MIAFTR product, we analysed existing claims data to understand the expected performance needs and set appropriate thresholds. This analysis considered factors like the maximum number of vehicles, the maximum number of versions, and the maximum number of matches found against live claims.
We have used this data to rigorously test and refine Navigate to make sure it meets our performance expectations. Based on this, the timeout bugs you currently experience will be prevented from occurring.
You'll access MIAFTR data (re-named to Vehicle Salvage & Theft Data) via the Navigate portal. Apart from how you log in to the new platform and a new look and feel, not much is changing to the functionality of accessing that data.
You can watch our demo video which gives you an idea of the Navigate portal functionality. We're open to any input that would make accessing MIAFTR data in Navigate easier for all our customers, but any enhancements will be considered as part of our future, Day 2 development.
...