SAP S/4HANA rollout at Queensland Health went so well that hospitals bent over backwards to avoid using it
- Reference: 1601302151
- News link: https://www.theregister.co.uk/2020/09/28/queensland_health_sap_s4hana_rollout/
- Source link:
A [1]report by the Queensland Audit Office [PDF] shows that the ministerial department responsible for operating the state's public health services experienced a troubled launch of the new system, which had been delayed twice and over-ran its budget by AU$33.5m.
The finance and supply chain system had been set to go live on 1 November 2018, but was put back to January 2019 and eventually went live on 1 August 2019, according to the report.
It said: "While the system operated as implemented, deficiencies in managing staff training and system customisation resulted in staff and vendors of Queensland Health soon encountering problems. Staff and vendors both experienced an adjustment period as they became familiar with S/4HANA."
Within the first four months of going live, the system was the subject of 17,181 service desk requests. At the same time, AU$540m of vendor invoices were paid late due to improved quality controls and system configuration issues.
Queensland Health, which runs 16 hospitals and health services across the state, began its upgrade project in 2016 with a plan to replace its 22-year-old finance and materials management information system, also based on SAP technology, with one based on the in-memory HANA database and related applications. The original budget was AU$105m, but by November last year that had increased to AU$135 million.
Lack of training on the new ERP system seems to have been at the heart of the problems.
As a result, 15 of the 16 hospitals operated by Queensland Health adopted manual workarounds to solve problems after the go-live date. These included placing direct orders with suppliers to bypass the need for inventory to go through the centralised distribution warehouses, despite warehouse stock being available for order; placing urgent off-system orders via email or telephone instead of through S/4HANA; and using corporate credit cards to pay outstanding invoices to reduce the risk of vendors withholding supplies, the audit report said.
It also found that hospitals had trouble ordering supplies in the right quantity and that users did not fully understand the system capabilities and processes.
Additionally, the health department had technical difficulties with a reporting tool external to S/4HANA. The problems resulted in the organisation being unable to produce reports on vendors charging goods, vendors with bank account changes and duplicate vendor master records.
Neither Queensland Health nor SAP have responded to The Register ’s request for comment.
Although the launch of the new ERP system was beset with difficulties, the audit report did note that overall it had "significantly improved Queensland Health's supply chain management capability". The software also resulted in increased purchasing power and better demand management. ®
Get our [2]Tech Resources
[1] https://www.qao.qld.gov.au/sites/default/files/2020-09/Queensland%20Health%27s%20new%20finance%20and%20supply%20chain%20management%20system%20%28Report%204%E2%80%942020%E2%80%9321%29.pdf
[2] https://whitepapers.theregister.com/
Re: So tell me if you heard this one: an ERP deployment goes horribly over budget...
You can get a horribly-over-budget ERP deployment from any of SAP's onshore partners; I think this is the inevitable result of trying to adopt SAP rather than anything related to offshoring.
Lack of training on the new ERP system seems to have been at the heart of the problems.
It's never the system. Couldn't be. Just not had enough training.
Re: Lack of training on the new ERP system seems to have been at the heart of the problems.
They've had training, they're just not using it right. You need to adopt mangle your business processes to be in line with how SAP works functions hobbles.
Sounds good
Less than a year late, less than 30% over budget, and the system was actually implemented and "worked" (for some definition of worked). That sounds like a successful ERP project to me! I'm guessing this puts it into the top 1/3 rd of all ERP projects using SAP.
Hell, just getting the system implemented and it not immediately falling over probably puts it into the top 1/3 rd.
This sounds like the sort of thing that goes wrong big when something big goes wrong, e.g. a worldwide virus epidemic. And shows up in Private Eye or an Australian equivalent.
Back here next year for Auditing 2: This Time It's Personal Protective Equipment?
So tell me if you heard this one: an ERP deployment goes horribly over budget...
Then over-promises, under-delivers, and users revolt... So what terrible Indian outsource shop/slave market did they use?