Initiate a data collection project
Alfabet provides a Data Collection Initiative functionality that allows your company to collect specific data for applications, information flows, components, and physical and virtual servers that are already in the repository. A data quality initiative could be started for any of the following situations:
- Capture particular data to insure gaps are filled. For example, you could ensure that start dates are captured for all applications.
- Initiate a review of existing data. For example, you could trigger a yearly review process to ensure accuracy about the data regarding your company's components and servers.
- Collect data for a specific project. For example, you could initiate a process to collect data to assess a planned project to consolidate applications relevant to a business capability or business process.
- Increase the maturity of your enterprise architecture or strategic portfolio management practices by improving the level of data in the repository. For example, you could start a data collection project to document the compliance of your IT with various types of legislation and standards such as SOX, COBIT, or GDPR.
- Fill gaps in data that remain after the data import process. For example, you could target application managers to add or update the application data based on their expertise.
As portfolio administrator, you can configure data quality rules to initiate a data collection initiative in your company. In the data quality rule, you specify whether the initiative targets applications, information flows, components, or physical and virtual servers as well as the attributes that shall be included in the data workbench for the data collection. You can also specify the users in the user community that shall be responsible for providing the necessary data. These users will have access to the relevant data workbench in Alfabet in the navigation panel > Data Quality > Data Collection Initiative. The assets that they are responsible for will be displayed in the data workbench. As soon as the required data is provided for an asset, it will be removed from the data workbench. In this way, users see only the assets that they need to process.