🔓 Public Page
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 and Meeting minutes acceptance
New Member Request
Recap Last Week
CAPIS Simplified
CAPIS Avatar
2022R1 Coming Soon
Itemized Services Project Request
Work Session
Mike walkthrough of VINDecoder/VehicleInfoLite with Reference and Bundling
Work on the Architecture Guideline to help people understand the flattening
Work on Party and ClaimInfo
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
New Member Request to meet with CIECA members to help with implementations
A new CIECA member had reviewed the Schemas and BMS and understood all those concepts but was struggling with implementation.
CIECA does not control implementations or work with the implementations. Paul has developed the Technical Form concept on the new web page for members to ask questions.
The new member had done some research and found Mike Hastings and wanted to meet with Mike. Paul and I discussed, and we thought it would be better if the Architecture Committee was allowed to meet so the new member was exposed to different segments of the business and the Architecture Committee could see what members were asking about the technical documents.
Mike recommends making sure your messages validate with your partner and was willing to help any way he could.
Other Members are curious with what the member is looking for but are good with Mike reaching out and working with them individually.
A meeting will be set up with Mike and the new member for introductions and everyone else will be invited as optional so they can join if available.
Recap Last week
CIECA Simplified
A very brief Demo of the new test site.
Will Charley’s links work in the BMS? The hyperlinks do not work in the Web page rendering, but they do work in the Download Word Document.
The Master Code list from the latest release does not have the change log updated. We reviewed the change log and the one that I had pulled up did have changes. Need to look and see what version is posted.
Recommendation to add the Change Log to the Index.
We are asking Architecture, Marketing and the Executive Committee and Board to review the test site, Home - CIECA Products (zohosites.com) and provide feedback before we build all the Products out.
CAPIS, Cappy (Digital Dan). Digital Dan was approved
Talked about changing hairstyle to a mohawk.
Stacey is going to put together a challenge to the industry to come up with an Avatar, but until then, we have digital Dan.
Jira Board Review for 2022R1
Itemized Services Project Request from Chuck Olsen to Share itemized services beyond scanning
As a leader in the industry, we see the logical next move towards documenting work performed by individual procures verses scans with average pricing. Each session (regardless of scan-type) has varying levels of complexity, technician skills, and time invested by both the shop and our diagnostic technicians and must be transparent, justified and thus compensated for accordingly.
Is this for only SCAN Tools and Pre and Post Scan
Itemized Services name is not detailed in the name
Is the request for Estimate
Estimate and Invoice
Invoice has Header for Buyer and Seller and then the Charges
The detail followed
Shop doing a Sublet service and charging, this is sounds like a sublet that you share with the shop and not with the customer.
Insurers are dictating the amount they want to pay, and this is to help promote those changes.
This sounds like work we did for Operation Codes for Pre-Scan and Post Scan; we just need to make it itemized.
This would be a good Project for VDI and PMP
We will take this information back to Chuck and then do a formal presentation for approval to the SAB and Architecture.
Does this mean a new message or new aggregates? At this time, we believe this is a new aggregate, but the committees may decide a new message.
Mike walked through the work that he did on the proof of concept with Vehicle Info.
Take Vehicle Lite and coding now to reference
There references can go down and only pull the one property, it is hard coded in the display because Mike did not have VinInfo built out yet.
The BMSCommonGlobalTypes that was created by Andy’s work was used as the reference and straight from the BMS
These are the old style that Andy’s tool created and does not follow our style guide.
We created a new common type of file that had a flattened version.
Being a developer and not wanting to type in everything this was attempted
Andy could create the naming with the new style guide, but the importance on flattening and making sure the industry is what it is needed.
Eliminate things that are not going to be used as much and flattening, with new CAPIS common Types file and then build what Mike did here as Small Med Large with bundling.
The Key thing is the references.
Powertrain could be Engine and Transmission to help flatten but it may okay to flatten.
Great Meeting!
Up Next
Antitrust and Meeting minutes acceptance
2022R1 Release work
Working on Proof of Concept
Mike walkthrough of VINDecoder/VehicleInfoLite with Reference and Bundling
Work on the Architecture Guideline to help people understand the flattening
Work on Party and ClaimInfo
Participants
Paulette Reed (Scribe)
Chrisa Hickey
Andy Bober
Dan Webster
Mike Hastings
Jeff Schroder