Why interoperability has moved to the centre
Interoperability has long been presented as an unglamorous technical objective: make systems exchange data, interpret it consistently and support predictable operations across organisational boundaries. That remains true, but the policy meaning of interoperability has widened. Governments increasingly treat standards and interfaces not merely as engineering choices, but as levers for market structure, cyber resilience, public-sector efficiency and strategic autonomy.
The shift is visible across multiple domains. Competition authorities now examine whether interoperability barriers entrench incumbency. Cyber agencies urge secure-by-design architectures that depend on common protocols, shared vocabularies and machine-readable security information. Public procurement frameworks increasingly favour open standards to reduce lock-in and improve portability. Meanwhile, digital identity, health data exchange, industrial internet systems and energy networks all rely on governance arrangements that determine who can connect, on what terms and with what assurances.
Interoperability is no longer a technical afterthought; it is becoming a primary way states shape digital markets without directly choosing winners.
This matters because standards can quietly determine the balance of power in a market. A proprietary interface can make an ecosystem sticky. A broadly adopted open specification can expand participation, lower switching costs and stimulate follow-on innovation. Yet openness alone is not enough. In safety-critical or security-sensitive settings, interoperability must be paired with testing, certification, version control and dispute resolution. The strategic contest is therefore not simply open versus closed, but governed versus unmanaged interoperability.
The economic case for common standards
The classic economic argument for standards is straightforward: they reduce transaction costs. If data formats, messaging protocols and interface requirements are commonly understood, organisations spend less time building one-off connectors and reconciling inconsistent records. For firms, this can lower integration costs and expand addressable markets. For buyers, it can increase substitutability and improve bargaining power. For the wider economy, it can support network effects without handing excessive control to a single provider.
International institutions have for years linked standards to productivity and trade. The OECD has argued that digital interoperability underpins more efficient public services and cross-border commerce. The World Trade Organization has long recognised standards as important features of trade facilitation, even while warning that poorly designed technical barriers can fragment markets. The less visible point is that interoperability also affects the diffusion of innovation. New entrants can compete more easily if they can plug into established workflows rather than rebuilding entire stacks from scratch.
There is, however, a distributional question. Standards create winners as well as efficiencies. Organisations with greater resources often participate more actively in standard-setting and can influence specifications in ways that reflect their installed base. Small firms and public-interest groups may be underrepresented. This is one reason why the governance of standards bodies, implementation forums and procurement rulebooks has become more consequential. Interoperability is an economic public good, but its design is not politically neutral.
Open standards, but not open season
Policy documents frequently call for open standards, yet the term is often used imprecisely. In practice, openness can refer to several different attributes: public availability of the specification, transparent governance, non-discriminatory access to implementation rights, and the ability of multiple independent parties to build conformant systems. These dimensions matter because a nominally open standard can still produce de facto concentration if testing regimes, licensing terms or reference implementations are controlled too narrowly.
Interoperability is no longer a technical afterthought; it is becoming a primary way states shape digital markets without directly choosing winners.
The European Union’s approach offers a useful lens. Its European Interoperability Framework emphasises legal, organisational, semantic and technical interoperability rather than treating the matter as purely syntactic data exchange. This broader framing recognises that systems fail to interoperate not only because interfaces differ, but because institutions define concepts differently, allocate responsibility ambiguously or lack common trust mechanisms. In other words, interoperability is as much about governance and incentives as file formats and application programming interfaces.
The practical implication is that public authorities must distinguish between standard publication and operational interoperability. Publishing a specification may improve transparency, but it does not guarantee compatibility in live settings. Real interoperability usually requires implementation guides, conformance profiles, testing tools, maintenance processes and migration plans. Without these, open standards can become open-ended documents that still produce incompatible deployments.
Publishing a standard is easy; sustaining interoperable implementation is the hard, expensive and politically charged part.
Europe’s digital rulebook is raising the stakes
Recent European legislation has elevated interoperability from administrative preference to regulatory expectation. The Interoperable Europe Act, adopted in 2024, seeks to strengthen cross-border public-sector digital cooperation across the EU by introducing mechanisms for shared assessments and interoperable solutions. The logic is not merely bureaucratic tidiness. Fragmented public systems increase compliance burdens, hamper mobility and make it harder to deliver digital public services consistently across the single market.
Alongside this, sector-specific rules are nudging institutions towards common data frameworks. The European Health Data Space aims to improve health data use and exchange under defined governance conditions. The Data Act includes provisions on access and portability intended to lower frictions around connected products and related services. NIS2 and the Cyber Resilience Act, while primarily focused on security obligations, indirectly reinforce the case for common technical baselines and better lifecycle management of connected systems.
The broader pattern is clear. European policy is moving towards an environment in which interoperability is no longer optional for organisations participating in regulated digital ecosystems. The challenge will be implementation capacity. Member states and local authorities vary sharply in technical maturity, procurement capabilities and legacy constraints. Formal rights to data portability or cross-border exchange can therefore outrun administrative reality unless backed by funding, expertise and common implementation assets.
Interoperability and cyber resilience are now intertwined
For years, some organisations treated interoperability and security as competing objectives: more connectivity meant more attack surface. That concern remains valid, but the relationship has become more nuanced. Modern cyber defence increasingly depends on interoperable telemetry, shared schemas, machine-readable vulnerability information and common approaches to identity and access management. Fragmented systems can make it harder to detect incidents, coordinate responses and patch vulnerabilities at scale.
Guidance from agencies such as the US Cybersecurity and Infrastructure Security Agency and the UK National Cyber Security Centre points towards architectures that support secure updates, asset visibility, supply-chain transparency and stronger identity controls. None of these can function efficiently in complex environments without common protocols and dependable interfaces. In industrial and operational technology environments, the challenge is greater still, because old equipment may rely on proprietary or obsolete communications methods that complicate monitoring and segmentation.
This creates a strategic tension. Pushing for interoperability too quickly can expose brittle legacy systems or normalise insecure implementations. Moving too slowly can preserve opaque silos that are difficult to defend. The sensible policy response is phased interoperability: prioritise high-value layers such as identity, logging, software bills of materials and incident reporting formats; then build outward through tested profiles and certification schemes. Secure interoperability is not maximal connectivity. It is governed, auditable and least-privilege connectivity.
The quiet importance of semantic interoperability
Publishing a standard is easy; sustaining interoperable implementation is the hard, expensive and politically charged part.
Technical standards often receive most of the attention, but semantic interoperability is where many initiatives falter. Two systems may exchange data perfectly while still misunderstanding each other. A common example is address data, where formatting differences, localisation issues and inconsistent identifiers can undermine otherwise well-designed exchanges. The same problem appears in health coding, customs information, geospatial data and digital identity attributes.
The World Wide Web Consortium and ISO have long supported models for machine-readable semantics, metadata and identifiers, yet implementation remains uneven. Public agencies, in particular, often discover that their largest obstacle is not data transmission but agreement on meaning. The European Interoperability Framework explicitly recognises this by separating semantic interoperability from technical interoperability. That distinction deserves more attention in industrial strategy and public procurement alike.
Semantic alignment is slow work because it requires institutional compromise. Agencies may use similar terms while attaching different legal consequences to them. Firms may resist common vocabularies if bespoke definitions preserve competitive advantage or reduce comparability. Yet without semantic convergence, the promise of data spaces, artificial intelligence deployment and automated compliance remains constrained. Systems can only scale trustworthy automation if they interpret key fields and events in consistent ways.
Procurement is where standards become real
Much discussion about interoperability focuses on legislation and standard-setting bodies, but procurement is where ambitions are translated into operating reality. Buyers determine whether contracts require open interfaces, machine-readable exports, documented data models, migration support and conformance testing. If tenders remain vague, suppliers have little incentive to build for substitutability or long-term portability.
The OECD has repeatedly highlighted the importance of digital government procurement in avoiding fragmentation. In practice, the strongest public buyers now specify not just deliverables but interoperability conditions: adherence to recognised standards where appropriate, publication of interface documentation, support for common identity frameworks, and evidence of secure integration practices. These requirements can be especially important in health, transport, justice and local government, where fragmented systems create large cumulative costs.
There is a cautionary point here. Procurement can strengthen interoperability, but overly prescriptive specifications can freeze technology choices or exclude smaller suppliers that lack resources to navigate complex compliance exercises. The best tenders tend to define outcomes and conformance needs clearly while allowing implementation flexibility. They also plan for lifecycle issues, including versioning, deprecation, dispute handling and exit arrangements. Too often, interoperability is included in a contract as a static requirement when it should be treated as a continuing governance function.
The decisive battleground for interoperability is often not parliament or the standards body, but the tender document and the maintenance contract.
Strategic autonomy without digital autarky
Governments increasingly speak of digital sovereignty or strategic autonomy, especially in Europe. Interoperability sits awkwardly but centrally within that agenda. On one hand, common standards and portability can reduce dependency on dominant actors by making substitution easier and enabling more diverse supplier ecosystems. On the other, excessive localisation or incompatible national rules can produce the very fragmentation that weakens resilience and raises costs.
The most credible path lies between dependency and autarky. Strategic autonomy is better understood as the capacity to choose, switch and govern than as the capacity to build every layer domestically. From that perspective, interoperability is a sovereignty enhancer because it improves reversibility and reduces captive dependence. But this only holds if standards are internationally legible and if conformance regimes are trusted beyond a single jurisdiction.
This is where global standards institutions retain importance despite mounting geopolitical tension. ISO, IEC, ITU and sector-specific bodies continue to provide venues, however imperfect, for technical alignment. Their work can lower fragmentation risks, but only if governments resist the temptation to turn every strategic concern into a unique local requirement. The world does not need frictionless uniformity in every domain; it does need enough common ground for trade, assurance and crisis coordination to function.
The decisive battleground for interoperability is often not parliament or the standards body, but the tender document and the maintenance contract.
Sector lessons from health, energy and manufacturing
Some of the clearest lessons come from sectors where interoperability has moved from aspiration to infrastructure. In health, data exchange standards have advanced unevenly across countries, but the policy direction is unmistakable: patient mobility, clinical coordination and secondary use of data all depend on agreed formats, terminology and governance. The European Health Data Space reflects this reality by linking technical exchange to legal rights and institutional safeguards.
In energy, the rise of distributed systems, smart metering and cross-border balancing makes interoperability a condition for resilience and decarbonisation. Grid operators and regulators need common data models and dependable interfaces across assets that were not designed to operate as part of a highly digital, decentralised system. In manufacturing, standards associated with industrial communication and digital product information increasingly shape whether firms can integrate suppliers, automate compliance and trace components through complex value chains.
Across these sectors, one pattern stands out: interoperability is most durable when tied to a clear operational problem. Where standards are framed as abstract modernisation, implementation tends to lag. Where they solve visible problems such as patient record exchange, incident reporting, emissions traceability or equipment maintenance, institutions are more willing to absorb migration costs and coordinate governance.
What organisations should measure now
If interoperability is becoming a policy and competitiveness issue, organisations need better metrics than simple counts of interfaces. A more useful dashboard would include the share of critical systems with documented and versioned interfaces; the proportion of data objects mapped to common vocabularies; the time and cost required to switch or add suppliers; the coverage of conformance testing; and the percentage of high-value workflows dependent on proprietary gateways or manual reconciliation.
Cyber metrics should also be integrated. Relevant measures include the proportion of assets producing machine-readable logs to a common schema, the coverage of strong identity controls across integrations, and the ability to distribute authenticated updates across heterogeneous estates. In procurement, buyers should track whether contracts include explicit portability and export obligations, not merely service-level commitments. These indicators are less headline-friendly than broad digital transformation targets, but they reveal whether interoperability is improving in ways that matter operationally.
Boards and public authorities should also pay closer attention to governance risk. Who owns interface decisions? How are schema changes approved? What is the process for deprecating a protocol? Which third parties can join an exchange environment, and under what assurance conditions? Many interoperability failures stem not from technical impossibility, but from the absence of durable decision-making structures. Metrics should therefore capture governance maturity as well as technical deployment.
The next five years
Over the next five years, interoperability is likely to become more formalised, more regulated and more contested. Formalised, because public authorities will increasingly require common specifications, testing and reporting across critical digital domains. More regulated, because data access, portability and security obligations are being embedded in law rather than left to voluntary coordination. More contested, because control over standards and interfaces shapes market entry, switching costs and geopolitical influence.
Three implications follow. First, organisations should treat interoperability as a strategic capability, not a compliance afterthought. Secondly, policy-makers should invest as much in implementation support, conformance infrastructure and maintenance as in drafting frameworks. Thirdly, standard-setting must become more inclusive and accountable if it is to command legitimacy across sectors and borders.
The broader lesson is that standards are no longer peripheral to digital power. They are part of the institutional architecture through which markets are opened or closed, systems are secured or exposed, and public authority is exercised in increasingly software-defined environments. The technical details still matter enormously. But the central question has become unmistakably political economy: who gets to define the rules by which digital systems can connect, compete and endure?
