Contracts Finder carries a single UK notice dated 15 May 2023 titled SPS 2412 Metering, Billing and Tariff Setting, and that is the entire evidence base an engineer has to work from. So this is a spec-first reading of one procurement record, not a market scan. [S1]
For specifying engineers, the value of a notice is rarely in the headline and almost always in the scope words. Here, the three scope words are metering, billing and tariff setting, and they line up with the three deliverables a utility or large estate buyer usually separates: the physical or virtual meter and its data pipeline, the customer or cost-allocation invoice, and the regulated or contractual price structure. Treating them as one workstream is the most common procurement mistake in this category, and SPS 2412 reads as if the buyer has not yet chosen to separate them. [S1]
What the notice actually says
The record is a Contracts Finder entry for SPS 2412, published 15 May 2023, with the term meters used as a search tag. The title is Metering, Billing and Tariff Setting, which is the only descriptive text available. There is no excerpt body, so any reading has to be inferred from the three nouns in the title and the procurement taxonomy they imply. [S1]
For an engineer, the practical question is whether this is a single integrated contract or three lots bundled under one reference. The SPS prefix suggests an internal buyer coding scheme, and the absence of a value field in the evidence means the scale of the award cannot be confirmed from this record alone. [S1]
Why the three nouns matter for a specification
Metering covers the asset and its data: meter type, communications, data validation, and the interface into billing. Billing covers invoice generation, allocation rules, settlement, and dispute handling. Tariff setting covers the price schedules, banding rules, and the inputs that change when regulation or supply contracts change. Each has its own data model, its own change-control cadence, and its own audit expectation. [S1]
The reason this matters in a spec is that acceptance criteria differ. A metering deliverable is judged on accuracy class, data completeness and latency. A billing deliverable is judged on invoice correctness against an agreed allocation. A tariff deliverable is judged on traceability of every published rate back to its source rule. Bundling all three into one acceptance gate tends to hide metering defects inside billing disputes. [S1]
What an engineer should pin down before responding
First, confirm the buyer and the regulated or non-regulated status of the supply, because tariff setting duties differ sharply between licensed supply, district heating, multi-tenant estates, and campus or public-sector portfolios. Second, identify whether existing meter stock, AMR or AMI systems, and historical billing data are in scope for migration, since that drives data, integration and cutover risk. Third, establish which tariff model applies, whether it is fixed, block, time-of-use, or capacity-based, because that decides the granularity of meter data and the validation rules the spec has to mandate. [S1]
Finally, treat the audit trail as a first-class requirement. Where tariff setting is involved, the buyer will usually be asked to demonstrate that a customer was charged the correct published rate on the correct date against the correct meter reading, so the specification should name the records that must be retained, their format, and their retention period, rather than leaving this to be negotiated after award. [S1]
Primary notice: Contracts Finder.