Energy software development for utilities, suppliers and operators

A meter read is not a number, and the bill built on it is a restatement rather than a fact. Systems that store a reading as an integer produce invoices nobody can defend six months later.

  • Reads carry a quality flag
  • 46, 48 or 50 periods a day
  • DLMS, OBIS and CIM
  • SCADA at the boundary
What this involves

Tell us what you are building

By submitting this form, I authorize Zyneto to collect and process my personal data in accordance with theZyneto Privacy Policy.

We reply to every enquiry within one business day.

What does energy software development cover?

Energy software development builds the systems behind a meter read: interval storage, validation, estimation and editing, settlement timelines, and billing that can be defended months later. A read is a value with a source, a quality flag and a settlement status. Phase one for a metering and billing build typically runs 18 to 26 weeks.

Phase one hours
1,460 in the worked example
Timeline
18 to 26 weeks
Full module span
1,120 to 1,980 hours
Periods in a day
46, 48 or 50

Definition

What is energy software?

Energy software is two estates. The commercial side collects reads, validates them, stores intervals, settles and bills. The operational side runs the network in real time, on different data and usually a different team.

Scope

What we build for utilities, suppliers and operators

Most engagements are three or four of these. Expect to meet Itron, Landis and Gyr, Siemens EnergyIP, Oracle Utilities or Kamstrup on collection, Genus or Secure Meters in India, and SAP for Utilities, Hansen or Gentrack on the ledger.

Tariff, rating and billing integration

Time of day, block and netting arithmetic computed per interval against the contract, not per month against a total.

Prepaid balance and disconnection

A reviewable decision with the balance and the payment timeline attached, because the consequence is somebody's lights.

Market messaging and payments

Each counterparty has its own message set and rejection semantics. A flow that silently retries is worse than one that stops.

The data model

What a meter read actually is, and why a bill is a restatement

Initial settlement often runs on estimates and reconciliation replaces them with actuals months later, so a system storing one number per interval has destroyed the evidence a dispute needs. Two days a year carry 46 and 50 half hourly periods, not 48.

A value, and the unit behind it

Water and gas are billed after a conversion whose factors change, so the factors need their own dated history.

A quality flag

Accepted, corrected or estimated, with the method named. Overwrite an estimate in place and nobody can explain why March was restated.

A settlement status

Which run the read has been through, and whether its period can still move. Closed is a state the data carries, not a date.

Standards

The standards that decide the data model

Each card names where we read the instrument and when.

IEC 62056-6-1:2017, DLMS and COSEM with OBIS

The IEC webstore, read 17 November 2026, says part 6-1 specifies the Object Identification System and maps common metering data items to identification codes. OBIS separates an import register from an export one.

IEC 61850:2026 SER, substation and utility automation

Published at webstore.iec.ch, read 17 November 2026, as Communication networks and systems for power utility automation. It governs how protection and control devices exchange data.

IEC 61968-1:2020 and IEC 61970, the Common Information Model

Read at webstore.iec.ch on 13 November 2026: the distribution side builds interfaces on an Interface Reference Model, and IEC 61970-301 is the transmission base model.

IEC 62443, industrial control system security

Part 1-1, read at webstore.iec.ch on 17 November 2026, sets the terminology for network and system security. The family decides where the operational estate ends, and a path that can disconnect a customer sits on the wrong side of it.

Choosing a partner

What are the top energy software companies?

We do not publish a ranking. One written by a vendor that places itself first is marketing. Three questions sort a shortlist faster, and they work on us too.

Can they talk to your SCADA estate?

Ask where the boundary sits between the operational network and the billing path, and who owns the security review on each side.

Can they name the metering data model?

Ask which standard the read model follows and what happens to the OBIS code. An answer that flattens a read is the answer.

Will they say what they are not?

Ask for the exclusions in writing. A partner who will not name them has scoped the easy half.

Compliance

Security and compliance a buyer will ask about

Not a badge wall. Each row carries its source and the date we read it. Settlement programme dates are deliberately absent: they belong to the programme's own published plan.

InstrumentWhat it forces the software to doSource and date
NERC CIP, the Critical Infrastructure Protection standardsCyber security controls on systems in scope for the Bulk Electric System: asset categorisation, security management, personnel and training, electronic and physical security perimeters, system security management, incident reporting, recovery plans, change management, information protection, supply chain risk and internal network security monitoring.The CIP list at nerc.com, read 17 November 2026, carried 29 standards numbered CIP-002 to CIP-015: 13 mandatory, 16 subject to future enforcement. An in scope build targets the enforced version and the next one at once.
ISO 50001, energy management systemsIt certifies a management system at your organisation, not our code. What it puts on the software is auditable consumption and baseline data, so we build the reporting and you hold the certificate.The BSI catalogue, read 13 November 2026, lists BS EN ISO 50001:2018 as Current, with an amendment, ISO 50001:2018/Amd.1:2024, also Current. iso.org returned HTTP 403, so this is the UK national standards body rather than the publisher.
EU NIS2 Directive, (EU) 2022/2555Energy is the first sector listed in Annex I, sectors of high criticality. Article 23 reporting is three artifacts on three clocks, out of your incident tooling rather than a policy: an early warning within 24 hours of becoming aware of a significant incident, a notification within 72 hours, and a final report within one month of that notification.EUR-Lex, read 17 November 2026. Article 41 required member states to adopt the measures by 17 October 2024 and apply them from 18 October 2024.
GDPR and UK GDPRHalf hourly consumption reveals when a household is occupied, empty or asleep, which changes the lawful basis and the retention answer. Consent for settlement is not consent for analytics.An ongoing obligation. It belongs in the interval store's schema and retention jobs, not a policy nobody can query.

We hold no security certifications and do not imply otherwise. We build to the controls, write the evidence as we go and hand it to your auditor. We do not operate metering assets, we are not a licensed supplier or a settlement agent, and we are not an accredited provider for e-invoicing or statutory filing. On sizing a build, see how a metering and billing build is estimated module by module.

Transparency

What a phase one actually contains, module by module, in hours

None of the fourteen pages we read on this search on 14 November 2026 publishes an hour figure. Here they are, so you can argue with any line. The scope is a utility keeping its head-end and core ledger, and taking the interval store and settlement path in house.

Phase one hours

1,460

The worked example, added up module by module below.

Typical timeline

18 to 26 weeks

As a squad. A milestone inside the window compresses scope, not the calendar.

Useful hours

1,120 to 1,980

Every module at its minimum, through to every module at its maximum.

What moves the hours, ranked
DriverHours
How many meter points, and at what intervalMonthly registers and half hourly profiles are different systems at the same customer count.High impact
Whether reads already carry provenanceIf source and quality are held per read, this is integration work. If values are overwritten in place, the model goes in underneath.The largest swing
Whether prepaid is in scopeA prepaid balance is a real time obligation with a physical consequence, not a setting on a monthly bill.150 to 260
Which head-end and ledger you keepVendor API surface at your version, not the one in the current documentation. The most common mid build surprise.80 to 200 each
Whether operational technology is in scopeA SCADA, substation or control centre estate brings its own security boundary and review cycle.Medium
Hours by module
ModuleHours
Meter data acquisition and the head-end interface180 to 320
Validation, estimation and editing160 to 280
Interval store and the settlement timeline180 to 320
Tariff, rating and billing integration200 to 340
Prepaid, top up and disconnection control120 to 220
Integrations: market messaging, payments, finance160 to 280
Operational reporting, losses and audit trail120 to 220

Phase one, added up

  • Meter data acquisition 230 plus validation and estimation 210 plus interval store and settlement 230 plus tariff and rating 260 plus prepaid and disconnection 150 plus integrations 220 plus reporting and audit 160 equals 1,460 hours. Every one of the seven sits inside its own range above, so you can move any line.
  • The full span is 1,120 hours at every minimum to 1,980 at every maximum, landing in 18 to 26 weeks as a squad. Outside it: quality assurance at 20 to 25 percent of build, environments and deployment at 80 to 160 hours, security review and penetration testing at 60 to 120, NIS2 incident reporting at 100 to 200, and Common Information Model mapping at 80 to 160 per counterparty.

Delivery

How we deliver energy software development

Five phases, each named by the artifact it produces.

  1. Phase 01

    Meter data decision record

    Which series is authoritative, what provenance every read carries, and how a restatement is represented. Every later argument resolves here.

  2. Phase 02

    Estimation rule book

    Every validation tolerance and estimation method named, with how a later actual replaces it. The document a disputed bill is defended from.

  3. Phase 03

    Operations and evidence pack

    Runbooks, exception procedures and the control documentation your auditor asks for, written during the build.

  4. Phase 04

    Settlement timeline map

    Each run, each reconciliation and each window in which a closed period can still move, agreed with whoever owns your market obligations.

  5. Phase 05

    Read replay test pack

    A full past year replayed interval by interval and compared period by period, with both clock change days tested explicitly.

Frequently Asked Questions

What is energy software?

Energy software is the systems that measure, move and account for energy. On the commercial side: meter data collection, validation and estimation, interval storage, settlement and billing. On the operational side: SCADA, distribution management and asset monitoring. The halves hold different data.

What are the top energy software companies?

We do not publish a ranking, and one written by a vendor that places itself first is marketing rather than evidence. Three questions sort a shortlist faster: can they talk to your head-end and SCADA estate, can they name the metering data model, and will they put exclusions in writing.

What is the difference between a head-end system and a meter data management platform?

The head-end talks to meters and knows nothing about tariffs. Meter data management holds the validated series, each read with its source, quality flag and estimation method, and does not rate it. Billing rates and invoices and usually cannot hold interval history at rollout volume. Buying one does not give you the others.

Do you work with SCADA systems?

At the boundary, not inside the control loop. We integrate with SCADA, advanced distribution management and historian exports so operational and metering data can be reconciled, and we do not write protection or control logic. Where that boundary sits is an IEC 62443 question, and part 1-1 was read at webstore.iec.ch on 17 November 2026.

What are DLMS, COSEM and OBIS codes?

DLMS and COSEM are the metering data exchange suite published as IEC 62056. Part 6-1, read at webstore.iec.ch on 17 November 2026, specifies OBIS, the object identification system that maps common metering data items to identification codes. The OBIS code tells an export register from an import one.

Does NERC CIP apply to our software?

It depends on whether the system is in scope for the Bulk Electric System, which is a scoping answer we settle before design. A billing platform with no path into an in scope control system is a different conversation from one integrating with a control centre. The CIP list at nerc.com, read 17 November 2026, carried 29 standards from CIP-002 to CIP-015.

How long does a metering and billing build take?

The worked example on this page is 1,460 hours across seven modules, landing in 18 to 26 weeks as a squad, and the module ranges sum to 1,120 hours at every minimum and 1,980 at every maximum. Rollout and settlement programme dates move that, and both belong to somebody else's calendar.

What happens next

Three steps, each with a shape attached, so booking a call is a known quantity.

  1. A 30 minute technical call

    Bring what your system stores against a single read, and one bill you had to restate. Those two answers size the project.

  2. The provenance question

    We establish whether your reads carry source and quality, and what it costs you when they do not.

  3. A scoped phase one

    Module by module against the hour ranges on this page, with anything excluded named as excluded. The document is yours either way.

Start with what a read carries

Bring one read as your system stores it and one bill you had to restate. Thirty minutes usually settles whether this is a fit.

Our Success Stories

Real feedback from the people we've proudly partnered with.

Brooklyn Foster profile

Brooklyn Foster

Sales Director |Cintas

United States

GoodFirms
"

Zyneto Global Technologies provided excellent project management and technical expertise throughout the engagement. The team was responsive, collaborative, and adaptive, ensuring the project met our expectations and set a strong foundation for future growth.

"
Verified Review
Rating: 5 out of 5
Krystian Chlebek profile

Krystian Chlebek

Founder & CEO |Moneteo

TechBehemoths
"

We engaged Zyneto to design and develop a custom web platform for Moneteo, aimed at improving project management, data tracking, and collaboration across internal teams and external partners. Their work included full-stack web development, custom modules for workflow automation, API integration, and comprehensive testing.

"
Verified Review
Rating: 5 out of 5
Kevin Scott profile

Kevin Scott

CEO |E-Commerce Platform

Clutch
"

Overall, their responsiveness and timely deliveries contributed positively to the project's success. The client achieved better data management and quality. The service provider delivered the project on time and ensured prompt responsiveness throughout the engagement. Their innovative approach was outstanding.

"
Verified Review
Rating: 5 out of 5

Explore further

Go deeper

Build the system

Adjacent capabilities

Other sectors

Worth reading next

WhatsApp
Email
Book a Meeting