What to take into your next decision
- Check each required function on the installed model and firmware.
- Test the event from the site through to the person receiving the handoff.
- Keep failures and exclusions visible until an accountable person closes them.
Write the acceptance test before connecting the site
Begin with the activity the client needs reviewed: a person entering a closed yard, an alarm at a rear door, or a scheduled check of a loading area. Name the view, coverage window, authorized response and record needed for that activity.
For each test, record the expected result, actual result, supporting evidence, reviewer and date. Use pass, fail, not tested or not applicable. An untested function should remain untested in the record; do not turn it into a pass because another function worked.
| Function | What to establish | Evidence to retain |
|---|---|---|
| Live view | The operator can see the required activity in relevant lighting and site conditions. | Camera identifier, view, test conditions and result. |
| Alarm or analytic event | The intended event reaches the monitoring workflow with the correct site and camera context. | Event reference and linked camera mapping. |
| Audio, if included | The authorized speaker can be selected and the message is intelligible at the intended location. | Device, test location and observer's result. |
| Event record | The partner receives the fields and media access needed for follow-up. | Test record and recipient confirmation. |
Check compatibility at the function level
Record the camera, recorder or VMS make, exact model, firmware or software version, connection method and required license. Separate live video, event delivery, playback, audio, PTZ and device-health notifications. A working video stream does not prove that the other functions work through the same integration.
ONVIF ties conformance to a specific product firmware or software version. Its Profile T includes mandatory and conditional features; the profile name alone is not a promise that every device and client provides every function. Check the official product entry and the monitoring platform's supported-feature documentation, then test the installed combination.
For a proposed 1Degree account, bring that equipment inventory to the technical review. This checklist is not a list of platforms or devices approved by 1Degree.
Reference: ONVIF conformance and firmware versions · ONVIF Profile T feature scope
Test the connection under the conditions you are selling
Record the stream settings, concurrent streams, site upload capacity and any competing traffic. Repeat the view check in the monitoring window, including low light or a busy operating period when relevant. A speed test at an empty site is a different test from usable video during normal activity.
Axis documents that configuration, image complexity, lighting, client load and network conditions affect video performance. Its latency guidance distinguishes camera processing, network transport and the receiving client. Keep video delay separate from operator handling time when evaluating an event.
Do not apply a universal bandwidth-per-camera promise. Use the installed system's settings and measured conditions, and record who owns network troubleshooting.
Reference: Axis network troubleshooting guidance · Axis: latency in live network video
Separate a site outage from a monitoring-center outage
A lost camera, local power failure or failed site uplink removes a different part of the service than a monitoring-platform interruption. Ask how each condition is detected, who is notified, what work remains possible and what evidence shows restoration.
Schedule any failure test with the people responsible for the installation. Keep tests controlled and clearly marked. Do not trigger an unannounced police, guard or emergency response to prove that a workflow works.
At the client site
Name the owner for cameras, power, network and local access. Document the notification route for an unavailable view.
In the monitoring operation
Request the provider's continuity process, incident communication route and recovery evidence. A claim of redundancy needs an explanation of what it covers.
At the handoff
Test an unavailable primary contact and the next authorized contact. Record what happens when neither answers.
Close the account record before activation
The handover should identify monitoring hours and time zone, holiday exceptions, authorized visitors, temporary closures, escalation contacts, audio permissions, report recipients and excluded areas. Name who can change those instructions and how the current version reaches operators.
Keep passwords, access tokens and sensitive site plans out of public contact forms and this downloadable worksheet. Exchange access information through the approved secure process for the account.
Finish with an acceptance record: tested functions, unresolved issues, responsible owners and the activation decision. Recheck affected functions after firmware, camera position, network, site-boundary or response-plan changes.
Questions partners ask
Can an existing camera system be used?
Possibly. Evaluate the exact installed models, versions, access method and required functions, then test them through the proposed monitoring workflow. Do not decide from the camera brand alone.
Does an ONVIF label prove monitoring compatibility?
No. Check the product's registered version and supported profile features, the receiving platform's integration support, and the functions required for the account.
What should stop activation?
An unresolved failure in a required function, unclear response authority, missing usable contacts or unapproved coverage instructions should be addressed before that part of the service is represented as active.
