Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
CIECA 500 Westover Dr #11617; Sanford, NC 27330
Date
| Info |
|---|
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
Discuss New Meeting Occurrence
Architecture Guidelines Review
DamageType code; the * was tested in the test instance and valid, do we still need the Z that was there to replace the *?
Application Info repeating? - How (In messages: claims save message, evaluation messages, Inventory message, vehicle damage message).
3.6.4 Deductible Info has option XOR, but its Not in schema(backward compatibility) needs XOR to be removed and both be optional.
VehicleDamageEstimateChangeRq, Add Calibration?
Compare the Schemas to show the differences.
Go through the new items that need to be spelled checked to get approval of spellings and added to the list.
Review of the JSON Draft Provided from Stacey (When Ready).
Farewells to Charley as this will be his last Architecture meeting.
Meeting Minutes
Antitrust Agreed
Minutes from pervious meeting accepted.
With Charley’s retirement, the current meeting will cancelled and a new meeting will be created.
Committee agreed that the same day and time would be good for the new meeting occurrance.
Damage Type Z was created asterisk(*) but since asterisk(*) works do we want to replace it?
Asterisk(*) was seen as an invalid code that would error the schema, so it was proposed that we would add a Z code to reference the ZZ unspecified code in other applications.
Asterisk(*) is seen as a wildcard.
There are many applications that use asterisk(*) as wildcard/unknown/not specified.
It was agreed that asterisk(*) is valid and should be used instead of the newly proposed Z code.
Architecture Guideline Review
Review will continue offline and follow up next Meeting
👏 👏 Thanks for All Your Hard work Charley, you are going to be missed! 😢 Stay in touch and stay safe!
🤔 Great Meeting Today Everyone. Thanks
Up Next
Antitrust and Meeting minutes acceptance
Spelling Update Paragraph(s) to be replaced by the process for backward compatible.
Discuss the offline Review of the Architecture Guideline changes .
Application Info repeating? - How (In messages: claims save message, evaluation messages, Inventory message, vehicle damage message).
3.6.4 Deductible Info has option XOR, but its Not in schema(backward compatibility) needs XOR to be removed and both be optional.
VehicleDamageEstimateChangeRq, Add Calibration?
Compare the Schemas to show the differences.
Go through the new items that need to be spelled checked to get approval of spellings and added to the list.
Review of the JSON Draft Provided from Stacey (When Ready).
Action items
- Paulette and Charley will provide the updated Architecture Guideline document to the committee members.
- Architecture committee members will review document and discuss any changes or modifications with Charley before Friday.
- Paulette Reed set up new Architecture Meeting Occurrence.
Decisions
- Damage Type asterisk(*) will remain and Z is no longer going to be added to 2020R2.
Participants
Paulette Reed- Facilitator/Scribe
Andy Bober
Dan Webster
Chris Poulos
Jeff Schroder