2024-06-20 OEM Repair Procedures and Build Sheet Data Meeting Minutes

 

Public Page

 

 

 

Date

Jun 20, 2024

ANTITRUST STATEMENT

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.

Agenda

  • 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

  • Get Vehicle

  • Get Build Sheet

  • Get Repair Procedures

  • Mark Allen demo his process of looking up the Repair Procedures

Meeting Minutes

  • Welcome/Networking

    • Gene brought interns to the meeting to introduce them to our team.

      • Mark recommended to have the interns pull OEM Repair Procedures to see how that works.

  • Antitrust

  • Meeting Minutes

  • Messages

    • Get Vehicle

      • VIN

        • VIN is first and most reliable method

          • A number of times that a BMW goes to a shop that is not able to repair the BMW.

          • Could this be a customer shopping for a shop.

      • Year, Make, Model, sub model, trim, engine

        • Should these values be open code list in CAPIS?

        • This is not the recommended process to get the vehicle, but it may be needed.

        • Trims

          • Currently an array

          • Not sure we would need trim package to make repair

            • exterior trim can be different color and it could be important to get paint code?

            • Trim is not important in the search

        • Engine

          • Powertrain is important for gas, hybrid, electric and that impacts repair procedures.

          • There can be a different number of engines.

    • Reviewed the Vehicle in CAPIS

      • Who makes the coding changes

        • For CIECA the Architecture team and technical members work to create the data. The technical teams do not know the collision industry or work on the vehicles, but they gather the requirements from the business team and the professionals in the industry.

        • This is another avenue for our interns.

    • Get Build Sheet

      • With Vehicle

      • How much would this be used to get parts?

      • We need the payload for the Build Sheet . This is not something that is in BMS today so we will need the examples of the information.

      • Build Sheet may have more information than the vehicle or less. For example, it may say there is a number of ADAS features but it may not be on the Build sheet.

      • Will this be a link to the URL or everything in the build sheet

        • Safer to provide everything in the build sheet.

      • Parts Suppliers can provide build sheet and sometimes there are times they say the build sheet is not available. Sometimes the build sheet is 2 pages and sometimes they are 8 pages.

      • Can we get some build sheet examples from the team.

        • We have a few that were provided when we started this project that we can look at, but the more examples the better.

    • Get Repair Procedures

      • with Vehicle

      • Area of impact or buckets for area of car

      • Repair vs replace

      • Operations

        • Calibration

        • Alignment

        • ALL

      • Internal panel or external panel

      • Diagnostic trouble codes from pre-scan descriptions

        • There are different codes for each manufacture

          • What is a U code and P code (Everyone use same 3 codes?)

            • P Powertrain

            • C chasse

            • B Body

            • U Network/Communications

Great Meeting Everyone

  • Welcome/Networking

  • Antitrust

  • Meeting minute Review

  • Demo by Mark

  • Review all the examples of build sheet data

Action items:

Decisions

References:

 

 

Participants

  • @Paulette Reed

  • Chuck Olsen

  • Trent Tinsley

  • Mark Allen

  • Gene Lopez

  • Taylor Moss

  • Michael Giarrizzo

  • Stacey Phillips

  • Kirk Carlisle

  • Ross Whiteley

  • Aaron Rolfsrud

  • Paul Marshall

  •  

  • Paul Barry

  • Micah Deaville

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. OEM Repair Procedure and Build Sheet Data Standards Committee Home

o

Looking for labels? They can now be found in the details panel on the floating action bar.

Related content