US 12,190,660 B2
Systems and methods of building a consistent vehicle data repository
Jody Ann Thoele, Bloomington, IL (US); Jaime Skaggs, Chenoa, IL (US); Scott Thomas Christensen, Salem, OR (US); Ashish Sawhney, Bloomington, IL (US); Neill Broadstone, Bloomington, IL (US); Angela Glusick, Bloomington, IL (US); and Gustufus Phillip Theofanis, Indianapolis, IN (US)
Assigned to STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY, Bloomington, IL (US)
Filed by STATE FARM MUTUAL AUTOMOBILE INSURANCE COMPANY, Bloomington, IL (US)
Filed on Feb. 16, 2022, as Appl. No. 17/673,037.
Claims priority of provisional application 63/279,049, filed on Nov. 12, 2021.
Prior Publication US 2023/0154254 A1, May 18, 2023
Int. Cl. G07C 5/08 (2006.01); G06N 20/00 (2019.01); G07C 5/00 (2006.01)
CPC G07C 5/0841 (2013.01) [G06N 20/00 (2019.01); G07C 5/008 (2013.01); G07C 5/0816 (2013.01)] 20 Claims
OG exemplary drawing
 
1. A computer-implemented method for building a vehicle data repository, the method comprising:
obtaining, by one or more processors, vehicle build information for a plurality of vehicles manufactured by a plurality of original equipment manufacturers (OEMs), the vehicle build information containing OEM-specific terminology associated with one or more features associated with each vehicle;
analyzing, by the one or more processors, obtained vehicle build information to generate an ontology model mapping each feature to any OEM-specific terminology associated with the feature for each OEM;
applying, by the one or more processors, the ontology model to the vehicle build information to generate translated vehicle build information for each of the plurality of vehicles, such that the OEM-specific terminology associated with each feature is replaced with OEM-agnostic terminology for the feature;
constructing, by the one or more processors, an OEM build sheet based upon the OEM-agnostic terminology;
obtaining, by the one or more processors, a vehicle build sheet from a second data source;
constructing, by the one or more processors, a standardized build sheet comprising a plurality of fields, one field of the plurality of fields comprising a vehicle identification number (VIN), the standardized build sheet constructed by filling fields of the plurality of fields with information selected from the OEM build sheet and the vehicle build sheet from the second data source;
populating, by the one or more processors, a discrepancy field of the standardized build sheet to indicate that a discrepancy exists between data sources; and
causing, by the one or more processors, a display to display information of the standardized build sheet.