Executive summary
Production allocation is one of the hardest jobs in oil and gas. It sits where metering data, commercial agreements, and joint venture rules all meet. Get it wrong and the costs are real. Revenue goes to the wrong party. Regulators issue fines. JV partners raise disputes. Trust takes years to rebuild.
For most operators, the system that runs allocation was built by someone else. A vendor scoped it, built it, and handed it over. When something needs to change, the vendor comes back. The domain expert who understands exactly how the numbers should work is not the person who changes the system. They wait.
That model is changing.
Configurable cloud platforms have given domain experts the tools to build and own the systems themselves. The hydrocarbon accountant who knows the metering data, the commercial rules, and the reporting requirements can now configure the logic directly. Some teams do that work entirely in-house. Many work with specialist implementation partners who bring both platform expertise and deep operational knowledge. Either way, the logic stays with the people who understand the asset, not locked inside a vendor’s codebase.
This paper explains why production allocation is complex to manage well. It looks at what a configurable cloud platform makes possible across different asset types. And it addresses the questions that operators still on legacy or on-premises systems tend to ask before making the move.
The complexity of production allocation
Anyone who runs production allocation knows how demanding it is. The data comes from multiple sources. The rules that govern how production is split are set by commercial agreements that can run to hundreds of pages. Measurement methods vary by stream. JV partners have their own views on how numbers should be calculated. Regulators have their own requirements. All of it needs to reconcile, every month, with a full audit trail.
The scale of that complexity is easy to underestimate from the outside. Consider bp’s Azeri-Chirag-Gunashli field in the Caspian Sea. Eight co-venturers, including bp, SOCAR, ExxonMobil, and TPAO, each with different equity stakes. Seven platforms. An average of around 342,000 barrels per day in 2024. Every barrel allocated. Every allocation defensible to every partner.
That is not an unusual level of complexity. It is the everyday reality of allocation at scale.
What makes it harder is that the rules change. Assets are bought and sold. JV agreements are restructured. New measurement points come online. Regulations shift. Each change requires the allocation system to change with it. In most organisations, that means going back to the vendor.
The hydrocarbon accountant who knows the commercial rules and the edge cases that only appear after years on the same asset is rarely the person who can change the system. They write a specification. The vendor scopes the work. A project begins. Months pass.
That gap, between the domain expert who understands the problem and the vendor who owns the system, is where risk lives. Workarounds appear. Spreadsheets fill the gaps. Manual checks multiply. The system drifts further from the operation it is supposed to reflect.
It does not have to work this way.
What changes when domain experts own the system
The allocation system should fit the asset, not the other way around
Every allocation system encodes a set of rules. Those rules reflect the commercial agreements, the measurement methodology, and the reporting requirements of a specific asset at a specific point in time.
The problem with most legacy systems is that those rules are locked in. When the asset changes, the system requires a vendor to change with it. That takes time and money. In the meantime, the team works around it.
A configurable platform works differently. The rules live in the configuration, not in the code. When a JV agreement is restructured, the domain expert updates the allocation logic. When a new measurement point comes online, they extend the data model. When a regulator changes a reporting requirement, they build the new output themselves.
The system stays current because the person who understands the asset is the one keeping it current. In many cases, that person sits within the operator’s own team. In others, a specialist implementation partner carries the build and hands over a system the operator can then manage and adapt. The important thing is that the knowledge lives in the configuration, not in a vendor’s proprietary code.
Gartner’s research on oil and gas digital transformation is clear on where the industry is heading. By 2028, more than 50% of oil and gas companies will modernise their approach to operational excellence by making intelligent, adaptable assets the primary objective of digital investment. Allocation systems that cannot change without vendor involvement are not adaptable. They are a barrier.
Different assets, different problems
Not all allocation challenges are the same. The asset type shapes the problem, and the platform needs to serve all of them.
Marginal and acquired assets
When a smaller operator acquires an asset from a major, they often inherit a large, complex legacy system with unclear ownership and licensing. Standing it up fully is expensive. But the asset needs allocation from day one.
A configurable cloud platform changes that. There are no hardware costs, no licensing issues, and no need for local infrastructure beyond a connection. Configuration can start straight away and grow as the team learns the asset. If the asset is later sold on, data and access rights transfer cleanly to the new owner.
Ancala Midstream faced exactly this when they took over the SAGE pipeline and terminal. The inherited setup was built around a system that could no longer do what the business needed. Working with an experienced implementation partner, the team moved to EnergySys and built a platform they could configure themselves, extend as needs changed, and share with shippers and partners through a self-service portal. That combination of specialist support and platform flexibility is how most operators make the move.
Mature assets
Mature assets carry years of built-up complexity. The core allocation system may work, but alongside it sits a collection of spreadsheets: extra reports, checks, and workarounds for things the main system cannot do. These are hard to audit, hard to maintain, and carry key person risk.
A configurable platform can absorb that complexity properly. The logic that currently lives in spreadsheets can be built into the system itself, with full audit trails and version control. When someone leaves, the knowledge stays in the system.
New assets
New assets bring a different challenge. Commercial rules are often not fully agreed until shortly before first production. Processes change often in the first months. Reports are added. Calculations are revised.
Traditional buying processes handle this badly. A large requirements document is produced. A bespoke system is built to match it. By the time it goes live, half the requirements have changed.
A configurable platform is built for this. Business rules can be changed quickly and in a controlled way. The team builds what they need now and extends it as the asset grows, rather than trying to specify everything upfront. A specialist partner can accelerate that initial build considerably, working alongside the operator’s own team and leaving them with a system they fully understand and own.
Questions operators ask before making the move
Operators still on legacy or on-premises systems tend to ask the same questions before moving to a cloud platform. They are good questions. They deserve straight answers.
Is it secure?
This is the most common question, and the most reasonable one. Production allocation data is commercially sensitive. JV partners, regulators, and internal teams all have an interest in knowing it is protected.
A well-run cloud platform is more secure than most on-premises setups, not less. EnergySys is hosted on AWS, SOC2 certified, and uses role-based access controls so users only see the data they are authorised to see. Data is encrypted in transit and at rest. Audit trails record every change, who made it, and when.
The risks that affect on-premises systems, including outdated hardware, unpatched software, and key person dependency, do not apply in the same way to a fully managed cloud platform. Security is handled by specialists whose entire job is infrastructure, not a secondary task for an internal IT team.
How do I get my data back?
This is a question about ownership, and it matters. Your data is yours. Full stop.
You can take backups whenever you want. The platform provider has no right to use your data beyond what is needed to run the service. If you choose to leave, you take your data with you. There are no sunk costs to make that decision expensive.
This is one of the key differences between a configurable platform and a bespoke vendor system. In a bespoke system, the logic often lives with the vendor. In a configurable platform, the logic was built by your team or your implementation partner. Either way, you own it.
Can it meet our requirements?
Allocation requirements are specific. No two assets are identical. The commercial rules, the measurement methodology, and the reporting obligations of your operation are yours alone.
A configurable platform is designed for exactly this. You do not adapt your operation to fit a pre-built system. You build the system to fit your operation, using the platform’s tools and your own domain knowledge. If your team needs support getting there, EnergySys partners bring both platform knowledge and sector expertise. They can configure alongside your team, or lead the build entirely, and hand over a system your people can own and adapt from day one.
That said, it is worth starting with what the platform offers before building a wish list. The best implementations begin with the core process and extend from there, rather than trying to capture every edge case before go-live.
Can we keep the software on-premises?
EnergySys is a cloud-only platform. There is no on-premises option.
That is a deliberate choice, not a limitation. A fully managed cloud service requires a single, consistent infrastructure. The security, uptime, and continuous improvement that come with that model depend on it.
For operators with data residency requirements, it is worth a direct conversation. AWS operates in multiple regions, and residency needs can often be met within the cloud without an on-premises deployment.
Find out what your team could build
EnergySys is the configurable cloud platform for domain experts. It gives the people who understand your operations the tools to build, own, and adapt the systems your business runs on.
See what EnergySys can do for your team, explore our platform, or get in touch at sales@energysys.com.
