Date

12 Jan 2023

ZOOM Meeting Information:

Thursday, Jan. 12, 2023, at 9am PT/12pm ET

Join Zoom Meeting

Meeting ID: 790 499 9331

Attendees:

~~Ken Sayers (AAIS)~~

I. Introductory comments

A. LF Anti-Trust statement

B. Personal Intros by Attendees

II. Meeting Business

A. Need for a Chair on Architecture working group

SB: met this past monday - made great progress last year, anticipating great progress for 2023
SB: We want to have two chairs for the AWG following Satish's departure.
SB: We most need someone to lead arch. discussions, from the community. This will be noted again at the AWG on Monday.

B. PA: RRDMWG Update

Going very well - great engagement from carriers
Significant progress 2022 - auto stood up and working.
Just before NYE a prelim. extraction pattern for homeowners, and test data loaded
Now investigating commercial auto. loads with the same stat plan as personal auto but there is a different interpretation
Sourced test records for commercial auto, looking into schemas and converters and test data for CGL
Happy with work with Senofi getting postgreSQL DB set up - close to being able to satisfy data calls in a fulsome way.
We anticipate getting schemas done in the next year. No visible obstacles.
Personal auto took a year to set up but Homeowners only took about a month.
We're aiming for a month per line moving forward.
AT: clarified/asked about rollout plan (implementation plan) moving forward. JB: on a technical side: we need to establish the steps necessary to get connected to technology and in some case (eg. Hanover) convert/map data to AAIS format. 50 state rollout question will be determined thereafter. No timeline in place yet; JB noted that individual member setups will be forthcoming soon, and we will do individual carrier discussions/followups.

C. Peter Antley: end-to-end demo discussion

Internal stat reporting using everything we're doing with AWG - moving along, no obstacles
PA has been working with Senofi - we got new HDS functional, created and responded to data call, generated a report with only minor tweaks
We're working on demonstrating our success via a short video 'Responding to a Data Call with openIDL' (working title). We'll talk about the network and its general operations and respond to a data call within the video.
Demo will be run on live test net and video produced against this

D. North Dakota Updates (SB covering for Ken Sayers)

Moving forward - rec'ing data from carriers - will run data call first 10 days of February for data in month of January. (4 weeks from now

E. openIDL Test Net - JB

Continuing to report with stat reporting POC
We've done database conversion to PostgreSQL
Will be reaching out to get test data and looking at how carriers can be using this in the next quarter
We'll also be looking at defining joining process/Certificate Authority process
We'll be working on deployment tools

F. Infrastructure Working Group

Begins Thu. 1/19 - kickoff call - every other week from TSC same cadence and time
Purposes
1. OSS project management - repos for openIDL will merge in future - this group will manage that.
2. Network separated from application layer
3. Definition of maintainer policy
4. PM policies for openIDL will emerge from this team
5. This group will also be responsible for network operations. Second major priority for this group to define policy & rules surrounding network ops.
6. Two chairs will be selected and leading discussions
7. Chainyard and Senofi will be at center of group as infra partners.
8. IWG will also be taking recommendations to the Technical Steering Committee.

III. Adjournment - Meeting adjourned at 12:27pm.

Time	Item	Who	Notes