“AV over IP” describes an approach to moving audiovisual signals across networks. It does not, by itself, establish that two products will exchange the required media, respond to the same controller or recover predictably after a restart.
A current development gives buyers a more specific reference point. The IPMX technical library lists version 1.1 of its Product Qualification and Certification Requirements dated 30 August 2026. The document defines the programme’s conformance and certification framework. Buyers should consult the applicable requirements and product evidence rather than treating any general interoperability claim as sufficient.
The practical lesson is to separate the layers of a working system.
Discovery is not connection management. AMWA’s NMOS IS-04 specification enables applications to discover network resources. IS-05 addresses connection management between media nodes. AMWA notes that ST 2110 does not specify that connection-management function. A procurement document should identify the required control capabilities, not simply a media-transport standard.
Translate the use case into a compatibility matrix. Record required resolutions, frame rates, compression, audio formats, latency expectations and any content-protection requirements. Add controller and firmware versions. Ask suppliers to identify supported combinations and limitations explicitly, including the scope of any certification.
Treat the network as part of the AV design. Establish capacity, switching behaviour, addressing, timing requirements where applicable, security boundaries and monitoring responsibilities. AV and IT teams should agree who owns configuration changes and how faults will be investigated.
Test the intended combination. A useful acceptance test follows real operational tasks: discovering devices, routing a source, changing formats, recovering after a power cycle and restoring saved configurations. Include representative displays, controllers and network equipment. Where protected content is required, test it explicitly rather than relying on unprotected demonstration material.
Finally, maintain an accurate asset and configuration register. Record firmware, network settings, support status and tested combinations so that a later update does not silently invalidate earlier assumptions.
Open standards can support a more flexible procurement strategy. Their practical value depends on specifying the right functions, verifying the actual implementation and preserving that evidence throughout the system’s service life.
