Page History

...

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 for ND project.
   5. Mr. Antley: timeline for this. Kickoff at end of July for ND - should have documentation after we return. But Mr. Sayers affirmed that : we have engagement packages we're giving out to each of carriers and there will be a technical part of this as well, but this is not exactly what Mr. Hoffman requested. Follow-Concerned more about the hardening they are doing to make this happen. This needs to be followed up on this specifically as an action item/deliverable.
3. Stat Reporting openIDL project inside AAIS AAIS
   1. Great progress being made.  
   2. 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 like extraction pattern that need to be worked on, expanded, improved, etc. Stretch points of current architecture to do stat reporting. AAIS will be feeding lessons back into TSC and AWG, how to improve etc.
   3. Mr. Braswell: this has also been coming out in the data management WG re: the types of things that we need to make this happen w/stat reporting through idl etc. Asked Mr. Antley to comment on using flat file to produce existing stat report and then going to a more flexible HDS option to produce the same report. Sequence of steps to go through - as laid out in last meeting. Great progress. Much of work Mr. Antley has been doing has been advancing our ability to show auto stat plan as a proof of the plumbing working for the POC.
   4. Mr. Antley: has been working on reproducing two reports - going via existing architecture - Mongo with mapreduce. Going through columns on report discussing math required to generate various columns and working on calculations and highlighting that format in which we're ingesting data is sufficient . But for ingestion but a data level is missing: (embedding ETL into VI layer): how can data be made available to business users, more accessible, queries can be performed without excess overhead. Id'ing required fields and various calculations. We still need to be able to query through time . Actively working on this. Demo forthcoming in Augustwhich demands more complex data model. Yesterday: ETL pipeline. Two lambdas hooked up to facilitate ingestion of data successfully. Extraction pattern run today for ND POC. Demo forthcoming in August.
   5. Mr. Braswell concluded by affirming that many great things are coming out of these WGs and we'll benefit from taking work to the next level.

C. Mr. Braswell - openIDL TestNet plan

1. SOW with Chainyard ID'ing to implement an initial 4-5 note Testnet with which idl can work - so we can get up to speed on monitoring and certificate of authority validation processes idl will doopenIDL will help monitor and provide. 
   1. Part of work: providing documentation : defining about how new members can join etc. At some point we need to work toward production-ready main net. This means involving Chainyard more integrallyWhat do we need to deploy code to the network?
   2. Given the fact that some work is happening with Chainyard on other projects, we want to have some intra-project sharing. Using one aspect of the work to inform the types of things that we need to do at openIDL to ingest that work and turn it from a development project into more of a production entity.
   3. Plan now is to get up and running with this initial SOW, which has been modified slightly to inform Chainyard we need their participation beyond basic network set up
   4. This will mean dovetailing with AAIS work. We do have a modified SOW which indicates that Chainyard will be standing up this network and monitoring it for the coming months.
   5. Better presentation of what this looks like forthcoming on next call.
   6. Moving fwd. now with strategy that enables us to see how openIDL can accept and bring on board new application that is being developed while continuing with the broader developments for stat plan and general queries. 
   7. More information about this approach forthcomingas we go forward
   8. Types of things openIDL needs to do itself to monitor, register and manage the infrastructure of the network in an oversight process.
   9. Called for any additional questions from group - none presented.
2. 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 29pm EST.3.

Discussion Items:

...