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

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:

Ken Sayers 

Nathan Southern 

Sean W. Bohan 

peter antley 

Hicham Bourjali

Kevin Petruzielo

Brian Mills

Mason Wagoner 

Kelly Pratt

Dale Harris 

Lanaya Nelson

Ash Naik 

Jeff Braswell 

Joseph Nibert

Mike Nurse

Rambabu Adabala


First item: Moving in the direction of prepping for a discussion on 3/27 - Mason and Peter indexing their work

SQL tables have been made - for auto data standard - reference tables are needed. A request was made wrt business users being able to interact with codes - so JSON is now being used to co-generate SQL file.

Auto program wrt ingesting test amounts of data and produce a report - team is approaching this stage

Peter will rewrite extraction pattern to fit into new pattern

He will be adding documentation and formalizing openIDL auto data standard - then AAIS will load live data into node

Homeowners is next on the agenda.

Second item: Mason Waggoner

-Working through test data and table population, an issue arose wrt discrepancy in some of codes w/i the stat plan

-One instance concerned vehicle use codes - basic question: what do we do with codes that aren't directly coded w/i the stat plan. Question arose when looking at vehicle use - a code of 9 recurrently popped up - signaling drools not up to date with vehicle use. Should 9 be accepted? A drool rule could be missing.

-There may be an addendum if 9 is a valid value, otherwise the code 9 is incorrect. 

-Conclusion of the group: likely an error (9) - backlog for drools may need to be created.

-9 may have gone through since it flew under the threshold

-Dale agreed to send a message to Susan and Reggie inquiring about special exceptions for vehicle use. 

Looking ahead:

Mason will be working on homeowners and filling out that spreadsheet

A detailed plan will be ready the end of April

Peter has largely finished the decoding job. His goal is to rewrite the extraction pattern they had that worked against the old data standards - the pattern will be updated, sent to Tornquist after Jenny finishes the NAIC filing, and once Peter gets clearance - PA will document all of his work with personal auto and bring it back to this group

AAIS is providing a reference implementation for serverless data load relying heavily on AWS. Drools will be central to the validation. Using a react interface, lambdas and EFS - a parallel load and validate into a stage. 



Discussion items


Action items