Ken - demo of the ND POC end to end which may help reinforce understanding of its role/functionality
Ken: Next section of the work - communication/the “control module”.
Catch up our documentation on status of design
Notes:
Notes included in Architecture Definition Workspace doc
Minutes
NS began with LF Antitrust Statement
KS: POC Scope Page - Updates - as discussed last week (TSC)
Requirements page: what should be part of technical POC vs. not. High-level scope items/accept. criteria/detailed req. #s - 2 wk. turnaround.
Demo of ND POC
Some related questions have arisen based on onboarding dates for stakeholders. Want to see end-to-end process of data call
About to start connecting to carriers for ND POC and will start doing Dec. data call for uninsured motorists
Walkthrough of flow will illustrate the steps involved - what data goes in and comes out
Process
Carrier - wants to identify who is uninsured.
Scope for POC - carriers provided VINs to system to upload one day during a month x number of VINs insured, into their node; then DOT does likewise, uploading reg'd VINs. Carrier and analytics node each have one set of data. Carriers can provide raw data or previously hashed values. DOT creates data call to request VINs from carriers and compares that against hashed other set of data and compares #s etc. and evaluates results. All matches considered to be insured.
Three things underway
POC Scope
Capturing of progress in the wiki (e.g., postgreSQL, etc.)
Data module (presented illustration) discussed - now we're talking about openIDL Control Module. Component where we put in data call, communicate w/other carriers, control process. But doesn't hold any data - more a place that we pass through. Doesn't run extraction itself. How we run this: our next discussion point. Allows interfacing of users/carriers/clients into network for control/communications.
First activity to describe module: white/black box - what is it doing from the outside's perspective? e.g., requesting data, allowing for mgmt of data calls, etc. what is the functionality it is fulfilling? What is the scope of its functionality? (We can subsequently discuss internal components). Application + connection to network parts of control module. Functionality" (Network underpinning communication between all modules). Both peer-to-peer and a central mechanism.
Application Layer
Control Module Functionality
Crud data calls (requests from DOI to carriers)
Likes and consents
Requesting extraction of data
Requests extracted data
Transport extracted data to analytics node
Provide analytics for final release consent
All access to ledger happens here
Interacts with communication mechanism
This is where we will have our peer that connects to the blockchain network.
Analytics Module functionality
Determine carrier percentage of report
Enable second consent
Create report
Combine results
No access to ledger
In ND case - comparison with registered VINs
Gets results from each one of the consenting carriers - pulls together into a report
Fundamentally just a service provider for providing reports
Should just know where the data is and what kind of report to run
Development of Extraction Pattern
Local machine with access to the system
PA: Senofi techs got PA set up with Test Net from LF.
Time
Item
Who
Notes
Documentation:
Notes: (Notes taken live in Requirements document)