Public Page

2023-02-28 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Mar 07, 2023
2 min read

Public Page

Date: Feb 28, 2023

 

 

 

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

  • Network/Welcome

  • Antitrust Statement

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

  • Review Meeting Minutes

  • Dan’s Scheduling

  • What's going in CAPIS April Release

  • Sneak Peak into AI

  • Technical Call to Action

    • BMS Flattening

    • BMS Named Value Pairs

    • Telephone

    • Address

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes Reviewed and Accepted

  • Dan’s Scheduling

    • Dan has morning appointments the next few weeks, but at this time plans to still attend the Architecture Meeting(s).

  • April Release

    • Implement Flattening

    • Fix Structure so Schemas work

      • Andy has a fix

    • Work on Jiras

    • Get Contacts moved in

  • We want to declare elements we want to use in the schema and not having alternative ways to do the same thing.

  • Use Discipline, we don’t need 250 country codes in our Code List.

  • Between CIECA releases, teams can implement changes and bring them to CIECA to get in the next release.

  • Looked at the AI JSON message.

    • This showed how Company ID and UUID were being used with messages now.

    • Reference ID is used to associate the request and the response and then identifies a claim or a car and sends a bunch of pictures or videos to get an estimate.

  • Phone Number

    • We will have two properties; one will be a number pattern and the other is the extension. The phone number uses the international telephone E164 format with the optional plus sign with the country code.

  • We no longer need the ID Array with ID Qualifier and ID Num

    • We do not need all of the ENUMS to begin with, we will start with the zero-based budgeting concept.

  • Address will be the same as ID Array, we will have a BILL-To Address and a ship to Address instead of having an enum to specify the type of address it is. Same with Phone number.

    • Preferred phone number Boolean in the BMS

    • A reason to keep this explicit is for two factor authentication.

  • Call to Action to be on the Architecture Committee

    • We finish the April release and reach out to get a consensus from the technical folks a few weeks before the QA.

Great Discussion everyone

Up Next

  • Network/Welcome

  • Antitrust

  • Review Meeting Minutes

  • Review 2 factor authentication example

Action items

Decisions

 

Participants

  • Paulette Reed

  • Mike Hastings

  • Andy Bober

  • Dan Webster

  • Paul Barry

  • Jeff Schroder

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. https://cieca.atlassian.net/wiki/spaces/ARCH