In detail explained in section 2.3, pages 29-39 of the BRIAF, this group of phases focuses on the conceptualisation of data models through management of Master data, the main asset of a Base registry, with a continuous cycle of Data Quality, having the data protected and secured.
|
Master Data Management phases |
|
Phase |
Description/Scope |
|
|
1 Plan |
This phase consists of a sequence of actions, intended for the creation of a data management plan. In a data management plan, the sources from which data will be retrieved are identified and secured, and the processes for data gathering, management and use are defined. |
|
2 Specify | The aim of this phase is to ensure a comprehensive and consistent data definition. This is done through the standardisation of data in the data model, which establishes the relationship between data itself, and the properties of the entities that they represent. |
|
3 Enable | This phase has an objective of ensuring all necessary infrastructure for the adoption of the predefined data models in place. This should include several aspects, starting from the construction of the repositories and interfaces of the solution. Once built, they should be tested in order to ensure their full operability. If the tests are satisfactory, the components of the solution are deployed. Finally, this phase will also include the maintenance of all solution components while the service is running. |
|
4 Create | Once all the necessary infrastructure is in place and in normal operation, the data shall be designed. This data has to comply with the data model and other characteristics, previously defined in the service’s data policies, set by the data governance body. It also has to be relevant from the point of view of the service in terms of business value. |
|
5 Acquire | This phase consists of the acquisition of data from other repositories to store it in a Base Registry. The acquired data has to be analysed in order to determine their degree of compliance with the different sets of characteristics for data, defined by the Base Registry itself, like the format and the terminology in which data are expressed. |
|
6 Maintain | This phase consists of performing the necessary activities to ensure the integrity and comprehensiveness of data during the service’s lifecycle. One of the main activities performed in the context of this task is data cleansing. Data cleansing covers detecting and correcting inaccurate or corrupt data stored in the Base Registry, identifying the affected parts of the data, and replacing them with other data. |
|
7 Archive | In this phase, the data is archived in the Base Registry. The actual repository in which the data is archived depends on the layout of the base registries for the delivery of the integrated public service. A centralised Base Registry will archive its data primarily in a main repository, while a federated Base Registry will rely on a set of repositories distributed across its Base Registries. |
|
8 Retrieve | In this phase, the archived data is being retrieved, when needed. It is essential to study the related regulatory requirements for data archiving and retrieving in order to adopt the best solution. |
|
9 Purge |
This is the last phase of the data lifecycle and it implies the elimination of data that have been evaluated as not relevant or necessary anymore, or which an entrusted actor has requested their elimination. One example is a request for the elimination of personal data. |