2024-03-14 OEM Repair Procedures and Build Sheet Data Meeting Minutes


Public Page





Mar 14, 2024


As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds.


  • Welcome/Networking

  • Antitrust

    • This meeting is subject to the terms of our anti-trust statement shown here.  In addition, this meeting may be recorded. 

  • Meeting minute Review

  • April Release

    • Anything we need to attempt to get into the release?

  • API

    • Search

    • Response Payload

Meeting Minutes

  • Welcome

    • Welcome back, with Holidays and CIC, we have not meet for awhile.

  • Antitrust and recording accepted.

  • Meeting Minutes review accepted.

  • April Release

    • We do not have any items in the April Release.

  • API Work

    • The Search criteria to find OEM Repair procedures should be easy, however the payload is going to be more complex.

    • The Search

      • Would have to be off Vin or make/model/Sub model and this would all require code list based off the OEM definitions.

      • We would have to list packages, trans, engine to help reduce the search results.

    • The OEM’s are mostly UI based and allows the user to select the options and drives them based on each selection.

    • The API’s we have may be search for ‘Audi’ and the service would provide all the Audi Make/Model to select from, then an API with the Selected Make/Model would return the packages or engine… so numerous APIs to get the information.

    • The OEM’s supply companies with the OEM Repair Procedures and they store them on their own servers or databases, and they make a UI to help find the OEM Repair Procedures.

    • The API would need to show the part of the car needing repair to reduce the number data being sent.

    • OEM one stop provides a link

      • There is security to get to the link for each OEM

    • For API to work, we may need a payment option because if they were not a subscriber to that OEM, they would be given temporary access to view the OEM Repair Procedures.

    • The API results could be the OEM Repair procedures links for the front of the car, back of the car, Center of car to provide in the estimate.

  • In repair shops there are companies trying to use Chat, GPT or AI technology to make estimate and OEM Repair Procedures.

  • We don’t have to do the full implementation, but making tiny steps are better than nothing.

  • Mark will be having surgery and out of the office for a few weeks.

  • The need for the OEM Repair Procedures that are followed and the proof they were followed is a need to the industry. This will help repair facilities prove the vehicle was repaired correctly.

  • When the data is stored, it can be used for reporting to determine how long a repair normally takes following the OEM Repair Procedures and can be used for other statistics.

  • Business problem: We have mission critical data being produced by different providers in different formats, different look and feel. This data needs to be consumed by potentially thousand of different companies.

    • Develop standard methodology to request information and receive it.

      • Back to creating a request for Vehicle Repair Procedures and a response.

    • Could we work with an OEM and run analysis on the data we could get back. Compare a Repair Procedure for quarter panel, a rear body panel and a bumper cover or maybe a headlight, simple repair procedures. This would give us an idea of how the data is returned and what we would need to capture.

    • Work with CCC and Mitchell or Auto Text and see how they store and transmit this data in their own systems and to customers.

      • Mitchell Estimating system provides the repair procedures based off the parts in the estimate.

        • This API is not something that the Estimating providers need, because they already have access to the data in their own systems. The API we are talking about is a repair facility or a new company that would like to get this information from the OEM.

  • Andrew will present at the next meeting on how Repair Procedures are used via BMW Repair shops.

Great Meeting Everyone

  • Welcome/Networking

  • Antitrust

  • Meeting minute Review

Action items:

Andrew Batenhorst can demo BMW Repair Software showing how they utilize and access and research repair procedures.
Mark Allen can show his process of looking up the Repair Procedures.
Everyone that is familiar with a system that is used to find repair procedures, look at the fields the UI ask you to fill in for the search, then look at the data retuned and share that with the committee.
Phil will ask his team on a generic level what is needed and how the responses are sections are shared.






  • @Paulette Reed

  • Paul marshall

  • Chuck Olsen

  • Dave Butler

  • Trent Tinsley

  • Mark Allen

  • Stacey Phillips

  • Nick Dominanto

  • Phil Martinez

  • Dale Ringwald

  • Paul Barry

  • Kelci Lemanski

  • Todd Korpi

  • Don Porter

  • Andrew Batenhorst

  • Chis Chesney

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. https://cieca.atlassian.net/wiki/spaces/CPSC/pages/1354760193