rebekkabry
commented
1 year ago We're building a high-level dashboard that synthesizes real-time data to visualize the work and goals of TPW and its divisions.
Milestones
Phase 1: Current State
[] gather ATD data sources [] gather PW data sources [] link to organization divisions, departments and/or programs TPW [] investigate missing areas or gaps
Phase 2: Gap Investigation
[] TDB
Outcome:
[] compiled list of TPW data sources [] diagram that shows all our applications and how data flows between them and the open data portal [] automated updates for https://atd.knack.com/dts#open-data-inventory/
- which attributes are used or needed to keep site updated. -- current: Dataset Name, Description, Source Application, Dataset URL, Status
-
results.resource.name; results.resource.description; results.resource.type; results.resource.publication_date; results.classification.domain_category; results.classification.domain_metadata.value (frequency to update); results.permalink; results.link;
Outcome Additional Values:
[] find trends, relational concepts, commonality and story value [] list of assets for TPW? Possible github type record and note sharing?
Opportunities
[] build standardized reporting or data sets needs across business function areas [] insight into overlaps and/or gaps [] insight into executive main interests and/or gaps
amenity
Ecosystem Map is an enterprise-wide view of the data sources that support our business dashboards and provide insight into operational performance.
Background
Prior to the TPW merger, PW and ATD respectively have developed a variety of datasets, data source locations, operational tools and dashboards that provide insight into business activities and consideration for business initiatives toward changes. Currently there is no standard data documentation or visibility into the data pipelines that support our major dashboards and tools. The ideal behind the Ecosystem map is to provide documentation to support current tools, provide standardized data mapping documentation standards, and to provide stakeholders with a centralized “themed” platform to access all dashboards, reports, resources related to a specific workgroup or tools.
This map and documentation will be the backbone for current and upcoming projects. Such as: Dash, TPWStat, 311 integrations, etc.
Scope & Deliverables
Due to the large, complex nature of this initiative, we are planning to address this initiative in 4 phases:
Phase 1 – Collecting Start to End
Phase 2 – Current State Mapping Dashboard/Tools Level
[ ] Transpose maps into single line
Phase 3 - High Level Data Relationships between the stakeholders
[ ] Enterprise Wide Excel Mapping
[ ] Enterprise Wide Data Connections
Phase 4 – Centralized Platform Build Out
Desired Outcomes
Timebox
This is an iterative project that will accumulate data from different divisions as data owners become available to walk through the pipeline and variations of data collected.
Concepts and references
What is a data ecosystem map?
A data ecosystem map illustrates the different actors in a data ecosystem, and how value is exchanged across it. A data ecosystem consists of data infrastructure, and the people, communities and organizations that benefit from the value created by it. Data infrastructure is made up of data assets, standards, technologies, policies and the organizations that steward and contribute to them.
Why use the tool of an ecosystem map? Creating a data ecosystem map helps to understand how data creates value. It identifies the data, data stewards and data users; the different roles they play; and the relationships between them. You can use your map as a practical tool to plan and visualize a data ecosystem, or show opportunities for increasing value to particular parts of a data ecosystem. A data ecosystem map can be used to:
Opportunities and Value
Request details
https://atd-dts.gitbook.io/wiki/product-ops/dts-website#images The first image will be used as the project's thumbnail image on the website.
This Github issue represents a project of Austin Transportation's Data & Technology Services team. Project status is documented regularly in the comments below.