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.
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
Peter Antley (AAIS)
Dale Harris (Travelers)
Ash Naik
Birny Birnbaum
BourjailiHi
Brian Hoffman
James Madison
Jeff Braswell
Ken Sayers
Libby Crews
Lori Dreaver Munn
Mike Nurse
Patti
Sandra Darby
Reggie Scarpa
Agenda
AAIS progress on Auditing the math
Whats been done
Whats been left to do
Review our plans for Homeowners
Evaluate Health of Group overall
Meeting time,
Agenda
How can we do more
Should we do more?
Goals
Meeting Minutes
PA
Took data, tried to have same data on both sides
of all data, 2 numbers coming out correctly
different processes and steps to go from stat record to this page
<link to Peter's doc>
SDMA table - converts records to table design
Next action - make sure getting the same # of records starting with all the way thru system
plan on debugging car years first
JM - where does data come from?
PA - raw stat records
JM - not surprising, goes back to where the difficulty is, discussion couple weeks ago: from requirements or million little things not in the spec, basically repro logic from 4 boxes
PA - trying to come up with same end result, went over biz layer logic, doing everything at query time, very simple, was built (long time ago), lot of ETL jobs described graphicallly in ETL tool, cant just read progressive lines of code - lot of decoding, big thing wrap up events in quarters, want to copy that, lets just make it as easy as possible to load w/o mult stages - couple places doing stuff wrong, could be extracting select queries, might have less than = to, maybe greater thans, unpacking and figuring out where deviations are
DH - consider w/in transmittal table, might want gross prem and incurred losses to see if they come out equal
PA - woprking with andy to gfigure out various tables, fig out where going differently, expect more clarity
JM - what I expect, everyone likes stat records, easy to load/und, also that record gets incredibly large, why need steps along the way, idea is that bunch of stuff "we dont want this in code", thinking reverse way back into reasonable number b/w stat records and...
PA - making report, runnign alias on earned exposure column, lot of code used, start to look at