2023-10-19 Calibration Committee Meeting Minutes

Public Page

Date

Oct 19, 2023

Agenda

• Welcome/Network

  • Dan Dutra

  • Elizabeth Prosser

  • Bud Center

  • Adi Bathla

• Antitrust

  • This meeting is subject to the terms of the Antitrust Statement and may be recorded.

• Meeting Minutes Review

• Chuck was looking at possible verbiage to add to prerequisites.

• UI Flowchart/Best Practices Update

• ICAR presentation by Bud Center

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Reviewed and Accepted

• Welcome

  • Adi Bathla from Ravidas

• Reviewed Industry Page on cieca.com

  • We added links to CIC Flowchart

  • Added Link to UTube video on calibration workflow

• UI based design.

  • Reviewed draft on cieca.com

  • This is not to replace the CIC Flowchart, this is a quick reference page.

  • Changes suggested.

    • We should move Post Scan; it should not be before calibration and before the road test and return to customer.

    • We should be doing the final post scan after we’ve done a road test validating ADAS functionality and before returning to vehicle.

  • Disclaimer

    • This work is being done to help this committee find data that may need to be added to the data standards and will be good to share with CIC, however, CIECA dos not set repair standards and we do not want people to be confused that the work we do is the standard on repair procedures, we just gather the process to look for data.

    • Add disclaimer to CIECA page.

  • Adding Data we capture at each step in the process, the documents used reference and data captured.

    • Capture which seatbelts were impacted during collision.

    • Previous damage

    • Previous warning lights on dashboard

    • In process scan and they may be done multiple times and the answers that we're looking for a standard way to communicate the activities performed and if possible be able to validate that work was paid for it and how it was performed.

  • Work with ICAR to have them present and talk and get talking points for our workflow.

• Chuck Review of workflow and Committee Documents

  • Chuck and Darrell reviewed the documents and did not see where the information in the documents were different.

  • Precondition vs Prerequisite, we have them being used as interchangeable, but they mean something different in the industry, so we need to come up with a standard in documentation

    • CIECA is not changing this for the industry, just looking at how we would like to document.

    • In the workflow, prerequisite is used 95% of the time.

    • In our documents, because we are talking about how to document the work being completed, we are going to go with prerequisite. A precondition seems to be more of an option and not something that would need to be documented.

  • Include verbiage “according to OEM service information with respect to any of the preconditions or prerequisites”.

  • Add section to focus on the data needed to document.

    • What data is needed to show the work that needed to be done?

    • What data is needed to prove the work was done as required.

• Bud Center from ICAR joined to answer questions from the committee.

  • In a committee meeting it was mentioned that ICAR had a 15 min video that may help with the prerequisites of the workflow.

  • As per the precondition vs prerequisite, Bud says ICAR uses precondition.

  • ICAR has collision documentation

    • Facts at a loss.

      • What to what situation was the car in when it was in a collision?

    • Damage analysis courses

      • where we ask questions like how many people were in there?

      • what seatbelts were being worn at the time, how did it happen?

      • Did you go off road?

  • The industry seems to ask the customer a number of questions and they are not shared. So at the time of the accident the FNOL may capture this information, then the Insurance agent may ask the customer and then the repair facility.

    • Is there a way to capture this and share it so the customer is not ask repeatedly?

• Post repair scan when it's supposed to be done?

  • Does it come before the calibration is performed or after the calibration is performed?

    • Today we have the post scan and final scan after calibration.

    • Add a post repair/pre calibration cause it's important that that scan is done at that point as one of the prerequisites of going forward with the calibration that all the repairs that you did the codes are clear of the TPM but you know that those other things are fixed there because I I thought somebody had mentioned in there of moving the post repair scan in the chart after the calibration but to me it kind of looks like 1/3 opportunity.

    • Reference to previous meeting where we call Process Scan meaning we do it several times.

    • A healthy check code could be added.

• Prerequisites documentation who’s role is that?

  • CIECA Committee for Calibration can work on the full list.

  • OEM would be perfect to have the list so it would be standard.

    • OEM may take a while because they are working on other things.

  • RTS website where you can go in and look at calibration requirements.

  • One of the things that we're looking at adding to that is the information on alignment requirements with these calibrations, when it's required, what it means, why?

    • Bud will create a list of prerequisites and then run by this committee for review.

    • See if we can present at OEM roundtable to get some exposure to the OEMS.

    • Sean Carey has a lot of good information in his presentation.

    • Mark Allen and/or Jake Rodenroth would be good reps for the OEM roundtable.

    • Ask Chis Carris to get on the OEM roundtable agenda.

      • Invite him to the Calibration Committee

Great Meeting.

Up Next

• Welcome/Networking

• Antitrust

• Meeting minute Review

• Chuck was looking at possible verbiage to add to prerequisites.

• UI Flowchart/Best Practices Update

• ICAR presentation

Action items

Decisions

Refence Documents

https://cieca.atlassian.net/wiki/spaces/CPSC/pages/1425375233 (OEM Manufacture Requirement Examples, GM Driver Assistance Systems Aid.pdf, Honda ADAS Document.pdf, Advanced-driver-Assistance-Systems-FORD.pdf

Release Documents: (Master Data Dictionary, Test Instance - VehicleDamageEstimate_Add_Calibration.xml)

Participants

• @Paulette Reed

• Tim Ronak

• Gene Lopez

• David McCreight

• Chuck Olsen

• Paul Barry

• Randy Kwan

• Stacey Phillips

• Chris Chesney

• Darrell Amberson

• Phil Martinez

• Don Porter

• Adi Bathla

• Melissa Wolf

• Bud Center

• Kim Sorlien

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/CPSC/pages/49479907