🔓 Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
| 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
Antitrust
Introductions
Future of CIECA
Business Use Case Review for Appointment/Archive Word Documentation
Pain Points or new Implementations needed
API Standards
Concept of Product Based Committee’s and meeting occurrences.
Meeting Minutes
Antitrust Accepted
Introductions of CIECA Staff and Committee Members on the call
Future of CIECA
Reviewed the new http://cieca.com design by introducing the home page with the new video.
Reviewed the Products approach to the Standards documentation.
Reviewed that Most of the Standards Development Committees have been in maintenance mode for years, these committees used to meet twice a year for the Semi-Annual Meetings, however, the Technical CIECAST replaced those meetings and some of the meetings have not meet because the chairs did not have new work to propose.
Calibration last meet July 2020
CER last meet May 2018
CSI last meet October 2011
FNOL last meet September 2017
Glass last meet November 2012
Information Privacy Ad Hock last meet April 2021
Photo Estimate last meet September 2018
PMP last meet December 2009
Rental last meet July 2012
SCAN last meet June 2018
Scheduling last meet March 2014
Talked about scheduling the meetings and working on the Product based approach.
Products with Single Committee
Appointment - Scheduling Committee
Claims - VDI Committee
Valuation - Total Loss Committee
Disposition - Salvage Committee
Location - Rental Committee
Vehicle Repair - Repair Status Committee
Status - Subrogation Committee
Survey - CSI Committee
Title - Titling Committee
Products with Multiple Committee
Assignment (CER, Glass, Rental, Scan, Subrogation and VDI Committees)
Attachment (CER and Scan Committees)
Authorization (Rental and Repair Status Committees)
Estimate (Calibration, CER, Glass, SCAN, and VDI Committees)
FNOL (FNOL and SCAN Committees)
Invoice (Glass, PMP, RP&I, Rental, Salvage, Subrogation and VDI Committees)
Procurement (CER, Glass, PMP, RP&I, Repair Order and SCAN Committees)
The old web page design was based around the Standards as a package in Drop Box, but the Use Cases and Implementation Guides were based on the Committee that created the documentation. This could be easy if you were looking at the BMS and seen Tilling Services and saw a committee named Titling. However, this was not as straight forward for Location being under the Rental Committee. It was even more difficult for Assignment where you would have CER, Glass, Rental, SCAN, Subrogation and VDI documentation. You may find Assignment under Rental and not know to go look at the other examples. This is why we thought it would be best to move to a Product design.
Business Use Case Review
Reviewed the Appointment Business Use Case Documentation and showed the Scheduling Implementation Guide as a comparison.
The Word Document for Scheduling had committee information, which was moved to the committee Confluence page, and the description, industry benefits, triggers and messages were moved to the business Use Case.
The Business Use Case was approved.
Archiving the Word document Implementation Guide for Scheduling was approved.
Next up will be moving the implementation Guides and Test Instances to Product base.
Discussed concept of moving the Standards Development Committees to be Product Based
This would mean that Scheduling Standard Development Committee would be Appointment, that is simple, but Assignment would replace CER, Glass, Rental, Scan, Subrogation and VDI)
All Standard Development Committee’s would have the same Charter and Business Plan but specific for that Product and consist of the industry expertise for that product.
New Invitations to the Industry would be sent to get members.
The Standard Development Committee would be responsible for approving all work proposed for their Product.
Projects:
If work would only impact one product, then the Standard Development Committee would be responsible for the work
If work would impact more than one product, a Project Committee would be implemented, and goals set for that Project. The project would be completed when the standards was proposed and approved by the SDC, SAB and/or Architecture Committees.
Brainstorming/Discussion of Messages and Pain Points.
Do we know who uses the messages and how they are implemented?
CIECA is not Aware of who uses what messages and how those are implemented. We have sent polls out and reached out to companies but widespread we do not know. Also, part of the benefits of using CIECA standards is they can be customized and used the way a company sees fit.
Look at impacts and work of Shop Monkey and Podium
Poll/Texting Response Rate
Do we need to standardize reminders being sent via txt?
Great Meeting Everyone and Thank you for your participation and continued support of CIECA.
Up Next
Meeting Occurrence can stay as when needed at this time
See more meetings starting for Implementation Guides moving to Product and with new API development.
Action items
Decisions
Participants
David McCreight