The figure describes the approach phases that the assessment underwent. From assessing the build status, to evaluating what could potentially be reused, to how to implement the artifacts.
The image shows a six-part process in a wheel, showing that stage six feeds back to stage one in a constant cycle. The six stages are:
The figure describes the intended future state of uplifting an agency's enterprise resource planning from their current to future state into GovERP.
The image shows 90+ agencies with bespoke systems, shown as the 'current' state, and shows them all moving to GovERP as the 'future' state. It shows a single system for all agencies, rather than agencies each with a bespoke system.
OffGovERP was overseen by the Shared Services Sub-Committee (SSSC), comprising 13 Government entities (see Reference 2). Program delivery was a collaborative effort between the GovERP Program, Provider Hubs, and Client entities across three releases, focusing on staged delivery of an MVP in line with the P2A framework (see Reference 3).
Smaller entities were envisaged to utilise alternative technology bases such as TechnologyOne / Aurion (overseen by the Department of Industry, Science and Resources) or Oracle, and larger entities were envisaged to utilise an SAP solution overseen by Servies Australia.
The Program aimed to serve approximately 90 Commonwealth entities and around 130,000 APS staff, replacing existing ERP systems in use at five shared services hubs (see Reference 4) within:
The Program’s intended operating model was two corporate service ‘hubs’, specifically:
In November 2023, the Minister for the Public Service announced a new APS ERP approach, concurrently repurposing GovERP for use by Services Australia.
Figure 5 provides a high-level overview of the significant events in the history of GovERP. Further details can be found in Appendix I.
The MVP (see Reference 5) encompasses the planned capabilities for GovERP, as agreed by the Shared Services Steering Committee as outlined in Figure 6 below.
The MVP was determined based on Steering Committee Strategic Policy Decision 12
(December 2020; see Reference 6), which specified mandatory and non-mandatory capabilities. These capabilities represented what an agency would mandatorily need to deliver on; that is, the requirements that are mandated through legislation, policy, and enterprise agreements.
The salmon boxes in Figure 6 refer to those Decision 12 MVP components which were deprioritised in response changes identified during delivery of GovERP, and were not built by Services Australia. Therefore, the assessment of what has been built by Services Australia excludes these MVP salmon boxes.
Capabilities beyond the MVP were labelled as ‘target’ (or ‘extended’; see Reference 7), and were intended for future phases of the GovERP program.
Entities requiring capabilities beyond the MVP scope were required to facilitate their own integration using standard interfaces of those out-of-scope areas. This applied to both capabilities that are entirely out of scope and capabilities where a consumer chooses to use an alternate solution to that provisioned in the MVP.
This figure describes the timeline of GovERP at a high level from November 2014 to January 2024.
A complex diagram showing whole-of-government ERP capability. There are four main areas: service, functional, governance and enabling. These categories are then split into subcategories, which have a number of capabilities. These capabilities are then identified as either
The contents of the diagram follow as a list. Each of the four main areas is divided into its subcategories, which then list the individual capabilities and their current status.
To support the future one-APS vision, it was important to consolidate and standardise disparate corporate processes within the Australian government. The GovERP value streams comprise:
Service and functional capabilities within the business capability model have been mapped to value streams in Figure 7 below. These highlighted capabilities represent most of the functionality for each value stream, although not necessarily all capabilities involved.
The graphic shows capabilities, grouped by type business area, and which value stream they are in. The following list is ordered by type, then business area, then capability type.
Entities are expected to access services through value streams, which delineate the scope of offerings. While five value streams support functional capabilities, two of them (Prepare to Adopt and Enquire to Resolve; see Reference 10) are pivotal for the service management and the on-boarding of client entities and Provider hubs.
Value streams transcend capabilities and functions, and entities within shared services, integrating these elements to deliver value to stakeholders.
Rather than representing discrete services, value streams embody overarching lifecycles in which all entities participate to achieve business outcomes.
Each value stream encompasses a series of customer journeys and associated processes.
The MVP was designed as a foundational template encompassing essential solutions necessary for supporting critical government functions. These solutions included robust capabilities in human resources, finance, procurement, and travel and expense management, forming the core framework of the ERP system designed to meet specific APS requirements.
Additionally, it embraced additional edge functionalities like recruitment, onboarding, learning management, success planning, and performance measurement, enhancing the versatility and utility of the ERP solution.
Core and edge capabilities were categorised as:
The Core implementation was standardised; however, entities had flexibility to choose Edge products according to their specific needs. A panel of products and partners was established, offering a range of options for Edge products.
GovERP adopted an incremental delivery approach for both core and edge capabilities, aligning with a whole of government solution template.
GovERP’s core offerings comprised SAP S/4HANA and SAP SuccessFactors, with various other capabilities operating as ‘Edge’ systems extending the core. Provider Hubs used this template to create an instance of the GovERP system to support their client entities.
External and internal traffic was expected to pass through an outsourced Secure Internet Gateway (SIG), with all GovERP SaaS applications hosted on secure clouds in Australian data centres. Note, a vendor was procured for the SIG, but the contract was not executed given the pause of the GovERP Program.
The graphic shows core and edge capabilities, grouped by business area, and whether they are core capabilities or edge capabilities. The following list is ordered by business area, then whether capabilities are core or edge capabilities.
The table above contains the following information:
• Learning management
• Leave and absence management
• Organisational management
• Performance and goals management
• Recruitment
• On-boarding
• Off-boarding
• Work time and attendance
• Time sheet recording and management
• Manager self-service
• Employ self-service
• Payroll services
• Asset accounting
• Cost management
• Funds management
• General ledger
• Project accounting
• Tax management
• Statutory reporting
• Management reporting
• Budgeting and planning
• Accounts receivable
• Banking and cash management
• Services procurement
• Purchasing
• Receipting
• Contractor management
• Contract management
• Supplier management
• Expense management
• Auditing and compliance
Note, no System Integration Testing (SIT) or User Acceptance Testing (UAT) occurred as part of GovERP.
The table below summarises the current capability status within the value streams.
| Value stream | Full GovERP Solution coverage | MVP1.1 solution coverage | ||
|---|---|---|---|---|
Built | Planned | Built | Planned | |
| Hire to Retire (H2R) | 9 | 22 | 9 | 13 |
| Finance, including Revenue to Bank (R2B) and Budget to Report (B2R) | 8 | 15 | 8 | 13 |
| Procure-to-pay (P2P) | 2 | 13 | 1 (see Table note 1) | 9 |
| Travel and expense management (TEMS) | 0 | 4 | 0 (see Table note 2) | 4 |
| Total | 19 | 54 | 18 | 39 |
Table note 1: “Supplier Management” was not in scope of MVP1.1. However, Services Australia built and functionally tested this capability.
Table note 2: The vendor, 8common, advised all build elements were completed and tested, however, these were not integrated by Services Australia as part of the GovERP solution.
In respect of the above value streams, a total of 167 WRICEFs were identified as part of this assessment, of which 13 relate to AGD.
Further to the Value Stream view provided in Section 4.1, below is the current build completeness of each capability within GovERP.
The status provided aligns with the information communicated by Services Australia (see Reference 1). Appendix C provides details on the intended contents of each component box.
Engagement with stakeholders identified the need for enhancements to meet the specific requirements of other entities. Anecdotally, this was always expected within the GovERP intended operating model, prior to project’s pause. For example, additional changes to MVP1.1 with AGD enhancements were identified to address the needs and scenarios of AGD, particularly in areas such as recruitment, learning management, finance and procurement.
Further insights into the build status of each of the Value Streams is discussed in the subsequent sections.