Shift supervisor handbook
On this page
- What this covers
- Who it is for
- The admin screen
- Start of shift checklist
- 1. Live alarms and supervision
- Watch the shift
- Step in on one site
- Handle alarms yourself
- If something goes wrong
- 2. Operator availability and automatic forwarding
- Operator states
- When no operator is available
- What you should do
- Good to know
- 3. Recordings and alarm viewer
- Find alarms
- Open one alarm
- Export
- Typical questions and the filter for them
- If something goes wrong
- 4. Dashboards
- The figures
- Alarm flow trend
- Onboarding health
- Latest decisions
- Getting started checklist
- Operator performance
- If something goes wrong
- 5. Reports and e-mails
- Set the schedule
- Other e-mails from GC Surge
- If something goes wrong
- 6. Users, roles and access
- Roles
- Invite a user
- Good to know
- If something goes wrong
- 7. Settings
- 7.1 Report schedule
- 7.2 Change password
- 7.3 Alarm reception: where confirmed alarms go
- 7.4 Alarm routing: the timing
- 7.5 Delete tenant
- 8. Audit and traceability
- What is recorded
- Trace one alarm
- Trace actions
- Typical uses
- Good to know
- FAQ
What this covers
Everything an admin or shift supervisor needs to run a shift with GC Surge: watching live alarms and operators, what happens when no operator is available, reviewing recordings, reading the dashboard, reports and e-mails, users and roles, settings, and the audit trail.
Who it is for
Users with the role Admin who supervise operators. Setting up sites and devices is described in "Onboarding sites and devices".
The admin screen
Item in the top navigation | Use |
|---|---|
Home | Dashboard: figures, trends, onboarding health, latest decisions. |
Live Alarms | The queue and the operators, live. |
Sites & Cameras | Sites, devices, forwarding per site and device. |
Team | Users, roles, operator performance. |
Billing | Subscription, usage, invoices. |
Recordings | Every alarm and every decision. |
Time range (for example Last 24 hours) | Sets the period for the figures and lists. |
Admin / Operator switch | Switch to the operator screen to handle alarms yourself. |
Settings, Profile, Log out | Account settings, your own profile, sign out. |
Start of shift checklist
- Open Live Alarms. Check that the expected operators are monitoring.
- Check Sites waiting in queue and Longest wait.
- Open Home. Look at Latest decisions for entries Forwarded, no operator since the last shift.
- Look at Onboarding health for warnings.
---
1. Live alarms and supervision
Watch the shift
Watch:
- Open Live Alarms. This is the first page an admin sees after sign-in.
- Read the four cards:
Card | Meaning | Act when |
|---|---|---|
Operator monitoring | Operators who are monitoring now. The line below shows how many are paused and how many are on cooldown (the hold after a real alarm). | The number is lower than your shift plan. |
Sites waiting in queue | Site events that wait for an operator, with the alarms collected. | The number keeps growing. |
Longest wait | The age of the oldest waiting site event. | It comes close to your target, or to the Alarm queue timeout. |
Forwards to ARS today | Forwards to your alarm system today: by operator and with no operator. | "With no operator" is higher than you expect. |
- Read the queue table ("Queue · longest wait first"). Filters: All, Waiting, Assigned. Columns: Site, Waiting, Open alarms, Cameras, Assigned to, Supervisor actions.
- Read the Users panel. It shows each operator with the state. Filters: All, Paused, Offline.
Step in on one site
In the row of a site, open Supervisor actions.
Action | What it does | Use it when |
|---|---|---|
Assign... | Gives a waiting site to the operator you choose. | A site must be handled now by a specific person. |
Reassign... | Moves a held site to another operator. | The current operator cannot finish it. |
Release | Puts a held site back into the queue. It keeps its wait time. | The operator is blocked and anyone may take it. |
Forward now | Sends the alarms of the site to your alarm system immediately. | The site cannot wait and no operator can take it. |
You can only choose operators who are actively monitoring.
Handle alarms yourself
- Switch from Admin to Operator at the top.
- Click Start Shift, then Resume Monitoring.
- Work as described in the Operator handbook.
- End your shift before you switch back to Admin.
While you are in Operator with a started shift, you count as an available operator.
If something goes wrong
Symptom | Cause | What to do |
|---|---|---|
The page shows a Coming soon notice at the top | Some live figures of this page are still being completed. | You can close the notice. If a figure looks wrong, compare it with Home (Latest decisions) and Recordings. |
An operator is signed in but gets no sites | The shift is not started, or the operator is paused or inactive. | Ask the operator to click Start Shift. |
A site stays Assigned for a long time | The operator is busy with a large site, or has left the desk. | Talk to the operator. Use Reassign... or Release. |
"You can only assign operators who are actively monitoring" | The chosen operator is not monitoring. | Choose another operator. |
"This operator is on post-forward hold and cannot take a site yet" | The operator has just confirmed a real alarm. | Wait or choose another operator. |
"Failed to forward alarms. Please try again." | No destination is set, or the receiver did not answer. | Check Settings > Alarm reception. Use Send test event. |
"End your shift before switching back to admin mode." | Your own operator shift is still running. | Open the menu on the operator screen and click End shift. |
---
2. Operator availability and automatic forwarding
Operator states
State | Meaning | Gets sites? |
|---|---|---|
Monitoring | Shift started, in the queue or holding a site. | Yes |
On hold (cooldown) | Confirmed a real alarm. Finishing it in the alarm system. | No, until the hold ends |
Paused | Paused by the operator. | No |
Inactive | Paused automatically: held a site too long without a decision. | No, until the operator starts the shift again |
Offline | Not signed in, or connection lost. | No |
When no operator is available
No operator is available when nobody is monitoring. Admins in Admin mode do not count.
- NOVA99x still filters every alarm.
- A real alarm waits for the time set in Forward after (NOA).
- If nobody starts monitoring in that time, GC Surge forwards it to your primary alarm reception system.
- The alarm is marked Forwarded, no operator. In the alarm detail the operator is "System: no operator available" and the handling status is "Forwarded to ARS · no operator".
The same happens with a site that an operator releases (pause, inactivity, end of shift, logout) when no other operator is free.
What you should do
Situation | Action |
|---|---|
A gap in the shift plan is coming | Decide before: either an admin switches to Operator, or you accept automatic forwarding for that time and tell the people at the alarm system. |
You see Forwarded, no operator in Latest decisions | Open the entry in Recordings. Check that the alarm arrived in your alarm system and was handled there. |
It happens often | Check shift coverage. Check Operator inactivity: a short value sets operators to inactive quickly. |
You want no unchecked alarm at the alarm system | This is not possible without an operator. Keep at least one operator monitoring at all times. |
Good to know
- Without a forwarding destination, alarms cannot be forwarded. They stay in GC Surge. Set the destination before you go live (section 7.3).
- Automatic forwarding is recorded like every other step.
---
3. Recordings and alarm viewer
Watch:
Recordings lists every alarm that GC Surge received: filtered alarms, alarms decided by operators and alarms forwarded automatically.
Find alarms
- Open Recordings.
- Set the time range at the top.
- Choose the view: Card view (one card per alarm with its picture, its result, the camera and the time), List view (table) or Events logs (section 8).
- Use the filters for site and device. Click More filters for:
Filter | Values |
|---|---|
Operator | One of your operators. |
Operator decision | True alarm, False alarm, Not handled |
NOVA99x | True alarms, False alarms |
Modality | Thermal, Optical |
System action | Passed to ARS, Not passed |
Status | For example Open, Closed, Sent to ARS, Not an alarm, Forwarded, no operator |
- Total alarms shows the number of results. Clear removes the filters.
The list shows Current image, Site, Device, Date, Acknowledged status and Modality. Click Show more for further details of a row.
Open one alarm
Watch:
- Click an alarm. The panel Alarm details opens with the camera name.
- Alarm images: Pre-alarm, Alarm, Post-alarm and GIF. Alarm sequence plays them in order.
- Alarm workflow shows the history of this alarm:
Line | Meaning |
|---|---|
Event received at | When GC Surge received the alarm. |
NOVA99x filter | The result of the filter, for example "Real alarm". |
Operator | Who decided, or "System: no operator available". |
Handled at | When the decision or the automatic forward happened. |
Operator handling status | The result, for example "Forwarded to ARS · no operator". |
- Actions: Open alarm details (full page), Copy link (a link to this alarm for a colleague or for support), View ZenMode event (the whole site event as the operator saw it).
Export
- Set the time range and the filters.
- Click Export.
The time range must be less than 24 hours to export. For a longer period, export day by day.
Typical questions and the filter for them
Question | Filter |
|---|---|
Which real alarms did we send today? | System action: Passed to ARS |
What was forwarded without an operator? | Status: Forwarded, no operator |
What did NOVA99x filter on site X? | Site X, NOVA99x: False alarms |
What did operator A decide last night? | Operator: A, time range of the night |
Which alarms are still open? | Operator decision: Not handled |
If something goes wrong
Symptom | Cause | What to do |
|---|---|---|
No results | The time range or a filter excludes everything. | Click Clear. Set Last 24 hours. |
"The time range must be less than 24 hours to export." | The period is too long for one export. | Shorten the time range and export several times. |
"Could not export alarm events. Try again." | A temporary problem. | Try again with a shorter period. |
"There are no ZenMode events for open alarms" | The alarm is not decided yet, so there is no site event to show. | Open it again after the decision. |
A copied link shows "The linked alarm is outside the current viewing period." | The time range of the person who opens it does not include the alarm. | Change the time range to include the date of the alarm. |
An alarm has no pictures | The device sent none. | Check the alarm settings of the device. |
---
4. Dashboards
Watch:
Home is the dashboard. All figures follow the time range at the top and the site and device filters.
The figures
Card | Meaning | How to use it |
|---|---|---|
Operator-handled alarms | Alarms that operators decided. | Workload of the team. |
Alarms filtered by NOVA99x | Alarms that were filtered before an operator saw them. | The work the filter saved. |
Avg. operator processing time (sec) | Average time from assignment of a site to the decision. | Speed of the team. A sudden rise means a problem: difficult sites, or operators leaving sites open. |
Avg. cameras per operator | Cameras covered per operator. | Capacity planning. |
Alarm closure efficiency (%) | Share of alarms closed within the target time. | Service quality. |
Alarm flow trend
The chart shows Total, Filtered and Real alarms over time. Use it to find peak hours and plan shifts. Next to it:
Figure | Meaning |
|---|---|
Time saved | Estimated operator time saved by the filter and the site grouping. |
Cost saved | The time saved, valued at an hourly rate. |
Potential capacity increase | How many more devices the team could cover with the time saved. |
Potential revenue increase | An estimate based on the freed capacity. |
These four figures are estimates. Move the mouse over a figure to see the assumptions and the formula.
Onboarding health
Shows Cameras active, Reaching alarms, the cameras per connection type and warnings such as "3 cameras stuck > 24 h". Click Fix to see the devices and what to do. See "Onboarding sites and devices".
Latest decisions
A table with Time, Site, Camera, Decision, Operator and Time to decide.
Decision | Meaning |
|---|---|
GREEN | The operator decided Not an alarm. |
RED | The operator decided Real alarm. It was forwarded. |
Forwarded, no operator | Forwarded automatically. |
Getting started checklist
Shows the open setup steps of your account. See "Signup and first login".
Operator performance
Open Team. Below the user list, Top Performers shows the number of operators, the top alarm count and the leader. The table shows per operator: Picked sites, Avg. processing (sec), Alarms handled and Unique devices. The entry "system" stands for alarms that were forwarded automatically without an operator.
If something goes wrong
Symptom | Cause | What to do |
|---|---|---|
All figures are empty or 0 | No alarms in the time range, or a site or device filter is set. | Set a longer time range. Reset the filters to All sites and All devices. |
"No operator decisions in this period yet." | No operator decided in the time range. | Extend the time range. |
The figures differ from your alarm system | GC Surge counts camera alarms. Your alarm system receives one alarm per confirmed event. | Compare RED decisions and Forwarded, no operator with the alarms in your alarm system. |
One operator has a much higher processing time | Large sites, or sites left open. | Look at the decisions of this operator in Recordings. Check how often the operator became inactive in Events logs. |
---
5. Reports and e-mails
Watch:
GC Surge sends a report e-mail with the operator figures (cameras per operator and alarm processing time) on a schedule you set.
Set the schedule
- Open Settings > Report schedule.
- Choose the Frequency: Hourly, Daily, Weekly or Monthly.
- Choose the Time zone.
- Choose the Time of day.
- For Weekly, choose the Day of week. For Monthly, choose the Day of month.
- Click Save Schedule. You see "Report schedule updated successfully".
Frequency | When the report is sent |
|---|---|
Hourly | Every hour. No day or time is needed. |
Daily | Every day at the selected time. |
Weekly | On the selected day and time. |
Monthly | On the selected day and time. |
Other e-mails from GC Surge
Who gets it | When | |
|---|---|---|
Verification e-mail | Every new user | After registration. |
Invitation | Invited users | When an admin invites them. |
Password reset | The user who asked for it | After Forgot password?. |
Site key and setup instructions | The site contact | When you send the site key or delegate an installation. |
Invoice | The admin | On the 1st of the month. |
Fair-use alerts | The admin | At 80% of a camera's quota and when a camera exceeds it, if switched on in Billing. |
If something goes wrong
Symptom | Cause | What to do |
|---|---|---|
No report arrives | The e-mail address is not verified, or the report is in spam. | Verify your e-mail (banner on Home). Check spam. Check the schedule and the time zone. |
The report arrives at the wrong hour | The time zone is not yours. | Set the Time zone and save. |
"Failed to update report schedule. Please try again." | A field is missing, or a temporary problem. | Fill in all fields for the chosen frequency and save again. |
---
6. Users, roles and access
Roles
Role | Can do |
|---|---|
Operator | Handles alarms on the wall. No access to sites, team or billing. |
Admin | Everything an operator can do, plus sites, team, routing and billing. |
Invite a user
Watch:
- Open Team. The page shows User list ("Manage user accounts and role assignments") with Avatar, Name, Email, GC Surge Role and Actions.
- Click Invite New User.
- Enter the Name and the Work email. You can upload an image.
- Choose the role: Operator or Admin.
- Click Send Invite.
- The user gets an e-mail with a link and sets a password. Operators land on the wall, admins on the admin pages.
Good to know
- Invite every person with their own address. Decisions are recorded per user.
- Give the Admin role only to people who need sites, team, routing and billing.
- Tell new users to check the junk or spam folder for the invitation.
- For your own account you can edit your image and name in Profile.
- Invite an operator is an item of the Getting started checklist.
If something goes wrong
Symptom | Cause | What to do |
|---|---|---|
The user did not get the invitation | Spam folder, or a typing mistake in the address. | Ask them to check spam. Check the address in the user list. Invite again with the correct address. |
"Enter a valid email address" | The address is not valid. | Correct it. |
The invited user sees a registration form | The user opened the website and clicked Register instead of the link in the e-mail. | Ask them to use the link in the invitation. Registering creates a separate organisation. |
An operator can see too much, or an admin too little | Wrong role. | Change the role in the user list. |
A user left the company | The account is still active. | Remove the user in the user list, or contact NXGEN support if you cannot. |
---
7. Settings
Open Settings at the top right. The sections are Report schedule, Change password, Alarm routing, Alarm reception and Delete tenant.
7.1 Report schedule
See section 5.
7.2 Change password
- Open Settings > Change password.
- Enter Current password, New password and Confirm new password.
- Click Update Password.
Symptom | Cause | What to do |
|---|---|---|
"Wrong password" | The current password is not correct. | Enter it again, or use Forgot password? to get a reset e-mail. |
"New password must be different from your current password" | Old and new are the same. | Choose another password. |
7.3 Alarm reception: where confirmed alarms go
This is the main destination for the whole account (Primary alarm reception system). It is used after a Real alarm decision and for automatic forwarding when no operator is available.
Watch:
- Open Settings > Alarm reception.
- Under Forwarding destinations, choose the tab Webhook or DC09. To add a further destination, click Add webhook or Add DC09.
- Fill in the fields:
Type | Fields |
|---|---|
DC09 (SIA DC-09) | Receiver IP address, Receiver port, Account, Key |
Webhook | Method, URL, headers (Key, Value; Add header for more), Authentication (No Auth, Basic Auth, Digest Auth, Bearer Token) |
- Click Send test event. Check that the test arrived in your alarm system.
- Click Save Changes.
Forwarding for one site or one device is set in Sites & Cameras. See "Onboarding sites and devices", section 7.
Symptom | Cause | What to do |
|---|---|---|
"Failed to send the test event. Kindly check the credentials." | Wrong IP, port, account or key, or the receiver is not reachable from the internet. | Check the values with the administrator of your alarm system. Open the port on the firewall. |
"Fill at least one DC09 or webhook destination before sending a test event." | No destination is filled in. | Fill in one destination first. |
The test is sent, but your alarm system shows nothing | The receiver accepted the connection but does not know the account. | Create or check the account in your alarm system. |
"Could not save alarm reception settings. Please try again." | A field is not valid, or a temporary problem. | Check IP, port and URL. Save again. |
If you do not configure a receiver, alarms stay in GC Surge and are not forwarded to an alarm system.
7.4 Alarm routing: the timing
Watch:
- Open Settings > Alarm routing.
- Set the values and click Save Changes.
Setting | What it controls | Possible values | A new account starts with |
|---|---|---|---|
Forward after (NOA) | How long to wait before forwarding an alarm to your primary alarm reception system when no operators are online. | Immediately, 60s, 120s or 180s | Check your value |
Operator inactivity | How long an operator can remain inactive on a held site before being paused and the site is released. | 1 to 120 seconds | 30 seconds |
Hold after escalation | The wait after a Real alarm decision before the operator receives another site. | 1 to 120 seconds | 60 seconds |
Alarm queue timeout | The maximum time alarms remain in the queue before timing out. | 1 to 30 minutes | 30 minutes |
How to choose the values is described in "Queue and assignment", section 4. Tell your operators the values of Operator inactivity and Hold after escalation. They work with them every minute.
7.5 Delete tenant
Delete tenant removes your whole organisation: all sites, devices, users, alarms and configuration. This is permanent and cannot be undone.
- Open Settings > Delete tenant.
- Click Delete Tenant.
- Type your account e-mail exactly to confirm.
Before you do this: export what you need from Recordings, download your invoices, and change the alarm path of your devices so that your alarm system still receives alarms. To stop only the subscription, use Billing instead.
---
8. Audit and traceability
Watch:
GC Surge records what happens to each alarm and what users do.
What is recorded
Area | Examples |
|---|---|
Each alarm | Received, result of NOVA99x, decision, operator, times, what was forwarded. |
Operator session | Shift start, pause, resume, automatic pause because of inactivity, end of shift, logout. |
Supervisor actions | Assign, reassign, release, forward now. |
Configuration | Changes to sites, devices, forwarding and settings. |
Trace one alarm
- Open Recordings and find the alarm.
- Open it and read Alarm workflow (section 3).
- Click View ZenMode event to see the whole site event.
- Use Copy link to put a reference to the alarm into your own incident report.
Trace actions
- Open Recordings > Events logs.
- Set the time range.
- Read the columns:
Column | Meaning |
|---|---|
Date & time | When it happened. |
Action | What was done. |
Action status | The result of the action. |
User | Who did it. |
Category, Sub category | The kind of action. |
Source entity | What the action was applied to. |
Device, Site | Where it applies. |
Typical uses
Question | Where to look |
|---|---|
Who decided this alarm, and when? | Recordings > alarm > Alarm workflow |
Was this alarm forwarded, and by whom? | Operator handling status in the alarm detail |
Why was an alarm forwarded without an operator? | Events logs at that time: were operators paused, inactive or logged out? |
Who changed the forwarding of a site? | Events logs, filter by site |
How often was an operator set to inactive? | Events logs, filter by user |
Good to know
- Operators are told on every confirmation (pause, resume, end shift, logout) that the action is recorded.
- For a customer complaint, the alarm detail with pictures, times and operator is the evidence. Copy the link and export the period.
Symptom | Cause | What to do |
|---|---|---|
Events logs shows no records | No actions in the time range, or a filter is set. | Extend the time range. Clear the filters. |
You cannot find an old alarm | The time range does not include it. | Set a custom range around the date. |
---
FAQ
Can I see what the operator saw? Yes. Open the alarm in Recordings and click View ZenMode event.
Can I undo an operator decision? No. If a real alarm was closed as Not an alarm, handle it in your alarm system by hand and note it in your own incident process. The original decision stays recorded.
Can I pause an operator? Take the site away with Release or Reassign... and talk to the operator. The operator pauses with Pause monitoring.
Can operators see the dashboard or recordings? No. Operators only have the operator screen.
What should I check first after a night without supervisor? Home > Latest decisions for Forwarded, no operator, then Recordings with System action: Passed to ARS.
Thank you — your feedback goes to the team that owns this page.
