2021-12-16 Meeting notes

Public Page

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Dec 16, 2021

Agenda

• Antitrust Agreement and Meeting minutes acceptance

• Review OEM telematic systems

• Work through CIECA impacts of Telematics and recommendations.

  • Data Ownership and Security

    • Insurance Estimate Time of Repair for Shop

    • Estimate for Reverse lookup of parts to Salvage

  • Scan tool being used to identify Telematics, possible checklist for Telematics

Meeting Minutes

• Antitrust Accepted

• Meeting Minutes Accepted

• In the last meeting we discussed using the Checkmark Style approach with the OEM Telematics document that was in the MyCar, July 2018. We reviewed the Checkmarks and the new Columns that were added to Break down the Telematics.

  • For Example, in the first document All Remote Features were in one column, but now we have Remote Engine Start/Stop, Remote Door Lock/Unlock, Remote Alarm Assist.

  • Things still needing to be done for the document

    • Putting the OEM in Alphabetical order

    • Updating the OEM System names to newest systems

    • Validating all the features against the webpages due to the new Telematics Columns being added.

    • Adding a Date to the Document to say when the data was and a disclaimer that Telematics are changing rapidly, and this was the data of publication.

    • Recommended that if we publish that we would review annually

    • Gene wants the Check marks to be same font as Lettering; then Sandy and others mentioned making the font larger to match the Checkmarks would be helpful.

    • Since OEM Repair Procedures need to be followed should we provide links to the OEM repair procedures?

      • We should provide the URL to OEM One Stop where all OEM Repair Procedures are located.

    • Should we ask OEM to validate?

      • We can ask but it won’t be done

    • The Vehicle itself will always have the latest information and the software version that it is using; so, the Scan tool is the best tool at finding Telematics.

    • As rapid as Telematics and Software Versions change, it is possible for this document to be out of sync the day it is published.

  • Remove all the Checkmarks and have a list of the OEMs and the systems they use with the URL and the OEM One Stop URL and a list of possible Telematics.

  • Paulette will be mad scrapping all this work… lol

    • The document was not created to be a tool for the industry, the document was created for this committee to see what was available so we could determine if CIECA needed to provide any of this data in the messages between the industry, would we need a code list addition like we did for ADAS. In short, Paulette is good with the document versions and believes the document did what it needed to promote communication.

  • Should V to V (Vehicle to Vehicle) Telematics and V to I (Vehicle to Infrastructure) be added to the list of Telematics

    • They are not mentioned as V-V or V - I in the spreadsheet, however we do have items like Realtime Traffic, Service Assist, Fuel assist for the (V-I). Connect Fleet is for the V-V, so much like the Remote Functions, the functions will probably me more specific and broken out.

• Review CIECA impacts of Telematics and recommendations from last meeting to see what this committee can do

  • Data Ownership and Security

    • Insurance Estimate Time of Repair for Shop

    • Estimate for Reverse lookup of parts to Salvage

  • Scan tool being used to identify Telematics, possible checklist for Telematics

    • We removed the mention of ADAS from the previous meeting minutes and the agenda to make sure we reflected that the Scan tool could be used to help identify Telematics.

    • There is no need for a Checklist; it should be stated to go look at the OEM Repair Procedures

      • What about Telematics that may be aftermarket

        • Aftermarket parts would not be found with the Scan tool, this would be a conversation with the owner.

        • Shops should always talk to the owner/customer to find out as much detail about the vehicle in repair as possible, but the OEM Repair Procedures is what the shop must use.

    • What risk would or could be reduced with a checklist?

      • If they use the OEM Repair procedures, they should not have to worry about the doors being locked or the vehicle being started when they are in repairs.

      • One concern is the customer receiving a lot of unnecessary notifications when the vehicle is in repair.

        • It seems most customers know the vehicle is in the shop and ignore these alerts, at times customers call to question the alerts.

    • Telematics have been standard on Vehicles since 2016-2018. All Vehicles now have to have a reverse camera.

    • Checklist would be 1, ask customer about vehicle and 2, use the OEM Repair Procedure.

  • In looking at the Telematics in the document, can we see anything that we need to document?

    • We already discussed the Remote Start/Stop, this can only be done if the vehicle is locked, therefore, it is not a concern during vehicle repair.

    • Remote Lock/Unlock will only work when all the doors are closed.

    • OEM’s have safety parameters built in, but the OEM repair procedures document how to turn and what to turn off when repairing a vehicle.

    • GEOFence is a Telematics on the list where the car is monitored about where it goes and how fast it goes.

      • This is something that could alert a customer that the car is moving, that it is going over a certain speed because some repairs require the vehicle to be driven at certain speeds for so many miles. Again, this is something the customer would probably ignore when it was in the shop or would be a simple call to the shop to get an explanation.

    • Health and Diagnostics were talked about earlier and again, this may happen today, but most customers ignore.

• Meeting Occurrence and Time for 2022

  • Everyone is good with the Current set up and Paulette will send invitations out ASAP to get everyone's calendars full.

  • Topics for Next Meeting

    • Do we continue with Telematics or do we think we are done with Telematics after a review of the new document?

    • Committee decided that Frank and Gene needed a lot of Homework for the Holidays.

Great Meeting Everyone! Have a Safe and Happy Holidays

Up Next

• Antitrust Agreement and Meeting minutes acceptance

• Coming Soon (After Frank and Gener complete Homework)

Action items

Decision

Participants

• Paulette Reed (Scribe)

• Mark Allen

• Chuck Searles

• Frank Terlep

• Stacey

• Benito Cid

• Gene Lopez

• Paul Barry

• Sany Blalock

• Ed Mondragon

• Mike

• Fred Iantorno

• John Eck

• Don Porter

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