🔓 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 and Meeting minutes acceptance
🥁 Doodle Poll Results
Hollander Accepted Architecture Committee Proposal
Work on VIN Decoder API
Work on Simplifying Vehicle Info with the information Mike investigated
Emerging Technologies New Code List Values for Options
Meeting Minutes
Antitrust Accepted
Meeting Minutes Accepted
The Doodle results had the most committee Members being available on Tuesdays from Noon - 1 CST.
The meeting time will be updated for the occurrence
The September 14 meeting will be cancelled due to CONNEX
Hollander accepted the Architecture Committee’s proposed changes to the Code List.
Work on VIN Decoder API
Mike previewed the new Schema for VIN Info that only has the data needed for the VIN Decoder.
There would be 12 New Data fields and 6 new code list
The Question was raised if we need the new data in the XML Vehicle Info
It was determined that we do not need to keep the data in sync between the new approach and the BMS.
Mike will work on moving the new Schema to Stoplight.
Dan recommended that we change string instead of numeric for the Year data type
Once the team has a solid proof of concept, The VIN Decoder will be taken to the VDI Committee to review and approve.
The work being done at this time, is work to prove the Architecture Committee PrincipalsPrinciples
The most current roadblock is deciding if slimming down the BMS Data Aggregates by removing Hierarchy is enough, or do we need to remove fields that will not be used in one message but may need to be used in another message. Questions are, do we bundle, do we make Vin Info, Vehicle Info, Vehicle Tow Info, Vehicle Estimate or do we just make the fields for each message and we will have numerous Vehicle Info? This is the topic we need a good forum to meet on and discuss.
Committee Members
We hope with the new timing of the meeting that we will draw more attendance. It would be nice to get some more technical people that have worked with open API so we have more experience.
It was recommended to reach out to Becky and see if we could get her back on the committee.
Great Meeting everyone
Up Next
Antitrust and Meeting minutes acceptance
Meeting was move to Microsoft Teams Meeting
Review New Options Code List for Emerging Technologies.
Discuss Bundling
Discuss data aggregate structure of smaller more useful aggregates.
Work on Vin Decoder
Participants
Paulette Reed (Scribe)
Mike Hastings
Jody Prather
Jeff Schroder
Joanna Cohen
Paul Barry
Dan Webster