Full Deployment Journey

• Genie URL: https://gcsurge-docs.nxgen.cloud/gcsurge/docs/setup-deployment/full-deployment-journey

This guide is an end-to-end, step-by-step guide for bringing a new customer or new site cluster onto GC Surge. Use it as a pre-deployment checklist, a reference for tracking progress during rollout, and a post-deployment validation reference. Covers: About This Guide, Phase 1: Account and User Setup, Step 1 – Create the account.

About This Guide

This guide is for Super Admins responsible for bringing a new customer or site cluster onto GC Surge. Follow the phases in order — each phase builds on the previous one. The guide covers six phases: account and user setup, site creation, Site Key distribution, field activation, operational setup, and go-live confirmation. Use it as a pre-deployment checklist before you start, a progress tracker during rollout, and a validation reference before handing off to the operations team.

Phase 1: Account and User Setup

Step 1 – Create the account

1. Navigate to the GC Surge signup page.
2. Complete all required fields: email, tenant name, phone number with country code, password. The Tenant Name cannot be changed after creation — choose it carefully before submitting.
3. Complete OTP verification via SMS. Successful OTP verification logs you in automatically — no separate login step is needed.
4. Verify login completes successfully and the Home dashboard is accessible.
5. On first login, an Email Verification — Action required callout appears on the Home dashboard. Click through it to confirm your email address before you can receive shift reports or scheduled notifications.

Step 2 – Invite all required users

1. Navigate to the Users module and click Invite New User. Enter the user’s name, email, and phone, then select their role — Super Admin or Operator — from the GC Surge Role dropdown in the invitation modal, and click Send Invitation.
2. Invite all Super Admins first – they need access to complete the remaining steps.
3. Then invite all operators who will handle incoming alarm events during shifts.
4. After each invitation is sent, confirm the user appears in the Users table with the correct role and an Active status.
5. Each invitee completes first-time login (including phone OTP verification) to activate their account — have operators do this before you assign them to sites and shifts.

Phase 2: Site Creation

Step 3 – Create sites in Configuration

1. In the left sidebar, go to Configuration.
2. Click ADD and choose the method that fits your deployment:Guided setup (Recommended) — walks you through each step interactively. Best for first-time onboarding or when you want to verify every setting as you go.Add sites manually — fills in a single-site form directly. Fast when you already know all camera details and connection type.Import from spreadsheet — upload an .xlsx file to add multiple sites and cameras at once. Best for large deployments. See Bulk Spreadsheet Import for the spreadsheet format and column definitions.Universal camera support — for cameras that push alarms to GC Surge on their own via REST API, SMTP, or FTP, rather than being polled directly.
3. For each site, complete the required fields. Required fields vary by connection type:Public IP (direct connection): Site name, Camera IP, Camera brand, Port, Username, Password. Contact Info is optional for Public IP sites.Private network, VPN, or GC Edge: all of the above plus Contact person, Contact email, and Contact phone. The Site Key is sent to the contact email (and optionally WhatsApp) to complete field activation. Empty contact fields block Site Key delivery.For full field definitions by connection type, see Setting Up Sites.
4. Use consistent site naming conventions. Site names appear in Video Search, Analytics, and subscription filters. Inconsistent names create operational confusion downstream — agree on a naming format before you start.
5. After creating all sites, open the Sites Table and confirm every Private/VPN and Edge site has a Contact email populated. The Site Key is delivered to this address. Public IP sites do not require contact info.

Step 4 – Validate site data before proceeding

1. Confirm the Camera brand field is correct for each site. An incorrect brand prevents automatic alarm configuration.
2. For Private/VPN and Edge sites, confirm all Contact Info fields are populated — empty fields block Site Key delivery. Public IP sites do not use a Site Key and do not require contact info.
3. Confirm site names follow your agreed naming convention before you distribute Site Keys. Site names are difficult to change once sites are active and alarms are flowing.

Phase 3: Site Key Distribution

Step 5 – Distribute Site Keys to onsite contacts

Each site has a unique Site Key, beginning with the GCSK- prefix. This key must reach the person who will run the GDA activation app at the physical site before they travel to the location.

1. In Configuration, locate the site in the Sites Table.
2. Open the site Actions menu and select Send Site Key.
3. Choose the delivery method — WhatsApp sends the key directly to the contact’s phone — they copy-paste it into the GDA; email works for the same purpose; QR code is best for in-person handoffs. Confirm receipt with the contact before they travel to the site.
4. Treat Site Keys as temporary passwords. Do not share them via unsecured channels or public messages.

Phase 4: Field Activation

Step 6 – Activate cameras using the GDA

This step applies to Mode 2 (Private/VPN) and Mode 3 (Edge) sites. Mode 1 (Public IP) sites do not require this step — cameras are configured automatically by GC Surge when the site is created in Configuration.

• Mode 2 (Private/VPN) — the onsite contact runs the GDA on a PC on the same network as the cameras (Windows). See Setting Up Sites for the local agent option.
• Mode 3 (Edge) — the onsite contact installs GC Edge on a Windows PC at the site. GC Edge connects to the camera’s RTSP stream, automatically scans the network for cameras, and runs NOVA99x filtering locally. After setup, GC Edge must be manually armed before alarms begin flowing — it does not arm automatically.

In both modes, the contact must be physically present at the site. The app discovers all ONVIF-compatible cameras on the local network and configures event forwarding to GC Surge automatically.

1. Ensure the PC running the GDA is connected to the same local network as the cameras — same Wi-Fi network or switched Ethernet segment. If cameras are on a separate VLAN, additional network configuration is required before activation. See Genie Discovery Agent (GDA) — Field Activation for network topology options.
2. Open the GDA and enter the Site Key when prompted.
3. The app runs WS-Discovery to find all ONVIF-compatible cameras on the subnet. Review the discovered camera list and confirm the count matches what is expected.
4. If cameras are missing from the discovered list, confirm ONVIF is enabled on the devices and that UDP multicast is not blocked on the network switch.
5. Confirm activation in the app. GDA configures event forwarding for all discovered cameras automatically — no per-camera manual steps required.

Step 7 – Confirm activation status in Configuration

1. Return to Configuration and monitor the Site Status. A site’s Site Status reaches Done once all its cameras are configured and events begin flowing. (The separate Status column shows the site as Active once it is enabled, regardless of onboarding progress.)
2. Allow up to 10 minutes after the GDA confirms success. The cloud status update is not instantaneous.
3. Verify the device count shown in the Sites Table matches the number of cameras activated at the site.
4. If a site remains Pending after 10 minutes, open Video Search and check whether events are arriving. If events are visible, the activation succeeded and the status display has a lag.

Phase 5: Operational Setup

Step 8 – Verify NOVA99x Is Filtering

NOVA99x is always active on every camera from the moment cameras are connected — no action is required to enable it. There is nothing to configure or confirm in My Subscription.

After 24 to 48 hours of alarm flow, open Analytics and check the filter ratio. A high filter ratio confirms NOVA99x is actively removing noise before alarms reach your operators. On a paid subscription, each camera includes 3,000 alarms per month in the base price.

Step 9 – Verify event flow in Video Search

1. Navigate to Video Search.
2. Select the customer and site from the top selectors. Events will not display without both selections.
3. Confirm events are appearing. If no events appear within 10 minutes of a confirmed camera trigger, follow the “Events are not appearing in Video Search” section in the Troubleshooting Guide, which walks through customer/site selection, site status, activation, and (for SMTP cameras) delivery checks.
4. Open one event and confirm the event detail view loads correctly with image and metadata.
5. Confirm operators can navigate Video Search filters confidently and locate events without assistance. If they struggle, run a short training session on the filter panel before go-live.

Phase 6: Go-Live Confirmation

Step 10 – Final validation checklist

Before marking the deployment complete, confirm each of the following:

• All sites show a Site Status of Done in Configuration (no sites left in Pending, Error, or Partial states).
• All operator accounts are active and verified in the Users module, and operators can log in successfully.
• Events are flowing in Video Search for all active sites.
• NOVA99x is active on all sites — confirm the filter ratio is visible in Analytics.
• At least one operator has completed a live monitoring session in ZenMode.
• The Alarm Center - Admin View dashboard shows operator activity during an active shift.
• Analytics shows data for all active sites.
• The primary Super Admin has reviewed My Subscription and confirmed all camera counts are as expected.

Ongoing Operations

Once go-live is confirmed, hand the platform to the operations team with the following standing instructions:

• Super Admins check Alarm Center - Admin View at the start of each shift to review active operator status and overnight performance.
• Operators use ZenMode during active monitoring shifts and Video Search for investigations and evidence review.
• My Subscription is reviewed monthly to monitor usage and identify any unexpected overage exposure.
• Configuration is audited monthly — remove any sites or cameras that are no longer active to keep counts accurate.