Face recognition for Network Optix

Through the Nx Metadata SDK, which Network Optix provides for integrating third-party video analytics by exchanging metadata and events with the server. An analytics plugin runs against the Nx server and emits metadata packets, which the server stores against the camera and the timeline. This is the platform’s documented integration route rather than a side channel.

Network Optix documents both as distinct packet types that may be sent to the server at the same time. Object metadata describes detected objects — their position, type and attributes — and is what makes the timeline searchable afterwards. Event metadata describes a discrete occurrence the system should react to. Using only one of the two is the most common way an Nx integration ends up either unsearchable or unusable.

Where the integration writes object metadata to the timeline and the metadata retention covers the period, yes — that is the point of using the Metadata SDK rather than only firing alerts. An investigation becomes a query against the timeline rather than scrubbing footage. How far back a search can reach depends on the configured metadata retention, which should be specified alongside the video retention.

A Rules Engine event in Nx that fires on detected objects and can be filtered by object type and attribute, which lets a customer configure different system reactions for different detections. For a face recognition integration it is the mechanism by which a match becomes an action — a bookmark, a notification, an output trigger — without writing custom code for each rule.

No such status is claimed on this site. The page describes the use of Network Optix’s documented plugin architecture, which is a statement about how the software works rather than about a commercial or certification relationship. Where marketplace or certification status matters to a procurement, verify it with Network Optix directly.

In the Ayonix deployment, not inside Nx. Nx receives analytics metadata and events; biometric templates remain under the Ayonix deployment’s own access control, retention and audit configuration. This keeps one governance model for the biometric data rather than splitting it across two systems with different rules — which matters when someone has to demonstrate the data lifecycle.

This page does not publish a version matrix, for the same reason it appears nowhere else on this site: a compatibility claim that has not been tested against each release is a guess presented as a commitment. Network Optix documentation is the authority on which SDK interfaces exist in which release. For a specific deployment, record the product and version and the supported configuration is confirmed in writing.

The Metadata SDK plugin architecture runs plugins against the Nx server, which means the analytics load sits alongside recording and must be sized for. Where the recognition workload is heavy or the gallery is large, a design that keeps matching on separate Ayonix infrastructure and uses the plugin to carry results into Nx is usually the better arrangement. Which applies is a sizing question answered by measuring the real streams.