Date

ZOOM Meeting Information:

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


Join Zoom Meeting

https://zoom.us/j/7904999331

Meeting ID: 790 499 9331

Attendees:

  • Sean Bohan (openIDL)
  • Nathan Southern (openIDL)

  • Michael Sweeney (Montana)

  • Jeff Braswell (openIDL)
  • Peter Antley (AAIS)
  • Yanko Zhelyazkov (Senofi)
  • David Reale (Travelers)
  • Mohan Subramaniam (Hartford)
  • Tsvetan Georgiev (Senofi)

TSC Voting Members Attendance:

Ken Sayers (AAIS)

  • Allen Thompson (Hanover)
  • James Madison (Hartford)
  • David Reale (Travelers)

Meeting Agenda:

  1. Call to Order 
  2. Anti-Trust, Review of TSC Meeting format and Participation by TSC Chair
  3. Introductions
  4. TSC Activity Desk
    1. Architecture Working Group (SeanB)
      1. Call for AWG Chairs
      2. NO AWG CALL MONDAY 1/16 - NEXT CALL MONDAY 1/23
    2. RRDMWG Update (PeterA))
    3. AAIS Stat Reporting using openIDL internal Project (PeterA)
      1. New HDS functional, send-respond to data call, gen report is next
      2. Video: "Responding to a data call with openIDL" in production
    4. ND Uninsured Motorist POC 

      1. North Dakota is moving forward

      2. receiving data from carriers first 10 days of Feb for month of Jan

      3. Running data call based on that data after those 10 days

    5. openIDL Testnet update (JeffB)
      1. Phase 2 Discussion
    6. Infrastructure WG Next Thurs 1/19 (SeanB)
      1. Open Source Project Management
      2. Network Operations
  5. AOB


FOLLOW UP:

  •  

Recording/Meeting Minutes

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

  1. SB: met this past monday - made great progress last year, anticipating great progress for 2023
  2. SB: We want to have two chairs for the AWG following Satish's departure. 
  3. 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

  1. Going very well - great engagement from carriers
  2. Significant progress 2022 - auto stood up and working.
  3. Just before NYE a prelim. extraction pattern for homeowners, and test data loaded
  4. Now investigating commercial auto. loads with the same stat plan as personal auto but there is a different interpretation
  5. Sourced test records for commercial auto, looking into schemas and converters and test data for CGL
  6. Happy with work with Senofi getting postgreSQL DB set up - close to being able to satisfy data calls in a fulsome way. 
  7. We anticipate getting schemas done in the next year. No visible obstacles.
  8. Personal auto took a year to set up but Homeowners only took about a month. 
  9. We're aiming for a month per line moving forward.
  10. 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

  1. Internal stat reporting using everything we're doing with AWG - moving along, no obstacles
  2. PA has been working with Senofi - we got new HDS functional, created and responded to data call, generated a report with only minor tweaks
  3. 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.
  4. 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

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

F. Infrastructure Working Group

  1. Begins Thu. 1/19 - kickoff call - every other week from TSC same cadence and time
  2. 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. 

Discussion Items:



TimeItemWhoNotes




Goals:


Action Items: