| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Jul | Sep » | |||||
| 1 | 2 | |||||
| 3 | 4 | 5 | 6 | 7 | 8 | 9 |
| 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| 17 | 18 | 19 | 20 | 21 | 22 | 23 |
| 24 | 25 | 26 | 27 | 28 | 29 | 30 |
| 31 | ||||||
- product manager (7)
- projects (40)
- resourcing (4)
- software selection (1)
- tax billing software (32)
- vendors (49)
- water billing software (38)
- 19. April 2011: User groups
- 19. April 2011: Detecting theft
- 13. February 2011: Automated water meter reads
- 27. January 2011: What German utility billing software would that be?
- 5. November 2010: Seven myths of billing implementations
- 24. October 2010: Comparing utility billing software
- 1. October 2010: Failing in the public sector
- 29. September 2010: Project failures
- 27. September 2010: Not the product manager
- 25. September 2010: Not the product roadmap
projects
AGL Project Phoenix take-off delayed
The Australian Financial Review recently reported on energy utility AGL’s billing system overhaul, known as Project Phoenix, which has been struggling for some time to meet the ambitious savings targets it set at its inception in 2006. At the time the company forecast savings of up to $70 million a year from 2008 onwards. However the deadline for achieving benefits from the $200 million billing systems overhaul has been pushed back, after problems it experienced following the migration of customers to a new SAP system caused costs to blow out (and they’re surprized?). Spending on the project, which was originally budgeted for $80 - $90 million had swelled to $215 million by the February reporting season and has now increased to just over $230 million.
This is another lesson for those who select billing systems – while estimating savings targets is a wet-finger exercise; achieving them is something else.
Leave a Reply
You must be logged in to post a comment.