2021-6-9 Meeting notes

Public Page

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Jun 9, 2021

Agenda

• Antitrust Agreement and Meeting minutes acceptance

• ADAS next steps.

Meeting Minutes

• Antitrust Agreed Accepted

• Meeting Minutes Accepted

• Fred had previous engagements and unable to attend the meeting this week, Gene and I walked through a recap of the last meeting

  • We moved AI and Electrification to numbers 4 and 5 of the Top 5 Emerging Technologies after reviewing them based on CIECA messages and data.

  • ADAS was moved to the top of the Emerging Technologies because it was believed that we could share data and codes from the Vehicle Diagnostics on the Estimate that would justify the reason for line items to be included on the estimate.

  • Electrification did include battery and Recycled Parts and Inventory Committee is looking at how the battery impacts CIECA messages; so please let Paulette know if you would like to be included in the Recycled Parts and Inventory Committee.

• Propulsion will be added to the Emerging Technologies Electrification Category. This was mentioned in last weeks meeting due to Toyota announcing they were not doing electric battery but focusing on hydrogen fuel cells.

  • Hydrogen propulsion of a vehicle is not a new concept, it has been around since the late 60’s, however, it does show that Emerging Technologies moving forward will not only focus on the Electrification of vehicles.

  • Propulsion showing up in repair specifications? The terminology of propulsion vs powertrain is confusing.

  • If the vehicles are running on the roads, they have specified repair procedures. Repairers may need to look at the specific OE specifications.

• ADAS Emerging Technology

  • Vehicle Diagnostic report may show the ADAS specifications, would infer red camera show up on a diagnostic report?

    • They would show up if there was an error with it working, but it will not have a code to say if it is functioning properly. For Example, if the camera is not pointed in the correct direction.

    • Any aftermarket software may only look for certain items, they may not find all of the available items on a vehicle, that would be up to the software they are using. Then the diagnostic report is different, they are pulling codes.

      • Codes are made available if they are willing to license them, and ETI works through this.

      • Codes are not specific to the problem, the codes say there is a problem and here is a list of possibilities that you need to research to undercover the root cause of the problem.

        • Best action is to work together with ETI and the SAE works committee to make the information available, but you will still have to follow the guided fault finding to lead you to the problem.

        • Need to step back from the big picture to see how all the senses work together. The infer red camera is dependent on others parts of the vehicle.

  • The better we get with IP and create better search engines for mine information on the codes and the OE Procedures and Guided Fault finding between IPs, ETI, SAE works committee and manufactures will get the ultimate benefit to all. The manufactures are sharing this information today, it is just not convenient to the industry. It is felt that the IP would be the most convenient way to get it to the estimate and get it repaired.

  • The data communication and terminology within the industry is different, which causes a lot of work and commitment to complete.

  • CIECA data is shared with the IPs to help with the estimate, through the work mentioned above to look at the vehicle sensor platforms.

  • The ADAS assist systems do not seem to be complete in our list, do we need to identify all the Vehicle sensor platforms.

  • Reviewed a Vehicle Damage Estimate in CIECA today to show the data that is shared today to show the line items. The DamageInfoLineInfo shows the Line Item Category Coded.

  • Reviewed Calibration Info in an estimate

  • Codes are showing a possible issues, if a headlight is not working, there will be a code; however, if the headlights are pointed upward, there will not be a code to let a technician know there is an issue. So there are things that will be on an estimate that do not have a code.

    • Documentation for an estimate should be to document what the car has, what technologies it has, so you know the impact of the loss or the repair process. What happened in the loss, what happened in the repair process and the history.

  • Lane Keep device or camera with damage, how do we let CIECA data reflect a code that we know we need to work that for Claim Estimator?

    • List code and note further diagnostic required through guided fault finding and supplement end notes.

    • Damage is easy to document, but there is getting it back online to function correctly. Identify damage is easier than getting it back online to function and the documentation of that process.

    • Today repair estimate we have a bucket of calibration and diagnostics information, is there a benefit to have calibration data and the diagnostic work or do we need a list of all the diagnostics that are preformed from the repair procedures?

      • Repairs see this information being important.

      • Could this come from the insurance adjuster with an open code?

      • There is not a good way today to identify the build data to be on the estimate without the repairer to review the options and determine what is on the vehicle. Identify the systems on the vehicle is critical before determining the diagnostics.

        • There may not be a build sheet for the estimator, technician and/or repairer.

        • Under calibration or sublet line items with the areas that be fixed, could we have the vehicle options?

        • Identify the systems/technologies on the vehicle and be able to capture what needs to happen to those systems, and then the repair procedures and processes can be documented.

        • last week it shared the calibration was all in a PDF format and can we get this information in the data.

          • A line item with the PDF is useful, but can we make it better.

        • Where does the Build data of a vehicle need to be captured, would this be part of Vehicle info or do we to show in line items with the estimate.

        • Depending what tool you are using, it may not pick up all the technologies of a vehicle, so tools may pull different data, so what is on the vehicle is most important.

        • Build data of the car is the critical and the base of everything, then we can determine diagnostic and work required.

          • vehicle data first

          • diagnostics second

        • The variability between manufacture to manufacture but the manufacture model line, so the complexity is guided fault finding and the history of the vehicle is very important.

        • Data can be imported of the repair from the technician from whatever system they are using. The technician provides data from the system and technology they are using to what corrective actions are taken.

  • Look at ADAS list under emerging technologies to add to this list for a complete list of ADAS.

    • How do we take Build data to get it on an estimate. What systems and standards is needed to provide this to an estimating system.

    • Vin numbers do not show up all the modules and build data does not show up and is hard to find. So build data does exist but we need to know what all is on build data and then group the data. VINDECode, the platforms that allow that to be accessed. Manufactures can share this, there are concerns with sharing the data. We need to get this data to the repair industry for collision or mechanical.

Great Meeting Everyone! Thank you everyone for the participation. Please continue to invite others that can help in these discussion.

Open

Up Next

• Antitrust Agreement and Meeting minutes acceptance

• Identify Vehicle Build Sheet new ADAS modules

Action items

Decisions

Participants

• Paulette Reed (Scribe)

• Benito Cid

• Gene Lopez

• Phil Martinez

• Troy Stone

• Michelle Corson

• Heather Bartolotta

• Stepgen

• Russ Sims

• Don Porter

• Aaron Schulenburg

• Stacey Phillips

• Chris Fatica

• Fred Iantorno

• Mark Allen

• Ginny Whelan

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/ETAC