Public Page
2021-01-12 Architecture Meeting Minutes
Public Page
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
Jan 12, 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.
Currently have codes with 4 characters, however, we are running out of Labor Codes and we need to look at the impact of moving this code to 5 characters.
Standardize Percentage definitions question (Becky)
Changes to the Architecture Guidelines from QA and description change for code list value update.
Meeting Minutes
Antitrust and Meeting minutes acceptance
Review proposal to be sent to all the committee’s to inform them of the Code List Changes.
Reviewed two new codes in the sync spreadsheet that were not discussed and found when creating JIRAS to do the work.
OTDP Other - is under Total Type code list. Nobody was aware what this code was and why the description was not complete.
Need to find more information on this code before adding it to other code list or deprecating it.
The Code is not in History and does not have a release or any documentation that can be found.
OTTR code for Total Type code list description will be changed to be in sync with the other list descriptions.
The Announcement Proposal to all the committees of the new code list changes was reviewed.
Need to identify the first codes as existing codes in other list, but added to this list.
Currently have codes with 4 characters, however, we are running out of Labor Codes and we need to look at the impact of moving this code to 5 characters.
It was decided that 4 characters were enough and we should continue with 4.
Standardize Percentage definitions question (Becky)
From memory of the QA meeting, this was for negative and positive percentage values, but it would be nice to have Becky in the meeting when we discuss a resolution.
Changes to the Architecture Guidelines from QA and description change for code list value update.
The changes to the Architecture Guidelines were approved.
Negative Test Instances
Andy put a structure in place to allow for negative test instances to be added to the build.
The existing negative test cases are scheduled to be added in the 2021R1 release.
At this time, any committee wanting to add a negative test case, can submit a test instance and we can review it, and get it added to a list, but with the JSON effort, we will be building new test instances and will be focused on that.
JMS Committee
The committee will be kicked off after the Board meeting.
The thought was Architecture committee would be doing the first messages and setting the architecture of the JMS and then we would move it to specialized teams.
The invite to all committee members will be sent in case there is someone that has extensive knowledge of JSON and would like to share this knowledge and help in the initial process.
The Architecture Committee members will be critical in this process, but we are keeping them separate in hopes that people will be able to join and participate.
The Confluence Site has been created for the JMS Committee, if anyone would like to start looking at it. We are also adding JIRAS to build the steps we need to take for the committees.
Hopefully members will show interest and next week a doodle will be sent to find the best time for the committee meeting and we can get the meeting invites sent out.
One of the key items that need to be discussed is how we document and where do we store the JMS documentation.
Today CIECA.com and DropBox is used for the documentation. This is cumbersome and hidden under committee pages and sometimes it can be hard to find the information you are looking for.
A suggestion of creating documentation based on the message instead of by committee was made. For example, Assignment would be an area and Estimate would be an area.
The suggestion of confluence, Wiki pages and Swagger was mentioned for tools for documenting.
Meeting was adjourned early to give everyone some time back and continue to have a great week.
Up Next
Antitrust and Meeting minutes acceptance
Review proposal to be sent to all the committee’s to inform them of the Code List Changes.
Standardize Percentage definitions question (Becky)
Kickoff JMS
Action Items
Decisions
Participants
@Paulette Reed
Mike Hastings
Phil Martinez
Paul Barry
Jeff Schroeder
Cindy Chapman