How Installers Offer CCTV Monitoring: Graded Centre or Software Layer

Monitoring is what turns project income into monthly recurring revenue, which is why nearly every installer looks at it eventually. The question is not whether to offer it but how to deliver it. This guide is about the delivery model. For the pricing structure and the revenue arithmetic, see how CCTV installers build recurring revenue in 2026, and for the buyer-side comparison of the monitoring models, see back to base monitoring vs AI CCTV monitoring.

Before you start: the compliance picture

Australian security licensing is regulated at the state and territory level, and the rules differ depending on what you actually do. Both paths sit inside that framework. A graded control room performs a licensable activity and is certified to standards for it. A software verification layer filters and verifies camera events; it does not perform graded operator dispatch and it does not remove any licence you would otherwise need. Where an incident requires physical attendance, that comes from appropriately licensed responders: your own keyholders, a patrol company, or a graded alarm receiving centre you escalate to.

Two practical consequences. Confirm your state licensing requirements for the activities you intend to perform before you sell anything. And be precise with customers about the difference between automated notification and certified dispatch, because that distinction is what they are actually choosing between.

Path 1: a graded monitoring centre

The established route. Signals from the site reach a control room graded under standards such as AS/NZS 2201.2, where a licensed operator verifies them and works the response plan. Installers reach this path in one of two ways: by building a centre, which very few do, or by partnering with an existing one under a wholesale agreement, which is how most of the market operates.

What the graded path requires

• Continuous staffing. Around the clock rosters, trained and licensed operators, and cover for leave and turnover.
• Certified infrastructure. Redundant power and communications, physical security of the control room, and a monitored signalling path to every site.
• Audited process. Documented procedures, retained records and periodic audit against the standard.
• A dispatch relationship. Patrol contractors or in-house guards who actually attend, with agreed response times.
• Capital and time. Building a centre is a capital project measured in years. Partnering with one is a commercial agreement measured in weeks.

When the graded path is the right answer

Whenever a contract, tender, lease or insurance schedule names graded monitoring, this path is the answer and the decision is already made for you. It is also the right call where a customer needs a guaranteed physical attendance, where police response may form part of the plan, and where the site is a full alarm system with panels, sensors and duress rather than a camera network. A graded centre is a serious operational commitment and it is what customers with those requirements are correctly buying.

Path 2: a software verification layer

The newer route. Software sits over the cameras already on site, analyses still images captured on motion, classifies what is in them, and raises an automated call, SMS or email on a verified person or vehicle. There are no human operators on the software vendor's side, which is what keeps the cost structure flat and what defines the limits of what it can promise.

What the software path requires

• Supported cameras or an NVR. Vael works with most IP cameras and NVRs via standard image upload (SFTP or FTP), including major brands such as Hikvision, Dahua, Axis, Bosch, Hanwha Vision, Uniview, Honeywell, Avigilon and Pelco. No proprietary hardware swap is needed.
• An upload path from the site. Images on motion are forwarded from the customer's NVR to Vael's Australian coordinating infrastructure over a standard image upload.
• Rules and schedules per camera. Detection rules tuned per camera, including a confirmed-only mode that escalates only when a definite person is detected, and monitoring windows. The default schedule runs 18:00 to 06:00 when none is configured.
• A written escalation path. Who is called, in what order, and when it rolls to a patrol company or a graded centre.
• A licensing check. Operating an automated monitoring service can itself be a licensable security activity in some states and territories.

What the software layer does not include

Being explicit here protects the sale. The layer does not include human operators, graded operator dispatch, or any guaranteed physical attendance. Alerts are automated and go to the contacts you nominate. If somebody needs to turn up, that comes from your escalation path. Selling it as anything more creates a gap between what the customer thinks they bought and what happens at three in the morning.

When the software path is the right answer

It fits unattended yards and depots that have cameras and no panel, sites where false alarm volume is the actual cost problem, and customers who want to know within seconds that a person is on site out of hours. It also fits in front of a graded centre, pre-screening events so that operators see fewer routine ones. Detection covers three products: Security Monitoring, Fire and Smoke Detection and Gate Watching.

Comparing the two paths

Setting up the software layer

If the software path is the one you are adding, the sequence is short.

1. Define the service and the target sites. Construction, plant and equipment yards, contractor depots, warehousing, retail. Match the model to the risk at each one, and write down what "a response" means for every tier you sell.
2. Connect the cameras. Point the site's NVR at Vael over standard image upload (SFTP or FTP). You work with the cameras already on site or the ones you are installing.
3. Configure detection. Rules per camera, confirmed-only mode where you want fewer and stronger alerts, and a schedule per site.
4. Set the alert workflow. Decide which channel reaches which contact in which window. Vael delivers automated phone calls, SMS and email with a first alert within seconds of detection (detection-to-first-alert, subject to network conditions), around the clock (subject to system availability), with the option to attach the triggering image.
5. Define escalation. Name who is called, in what order, and when it rolls to a patrol company or a graded centre. This is where licensed responders take over.
6. Price and brand it. Wholesale is quoted per site and you set the retail price, keeping the spread as recurring revenue. Present alerts and reports under your own name. The arithmetic is worked through in the recurring revenue guide.

What Vael handles and what you handle

Choosing between them, site by site

Treat this as a decision per site rather than one you make once for the whole business. The sequence is the same each time.

1. Read the contract and the insurance schedule first. If either names graded monitoring, the graded path is the answer and everything else is designed around it.
2. Ask what has to happen at 2am. If the answer is that somebody must attend within a set time, you need a dispatch relationship. If the answer is that the right person must know immediately, verified notification does the job.
3. Look at where the false alarms are landing. A site generating repeat attendances for wildlife or weather is a candidate for verification in front of whatever it already uses.
4. Check what the site actually has. Panels and sensors point to the graded path. Cameras and no panel point to the software path.

Common mistakes to avoid

• Overpromising guaranteed dispatch. Automated alerting is a different commitment from graded operator response. If a graded centre is not in the chain, do not describe it as though one is.
• Skipping the escalation path. A verified intrusion needs a defined next step. Decide it before you sell, not after the first incident.
• Treating monitoring as an upsell. It is the recurring revenue engine. Quote it as a standard line on every job.
• Talking down the graded path. Plenty of your customers need it, and the ones who do will notice if you argue against what their insurer requires.
• Ignoring data residency. Vael's coordinating infrastructure runs on Australian infrastructure, but default AI analysis is performed off-shore. Where a customer requires processing to stay in Australia, ask about the fully-onshore private inference option.