Versions Compared

Key

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

...

Goals

Meeting Minutes

  • Anti Trust Policy notice reviewed
  • Data Modeling
    • Technical Considerations discussed
      • RDS, not NOSQL. Traditional ANSI SQL makes sense
      • Min ANSI requirements reviewed
      • Model Layers discussed
      • Goal: Flat dictionary to something that can be used
    • James Madison: On spreadsheet: groupings to get to entity-relation model
      • 4 layers: physical table layer, need machine efficiency, will not look like business model.
      • Today, look to get business model and the entities.
      • Persistent view layer, needed for extraction table and proper data loading and question answering.
      • Showed table models, just from groupings the spreadsheet
    • Reviewed tables to discuss relations between tables/entities
      • Can have Day 1 and Day 2 elements in the same entity
      • Used business model coverage elements to show how to move between business model and data model (tables, ERD)
      • Susan Chudwick says for Auto it’s all at the vehicle level.
      • James Madison: Keep repeating this process for additional elements and we will get this done well and complete
    • Last week’s suggestion
      • Should we start with AAIS stat plans as day 1?
      • Objections of starting with AAIS stat plan on HO?
        • Susan has questions on timing. How long will architecture take?
        • Dale wants to build existing stat plan so it can become the vehicle for stat reporting
        • Unpacking values like 2 fields that become 8.
        • Moving from code “01” to text “AL” for example.
      • Should Auto go back to stat plan?
        • Ken: first day all the same. New format not even finished, plus should do all the same.

...

  •  Susan – Confirm that all is at vehicle level, research UI/UM stacking
  •