| H2R1 | For an agency that has a large IT support team, ongoing management and upgrade of this solution would be achievable. For smaller entities, closer consideration would need to be given to maintenance implications. |
|---|
| H2R2 | The whole of government GovERP template has not been updated for the new whole of government common conditions. |
|---|
| H2R3 | A number of the WRICEF enhancements that were implemented were required to make the system suitable for public sector use. |
|---|
| H2R4 | While the solution offers comprehensive HR management capabilities, and a lot of reporting capability out-of-the-box, in-depth analytics and reporting is not fully provisioned. |
|---|
| H2R5 | To enable shared services, data separation on the same tenant would need to be built and tested. |
|---|
| H2R6 | For ongoing use, application regression testing, and any resolution of defects, or resolution of custom or enhanced codes, will be the responsibility of the customer to manage, not the vendor. There will be at least two application upgrades a year. |
|---|
| H2R7 | There are 18 H2R WRICEF's, most of which will require effort to maintain. |
|---|
| H2R8 | Advice has been provided from Services Australia, that 'Manage APSED Report' is the only sub-component within Employee Management outstanding in the build. Similarly, within Payroll Services, only 'Manage Salary Recall' has not passed functional testing. |
|---|
| H2R9 | The existence of WRICEF components highlights the importance of considering the maintenance overhead associated with these customisations when assessing the reusability of H2R capabilities in GovERP. |
|---|
| H2R10 | If entities only want to use specific capabilities, or any part of the solution stack, then an appropriate commercial construct would likely be required at a whole of government level. |
|---|
| H2R11 | MVP1.1 with AGD enhancements already sits on top of MVP1.1. The solution is now ageing. Further delays of how to use this platform will put the re-use agenda further out of reach for ERP. |
|---|
| H2R12 | A whole of government standard could be set on how vendors need to operate with the APS in order to deliver on ERP services. This would greatly increase the chance of interoperability and re-use in the sector. |
|---|
| FIN1 | S/4HANA will need to be upgraded from FPS01 (2021) to at least the October 2023 build to reduce ongoing out of year maintenance, and to remain on the upgrade path, noting that the underlying technical stack (ABAP/T) has had a version change between 2021 and 2023. |
|---|
| FIN2 | 38% of the processes within Finance were not agreed to by the BPMC and have not been ratified. |
|---|
| FIN3 | IRAP assessment of the FMIS relied heavily on security settings in Microsoft Azure. |
|---|
| FIN4 | There are 89 Finance WRICEF's (63 in B2R and 26 in R2B), most of which will require effort to maintain. |
|---|
| FIN5 | S/4HANA is the on-prem version, tenanted on the Service Australia private Microsoft Azure cloud. This version could be installed locally by another agency. |
|---|
| FIN6 | Note the number of customisations and enhancements in the solution, it is likely that unless an entity has a large existing SAP workforce, that ongoing maintenance and upgrade of the solution will be difficult. Equally, for a large agency with complex ERP needs, the solution could be used as an accelerator. |
|---|
| FIN7 | Consideration should be given to the integration layer that has been built during the project, it is likely the ability to integrate and pass data between other core systems and GovERP exists, and could be considered for initial data standards / integration standards. |
|---|
| P2P1 | There are 37 P2P WRICEF's, most of which will require effort to maintain. |
|---|
| TEMS1 | Expense8 has had several functionality uplifts prior to the handover of GovERP to Services Australia, and as a configurable SaaS product, is able to be immediately reused by other entities. |
|---|
| TEMS2 | None of the WRICEFs built into the TEMS solution (Expense8 and GovComply) are anticipated to have a high complexity of ongoing maintenance. As a SaaS solution, the vendor is responsible for the ongoing management of these WRICEFs. |
|---|
| TEMS3 | There are 10 TEMS WRICEFs, all of which will require a low effort to maintain. |
|---|
| TEMS4 | Despite the build status of the GovERP template for TEMS, Expense8 can be operated independently of GovERP as a standalone product, which can be integrated into another entity's environment. |
|---|
