1. hurricane Zeta call, made by DOI of MS, request all info from insurers, claims activity for period of time in certain area
2. AAIS combines data
3. Create report and send to DOI
Set up a node (Carrier Node)
Load data to HDS from their db
OLGA prob basis for loading that data, adjusted to make sure load data into HDS
work with Carrier to impress the format of the data (Stat format, loads into DB, will be sparse claims stat data format)
extraction pattern and data call, run against data loaded, rolls up to aggregated data, sends to the channel to the analytics node, report generator, creates report
Groups
Carrier
aais, format, olga, EP
senofi - carrier node setup
chainyard - analytics node and other nodes, writing the code for the report generator
Will defer setting up nodes for. a little while, dont want $ costs while still working with the data, setup temp HDS, mock extractions
Set up nodes once data is right
Phase 1 does not inc. Crisis track data
Reports:
MS DOI & MEMA, go to crisistrack, get all the damage based on an area (polygon or collection of zipcodes)
access to damage reports, DOI wants to know damage as well - what % insured
2 ways
put address into HDS, EP provides an ID of the location to the analytics node and uses identifier # to access crisistrack, combine ins info with damage info+image
do the same extraction, push # to crisistrack they can capture with that location so MEMA can go to crisis track, see a bubble
things make this hard
cant send the address, considered PII
they dont want it outside the node
crisistrack will pub API, send in an address will give back damage info but give back a bunch of addresses (clearance and cleansing process), provide a crisistrack PIN, no standardized #, dont want others to id that address, get PIN and put it into the HDS
work for crisistrack to output API, work on AAIS to get that PIN
Dont see a change on the chaincode side, EP and data in HDS anyways, no need to adjust or change the chaincode model
dont see moving fields but maybe adding fields
Ordering service plan? Part of openIDL or a node on its own
running on AAIS node in prev networks
reco sep node, talk about that
just go on AAIS Node like done in the past
Could make part of openIDL network, common channel is configurable, not stuck with unique channel name, could bring diff POCs with diff names on same network
option - own dedicated node, hosted on carrier or analytics node, no tech limitation
orderer on carrier node if possible
Default channels assigned to POC, data kept private, good to try to do with the tools senofi has developed, integrated later
priv and sec of data, not visible to others
Transaction volumes
Not big records but millions of them, at minimum 100s of thousands, network load
found DB on the channel broke, expand that
Making avail damage info to the carrier customers
customers all over the world, want to see damage to. their property
Carrier very excited about getting pics of damage to property owners
new API from crisistrack, return photos from PIN, use same PIN
