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
...
- Eric Lowe
- Dale Harris
- Mike Nurse
- Jenny Tornquist
- Wanchin Chou
- Andy Case
- Reggie Scarpa
- Ash Naik
- Ken Sayers
- Bourjali Hi
- Kristin McDonald (Deactivated)
- Chudwick, Susan R
- James Madison
- Tahoe Blue
- Nathan Southern
- George Bradner
Goals
Meeting Minutes
I. Opening
...
II. Agenda - Data Modeling and Internal Data Work - Mr. Antley
Mr. Antley pulled up dialogue - graphic on earned premium - Greg W. spoke about car years last week
Mr. Antley: we want to discuss concept of business layer
Stat data as it is gives us what we need to do regulatory reporting. Specified accounting date and duration - clarification of coverages and exposures.
When we consider requests brought to us, some terms are brought up repeatedly: EP, incurred premium, exposures and premiums incurred and written, average expenditures and premiums, loss ratios, underwriting expenses, etc.
Today: we take input records and process those records and calculate all of these categories (various figures) on a quarterly basis. In current mode, grouped by policy and by quarter. Select queries feasible - yield year outputs. Calculations = aggregations.
In AWG: discussing what is the right level and how to set up HDS to make accessible to regulators without A. Overview/Recap
- Discussion of data modeling and what idl project is doing with data. Concerned that discussions may be becoming overly technical. Wants to dial the tech speak down a bit
- Pulled up graphic on Earned Premium - 3 columns: Input / Business Layer /Output
- Noted that last week, Mr. Williams led a discussion on car years.
- Also noted that he led the discussion on business layer - wants to revisit and continue this.
B. Business Layer
- Re: Input, Stat plan as it is gives us adequate data to do regulatory reporting, and we can ingest most of needed information:
- Accounting date
- Duration
- Coverages and exposures
- Re: Output: some of the terms for which people are asking (presented examples here): e..g, Earned premiums, car years, incurred loss, earned/written exposures and premiums, incurred claims/losses, calculated ratios, average expenditures, average premiums, underwriting expenses.
- Mr. Antley: the way they solve (@AAIS, in his warehouse) these questions today: they take the input records, process these to be centered around the idea of a policy, and then calculate: earned premium, paid loss, incurred loss, outstanding losses, earned exposures, paid claim counts, outstanding claim counts. They calculate all of this on quarterly basis. Sits and persists in data store on level on which they are making reports, they have these terms, grouped by policy, calculated by quarter. If x person asks "what is my earned premium for the year, for these kinds of coverages," he does a select query that does filters and aggregates and produces year output. Data on a policy and quarterly basis with the premium after it has been earned.
- In AWG: Discussion - how do we set up HDS so it is accessible to regulators, sans putting undue burden on rest of system
...
- ?
- Pointed to base layer, from which we
...
- answering questions. How do we make it accessible to
...
- the persons making queries?
...
- Quarterly basis
...
- reports right now -→ fairly easy and straightforward
- Mr. Antley
...
- solicited thoughts/suggestions from group about what the data layer will look
...
- like
- Mr. Sayers: when looking at data layer, we must ask visibility to whom? Carriers e.g., want to see stat plans eventually with more data. Can we put this in HDS per Mr.
...
- Braswell's suggestion? Data layer could be an ephemeral pass-through that is part of the extraction pattern, or a standing entity where ETL transforms stat plan. Key questions: what are we asking the carriers to prove, and do they care about any format other than the stat plans?
- Mr. Antley: who are the voters in this RRDMWG? We have carriers, and we have regulators. Another critical question: if we just look at the easiest way to load this, and say, the carriers can just be done with loading the stat records, at this point who is tasked w/turning the stat records into a query that makes sense for the regulators? Without relying on regulators to expend the energy/effort into turning records into something useful?
- Mr. Sayers: There is discovery here. We start from the stat plan - may want to make it less codified to make it more workable, but it can be a perfectly viable raw material. We can throw some reports at it however and say how difficult is it to get from the stat plan data to this report?
- What are we asking carriers to provide and do they care about formats other than stat plans
Mr. Antley: carriers vs. regulators. For him, critical question: who is tasked with turning the stat records into a query that makes sense for regulators?
...