openIDL Navigation

Page tree
Skip to end of metadata
Go to start of metadata


Antitrust Policy


  • Sean Bohan (openIDL)
  • Jeff Braswell (openIDL)
  • David Reale (Travelers)
  • Peter Antley (AAIS)
  • Dale Harris (AAIS)
  • Satish Kasala (Hartford)
  • Ken Sayers (AAIS)


  1. Continue discussion - Architecture& Scenarios
    1. openIDL - Architecture Definition Workspace (NEW)
  2. Previous Discussions 
    1. openIDL - System Requirements Table
    2. openIDL - Policies
    3. openIDL - Operating Roles


  •  KS
    • Architecture we can implement
      • Simple deployment plan on top of Arch (devops)
      • JB & PA process of standing up node, starting on deployment pattern
      • Not simple, end goal should be easy to stand up and take a look at
    • What are the artifacts we can work on  
    • Arch Diagram, Technical Architecture, lot of opinions on what is useful (interaction diagrams, etc.)
    • Thoughts?
    • Scenario Review
    • How to capture - notes as we go will suffice and org as we go into somethign that works for all
    • Satish-Hartford, David/Dale - Travelers, LF (network)
  • DR - not go too far w/o buy-in/check from folks at Hanover, only other entity besides Travelers and Hartford, need engagement / buy-in
  • SK - process, already had some baseline architecture defined/started then went into requirements, thinking go back, this is what we had/reqs and define gaps?
  • KS - wouldn't consider what we had a thing to migrate from (then-now), not in production, dont think start from old arch as start from what we can accomplish
  • DR - utilize what has been done but as we need pieces as proven out, but dont reference old at the beginning
  • SK  - need to lay out the, define, bottom up or top down? Top down, intentional arch (dir we want to head towards / Bottom up look at each component, build up component by comp
  • KS - dont have components to build up w/ right now - have to start from high level what are we trying to accomplish, put rough comp in place, address sequentially, too many arch really hard, lots of directions, get thru problem statement, what accomplish and then draw the diagram, dig in from the top
  • DR - interaction diagram, stem from that, how works, then neccessitates top down, dont want any mandates from component level that translate up
  • SK - how we approach, making sure, if we go top down, we normally create intentional diagram
  • KS - no assumptions - state them
  • SK - intentional architecture - this are the major pices of the puzzle and how laid out, broad brush, ex: Carrier node, what does it contain, HDS what does it contain and do, Analytics Node components
  • KS - application arch here, not enterprise arch, little different than funct breakdown, extract common pieces out, figure out funct components from scenarios (load data, access data, create report
  • DR - more of where you have cross disciplinary or cross enterprise to standardize of unify - little overkill for this, dont get too bogged down in nomenclature and methodology, lets go as low overhead as possible - what we want it to do and do it, dont be too methodoloy-driven not dogmatic
  • DH - there are subscriptions to data calls, agreeing to do it, annual, repeated each year (some 1/4 some monthly), have many similar data calls across states, state dictating what and how they want it
  • KS - diff channel? direct? stat reporters?
  • DH - use data call team, sep from Stat Reporters
  • PA - broken out because asking questions not in stat plan?
  • DH - stat plans so much info, hard to navigate thru (sources)
  • PA - easier to answer question than go thru Stat Report team
  • DR - funct, subscription is automating a piece of the arch - consent could add feature (annualy, quaterly, annual, etc.) - captured by some consent and how given - automation on both sides, person issuing could automate theirs, recept automate theirs - doesnt change underlying arch, same pipes and worker stuff
  • DH - does order matter?
  • DR - menu of data so to speak, lot of data calls designed to leverage whats there, data might be there before subscription, 
  • KS - data call model, tenet of the openIDL is the data is there why build it again
  • DR - could see Subscribe to Report occur after data load, then again, we will load data before subscribe
  • PA - loading something about ABS breaks on every record
  • KS - wouldnt load any data if you didnt sub to any reports, not sequential set
  • PA - ETL and networking ops too disconnected processes - process of loading and making data avail is sep from scenarios of "how to utilize openIDL to fulfill data requests"
  • KS - disjoined, dont have to do one or the other but CANT do reporting without loading data
  • DR - open account you dont intent to use, you could do, doesn't make sense but you could - start w/ scenario, state assumptions - simplify - "HDS is created and some data in it" good base assumption? 
  • KS - workfliow? pre and post condition? 
  • DH - scenario determines whats in HDS
  • DR - a check, is data there "Y/N", scenario is and is not, assume that for the scenarios these are operational scenarios, assum some pipes are built, operating as intended, day1 some doesnt exist but operating on Day 2 and work backwards
  • KS - scenarios - assume all is working
  • will be a check, scnario to work thru "is data there? no? load data"
  • SK - Day 2? when does the check happen?
  • DR - to be decided, talk early that every time write data to HDS assume data is there, could make arch such that theres data in HDS, maintained to some level of accuracy, when extracted a check "Y/N", there will be trivial cases for stat reporting where most likely that will be trivial (all plannkng for it) bu there will be scenarios unknown
  • JB - specific ation of a data call - stat reports repeat, know there, when comes to servicing data calls, one of your upfront cases is how do you define? 
  • KS - sep between data calls (asserted to being there) and stat reports (based on known data)
  • DR - simplifies to the trivial, process the same, expected success is higher, extend to a check to show data is there, not neccessarily leads to a data call - if someone makes a data call, makes request, checks meta data or funct we need, way for us to allow that
  • JB - inquiry, 
  • DR - ping to see if there, has data needed? might be funct helpful to regulators to benefit of carrier to tailor data calls to whats there - these elements satidy answers Reg wants, every carrier has it, can do that w/o Carriers exposing data early, telling them it is ppossible
  • DH -say data is there fields populated, but "as of Jan 1"
  • DR - if data call says "I need data Q3 Q4 2019 - data call provides success criteria - funct would have to live in carrier environmewnt, dont expost data until proper auth, dont want to do, is dont want to burden Regs to get buyin from all carriers if thats possible and demand "keep putting more data in" and see "i can answer my question" without having to put more data in - are there enough carriers? if thats the only way they can tell the data is there, will make them frontload work and then ask the question but if they can ask the question in a lightweight way, not actual data - 
  • JB - would support notion of defining metadata of what is asked for
  • DR - where does that live? in the query? in the adapter? part of it
  • JB - some distributed metadata concept for R to fashion query if he knows its defined in the system
  • KS - what the "LIKE" does right now, but not tied to current arch
  • DR - kind of like the light but programmatic but deeper than a like, structured query that answers "its possible"



  1. openIDL - Architecture - Member Requirements Files
  2. Regulatory Reporting Requirements from Dale H - VERSION 1(Travelers)
  3. Regulatory Reporting Requirements from Dale H - VERSION 2 (Travelers)
  4. Regulatory Reporting Requirements from Dale H - VERSION 3 (Travelers)
  5. Architecture WG Requirements Table
  6. HDS Requirements WIP (JamesM @ Travelers)

Notes: (Notes taken live in Requirements document)



  • No labels