The Software Line on the BOM: A Five-Year Licence Audit for UK Camera Estates

On a typical UK camera estate, the hardware line on the bill of materials is legible. Cameras, lenses, brackets, switches and recorders can be counted, compared and challenged. The software line is where the arithmetic becomes less certain. Video management software and analytics are often quoted as a single figure, but that figure may rest on a charging model that changes when the estate grows, when firmware is updated or when a third-party camera is added.

For trade buyers and installers, the risk is not that software costs money. It is that the basis of the charge is not pinned down at quotation stage, so the five-year cost emerges after handover rather than before it.

Four meters, one estate

VMS and analytics licensing is usually charged on one or more of four bases: per camera, per channel, per concurrent user and per analytic stream. Each measures something different, and the differences matter.

A per-camera licence is tied to the device. It may be perpetual, in which case the entitlement sits with the camera for its service life, or subscription, in which case it is tied to an account and a renewal date. A per-channel licence is not always the same as per camera. Multi-sensor units, video encoders and virtual channels can consume more than one channel per physical device, or fewer if the VMS treats a multi-sensor unit as a single logical camera.

Concurrent-user licensing controls how many operators can be logged in at the same time, not how many named accounts exist. A control room with six desks may need six concurrent licences even if twenty staff have accounts. Analytic streams are counted per algorithm per camera. A camera running intrusion detection, loitering detection and people counting can consume three analytic streams, not one.

Where the licence lives: edge or server

Edge licensing places the entitlement on the camera or device. The analytic or VMS function runs at the edge, and the licence is typically tied to that hardware. This can simplify deployment on small sites and reduce server load, but it can make replacement and transfer less flexible. If a camera fails and is replaced with a different model, the edge licence may not move with it.

Server licensing concentrates entitlements in the VMS or analytics server. It often uses a channel count for the VMS and a separate analytics engine licence for processing. This can be more flexible for centralised monitoring and multi-site estates, but it introduces server tiers, failover considerations and a second place where licence counts can drift. A server licence that covers 50 channels may be adequate at handover and inadequate six months later when the estate reaches 60.

A worked example: sixty cameras, five years

Take a UK site with 60 fixed cameras. Twenty of those cameras need two analytics each, so 40 analytic streams are required. The control room has six concurrent operators. For illustration, assume a perpetual VMS licence at £60 per camera, analytics at £100 per stream, a server tier uplift of £1,200 because the estate exceeds 50 channels, and client licences at £150 per concurrent user.

The capital software total is: VMS at 60 × £60 = £3,600; analytics at 40 × £100 = £4,000; server uplift £1,200; clients at 6 × £150 = £900. Total capital software cost: £9,700. Year-one support at 18% of capital adds £1,746. Over five years, if support is held at 18% of the original capital figure, the software cost is £9,700 plus five years of £1,746, or £18,430. That is before any change to the estate.

Now introduce change. A firmware update reclassifies 12 cameras as enterprise-class because they run a new codec or a higher frame rate. The VMS vendor applies an enterprise licence uplift of £45 per camera, adding £540. Two additional analytics are enabled on ten cameras, adding 20 streams at £100, or £2,000. A seventh concurrent operator is added for seasonal cover, adding £150. The five-year figure moves to roughly £21,120 before support on the uplift. The exact numbers are illustrative, but the pattern is not: a £9,700 capital line can become a five-figure operational line without a single new camera being installed.

Firmware and the reclassification trap

Licence classification is increasingly software-defined. A camera model number may not determine its licence tier; the firmware, codec, resolution or analytics profile may. A camera that was quoted at a standard tier can be reclassified after a firmware upgrade because it now supports a feature the vendor treats as enterprise. In some cases the reclassification is automatic at the next licence audit; in others it requires a manual order. Either way, the buyer discovers the cost after the change, not at quotation stage.

The practical defence is to ask for the licence classification rules in writing. Which firmware versions, codecs or features move a camera between tiers? Is the reclassification retrospective? Does support cover the uplift? Can the estate refuse the firmware update and keep the original tier, and if so, what functionality is lost?

Third-party cameras and the compatibility tax

Not all VMS licences are camera-agnostic. ONVIF conformance covers basic streaming and discovery, but it does not guarantee analytics, metadata, edge recording or two-way audio will work without additional licensing. A third-party camera may connect to the VMS but consume a higher licence tier, or require a connector licence. In some estates the compatibility tax is modest; in others it is the difference between a standard channel licence and an enterprise channel licence across dozens of devices.

For UK trade buyers, the question is not simply whether a camera is supported. It is which licence tier it consumes, which features are available at that tier and whether the vendor can change the tier in a future release.

Questions to pin down at quotation stage

• Is the licence perpetual or subscription, and what happens at renewal?
• Is the count per camera, per channel, per sensor or per analytic stream?
• Which analytics are included and which are chargeable per stream?
• Are client licences concurrent or named, and how many are included?
• What is the support percentage, and does it apply to list price or discounted price?
• How are firmware upgrades classified, and can a camera move tier without a new order?
• Which third-party camera models are supported at which licence tier?
• Can licences be transferred between devices, sites or replacement cameras?
• What is the cost of failover, redundancy or a second server?
• Is there a minimum term, exit fee or data-export charge?

Keeping the line honest

At handover, the software schedule should be as detailed as the camera schedule. It should list the licence basis, the count, the tier, the term and the support arrangement for each line. It should also state the assumptions: the number of analytic streams, the number of concurrent users, the server tier and the third-party compatibility position. If those assumptions are not written down, they cannot be tested when the estate changes.

For UK trade buyers, the discipline is to treat the software line as a living document rather than a closing figure. The camera estate will change. The question is whether the licence model was understood before the first purchase order, or after the first firmware update.