EnergySys is built around a small number of powerful components. Domain experts build applications that reflect how your business operations actually work.
Platform features.
The building blocks.
Everything in EnergySys is configured, not coded. The platform is metadata-driven: the data structures, screens, workflows, logic, and security roles are all defined as configuration, not custom code. That means they can be changed quickly, without a software development team, and without touching the underlying platform.
There are five core components.
Objects.
Objects are the data structures that hold your business data. They define the entities your operations depend on: assets, wells, facilities, contracts, metering points, or whatever your business requires. Relationships and hierarchies between objects reflect how your data is actually organised.
Processes.
A process takes data from objects, loads it into an Excel workbook, performs any required transformation or calculation, and outputs the results back into the platform. Calculations happen in Excel, in the language your team already knows and trusts. Nothing is hidden in proprietary code. Every step is auditable. Processes can be triggered manually, on a schedule, or automatically by system events.
Reports and layouts.
Reports and layouts are configurable outputs that let business users consume validated, calculated data in the format they need. Output to Excel, PDF, or feed data downstream via OData API to dashboards, BI tools, or data lakes.
Security and permissions.
Role-based access controls determine who can see, edit, and approve data. Permissions are configured to match how your organisation actually works, down to the individual user and object level. Federation with your Identity Provider (IdP) means user access is managed centrally.
Notifications and logs.
Every process execution is logged. Validation errors are flagged. Calculation logs record what ran, when, and what it produced. When an auditor or regulator asks how a number was produced, you can show them the full working.
Connecting to your existing systems.
EnergySys doesn’t sit in isolation. Connectors bring data in from the systems your operations already rely on, so everything flows into a single, governed environment.
Historians.
PI, IP21, and PhD bring in field meter readings directly.
Database (SQL) connectors.
Pull operational data from any SQL database, including Aurora, Oracle, and SQL Server, into the platform.
Email connectors.
CSV, TXT, Excel, and XML content is read and processed automatically, whether it arrives as an email attachment or in the message body itself.
OData.
Read-only endpoints feed dashboards, ad-hoc reporting tools, and data lake pipelines. The newer OData v4 API also supports create, update, and delete operations for more complex integration requirements.
What people use it for.
The same platform components support a wide range of operational workflows. Here are the most common.
Production and allocation.
Import data from field historians, validate against reference data, run allocation calculations in Excel, generate partner reports for joint ventures. Full audit trail maintained throughout.
Governance and reporting.
Maintain reference data through objects. Generate and distribute regulatory and operational reports on a schedule or on demand.
Measurement and validation.
Import metering data, run validation checks, flag anomalies for review before data moves downstream.
Forecasting and planning.
Support manual data entry and approval workflows for production plans and nominations. Export to Excel or OData for decision-making tools.
Environmental and compliance.
Consolidate emissions data across assets, validate against reference data, and produce regulator-ready outputs.
What makes it different?
Other platforms hide their logic, require developers to make changes, and lock you into a vendor relationship that’s expensive to leave.
EnergySys is built on the opposite assumptions. The logic is open, visible in Excel, and traceable back to source. Domain experts configure directly, without a programming background. And because the platform is separated from the applications built on top of it, upgrades happen without touching your configuration.
The applications built on EnergySys belong to the organisation that owns them. Partners can build, hand over, and move on. Clients can change partners without losing their system. Nobody is locked in.
See it in practice.
The best way to understand what EnergySys can do is to see it applied to a real workflow. Our customer stories show how operators and their partners have built production allocation, emissions management, and regulatory reporting applications on the platform.
