Public Page
2021-01-19 Architecture Meeting Minutes
- Paulette Reed
Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
Jan 19, 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
Review proposal to be sent to all the committee’s to inform them of the Code List Changes.
Kickoff JMS
Meeting Minutes
Antitrust Accepted
Meeting Minutes approved
The Announcement of the Code List Sync Initiative was approved anonymously and will be sent to all committees.
JMS (now CAPIS) Kickoff
Originally the JMS initiative was being treated as needing a new committee. However, after a review of the CIECA SDM document, the CIECA staff felt that the Architecture Committee could do the work because it falls under the CIECA ARCHITECTURE COMMITTEE CHARTER.
The Architecture Committee Reviewed the SDM and agreed the API development could be done under the CIECA Architecture Committee and the current Charter.
Started working on the CIECA API Standards Business Plan
Most of the information was captured in the Business Plan itself.
The process of working with Data Types and Objects and picking the most used Data Types to start create the objects was discussed.
Party Type
Address
Borrow from JSON Standards Objects
Which messages will we start with?
Vehicle Repair
Assignment
Procurement
Estimate
Procurement is very complicated in BMS and not used often because of its complexity, so should we start with it?
Framework of API needs to be defined by Architecture Committee.
Data Types should be more standard to and use JavaScript.
This project was to stay away from duplicating the BMS as the first attempt of BMS did.
We will add a history section to the business plan that discusses how we created JSON messages off the BMS and it moved the complexity and size to JSON, which defeats the purpose of using JSON.
Paulette will add a History and Objective section to the Business Plan for review of the next meeting.
Naming of JMS
The topic was brought up if the name JMS was correct for the project. If we are trying to follow the previous standards of EMS and BMS, maybe JMS is okay, but the concern is our standards have not used the implementation of the standards before. EMS was not dBase and BMS was not XML, so do we want this to reflect JSON?
Paul let everyone know that he was just using JMS because it did follow the other path, but he was open for discussion to other ideas.
CIECA API Standards (CAPIS) was unanimously voted into approval.
Up Next
Antitrust and Meeting minutes acceptance
Continue to work on the CAPIS Business Plan.
Standardize Percentage definitions question (Becky)
Action Items
Decisions
Participants
@Paulette Reed
Andy Bober
Dan Webster
Mike Hastings
Phil Martinez
Paul Barry
Jeff Schroeder