Procure sensor networks using five-year whole-life cost

A low-priced sensor can become the expensive choice over five years when installation needs several appointments, batteries fail early or every incident triggers a long journey. Before market engagement, a municipality should calculate two values: the whole-life cost of the working sensor network and the cost per usable monitoring point over one common period. Unit price remains an input, not the result.

The model needs fixed quantities, site classes, internal labour rates and three scenarios for uncertain events. Every bidder completes the same price and quantity schedule. The procurement team checks evidence for service life, maintenance, software support and retirement. It can then compare ownership, rental and managed service across one service boundary without pretending that the future has one precise cost.

Define the working monitoring point first

A working monitoring point delivers a usable value at the agreed interval and includes the device, installation, power, connectivity, data handover, monitoring, maintenance and controlled retirement. This unit stops one bid pricing hardware alone while another includes installation and operations.

A municipal sensor network's five-year whole-life cost is every attributable expense required to establish the agreed number of usable monitoring points, operate them securely for five years, restore them after faults and retire them in a controlled way. The municipality records one-off, annual and event-driven costs separately.

This follows established life-cycle costing. Germany's Federal Environment Agency guidance describes a comparison of all relevant costs, including installation, use, maintenance and end of life. Section 59 of the German Public Procurement Ordinance permits life-cycle cost evaluation and requires the contracting authority to state its calculation method and the bidder information it needs in the procurement documents. The responsible procurement office should confirm the legal treatment for its procedure.

Seven cost blocks make bids comparable

The workbook separates costs by cause. Each row carries a quantity, unit, price, due date, responsible party and required evidence.

Cost block	Typical items	Useful evidence
Planning and setup	radio and site survey, privacy and security work, configuration, integration, training	scope, staff days, acceptance criteria
Hardware and installation	sensor, enclosure, bracket, gateway, power, access equipment, traffic management	bill of materials, site class, installation price
Recurring service	connectivity, network server, platform, hosting, support, licences	annual price and scaling tiers
Planned maintenance	cleaning, calibration, inspection, battery, firmware care	interval, labour time, material price
Incident and replacement	diagnosis, travel, access, repair, spare device, recommissioning	response model, fixed fees, replacement rate
Internal work	service department, IT, procurement, security, data care, contract management	role, hours per event, internal labour rate
End of use	removal, data export, deletion, return, recycling, site restoration	retirement plan, price, responsibility

The list should reflect the service. A water-level sensor at a hazard site needs different cover and backup routes from an indoor climate sensor. Alternatives become comparable when each model uses the same service, term and site distribution. The UK's 2026 whole-life cost guidance for medical technology addresses another sector, but its method transfers well: compare deliverables over the same period and ask suppliers for service life, implementation, operating, post-warranty service and disposal costs.

Site classes replace the average sensor

A fleet average hides the costliest conditions. Before tendering, the service department groups planned sites such as open access, indoor room, roof, basement, chamber or street. Each class receives assumptions for installation time, access, radio testing, power, maintenance travel and traffic management.

The municipality does not need decimals for every uncertainty. Three scenarios are enough:

1. Base case: expected component life, planned maintenance and normal incident rate.
2. Stress case: shorter battery life, more site visits and some early replacements.
3. Boundary case: the least favourable combination that operations and the approved budget must still absorb.

The team records the source and owner of every uncertain value. A supplier supports its promised figures with a data sheet, field evidence, warranty or service commitment. The service department supplies site quantities and maintenance windows. Field operations estimates travel and access time from similar work. Finance sets labour rates, inflation assumptions and any discounting method. Readers can see which figures the contract guarantees, which the municipality observed and which remain assumptions.

Field work needs an event model

Travel often disappears inside a maintenance fee. In practice, the site determines the work. One visit may require an appointment, key collection, safety briefing, journey, closure, repair, functional test and record update. The workbook captures these steps as time or an agreed fixed charge.

A practical formula is:

Five-year whole-life cost = setup + five years of recurring service + all expected maintenance and incident events + replacement purchasing + retirement. Cost per usable monitoring point divides that value by the number of points meeting the agreed quality and availability threshold.

The second measure exposes a bid that supplies many devices on paper but leaves a high share unusable in operation. A municipality should not copy a published figure as a benchmark. The Smart City Dialog case on the intermunicipal LoRaWAN infrastructure Five for South Westphalia separates concept, gateway, sensor, network-server, electricity and internal staff costs. The source calls its four-hour annual maintenance estimate per device a theoretical assumption. That caveat shows why local site classes and later actuals matter.

Allocate shared infrastructure visibly

A gateway, network server or data platform can support several applications. The first service should not carry the entire common cost, and shared infrastructure should not vanish into another department's budget. The project lead separates three levels:

• Monitoring-point costs go directly to the relevant use case.
• Shared infrastructure uses a declared allocation key, such as active devices, data volume or reserved capacity.
• Strategic base costs remain visible as central infrastructure where the municipality wants the capability regardless of one service.

Apply the key consistently across five years. When a second application joins, the model shows both its incremental cost and the revised allocation of the common base. The decision board can then see whether scale lowers cost or pushes the service into a larger tariff tier.

Compare ownership and managed service at one boundary

Under an ownership model, the municipality may carry the devices, spares, inventory, contract management and parts of operations. A managed service bundles several items into a monthly charge, but may exclude installation, difficult access, damage or data export. A fair comparison fixes the same number of usable monitoring points, site classes, service hours and retirement duties.

The schedule therefore asks who pays for batteries, firmware, fault diagnosis, travel, replacement devices, connectivity, platform operations, security updates and secure decommissioning. The local-authority Secure Connected Places Playbook calls for realistic, measurable requirements across the lifecycle. It recommends contractual timescales for patching and bug fixes and early treatment of hardware, software and data at end of life. The cost model must include each activity as a supplier service or municipal workload.

Make the workbook part of bid and contract

The procurement office should not give bidders an empty spreadsheet. It provides quantities, site classes, term, service hours, labour-cost method and scenario rules. Bidders add prices and supportable product assumptions. At least eight fields should be verifiable:

1. guaranteed and expected component life, including batteries;
2. installation and commissioning price by site class;
3. annual charges with tiers, indexation and included quantities;
4. maintenance intervals, required skills and planned duration;
5. price and response time for diagnosis, travel and replacement;
6. security-update period, process and price;
7. ownership, return, export, deletion and removal at contract end;
8. exclusions, quantity caps and excess-use prices.

Acceptance should test more than readings. The team performs a battery change, device replacement, support case and export of one monitoring-point record. After six and twelve months, contract management replaces the most important assumptions with actual figures. A material deviation triggers a budget correction, process change or agreed contractual response.

urbanOS fits shared operations across sensor types

The urbanOS Urban Data and Urban Intelligence platform is a strong fit for German municipalities or large-estate operators that need to connect existing and new sensors over LoRaWAN, NB-IoT or LTE and run several applications through shared dashboards, automations and open interfaces. The product page lists sensor-agnostic connectivity, existing networks, an API, plus GeoJSON and GPX export. This suits a five-year model where common data routes and a managed platform serve several use cases. A short, single-purpose measurement campaign may not justify a permanent platform. The municipality must still test installation conditions, device life, network coverage and its own staff effort.

Use one award rule to protect the budget

A municipality should evaluate a sensor network by life-cycle cost only when every bidder prices the same working monitoring point, site classes, contract term and scenarios. Each material assumption needs named evidence or a value set by the municipality.

Before releasing the documents, the team checks ten questions:

• Does the model separate setup, service, events, replacement and retirement?
• Does it include internal staff time?
• Does it represent difficult sites?
• Are common and use-case costs visible?
• Does it compare ownership and service at the same boundary?
• Can readers distinguish promised, observed and assumed values?
• Does a stress case show the required budget reserve?
• Are security updates and post-warranty support priced?
• Can contract management update the model with actuals after six and twelve months?
• Do the procurement documents explain the full calculation method?

The lowest sensor price answers none of these questions. A shared workbook shows which service the municipality can fund and operate for five years.