Versions Compared

Old Version 1

changes.mady.by.user Paulette Reed

Saved on

compared with

New Version 2

changes.mady.by.user Paulette Reed

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

🔓 Public Page

Date

20 Jul

Info

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

  • Welcome/Network

  • Antitrust

    • This meeting is subject to the terms of the Antitrust Statement and may be recorded.

  • Meeting Minutes Review

  • Workflow Prerequisites

    • Chuck was looking at possible verbiage to add to prerequisites.

  • Review Project Plan and Next Steps and email suggestions

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Reviewed

👥

Up Next

  • Welcome/Networking

  • Antitrust

  • Meeting minute Review

  • Workflow Prerequisites

    • Chuck was looking at possible verbiage to add to prerequisites.

  • Review Project Plan and Next Steps

Action items

  •  Paulette Reed to send email with talking points for Project Plan

  • Chuck can discuss prerequisites to determine how we can fit them into the workflow.

    • Scope of Project Plan https://cieca.atlassian.net/l/cp/CcFzsuQ0

  • Must have: Document proper calibration (Screenshots) and how the calibration was done correctly.

    • We added Attachment Type codes.

    • The Estimate has EventType with Event Type Code List that includes OEM Build Data Sheet Accessed, OEM Procedures Accessed and OEM Program Files Downloaded. Is there any other Event Types that we could add to help with the documentation?

  • Must Have: Ways to identify Sublet work is complete

    • Could we had a boolean flag to say work completed by sublet?

    • LaborInfo for the Damage Line could we add LaborType Code List to identify the labor done was Sublet or ADAS?

    • And for LaborInfo could we add sublet completed work flag here or a technician name?

    • Must have: Calibration details to show in invoicing.

    The Estimate has DamageLineInfo

  • This allows for a Parent Line and Child Line(s) of damages

    • LineItemCategoryCode that has the below ADAS values; should we add more for clarity?

  • ADAS - Calibration, Dynamic

  • ADAS - Component Initialization, Configuring

  • ADAS - Calibration, Static

  • ADAS - Diagnostic Operations

  • ADAS - Programming

  • ADAS - Research, ADAS

  • ADAS - Research

  • ADAS - Scanning

  • ADAS - Test Drive or Road Trip

    • ADAS - Vehicle Transportation (e.g., to sublet vendor)

    Decisions

    •  

      Refence Documents

      Calibration Work Documents (OEM Manufacture Requirement Examples, GM Driver Assistance Systems Aid.pdf, Honda ADAS Document.pdf, Advanced-driver-Assistance-Systems-FORD.pdf

      Release Documents: (Master Data Dictionary, Test Instance - VehicleDamageEstimate_Add_Calibration.xml)

    Participants

    Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. Calibration Committee