Arisan · Product & Sales Guide

Don't replace what the customer already has

All three product lines say the same thing: whatever the customer has already paid for stays, and we connect to it and fill the gap. Integration is our strongest suit — in the field, get the brands and model numbers; the integration work itself is handled back at the company.

Customer says“All my fixed cameras are in the VMS, but the body-worn footage sits apart — pulling it is a manual job.” → LiveEdge Customer says“Several brands, some of the gear is old, and checking one location means opening three systems.” → XMap Customer says“The recorders are all on site. I can't reach them, and I only find out they're down when someone drives there.” → Smart Gateway

Three product lines

Every card has the same shape: the sentence the customer says, what you are actually selling, three benefits they'll understand, who buys, and what to nail down.

LiveEdge

You are selling body-worn hardware plus the Nexus command centre — and it plugs into the VMS the customer already runs.

Trigger line “All my fixed cameras are in the VMS, but the body-worn footage sits apart — pulling it is a manual job.”

Animations: body-worn camera and dashcam

Out on patrol there are two modes. Live + Record streams back to the command centre the moment Record is pressed. Buffer keeps everything on the camera (including a configurable pre-record) until SOS is pressed, which alerts the command centre, sends video back and opens two-way talk. Location goes straight to Nexus the whole time the guard is out.

Open the full page →

How it works: two very different situations

Indoors and out in the field, a body-worn camera takes completely different paths. Make that clear and the customer understands why both Vault and Nexus exist.

Case A Back at the station (indoors) Camera and Booth only — the job is backfill

Nothing here involves command and control: the officer returns, the camera is docked, whatever hadn't uploaded lands in Vault. Done.

Case B Out in the field (while streaming) Video goes through Vault; location and audio go to Nexus

Video only ever goes through Vault, which relays it as-is, without re-encoding. The service endpoints for location and two-way audio sit on Nexus. In the customer's own VMS, each camera is an ONVIF camera (video over RTSP), added like any other — Nexus does not connect to the customer's system directly.

Which path uses which protocol

What is being sent	Protocol	From → to
Video while in the field	RTMP	BWC → Vault
Live video for the command centre	WebRTC	Vault → Nexus
Video for the customer's VMS	ONVIF · RTSP	Vault → customer's VMS
Location	HTTP POST	BWC → Nexus
Two-way audio (after SOS)	WebRTC	BWC ⇄ Nexus
Backfill after returning	Booth	BWC → Booth → Vault

What ArgusVault does

Ingest: RTMP while in the field, Booth backfill once back at the station
Convert: WebRTC for live viewing in Nexus; in the customer's own VMS, each camera is an ONVIF camera
Evidence management: auto-assignment to cases, chain of custody, export audit trail
Retention: automatic deletion at expiry, legal hold on anything under investigation
Each licence includes 5 direct RTSP connections, so ad-hoc fixed cameras come in too

What Nexus does

Live command: where people are (location via HTTP POST) and what they see (WebRTC from Vault)
Two-way audio over WebRTC — the service endpoint lives on Nexus
Dispatch and reporting: assign tasks, status back from the field
Event handling: events in, with the handling process and outcome on record

Say it like this “Your fixed cameras don't move and your VMS doesn't change. What we add is the part that moves — and each camera shows up as an ONVIF camera in the VMS you already have, so you see it on the screen you already use. It isn't another platform.”

Who buysCustomers who already have a VMS and fixed cameras in place, but nothing covering people on the move. Someone who has already spent the money is the easiest conversation — the budget exists and so does the person running it.

Opening question“How do you line up your body-worn footage with your fixed-camera footage today?”

Nail downWhich VMS and which version · how many devices · self-hosted or cloud · how long evidence must be kept

XMap

Every brand of device pulled into one interface: map, event management, CMS.

Trigger line “Several brands, some of the gear is old, and checking one location means opening three systems.”

Three pillars

Map

Every point on one map, regardless of brand or site. An alarm comes in and the map jumps to it — the operator doesn't have to work out which camera it was.

Event Management

The layer on top of the map, built for security companies: events in, work dispatched out, SOP checked off step by step, handling on record, reports afterwards. This is what a guarding company does all day, and it's the part that gets the nod fastest.

CMS

Again, every brand integrated. What the customer sees is one interface:

Map ViewCMS ViewLive ViewPlaybackEvents

What it looks like once integrated

Read it bottom-up: devices of any brand come in → live view, playback and events apply to all of them equally → the top layer presents Map View, CMS View and Event View. Not a single device gets replaced; the dashed box on the right is a brand we haven't connected yet, which the company will integrate.

How far does the integration go

Essentially, we can integrate anything. Already integrated: Dahua, Hikvision, Nx Witness and LILIN, among the main brands. If the customer has something else on site, the company will integrate it. The only thing to do in the field is bring back the brand and the model number.

Say it like this “Not one device gets replaced. The main brands are already connected — if you have something else on site, give me the model numbers and we'll integrate it.”

Who buysMulti-site operations, mixed-brand estates, campuses and plants — plus any guarding company that needs event management and dispatch. Where a VMS exists but nobody can see the whole picture, you're in fastest.

Opening question“To check what's happening at one location right now, how many systems do you have to open?”

Nail downBrands and models on site · how many cameras go on the map · event management and dispatch needed? · any LPR, face recognition or access control to connect

Smart Gateway

The software gateway that brings a site's cameras and recorders up to CliO Cloud — and an AI Operator on site while it is there.

Trigger line “The recorders are all on site. I can't reach them, and I only find out they're down when someone drives there.”

Gets the site onto CliO CloudLILIN, Dahua, Hikvision, Network Optix and others reach the cloud through it, with no fixed IP and no VPN — or get bridged into another VMS. Nothing gets replaced or standardised.

An AI Operator watching the gearChecks every site daily: recording gaps, cameras knocked out of position or blocked. You don't wait for the customer to call and complain — and that part runs purely locally.

Reports sent out automaticallyInspection results emailed to the customer or the site manager on a schedule. For a guarding company, that's something to hand over every month.

What the architecture looks like

One Smart Gateway takes in a whole site's worth of mixed equipment. Go to the cloud and see every site together — or, if the customer doesn't want the cloud, leave it standing on site on its own. That's your fallback when the cloud conversation stalls.

Say it like this “It puts the equipment at every site onto the cloud, so you can see them from wherever you are — and it works like a duty officer who never takes a break: every day it checks the gear, tells you first when something's wrong, and emails you the report at the end of the month.”

Who buysGuarding companies with many sites, chains, property management. The ones who only discover a recorder is dead by sending someone out feel this most.

Opening question“How do you find out today that recording has failed at one of your sites?”

Nail downHow many NVRs and how many channels each (use the real model: 4 / 8 / 16 / 32 / 64 / 128) · which brands · cloud or not · who should receive the inspection reports

Integration is what we're strongest at

Every “can you connect to this?” gets the same answer. Don't decide in the field that something can't be done.

“Do you support my brand?”

The main brands are already integrated — Dahua, Hikvision, Nx Witness, LILIN. For anything else, the company will handle the integration. All you need to do is bring back the brand and model; you don't have to answer on the spot.

“What if playback can't be reached?”

It isn't that it can't be done — it hasn't been integrated yet. Bring it back and the company will work on it; if it can be integrated, we will. Only truly old equipment with no interface at all leads to the side-recording route, and that's a fallback, not the main approach.

“What if events don't come through?”

Integration first, again. If the device emits events, we integrate them. Old equipment with no software events almost always still has a dry contact, which goes into Smart Gateway and becomes an event that pops on the map. Side recording plus AI is also an option, but it sits behind integration.

Lead with what works, then what needs checking. “You'll see all of your locations; a few of these are older, so let me confirm the best way to connect them” — never open with “that one isn't supported.”
Don't make the call in the field. Whether something can be connected isn't a field decision. Bring the model numbers back and ask.

Two together sell better than one alone

One product solves one pain. Two together is where the customer sees what “the whole picture” is actually worth — and they're far less likely to price it against some single-function box.

Smart Gateway ＋ XMap — the control room for a guarding company

Smart Gateway first, to take in the equipment already installed at each site; then XMap to put it all on one map with event management and dispatch. What used to take a dozen systems to review becomes one screen. This is the easiest pair to sell, because neither one replaces anything the customer owns.

LiveEdge ＋ XMap — mobile and fixed in one place

The point isn't an extra command console, it's integration: the position and live video of a patrolling officer appear on the same map as the fixed cameras from the customer's own VMS. The line that lands: “Wherever the officer goes, the picture goes — on the same screen as my existing cameras.”

All three — the full command centre

The core is XMap ＋ Smart Gateway: Smart Gateway takes in and watches over the mixed equipment on site, XMap provides the map, events and CMS above it, and LiveEdge adds the mobile piece. That's what a large project looks like — but don't lead with the whole suite. Solve one clear pain with XMap ＋ Smart Gateway, get it running, then build upward.

What customers always ask

Answer it this way. Don't improvise on the spot.

“Do I have to replace my current system?”

No. This is the biggest difference between us and everyone else — every device and VMS the customer has already bought stays and we connect to it. What they've spent doesn't become a sunk cost. Finish that point before moving on to anything else.

“My equipment is old and the brands are all over the place. Can you connect to it?”

The main brands are already integrated, and the company will integrate the rest. Bring back the brands and model numbers. Don't say no in the field, and don't promise a timeline in the field either.

“Cloud or my own server room?”

All three work: fully on-premise, fully cloud, or hybrid — the command centre (Nexus) in the cloud and the video kept in the customer's server room on Vault, with Nexus reading recordings back from Vault. When a customer is torn, ask whether they want to run and back up the servers themselves; the answer sorts itself out.

“Isn't the cloud more expensive than on-premise?”

In year one the gap is small, and the customer doesn't have to stand up servers, configure the network or run backups. Make that point first — lead with a monthly per-device figure and all they'll do is multiply it by their device count.

“What does it cost?”

Pricing comes through your sales contact; don't quote in the field. What you bring back is the requirement and the equipment list, not a price negotiation.

Three things that are easy to get wrong

Never say “that device isn't supported.” Integration is handled back at the company — get the brand and model first.
Don't describe hybrid as “the video goes to the cloud too.” With the command centre in the cloud, video still lives on Vault in the customer's server room; Nexus only reads it back.
Never commit to an integration timeline or a price on the spot. Both go back for confirmation; getting either wrong once is hard to recover from.