Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

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.

...

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 systemin a standard way to the estimate and invoice

  • Make sure the procedures are referencing back to lines on an estimate or feeding lines to an estimateEstimate lines and Invoice lines reference back to the procedures for less supplements and delays.

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

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

...