2020-11-03 Architecture Meeting Minutes

   CIECA 500 Westover Dr  #11617; Sanford,  NC  27330 

Date

Nov 3, 2020

Agenda

• Antitrust and Meeting minutes acceptance

• Select first message to work for JSON/Open API

  • This will set the standards for moving forward with Open API

• Changes to the Architecture Guidelines from QA and description change for code list value update.

• TotalType, LaborType and RateType Code list

  • Identify differences to get in sync.

  • 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)

• How can we handle Negative Test Instances in our process?

Meeting Minutes

• Antitrust was agreed.

• Meeting Minutes were accepted.

• With Phil and Dan being out, no decisions were made on the message we would start with.

  • Assignment and Procurement add request messages are the messages that was mentioned to start with.

  • It was discussed to look at the business flow and determine the messages.

  • Paul informed the group that the information from the Architecture Committee moving towards API development is something he is going to discuss in the CIECA Board meeting on November, 4, 2020. This is the CIECA Board strategic planning meeting and a great time to look at the future of CIECA.

  • The JSON initiative would need a Charter and project business plan.

• The Architecture Guidelines document was reviewed

  • BMS section for repeating aggregates that was worked on in the last session was accepted.

  • Code list section for descriptions not being changed and adding a new code was accepted.

    • It was mentioned that we need to clarify that adding a description to a code list that did not have a description also changes the meaning and we should create a new code.

  • We walked through some changes to the GitHub section of the document but ran out of time.

  • We do not have it defined that TotalType, PartType and Rate type need to be in sync or be 4 characters for EMS, we need to define what we want with the sync and the characters and identify it in the Architecture Guidelines.

• TotalType, PartType and RateType Code list

  • Mike and Paulette both provided documents to show the differences in the code list.

    • Brief review of the information.

      • Shows that a number are out of sync through the 3 code 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.

    • Total Type already has Codes that are descriptions and are over the 4 character code.

  • Discussed the ROE is the new standard but it may be a trademark value and should we add trademark values to our code list?

    • PAL will be changed back for Part Type to the EMS original wording.

Up Next

• Antitrust and Meeting minutes acceptance

• How can we handle Negative Test Instances in our process?

  • Andy added negative testing to the build process and pushed changes to the 2021R1 branch. 

  • The xml-test-instances directory now has two subdirectories: valid & invalid.

• Select first message to work for JSON/Open API

  • This will set the standards for moving forward with Open API

• Changes to the Architecture Guidelines from QA and description change for code list value update.

• TotalType, LaborType and RateType Code list

  • Identify differences to get in sync.

  • 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)

Action Items

Decisions

Participants

• @Paulette Reed- Facilitator/Scribe

• Andy Bober

• Mike Hastings

• Cindy Chapman

• @Paul Barry

• Jeff Schroeder

Participants in the meetings are noted for your information.  If you have questions on the committee’s activities, please contact a recent attendee. Architecture Committee