Optional fuzzy searching in EES
Summary
This change seeks to introduce new configuration settings in to the EES API - to enable a search to be exact or fuzzy.
Latest update and next planned activity
Date of latest update
Latest Update
08/11/2024 - This Change Proposal has been implemented as part of the November 2024 REC Release.
Impacts Overview
Impacted Consumers
Electricity
Gas
Domestic
Non-Domestic
Impacted REC Parties and Market Participants
Energy Supplier
Impacted REC Services
Electricity Enquiry Service (EES)
Priority and rationale
Standard
Priority last updated on 29 May 2026
Solution development
Problem Statement
Where a Consumer initiates a Switch through a Supplier, PCW or TPI that utilises the EES API address searches can fail as the API only undertakes “fuzzy” matching. Address Search errors will then need to go through an exception handling process creating an inefficiency and producing a loss of confidence in the Switching process.
Proposed solution summary
- As a Consumer, I want to be able to switch my electricity easily and efficiently.
- As an organisation providing switching services, I want Consumers to be able to search addresses efficiently.
No documents available.
Change Plan
Service Provider Impact Assessment window start
Completed
Start:
07 Mar 2023Due:
09 Oct 2023Completion:
09 Oct 2023Service Provider Impact Assessment window close
Completed
Start:
09 Oct 2023Due:
27 Dec 2023Completion:
24 Nov 2024Party Impact Assessment start
Completed
Start:
27 Dec 2023Due:
12 Jan 2024Completion:
12 Jan 2024Party Impact Assessment close
Completed
Start:
12 Jan 2024Due:
02 Feb 2024Completion:
02 Feb 2024Preliminary Change Report and Consultation issued
Completed
Start:
02 Feb 2024Due:
16 Feb 2024Completion:
16 Feb 2024Consultation close
Completed
Start:
16 Feb 2024Due:
08 Mar 2024Completion:
08 Mar 2024Final Change Report issued
Completed
Start:
08 Mar 2024Due:
15 Mar 2024Completion:
15 Mar 2024Responsible Committee decision
Completed
Start:
15 Mar 2024Due:
27 Mar 2024Completion:
27 Mar 2024Appeal window closure
Completed
Start:
27 Mar 2024Due:
12 Apr 2024Completion:
12 Apr 2024Original submission
Change details
Andrew Dawson - GB Group plc
7 Mar 2023
Change details
Optional fuzzy searching in EES
The EES API currently undertakes 'fuzzy' matching of address requests. For example a search of building 1 and postcode CH2 2AF returns address matches for 1, 11, 13, 15, 17 and 19
There is a requirement for this service to function in the same way as GES so that a search on CH2 2AF, 1 returns the details for just property number 1.
However, we appreciate that there are also use-cases where fuzzy matching is useful and there for propose that this functionality should be configurable using a setting in the JSON service request such as ExactMatch=true/false (with the default being false to ensure backward compatibility with the existing functionality).
There is a requirement for this service to function in the same way as GES so that a search on CH2 2AF, 1 returns the details for just property number 1.
However, we appreciate that there are also use-cases where fuzzy matching is useful and there for propose that this functionality should be configurable using a setting in the JSON service request such as ExactMatch=true/false (with the default being false to ensure backward compatibility with the existing functionality).
GBG's Utilities Register consumes the EES (and GES) APIs. We offer additional functionality allowing users to pass an unstructured address, possible containing errors. Our address-verification software cleanses and tokenises the address (identifying discrete address components) before passing the postcode and building number to EES. This enables energy suppliers to pass unvalidated addresses received from third parties such as brokers or PCWs, to our service in bulk (say on overnight runs) to append meter point details and proceed automatically with the switch.
The impact of fuzzy matching means that many verified addresses such as the one in the above example, would fail to process automatically because multiple candidates are returned from EES.
The impact of fuzzy matching means that many verified addresses such as the one in the above example, would fail to process automatically because multiple candidates are returned from EES.
Enhancement to EES to provide 2 new configuration settings in the the API request:
1) allow the request to specify whether the search should be exact or fuzzy.
2) specify the failover operation should a match NOT be found when in Exact Match Mode to operate as follows:
ExactFailError=true: If no exact match when in Exact Match Mode, return nothing (error - no match found)
ExactFailError=false: If no exact match when in Exact Match Mode, revert to fuzzy mode and return matching candidates
In 'Exact Match Mode' , if a single match can be found, then this should be returned.
1) allow the request to specify whether the search should be exact or fuzzy.
2) specify the failover operation should a match NOT be found when in Exact Match Mode to operate as follows:
ExactFailError=true: If no exact match when in Exact Match Mode, return nothing (error - no match found)
ExactFailError=false: If no exact match when in Exact Match Mode, revert to fuzzy mode and return matching candidates
In 'Exact Match Mode' , if a single match can be found, then this should be returned.
-
Impacts
Electricity, Gas, Domestic Prepayment, Domestic Credit, Small and Medium Enterprise (SME), Industrial and Commercial (I&C), Other (please specify in the Additional information box below)
Switching experience, Trust and confidence, Other (please provide details in Additional information box below)
This will improve the number of successful, automated switching journeys by GBG's customers (including suppliers, PCWs and other TPIs). Those searches of perfectly well-formed and accurate addresses that fail because of the fuzzy matching functionality, will need to be passed to an exception-handling process possibly requiring further contact with the consumer. This will increase overall journey friction resulting in loss of confidence, possible journey abandonment and even disincentivising the consumer from engaging in future switching.
This affects all consumers wishing to switch their electricity supplier.
This affects all consumers wishing to switch their electricity supplier.
No details provided
I don't believe this will impact the REC or any schedules
No details provided
-
No details provided
-
No details provided
I don't believe this will impact any data items or catalogues
No details provided
-
No details provided
This will impact the EES Specification but not the Service Definition (SLA) document. (EES Technical Specification is not on the drop-down list)
Energy Suppliers, EES Users
The proposed change will have a beneficial impact on energy suppliers and TPIs undertaking electricity switching for consumers
No details provided
n/a
No
No details provided
Priority & timing
No
With the volumes of switching traffic expected to increase in the spring of 2023, a timely change will mean that suppliers, TPIs and consumers will be able to benefit as soon as possible.
No
No
No details provided
-
Activity
Proposed solution summary changed to As a Consumer, I want to be able to switch my electricity easily and efficiently.As an organisation providing switching services, I want Consumers to be able to search addresses efficiently..
Implementation Date has been updated to 08 Nov 2024.
Orphaned SME: Lead Technical Analyst has been allocated as SME.