This page describes the scope of the POC to prove that openIDL meets the needs of the community.
High Level
- generate the report and it reconciles / matches expected
- where does the data reside and what happens to it along the way to the report
- multiple sources / pull the data / create the report
Acceptance Criteria
Architecture / Design
- documented architecture
Infrastructure Requirements
- runs on aws
- able to host hds in carrier cloud
Functional Requirements
- 2 personal auto reports
- submission format is personal auto statistical plan (flat, positional)
- end to end process
- data call creation
- data call like and consent
- extraction pattern development and testing
- report creation
Non-Functional Requirements
- data privacy
- security
- auditable
Specific Requirements
Identify the specific requirements by number from this page: openIDL - System Requirements Table (DaleH @ Travelers)
Please complete by
| Priority (H,M,L) | Requirement Number | Comment |
|---|---|---|
General Comments
Put any comments about what should be in the POC
Business Case / ROI
- cost to carrier
- cost to run
- funding model
- potential savings
- value provided
- across potential scenarios
- likelihood of healthy community
Governance
- acceptance of this POC scope by TSC
- approval of spike work (budgeted or not)
- presentation of POC solution to TSC
- acceptance of POC results
- define path to business case and go / no go