+27 (0) 12 315-5481   


Frequently Asked Questions

What is the Integrated Financial Management Systems (IFMS) and what is its main purpose?

The IFMS Programme is a joint initiative between DPSA, National Treasury and SITA to replace the current legacy enterprise resource type systems such as BAS, LOGIS and PERSAL in the Public Service by implementing a single Enterprise Resource Planning (ERP) Commercial Off The Shelf (COTS) system.

What is a Commercial off the Shelf (COTS) solution?

A COTS solution is commercially available software that has specific built in functionality for business needs. A COTS solution is designed to be easily installed and configured for use.

What is an Enterprise Resource Planning (ERP) solution?

An ERP solution is business process management software that allows an organisation to use a system of integrated applications to manage the business and automate many back office functions related to financial management, human resource management; payroll and supply chain management.

What is meant by 'legacy systems'?

'Legacy systems' refers to systems that are currently being used in the Public Service such as BAS, LOGISand PERSAL, which will be replaced by the IFMS.

What is 'self-service' in the context of the IFMS?

'Self-service' within ERP solutions generally refers to a web-based system that provides employees, for example, access to;

  • Update their personal information, such as home address, beneficiaries, personal details, etc.;
  • View the payslip details; and
  • Perform transactions, such as applying for leave and submitting travel claims.

The specific self-service functionality to be offered by IFMS will only be confirmed once the design of the solution has been finalised.

What will the implementation process in a department entail and how long will it take to complete?

The implementation will follow an approved implementation methodology that will include activities such as change management, training of users, data migration and user acceptance testing. The duration of individual implementations will depend on a number of factors such as the size of the department, the number of employees and the geographic spread of the department.

How will the unique requirements of departments be catered for in the solution?

The new IFMS is designed to cater for the general corporate management needs of the Public Service and does not specifically cater for unique requirements within a department. Where feasible, unique requirements that fall outside the scope of IFMS will be met by interfacing existing departmental solution to the IFMS. During the roll-out of the solution to all departments in the Public Service, opportunities will be explored to ensure that the entire solution (IFMS in combination with departmental solutions) meets the unique business requirements of specific departments.

What will happen to people working on current IFMS modules and on legacy systems?

In the majority of cases, employees who are currently working on legacy systems and the IFMS modules currently in operation will be trained on the new IFMS and will continue to perform their existing functions after implementation. Some employees’ jobs may change as a result of the implementation of the IFMS. This will specifically apply in cases where employees are currently responsible for processes that will be automated through the implementation of IFMS. For example, leave forms will no longer be captured manually on the system as the leave application and approval process will be automated. In such cases, employees’ job descriptions may have to be amended and they will be retrained, if required, to perform other related duties

Will there be any job losses due to the implementation of the IFMS solution?


How will users be trained to operate the new solution effectively?

Different types of training such as classroom based and on-the-job training will be conducted to enable users to operate the new IFMS effectively.

What will be the approach to change management at an organisational level and at a user level?

A formal change management programme will be embarked upon to ensure that all users are adequately informed regarding the new IFMS, that potential resistance to the adoption of the new system is managed and that users receive sufficient training to enable them to operate the system.

How will users be able to access the IFMS?

Most users will access the new IFMS through a web browser (e.g. Internet Explorer or Firefox) on computers (desktop or laptop). Users will require a valid username and password to access the system functionality. Access via mobile devices will be considered during later phases of the Programme.

What are the minimum technical specification for computers (desktops or laptops) or mobile devices (smartphones, tablets and phablets) to access and operate the solution?

The minimum technical specifications for devices will be made available during site readiness assessments and before commencing with implementation.

How will users be supported to ensure that they are able to operate the solution effectively?

A formal support structure in the form of a functional application support team and help desk will be put in place to support users who experience incidents or problems in the new system.

How will data from legacy systems be made available?

Some data will be brought across to the new system. Data that is not brought across will be made available either on the legacy system itself until it is decommissioned, or it will be archived and made available to users electronically.

How will the Programme address connectivity and infrastructure challenges in remote areas?

Remote locations and associated connectivity and infrastructure challenges will be quantified during the Infrastructure Design Phase of the Programme, so that solutions can be designed and planned for.

What will Departments be expected to budget for?

Departments implementing the IFMS will be expected to engage and sign a Memorandum of Understanding for that specific department

  • Maintenance fees for the IFMS, post go-live.
  • Appointment of implementation project managers and related personnel, if additional capacity is required by the department.
  • IT LAN/WAN, server and access devices (e.g. desktops infrastructure).
  • Integration of departments’ unique systems with the IFMS if required.
  • Computer literacy and functional training if required.
  • Data cleansing.
  • Change management materials, should the department wish to use such material.

What is 'data cleansing'?

Data cleansing is the process of amending, removing or improving data in a database that is incorrect, incomplete, improperly formatted, or duplicated. This needs to be done in the legacy systems prior to the data being migrated into the IFMS. During implementation assessments, departments will be provided with the specific data fields that need to be clean for migration purposes.