2023-03-16 Calibration Committee Meeting Minutes

Public Page

Date

Mar 16, 2023

Agenda

• Welcome/Network

• Antitrust

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

• Meeting Minutes Review

• Review Manufacturer Requirements provided by Owen.

• Review Sample XML/Code List/Workflows

  • Sublet needed in Workflows.

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Reviewed and Accepted

  • Make sure the flow chart is not giving specific like I'll say with the full tank of gas not always is it a full tank of gas. Sometimes it's half a tank, they say sometimes they give a weight in there. The flow chart, can we call out you know looking at things like requirements like there could be a requirement for.

  • New documents for today's meetings show where you might want to put the sandbags in the vehicle if you don't have a full tank of gas and how to calibrate the differences and stuff for that that's needed. So there's a lot of new requirements there that I don't think that was there two years ago.

  • The Flowchart does not get that specific. There is a few places that just refers to ensure all calibration prerequisites are met.

• Purpose of Calibration Committee Reviewed

  • Committe is looking at getting and making sure that the data that is provided electronically is the correct data. That is, so if we need new line-item types or if categories or if we need anything like a new flag or indicator to help with the data transmission, that's what we're looking at right now. And then doing that we kind of look at the, the process and the workflow of course I'm to help identify any new data needs, any new.

  • New Flows or Business Use cases that might help find data.

  • To determine the exchange of electronic data. That's really why it was formed. And so that so if you think of that in an ADAS world, how would we apply that? So part of the purpose of the flow chart was to not establish these standard, we established a standard that could be utilized. We're not so presumptive as to say this is what has to be used, but this is a good standard that you could use and it is ultimately has to do with the exchange of data.

• Calibration Requirements by Manufacturer

  • Owen provided a document to show the differences between manufacturer requirements on prerequisite for calibration.

  • Fuel tank requirement if there isn't a fuel tank requirement on the vehicles that have airmatic suspension. But the ones that have spring suspension, steel springs, a lot of them actually still do have a requirement of either fuel or weight usually something is put in there on there. It does depend on the suspension that the car has.

• Alignment Order

  • Between the alignment, the alignment check when it comes to messaging. If it's in the collision repair and alignment has taken place that fulfills an alignment check. But if you have a vehicle that has a repair that the repair doesn't necessarily require and alignment. Then they an alignment check to make sure that's what the spec would happen, but it would have to be in the logic that it's either one or the other, not both.

  • They need to be thought of in appropriate order. Some manufacturers require that you have a known good alignment.

  • Some manufacturers require that if you have to change the alignment then that leads to certain calibrations.

  • Make sure there's a clear differentiator between an alignment check and an actual alignment to two complete separate procedures.

• In the Flow Chart, we need to expand the prerequisite list, Chuck will look for items to help clarify other areas of prerequisite.

  • We could say reference manufacturer instructions to point them back to the OEM procedures.

• Brainstorm

  • For Line item, we need to have something listed as a category for the prerequisite expenses, such as topping off fuel or airing up a tire

    • We could have prerequisite for Vehicle and one for the environment.

      • This would help with floor leveling and lighting that is required.

    • The tools repair shops are using normally have the prerequisites listed.

    • There is concern that this is not needed because it is following the Repair Procedures

  • Help show you followed the Repair Procedures

    • To keep the data with the vehicle, the attachment line can be used to show the documentation used and followed to repair.

    • New Attachment Type Code List

      • Help the issue processes or calibration procedures from OEM and that prerequisites were met. So, could we come up with some kind of verbiage that would kind of cover that?

      • Do we need one for safety?

  • Going to review the code list needed in the next meeting.

Great Meeting Everyone

Up Next

• Welcome/Networking

• Antitrust

• Meeting minute Review

Action items

Decisions

1. Add Attachment Type Code list for Different Type of Documentation that goes with a repair to validate OEM repair procedures and prerequisites were meet.

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

• Russell Hildebrand

• Erin Solis

• Jason

• Darrin Bernatowicz

• Jacques

• Stacey Phillips

• Kris Bjerke

• Jesus Gutierrez

• Matt Davis

• Benito Cid

• Darrell Amberson

• Audrey Nass

• David

• Greg Peeters

• Melissa

• Bruce Davidson

• Kevin Y

• Ryan Gerber

• Roy Hall

• Bill Downey

• Paul Barry

• Gene Lopez

• Chuck Olsen

• Steve

• Joel Adcock

• Kimberly Sorlien

• Ginny Whelan

• Nathan Keudell

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