2021-8-19 Meeting notes

Owned by Paulette Reed
Last updated: Feb 24, 2022
4 min read

 

 

Public Page

 

 

 

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Aug 19, 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

  • Review EXCEL document that shows Current CIECA Vehicle Options Code List and possible ADAS features

Meeting Minutes

  • Antitrust Accepted

  • Meeting Accepted

 

  • The Excel document was reviewed with the first Tab having Features that came from a vehicleInfo.json example, the second tab having the current Options code list, the third having the combination of the list. The Combination Tab had a recommendation of the new Codes to be added to the CIECA.

    • The approach is to find generic names for the standards.

    • Would OE names that are not generic be listed? It would help

      • The list would be long and it would need to be updated yearly

      • The IPs need to work with OE to code the VIN and put terminology of vehicle in the estimating system along with the repair procedures.

      • It is not seen that the OEs will use generic packages and terminology.

      • The terminology will help communicate with the customer. The OE advertises the packages and features by vehicle, so customer is familiar with this.

      • VINDecode and Search engine to pull the repair procedures.

        • Some OE have API for Vehicle VIN to get Vehicle information and identify all options on a vehicle.

        • Some are working on APIs

        • What industry needs is to get information accessible so everyone has credibility.

        • The Repair procedures has Build Data today, the API has packages and breaks down what is in the package.

        • Frustration in the industry is when someone has an issue with a possible solution, the solution is implemented and the target moved.

    • Should CIECA look at working on the standards for the VIN DECODER API?

      • Manufacturers will create the standard because VIN can be seen as Private Information.

      • VIN = Build Information of Car

      • Customer Data and Service information is not needed.

      • Concerns is giving the information to packages and options is giving secrets to competitors. Not that it can’t be done, but being standard is not something that is going to be looked at.

      • Blind Spot can be called X by one manufacturer, Y by another and Z by another, so do we need to identify the Blind Spot System Code instead of using the marketing name. So CIECA Generic names can be used instead of Marketing. SAE Committee has provided this generic definition.

      • Many systems can use different technologies and systems can cross technologies with other systems. The repair of camera may impact 5 features.

      • Customer service representatives will have to look at the components and break it down when talking to a customer.

      • Recommended that SAE standard naming conventions terminology be used.

  • SAE, AAA, JD Power generic list was reviewed.

    • This is the descriptions of what codes need to be added to CIECA.

    • These descriptions were added as our Emerging Technology and will be used to propose the codes.

    • SAE Committee is kicking back up to add new additions to this document.

  • The naming with category

    • ADAS can be dropped because as time goes on, the Advanced systems will just be systems and eventually they will not be ADAS.

    • The coding seeing ADAS could help the estimator, the more information the better when creating a repair plan.

    • Does CIECA need to add a Category?

      • So ADAS or Safety and Driver Assistance - Safety and Driver Assist would be better category name than ADAS

      • Packages and what is included in packages.

  • Vin Decode platform

    • Everyone is using different data

    • Can we come up with a standard, Features, Installed Equipment, Installed Options/Details

    • This would be a big job and not just new technologies data.

  • Next Steps

    • The ADAS features are not yet completed and need to be reviewed after the codes are completed.

    • Telematics are the Next thing to look at after ADAS.

    • In the next meeting we will come up with Next Steps

Great Meeting Everyone!!

Up Next

  • Antitrust Agreement and Meeting minutes acceptance

  • Go over Code List Additions

  • Review Next Steps

    • ADAS

    • Telematics

Action items

@Paulette Reed will add the SAE Terminology to Master Code List and send to the committee and get virtual approval if possible.

Decisions

  1. Use SAE Document Terminology for new CIECA Options Code.

 

Participants

  • Paulette Reed (Scribe)

  • Gene Lopez

  • Mark Allen

  • Ginny Whelan

  • Kelly Roberts

  • Chris Fatica

  • Benito Cid

  • Tony Adams

  • Al Kiepert

  • Frank Terlep

  • Chuck Olsen

  • Kevin Keating

  • Mark Allen

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

Â