2024-06-11 Architecture Meeting Minutes

Public Page

Date: Jun 11, 2024

Agenda

• Network/Welcome

• Antitrust

• Review Meeting Minutes

• Work on EMS to BMS to CAPIS Conversion document

Meeting Minutes

• Network/Welcome

• Antitrust Statement & Recording Accepted

• No meeting minutes from last meeting

  • It was a work meeting, and all updates were made real time to the EMStoBMStoCAPIS conversion document.

• Meeting Minutes

  • Info being removed from names

    • We do not currently have a rule, but we have removed “Info” from several property names, such as ClaimInfo is now claim and VehicleInfo is now vehicle, we have come across other names with “info” and just wondered if that was a rule.

    • It is believed that in some cases, info will need to remain and others it can be removed.

    • Recommendation: Aggregate/object names ending with Info or Details are often the "extraneous levels of hierarchy" discouraged by our JSON style guide. Such Objects should be flattened away if possible, and if Objects are not flattened away, the "info" portion of the name should be removed.

      Unless otherwise required to remove ambiguity, "info" is not needed as part of a property name.

  • Reviewed Chris Poulos examples of APIs that were created with BMS fields.

    • There is information that was flattened and removed from CAPIS such as documentInfo was removed, AdminInfo was flattened and its children promoted

    • EventInfo has different event information, such as AssignementEvent, Estimate Event, etc.

      • EventInfo can be flattened, and the children will be promoted up.

  • Committee Work

    • Could we send the XML implementation Guides back to the committees to get them to convert to API

      • The CIECA Implementation Guides have more data than the industry uses, because they are used to test. There are recommendations, however, some are not true industry solutions.

      • The Architecture team is working through the high level conversion and proving the concepts of flattening and zero based budgeting. There are experts for many of the industry segments in this committee and have ask them to look at the naming and possible flattening first.

        • The difference in CAPIS and BMS is that we are not leaving things in that are misspelled and we may make changes that impact future releases, we are not guaranteed backward compatibility.

        • The Committee’s will review the work and much like the VDI committee, they are doing the same process as Architecure with the EMStoBMStoCAPIS conversion document and then they will propose API.

        • The Referral and API work was done before this, and we will have to review and make recommendations based on the Rules we have set.

        • The style guides ultimately get converted into API endpoint schemas.

        • At this time, the Data Dictionary is being converted by architecture as primary goal and not working on flattening with Architecture.

        • The VDI committee is doing the same work.

  • Homework

    • If you review the same fields as someone else, please initial and list any concerns in the notes and we can focus as a committee the concerns and not all the ones we agree are good.

Great Job

Up Next

• Network/Welcome

• Antitrust

• Review Meeting Minutes

• Update on Committee Process with new API work and Architecture Goals

• Mike to display Part Price and File Attachment

• Continue with EMStoBMStoCAPIS conversion.

Action items

Decisions

Reference

Participants

• Paulette Reed

• Dan Webster

• Andrew Bober

• Mike Hastings

• Chris Poulos

• Chris Martinez

• 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