Guideline 47. Implementation of master data systems

Submitted by Anonymous (not verified) on

The institution implements the master data systems taking into account the functional requirements of all involved business areas of the institution.

Guideline code
ICT_06200
Mechanism
Mechanism
  • The Master Data Governance Committee, the Master Data Management Committee and the ICT unit should set up a project with organizational structure and resources adequate to implement the institution’s master data system.
  • The Master Data Management Committee should specify the requirements for the master data system. The following considerations should be taken into account:
    • Concerning architectural aspects, the implementation should follow the defined architecture and an SOA approach. The system should provide service-oriented interfaces and use SOA-oriented middleware to facilitate access across and outside the institution;
    • Concerning the contents, the system should use reliable identifiers, especially for persons, as well as reference data (e.g. activity and geographic codes, etc.). The system should manage data versions, keeping the values for slowly changing objects, such as persons changing family status and address, or companies changing sector of activity. In turn, the criteria for moving active data to historic databases should be defined;
    • Concerning operations, the system should implement data management operations including CRUD and should support online transactions and provide master data to decision-support systems (i.e. data warehouses and business intelligence tools).
  • The scope of the data objects to include in master data constitutes one of the main types of functional requirements. Based on the preliminary scope, defined as recommended in Guideline 2, IT governance processes, the following data types may be included in the master data:
    • Persons, including basic data and specific data corresponding to their different relations with the social security functions (employee, beneficiary, contributor, etc.), family and household-related links;
    • Employers, including basic data and the contribution collection balance if relevant for other areas of the institution;
    • Labour records (employee–employer relationship, employee’s monthly salary).
  • The ICT Governance Committee, with the assistance of the ICT unit, may conduct the elaboration of a detailed design of the master data model and the metadata.
  • The ICT Governance Committee, with the assistance of the ICT unit, should conduct the corresponding buy-or-develop analysis to choose the most appropriate option.

Several master data products are available on the software market, which should be customized to the social security domain.

Structure
Structure
  • The board and the management should commission the Master Data Governance Committee, the Master Data Management Committee and the ICT unit to define a project aimed at implementing a master data system.
  • The project should take into account:
    • Functional requirements of all involved business areas of the institution, especially those managing core social security functions such as enrolment, benefits, contribution collection and payment;
    • Non-functional requirements of the ICT unit and other competent areas. This should include service-level agreements (SLAs) for the operations of the master data systems.
  • Component development may be based on processes for software development described in ISO 12207 or CMMI-DEV. In the case of acquiring the software components, the institution may apply processes for software acquisition described in ISO 12207, ISO 20000 or CMMI-ACQ.
  • The implementation of the master data system should be based on the institution’s project and development frameworks and models.
Title HTML
Guideline 47. Implementation of master data systems
Type
Guideline_1
Weight
65