The camera compatibility walk-around sheet
Take a clipboard before taking a catalog. The installed-camera list should say what is actually on the wall, what firmware it runs and which function the new system must perform. “IP camera” on its own is not a compatibility answer.
Use this sheet for an installer walk-around. Keep passwords, secret stream tokens and private addresses out of any publication or shared public quote.
One row per feed
| Field | Example entry | Evidence to keep privately |
|---|---|---|
| Location and view | West gate, fixed approach | Current permitted reference image |
| Model and firmware | Copy from actual device record | Device label or admin export |
| Feeds/sensors | Record each intended stream | Installer's channel map |
| Resolution and codec | Record chosen operating stream | Receiving-system compatibility answer |
| Network path | Local recorder or approved outbound route | Private topology drawing |
| Required action | Live view, search, recording, alert | Demonstration result per action |
| Ownership | Named admin role | Handover checklist |
Example entries are worksheet prompts, not product capabilities.
Read the profile with the function
ONVIF profiles define functions for conformant devices and clients, and some features are conditional M05. Check the camera model, firmware and receiving system together — codec support and support for a particular analytics event answer different questions M05.
Ask the vendor which required action is supported on that exact combination. A live picture that works is evidence for the view path; it does not, by itself, establish the planned search, alert or archive workflow.
Use each supplier's own boundary
For a Spot AI proposal, record whether the existing IP devices meet its documented ONVIF compatibility requirement V01. A Lumana proposal should name the standard streaming protocol used by each intended IP feed V06. If Eagle Eye is being quoted, have the installer mark each model against the vendor's supported-device list, which covers analog equipment as well as ONVIF IP models V11. Save those answers beside the inventory rather than leaving “compatible” as an unsupported tick.
Verkada Command Connector supports compatible third-party views and people/vehicle searches, while license-plate-of-interest alerts are unavailable on Connector channels V09. This is why the worksheet needs a required-action column. “Works with our platform” leaves too much unstated.
Ask for a small demonstration before the full order
Pick a representative difficult camera, not just the newest indoor model, and use the chosen stream settings. Demonstrate the required view, retained footage and alert route wherever those functions are in scope. Record failures and unresolved functions as well as successes.
Keep the result specific: model, firmware, settings, receiving product and test date. If the installer later swaps in an encoder or stream, update the row and repeat the affected check. Another technician should be able to reproduce the answer without phoning the original salesperson.
Leave the building with an owner
Each row needs an admin role and a person responsible for unresolved compatibility. Keep shared credentials out of the general handover sheet; use the organization's approved account process and private storage for access details.
Bring the completed inventory to the quote comparison. Counting feeds before pricing makes it less likely that an extra sensor turns into an unexpected license after installation.
FAQ
Does an ONVIF label guarantee every function?
No. Profiles specify defined functions, including conditional ones; confirm both sides and the intended action M05.
Can we skip testing a camera that looks identical?
Record model and firmware rather than judging the housing. Grouping equivalent devices can be a reasonable project choice, but write down the basis and test any changed configuration.
Fact traceability
Source-register IDs used on this page: M05, V01, V06, V09, V11. Direct primary links sit beside the relevant claims. Calculations and selection judgments are editorial examples, not measured product results.