Harbour Energy merger: how EnergySys grew through a corporate merger and kept going
When two companies merge, software systems are usually the first casualty. Licences get reviewed, replacements get scoped, and something gets switched off.
That is not what happened here.
When Chrysaor merged with Premier Oil to form Harbour Energy, EnergySys came through the other side. Not just retained, but extended. A newly formed company, with every reason to start fresh, looked at what Chrysaor had built and chose to build more of it.
Challenge: a major acquisition, an inherited system, and no time to wait
Chrysaor was a North Sea exploration and production company focused on the development of dormant discoveries and incremental reserves. Following a significant acquisition of North Sea assets, the team quickly identified that the incumbent production data management system was not fit for purpose.
The portfolio had grown fast. The system hadn’t kept up. Chrysaor needed something with high levels of flexibility, automation, stability, and security, and they needed to turn it around within tight deadlines.
Solution: deployed fast under Chrysaor, extended under Harbour Energy
Chrysaor deploys EnergySys
Chrysaor selected EnergySys and worked with reseller partner Accord Energy Solutions on the implementation.
Accord’s scope was broad from the start: production and revenue forecasting, physical and commercial allocation to fields and wells, loss management, non-operated production reporting, hydrocarbon pricing, sales and inventories, and emissions reporting. The deployment was completed within Chrysaor’s tight deadline.
A merger, and a decision
Chrysaor merged with Premier Oil to form Harbour Energy. It was a significant corporate event. The newly formed company now operated 20 facilities and over 200 wells, with a portfolio that spanned the North Sea.
In that context, the EnergySys deployment could easily have been reviewed and replaced. Instead, Harbour Energy looked at what was already running and decided to go further.
Harbour Energy extends the platform
Rather than starting again, Harbour Energy enacted a corporate-wide deal to extend EnergySys across all its UK North Sea assets.
”Following the development of the Solan Oilfield, Harbour Energy required a system to provide stability, security, and flexibility, and to replace a legacy system that was no longer compatible with the recent growth of our company. We saw EnergySys as an ideal solution because their architecture provides much more flexibility to accommodate change than previous systems. It allows us to layer on extra functionality whilst still allowing upgrades to the underlying base code.
Programme Manager, Harbour Energy
The extended scope covered an FPSO with three connected fields and multiple partners, as well as all non-operated assets. Both Harbour Energy’s internal team and Accord continue to handle configuration as the business evolves, with no vendor dependency for day-to-day changes.
Outcomes: a platform that outlasted a corporate restructure and kept growing
- A rapid legacy system replacement delivered within tight deadlines following Chrysaor’s major North Sea acquisition.
- Full production data management across the acquired portfolio, covering production and revenue forecasting, physical and commercial allocation, loss management, non-operated production reporting, hydrocarbon pricing, sales and inventories, and emissions reporting.
- EnergySys was retained and extended following the Chrysaor and Premier Oil merger to form Harbour Energy.
- A corporate-wide deal rolled out across all UK North Sea assets, including an FPSO with three connected fields and multiple partners.
- Ongoing configuration shared between Harbour Energy’s internal team and Accord across 20 facilities and over 200 wells.
The bottom line.
Chrysaor needed a system that could move fast. They got one.
When the business became Harbour Energy, that system was already embedded deeply enough to survive a full corporate merger. Not because it was difficult to remove, but because the people using it didn’t want to.
That is a different kind of proof of value.
