Why interop across wired technologies matters more than ever

A member utility recently asked us to help unblock a substation retrofit. The plant was mixed: fiber to the main buildings, twisted pair to older control cabinets, powerline to a handful of outlying enclosures that nobody wanted to re-trench. The control vendor shipped Ethernet. The remote-monitoring vendor shipped G.hn over powerline. The cybersecurity baseline required end-to-end identity and telemetry. Three separate management planes. Two working certifications. Zero reference architectures that covered the whole job.

The technology to solve this has existed for years. The integration has not.

The shape of the problem

Most discussions of interoperability frame it as a technology question: “does A talk to B?” That framing is misleading. For every operator we work with, the real interoperability question is:

Can I deploy, manage, secure, and certify a network that crosses three or four wired technologies — and hand it to an operations team that is not specialized in any one of them?

Answering that question requires more than a protocol bridge. It requires:

• A management surface that speaks to every media in the plant without forcing a per-technology operations team.
• A security baseline that holds end-to-end, not just within each technology island.
• A telemetry model that AI-assisted operations can actually consume without a custom integration per vendor.
• Conformance evidence that survives audit — not a demo video from a trade show.
• Training and certification that produces engineers who are fluent across media, not specialized in one.

Everything else — the protocol bridges, the PHY abstractions, the management primitives — exists or is close to existing. What has been missing is a body that is structurally willing to work on the integration problem across technologies without threatening the technology alliances that own the constituent pieces.

What “complementary, not competitive” actually means

The foundation’s position is that we complement single-technology alliances rather than competing with them.

That is not a diplomatic formulation. It is an engineering one. Specs for G.hn, MoCA, Ethernet, and PON are produced by bodies with deep expertise in their respective technologies, and we have no intention of re-litigating that work. What we do is one layer up: the integration code, the cross-technology test harness, the unified management surface, the CRA-aligned security baseline.

Concretely, our working groups pick up where the single-technology alliances leave off:

• We consume certified PHYs and MAC layers as black boxes.
• We publish reference integrations that combine them.
• We publish cross-media conformance tests that validate the combination.
• We publish reference operations tooling — AIOps, telemetry schemas, incident runbooks — that treat the plant as one network.

The substation retrofit is now on track, using the first draft of our utility reference architecture. The plant operators did not need to become G.hn experts, powerline experts, or PON experts. They needed a validated integration, an auditable security baseline, and documented operations procedures.

Where cross-media interop will matter most in 2026

Three deployment contexts are driving urgency.

Smart-building retrofit. The commercial real-estate stock in every major market is aging, wired heterogeneously, and under pressure to add connectivity-dependent services. Trenching is expensive and often impossible. G.hn over existing copper, combined with targeted fiber and Ethernet, is the only economically viable path. Operators need reference designs and security baselines they can trust.

Utility substations and distribution automation. Grid resilience requirements, combined with regulatory cybersecurity obligations in both the EU and the US, are forcing utilities to modernize communications across plants that were built over forty years. No utility is going to rip and replace. The only path is mixed-media integration with a unified operations layer.

Industrial brownfield. Manufacturing and logistics sites rarely have the luxury of a greenfield network rebuild. Deterministic, secure edge fabrics need to run on whatever cabling is installed — often a mix of industrial Ethernet, legacy serial, and retrofitted powerline for outlying sensors. The interop problem is the whole problem.

What you can do with this today

If you are a member, three things.

1. Use the utility reference architecture when it lands (milestone is in the current roadmap). Give us deployment feedback.
2. Bring your mixed-media headaches to the project proposals list. The fastest way to influence the next reference architecture is to contribute the deployment context for it.
3. Sponsor a conformance lab session. Public cross-media conformance results shift the economics for everyone, including you.

If you are not a member yet, participate. The first year of a foundation is the year in which its working groups set their habits — a good time to show up.

— Technical Steering Committee