Public Page

2023-01-10 Architecture Meeting Minutes

Owned by Paulette Reed
Last updated: Jan 17, 2023
3 min read

Public Page

Date: Jan 10, 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

  • Review Meeting Minutes

  • CIECAST/CONNEX

  • Technical Support Forum

  • Review JIRAS

  • BMS to CAPIS work

    • Update on Parts

Meeting Minutes

  • Antitrust statement accepted.

  • Meeting minutes accepted.

  • CIECAST/CONNEX

    • This year CIECA has goals to bring technical speakers to CIECAST and CONNEX. Instead of having our Architecture Team show how we are using the tools Swagger Hub, Smart Bear, etc.… we would ask those companies to speak and draw a technical audience. After they have spoken, the Architecture Team would present changes to the Release or an update on CAPIS.

    • If you know of any Technical Speakers that would help draw a good audience, please send the contact information to Paulette.

    • Stacey has a number of contacts that she will be reaching out to as well and will be helping to market this concept.

  • Technical Support Forum

    • Another Goal of CIECA is to help our members with a technical support forum. We ask all Architecture members to think back to implementation pain points in the past and add solutions to those problems and ask all Architecture members to help answer questions that come in from our members to this forum.

  • Review JIRAS

    • We made it through one Jira CSSBT-9 CAPIS - Add Address Type

      • The discussion was around address1 and address2, both of these address lines have the same description, so would it be best to have them reference a generic address line type? Would Address Line 1 and Address Line 2 ever need different rules or length?

        • We don’t want to get back into using the char80 for everything that is character length of 80, however similar fields such as address line 1 and 2 we could use a common type.

        • Another example is name, we have First Name and Last Name and Contract Name, these can all be different or the same

        • There is risk for having a rule that says don’t have two common types the same.

        • We don’t have a guideline on how to work with common types. (See below new JIRA)

        • Andy is assigned this Jira to look and provide examples for the Architecture Committee to review.

      • We created Jira CSSBT-37 CAPIS - Create Guideline for normalization of Types.

        • Not Important to be fully normalized. For example, Address Line can be char80 and Address Line 2 be char80, but other non-address properties that are char80 would still be defined and not use a common char80.

        • Properties are defined exactly once and referenced thereafter.

    • Everyone should have access to Jira and can look through and update any JIRAS that they know are completed; mark as done. If you see any that you have questions on, make sure to note them for the next meeting and hopefully we can speed up the review.

Looking forward to a Successful 2023!

Up Next

  • Network/Welcome

  • Antitrust

  • Review Meeting Minutes

  • JIAR Review

Action items

Decisions

 

Participants

  • Paulette Reed

  • Paul Barry

  • Dan Webster

  • Andy Bober

  • 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. https://cieca.atlassian.net/wiki/spaces/ARCH