Appendix C can be found on digital.gov.au together with this Eminent Panel report.
There is also a download link for a PDF on the Enterprise Resource Planning landing page.
OffERP Consultative Committee member entities:
Note: These entities were also represented in the Assessment’s interviews and working group.
Off
The above table is a list of capabilities grouped by value stream.
Within this set of capabilities, a scope for initial delivery (MVP) and target state were both defined, as reflected in the blue and purple respectively. Capabilities marked with a star are those Extended Capabilities that were to be considered for inclusion in the scope of Shared Services.
A brief description of each of the MVP1.1 functional capabilities is below.
| Capability | Description |
|---|---|
| Hire to Retire (H2R) | |
| Learning management | This capability relates to administration, documentation, tracking, reporting, and delivery of educational courses, training programs, or learning and development initiatives within an entity |
| Leave and absence management | Processes and systems used by an entity to manage employee time off, including vacation, sick leave, and other types of absences |
| Organisational management | Process of planning, coordinating, and overseeing the various functions and operations within an entity |
| Performance and goals management | Setting, tracking, and evaluating employee performance against established goals and objectives |
| Recruitment | Process of identifying and attracting candidates to fill job vacancies within the entity including the entire hiring process, from inception to the individual recruit's integration into the entity |
| On-boarding | Integration of new employees into an entity |
| Off-boarding | The process of managing the departure of an employee from an entity |
| Work time and attendance | Systems used by entities of all sizes, across the APS, to ensure accuracy of employee's time and attendance, pay and absence requests |
| Time sheet recording and management | Tracking and managing employee work hours and attendance |
| Capability | Description |
|---|---|
| Manager self service | Enables managers to access personnel data for their direct reports, such as leave, time-off, performance, and learning information. |
| Employee self service | System that supports employees to access and manage their own personal and employment-related information |
| Payroll services | Administration of an entity's employee's financial records including salaries, wages, bonuses, deductions, and net pay |
| Employee management | Processes, systems, and practices used by an entity to manage its workforce |
| Budget to Report (B2R) | |
| Asset accounting | Sub-ledger that records the financial transactions related to an entities’ assets |
| Cost management | Planning, estimating, budgeting, and controlling costs in a project or business operation |
| Funds management | Managing and overseeing the financial resources of an entity |
| General ledger | Complete record of all financial transactions over the life of an entity |
| Project accounting | Financial transactions related to managing a project including costs, billing, and revenue |
| Tax management | Management of an entity’s tax obligations to ensure Australian tax laws and regulations compliance |
| Statutory reporting | The mandatory submission of financial and non-financial information by an entity to the australian government or regulatory bodies |
Management reporting | Provision of information to managers, to assist with informed decisions including tracking progress or KPI’s, identifying trends, and highlighting areas that may require attention or improvement |
| Budgeting and planning | The process of creating a detailed financial plan for an entities’ future expenses and revenues |
Commonwealth reporting | Mandatory reporting requirements for Australian Government entities to prepare and submit financial statements, performance reports, and other information to the government in accordance with relevant legislation and accounting standards |
| Lease accounting | The accounting treatment of leases, which are contractual agreements between a lessee and a lessor for the use of an asset |
| Revenue to Bank (R2B) | |
| Accounts receivable | Funds that customers owe for products or services that have been invoiced |
| Banking and cash management | The operational and banking processes associated with the collection, aggregation, holding and disbursement of cash |
| Procure to Pay (P2) | |
| Service procurement | The process of acquiring services from vendors including preparing RFTs/RFQs, managing purchasing and contract lifecycles, sourcing, requisition, order processing, payments and reporting |
| Purchasing | Purchase of goods and/or services by an entity |
| Capability | Description |
| Receipting | The process of recording and acknowledging the receipt of goods, services, or payments |
| Contractor management | Management of the relationship between an entity and its contractors |
| Contract management | Process of managing legally binding agreements including creation and negotiation, contract execution, contract compliance monitoring and renewal or close out |
| Accounts payable | Money owed by the entity to its vendors |
Report procurement activities | Reports showing procurement activities, costings and purchasing information regarding goods and/or services |
| e-Procurement | Use of electronic methods to conduct transactions between buyers and suppliers |
| Whole-ofgovernment central purchasing | Whole-of-government procurement designed for permission-based services as permits, accreditations, licenses, and registrations |
Supplier management | Task ensuring suppliers meet the expectations of their contract |
| Sourcing | Process of locating products or services outside the entity |
| Travel and Expense Management (TEMs) | |
| Expense management | Bookkeeping system for controlling, tracking, and processing employee expense reimbursements |
| Auditing and compliance management | Measurement of an entity’s adherence to rules and regulations, standards, and any relevant internal bylaws and codes of conduct |
Credit card management | Employee-related corporate credit card transactions |
Travel management | System used by entities to oversee and facilitate business travel |
This Reuse Assessment Review report is an independent assessment of the Australian Government ERP ecosystem, GovERP.
Taking into account what has been built as part of MVP 1.1 in preparing to onboard the Attorney-General’s Department (AGD) and the full scope of the ERP requirements of Commonwealth entities (MVP1.0), the assessment provides evidence upon which to assess the reuse potential of the GovERP solution and the ability to implement the Hire to Retire (H2R), Budget to Report (B2R), Revenue to Bank (R2B), Procure-to-Pay (P2P) and Travel and Expense Management (TEMS) value streams.
The report provides:
This report includes the following:
This report does not cover:
The report refers to the following government artefacts:
The approach developed to undertake the reuse assessment is outlined in the figure below.
This phase outlines the pragmatic considerations for reuse, including:
All these factors are collectively assessed to determine the viability of reuse.
The whole of government Shared Services Program, led by the Department of Finance, commenced in 2014 with approval from the Secretaries Board.
The enabling technology for the Shared Services Program, GovERP, began in 2017 when the Department of Finance undertook a Request for Proposal for a whole of government ERP. The GovERP Program aimed to consolidate and standardise common transactional corporate Australian Public Service (APS) processes and services aiming for cost-effectiveness, scalability, and advancing the one-APS vision while enhancing Australia’s digital capability.
In contributing to the government’s digital transformation, GovERP was intended to improve day-to-day operations within government departments, facilitating smoother interactions between entities, thus streamlining the access to (and consumption of) corporate services within the APS. This intended future state is illustrated in Figure 4 below.
The current GovERP solution serves as an initial framework aimed at establishing the groundwork for future enhancements and deployments. The current solution was paused mid-flight in November 2023, and hence a number of capabilities are still under development, and all testing
was not completed.
Figure 9 provides an overview of the build completeness of the MVP1.1 build in terms of both value stream and functional capability.
This letter appears on Digital Transformation Agency letterhead and comes from the CEO.
Dear Mr Hazlehurst,
RE: Services Australia ERP (formerly GovERP Reuse Assessment)
I am writing to provide an update on progress and preliminary observations of the Reuse Assessment currently being undertaken by the Digital Transformation Agency (DTA).
Reason Group Pty Ltd has been engaged as ERP specialists to develop a technical assessment of potential reuse opportunities. The draft technical assessment has been shared with Services Australia to ensure its accuracy, prior to consideration by the independent Panel of Eminent People. While the technical assessment is still in draft form, I would like to share preliminary observations and insights to keep you informed of progress.
The technical assessment considers potential reuse opportunities across three tiers:
The initial observations suggest substantial components of GovERP have been developed, however sufficient testing has not been undertaken on many of the components to enable confidence of reuse as 'Tier 1' opportunities. Further, it appears many GovERP components prioritised requirements of the Attorney General's Department (AGD) and, at the time of the program pause, were understandably not progressed to the level required for broader whole-of-government use.
Observations, as at 15 May 2024, indicate:
Initial analysis suggests cross-government Tier 1 reuse opportunities may be further limited from a commercial perspective for smaller agencies with less complex needs, particularly when considering 'choice' under the new APS ERP arrangements. Reusability could be appropriate for a specific implementation, or for a larger agency with more complex ERP needs such as Services Australia; I understand consideration of this is ongoing.
The assessment is likely to establish some reuse opportunities as potential accelerators or learnings for agencies ('Tier 2' and 'Tier 3' opportunities). Ideally, any reusable content from the Services Australia ERP can also be leveraged through the Australian Government Architecture. Examples of potential 'Tier 2' and 'Tier 3' reuse opportunities include:
Finally, it is fair to say that the evolving view will indicate that Tier 1 use of GovERP would be most likely to relate to implementation within your agency and possibly (but not confidently yet) to your connected agencies to which you currently provide services.
In this context, I look forward to continuing collaboration with you and your staff to support the new APS ERP approach. I would be happy to discuss the Reuse Assessment's observations and insights at your convenience, including the Eminent Panel’s potential findings and recommendations.
Kind regards
Chris Fechner
20 May 2024
This letter appears on The Hon Bill Shorten MP's letterhead
The address on this letter reflects that it is written to Senator the Hon Katy Gallagher
Dear Minister
I am writing to provide an update on the Government Enterprise Resource Planning (GovERP) Programme, now known as Services Australia ERP (SA ERP).
Since your announcement on 28 November 2023, the Attorney-General’s Department, the only agency that agreed to onboard to the ERP solution in 2024, advised it no longer intends to onboard and requested any system-related activities cease. The Attorney-General’s Department is exploring alternative solutions to meet its requirements and budget.
The ERP solution was originally conceived and costed to service the Australian Government’s first of six shared services hubs which provided economies of scale that are no longer applicable. The establishment and onboarding of Services Australia’s shared services hub was not scheduled until a later phase of the project. The development of the current ERP solution had primarily focussed on meeting the Attorney-General’s Department’s requirements, which in its current form are not suitable to meet the expansive operational requirements of Services Australia.
The mid 2023–2024 Mid-Year Economic and Fiscal Outlook (MYEFO) process agreed that the Digital Transformation Agency would undertake an independent re-use assessment of the ERP solution, with any future requirements to be considered as part of the 2024–25 MYEFO process.
On this basis, Services Australia has refocused efforts to determine the functional requirements of the ERP solution for Services Australia.
In February 2023, you agreed to reprofile $60 million of Services Australia’s original GovERP budget allocation to the 2023–24 financial year. As at 31 March 024, the Programme has spent $38.2 million of the Agency’s 2023-24 budget. The remaining budget will be used to continue sustainment of the current ERP solution, including ongoing licencing and hosting costs of the platform.
Yours sincerely
Bill Shorten
26 April 2024
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
A complex diagram showing Services Australia-developed MVP1.1 functional capabilities. 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.
The diagram also shows two capabilities as ‘Target capability’ built. These are supplier management and sourcing in procurement under ‘Functional’ capabilities.
The Digital Transformation Agency (DTA) engaged Reason Group to prepare this report which provides an in-depth technical assessment of the Australian Government's Enterprise Resource Planning (GovERP) technology platform, with a particular focus on its potential for reuse by other government entities. The report is intended to support and inform a Panel of Eminent People appointed by the DTA to evaluate the suitability of GovERP (see Reference 1) use by Services Australia, and potential reuse by other Commonwealth entities to support their implementation of future costeffective ERP uplifts.
The assessment considers (see Reference 2) various aspects, including the current state of GovERP by value stream, which encompass critical business functions such as Human Resources, Finance, Procurement, and Travel and Expense Management. Its readiness for reuse, identification of reusable components, and considerations for implementation by other entities have been assessed within this report. The assessment highlights the progress made in GovERP’s development, comparing the original intended full solution (or capabilities) with what was built by Services Australia (see Reference 3) at the point of the project’s pause. Reason Group are also aware of a number of project decisions and change requests, however, this assessment is not litigating these but rather considering the current state for reusability.
The build status for core capabilities as per the intended full solution and Minimum Viable Product (MVP) scope is summarised in the below table. For the Service, Governance and Enabling layers, many capabilities were paused when decisions were made to move away from the original GovERP operating model.
| All capability layers | Full GovERP Solution coverage | MVP1.1 solution coverage | ||
|---|---|---|---|---|
Built (see Reference 4) | Planned | Built | Planned | |
| Service Layer | 3 | 16 | 3 | 16 |
| Functional Layer | 19 | 54 | 18 | 39 |
| Governance Layer | 0 | 10 | 0 | 10 |
| Enabling Layer | 0 | 38 | 0 | 36 |
| Total | 21 | 118 | 21 | 101 |
In respect of the Governance and Enabling layers, these were specific to the Shared Services operating model, so are not considered relevant for reuse. Further, all components of the Services layer were deemed out of scope of this assessment (see Reference 5).
A breakdown on the value streams of GovERP is summarised below.
| 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 Reference 6) | 9 |
| Travel and expense management (TEMS) | 0 | 4 | 0 (see Reference 7) | 4 |
| Total | 19 | 54 | 18 | 39 |
Based on the current build status, environmental considerations around data, integration and hosting, reuse has been conceptualised at three distinct levels:
The table below summarises the core components which are reusable from GovERP.
| Value stream | Technology | Tier 1 | Tier 2 | Tier 3 |
|---|---|---|---|---|
| Hire to Retire (H2R) | SAP Success Factors | not reusable | reusable | reusable |
| Finance, including Revenue to Bank (R2B) and Budget to Report (B2R) | SAP S/4HANA | not reusable | reusable | reusable |
| Procure-to-pay (P2P) | SAP S/4HANA | not reusable | not reusable | reusable |
| Travel and expense management (TEMS) | Expense8 | reusable (see Reference 8) | not reusable | reusable |
As part of this assessment, SAP provided advice there is nothing visible in the core solution which limit supportability or reuse, and that the standard code included no changes (see Reference 9).
In addition, there are 17 other technology (see Reference 10) components that are used in the end-to-end GovERP solution, that may provide accelerators for entities who adopt (or adapt) to the above SAP technologies.
While GovERP shows promise as a solution for large entities like Services Australia, with potential benefits for accelerating their ERP journey, it may present capacity and budgetary challenges for smaller entities. Alternative service models or technology solutions should be considered by smaller entities.
Moreover, the completeness of the GovERP build suggests it may not yet be ready for adoption by other entities. Further testing, refinement and completion of missing components are necessary to ensure any component could be suitable for reuse. Services Australia emerges as the logical entity to complete the component build, given the complexity of their ERP requirements, and the current hosting solution for the product, compared to smaller entities in the Commonwealth.
Looking ahead, if the components of GovERP achieve maturity and completeness, it could serve as an effective accelerator pattern for other larger entities seeking to modernise their respective ERP systems. However, careful consideration of agency-specific factors and requirements will be essential to maximise the potential benefits of GovERP’s reuse across the government sector.
This phase examines the current state of the GovERP system’s construction. Technical capabilities are evaluated based on a standard system development lifecycle, with an assessment of each capability’s progress.
Within GovERP, three templates exist:
For the purposes of this assessment:
Further, assessment against the following dimensions of the build completeness has been
conducted:
The evidence gathered throughout the review can be categorised into three main areas:
To understand the current state of the GovERP build, extensive research has been conducted,
including:
This phase is concentrated on identifying concrete opportunities for reuse within GovERP. The concept of reuse has been broadly interpreted, encompassing the use of existing technology and leveraging pre-existing processes or patterns. Nonetheless, to reuse something is to make use of it more than once for a different purpose, or for a subsequent time.
The Digital and ICT Reuse Policy outlines three high-level requirements for reuse:
Based on the policy, the current build status, environmental considerations around data, integration and hosting, reuse has been conceptualised at three distinct levels:
These three levels are shown in the figure below.