In 2019, the Australian Public Services’ (APS) Secretaries Board agreed to prototype a whole-of-government Enterprise Resource Planning (ERP) template, with the Department of Finance (Finance) leading prototype development. In 2021–22, the project moved to Services Australia. Services Australia was tasked with building and delivering a common corporate technology platform (GovERP) for use by APS entities.
On 28 November 2023, the Finance Minister announced a new ERP approach for the APS that includes GovERP being repurposed for use by Services Australia (as Services Australia ERP), and any entities that choose to use it (see A new approach for back-office functions in the Australian Public Service). The Minister also announced an independent reuse assessment of GovERP to support Commonwealth entities to implement future cost effective ERP uplifts. This report outlines the outcomes of the independent Reuse Assessment.
This Reuse Assessment has made 5 key observations relating to GovERP’s delivery to date, remaining work to complete, reusability and alternate designs or delivery pathways. These are summarised below.
Insights suggest that for the government’s investment in GovERP to date:
Against these key observations, the Reuse Assessment has made 5 recommendations for next steps.
The shifts in GovERP’s scope, changes in ownership, and limited stakeholder consistency (as evidenced by multiple changes to the entities identified for initial onboarding) have culminated in a program that has not delivered as originally intended. The volatility, and ambiguity in ownership and accountability, has resulted in an under-delivering project. The need for well-functioning ERP capabilities across government has not abated.
a) As core underpinning capability of all government entities, ERP uplifts need clear ownership and accountability mechanisms established at both the COO Committee and Secretaries Data and Digital Committee (SDDC) levels, to ensure considered uplift sequencing and to promote common approaches with limited customisations.
b) To ensure equitable access to market resources across entities, overarching SDDC governance is needed to support successful ERP uplifts and implementation across government.
GovERP has not achieved the aim of a standardised common transactional corporate service across the APS. 30 functional GovERP capabilities have been developed to date with 18 of these having completed functional testing, but none have progressed beyond functional testing into system integration testing, user acceptance testing or production.
The ERP solution in its current form is not suitable to meet whole-of-government or Services Australia’s operational requirements. The objective of a standardised, common transactional corporate service will not be achieved by GovERP, even if the remaining work to complete the MVP1.1 is progressed.
Given the objective of a standardised, common transactional corporate service will not be achieved by GovERP, further direct investment in GovERP for whole-of-government use is not recommended.
No results found.
Considering the current state of ERP capabilities, Tier 1 reuse opportunities (use of what has already been built) are limited.
Building on existing GovERP capabilities with a separate ERP instance (a Tier 2 reuse opportunity) may be desirable for larger entities with complex ERP requirements and substantial in-house functional and technical digital skills. In such a case, GovERP could serve as a potential accelerator as it can help minimise the effort and financial investment required to develop capabilities based on the current build and test status.
Any entity intending to progress ERP upgrades must have a robust business case for investment. The government needs to enforce, via policy, a strong incentive to ensure entities actively consider reuse of existing capabilities, as well as leveraging current arrangements with commercial vendors for licences and hosting costs where applicable.
There is strong demand for GovERP’s business process maps, designs, patterns and related documentation to be made available for reuse by other government entities (a Tier 3 reuse opportunity). While the Digital Transformation Agency’s Australian Government Architecture (AGA) provides a centralised site to make reusable designs available, there may be merit in a secure sharing facility to disseminate sensitive materials that are not suitable for publication on the AGA website.
The Digital Transformation Agency to provide a centralised site to make confirmed reusable designs available, including secure sharing facility to disseminate sensitive materials that are not suitable for publication on the AGA website.
GovERP was envisaged as a single, whole-of-government technology hub. Componentisation of each capability for potential reuse is possible but has limited commercial effectiveness. Grouping of like entities may help to achieve economies of scale without the complexity of pursuing a whole-of-government, one-size-fits-all approach. Further, focussing on smaller-scale projects over shorter time limits may help minimise ERP uplift delivery risks.
The new ERP Category under the Software Marketplace Panel, coupled with the Department of Finance’s work to support a small-entity solution, may help to identify next steps for a collective or group-based approach.
Where possible, future ERP uplifts should group entities of similar complexity and scale (not necessarily aligned to portfolio, organisation, or other corporate service provision arrangements), to help achieve economies of scale and re-use without the challenge of pursuing a whole-of-government approach.
To support Commonwealth entities to implement future cost effective ERP uplifts, the independent reuse assessment has focused on:
The Assessment’s terms of reference, as detailed at Appendix A, sought to:
The Assessment was led by a 4-person independent Panel of Eminent People (the Panel). The Panel brings together a unique set of independent, informed, and different perspectives from across government and the private sector. The Panel has extensive experience in leading complex transformation programs, including ERP systems.
The Panel consists of:
Biographies of members of the Panel of Eminent People are at Appendix B.
The Assessment was supported by a DTA Secretariat.
The Panel was informed by:
Entities represented in the Assessment’s interviews, ERP Consultative Committee, and working group are specified at Appendix D.
The Assessment was also informed by additional consultation activities undertaken by the DTA Secretariat (and, where relevant, supporting technical experts from Reason Group Pty Ltd) as follows:
Regular updates were also provided to the Digital Leadership Committee, the APS ERP Approach Reference Group, and the DTA’s Executive Board. On 20 May 2024, the DTA Chief Executive Officer shared preliminary findings and insights of the Assessment with of the Services Australia Chief Executive Officer (at Appendix E).
A draft of this report was shared with Services Australia and Finance stakeholders for factchecking and comment on 6 June 2024. In addition, the draft report was shared with the Finance Minister’s office. Key observations and draft recommendations were also tested with the Assessment’s working group.
OffThe Shared Services Program, led by Finance, commenced in 2014 with approval from the Secretaries Board. In 2019 the Secretaries Board agreed that Finance prototype GovERP, the enabling technology for the program.
On 14 September 2020, the Shared Services Steering Committee defined a suite of functional (and other) capabilities as the minimum necessary for a whole-of-government GovERP model. These 54 functional capabilities were grouped by ‘value streams’, notably: human resources (Hire to Retire), procurement (Procurement to Pay), financial (Budget to Report and Revenue to Bank), as well as travel and expense management. These are outlined at Appendix F.
In July 2021, the GovERP Program moved to Services Australia. Services Australia’s GovERP program was intended to comprise a SAP based core (see Reference 1) with a series of software solutions able to be added to provide specific functionality.
The previously defined suite of 54 functional capabilities, considered to be the minimum necessary for a whole-of-government GovERP model, was revised in consultation between Services Australia and its nominated client for initial onboarding (AGD). This revised minimum viable product (MVP), also outlined at Appendix F, reflected a more targeted suite of 39 ERP functional capabilities.
For the purposes of this report, references to MVP1.0 reflect the original Shared Services Steering Committee-defined scope of 54 functional capabilities for whole-of-government purposes, and MVP1.1 refers to the revised scope of 39 functional capabilities intended for initial onboarding of AGD.
In November 2023, the Minister for Finance announced the scaling back of the broader GovERP program, concurrently introducing an updated program titled “A new approach for back-office functions in the Australian Public Service.” (see A new approach for back-office functions in the Australian Public Service.)
The new APS ERP approach replaces the Shared Services Transformation Program and sets the strategic direction for how the APS will manage its ERP corporate systems, underpinned by the principles of choice, market competition, and affordability.
The new APS ERP approach reflects a move away from highly aggregated demand for shared services (premised on a whole-of-government ERP system) to more distributed models with some areas to be a hub or provider, but in most cases letting entities directly use ERP capabilities themselves.
On 5 January 2024, AGD advised it no longer intended to proceed with onboarding to GovERP (Services Australia 2024).
In February 2024, the related GovERP governance committees were dissolved (Services Australia Chief Information Officer 2024). GovERP was also renamed to SA ERP to reflect the APS ERP approach no longer pursuing a wholeof-government build. It was intended that GovERP designs be repurposed for use by Services Australia, and any entities who choose to use it, pending the outcomes of this reusability assessment (see A new approach for back-office functions in the Australian Public Service). In subsequent correspondence of 26 April 2024, the Hon Bill Shorten MP advised, Services Australia has refocussed efforts to determine the functional requirements of the ERP solution for Services Australia”…and “[t]he remaining [GovERP] budget [of $21.8m] will be used to continue sustainment of the current ERP solution” (see Reference 4).
The Panel recognises that multiple APS entities will likely be coming forward soon for ERP uplifts as the need for well-functioning ERP capabilities across government has not abated. These uplifts reflect core underpinning capability of all government entities. As such, formal cross-APS governance structures are needed to ensure common approaches and limit customisations as much as possible.
Guidance from senior executives, such as Secretaries Data and Digital Committee (SDDC), is particularly important in anticipation of removal of the government’s existing investment moratorium on ERPs.
Experience from the heavy industry sectors suggests ERP implementation requires a sustained commitment and continuity from the top, as they are hard to execute and stay the course through the ups and downs of what is usually a complex project.
Off