Intelligent video analytics
For the cameras you already have
Most organisations own cameras that record and nothing else. Intelligent video analytics reads the footage as it happens: somebody has fallen, a door was forced after hours, four hundred people came through the entrance this morning. Ericom supplies it, integrates it and runs it onshore.
What it watches for
One platform, three groups of capability. Most customers start with the group where they already feel the problem and add the others once the video is earning.
-
Security
Protecting people, assets and places, and catching an incident while it is happening rather than finding it on a recording afterwards.
- Intrusion and after-hours detection
- Asset and infrastructure protection
- Incident detection and response
- Access control
-
Safety
The wellbeing of the people in and around a site, including the ones nobody is watching at the time.
- Person down and fall detection
- Child protection and supervision
- Public safety monitoring
- Weapons and duress detection
-
Operational efficiency
Turning video into operational data, and into hours somebody no longer spends watching or searching it.
- People counting and occupancy
- Rapid forensic search
- Process and compliance verification
- Flow and utilisation analytics
Recording is not the same as knowing
Most camera environments were bought to answer questions after something happened, and that is all they do. Nobody watches the feeds, because nobody can. The footage gets opened when there is an incident, someone spends an afternoon scrubbing through it, and the storage bill arrives every month whether anything is learnt from it or not. Meanwhile the things a camera could have told you at the time, that a door was open, that somebody was on the floor, that the queue has not moved in ten minutes, went unsaid.
The equipment is rarely the problem. Nothing is reading the video.
What Ericom adds
The platforms are available to anyone. The difference is which one gets chosen, how it is put together, and who is accountable for it in year three.
Leads with
One accountable party
Cameras, infrastructure, software and analytics supplied as one solution rather than assembled from four suppliers who each blame the others. We select it, integrate it, and operate it.
-
Not tied to one vendor
The platform is chosen per site against what that site needs. Every vendor in the stack earns a specific job, and none of them is the answer to everything.
-
Onshore, your infrastructure or ours
Data residency is a decision made at design and written down. On premise, hybrid or cloud, depending on what you are obliged to do and what it costs.
-
Privacy and compliance built in
Delivered with a specialist privacy partner at the design stage. On camera projects this is the thing that stalls deployments, so it is handled before it becomes an objection.
-
Installed and maintained locally
Local partners do the physical work, so a failed camera is a visit rather than a freight arrangement.
-
Someone owns the outcome
Supplied, installed, managed, monitored, and reviewed against what it was bought to deliver. Most camera projects fail quietly at that last step.
You set the policy. We build to it.
Video is the most sensitive data most organisations hold and the easiest to collect more of than anyone intended. Ericom does not decide what you monitor, who can see it, or how long it is kept. Those are your decisions and your accountability. Our job is to make them decisions that were taken deliberately and written down, and to build a deployment that does what the policy says it does.
The platform
- Milestone
- On-premise core video management, for enterprise environments.
- Genetec
- The cloud and hybrid platform we lead with. Onshore data residency, and the deeper workflows where footage is shared with other agencies.
- iPro
- Cameras and the analytics layer, across every platform. Detection runs at the edge.
- Verkada
- All-in-one cloud, for a smaller site that wants one box and one bill.
- NX Witness
- Retained for edge deployments where a full platform is more than the site needs.
- Wasabi
- Surveillance cloud storage, where server and storage cost is the pressure rather than the cameras.
- Privacy and compliance
- Delivered with a specialist privacy partner, across every platform.
What this is, and what it is not
Video projects get bought under scrutiny, so it is worth being exact about the edges before somebody else draws them.
What it does
-
The whole solution
Cameras, infrastructure, platform and analytics, supplied and integrated as one thing with one party accountable for it working.
-
Works at one camera
A single entrance counted, or one bridge watched for flooding, is a complete deployment and not a pilot you have to grow out of.
-
Runs where you need it
On premise, hybrid or cloud, onshore, on your infrastructure or ours. Decided at design against your obligations rather than our convenience.
-
Stays after go-live
Monitored, maintained and reviewed against the outcome it was bought for. The service is the product.
What it does not do
-
Not a camera refresh
New hardware changes what you own, not what you know. If cameras need replacing, that is one line item inside a larger job.
-
Not one vendor's product
It is not a single platform sold under our name. That is a different purchase, with a different cost to leave.
-
Not our decision what you monitor
We do not set your surveillance policy, choose what is watched, or decide retention. We build to the policy, and we will say so when the policy is unclear.
-
Not our analytics
The detection models come from the camera and platform vendors. What Ericom does is choose the right ones, make them work together, and operate them. We would rather say that than imply we built them.
Where it is deployed
The capability is the same in each. What changes is the problem, the person who owns it, and the obligations attached to the footage.
-
Local government
Councils and the communities they serve. Public space, infrastructure and assets, and the movement data that evidences a place investment or a grant. Delivered as CivicVision.
-
Commercial real environment and strata
Incident review across a portfolio rather than a building, and tying an event to a tenancy without an afternoon of scrubbing through footage.
-
Childcare and early learning
Supervision and child protection, with access and retention governed tightly enough to satisfy a regulator and a parent asking the same question.
Where this usually starts
A conversation first, and what it turns up decides which of these makes sense. There is no fixed order.
-
A review of the cameras you have
For anyone who already owns cameras. What is actually working, what the storage and server footprint costs, and which of the capabilities above your existing hardware could already deliver.
-
A privacy and compliance review
For sites where the obstacle is not the technology but whether a deployment can be defended. Worth doing on its own, and it usually has to happen before anything else can.
-
A scoped proof of value
One entrance, one yard, one named problem. The right choice when the question is whether the analytics tell you anything you did not already know.
Common questions
Short answers first.
Is this just CCTV with a new name?
No, and the difference is commercial rather than semantic. CCTV records so footage exists if something happens. This produces data continuously whether or not anything happens: counts, detections, alerts. The cameras may well be the same hardware. What comes out of them is not the same thing.
Whose AI is it?
The camera and platform vendors'. Detection models are built by the people who build the cameras and the video platforms, and a great deal of the work happens on the camera itself. Ericom does not write them and does not claim to. What we do is choose which combination fits a site, make them work together, and run them, which is the part that usually determines whether any of it delivers.
Do we have to replace our cameras?
Usually not all of them. The first step is establishing what is working and what your existing hardware can already support. Replacement is an outcome of that review rather than an assumption going into it.
Can we start with one camera?
Yes, and it is often the sensible way in. A single camera acting as a sensor for one specific purpose is a complete deployment. Scale is something the result makes available, not a condition of starting.
Where do the footage and the data live?
Onshore, and where exactly is your decision. On your own infrastructure, cloud or private cloud, or hosted by Ericom. Residency is settled at design and written into the deployment rather than discovered later.
Who can see it?
Whoever your policy says, and the platform is configured to enforce that rather than rely on it. Where footage is shared with another organisation, access is controlled and the trail is recorded, so who saw what and when is a matter of record.
How is privacy handled?
As part of the design, with a specialist privacy partner. We do not set your policy on what is monitored or how long it is kept, but we will not build something you cannot explain to the people it watches.
Start with a conversation about the environment
An hour, no obligation, and an honest read on whether your existing cameras can already tell you something useful. If they cannot, we will say that too.
Book a discovery session