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:

I. Introductory Comments

A. Mr. Antley - welcome to everyone

B. Mr. Antley - Reading of LF Antitrust Statement

II. Agenda

A. Mr. Antley - Recap 

  1. Shift from Mongo to PostgreSQL
  2. We talked about test data set from Mr. Harris - great progress with premium records. Premiums loaded, calculated EP with PostrgreSQL setup. EP came out to same values that Mr. Harris made and his corresponding documentation
  3. Next hurdle with PostgreSQL - working with the loss records. Loss records have been loaded over the last week into Postgres  - we made a postgres table and loaded them.
  4. First big milestone: producing outstanding records - i.e., how much money is outstanding. Records usu. released quarterly. One that is most important is the most recent outstanding when calculated. 
  5. 'Valid records' - most recent record wrt occurrence that is also paired with coverage. We had a certain # of valid records. Also defined something called a 'Stale record' - i.e., an older record replaced with a newer record.
  6. Wrt outstanding records - PA split groups up correctly with same number of valid and stale records. An issue where summing the amt of losses is producing aberrant results. PA handed this off to data engineer who indicated that he fixed it.
  7. Last week - we discussed adjusting numerical precision, and having it set to 6. All code has been adjusted accordingly.
  8. Also last week, we discussed the fact that postgreSQL didn't allow for camelcase for attribute names, so PA updated all of tables
  9. We also talked in AMG about  using 2 schemas in database - master scheme (openidl_base - raw transaction. records loaded here) - extraction pattern schema (openidl_EP). New tables modified have been pushed into these. PA: will be reviewing some of finer details in the following week as gaps are closed between the expected values and the actual values. 
  10. PA: very pleased at the speed at which they've caught up with the translation into postgreSQL

B. Questions fielded from group (none presented)

C. Looking ahead (Mr. Antley shared a report, here)

  1.  PA has finished EP column, working on car years. Working on breaking out additional columns
  2. Will be working outstanding loss. 
  3. In next week columns should be broken out. 
  4. PA Has worked out bodily injury, property damage, earned premium, car years. 
  5. Getting closer and closer to the report we're ultimately working toward producing. 
  6. PA noted that current report isn't broken out by state.
  7. A little bit of refining is forthcoming and we will be producing additional reports.GMT20221028-170234_Recording_1920x1080.mp4

With no additional matters, Mr. Antley adjourned the meeting at 1:18pm EST.


Discussion items


Action items