Home›Journal›Interoperability you can look up
STANDARDS · 4 September 2026 · 5 min read

Interoperability you can look up.

Every manufacturer's literature says interoperable. Almost none of it says who tested that, against what, or where you can read the result — which is the only version of the word that survives a commissioning week.

JOURNAL / 014
TESTED, PUBLISHED, COUNTABLEUNCOMPRESSED VIDEOPASSUNCOMPRESSED AUDIO (AES67)PASSJPEG XS PROFILESPASSNMOS DISCOVERY & CONNECTIONPASSHKEPPASSPEPPASS62CERTIFIED PRODUCTSPUBLIC REGISTERA CLAIM YOU CAN LOOK UP IS A DIFFERENT KIND OF CLAIM
Published requirements, independent testing, a register anyone can read.

On 1 September the Alliance for IP Media Solutions announced that fourteen more products, from eight manufacturers, had passed IPMX certification. They were tested at the European Broadcasting Union's headquarters in Geneva across the last week of August, alongside an earlier round in January that certified forty-eight products from ten manufacturers. The running total is sixty-two at the time of writing.

The number is not the interesting part. The mechanism is.

What is actually being certified

IPMX is an open suite of specifications for professional audio-visual content over IP, assembled from standards that already existed rather than invented alongside them: SMPTE ST 2110 for media transport, AES67 for audio, AMWA NMOS for discovery and connection management, and the Video Services Forum's TR-10 specifications to bind them into something a manufacturer can build against. It is developed through AIMS with the Joint Taskforce on Network Media — VSF, AMWA, the EBU and SMPTE — rather than by a single vendor.

Every certified product passes a common baseline — timing, NMOS discovery and connection, device behaviour — and at least one profile: uncompressed video, PCM audio or JPEG XS; capabilities such as HDCP key exchange and privacy encryption are tested and listed separately. The EBU tests products against requirements AIMS publishes in advance, and the results go into a register at registry.ipmx.io that anyone can read without asking a salesperson.

Why a register beats an adjective

Consider what an integrator normally has to work with. A datasheet says a device is interoperable. A second datasheet, from a different manufacturer, says the same. Both are sincere. Neither has been tested against the other, and the first time anyone finds out is on site, with a room booked and a client watching a black screen.

A published requirement plus an independent test plus a public result changes the conversation from persuasion to verification. It also changes what a specifier can write into a tender: not shall be interoperable, which cannot be enforced, but shall appear in the current certification register for the named profile, which can.

The habit, not the standard

The transferable lesson is not that every project should be IPMX. Most rooms will never need ST 2110 lineage, and plenty of excellent installations run on transports that have no register at all. The lesson is the question: who verified this, and where can I read it?

It is a question with an answer more often than integrators assume. Dante devices have published channel counts and a device list. HDBaseT products have a certification programme. HDCP has a licensing position that a manufacturer either holds or does not. Each of those is a fact somebody can look up, and each is more useful in a tender than the sentence it replaces.

Where we stand, plainly

TELECIS's current networked range is JPEG2000 over one-gigabit infrastructure, with SDVoE over ten gigabit announced. We are not in the IPMX register, and this note is not an announcement that we are joining it. We are writing about it because the mechanism is the one we would want applied to us — the same principle that puts a specification table rather than an adjective on every product page, and that states compliance per model rather than as a badge on the brand.

Ask us the same question you would ask anyone: who tested it, against what, and where is that written down. A manufacturer that finds the question awkward has told you something.

Editor's note, October 2026. Corrected: the description of what IPMX certification covers, who publishes the requirements, and the register's address; the date of the AIMS announcement (1 September, its dateline, not 2 September); and the running total, now given as at the time of writing, since the register has grown. The sources this piece relies on are listed below. For what a listing leaves to the buyer, see What IPMX certification leaves to the buyer.

REF
Referenced in this article

Specified as a system.

Specifying?

Send the room.

We return the architecture, the bill of materials, and the route to supply.