Public Page

2021-02-2 Architecture Meeting Minutes

Public Page

 

      
   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

 

Date

Feb 2, 2021

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

  • Continue to work on the CAPIS Business Plan.

    • Update on findings from Charley’s folders that JSON did not have its own charter or Business Plan, it was handled under Architecture’s.

    • Start with Deliverables section.

Meeting Minutes

  • Antitrust Accepted

  • Meeting Minutes approved

  • It was ask to look at the JSON Charter from the past JSON projects.

    • I reviewed Charley’s folders and CIECA.com and JSON was handled under the Architecture Committee Charter in past projects as well, there is no Committee Charter or Business Plan for JSON. There are several working documents and meeting minutes under the JSON folder that if the committee would like to review we can.

  • CAPIS Business Plan

    • Deliverables

      • A High level section was provided to bring out discussion of the deliverables that the committee would like to complete.

        • Guidelines for API/JSON messages for other committees to follow

          • formalized http verbs

          • use standardized data types in JavaScript

          • flexible implementation of Use Cases

          • what drives non standards messages and a way to provide solution

        • CAPIS(CIECA API Standards) Documentation

          • Use Cases - An IG Appendix C to provide business use cases for system developers

          • Flow Charts

          • An Implementation Guide (IG) to define the business information

        • JSON messages

          • Schema

          • Test Instances

      • It was agreed that the list was good, but we needed to change JSON messages to Open API Specs and add Data Types and Code Examples to that list.

      • Discussion on how to move forward with documenting

        • Do we need to have rules and guidelines for building JSON messages (such as Chapter 2 of the BMS)?

          • If we use Open API Framework and use a tool such as Swagger to document, we should not need a section like Chapter 2 of the BMS.

        • We reviewed the sample of Swagger and how it documents.

          • Does Swagger/Smart Bear allow for Private accounts where a person would need to login to use the content.

            • It does look like Private API is available in Swagger Hub, more research will be done by CIECA staff.

        • Questions were arose if we should use Wiki docs.

          • CIECA.com is still looking for a new provider and hope to find a solution soon.

        • Reviewed a Confluence Use Case that was initiated to document services.

      • What message do we start with

        • Discussion of assignment and parts

          • Need to start with a popular message that will help many areas of the industry.

          • Need to start with a simple message.

          • Do we have any request for messages in JSON?

          • Assignment has a large number of the data elements that would be used, and would be the start of the collision process.

          • A vote was taken for the Architecture Committee to create Assignment for first JSON service, we had a consensus on starting with Assignment.

        • FNOL

          • It was then discussed that First Notice of Loss would be the start of the collision process and maybe we should start with FNOL.

          • The team worried that members of Architecture was not familiar with FNOL.

            • We do have a few members that are familiar with FNOL.

            • This is an example that the FNOL team can build off of, this is version 1.

          • A vote was taken for the Architecture Committee to create FNOL for first JSON service instead of Assignment, we had a consensus.

    • A CIECA Use Case Example was shown to the team to get feedback on the starting with a Use Case.

      • The Committee agreed this would be a good start, they would like to see swim line flowchart added to the Use Case.

      • Due to time restraints, Paulette will take information from the existing Appendix C and FNOL documentation to come up with a draft Use Case to be reviewed in the next meeting.

    • CIECA staff will look into Swagger and Confluence diagram applications.

Have a great week everyone!

Up Next

  • Antitrust and Meeting minutes acceptance

  • Continue to work on the CAPIS.

    • FNOL Use Case

  • Standardize Percentage definitions question (Becky)

Action Items

Decisions

 

 

Participants

  • @Paulette Reed

  • Paul Barry

  • Jeff Schroeder

  • 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