2021-10-7 Meeting notes

Public Page

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Oct 7, 2021

Agenda

• Antitrust Agreement and Meeting minutes acceptance

• Go over Code List Additions

• Review Next Steps

  • ADAS

  • Telematics

Meeting Minutes

• Antitrust Accepted

• Meeting Accepted

• Welcome back everyone, we have not meet since Sept 2 due to CONNEX and the timing of our meetings.

• The Options codes we sent to Architecture, we had a couple that got questioned, and the Committee Chairs agreed to remove them from the 2021R2 Release and we look over them as a Committee and propose additions to 2022R1 if we still need the codes.

  • The Committee discussed the Active Parking Assistance and Adaptive Cruise Control, which already belonged under the Accessories Category.

    • These Features can be turned off; so they may remain in Accessories.

    • The existing codes may already be in use and may impact systems.

      • The Descriptions would be the only thing that changed and may impact systems if they have drop downs built, but the codes would remain the same.

    • Could we have 2 codes

      • This was what we took to the Architecture team to begin with, it was proposed to keep them under one category since they are the same thing.

      • If we would still like 2 codes, one for Accessories Category and one for Safety and Security, we can take it back to the Architecture committee with the advisement and the reasons.

  • The Committee decided that at this time, Active Parking Assistance and Adaptive Cruise Control should remain under Accessories.

  • Blind Spot Monitor was an existing code and Blind Spot Warning (BSW) was proposed. The Architecture Committee ask if these were different and needed both codes.

  • The Emerging Tech Committee decided that these were different features and needed to be added to the 2022R1 Code list release.

• At this time, Emerging Tech feels that the review of ADAS is complete at this time, we know as with all Emerging Tech, new changes can come back up in this area, but at this time we are going to move to Telematics.

• Telematics

  • Telematics vs Electrification.

    • Telematics is in shops now

    • Electrification is not currently in shops

  • How to shops identify Telematics on a vehicle?

    • Normally it is a question to ask the customer what subscriptions or Telematics are on the vehicle.

    • An OEM telematic may show on the scanner and have a trouble code.

    • Aftermarket Telematics may show on the scan as an unknown module.

    • Telematics being plugged into the car can impact the scan.

  • Who is responsible to the damage of a Telematic device?

    • Is the customer responsible for the cost, for example, an insurance dongle that is plugged into the OB2 Port gets damaged, will the insurance company provide another for free or is there a cost to replace damaged?

    • Fleet Devices seem to be specific to Fleet and the Fleet would replace the telematics?

  • Types of Telematics

    • The Insurance Companies have a Dongle that can plug into the OB2 Port and/or cell phones can be used to report some customer telematics.

  • In Reviewing the list on the Emerging Tech page, the infrastructure is seemed to be the vehicle talking to devices outside of the car and not seen to be part of the Collision Industry.

  • CIECA Needs to Identify Telematics like they did ADAS

    • Chuck Olsen had some documentation that he shared on the OEM Telematics, he will provide a more detailed list to Paulette after the meeting and the Chair(s) of the Committee and Paulette will look over it and get it in a presentable format for this committee to review in the next meeting.

    • Chucks presentation had GM/OnStar, Ford/Sync, Honda/Link, BMW/Assist, Mercedes/Embrace, Nissan/Connect and others.

    • We need to identify Telematics that OEM partners with Third Party Vendors.

      • Third Party Vendors that partner with OEM share data with insurance companies. The OEM and Insurance companies promote the customer must consent to an agreement before the data is shared. We are assuming this is done when the vehicle is purchased or when the subscription is purchased.

    • Is all Telematics subscription based? Some Telematics are given away to try for a few months when a vehicle is purchased.

    • We need to Telematics outside of OEM.

    • Most Fleet has Aftermarket Telematics.

• Next Steps

  • Identify Telematics and the capabilities of each to determine that data and how the data needs to be shared.

  • What Code List or CIECA messages are impacted by Telematics?

    • FNOL, Estimate, Repair are all first thoughts

    • Telematics may be able to determine the vehicle is not drivable and be able to send a Rental Request, contact Emergency road side assistance, and even may be able to order parts.

Great Meeting Everyone!!

Up Next

• Antitrust Agreement and Meeting minutes acceptance

• Review Telematics Presentation with the data Chuck provides

• Review Telematics descriptions in the Emerging Tech Confluence page and make changes as necessary.

• Work through CIECA impacts of Telematics and recommendations.

Action items

Decision

Participants

• Paulette Reed (Scribe)

• Stacey Phillips

• Chuck Olsen

• Steve Betley

• Dave Solak

• Chuck Searles

• Ryan Mandell

• Ginny Whelan

• Kevin Keating

• Frank Terlep

• Edmond Schneider

• Gene Lopez

• Phil Martinez

• Don Porter

• Sandy Blalock

• Russ Sims

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