/
2024-03-05 VDI Committe Meeting notes

2024-03-05 VDI Committe Meeting notes

Owned by Paulette Reed
Mar 06, 2025
2 min read

 

Public Page

 

Date

Mar 5, 2025

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/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

  • Application Info analysis from Dan and Phil

  • Work on API Assignment

Meeting Minutes

  • Welcome/Networking

  • Antitrust and recording accepted

  • Meeting minutes accepted

  • Second Meeting in this occurrence will be sent out after this meeting, this was not done to prevent confusion from multiple messages.

  • Application Info will be next meeting, Dan was not able to attend today.

  • We are excited to have more participation this week; thank you all for attending!

  • Working on Assignment API

    • We are not removing items that are common from the EMStoBMStoCAPIS, we may flatten aggregates that are only part of assignment.

    • Values that we do not put in Assignment but are already in CAPIS, is not something that has to be removed. These fields can be looked at after all the API messages are created and if they are not used, then they can be removed by Architecture. The only thing we are looking for at this time are fields that we plan on using in Assignment.

    • AssignmentEvent will be flattened because there are other event types for Rental event, tow event, estimate event, so each of those APIs can pick the elements they want.

      • Due to assignment Event being flattened, the name for createDateTime needs to be more specific and agreed to be called assignmentCreateDateTime

    • Starting with CustomElementDate next meeting

Up Next

  • Welcome/Networking

  • Antitrust Accepted

  • Application Info analysis from Dan and Phil

  • Work on API Assignment

Action items

@Paulette Reed set up a new reoccurring biweekly meeting.

Decisions

  1. AssignmentEvent will be flattened and due to this the createDateTime will be changed to assignmentCreateDateTime.

 

Participants

  • @Paulette Reed

  • Phil Martinez

  • Don Porter

  • Paul Barry

  • Brent Johnson

  • Neil Parr-Davis

  • David McCreight

  • Robert Brooks

  • Matt Carroll

  • Jim Puskas

  • Paul Riffel

  • Mike Hastings

 

 

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

 

Related content