Energy operations platform
We worked with a technical partner on an energy supplier’s operational platform. Angular screens, .NET APIs and background jobs connect property records, meter readings, customer moves, tariffs, billing and service work. The workflows carry information between these stages so teams can work from the same operational records.
From installation details to customer moves
-
01 /
Connected property records
Each property links to its project, connection type, heating and cooling equipment, maintenance supplier and billing settings. Shared settings come from the project, with overrides for individual properties. Staff can maintain common installation details centrally while recording exceptions where they apply.
-
02 /
Meter readings with validation
Reading submissions for annual settlement and customer moves are checked against dates, previous readings and expected values. The API returns validation results per meter and can retain readings for review. Teams can distinguish confirmed values from readings that need attention before using them in the next step.
-
03 /
Move-in and move-out workflows
Completing a move checks its date, status and required readings, then updates occupancy and payer periods, service tickets and related consumption records. Move-in processing also updates applicable tariffs and billing batches. The customer change carries through to the records used for billing.
From annual rates to accounting
-
01 /
Yearly tariffs and rate sheets
The platform creates a new year’s tariff version from the previous one and calculates indexed rates using configured index series and percentage weights. Finalised PDF rate sheets are stored and linked to the relevant properties and year. Staff can refer back to the rates that applied to each period.
-
02 /
Invoice batches with two reviewers
Invoices are grouped into batches by project, invoice type and billing period. The release workflow records two different reviewers and sends notifications during review. Operations staff can review the batch together before invoices become ready for transfer to accounting.
-
03 /
Accounting integration
A background service sends eligible invoices through an accounting web service. It maps the payer, project dimensions, billing period and line details, including meter readings, quantities and prices. Transfer status and invoice history give staff a record of processing results and failures that need follow-up.
Information and actions for day-to-day support
-
01 /
APIs for the customer portal
The platform provides APIs for consumption, meter readings, invoice balances, payment status and invoice documents. Responses use the customer’s property and occupancy context, and include reading validation flags. The portal can show customers information already held in the operational system.
-
02 /
Complaint follow-up deadlines
Creating a complaint generates follow-up tasks with deadlines calculated in working days. The calculation skips weekends and uses a public-holiday calendar. These dated actions give the support team concrete follow-up points for each complaint.
-
03 /
Maintenance order dispatch
Work orders are sent through the maintenance supplier’s configured route: email or a structured integration. The integration includes the property, instructions, urgency and service-ticket context, and records the dispatch response. Staff can track whether the order was sent, received or encountered an error.
Discuss your next project
Tell us about your systems, requirements and the problems you want to solve.