ETRM Replacement for a Major Utility in Southern Europe
Major Project to replace in-house ETRM launched
- RFI & RFP Process chose a leading vendor
- Limited expertise in handling an ETRM replacement exposed
- Even after 12 months only delivery was a lot of Powerpoint
Project Failure loomed large
- Major Business expansion projects were stalled
- No clear vision on how to transition from the Old to the New
- Existing in-house ETRM was end of life
RFP Requirements were out of date
- Business Requirements written for ETRM acquisition were 2 years old
- Initial design proposed by vendor were not what was needed
- Existing system covered only about 30% of total features required
Limited in-house capacity & expertise
- Limited experience of in-house personnel to drive the program
- Knowledgeable resources were busy with the BAU
- Senior management needed help to resurrect the situation
Quick Fire Study to Assess
- Ran a 3 months exercise to inventorize & evaluate
- Rejected the vendor design as insufficient & in some ways unnecessary
- Proposed a new design and also implementation approach
Unique Co-Existence Design
- Build a data bridge to integrate data in the old ETRM and the new ETRM for driving downstream systems and processes
- Implemented standard products 1st and added complex businesses/products in a continuous series of Agile sprints
- Designed and implemented a custom M/W to ensure seamless integration of more than 60 upstream interfaces
1 Team for Run(Operations) & Change(Evolution)
- Blended external resources with internal in a single team
- Continuous governance via a Tactical Board of Business & IT management
- Prioritisation model took both Business Value & Degree of Difficulty into account
Just in Time Requirements & Architecture
- Quick build and demo before details led to optimal business time management
- Architectural Principle of Reuse , before buy, before build
- Continuous feedback Retrospectives drove continuous collaboration
The Roadmap
How the ETRM Ecosystem was Transformed
Quick Fire Study enabled a thorough understanding of the Business and the IT landing zone
Approach recommended a 1st deployment with core system with master data ready for incremental releases
Multiple monthly sprints released new features incrementally
Automated regression routines ensured that new features did not compromise existing functionality
Bucked the trend to demand detailed requirements – small PoC/Pilot approach with a demo for the Business allowed quicker delivery of MVPs – refinements were added in subsequent sprints
Quick successes booked earned Business and management confidence and trust
Single team for Change and Support ensured quality of delivery and also knowledge retention