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

Dates

Project Proposed

Project Reviewed by CIECA Staff

Submitted to Committee(s) Review

Project Started

Rejected/Completed

Project Proposed

Project Reviewed by CIECA Staff

Submitted to Committee(s) Review

Project Started

Rejected/Completed

Oct 21, 2021

Nov 18, 2021

Feb 28, 2022

Jul 7, 2022

Background

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 / Repair Facilities / Insurance / Estimating Platforms / Information Providers

Problem Statement:

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. This is causing technicians 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.

Scope:

Must have: Way to cross reference all part names

  • 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

Must have: Message parameters to search for repair procedures

  • This committee would have to 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.

  • 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

Must have: Sending procedures back into the estimating system

  • Make sure the procedures are referencing back to lines on an estimate or feeding lines to an estimate.

Nice to have: Repair Categories standardized

  • 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:

Releases and Task:

Scheduled Release:

Jira Report:

 


Reference Materials: