OEM Repair Procedures and Build Sheet Committee Project Plan

All Project Committees will follow the Project Standard Committee Guidelines and Mission.

Status: In Progress

Not Started / CIECA Staff Review / Committee(s) Review / Rejected / In Progress / Completed


Project Proposed

Project Reviewed by CIECA Staff

Submitted to Committee(s) Review

Project Started


Project Proposed

Project Reviewed by CIECA Staff

Submitted to Committee(s) Review

Project Started


Oct 21, 2021

Nov 18, 2021

Feb 28, 2022

Jul 7, 2022


Author of Project Request: Emerging Technologies Committee

Objective: It was decided by the Emerging Technologies Committee that we needed a CIECA Committee to look at the OEM Repair Procedures and Build Sheet Data to determine a better way to communicate the data for accessing Build Sheet and OEM Repair Procedures.

Expected Outcome(s): The users of this data will be critical in this committee to develop the data standards and relieve pain points the industry is experiencing. The vehicle is becoming more complex, and the complexity of repairs are growing. The end result of this committee is to provide data standards that promote quality and safe repairs of the vehicle and have mutual accountability through the industry that if a repair procedure says to execute a step that everyone agrees this step has to be done. This can be accomplished by having easy open access to repair procedures anytime, anywhere, any place by anyone, data categorized for use in a search engine, pictogram can find the data for a repair, unified terminology, and standardized build sheet best definition of standard.

Impacted/Interested Industry Segments:

OEM: OEMs have a vested interest in the quality and safety of repairs as it affects their brand and customer loyalty.

Repair Facilities:

Primary Provider: Functions as a general contractor and has legal liability for the quality ad safety of the repair and for customer satisfaction.

Sublet Repairers: Have legal liability for the quality of the work they perform and owe a duty to the primary repair provider to perform work in compliance with repair procedures.

Vehicle Owners: Passenger safety is a primary concern for the industry. Vehicle owners need to know that their vehicles were repaired in compliance with the authorized repair procedures.

Insurers/Bill Payers: Have a vested interest in the repair process and ensuring the procedures invoiced are completed

Estimating Platforms:

Information Providers:


Problem Statement:

Vehicle repairs have become increasingly complex due to new technology, vehicle sensors, etc.

OEM’s publish detailed repair procedures for all aspects of vehicle repair to include methods, techniques, tools, materials, pre & post repair testing, etc. However, The OEM repair procedures are different based on each manufacturer (parts may be included or excluded or not give MPA), names of similar or same parts being called different things, difference in specifications of material considerations, categorizing repair procedures under different categories and the procedures are written from a service perspective instead of a collision perspective.

Technicians have many hours to find the correct information to provide into the information provider software programs.

The procedures are written from a service perspective instead of a collision perspective. This is causing technicians many hours to find the correct information to provide into the information provider software programs.

The procedures leave for questions and negotiate repair plans and multiple supplements and end up causing delays and impact the customer.


Vehicles are repaired to the OEM Requirements to ensure safety of the vehicle. Repair providers must have the ability to easily access repair procedures and to easily document the repairs fully and accurately.

Must have: Message parameters to search for repair procedures.

  • Define what are all the pieces of information that are going to be required to search for those procedures and that would be 1 standard.

  • Search criteria for retrieving repair procedures (VIN or Year/Make/Model or Year/Make/Model/Vehicle Options* or Scan or QR code)

  • Search criteria for specific repair procedures (VIN and Damage categories/Parts or Year/Make/Model/Damage Categories)

  • To get the options on a vehicle, we would ask each manufacturer to help provide the cross reference.

  • VIN is used to pull options and some manufacturers call these PR codes

  • Scan or search a QR code

*Vehicle Options are called PR Codes by some manufacturers

Must have: Data requirements on response of search with repair procedures.Sending procedures in a standard way to the estimate and invoice

  • Make sure the Estimate lines and Invoice lines reference back to the procedures for less supplements and delays.

  • Repair Procedure lines should be able to be tied back to the Estimate and Invoice Lines

  • If Repair Procedures cannot be found, what response do we return? Is there a look here option?

Must have: Retrieve Vehicle Options message.

  • Assist in finding repair procedures by identifying a vehicle and the options it does/may have.

    • If VIN is the search criteria, the Manufacturer options should be able to be sent in a response.

    • If a Year/Make/Model is sent the available Manufacturer options should be able to be sent in a response.

Must have: Way to cross reference all part names. Move to Nice to have?

  • Create list of part names and allow search engine to identify a part with all names(s)

  • Hollander is a universal mapping the salvage yard world, it takes an OEM part and converts it to a Hollander interchange.

  • Review CIECA Codes and look at Part Category

  • API Search requirements New message to retrieve part names by Year/Make/Model or VIN

Must have: Documentation of Repairs

  • Information that needs to be stored and shared to partners.

Nice to have: Build Sheet Data retrieval.

  • Provide the data needed to know what we are working on in a car, what is on the car and make sure we are hitting all the things that are on the car and this needs to be looked.

  • What is all the vehicle impacted to get accurate estimate for a total loss.

  • Not everyone has build sheet data

Nice to have: Repair Categories standardized

  • Could the search for Repair Procedures by VIN or Year/Make/Model return the Categories for the OEM that is used? So first call would be search and then return Damage categories?

  • This could be a standalone API to return the vehicles damage categories.

  • Adaptive Cruise Control Calibration Procedure (Steering, Suspension or both)

  • Look at the Top 10 biggest challenges for Repair (ADAS, Repairability of Steel) and work on top issues first.

  • Look at estimating systems database structure to help identify data needed and how to categorize.

Nice to have: Repair Procedures that can be used for Repair and Insurance

  • Insurance companies have to make sure the repair procedure is followed correctly.

Nice to have: Repair Procedures by Collision and not Service

  • Service does not provide all the detail needed for collision. When working on a replacing a door or fender you may also need to look at headlight that is not in the procedure.

  • creating common terminology do we use rail or apron.

Nice to have: Photo validation of repair.

  • Photos added to the Repair to validate work was completed.

Not in scope: Training technicians

  • Remote Assist Technology

Risk to scope:

CIECA Products Impacted:

Benefits to Industry:

Request that will provide a schema of the data elements necessary to request a repair procedure with a response that will allow the requestor to document the repair plan and action taken for the repair.

Repair Documentation will allow the technicians to document the repair procedures were followed and who performed the work and when.

Share repair documentation to vehicle owner, insurance company, etc.

Releases and Task:

Scheduled Release:

Task report

Edit to setup

Jira Report:


Reference Materials: