2024-05-09 Estimate (VDI) Committe Meeting notes

Public Page

Date

May 9, 2024

Agenda

• Welcome/Networking

• Antitrust

  • This meeting is subject to the terms of our anti-trust statement shown here.  In addition, this meeting may be recorded. 

• Meeting Minute approval

• Continue Review EMStoBMStoCAPIS document

• Next Steps

Meeting Minutes

• Welcome/Networking

• Antitrust and recording accepted

• Meeting minutes accepted

• EMStoBMStoCAPIS

  • Looked at Degrees and the first versions of CAPIS had these zero based budgeted and just using coordinates with latitude and longitude, again, if degrees is needed, we just need an example, and we can add the elements back.

  • In looking at the different aggregates under EventInfo, we see industry specific events, and this was due to 25 years ago that we created hierarchy to prevent the aggregates from being too large, however, the concept with CAPIS is to remove these levels of hierarchy and you select what you need.

    • This committee will look at the aggregates that work for assignment and Estimate, therefore, rental, salvage and others will need to be looked at by those area experts.

    • Dan Webster presented in the April Technical Webinar, CAPIS Architecture design. If you are interested in CAPIS or just making Dan famous, please go to cieca.com and watch the webinar.

  • File Attachment in CAPIS is missing some key BMS elements

    • With the file attachment in CAPIS would we send a binary as the image or would we send a URL

      • The idea with current CAPIS standard, would be if we have file attachment then there should be an instance filee where we have an endpoint.

      • It does look like File Attachment can use some work

      • If anyone uses File Attachment with JSON, we would love to see your examples, we will also look at the other committee recommendations.

  • Reviewed a few of the rules we have in CAPIS

    • we have an abbreviation list, where we will always use num instead of number, but we also have a rule to watch how we use number because sometimes it should be qty.

    • In CAPIS we are removing the name value pair concept. In the BMS we had IdInfo and under that we had a field that identified, normally with a code list, what type of ID it was, CompanyID, TaxId, UserId, where now with CAPIS we will have companyId, taxId and userId.

• Use Cases Discussed

  • Initial Customer contact was discussed as if it was needed for assignment/estimate

    • An assignment may have been received and later, an industry user may want to know when the customer was first contacted and send a request to get that information.

    • The initial customer contact time may be sent by the insurer and they start a clock at that point. The Body Shop might want to know how long it has been since the initial contact because they have an SLA to contact them within # hours.

  • Inspection Completed

    • We need to look that there are things that would not be on the initial assignment, but something that would be requested about the assignment later. Therefore, with inspection completed, that of course would not be a value sent on the initial assignment but would be a value you would expect on an assignment status inquiry.

• Made it through to O’s and we will start on Ps next meeting.

Great Meeting Everyone and Thank you for your participation. Have a great week!

Up Next

• Welcome/Networking

• Antitrust Accepted

• Work on EMStoBMStoCAPIS document starting with Ps

Action items

Decisions

Participants

• @Paulette Reed

• Tom Julius

• Dan Webster

• Bud Center

• Neil Parr-Davies

• Josh Steere

• Ross Whiteley

• Paul Barry

• Phil Martinez

• Todd Balan

• Jason Norman

• Michael Alarie

• Candy

• Javier

• Stacey Phillips

• Candace Everitt

• Richard Bardan

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