Line 96: |
Line 96: |
| * Outline the plan to allow other public sector organizations to reuse the common capability | | * Outline the plan to allow other public sector organizations to reuse the common capability |
| <b>Tools:</b> | | <b>Tools:</b> |
− | * Business CApability Heat Map | + | * Business Capability Heat Map |
| * Projects to Value Stream Script | | * Projects to Value Stream Script |
| | | |
Line 105: |
Line 105: |
| === Collect data to address the needs of the users and other stakeholders === | | === Collect data to address the needs of the users and other stakeholders === |
| * assess data requirements‑based program objectives, as well users, business and stakeholder needs | | * assess data requirements‑based program objectives, as well users, business and stakeholder needs |
| + | <b>How to achieve:</b> |
| + | * Summarize how the architecture meets the data needs of the users and other key stakeholders including: |
| + | * How does the data asset contribute to outcomes/needs of the user and other stakeholders |
| + | * Gaps in the existing data assets to meet the needs of the users and other stakeholders and how the architecture addresses these gaps |
| + | * Gaps in data collection and analysis and how the architecture is addressing it so that ESDC can ensure that we are serving the members of our society |
| + | * Alignment to the data foundation of the ESDC information/data architecture practice |
| + | * Alignment to the theoretical foundation of the ESDC information/data architecture practice |
| + | |
| + | <b>Tools:</b> |
| + | * For Data Foundation – Implement: |
| + | * Data Catalogue |
| + | * Benefits Knowledge hub |
| + | * Data Lake (growth) |
| + | * Data Science and Machine Platform |
| + | * Stakeholder Requirements |
| + | * Solution Requirements |
| + | |
| * collect only the minimum set of data needed to support a policy, program, or service | | * collect only the minimum set of data needed to support a policy, program, or service |
| + | <b>How to achieve:</b> |
| + | * Summarize how the architecture aligns to “collect with a purpose” including: |
| + | * What is necessary (as opposed to what is sufficient) to meet the stakeholder need |
| + | * Supporting Performance Information Profiles (PIPs) used to assess a progress towards target and broader objectives |
| + | <b>Tools:</b> |
| + | * Value Stream (Value Item and Value Proposition – Context on What we measure) |
| + | * KPI Linked to benefits outcomes and objectives |
| + | |
| * reuse existing data assets where permissible and only acquire new data if required | | * reuse existing data assets where permissible and only acquire new data if required |
| + | <b>How to achieve:</b> |
| + | * Summarize reusability of the architecture’s data assets given: |
| + | * Context of data assets and user and stakeholder needs |
| + | * Data quality and fit for purpose |
| + | * Privacy and Security Regulatory Framework |
| + | <b>Tools:</b> |
| + | * Legislative / Regulations |
| + | |
| * ensure data collected, including from third-party sources, are of high quality | | * ensure data collected, including from third-party sources, are of high quality |
| + | <b>How to achieve:</b> |
| + | * Summarize how the architecture meets the data quality requirements of third-party sources: |
| + | * Data quality meets fit for purpose |
| + | * Data quality dimensions including: |
| + | * Relevance, |
| + | * Timeliness |
| + | * Consistency, |
| + | * Reliability, |
| + | * Interpretability, |
| + | * Usability |
| + | * Data quality mechanism |
| | | |
| === Manage and reuse data strategically and responsibly === | | === Manage and reuse data strategically and responsibly === |