OMS Reduces External Address Refinement API Dependency to Under 1%, Completes Transition to In-House System
Key point
OMS reduced external address refinement API calls to under 1% and fully transitioned to its own in-house refinement system.
Details
OMS terminated its contract with the external address refinement vendor and completed the end game of performing address refinement with its own in-house system. Through this, external API call volume was reduced to under 1%, and both single and multi-buildings can now be safely refined.
Advancing Jibun Address and Exception Handling Logic
Among the remaining situations requiring external API calls, Jibun address processing was resolved using the Ministry of the Interior and Safety (MOIS) road name address lookup API. The isJibunAddress() function distinguishes address types, and after obtaining the building management number via the MOIS API, the same algorithm used for existing road name address processing is applied. Since the average daily request volume dropped to under 20 cases, an API call approach was adopted instead of building a DB.
For LOW level address requests, the following countermeasures were prepared.
- Demolished buildings: Managed in the OMS building DB with
reasonCode = 63, updated daily to prevent delivery failures. - Administrative district changes: For cases where an address has changed, such as the change from Dongtandae-ro to Dongtanyeok-ro, a change history DB was introduced to look up the building management number of the past address and refine it into the latest address.
Project Retrospective and Results
Over approximately 7 months from March to October 2024, the external vendor call interface was removed in stages while verifying service stability. The contract ended as of September 30, 2024, and the system has since operated for 2 months without bugs.
During development, a full refactoring centered on the AddressSearchParam class was carried out to organize the logic. In addition, a map-based back office was built to shorten response time for address-related CS inquiries. Initially, there was an issue where logic accumulated because cases without detailed address rules were not predefined, but by clarifying the multi-building refinement strategy and covering even HIGH level cases, in-house refinement accuracy was secured.
This summary was generated automatically by AI. Check the original for the author's claims and context. Copyright belongs to the original author.
Our guide explains how the AI works. Report summary errors, attribution issues, or removal requests via Contact.