Full-site design previewPreview forms do not send messages
1Degree Surveillance

Cloud video analytics

Make video alerts useful to the monitoring team.

Video analytics helps identify activity for operator review. 1Degree uses AI-assisted alert handling within its monitoring service for partners serving US and Canadian client sites. The useful question is which events reach an operator, with what context, and how the account responds.

Illustration of an Asian operator reviewing person and vehicle detection in camera footage

Choose how we watch
your cameras.

Get a quote
Illustration of a fictional monitoring specialist watching several live camera feeds
Day24/7Night

Watch all day

A real person watches your live cameras, 24/7. If we see a problem, we follow your response plan.

Shared team$25per camera / month

Your cameras and other sites.

Dedicated team$35per camera / month

Only your agreed cameras.

Continuous monitoring
Illustration of an alarm at a warehouse entrance after dark
AlarmVideo check

Check alarms

When your system sends an alarm, we check the video and follow your response plan.

$10per camera / month

60 minutes of staff time per camera each month, shared across your site. Extra time: $0.30/minute.

Alarm verification
Illustration of camera checkpoints at a site gate, yard and loading bays
Scheduled camera round1 Gate 2 Yard 3 Loading bays

Check at set times

We check your cameras at the times you choose and send you a report of what we find.

$0.75per scheduled check

Up to 16 camera views and 5 minutes per check. Minimum: $22.50 per site each month.

Virtual guard tours

Separate detection from the response decision

Detection software identifies patterns or activity that match its configuration. Filtering affects which events continue through the workflow. An operator then reviews available information against the site instructions. These stages answer different questions.

Detecting a person does not establish that the person lacks permission to be there. An expected delivery, a maintenance visit and activity in a restricted area may look similar until the schedule and location are considered. Keep that context with the account rather than asking the detector to supply it.

Analytics-assisted review

A detection starts the review.

  1. Detection

    A rule flags activity

  2. Review

    A person checks the video

  3. Improve the rule

    Review recurring triggers

Conceptual event path. Functions and processing location require a technical review.

View the working details
  1. Scene and rule

    A defined area and activity condition.

  2. Event

    A signal with site and camera context.

  3. Operator review

    Available video and site instructions.

  4. Recorded outcome

    Observation, action and unresolved detail.

Review recurring event causes

Use outcomes to identify scene changes or a rule that needs review.

Find out what the analytics connection includes

Processing may depend on the camera, recorder, another device or a hosted platform. The service name cloud analytics does not establish the actual architecture, storage location or retention period. Those details belong in the technical review.

Questions for the detection-to-review path
Part of the workflowInformation to request
DetectionWhich device or service creates the event, using which supported feature?
FilteringWhich rules determine what reaches an operator, and who can change them?
Video contextWhat live view or recorded material accompanies the event?
InterruptionWhat happens if the detector, connection or video source is unavailable?
RecordsWhich events and changes are retained, who can review them and for how long?

Test relevant activity as well as unwanted triggers

A useful evaluation includes the activity you want to detect and common activity that should not require an escalation. Observe the actual camera angle, lighting, scene movement and site schedule. Document where the system is uncertain or the view is inadequate.

Reducing alerts is only one part of tuning. Check whether representative relevant activity still produces the expected event and whether it arrives with usable video. Otherwise, a quieter queue could conceal a detection or delivery gap.

Use authorized test activity where practical. Keep the test condition, expected result and observed result together, so a later review can distinguish a change in site conditions from a change in the settings.

Keep a small record of each tuning change

When one camera generates repeated unwanted events, examine examples before changing the rule. A moving object, altered lighting or a stale access schedule calls for different work. Changing a whole portfolio because of one noisy camera can introduce new problems.

Describe the problem

Record the affected site and camera, recurring condition and example event references.

Record the change

Identify what changed, who authorized it and when it took effect. Keep the previous configuration or recovery route available to the responsible technical team.

Check both sides

Review unwanted triggers and relevant test activity after the change. Note any new uncertainty or loss of detection.

Revisit changed scenes

Moving stock, relocated cameras and seasonal lighting can make an earlier test unrepresentative. Reassess the affected views.

Bring the event problem you want to solve

Share camera and recorder details, the current detection path, coverage hours and examples of useful and unwanted events. Include the monitoring actions you want those events to support.

That information supports a compatibility and workflow review. A generic camera standard or an analytics label is not enough to establish that all the required functions will work together.

Illustration of monitoring staff testing camera views and site setup

Common questions

Before you bring an account on board.

Does analytics replace the monitoring operator?

In this service, analytics supports alert handling and operators carry out the defined review and response tasks. Identify what reaches the team and how unclear events are handled.

Can analytics miss activity?

Yes. View conditions, configuration, supported features and technical interruptions can affect detection. Review relevant test activity and missed or unclear events as well as unwanted alerts.

Does cloud analytics include continuous recording?

Not by the name alone. Recording, processing, storage, retention and footage access are separate functions to examine in the proposed arrangement.

Can you use our existing analytics?

Share the actual product, version, event output and video access requirements for review. Compatibility must cover the intended workflow, not just a product category.

What would you like
to hand over?

Share your company, client-site mix and coverage needs. Let’s work through the next step.

Illustration of a fictional monitoring specialist reviewing camera views
Your camera setupYour coverage hoursYour response plan