// UTILITIES & NETWORK OPERATORS

OS data for water, power, gas and telecoms networks that have to sit on the real world.

Network records only earn their keep when pipes, cables and joints join to the same buildings, roads and watercourses the rest of Britain uses. We license MasterMap, the Highways and Water networks, AddressBase and terrain for operators that plan, notice, survey and maintain infrastructure across Great Britain.

  • Join plant to TOIDs, UPRNs and the Highways Network
  • Water Network and terrain for gravity, flood and catchment work
  • Street-works noticing against an authoritative road network

// WHO THIS IS FOR

Operators, contractors and regulated asset owners.

The licence question is usually the same: can the field team, the noticing team and the GIS warehouse all point at one GB basemap without each buying a different cut.

Network operators

Water, power, gas and telecoms licensees.

You already hold some OS data, often through a legacy reseller or an internal GIS contract. Typical asks are a cleaner Highways join for street works, AddressBase for premise-level customers, or Water Network and terrain for drainage and flood interaction.

  • MasterMap topography as the as-laid reference
  • Highways Network for noticing, TM and permit schemes
  • AddressBase for customer premises and MPANs / SPIDs context
  • Regional or national coverage with contractor reuse scoped in
Delivery partners

Tier-1 contractors and survey firms working on the network.

Contractor access is where licences usually break. We can scope a partner cut that lets your delivery chain use the same basemap in the field without each subcontractor scraping a public map.

  • Field survey basemaps with British National Grid coordinates
  • Shared regional clips rather than per-gang paper plots
  • Imagery for desk validation before a confined-space visit
  • Clear contractor terms so the operator stays inside the licence

// USE CASES

Utility workloads that need licensed OS data.

These are network problems, not planning-map problems. The datasets below are the ones operators actually put into GIS, work-management and noticing systems.

As-laid and as-found records

Snap buried and overhead plant to MasterMap buildings, fences and land parcels so the next scheme does not start from a traced PDF.

Street works and permitting

NRSWA / road-works noticing against the MasterMap Highways Network rather than a centreline that disagrees with the highway authority.

Customer and premise matching

AddressBase Plus or Premium to hang SPIDs, MPANs, MPRNs and service points on a UPRN instead of a free-text address.

Drainage, flood and gravity models

MasterMap Water Network plus Terrain 5 or 1m for catchment, invert context and flood interaction around above-ground assets.

Wayleaves and land rights

Parcel and building geometry for easements, wayleaves and land-interest plans that have to match what the landowner sees on the ground.

Outage and incident location

UPRN and Highways context for control rooms that need to tell a customer, a tanker or a jointer where the fault actually is.

// HOW IT'S DELIVERED

Delivery that fits a regulated GIS stack.

1. Files into the warehouse

GeoPackage or GML regional/national cuts on the refresh cadence you already run. The usual first step for an established utility GIS team.

Best for: internal ESRI / Smallworld / GE Smallworld / QGIS estates.

2. Hosted API for apps and contractors

Vector tiles or feature APIs for work-management, contractor tablets and customer-outage maps without opening the warehouse to every supplier.

Best for: field apps and delivery partners.

3. Custom network build

Joined Highways + AddressBase + plant extracts, change-only updates, or a hosted viewer for a specific operational area.

Best for: a defined programme with a named AOI.

// LICENSING, EXPLAINED

Network licences, contractor reuse and derived products.

Operator licence

Coverage is usually regional or national, not a single site. We scope seats, environments and disaster-recovery copies so the GIS warehouse, test and training stacks are all inside the agreement.

Contractors and derived data

If a tier-1 contractor or a derived flood model needs to hold the data, we write that into the partner terms up front. That is cheaper than discovering an unlicensed copy on a survey laptop at audit.

// FAQ

Questions from utility GIS and asset-data teams.

We already buy OS data through another reseller. Why talk to you?

Most enquiries are about a cleaner Highways or AddressBase join, contractor reuse, or a hosted tile API the current contract does not include. We will say so if the existing supplier already covers the use.

Can contractors use the same cut in the field?

Yes, if we scope contractor access in the licence. We will not leave that as an informal “they have a login”.

Do water companies need the Water Network if they already model in InfoWorks?

Often yes, as the OS hydrology skeleton and naming, not as a replacement for your hydraulic model. It is the join layer to MasterMap and flood context.

Is AddressBase Premium required?

Premium is for lifecycle and historic UPRNs. Plus is usually enough for premise matching and non-postal assets. We will not upsell Premium unless the system of record needs it.

Can you clip to a DNO or WASP operating area?

Yes. Bespoke AOIs are normal for utilities. Send a polygon or a licence-area code and we will quote a regional cut.

How do updates land in our warehouse?

Full national or regional refresh on the OS cadence, or change-only where the subscription supports it. We match the format your ETL already consumes.

Official Ordnance Survey Licensed Partner

// REQUEST A QUOTE

Tell us which network and which join is broken.

Share the operator, the operating area, and whether the immediate need is Highways noticing, AddressBase matching, Water Network or a field basemap. Indicative pricing comes back under NDA within one UK working day.

  • Reply within one UK working day
  • Senior partner team - no SDR gauntlet
  • Indicative pricing under NDA