Public Page

2022-2-8 Architecture Meeting Minutes

Owned by Paulette Reed
Feb 09, 2022
4 min read

Public Page

 

 

Date

Feb 8, 2022

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

  • Work Session

    • Dan Excel Document

    • Different Subsets of VehicleInfo

      • Strategy of coming up with subsets

 

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Accepted

  • Hierarchy

    • We have been working through the best practices of moving from the BMS Data Dictionary Aggregates to the JSON Schema. With VehicleInfo we started with the all the fields and aggregates and then we shortened it with the VINDecoder, which was a lite version of VehicleInfo.

    • In working through the process, we have found we could have instances with or without hierarchy name.

    • Hierarchy is a familiar concept to everyone using the BMS.

    • Last week we had a breakthrough with using reference and the bundling tool.

  • Directory moving forward

    • Recommendation that a directory approach be created to store the test instances and the bundling.

  • Flattening

    • VehicleInfo has VINInfo and from there VIN Aggregate that has 5 fields. Some of those fields were decided that we did not need for our new VehicleInfo and VINNumber was the only field that was kept.

    • With the new Reference and Bundling availability do we want to remove fields that were used in previous and break possible releases because it will not be backward compatible?

      • This is a new Product and is not intended to be backward compatible.

  • Common Types

    • We want to make sure that all common data aggregates are referenced and not copying and pasting.

  • New API messages will reference Simple Types, Common types and code list.

  • Why are we not using a tool to convert the BMS to JSON

    • We attempted to do this and the BMS schemas were so large and causing issues with implementation and testing instances.

  • Need Rules for Flattening

    • We need Architecture best practices before we turn these over with the Product Committees.

    • Could we just turn over what we have and allow development and allow those committees to bring back to the Architecture Committee to get approval?

    • Things to think about

      • How the backend database is structured in categories (Vehicle, VIN, License) and it would be easy to keep aggregates that have this group.

      • JSON does not structure and keep sequence which the applications do not care about, however the developer that is reading to analyze and troubleshoot could use the sequence.

  • Next Steps

    • Mike is working on converting his VINDecoder Vehicle Lite using the reference and bundling. He is having some issues with Git and StopLight syncing, but when that is resolved he will share his updates as a proof of concept with using the Reference.

    • Work on Documentation to help Committees follow the Guidelines and concepts, the more committees you let start working, the more variations of the truth we will get if we do not have the Guidelines solid.

    • Party

      • Party was part of AdminInfo and you had to include all of AdminInfo in the BMS, this was large and one of the reasons we discussed flattening.

      • We could flatten to the last Aggregate in Dan’s Excel sheet?

    • Work on Party and ClaimInfo

    • Need Cute Avatar for CAPIS (Digital Dan). We could work with Stacey and the Marketing committee to create an Avatar competition.

 

 

Great Meeting! Here is the recording of the meeting and reference documentation provided in the meeting:

 

You can also access all Architecture Committee Work Documents in Confluence: Work Documents

Up Next

  • Antitrust and Meeting minutes acceptance

  • Working on Proof of Concept

    • Mike do a 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)

  • Dan Webster

  • Mike Hastings

  • Andy Bober

  • Chris Poulus

  • Jeff Schroder

  • Paul Barry

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