For the very latest updates on Navigate please see our Navigate Go Live page
Below is a full log of the updates we've shared since Navigate launched on 30 April.
Friday 28 June
Fixes to address the three issues listed in yesterday’s update were successfully deployed overnight. We’ll continue to monitor these.
Your next update will be Monday 1 July.
-----
Thursday 27 June
Here’s your latest Navigate update.
Standard File Transfer Processing (SFTP)- notification of scheduled downtime Saturday 29 June 10-11am.
Please ensure the team responsible for submitting your batch files to Navigate are made aware of the following -
SFTP processing will be temporarily paused between 10:00 and 11:00 on Saturday 29 June, while we carry out an important upgrade.
Users will still be able to access their SFTP account and submit files however the files will go on hold until the upgrade is completed.
No change or action is required by users and SSH keys currently installed will continue to allow access after the upgrade.
This work is required to improve our reporting capabilities.
We apologise for any inconvenience this may cause.
Reminder to customers and policyholders about correct submission format using the Standard File Format CSV Template (Macro Free version)
Shortly after Go Live, we provided customers with a non-macro template for those who were unable to use the macro enabled sheet.
As there are no macros, the leading zeros in any numerical field e.g. Supplier ID, Policy Number and Date are automatically being removed. If this is not corrected, the file of data will experience errors when it is uploaded as it will not be accurate.
To avoid this happening, users must ensure any numerical field is in the correct “text” format type with any leading zeros maintained e.g. 001 instead of 1 before saving and uploading the file to the Portal.
When completing the template also ensure that ‘empty’ columns of data do not have spaces in them, as this will cause the file to fail processing and cause errors.
It can be difficult to spot these, the simplest way to remove any is to highlight the cells and press delete to remove any spaces as shown below.
If you are able please use the macro enabled version of the CSV template.
Please find the links below:
Standard File Format CSV File Template (Macro Free version)
Policyholder Standard File Transfer User Guide (Attended File Transfer)
The macro enabled template can be accessed in Navigate on the Vehicle Update page.
See the training page of our microsite for these and other useful Navigate guides and resources.
Tonight’s scheduled fixes
Tonight (Thurs), after hours, we’ll deploy several scheduled fixes for the following issues:
1. Some users reported issues with fleet and commercial vehicle off cover dates vehicle showing incorrectly i.e where applicable they do not match the policy expiry date. The functionality has been fixed previously and tonight we’ll apply a data fix for the vehicles affected.
2. Some users have reported issues with fleet and commercial policies in the update vehicle tab not appearing correctly. Previous policy dates appear as current, and future policy dates appear as current.
3. Two further fixes for the E023 ‘PARTY POLICY CONTROL COUNT OUT OF SEQUENCE’ error.
- When a batch file has two records for the same policy number i.e. 9 and 10, if PPCC 10 has an error (not E023), PPCC 9 is also rejected with an E023 error.
- Some results files are being issued with an incorrect expected PPCC i.e. 00001.
Reporting
Last week we advised the standard PPCC and FR48 reports would be issued today.
We have now placed in your Navigate SFTP accounts the PPCC report for personal data and the FR48 report for Fleet/Commercial data.
These reports have the same file names as in the legacy MID and can be found in the “From_xpn” folder of your SFTP account.
---
Tuesday 25 June
Here's your latest Navigate update.
Scheduled fixes
Last night's (Monday) fix for when a Policyholder name containing a comma causes a misalignment in the download vehicle schedule was deployed successfully.
---
Monday 24 June
Here’s your latest Navigate update.
Scheduled fixes
Tonight (Monday), after hours, we’re deploying a fix for when a Policyholder name contains a comma causing a misalignment in the download vehicle schedule.
Thursday’s fix for erroneous E023 error
The fix deployed Thursday evening to resolve the erroneous E023 error caused when a policy was deleted from inception, any resubmitted records can be submitted with a PPCC from 0000 to 9999, was successful.
We understand there are other scenarios also erroneously generating E023, which we continue to work through. We’ll update you when we have further information.
----
Friday 21 June Update
MIAFTR delivery timeframes
We've previously shared that we were aiming to welcome MIAFTR users into Navigate in September 2024.
However, given our focus on resolving post-launch issues following the MID's transition into Navigate, it's clear that we need to carefully re-evaluate the MIAFTR delivery timeline, to ensure it's realistic and deliverable for all stakeholders.
Our ‘fix forward’ approach is making good progress. We’re also capturing the ‘lessons learnt’ from recent weeks and carefully considering these in our planning for MIAFTR transition into Navigate.
We also recognise that customers need sufficient time to prepare. And we want to provide customers with the most effective level of support ahead of Go Live.
So, we can now confirm that MIAFTR will not be replatformed in 2024 and a revised timeline for delivery in 2025 will be developed and shared later this year following further evaluation by the MIB Board. We’ll ensure that timeline is realistic and achievable for all our MIAFTR stakeholders.
This additional time will enable us to continue this 'lessons learnt' approach and also provide additional customer engagement and support ahead of MIAFTR’s integration into Navigate.
-----
Thursday 20 June Update 2/2
Reoccurring bug - erroneous E023 error
Scenario: When a policy has been deleted from inception, any resubmitted records can be submitted with a PPCC from 0000 to 9999.
We’re deploying a fix this evening (Thursday) for the above scenario which is erroneously generating the E023 error.
We understand there are other scenarios also erroneously generating E023, which we continue to work through. We will update you shortly.
----
Thursday 20 June Update 1/2
Here's your latest Navigate update.
Reports
We had hoped to issue the FR48 and PPCC reports to all organisationstoday. However, due to some irregularities spotted in testing, we need to fix a few bugs first before we can issue these.
We now anticipate these reports being issued to relevant organisations on Thursday 27 June.
The new, monthly FR05D report will be issued on 5 July.
We apologise for the short delay and thank you for your continued patience and understanding.
-----
Monday 17 June
Here’s today’s Navigate update.
We continue to see improvements in the stability of Navigate and the efficiency of SFTP file processing.
Issues with allocating policies to a Policyholder User
Some Helpdesk users are reporting issues when trying to add policies to a Policyholder user account. After clicking submit, the page becomes unresponsive, the request is unsuccessful and the portal times out. The fix for this issue is planned for deployment this evening (Monday) after hours.
Some users have reported that duplicate vehicle records were being displayed when viewing or updating vehicles on their policy within the Portal.
The fix for this issue will be deployed this evening (Monday) after hours.
Reoccurring bug - erroneous E023 error
We plan to deploy the fix for this erroneous error on Thursday 20 June.
Our technical team is continuing to monitor additional erroneous errors and how they correlate to specific scenarios.
The error codes still being investigated are:
E088 - NO POLICY RECORD FOUND FOR VEHICLE
E089 - VEHICLE ON/OFF DATES NOT WITHIN POLICY EFFECTIVE/EXPIRY DATES.
E103 - USER ID NOT AUTHORISED
----
Friday 14 June
Thanks for your patience this week as we continued to work through some important fixes, prioritising issues with the greatest impact.
Portal Stability Improvements
Last night’s fix to improve stability for portal enquiries was successful. We're continuing to monitor portal performance.
SFTP Data Submissions: Erroneous errors
We are continuing to monitor and validate the below errors:
E023 – PARTY POLICY CONTROL COUNT OUT OF SEQUENCE (reoccurring)
E088 - NO POLICY RECORD FOUND FOR VEHICLE
E089 - VEHICLE ON/OFF DATES NOT WITHIN POLICY EFFECTIVE/EXPIRY DATES.
E103 – USER ID NOT AUTHORISED
------
Thursday 13 June
Here’s your latest Navigate update.
Thanks for your continued patience this week as we continue to work through some important fixes, prioritising issues with the greatest impact.
Portal stability improvements
A fix will be deployed this evening (Thurs), after hours, to improve stability for portal enquiries.
SFTP Data Submissions: Erroneous errors
So far, we have successfully fixed the bugs that were causing the following errors to occur erroneously:
E019 – INVALID POLICY NUMBER
E020 - INVALID VEHICLE REGISTRATION MARK FORMAT
E035 - UPDATE TYPE IS A AND EXISTING RECORD NOT FOUND
E048 - UPDATE TYPE IS N AND EXISTING RECORD FOUND
E063 – CANCELLATION/LAPSE FOR UNKNOWN VEHICLE
E068 - ATTEMPT TO CANCEL AN ALREADY CANCELLED POLICY
E078 - UPDATE TYPE ON POLICY RECORD IS N AND EXISTING RECORD FOUND
Following analysis by our technical lead, we have identified several reasons for some errors continuing to occur erroneously. These are as follows:
-
Shortly after Go live, we provided customers with a non-macro template for those who were unable to use the macro-enabled sheet. As there are no macros, the leading zeros in any numerical field e.g. Supplier ID, Policy Number and Date are automatically being removed. If this is not corrected, the file of data will experience errors when it is uploaded as it will not be accurate. To avoid this happening, users must ensure any numerical field is in the correct “text” format type with any leading zeros maintained e.g. 001 instead of 1 before saving and uploading the file to the Navigate Portal.
-
The other reason is due to the display timeout affecting larger policies in the portal. Policyholder users who are impacted may think their vehicle is not on Navigate as it isn’t being displayed so they are subsequently re-uploading which is leading to certain errors due to an existing record being found.
We are also continuing to monitor and validate the below errors:
E023 – PARTY POLICY CONTROL COUNT OUT OF SEQUENCE (reoccurring)
E088 - NO POLICY RECORD FOUND FOR VEHICLE
E089 - VEHICLE ON/OFF DATES NOT WITHIN POLICY EFFECTIVE/EXPIRY DATES.
E103 – USER ID NOT AUTHORISED
------
Tuesday, 11 June
Portal timeouts on larger policies
During pre-deployment testing, we identified that the display timeout issue occurs for policies that contain over 1000 vehicles, rather than 1700 or more.
We have identified the fix for this which is planned for deployment this evening 11 June.
SFTP Data Submission: Erroneous Errors
E063 - Cancellation/Lapse for Unknown Vehicle
E020 - Invalid Vehicle Registration Mark Format
These were both successfully deployed last night.
-----
Monday 10 June
This week we continue to prioritise issues with the greatest impact. We’re now following a twice-weekly fix deployment which will take place after-hours on Monday and Thursday evenings.
We’ll share the planned fixes beforehand via email and here on the microsite.
In case of an outage or incident, we may implement fixes outside of these deployment days. Once we transition into ‘business as usual’ we’ll review the release cycle again.
Over the weekend, we successfully implemented a fix to improve the efficiency of the Navigate data processing job.
Tonight’s fixes
Portal timeouts on larger policies
Users searching on policies that contain more than 1,700 vehicles are still experiencing timeouts and freezing. This is being fixed this evening.
SFTP Data Submission: Erroneous Errors
E063 - Cancellation/Lapse for Unknown Vehicle
E020 - Invalid Vehicle Registration Mark Format
These errors were occurring erroneously which will be corrected in tonight’s fix
We’ll post the outcome of these deployments tomorrow morning on the grey Latest Update banner above
-----
Thursday 6 June 2024
Here’s today’s Navigate update.
Thanks for your continued patience this week as we worked through some important fixes.We’ve seen some significant progress as we continue to prioritise issues with the greatest impact.
Next week, we’re moving to a more standard approach which will increase the stability of Navigate. This means we’ll be deploying fixes twice weekly on Mondays and Thursdays and our updates will align with those.
In the event of an outage or incident we may implement fixes outside of these deployment days. Once we transition into ‘business as usual’ we’ll review the release cycle again.
We’ll next update you on Monday 10 June when we’ll share what bugs are due to be fixed and confirm whether those fixes have been successful.
Data Submission: Erroneous errors
We continue to investigate the existing erroneous errors and once a root cause is identified, fixes will be implemented.
Previous fixes
So far, we have successfully corrected the following erroneous errors; E048, E019, E035 and E078.
Upcoming fixes
Over the weekend we’re making an update to the batch processing job to improve efficiency. SFTP will be unavailable between 10am and 1pm on Saturday while we implement this update. There will be no impact to any files during this time, these will be processed as normal once the job is switched back on.
We continue to investigate the reoccurrence of errors that are appearing erroneously – E023, E063, E068 & E103 and these will be fixed as soon as we have identified the root cause.
This is in conjunction with the remaining error codes that continue to appear incorrectly causing the rejection of records. These are:
-
E077: Update type on vehicle record is A and existing record not found
-
E079: Update type on vehicle record is N and existing record found
-
E088: No policy record found for vehicle
-
E089: Vehicle on/off dates not within policy effective/expiry dates
Navigate portal
We’re continuing to work through the next priorities, including a fix for the Portal timing-out for policyholders with more than 1,700 policies.
We’re aware that some Policyholders are having trouble seeing policies that they should have access to. If a Policyholder that has a small number of policies contacts you for assistance, Helpdesk users can create them as a Policyholder user and allocate their Policy in the Admin Tile.
------
Wednesday 5 June
Here’s today’s Navigate update.
Data Submission: Erroneous errors
Today we identified an additional erroneous error which was prioritised and fixed immediately. This was E028 – Policyholder Name Not Present. The fix was successfully deployed and this is being monitored.
Previous fixes implemented
The above adds to the fixes for E048, E068, E103, E019, E035 and E078 that have been successfully deployed over the last week.
Upcoming fixes
We are investigating the reoccurrence of two errors that are appearing erroneously – E023 & E063 and these will be fixed as soon as we have identified the root cause,
We also continue to investigate other error codes that are appearing incorrectly causing the rejection of records. These are:
-
E077: Update type on vehicle record is A and existing record not found
-
E079: Update type on vehicle record is N and existing record found
-
E088: No policy record found for vehicle
-
E089: Vehicle on/off dates not within policy effective/expiry dates
Option 2 – Scheduled Results files
The fix for the issues faced by customers who receive scheduled results files was successful.
This means Insurers and DAs who have scheduled results files should now be receiving them with the correct BST date format and they should be copying across into the "previous_results_files" folder.
Navigate portal
We are continuing to work through the next priorities, including a fix for the Portal timing-out for policyholders with more than 1700 policies.
Tuesday 4 June 16:00
Here’s today’s Navigate update.
Data Submission: Erroneous errors
Latest fix(es)
Last night’s fix for E048 - Update type is N and existing record found was successfully deployed.
Previous fixes implemented
The above adds to the fixes for E103, E019, E023, E063, E035 and E078 that have been deployed over the last week.
Upcoming fixes
Tonight, after hours, we’ll be fixing the cause of erroneous E068 (Attempt to cancel an already cancelled policy) errors.
We continue to investigate other error codes that are appearing incorrectly causing the rejection of records. The codes we continue to investigate a root cause for are:
-
E028: Policyholder name not present (newly added priority)
-
E077: Update type on vehicle record is A and existing record not found
-
E079: Update type on vehicle record is N and existing record found
-
E088: No policy record found for vehicle
-
E089: Vehicle on/off dates not within policy effective/expiry dates
Option 2 – Scheduled Results files
This evening, after hours,we’ll be deploying a fix for the issues faced by customers who receive scheduled results files.
This impacts Insurers and DAs who have opted for the Option 2 - scheduled results files. Results files that are sent at a specific time are being placed in the “from_xpn” folder but not subsequently being copied across into the"previous_results_files"SFTP folder. The fix will correct this to ensure they are copied into the previous folder going forward.
There is also another issue specifically affecting scheduled results files, where the time stamp is displaying as GMT – tonight’s fix will correct this to display BST.
Navigate portal
Latest fixes
On Monday, we successfully deployed fixes for the following issues:
-
Policy cover dates displaying MTA date instead of a start date– policies should now be displaying the correct start date.
-
Commercial policyholders have missing policies under Update Vehicle tab in portal- users should be able to see all policies they have access to.
We are continuing to investigate other portal bugs and will share updates when we have them.
------
Monday 3 June Update 16:00
Here’s today’s Navigate update.
Data Submission: Erroneous errors
Latest fix(es)
Last Friday’s fix of E078 Update type on policy record is N and existing record found error code was successfully deployed.
Previous fixes implemented
The above fix adds to the fixes for E103, E019, E023, E063, E035 and E078 that have been deployed over the last week.
Upcoming fixes
This evening, we’ll be deploying a fix for the E048 Update type is N and existing record found – a newly added priority.
Through customer feedback and our own rejection monitoring, we continue to investigate other error codes that might be appearing inaccurately and causing rejection of records. The codes we're currently investigating are:
- E028: Policyholder name not present (newly added priority)
- E068: Attempt to cancel an already cancelled policy(newly added priority)
- E077: Update type on vehicle record is A and existing record not found
- E079: Update type on vehicle record is N and existing record found
- E088: No policy record found for vehicle
- E089: Vehicle on/off dates not within policy effective/expiry dates
Navigate portal
Policy cover dates displaying MTA date instead of a start date [Final fix to be deployed after hours 03/06]
For Fleet and Commercial policies, when an amend record is submitted to update the policy details, the user was seeing the policy effective date of the amend record rather than the full 12-month period.
We have fixed the first batch of policies and the remainder will be updated out of hours this evening.
Commercial policyholders have missing policies under Update Vehicle tab in portal [Fix to be deployed after hours 03/06]
Due to some previously deployed fixes, an error occurred where not all policies/vehicles are being pulled back in a search in the Update Vehicle section in the portal. For example, if a user has access to 50,000 policies, when searching in vehicle, it only pulls back the first 500 and not the remaining 49,500. This fix will allow users to view all policies the user has access to.
-----
Friday 31 May Update 15:30
Here’s today’s Navigate update.
Data Submission: Erroneous errors [Fixes ongoing]
Yesterday’s fix for the E019 Invalid Policy Number error code was successfully deployed.
This evening we will be deploying a fix for the E078 Update type on policy record is N and existing record found error code.
This adds to the fixes for E103, E019, E023, E063 and E035 that have been deployed over the last 72 hours.
Through customer feedback and our own rejection monitoring, we continue to investigate other error codes that might be appearing inaccurately and causing rejection of records. The codes we are currently investigating are:
- E077: Update type on vehicle record is A and existing record not found
- E079: Update type on vehicle record is N and existing record found
- E088: No policy record found for vehicle
- E089: Vehicle on/off dates not within policy effective/expiry dates
Policy cover dates displaying MTA date instead of a start date [Fix to be deployed after hours 31/05]
For Fleet and Commercial policies, when an amend record is submitted to update the policy details, the user was seeing the policy effective date of the amend record rather than the full 12-month period.
The bug causing this has been fixed and we are deploying a data fix for policies affected by this issue, this evening.
Vehicle schedule downloads not showing correct number of vehicles [Fixed and monitoring]
When a user downloaded an on cover vehicle schedule, it was including vehicles off cover too. This is now fixed and being monitored.
---------
Thursday 30 May Update 16:45
Here’s today’s Navigate update.
Data Submission: Erroneous errors [Fixes ongoing]
This evening we will be deploying a fix for the E019 Invalid Policy Number error code. This adds to the fixes for E103, E023, E063 and E035 that have been deployed over the last 48 hours.
Through customer feedback and our own rejection monitoring, we continue to investigate other error codes that might be appearing inaccurately and causing rejection of records. The codes we are currently investigating are:
- E077: Update type on vehicle record is A and existing record not found
- E078: Update type on policy record is N and existing record found
- E079: Update type on vehicle record is N and existing record found
- E088: No policy record found for vehicle
- E089: Vehicle on/off dates not within policy effective/expiry dates
Navigate portal performance issues [Fixed and monitoring]
The portal continues to be stable following the fixes applied to Check Your Vehicle. The portal is currently seeing a peak of 85,000 events per hour, with a response-time of 2 milliseconds for most transactions.
Character limit restrictions on Insurer Name [Fixed and monitoring]
Insurers were experiencing a character limit of 40 characters for Insurer Name. This has been fixed and we are monitoring.
Navigate portal missing policies [Investigating]
Some commercial policyholders have reported missing policies under the ‘Update Vehicle’ section in the portal, subsequently leaving them unable to update records. We are investigating a root cause.
On cover vehicles not being displayed within active policies [Fixed and monitoring]
Customers, particularly those with commercial and fleet policies, could not see some vehicles within a policy despite the policy being active and the vehicles being on cover. This has been fixed and we are monitoring.
---------
Wednesday 29 May Update 16:30
Here’s your latest Navigate update, reporting progress on the priority fix lists.
Check Your Vehicle downtime [Fixed and monitoring]
We have now implemented the fix and have relaunched Check Your Vehicle. We expect this fix to remove pressure on the wider Navigate portal in the event of increased demand on the Check Your Vehicle service.
Data Submission: Erroneous errors [Fixes ongoing]
We have deployed the fixes for the following error codes:
- E103: User ID not authorised
- E023: Party policy control count out of sequence
- E063: Cancellation/lapse for unknown vehicle
- E035: Update type is A and existing record is not found
Through customer feedback and our own rejection monitoring, we continue to investigate other error codes that might be appearing inaccurately and causing rejection of records. The codes we are currently investigating are:
- E019: Invalid policy number
- E077: Update type on vehicle record is A and existing record not found
- E078: Update type on policy record is N and existing record found
- E079: Update type on vehicle record is N and existing record found
- E088: No policy record found for vehicle
- E089: Vehicle on/off dates not within policy effective/expiry dates
Data submission: Processing multiple files at the same time [Fixed and monitoring]
Some customers were experiencing intermittent processing issues when submitting multiple files at the same time (to the same second) via the portal or SFTP. This is now fixed and is being monitored.
Data submission: Processing files with the same file name [Fixed and monitoring]
Some customers were experiencing intermittent processing issues when submitting files via SFTP with the same file name. This is now fixed and is being monitored.
---------
Tuesday 28 May Update 17:30
Here’s your latest Navigate update, following a weekend of ongoing “fix forward” development. This work is based on the priority list generated following feedback from customers and issues having the widest impact.
Check Your Vehicle downtime [Fix to be deployed after hours 28/05]
Following investigation and development to resolve why increased demand on Check Your Vehicle was subsequently affecting performance on the wider Navigate platform, we have now implemented the fix and will relaunch Check Your Vehicle tomorrow (Wednesday). We expect this fix to remove pressure on the wider Navigate portal in the event of increased demand on the Check Your Vehicle service.
Navigate portal performance issues [Fixed and monitoring]
Customers have been reporting intermittent service outages for those who use Navigate portal search for vehicle updates or claim enquiries. We have identified the root cause and made improvements but will continue to monitor performance.
A search lag still exists when searching on policies that contain more than 1,700 vehicles. We are working on a fix for this and will update you as soon as this has been deployed.
Data Submission: No Results Files [Investigating]
Some customers have reported they have not received a results file. We have now re-generated these and are investigating the root cause. In the meantime if you have not received a results file please raise a ticket.
Data Submission: Erroneous errors [Fixes ongoing]
Customers have been reporting an unusual volume of error codes and rejection of files. We are currently undertaking analysis on the top 20 error codes by volume to resolve any that are being generated inaccurately. Fixes to be deployed this evening (28/5) should result in the following error codes working correctly:
E103: User ID not authorised
E023: Party policy control count out of sequence
E063: Cancellation/lapse for unknown vehicle
E035: Update type is A and existing record is not found.
-----
Friday 24 May Update 11:15
Navigate portal and APIs are currently unavailable. We're urgently investigating as a Priority 1 incident and will update you when the service is back up and running.
We apologise for this inconvenience.
--------
Thursday 23 May Update 17:00
We are urgently investigating a current issue with the Navigate Portal and API availability.
We apologise for this inconvenience and will update you with more information when we have it.
--------
Thursday 23 May Update 12:45
Navigate portal
The portal functionality that was temporarily disabled yesterday has been restored overnight. We are closely monitoring performance today and we’ll update you if any issues arise.
--------
Wednesday 22 May Update 17:45
Navigate portal
However the functions previously advised as unavailable in today’s 3pm update remain so. We’ll work on this tonight and update you again tomorrow (Thurs).
--------
Wednesday 22 May Update 15:00
Navigate portal issues update
Further to our earlier update we can confirm that we have restored the policy search function in the Update Vehicle tile for all users.
To ensure the integrity of Navigate is maintained, we have taken the difficult decision to temporarily limit some other functions.
1. For policyholders, the list of allocated policies presented by default on the Update Vehicle tile will not be shown.
They can use the Policy Search function as this has been re-enabled.
2. For helpdesk users in the Policyholder Management tile the Select/Add a Policyholder function is currently disabled. Until it’s reinstated, any changes to policyholder users cannot be actioned.
We will update you again when we have further information.
-------
Update Wednesday 22 May 2024 12:00
This morning we have had to switch off the policy search function in the update vehicle tile of the Navigate portal.
Last night we deployed a fix which regrettably caused an increased demand on capacity. This led to an impact on the Police connection to Navigate and in order to protect this vital, secure connection, we’ve had to turn this function off.
Our team continues to work on a solution and we’ll update you as soon as we have further information. We appreciate this causes an impact on commercial and fleet policyholders and we apologise to all customers.
--------
Update Tuesday 21 May
As we shared yesterday (Monday), we’re committed to working alongside customers to prioritise future improvements to Navigate.
This week we’ll share more information on how we plan to do this.
Updates will be posted here.
Please see yesterday’s update for more information on this ‘fix forward’ approach.
-------
Monday 20 May
Given our progress in resolving issues over the last week, this update will now be provided daily rather than twice daily.
SFTP: file processing
We’re delighted to share that we’ve now cleared the backlog of received files and now have no files older than 24 hours waiting to be processed into Navigate.
Navigate Portal
Fixing forward – your priorities are our priorities
As previously communicated, we have committed to ‘fix forward’ any issues encountered with Navigate post Go Live.
We’ve cleared the backlog of submitted files to ensure Navigate is up to date and can support police officers carry out their vital work to get uninsured drivers off our roads. As a result, we’re now able to focus on resolving any specific issues with Navigate that our customers want to see improved.
This week, we’ll share a list of the issues we’re working on and seek feedback on which of those are most important to customers to help the prioritisation decisions in the weeks and months ahead.
Support for Insurer/DA helpdesks
On Friday we shared further information to Insurer and DA helpdesk teams, to help them resolve issues that Commercial and Fleet policyholders may be experiencing.
We also provided the link to our enhanced Helpdesk FAQs on our microsite.
Customers are politely reminded that Commercial and Fleet Policyholders should be directed to seek support on these issues from their Navigate helpdesk team and not MIB.
Further support
You can contact one of our team at navigatesupport@mib.org.uk
We will update you again on Tuesday 21 May.
---------
Friday 17 May 16:30
Further to our wider update this morning here's your latest update.
Support for Insurer/DA helpdesks
This afternoon we’ve shared further information to Insurer and DA helpdesk teams, to help them resolve issues that Commercial and Fleet policyholders may be experiencing with Navigate.
We also provided the link to our enhanced Helpdesk FAQs on our microsite.
Customers are politely reminded that Commercial and Fleet Policyholders should be directed to seek support on these issues from their Navigate helpdesk team and not MIB.
Check Your Vehicle
Since Check Your Vehicle went live yesterday morning (Thurs) we’ve had more than 250,000 enquiries made on the service.
Check Your Vehicle replaces our valued Own Vehicle Lookup service. Members of the public can check for free whether their vehicle is showing as insured in Navigate.
Navigate Portal
As we shared earlier the restored Policy search functionality in the Vehicle Update tile of the Navigate portal is working well.
We’ll continue to monitor it and we’ll be implementing additional fixes in the coming days to further improve performance.
The CSV file upload facility continues to be available, volumes are decreasing as expected as Insurers and Commercial and Fleet policyholders increasingly use the portal search functionality.
------
Friday 17 May 12:30
Here’s your latest Navigate update.
Navigate Portal
Since we restored Policy search functionality in the Vehicle Update tile of the Navigate portal to all users yesterday, we’ve not encountered further issues.
The fix is working well and we’re continuing to monitor it. We’ll be implementing additional fixes in the coming days to further improve performance.
Over the last 24 hours we’ve seen 52,000 successful portal user logins.
The CSV file upload facility continues to be available, volumes are decreasing as expected as insurers and policyholders increasingly use the portal search functionality.
SFTP processing
We’ve made significant progress in clearing the backlog of received files this week and currently have no received filesolder than 72 hours waiting to be processed.
We’re aiming to clear more files today to close in on our target of not having any received file submissions in our backlog that are older than 24 hours.
We appreciate customers’ patience as we’ve reduced the backlog this week and want to assure customers again that processing outstanding data into Navigate remains a key priority.
While we work to get Navigate data fully up-to-date we continue to offer additional support our police partners.
Our Police Helpline call centre will be open again on both Saturday and Sunday this weekend (18/19 May) to assist officers at the roadside with Navigate queries.
Support for Insurer/DA helpdesks
Although we published a set of Helpdesk FAQs on our microsite shortly after Go Live we want to provide additional support for Insurer and DA helpdesk teams.
We’ll share further information and guidance later today via email which helpdesk teams may find useful in resolving issues their policyholders are having.
Customers are politely reminded that Commercial and Fleet Policyholders should seek support on these issues from their Navigate helpdesk team and not MIB.
Further support
You can contact one of our team at navigatesupport@mib.org.uk
We will update you again later.
-----
Update Thursday 16 May 15:45
Navigate Portal
After further testing today we remain confident that the fix to restore Policy search in the Vehicle Update tile of the Navigate portal is working well.
This functionality can now be used by all users.
We’ll make additional fixes over the coming days to further improve performance.
Over the last few hours we’ve seen up to 15,000 users an hour successfully using the Portal.
Check Your Vehicle
As reported earlier today, our new Check Your Vehicle service is now live. Since 9am we’ve seen more than 50,000 searches made.
Check Your Vehicle replaces our valued Own Vehicle Lookup service and offers members of the public the ability to check if their vehicle is showing as insured in Navigate for free.
SFTP
We continue to work with customers to help process their outstanding files. We’re making good progress and want to assure all customers that processing this data into Navigate continues to be a key priority.
We thank those affected customers for their patience. Yesterday, we processed 193 files. Today (by 15:30) we’d processed 166 files.
Compensation for erroneous vehicle seizures
As we shared last week, MIB will reimburse any reasonable compensation paid by insurers to their customers under their complaints handling process where the erroneous seizure is a direct result of the challenges in uploading data to Navigate.
To apply for compensation, please email feedback@mib.org.uk providing a brief background to the complaint, how it relates to recent challenges in uploading data to Navigate and what has been paid to your customer.
Further support
You can contact one of our team at navigatesupport@mib.org.uk
We will update you again tomorrow.
-----
Update Thursday 16 May 12:00
Please see the latest update.
Portal
The fix to restore Policy search in the Vehicle Update tile of the Navigate portal was successfully deployed last night. This has been tested by a small group of customers and we’ll further continue our testing today.
If the testing continues to progress well we will roll out the functionality wider, while making additional fixes over the coming days to further improve performance.
Check Your Vehicle is now live
We're pleased to announce the new Check Your Vehicle service has now gone live.
This replaces our previous Own Vehicle Lookup service and offers members of the public the ability to check if their vehicle is showing as insured in Navigate.
Thank you for your patience while we resolved the issue and worked to make this free service live.
SFTP
We worked closely with customers again throughout yesterday to help progress their outstanding files and have made positive progress. This continues to be a key priority and we thank those affected customers for their patience.
------
Update Wednesday 15 May 17:45
Following a key Go / No Go decision late this afternoon, here’s your latest Navigate update.
Navigate Portal – Policy search in Vehicle Update tile
We’re pleased to confirm that a fix has been developed and testing will continue overnight. If successful, we will roll out the functionality to all customers tomorrow (Thursday).
Thank you for your patience while we have worked on this fix. We’ll update you again tomorrow morning with our progress.
Check Your Vehicle
We're aiming to make our new Check Your Vehicle service live tomorrow.
This replaces our previous Own Vehicle Lookup service and offers members of the public the ability to check if their vehicle is showing as insured in Navigate.
We know this delay has been challenging for you and your customers. Thank you for bearing with us while we resolved the issue and worked to make this free service live.
------
Update Wednesday 15 May 2014 12 noon.
Here's your latest Navigate update.
SFTP submission
We’re continuing to work with individual customers to process files that have encountered issues during submission. This is a key priority, and we have a dedicated team working to resolve these outstanding issues.
Navigate Portal – progress on search functionality
We’ve made good progress on the fix to restore Policy search in the Vehicle Update tile of the Navigate portal. We’re continuing our testing today.
We’re on track to launch this functionality ahead of the previously communicated Friday 17 May timeframe.
We’ll share more information on this in our next update.
Support for Insurer and DA’s Commercial and Fleet policyholders
While we work to restore the Policy search in the Vehicle Update tile of the Navigate portal outlined above, we’ve shared a Standard File Format CSV File Template (Macro Free version) and a new Policyholder Standard File Transfer User Guide (Attended File Transfer) to support insurers and DAs who work with Commercial and Fleet policyholders.
This can be used as an alternative solution if commercial policyholders are experiencing difficulties with manual updates to individual vehicle records.
Many insurers and DAs were already utilising this function but we wanted to remind all customers of its availability while we worked on the solution for the Navigate Portal issue outlined above.
Insurers and DAs can now decide whether to roll this out to any commercial and fleet policyholders who don’t already use this method of updating their policies.
This has been well received and we’re now looking at how we can further support insurer helpdesks assist their commercial and fleet policyholders. We’ll share more details on this shortly.
Customers are politely reminded that Commercial and Fleet Policyholders should seek support on this from their Navigate helpdesk team and not MIB in the first instance.
Please find the links below:
Standard File Format CSV File Template (Macro Free version)
Policyholder Standard File Transfer User Guide (Attended File Transfer)
Further support
We remain ready to support you via navigatesupport@mib.org.uk
We'll provide another Navigate update later today.
-------
Update Tuesday 14 May 15:15
Here’s your latest Navigate update
Following our earlier update we’re pleased to share the Standard File Format CSV File Template (Macro Free version) and a new Policyholder Standard File Transfer User Guide (Attended File Transfer).
This is intended for any insurers and DAs who work with commercial and fleet policyholders.
Insurers/DA’s can decide whether to roll this out to any commercial and fleet policyholders who don’t currently use this method of updating their policies.
Policyholders should seek support on this from their Navigate helpdesk team and not MIB.
Please find the links below:
Standard File Format CSV File Template (Macro Free version)
Policyholder Standard File Transfer User Guide (Attended File Transfer)
See the training page of our microsite for these resources and other useful Navigate guides.
------
Tuesday 14 May 11:00
Fleet and Commercial Policy updates
Policy search in the Vehicle Update tile of the Navigate portal remains offline and we’re on track to have this fully operational by the end of this week.
While this function is unavailable we have developed a new CSV file and User Guide for bulk uploading vehicles via the Navigate Portal to help insurers support their commercial policyholders.
This can be used as an alternative solution if commercial policyholders are experiencing difficulties with manual updates to individual vehicle records.
Yesterday we tested this with a small group of insurers. Feedback on the User Guide was positive and those contacted have not experienced any issues in utilising this method of updating policies.
We will reach out to additional insurers this morning (Tues) providing information about this functionality and intend to share this with the wider industry later today.
Insurers should decide whether to roll this out to their commercial policyholders who don’t currently use this method of updating their policies.
SFTP data submissions to Navigate
To date, we have successfully uploaded the vast majority of files that we have received.
Wipro has allocated additional resources to focus on processing batch uploads of data.
The Wipro team is aiming to clear all files that have been submitted in the correct format and that are currently in the backlog and have allocated additional resources to focus on this as a priority.
Yesterday, we engaged with customers who may not have submitted data in the prescribed format. We’re continuing to support those customers to address this issue.
------
Monday 13 May Update 17:00
Further to the detailed update earlier today, we are continuing to work on the outstanding issues. All other service statuses are shown below.
As updated earlier, we have started to contact insurers today to see how best to support with an interim solution while we work on launching the full functionality by 17 May.
Your next Navigate update is expected Tuesday morning 14 May.
----
Update: Monday 13 May 13:30
Please see the latest Navigate update.
We’re pleased to report that more than 99% of files containing records submitted to us since Go Live have now been loaded into Navigate following the initial migration of more than 4 billion records. A significant majority of insurers are now able to manage their policy records using Navigate.
We are working through a limited number of outstanding issues, including some arising from the submission of data by insurers in non-standard formats.
Navigate portal
We know a key requirement for commercial policyholders is the ability to update vehicle records via the portal.
For commercial policyholders, bulk upload of vehicle data is working. We are aware of issues with updating records through the policy search function of the portal.
Over the weekend, we have had teams at MIB and our technical developer, Wipro, working through solutions and we expect to have this functionality fully operational by 17 May.
In the meantime, we are rolling out an interim solution which includes expanding the ability to update records on a bulk basis through the portal. This involves using the standard file transfer process which is already used by some commercial policyholders. We intend to roll out in phases over the course of today, and will work directly with insurers to support you as these happen.
Police support
We continue to work closely with the police to ensure their critical connection continues to operate as required. We have also been providing additional support to officers at the roadside through extended weekend hours of our Police Helpline.
We would like to thank you for your patience while we make progress in implementing Navigate post-launch and solving the outstanding issues. While there have undoubtedly been issues during this transition, we know the old MID wasn’t providing an acceptable service due to issues around stability, aging inflexible platform and limited functionality. We remain confident that once Navigate is fully operational, this new cloud-based, self-serve platform will deliver a far better solution for users.
We remain ready to support with enquiries via navigatesupport@mib.org.uk
----
Update Friday 10 May 2024 16:30
Although a number of services are available and working as planned at this stage, we know this large scale technical implementation has resulted in various challenges. Our team shares your frustrations you may have that Navigate is not yet fully operational and we thank you for your continued patience while we get the issues resolved.
We’ve made significant progress in processing submitted files and we’re on course to meet our target of processing 99% of files received by the end of today.
We appreciate the phased approach to Go Live has meant challenges for customers as we processed the backlog of files and ‘fixed forward’ other issues we encountered. This was balanced with knowing that delaying Navigate Go Live and reverting to the MID would also have a significant impact on customers.
Time to Supply
We recognise that some members are concerned about the impact that challenges associated with the roll out of Navigate may have on TTS obligations under Article 76.
Having reviewed the current position and the overriding principle outlined in section 2 of Article 76, we can confirm that there will be no sanctions applied to any Member as at the ‘review date’ of 31 July 2024.
This concession applies to data loaded to Navigate in May, June and July 2024. The next A76 review date will be 30 November, where we will review September, October and November data submissions to Navigate in the normal way.
SFTP and Portal
SFTP and Portal updates were provided in today’s 12:15 update.
See below for that update.
Further support
You can contact one of our team at navigatesupport@mib.org.uk
We will update you again on Monday morning.
-----
Update Friday 10 may 12:15
Here is the latest Navigate update for you to share with your teams.
Please be assured that our teams are doing everything they can to identify the causes and resolve any issues being experienced by you and your customers.
SFTP: Outstanding file processing
Overnight we’ve processed more submitted files containing records and we continue to work closely with individual customers who are experiencing issues in this area.
As of this update, we have now processed 97% of files. By tonight (Friday), we’re aiming to reach 99 % of files submitted to us since SFTP opened. We recognise that there are a very small number of customers who have files that haven’t been able to submit to us but we’re working hard to resolve these issues.
Advice for policyholders while SFTP data is processed
As we continue to process that data into Navigate, we recognise that some policies and vehicles will not yet be showing.
Therefore, we recommend policyholders are reminded that an enquiry on Navigate is not proof of insurance status. Cover can be confirmed by the insurer.
Police support
Although we are getting closer to the point where the data is fully up to date, we are continuing to provide additional support to the police. Officers at the roadside are supported by our police helpline team in the event of insurance cover queries andthe team is working across the coming weekend (11-12 May).
Check Your Vehicle service
Our new Check Your Vehicle service that replaces Own Vehicle Lookup and allows drivers to check their vehicle is showing as insured in Navigate will go live once we have hit our target of processing submitted files.
Navigate portal
Regrettably the temporary fix for the policy search function within the update vehicle tile we worked on throughout the night was not successful. This function remains unavailable while we now work on a permanent fix. As explained in previous updates we need to ensure this functionality is not impacting the police connection before it can be reinstated.
We share your disappointment and frustration but at this point the earliest we anticipate a resolution is the middle of next week. We expect that the permanent solution will also improve wider performance issues that customers have raised with us.
We appreciate this impacts portal users who need to search for a policy before they can update it. Users will still be able to search and access any vehicle listed against the policy.
Compensation for erroneous vehicle seizures
As communicated yesterday, MIB will reimburse any reasonable compensation paid by insurers to their customers under their complaints handling process where the erroneous seizure is a direct result of the challenges in uploading data to Navigate.
To apply for compensation, please email feedback@mib.org.uk providing a brief background to the complaint, how it relates to recent challenges in uploading data to Navigate and what has been paid to your customer.
Further support
Thank you for your continued patience while we make progress through the outstanding issues.
You can contact one of our team at navigatesupport@mib.org.uk
We will update you again later this afternoon.
-----
Update Thursday 9 May 16:00
Following on from our update earlier, here is the latest. Please be assured that our teams are doing everything they can to resolve any issues being experienced by you and your customers.
SFTP: Outstanding file processing
We’re continuing to process submitted files containing records and are working with individual customers who are experiencing issues in this area. As of this update, we have now processed 96% of files. By tomorrow (Friday) evening, we are aiming to reach 99% of files submitted to us since SFTP opened.
Advice for policyholders while SFTP data is processed
While we continue to process that data into Navigate, we recognise that some policies and vehicles will not yet be showing.
Therefore, we would recommend policyholders are reminded that an enquiry on Navigate is not proof of insurance status. Cover can be confirmed by the insurer.
We continue to work closely with the police who have access to Navigate and are supported by our police helpline team in the event of insurance cover queries. The team is working across the coming weekend to further support officers at the roadside.
Navigate portal
The policy search function within the update vehicle tile remains unavailable while we work on a fix. We need to ensure this functionality is not impacting the police connection before it can be reinstated. We appreciate this impacts portal users who need to search for a policy before they can update it.
While we work on a permanent solution, we will be implementing a temporary fix but need to limit the number of vehicles returned in a search or Vehicle Schedule download to 100 records. You will still be able to search and access any vehicle listed against the policy.
Navigate API
There are no known issues at this time but we will continue to monitor API performance.
Compensation for erroneous vehicle seizures
As communicated this morning, MIB will reimburse any reasonable compensation paid by insurers to their customers under their complaints handling process where the erroneous seizure is a direct result of the challenges in uploading data to Navigate.
To apply for compensation, please email feedback@mib.org.uk providing a brief background to the complaint, how it relates to recent challenges in uploading data to Navigate and what has been paid to your customer.
Further support
Thank you for your continued patience while we make progress through the outstanding issues.
You can contact one of our team at navigatesupport@mib.org.uk
----
12:00 Thursday 9 May
Please find below the latest Navigate update, which aims to provide a more detailed insight into progress made and any outstanding issues.
SFTP: Outstanding file upload
To date, 95% of submitted files have been loaded into Navigate.
We are aware of a small number of insurers and delegated authorities where specific file content and format issues are preventing us from uploading their files. We are investigating these issues as soon as we become aware of them, are making code changes, testing and deploying fixes to allow those files to process. Our Support Team are engaged with affected customers individually to address this. As at the start of business yesterday, there were 52 files sent by insurers that had not been processed as a result of the issues. Throughout yesterday and overnight, having deployed some fixes, our teams have processed 16 of the 52 files, reducing the backlog to 36.
Navigate API
We reported yesterday that the performance issues identified earlier in the week had been addressed. We continue to monitor performance and make ongoing improvements.
Navigate Portal
Earlier in the week, we found that the Policy Search function was conflicting with the Police connection to Navigate. We therefore took the difficult decision to turn that functionality off.
We deployed a code change yesterday that, unfortunately, began to impact the Police connection again, so we were forced to back out the change. Policy Search remains unavailable at this time. Overnight, the team have identified a temporary solution that we intend to deploy today and go live by tomorrow morning. We appreciate that this continues to have an impact on many customers. Thank you for your continued patience as we work around the clock to address this issue.
Compensation for erroneous vehicle seizures
In 2023, in collaboration with Police colleagues, MIB helped to seize 129,000 uninsured vehicles from the roads. While erroneous seizures occur from time to time, we are aware of a small number of cases where vehicles may have been seized erroneously as a direct result of the challenges and/or delay in data being uploaded into Navigate.
We apologise for any distress and inconvenience caused to your customers as a result.
If your customer has experienced an erroneous seizure as a direct result of the challenges and/or delay in data being uploaded to Navigate, we trust you will seek to resolve matters with your customers in accordance with the FCA Handbook for resolving customer complaints, DISP.
We would like to reassure you that MIB will reimburse any reasonable compensation paid by firms to your customers under your complaints handling process that are a direct result of the challenges in uploading data to Navigate. We will provide details of how to do this later today.
MIB’s Police Helpline to open again this weekend
Over the Bank Holiday weekend, we opened our Police Helpline (usually closed on Sundays and Bank Holidays) to provide additional support to our Police colleagues at the roadside, dealing with potentially uninsured drivers. We assisted more than 200 officers during the course of the weekend. The Police Helpline will open again on Saturday and Sunday this weekend to continue to provide this valuable support to officers.
Time to Supply (TTS) requirements
We recognise that firms are concerned about the impact of some of the challenges associated with the roll out of Navigate may have on TTS requirements. We have therefore summarised the TTS rules below.
Article 76 of MIB’s Articles of Association provides that insurers have a requirement to upload 95% of MID 1 policy data with 7 days of any relevant change and for MID 2, 95% of policy data must be uploaded within 14 days of any relevant change having been made. Compliance review dates are 31 March, 31 July and 30 November for the purposes of assessing performance against the MID1 TTS target and the MID2 policy TTS targets.
At the review dates, firms must demonstrate they are achieving TTS compliance at:
-
either the rolling three month performance immediately preceding the review date, or in the single month immediately preceding the review date; and
-
that they have maintained or improved their performance against the 7 days TTS from that recorded at the previous review date.
We appreciate some firms are concerned about the impact that current issues in Navigate may have on TTS and would like to reassure customers that we are monitoring the situation and will assess options to address any TTS issues resulting from Navigate.
askMID / OVL
The askMID service is fully operational with the exception of the public-facing ‘Check Your Vehicle’ service (previously known as ‘Own Vehicle Lookup’ (OVL)). We expect to make ‘Check Your Vehicle’ live when we have cleared the backlog of unprocessed insurer SFTP files.
Thank you for your ongoing patience and understanding as we work through the issues. We will provide another update at 4pm
------
Update: 16:45 Wednesday 8 May
Please find the latest update. We’ll continue to work through the night to make further progress and resolve outstanding issues. Thank you again for your patience.
Navigate API
- We solved the performance problems we saw yesterday (Tuesday) and continue to closely monitor the API performance. No current issues have been reported.
Navigate portal
- We deployed the fix for searching for a policy within the Update Vehicle tile earlier this afternoon. However, this started to impact on the Police connection to Navigate. In order to protect this vital, secure Police connection, we’ve had to turn this function off again. Overnight, our team will continue to work on a solution and we’re aiming to test and restore this tomorrow. We appreciate this has impact for customers needing to search for a policy before they can update it.
- We’re also aware that some customers are experiencing intermittent Portal responsiveness and we’re investigating this. We’ll update you with our progress tomorrow.
SFTP
- As we shared yesterday by the end of Tuesday 7 May, we’d processed c. 90% of received files. We’re aiming to hit a 97% target by the end of today (Wednesday).
We’ll continue to share updates tomorrow and we’re grateful for your understanding as we work to resolve the issues outlined above.
------
Wednesday 8 May 1300
Thank you for your continued patience while we work through the outstanding issues. Here’s the latest information:
Navigate API
We resolved the performance problems we saw yesterday (Tues) and we’ll continue to monitor. There are no current reported issues.
Navigate portal
We ran performance tests overnight (Tues/Wed) and have seen improvement. We are continuing to investigate for users who are experiencing speed or time out issues.
We’re currently completing regression testing on the issue with Policy Search function. We’ll deploy the fix early this afternoon (Wednesday) to enable this function to be available again.
SFTP
We have loaded more files overnight and are aiming to have processed 97% of received customer files by the end of today (Wednesday).
We’ll provide another update for you later this afternoon.
---------
Tuesday 7 May 18:30
Thanks for your continued patience while we worked through some of our outstanding issues and some new challenges that have arisen today, we’re working round the clock to resolve them.
Here’s the latest information we have:
API
- We solved the performance problems we saw earlier today. We've seen no re-occurrence this afternoon, having monitored closely.
Navigate portal
- Unfortunately, the fix we tested earlier wasn’t successful, so our offshore team are picking up the work overnight.
- We are 50% confident that customers will be able to search for policies at the start of the business day tomorrow.
- We don’t need to wait until we’re out-of-hours to make the required change – so if the fix isn’t in place tomorrow morning, we’ll aim to fix as soon as we can during the day.
SFTP
- We have successfully uploaded more than 90% of all the files we’ve received from customers. However, there are further issues preventing us from successfully processing the remainder
- We're making a change this evening. By close of play tomorrow (Wed), we expect to have processed 97% of received files
- We'll then analyse/ fix the problems with the remainder. We expect to be at 99% by the end of the week.
-----
Tuesday 07 May 2024 update 14:15
After launching Navigate last week, we’re continuing to deal with a few issues:
- We have processed c.90% of submitted files but have some outstanding issues that are holding up the upload of the remainder. We’re in direct contact with the affected customers and expect the majority of remaining files to be processed by tomorrow (Wed).
- We’ve had a few performance issues with the APIs this morning (Tues) but have made changes to stabilise the service and continue to monitor it closely.
- Customers currently can’t search for a policy in the Navigate portal. The fix is being performance tested now. If successful, we intend to deploy it overnight, so that customers have functionality restored tomorrow (Wed). We'll update you later today on this.
-----
Update Friday 3 May 1300.
An update on our Navigate launch: Bringing forward API and portal Go Live
Our phased approach to Navigate Go Live this week has launched an exciting new era for MIB’s data services.
Given the scale of this technical implementation, it was inevitable that we would come across some unexpected issues and we apologise to anyone who has been affected by these challenges.
During the course of our phased approach, we have:
- Migrated 4.1 billion data records from the MID into Navigate;
- Undertaken extensive testing with insurers and the Police;
- Processed 700,000 new records into Navigate with no known errors so that 92% of policyholder data is now in Navigate.
In the lead up to Go Live, and over the course of this week, we have worked closely with our police partners who have been supportive of our approach to Navigate’s launch. They have been successfully connected to Navigate since Tuesday.
We opened Navigate for SFTP data submissions on Tuesday and have ingested the majority of those new SFTP files. There remain some outstanding issues and we’re working alongside individual customers to clear these as soon as we can.
From the data submissions we have seen, the level of error rates in submitted data has halved and we are confident that Navigate’s improved accuracy will help to lower the rate of erroneous vehicle seizures by the Police. From a customer experience perspective, this should be viewed positively given the 129,000 roadside seizures for uninsured driving last year.
Navigate API and portal Go Live this afternoon
We said yesterday that the API and the Navigate portal would not go live until Tuesday. We have, however, managed to resolve a number of critical issues and will make both of these available today. API is available now and the portal will go live later this afternoon.
We’ve created resources to help our Navigate portal users to familiarise themselves with the new environment. It is possible that some users may experience issues, but we have put in place a support team who will be available over the weekend to address issues such as password resets.
Looking ahead
We recognise that bringing these services online ahead of a Bank Holiday weekend brings with it some challenges, but many customers have asked for us to bring functionality online as soon as possible.
To further support our Police colleagues at the roadside dealing with potential uninsured drivers, we are opening our Police Helpline over the whole weekend (usually closed on Sundays and Bank Holidays).
As we work through the challenges of this significant implementation, we recognise that there will inevitably continue to be issues and we will have colleagues working over the weekend to address these as they arise.
Thank you to all our customers and stakeholders for your support, patience and collaboration over the course of this week.
We will continue to provide further updates from Tuesday via our microsite.
-----
Update Thursday 2 May 2024 18:00
We’ve made great progress catching up from the weekend and getting your data into Navigate. Most of the files we’ve received have been processed but there remain issues with some of them. Our team is reaching out to the customers affected. The Police are aware of the need to exercise caution at the roadside.
We’re still fixing and testing issues with the Navigate API and portal. We’re making changes as quickly as we can, but some are still under analysis. We’ll be working on these, and on the file upload changes, over the weekend.
We really appreciate your need for clarity on when all issues will be resolved. While we want to have realistic and achievable timeframes before we share them with you, we’re mindful of the Bank Holiday weekend approaching. So that you can plan ahead, our provisional timeframes are as follows:
- Majority of data ingestion complete: Tuesday 7th May
- API delivery: Tuesday 7th May
- Availability of Navigate portal: Tuesday 7th May
-----
Update: 13:45 Thursday 02 May
We’ve now ingested nearly 600,000 data records into Navigate. The police are using Navigate as expected.
We continue to process outstanding data and make changes to accelerate the pace and help us catch up.
We are progressing our investigation into issues with API and portal and will confirm at the end of the day our best estimate for when they will be available.
-----
Update: 10:30 Thursday 02 May
We’re continuing to process the backlog of data and implementing a fix to the Navigate API. Once we’ve tested this to ensure it’s working effectively, we’ll let you know once the Navigate API is made live. We’re also working hard to open access to the Navigate portal.
-----
Update: 16:45 Wednesday 01 May
Today we’ve ingested almost half a million data records into Navigate and connected to all key police services.
We’re now focused on getting the outstanding data since Friday evening into Navigate as quickly as we can for the benefit of all stakeholders. We’re aware that some customer files haven’t yet been processed. Please bear with us, we’re working to accelerate.
There are also some remaining issues we want to resolve before opening Navigate API to insurers so we won’t be opening this today.
We’ll aim to get it launched at the earliest opportunity tomorrow.
Thank you to customers for your continued patience.
-----
Update: 12:15 Wednesday 01 May
Our Navigate programme board has met this morning for the scheduled final checkpoint since Navigate Go Live.
We’re confident with the submission of files, our police connections to Navigate and our progress so far.
A decision has been made not to revert to the MID. We will go forward with Navigate and address any issues as they arise.
We are on track to launch APIs this afternoon and will update you later.
Subject to successful testing we’re aiming to open the Navigate portal tomorrow. We will update you on progress.
Thank you for your continued support.
-----
Update: Wednesday 01 May 06:00
Navigate is now open for SFTP Data Submissions
-----
Update: Tuesday 30 April 17:00
We're pleased to confirm a phased Navigate Go Live today (Tuesday, 30 April).
Our commitment to resolving critical issues before making Navigate live to customers meant that we undertook additional testing overnight. We have made good progress and we would like to thank customers for their patience while we worked through those issues.
We’re continuing our cautious approach and are pleased to confirm that Navigate will Go Live at 17:00 today. Overnight we will configure the platform so thatcustomers can start submitting SFTP files from 06:00 on Wednesday. Navigate will then begin the process of uploading the changes to MID records since 17:00 on Friday into the new platform, which now contains 4.1 billion records from over 100 firms in the motor insurance market. We will monitor those submissions to ensure they are successful.
As you will appreciate, this will take some time to process so we will open Navigate’s portal enquiry service once all data has been loaded and validation is complete. We will let you know when this service is available.
Further activities for Wednesday 01 May (subject to further testing):
- Connection to police data services
- API enquiry will open
We will continue to closely monitor all activity over the coming days.
The option to revert to the MID remains available in case of any unexpected issues resulting in significant impacts for users, but we’re hopeful that we will not have to do this. If we do need to revert to the MID, the Police National Computer and DRP services will continue to be available. We’ll provide an update on this decision to all customers and stakeholders as necessary.
We’d like to thank customers for their continued support as we launch a new era for our data services for insurers, the police and the public.
If you have any questions please reach out to our engagement team via engagement@mib.org.uk
For the very latest updates on Navigate please see our Navigate Go Live page
Share your feedback
...