Digital Municipal Utilities And Service Dependency Structure
Digital Municipal Utilities and Service Dependency Structures
Introduction
Digital municipal utilities are public or publicly regulated utility systems whose operation increasingly depends on digital platforms, cloud infrastructure, software, data networks, automated decision-making, sensors, digital identity systems, payment gateways, application programming interfaces (APIs), and algorithmic management.
Examples include:
- smart electricity and water metering;
- digitally managed waste collection;
- smart street lighting;
- municipal broadband;
- intelligent transport and parking systems;
- digital building-permit and land-use platforms;
- district-heating management;
- digital public-utility billing;
- IoT-enabled water and energy networks;
- municipal cloud and data platforms.
The competition-law problem arises when a municipality, state-owned utility, incumbent technology supplier, or dominant digital infrastructure provider becomes an indispensable intermediary between citizens, competing service providers and essential municipal services.
The resulting service dependency structure can produce situations where access to a utility technically remains open, but practical access depends upon one digital platform, proprietary software, data format, authentication system, payment infrastructure, cloud environment or algorithm.
Thus, the relevant competition question is no longer simply:
Who controls the pipes, wires or physical network?
It is increasingly:
Who controls the digital layer through which the physical municipal service can be accessed, supplied, monitored or administered?
1. Meaning of Digital Municipal Utilities
A traditional municipal utility generally involves a physical infrastructure network.
For example:
Water treatment → pipes → household
or
Electricity generation → distribution network → consumer
A digitally dependent utility adds a technological layer:
Physical infrastructure → sensors → communications network → cloud platform → algorithm → municipal operator → consumer
The digital layer can become economically indispensable.
Example
Suppose a city contracts with one company for smart-water management.
The company provides:
- smart meters;
- meter-data software;
- cloud storage;
- leak-detection algorithms;
- customer billing APIs;
- maintenance dashboards.
If the municipality later wants another technology provider, switching may be difficult because:
- historical data are stored in proprietary formats;
- APIs are undocumented;
- devices are technically locked to the platform;
- algorithms cannot easily be transferred;
- contracts prohibit interoperability;
- municipal staff have been trained only on the incumbent system.
The municipality therefore becomes technologically dependent even if it legally owns the water infrastructure.
2. Service Dependency Structures
A service dependency structure exists where continued access to a municipal service depends materially upon another undertaking or technological layer.
It can take several forms.
A. Infrastructure dependency
A competitor needs access to:
- electricity grids;
- water networks;
- district-heating systems;
- municipal broadband;
- charging infrastructure.
B. Software dependency
Municipal operations depend upon proprietary:
- operating systems;
- utility-management software;
- billing systems;
- SCADA systems;
- scheduling software;
- cybersecurity platforms.
C. Data dependency
A competing provider requires access to:
- meter data;
- consumption data;
- customer information;
- geospatial information;
- network-performance data.
D. Identity dependency
Access depends upon a single:
- municipal digital identity;
- authentication provider;
- digital wallet;
- API gateway.
E. Payment dependency
A municipal service can effectively become dependent upon one:
- payment gateway;
- digital wallet;
- billing intermediary;
- transaction platform.
F. Cloud dependency
A municipal utility may become dependent upon a particular cloud provider because its:
- databases;
- applications;
- analytics;
- AI models;
- cybersecurity systems
are hosted within that provider's ecosystem.
3. Competition-Law Significance
The principal competition-law concern is foreclosure.
A dominant undertaking controlling an essential digital input may use that control to disadvantage downstream competitors.
Potential conduct includes:
- refusal to provide access;
- discriminatory access;
- excessive access prices;
- tying;
- bundling;
- self-preferencing;
- interoperability restrictions;
- technical degradation;
- discriminatory APIs;
- data withholding;
- exclusive procurement;
- switching barriers;
- contractual lock-in;
- discriminatory authentication;
- algorithmic prioritisation.
This can prevent competitors from competing on the merits.
4. Essential-Facilities Dimension
The concept of essential facilities is particularly relevant.
A facility becomes competition-law sensitive where:
- access is indispensable;
- duplication is practically or economically impossible;
- refusal eliminates effective competition;
- access can feasibly be provided.
Digital municipal infrastructure can sometimes satisfy these characteristics.
For example, if every competing electricity-management provider must obtain real-time access to a municipal smart-grid API, denial of that API may have effects similar to denying access to a physical network.
The important development is therefore:
Physical essential facility → digital essential facility → hybrid essential facility.
5. Key Case Laws
1. United Brands v Commission
United Brands Company v Commission (Case 27/76)
The European Court of Justice recognised that a dominant undertaking can violate competition law where it uses its market position to impose unfair or exclusionary conditions.
Relevance
Municipal utility markets can involve strong dependency relationships. If a dominant digital utility operator controls an indispensable service input and imposes discriminatory or exclusionary conditions on dependent providers, the conduct may raise Article 102 concerns.
The case is important for understanding the broader principle that dominance entails special responsibility not to distort effective competition.
6. Commercial Solvents v Commission
Commercial Solvents Corp. v Commission (Joined Cases 6/73 and 7/73)
The Court dealt with a dominant undertaking controlling an upstream input and refusing supply to a downstream competitor.
Principle
A dominant undertaking may infringe competition law when it controls an indispensable upstream input and uses that control to eliminate competition downstream.
Digital municipal utility application
Consider:
Municipal data platform → competing utility-service providers
If the platform controls indispensable consumption or network data and refuses reasonable access to competitors while continuing its own downstream operations, the Commercial Solvents principle becomes highly relevant.
The important issue is therefore not merely ownership of the data, but whether the data infrastructure is being used to foreclose downstream competition.
7. Bronner v Mediaprint
Oscar Bronner GmbH & Co. KG v Mediaprint (Case C-7/97)
Bronner established important limitations on compulsory access under the essential-facilities doctrine.
The Court emphasised the exceptional nature of requiring a dominant undertaking to share infrastructure.
Three important considerations
The facility must generally be:
- indispensable;
- incapable of being realistically replicated;
- such that refusal eliminates effective competition.
Digital municipal utility application
A municipal digital platform should not automatically be classified as an essential facility merely because it is convenient.
For example, a competing waste-management provider cannot necessarily demand access to a municipality's proprietary software simply because access would reduce its costs.
The stronger case arises where the platform is genuinely indispensable because:
- no substitute exists;
- duplication is technically or economically impossible;
- competitors cannot operate without access.
8. IMS Health v NDC Health
IMS Health GmbH & Co. OHG v NDC Health GmbH & Co. KG (Joined Cases C-418/01 P and C-419/01 P)
The Court addressed refusal to license intellectual property in circumstances involving indispensable information structures.
Significance
IMS Health is particularly relevant to data-dependent municipal utilities.
Suppose a dominant provider controls a proprietary geographic or consumption-data architecture that competing municipal-service providers cannot practically reproduce.
The competition analysis must distinguish between:
- ordinary proprietary information;
- commercially valuable data;
- genuinely indispensable data infrastructure.
Where the latter becomes indispensable to effective competition, refusal to provide access can attract closer scrutiny.
9. Microsoft v Commission
Microsoft Corp. v Commission (Case T-201/04)
The General Court upheld important findings concerning Microsoft's refusal to provide interoperability information.
Central principle
Control over interoperability can become a competitive weapon.
Microsoft is particularly important for digital municipal utilities because modern utilities increasingly depend on interoperability between:
- sensors;
- databases;
- cloud systems;
- billing systems;
- payment platforms;
- municipal applications;
- third-party service providers.
Example
A municipality may require a smart-grid supplier to expose a standard API.
If the incumbent deliberately withholds interoperability information so that rival suppliers cannot connect their systems, the conduct may resemble the competitive problem addressed in Microsoft.
10. Slovak Telekom v Commission
Slovak Telekom a.s. v Commission (Joined Cases C-165/19 P and C-164/19 P)
The Court considered exclusionary conduct involving access to telecommunications infrastructure.
Relevance to municipal utilities
Telecommunications infrastructure often underpins:
- smart meters;
- connected streetlights;
- smart parking;
- municipal IoT;
- emergency communications;
- intelligent transport.
Therefore, digital municipal utilities can involve a layered dependency structure:
Municipality → telecom infrastructure → IoT network → utility platform → service provider
Control at any upstream layer can affect downstream competition.
The case reinforces the importance of analysing whether access restrictions make effective downstream competition impossible or materially less viable.
11. Google Shopping
Google and Alphabet – Google Shopping
The European Commission's Google Shopping decision concerned preferential treatment of Google's comparison-shopping service within its general search results.
Relevance
The case illustrates self-preferencing in digital ecosystems.
A municipal digital platform might simultaneously:
- operate the infrastructure;
- provide the platform;
- rank service providers;
- sell municipal services;
- process customer requests.
That creates a potential conflict.
For example:
Municipal service marketplace
could rank:
- the municipality's own service;
- affiliated provider;
- independent competitors.
If the platform systematically advantages its own downstream service, competition concerns can arise.
12. Google Android
Google Android (European Commission Decision, 2018)
The Android case concerned practices involving tying, distribution arrangements and restrictions affecting competition.
Digital municipal utility relevance
The case demonstrates how control over an ecosystem can create leverage across adjacent markets.
A smart-city platform might connect:
- municipal identity;
- payment;
- transport;
- parking;
- utilities;
- public information;
- digital permits.
If access to one municipal service requires adoption of several linked services supplied by the same undertaking, ecosystem leverage and tying concerns can arise.
13. Frankfurt Airport / Aéroports de Paris Analogy
Cases involving infrastructure access in regulated network industries demonstrate an important principle: ownership or operation of infrastructure can create competition consequences when competitors depend upon access.
Municipal utilities present an especially strong version of this problem because infrastructure frequently possesses:
- natural-monopoly characteristics;
- public-service obligations;
- high sunk costs;
- geographical exclusivity.
Digitalisation can extend those characteristics into software and data.
14. Digital Lock-In
One of the greatest risks is vendor lock-in.
A municipality may initially choose a technology provider competitively.
Over time, however, switching becomes increasingly expensive.
Lock-in cycle
Initial procurement
↓
Cheap integrated platform
↓
Large-scale deployment
↓
Accumulation of proprietary data
↓
Employee training
↓
API dependence
↓
Device compatibility requirements
↓
Migration costs increase
↓
Competitors become less viable
↓
Incumbent gains durable market power
This is a major competition concern because market power may arise after the procurement process, rather than at the moment of initial contract award.
15. Data Portability as a Competition Remedy
Data portability can reduce dependency.
A municipality should ideally be able to transfer:
- customer records;
- meter readings;
- network histories;
- GIS information;
- maintenance records;
- consumption information.
Effective portability requires more than merely permitting downloads.
It may require:
- machine-readable formats;
- complete historical records;
- documented APIs;
- metadata;
- interoperability standards;
- reasonable transfer times.
Otherwise, nominal portability may coexist with practical lock-in.
16. Interoperability
Interoperability is perhaps the most important structural safeguard.
A competitive digital municipal utility architecture should permit:
Provider A → common API ← Provider B
rather than:
Provider A → proprietary platform → Provider A's downstream services
Interoperability can reduce:
- switching costs;
- entry barriers;
- network effects;
- data advantages;
- ecosystem foreclosure.
It also allows municipalities to replace one component without rebuilding the entire system.
17. Network Effects
Digital municipal utilities can exhibit powerful network effects.
For example:
More consumers
↓
More data
↓
Better algorithms
↓
Better service optimisation
↓
More municipal contracts
↓
More consumers
↓
Still more data
This can produce a data-network-effect feedback loop.
A rival may therefore face difficulty entering even if it possesses superior technology.
18. Algorithmic Dependency
Algorithms increasingly determine:
- electricity demand forecasting;
- water leakage detection;
- waste collection routes;
- traffic management;
- parking enforcement;
- public transport scheduling;
- infrastructure maintenance.
If one provider controls the algorithm and the underlying data, competitors may have no practical way to reproduce the service.
This creates a new form of dependency:
Algorithmic essentiality.
The competition analysis should therefore examine not merely access to physical infrastructure but access to the computational resources necessary to operate it.
19. Cloud Concentration
Municipal utilities increasingly rely on cloud computing.
A municipality may place:
- utility databases;
- AI systems;
- customer portals;
- billing;
- cybersecurity;
- IoT management
within one cloud environment.
This can create cloud dependency.
Potential competition concerns include:
- high data-egress costs;
- proprietary APIs;
- cloud-specific software;
- technical incompatibility;
- bundled cloud services;
- preferential treatment of affiliated applications.
Thus:
Cloud infrastructure can become a digital utility bottleneck.
20. Public Procurement and Competition Law
Municipal digital utilities sit at the intersection of:
- competition law;
- public procurement law;
- public-service regulation;
- data protection;
- cybersecurity;
- digital-platform regulation.
A municipality should therefore avoid procurement specifications that unintentionally create permanent technological dependence.
For example, a tender requiring:
"compatibility only with the incumbent's proprietary platform"
may indirectly exclude competitors.
Better procurement design can require:
- open standards;
- API access;
- data portability;
- interoperability;
- exit assistance;
- source-code escrow where appropriate;
- migration rights;
- non-discriminatory technical access.
21. Abuse of Dominance
Where an undertaking possesses dominance, the following conduct may attract Article 102 TFEU or equivalent national scrutiny:
| Conduct | Possible competition concern |
|---|---|
| Refusal of digital access | Essential-facility foreclosure |
| Discriminatory API access | Exclusion |
| Self-preferencing | Downstream foreclosure |
| Data withholding | Raising rivals' costs |
| Excessive switching fees | Lock-in |
| Bundling | Leveraging dominance |
| Exclusive municipal contracts | Market foreclosure |
| Technical degradation | Interoperability foreclosure |
| Predatory introductory pricing | Competitor exclusion |
| Algorithmic discrimination | Unequal access |
22. German Competition-Law Perspective
Germany is particularly significant because the GWB contains strong provisions dealing with digital ecosystems and undertakings of paramount significance across markets.
The Federal Cartel Office's approach to major digital ecosystems demonstrates the increasing willingness to examine:
- cross-market leverage;
- ecosystem power;
- data advantages;
- access restrictions;
- intermediary dependence.
This is relevant to digital municipal utilities because a technology provider may not dominate a traditional utility market but may possess substantial power in an adjacent digital infrastructure market.
23. UK Competition-Law Perspective
In the United Kingdom, digital municipal utility dependency can engage:
- Chapter II Competition Act 1998;
- public procurement principles;
- regulated-network principles;
- digital markets regulation where applicable;
- sector-specific utility regulation.
The UK's modern competition approach increasingly recognises that market power can arise from:
- data;
- ecosystems;
- interoperability;
- network effects;
- switching costs.
Consequently, the traditional concept of a utility monopoly may need to be extended to digital infrastructure layers.
24. Structural Dependency Model
The relationship can be represented as:
Municipality
↓
Physical Utility Infrastructure
↓
Sensors / Devices
↓
Connectivity
↓
Cloud Infrastructure
↓
Data Platform
↓
AI / Algorithmic Layer
↓
Billing / Identity / Payment
↓
Citizens and Competing Service Providers
Control over any critical layer can create dependency.
The strongest competition concerns arise where one undertaking controls several consecutive layers.
25. Competition Risks
1. Foreclosure
Competitors cannot access an indispensable digital layer.
2. Vertical leveraging
An undertaking uses infrastructure dominance to enter downstream services.
3. Data advantage
The incumbent possesses datasets unavailable to rivals.
4. Switching-cost exploitation
Customers cannot realistically change providers.
5. Interoperability foreclosure
Competitors are technically prevented from connecting.
6. Algorithmic discrimination
Algorithms systematically favour affiliated providers.
7. Ecosystem concentration
Multiple municipal services become dependent on one technological ecosystem.
8. Resilience risks
A failure of one provider disrupts multiple public services simultaneously.
26. Remedies
Competition authorities and municipalities can consider several remedies.
A. Access remedies
Require non-discriminatory access to essential digital infrastructure.
B. Interoperability remedies
Require standardised interfaces and APIs.
C. Data-portability remedies
Ensure usable transfer of historical data.
D. Functional separation
Separate infrastructure operation from downstream commercial activities.
E. Non-discrimination
Require equivalent treatment of affiliated and independent providers.
F. Switching protections
Restrict excessive termination and migration charges.
G. Procurement safeguards
Prevent unnecessarily proprietary specifications.
H. Transparency
Require meaningful information concerning ranking and allocation algorithms where necessary.
I. Multi-sourcing
Avoid placing all critical municipal services with one supplier.
J. Resilience requirements
Maintain backup infrastructure and alternative suppliers.
27. Six Core Case-Law Principles
The most useful authorities can therefore be synthesised as follows:
| Case | Core principle | Digital municipal application |
|---|---|---|
| United Brands | Special responsibility of dominant firms | Preventing discriminatory utility access |
| Commercial Solvents | Upstream control can foreclose downstream competition | Control of utility data/API |
| Bronner | Strict essential-facility conditions | When digital infrastructure is genuinely indispensable |
| IMS Health | Exceptional compulsory access to indispensable information | Proprietary utility data structures |
| Microsoft | Interoperability can be competitively essential | Smart-city software/API access |
| Slovak Telekom | Infrastructure access restrictions can exclude rivals | Telecom/IoT infrastructure for municipal services |
| Google Shopping | Self-preferencing can distort downstream competition | Municipal platform ranking its own services |
| Google Android | Ecosystem leverage and tying | Integrated municipal digital ecosystems |
Conclusion
Digital municipal utilities represent a transformation from infrastructure dependency to infrastructure-plus-platform dependency.
The competition-law problem is therefore no longer limited to ownership of physical monopolies such as water pipes, electricity grids or transport infrastructure.
Market power can increasingly arise from control over:
data + APIs + cloud infrastructure + identity + software + algorithms + physical networks.
The central legal issue is whether these digital layers become indispensable gateways through which competing providers must operate.
The most important cases—Commercial Solvents, Bronner, IMS Health, Microsoft and Slovak Telekom—provide the foundations for analysing access and foreclosure, while Google Shopping and Android demonstrate how ecosystem control and self-preferencing can extend dominance into adjacent markets.
Accordingly, an effective competition framework for digital municipal utilities should focus on interoperability, data portability, non-discriminatory access, switching rights, multi-sourcing and prevention of vertical foreclosure.

comments