Date
This is a weekly series for The Regulatory Reporting Data Model Working Group. The RRDMWG is a collaborative group of insurers, regulators and other insurance industry innovators dedicated to the development of data models that will support regulatory reporting through an openIDL node. The data models to be developed will reflect a greater synchronization of data for insurer statistical and financial data and a consistent methodology that insurers and regulators can leverage to modernize the data reporting environment. The models developed will be reported to the Regulatory Reporting Steering Committee for approval for publication as an open-source data model.
openIDL Community is inviting you to a scheduled Zoom meeting.
Join Zoom Meeting
https://zoom.us/j/98908804279?pwd=Q1FGcFhUQk5RMEpkaVlFTWtXb09jQT09
Meeting ID: 989 0880 4279
Passcode: 740215
One tap mobile
+16699006833,,98908804279# US (San Jose)
+12532158782,,98908804279# US (Tacoma)
Dial by your location
+1 669 900 6833 US (San Jose)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 929 205 6099 US (New York)
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
888 788 0099 US Toll-free
877 853 5247 US Toll-free
Meeting ID: 989 0880 4279
Find your local number: https://zoom.us/u/aAqJFpt9B
Attendees
Goals
Meeting Minutes
- Megan Ebling
- Ken Sayers
- Dale Harris
- George Bradner
- James Madison
- Susan C.-by phone
- Allen Thompson
- Ash Naik
- Jeff Braswell
- Kevin Petruzielo
- Kristin McDonald (Deactivated)
- Libby Crews
- Matt Hinds-Aldrich
- Melissa Pereira
- Michael Payne
- Mike Nurse
- Nathan Southern
- Nike Vitale
- Ryan Blakeney
- Stephen Lee
- Truman Esmond (Deactivated)
Meeting Minutes
- Anti Trust Policy notice reviewed
- Data Modeling
- Technical Considerations discussed
- RDS, not NOSQL. Traditional ANSI SQL makes sense
- Min ANSI requirements reviewed
- Model Layers discussed
- Goal: Flat dictionary to something that can be used
- James Madison: On spreadsheet: groupings to get to entity-relation model
- 4 layers: physical table layer, need machine efficiency, will not look like business model.
- Today, look to get business model and the entities.
- Persistent view layer, needed for extraction table and proper data loading and question answering.
- Showed table models, just from groupings the spreadsheet
- Reviewed tables to discuss relations between tables/entities
- Can have Day 1 and Day 2 elements in the same entity
- Used business model coverage elements to show how to move between business model and data model (tables, ERD)
- Susan Chudwick says for Auto it’s all at the vehicle level.
- James Madison: Keep repeating this process for additional elements and we will get this done well and complete
- Last week’s suggestion
- Should we start with AAIS stat plans as day 1?
- Objections of starting with AAIS stat plan on HO?
- Susan has questions on timing. How long will architecture take?
- Dale wants to build existing stat plan so it can become the vehicle for stat reporting
- Unpacking values like 2 fields that become 8.
- Moving from code “01” to text “AL” for example.
- Should Auto go back to stat plan?
- Ken: first day all the same. New format not even finished, plus should do all the same.
- Technical Considerations discussed
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| Object Modeling | James/Ken/Peter | Technical Considerations | |
| Discussion to Adopt All AAIS Stat Plans | Group | AAIS stat plans have already been approved with states. Starting Day 1 attributes here is the leanest approach that will allow for Regulatory Reporting to happen via openIDL. |
...
Recording
| View file | ||||
|---|---|---|---|---|
|
Action items
- Susan – Confirm that all is at vehicle level, research UI/UM stacking