Page Comparison

Date

03 Oct 2022

Agenda

• Antitrust

• Intro to CIECA

• Introduction of our Chair

• Introductions of members

• Begin work on the Committee’s Project Plan

  • Problem Statement

  • Scope

• Discuss Meeting Occurrence

Meeting Minutes

• Antitrust Accepted

• Introduction of Chairs

  • Kim DeVallance Caron, Product Portfolio Director of Enterprise Holdings.

• Introduction of Members

  • Please see CIECA Referral Project Kickoff-20221003 recording in Referral Work Documents to hear all of the introductions.

• Intro to CIECA

  • CIECA is a nonprofit industry association created to develop a common language for computer systems to communicate efficiently.

  • CIECA does not develop or sale software

  • CIECA develops standards that member companies from all segments of the Collision Industry can exchange information electronically.

    • Discussed active committees

      • Drive for Technical Audience to help with Architecture committee.

  • Demo Home page of http://cieca.com

  Introduction of Chairs

• Introduction of Members

• Meeting Occurrence

• Review Committee Home Page

  • Reviewed Committee involvement and Attendance record

• Review Business Plan

• Status

• Important Dates

Background

• Background

  • Kim DeVallance Caron introduced the concept of the referral project in our Semi-Annual meeting. The referral is similar to an assignment message however, the assignment was triggered from the bill-to perspective in the past and the referral is coming from business partners that are not responsible for payment. For example, in the past, the insurance company that was paying for the tow, rental, etc. was normally the one that sent the assignment to the business partner. In today’s world, there are systems that work around the FNOL and repair that may trigger a tow or the rental that are not responsible for the payment of these assignments. The data needs are different between an assignment and a referral, and we would like to look at these data needs.

    • Cars may reach out for assignment at FNOL and get referral out, but OEM would not be paying for the assignments.

    • Want to take into account how the industry is changing when creating the new api standards.

• Objective

  • The committee’s objective is to improve customer service in the inspection and repair process by developing and maintaining messaging standards aimed at automating vehicle referral activities, which will create efficiencies for all industry stakeholders.

• Impacted/Interested Industry Segments

• Problem Statement

• Scope

  • All Collision Industry segments that use assignment

• Problem Statement

  • With emerging technologies, there are different ways the assignment of services in a collision incident can be initiated. As part of the CIECA CAPIS project, these different types of referrals need to be identified and standards need to be built.

    • CAPIS is the new standards for API Development

• Brainstorm to identify Problem Statement and Scope of the Project.

  • Reviewed the Referral Project

    • Status (Active)

    • Scope is what we are going to work on through this committee to define the Must haves, Nice to haves and not in scope.

      • This helps us identify the work we need to do as a committee

  • Brainstorm

    • FNOL committee may need to be involved because the car may be able to detect a loss and notifying emergency agencies (police, ambulance, etc.), getting a tow, rental or making the assignment to a shop.

    • What assignments could be possible at time of FNOL.

    • Fleet companies and insurance companies may get assignment for Estimate only but then change to a DRP assignment. Things may get lost between the client and body shop.

      • Look at the data in the BMS and determine what may be missing.

      • Examples could be provided.

    • In the past we always maintained backward compatibility but with the new generation of standards we want to make sure to only bring the data that everyone needs.

      • We need to review the data we have in assignment and look at PII and data that is appropriate and not pulling data that is not needed.

      • Architecture Committee

        • API is being released in October and there is a webinar to go over how we are coming up with the new standards.

    • `Referral for rental comes from the shop for customers when they set up a repair.

      • Shop can do referral for glass and calibration and other sublet providers.

    • The AI committee mentioned that a car will be able to identify it is a total loss and may send assignment to salvage.

  • Assignments

    • If anyone thinks of any other possible workflows are data or has examples, please email to paulette@cieca.com

    • Paulette will provide BMS and Workflows with FNOL and Assignment for next meeting.

• Appointment impact

  • CIECA Simplified concept was applied this year where all of the services became a Product Committee, and the committees, such as this one that would impact several messages was created to focus on a topic.

  • When a Project Committee makes recommendations, each Product Committee impacted will get the chance to review the recommendations and provide feedback.

  • When the Project and Product committees are in agreement, then the standard recommendations will go through the Architecture and SAB review as all CIECA Standards do before they are implemented.

  • Stacey did marketing to the industry to see who was interested. We can send invitations to Appointment and FNOL committee members to get involvement.

• Meeting Occurrence

  • Twice a month

  • Send out a doodle to figure out best days and times.

👥 Great Kickoff Meeting Everyone

Up Next

• Antitrust

• Meeting minute Review

• Welcome/Networking

• Review Project Plan

• Review topics emailed from the committee

• Review cieca.com message workflows

Action items

•  I

Decisions

Reference Material:

Referral Work Documents

CIECA Referral Project Kickoff 20221003 Recording

CIECA Referral Project PowerPoint