2021-6-30 Meeting notes

Owned by Paulette Reed
Last updated: Jun 30, 2021
4 min read

 

 

Public Page

 

 

 

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Jun 30, 2021

ANTITRUST STATEMENT

As participants in this meeting, we need to be mindful of the constraints of antitrust laws. There shall be no discussions of agreements or concerted actions that may restrain competition. This prohibition includes the exchange of information concerning individual prices, rates, coverages, market practices, claims settlement practices, or any other competitive aspect of an individual company’s operation. Each participant is obligated to speak up immediately for the purpose of preventing any discussion falling outside these bounds.

Agenda

  • Antitrust Agreement and Meeting minutes acceptance

  • Meeting Occurrence

  • Is there any ADAS modules identified that are not in the current list?

  • Look at ADAS and compare to Generic Industry Standards

    • Do we need Data Aggregates on Insurance, Estimate, Repair that states the ADAS systems and share this information.

      • What information is needed to be shared?

Meeting Minutes

  • Antitrust Accepted

  • Meeting Accepted

  • In the last few weeks, businesses has started to allow travel and people are taking vacations and it is becoming more difficult for people to attend weekly meetings. It was proposed that we move to bi-weekly meetings.

    • A Doodle Poll will be sent out to determine everyone’s best availability.

    • The SAE meetings are booked at the same time currently on the 3rd Wednesday of every month.

  • The ADAS Emerging Technology list that the Committee Created will be reviewed with the new documentation that the Chairs of the committee shared.

    • Adas-nomenclature pdf is simplified category of ADAS modules from All Data and AAA is different than the current ICAR category, but the committee reviewed the provided documentation. The PDF was emailed during the committee to all members.

      • These Categories were added to the Emerging Technology page in the meeting.

        • The definitions of these Categories need to be added to the page as well.

    • VehicleInfo.json document was shared with the committee to view the new API format and to see the Safety and Driver Assist Categories.

  • New ADAS Features discussed

    • Stability Control Assistance, is a program that identifies that someone is carrying items on the roof carrier and lowers the load to stabilize.

    • Road Adaptive Suspension, is when the vehicle laser scans the road to determine the conditions to adapt the suspension.

  • CIECA concepts

    • When we identify all the categories, we can add these to a field with a code list. This will allow new ADAS features to be added without making changes to the messages. The process we are working on now is to help us identify the correct way to capture the data. Do we need Category and Module fields? And when we know the ADAS modules, what data do we need to share about the modules to the industry. Some examples of other items to share would be Action (Calibration, inspection, etc.), Optional vs Standard.

  • Today the Estimate has an area at the top to identify the Vehicle Features and ADAS modules.

    • This seems to be a manual process.

    • To get the Build Data sheet is a phone call to a dealership to retrieve the information.

      • Build Data does not seem to be complete, is there a way for the vehicle to identify all the features?

        • There are things such as a heated steering wheel that will not show up in scans of the vehicle, but will be part of the vehicle.

      • Build Data is specific to the vehicle.

      • The Manufacturer Label for Port will have all of the features and systems on the vehicle from the manufacturer.

    • Must Access the OEM Repair Procedures in a different call or search by VIN.

  • Year is a relevant item to be discussed, because each year and by model, there can be different availability on vehicles, such as after a certain year Back up cameras were in all vehicles, Emergency Braking is supposed to be on all vehicles in 2022 or at least 97%.

  • Type of car is relevant because all Electric Vehicles are required by law to notify pedestrians they are coming and my be in range of them.

  • Discussion for Next Steps

    • Clean up and verify the Emerging Technologies Confluence page.

    • Start working on a Workflow to capture where this data will come from and who in the industry can get the data and when they need it.

Great Meeting Everyone!! We will take the first week of July off to Celebrate the 4th of July. Everyone have a safe and happy Holiday! The second week there is travel for CIC Conference, so we will also take that week off. Please respond to the Bi Weekly Doodle Poll and look for the new meeting invite.

 

Up Next

  • Antitrust Agreement and Meeting minutes acceptance

  • Review updates to Emerging Technologies Confluence page that simplifies and merges the documentation provided.

  • Start a workflow to identify where the data is coming from and who needs the data and when.

Action items

Paulette will add the definitions of adas-nomenclature pdf to the Emerging Technologies Confluence page.
Paulette will work on combining the list from the new simplified ADAS Categories and the Committee defined ADAS modules for review in the next meeting.

Decisions

 

Participants

  • Paulette Reed (Scribe)

  • Stacey Philips

  • David Solak

  • Charles Dillard

  • Ginny Whelan

  • Gene Lopez

  • Tony Adams

  • Mark Allen

  • Benito Cid

  • Fred Iantorno

  • James Spears

  • John Eck

  • Paul Barry

  • Matt Carroll

  • Aaron Schulenburg

  • Frank Terlep

  • Sandy Blalock

  • Chris Caris

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

Â