Versions Compared

Old Version 3

changes.mady.by.user Nathan Southern

Saved on

compared with

New Version 4

changes.mady.by.user Nathan Southern

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FOLLOW UP:

  •  

TSC Voting Members Attendance:

...

  1. Call to Order
  2. Anti-Trust, Review of TSC Meeting format and Participation by TSC Chair
  3. AAIS TSC member succession
  4. TSC Chair succession
  5. Update on TSC WG activities
    1. Architecture Working Group
    2. AWG HDS Task Force
  6. Progress on openIDL Auto Stat Plan
  7. openIDL testnet plan and SOW
  8. openIDL governance requirements and procedures
    1. To register/identify/accredit new members
    2. To monitor network
    3. To manage infrastructure and application deployment/upgrades
    4. Provision for network communities
  9. AOB

...

Recording/Meeting Minutes


A. Procedural Matters

  1. Mr. Braswell discussed new appointment of chair for TSC - and asked for unanimous consent for Mr. Sayers to take over as TSC chair. Laid out rationale for appointment of Mr. Sayers
  2. Asked for any comments, objections, criticisms from members.
  3. No objections presented. Mr. Braswell asked for lazy consensus of voting members - four present. Mr. Sayers thus named new TSC Chair
  4. Mr. Braswell then moved into general update and reporting of activities.
  5. Mr. Braswell then turned over to Mr. Sayers to Lead Update

B. Mr. Sayers: 3 Main Threads Underway

  1. AWG and spinoff HDS WG, and process of making sure architecture meets biz and technical requirements. We're reestablishing reqs and making sure all have these req in mind and understood. Updates on wiki accordingly, a/w accompanying documentation. After requirements, we'll discuss actual architecture constructs and go through this process. Possible reconfig of current architecture.
  2. ND POC from AAIS reporting on uninsured motorists - AAIS doing with ND and Top 10 carriers in ND. We are ensuring we understand requirements of captured the insured vins in ND compared against all vins - extraction will be performed etc. Kickoff session on 7/26 in ND, many carriers will be attending. A remote option will be made available. Open to anyone who wants to participate. We will set up nodes for carriers in a hosted fashion, not on their own clouds. Data loaded through a simple UI, loaded into HDS. Test net - Chainyard setting up 10 carriers w/corresp. nodes multitenant and analytics. Reports will be run in Jan Feb 23. ND should be kept abreast. 
    1. Mr. Hoffman inquired about the availability of a sale sheet related to ND, how will corresponding readouts be done. 
    2. Mr. Sayers: dial in and connect with project directly through Chris Aufenthie - he can tell Travelers et. al. directly. Engage with ND - we are really interested in what you are doing.
    3. Mr. Hoffman referenced IICMVA - asked were they part of RFP process?
    4. Mr. Sayers: we should do any sale sheets in concert with ND - this should be put in action items/to-dos.
    5. Mr. Antley: timeline for this. Kickoff at end of July for ND - should have documentation after we return. But Mr. Sayers affirmed that this is not exactly what Mr. Hoffman requested. Follow-up on this specifically as an action item/deliverable.
  3. Stat Reporting openIDL project inside AAIS 
    1. Scope: two reports id'd for personal auto - very straightfwd initially - using data we currently have as input to feed into idl, using plumbing, not engaging any other carriers. Used to learn how HDS should look, where we're stretching architecture, pieces that need to be worked on, expanded, improved, etc. AAIS will be feeding lessons back into TSC and AWG, how to improve etc.
    2. Mr. Antley: has been working on reproducing two reports - going through columns discussing math required to generate various columns and working on calculations and highlighting that format in which we're ingesting data is sufficient. But a data level is missing: how can data be made available to business users, more accessible, without excess overhead. Id'ing required fields. We still need to be able to query through time. Actively working on this. Demo forthcoming in August.

C. Mr. Braswell - openIDL TestNet plan

  1. SOW with Chainyard ID'ing 4-5 note Testnet - so we can get up to speed on monitoring and validation processes idl will do. 
    1. Part of documentation: defining how new members can join etc.
    2. At some point we need to work toward production-ready main net. This means involving Chainyard more integrally
    3. Better presentation of what this looks like forthcoming on next call.
    4. More information about this approach forthcoming.
  2. Called for any additional questions from group - none presented.
  3. openIDL governance requirements and procedures - letting TSC know that a number of stakeholders have a role in this process. We are in the process of laying out processes for registering/id'ing accrediting new members, monitoring network, managing infrastructure, provisioning for network communities, etc. 

D. Mr. Braswell - conclusion - turned back over to Mr. Sayers - no additional comments or business. Meeting adjourned at 12:27pm EST.


3.

Discussion Items:



TimeItemWhoNotes




...