The Government Pensions Administration Agency (GPAA) is an Agency that provides administrative services to the GEPF and National Treasury. The provision of services is regulated by Service Level Agreements (SLAs).
The funds and schemes that are currently administered by the GPAA are as follows:
The Government Pensions Administration Agency (GPAA) in its efforts to streamline its business processes to provide a more effective Defined Benefits Pensions Administrations process has embarked on a Modernisation Programme.
The core deliverables of this programme are Data Migration from legacy systems and Master Data Management aligned to an Enterprise Data Model. The solution will provide for the monitoring and ownership of data quality within the organisation as aligned to key performance indicators and governance frameworks. The objective of the GPAA Modernisation Programme EDM deliverable is to establish and operationalise the management of information during the entire life cycle, including data creation, processing, consumption, storage, archiving and disposal.
The scope of the project includes the following services:
The following strategic benefits will be delivered:
The migration of information from the current systems will include data analysis, profiling, classification, cleansing and transformation. The current information producers are a combination of internal and external sources. Internally the GPAA stores information on Oracle databases, as well as on a mainframe system that runs on a Z/OS operating system with Natural programs connecting to an Adabas database version 8.2.6.
Business critical data is fragmented and spread across various departments, functions, processes and systems. To enable data ownership and stewardship, GPAA requires all the critical data entities in a central repository from which a single or 360-degree view of the data is created so that the business owner does not have to go from one system to another to verify its accuracy, completeness, conformity and integrity of the data.
The enterprise data model is simply a canonical or standard model of the common data objects or entities and their key attributes that are required to run GPAA. In order to have a central repository (MDM), especially where data is fragmented and spread across various systems, it is important that stakeholders speak a common language. The EDM solution should facilitate this via an Enterprise Data Model around which common business and technical terminology can be created and linked together. The GPAA requires a defined metadata function to manage the technical, operational, and business metadata. Technical metadata should include legacy platform fields and definitions. Operational metadata should include data transfers, movement, and mapping, while business metadata encompasses business glossary and the common vocabulary.
Quality of data has a direct impact on how well GPAA performs. The GPAA needs to monitor data quality metrics which is linked to key organizational and individual performance indicators. The EDM solution should provide reports and dashboards that reflect these data quality metrics and known data issues so that stakeholders can perform the required data quality monitoring and react appropriately. Information should be available for trending and forecasting.