Page Comparison

Date

22 Jul 05 Aug 2021

Agenda

• Antitrust Agreement and Meeting minutes acceptance

• Meeting Occurrence

  • Thursday at 10am CST.

  • First and Third Thursday

• Review Meeting Minutes from last week

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

• Review Glossary page updatesBrief Recap of last meeting

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

Meeting Minutes

• Antitrust Accepted

• Meeting Accepted

• Meeting Occurrence will be the Frist and Third Thursday at 10am CST.

  • The invite will not allow both the First and Third week to be on the same meeting invite, therefore, the 2 request will be sent after this meeting.

• Documentation Review from Last meeting:

  • 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.

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

• Reviewed and finalized the https://cieca.atlassian.net/l/c/1ewreL1G

  • The list was merged with the information the committee and previously and the Adas and vehicle info documents from last week. The committee reviewed the duplicates and removed.

  • The question was still how detailed do we want to get? We are talking about features that cross multiple cameras or sensors.

  • The examples of the programming and technology is much like the human nervous system. There are many senses that are used to cause a reaction, site and feel may both me used or maybe only site. That is how the cars sensor and camera systems work.

• Reviewed https://cieca.atlassian.net/l/c/pkEQXXaN

  Adding Remote human assistance - that which will be a feature in the autonomous vehicle

  Recap of last meeting

• Jake shared some of the Build Sheet Data to show the differences in the data received.

  • Some OEM has the data on the web sites and some do not.

  • The data is formatted different by all OEM

• To get build sheet data the first step is to call dealer or whole seller, then go to OEM platform, then All Data.

• Data Changes at times and OEM needs to be contacted.

• People that build their own vehicle or get modifications to vehicle after dealer, the additions may not be seen in the data.

• CIECA currently has Code List for Vehicle Options

  • We looked at the Options and some of the ADAS features are provided and others are not. For next meeting, we will work on getting this data together and see what information we need added to the CIECA Code List for ADAS.

Great Meeting Everyone!!