Skip to content

WestPoint · Video software · Salient CompleteView

It records well, it does not tie you to one camera and it stops there.

CompleteView is the video software from Salient Systems, and it does not do a single showy thing. It records, it is easy to manage, it works with any make of camera and the cost per channel comes out contained. In the table it appears with no surname and that is exact. For some installations it is just what was needed; it is worth knowing which ones.

What it is, and what kind of installation it was made for.

The scenario: a town council, a network of schools, a medium-sized industrial group. Between a hundred and fifty and six hundred cameras spread over twenty or forty sites, one or two IT people, and no control room with shifts.

What that installation needs can be written in five lines: that everything records, that the retention is the one that was promised, that any of the forty sites opens from one client, that you know the same day when a camera stops recording, and that exporting for a police report is three clicks and a file that opens in court.

That is what CompleteView does, and not much more. And «not much more» is a feature when the alternative is a platform of which a fifth is going to be used: what is not there does not get configured wrong, does not get updated at the wrong moment and does not get paid for.

It does not make cameras, so it pushes none: a long device list, ONVIF for the rest, and the freedom to put at each point the camera that point asks for. In a public installation that buys by tender every two years, that is not ideology: it is being able to buy.

How it is built.

Simple on purpose, with two pieces that decide whether a forty-site installation ages well or badly.

  • Recording servers on Windows, either as software on your own hardware or as the manufacturer's own boxes with everything inside. The closed-box route is shorter to commission and more rigid to extend; it is chosen at the start and according to who is going to maintain it.
  • One client that sees many servers and many sites from one place, with the users and the permissions managed above. That is not the kind of federation a specification with an audit trail asks for, and it has to be said; for forty medium-sized sites it is exactly what is needed.
  • The health watch over the whole thing: which server, which camera and which drive is wrong. In a single-building installation this is a luxury; in a forty-site one it is the piece that justifies the purchase, because the real problem in those installations is not the image quality, it is that nobody knows school seven stopped recording in March.
  • Recording on local drives, NAS or an array, with rules by timetable and by event to stretch the retention. Fault tolerance and recording backup are checked against the tier: as in nearly all of them, it may not be adding a licence but changing tier.
  • Web and mobile clients, with the warning that in a spread-out installation is the one that hurts most: what consumes is not recording, it is how many people watch from outside at once. You count it for two years' time, when there are twenty site managers with the app installed.
  • A programming interface and an SDK, and integrations with access control and with third parties whose catalogue is a fraction of the one the open platforms have. Nothing is promised without checking the system, the version and who maintains the connector.

What it does not have, said before the demonstration.

With a platform like this, the honest page is the list of what is missing. And after that, why it is still on the table.

It does not have federation of hundreds of sites with hierarchical administration and certified procedures. It does not have a control-room procedure layer —that is a PSIM and it is another thing—. It does not have a business data layer for crossing the video with a transaction. And its catalogue of third-party integrations is short: if your project rests on connecting five systems from five manufacturers, this is not the conversation.

Nor does it have analytics of its own that justify the purchase. The analytics you are going to have are decided in good measure by the cameras you put in, and that does not change the licence budget: it changes the camera one. It is worth doing that sum before and not after.

And it has the same question as any manufacturer without much local presence, which is a contract question and not a product one: who picks up the phone, in what language and at what hours; how many integrators in your country can take charge of this system if yours disappears; and how you find out that there is a security fix to apply. You ask for it in writing, with names, before signing. And if the answer to the second one is «few», the way to take the weight out of it is documentation that works without us and the administrator passwords in your name from day one.

Why it is still on the table, then. Because a platform that does exactly what that installation needs, at a price per channel that leaves money for cameras and for drives —which is where the image comes from—, is a perfectly defensible decision. The platform that does everything is one too. The one that fails is the one chosen for the data sheet and not for the installation, and that happens in both directions.

The licence, and what arrives in year three.

Per channel, with tiers above where the high functions live: recording backup, fault tolerance, some client functions. Choosing a tier is choosing a ceiling, and it is the most expensive decision to undo. And the manufacturer's own boxes come with the software and the licences inside, which changes the sum for a medium-sized installation enough to be worth looking at.

On top goes the annual support and updates plan, which is what gives the right to new versions. Letting it lapse switches nothing off and leaves the system still, with the usual effect: the cameras you buy in three years' time need a driver that comes in new versions. And in a public installation that buys cameras by tender every two years, that is more serious than elsewhere: standing still means not being able to buy whatever comes out of the next tender.

Outside the licence sits what grows on its own: storage, Windows and hardware. And here is the honest warning about this platform: the price per channel makes the comparison look won in the first year. The comparison that matters is at five, with the support plan and the hardware refresh inside, and we do that sum even when it comes out against.

And a line of its own for forty-site installations: keeping forty servers on the same version. It is not licence money, it is hours, and if they are not budgeted they do not get done — and after three years there are four different versions scattered around the province.

Who it fits, and who it does not.

The border is clear, and it lies in whether the installation is going to use what a big platform brings on top.

It fits if…

You have a lot of medium-sized sites and one or two IT people. If what weighs is that everything records and that it shows the same day when something stops recording. If you buy cameras by tender and do not want to tie yourself to one make. And if you would rather put the money into cameras and drives than into platform functions nobody is going to touch.

It does not fit if…

There is a control room with shifts, procedures that have to be followed the same way at four in the morning, or many subsystems from different manufacturers that have to be brought together. If the specification asks for federation with an audit trail. If strong analytics are expected out of the box. Or if your purchasing needs a manufacturer with a lot of demonstrable local presence.

The sum you have to do anyway

The five-year one with everything inside: licences, the support plan, the hardware refresh and the hours of keeping forty servers on the same version. It is the only way to compare this with a platform that costs more per channel, and sometimes the result surprises you in the opposite direction to the one expected.

What we do.

In a spread-out installation, the value is not in building one site: it is in the forty ending up the same and in somebody finding out when one breaks.

  • The sizing written down, site by site: cameras, real resolution and frames, days of retention, drive and line. With the calculation handed over and the assumptions in plain sight, because nearly all the problems in a big video installation are sizing problems and not software ones.
  • The choice of tier and of route —software on your own hardware or the manufacturer's own boxes— justified in writing against a three-year horizon, and the five-year sum with the support plan and the hardware inside.
  • The repeatable installation script: the same naming scheme, the same configuration, the same numbering across the forty sites. In a spread-out installation, a camera name invented by the technician who went that day is one more hour on every incident for eight years.
  • The commissioning of the health watch with a recipient and not just a screen: which email address gets told that school seven stopped recording, who looks at it on Mondays and what gets done. An alert with no owner is a red icon nobody sees.
  • The export properly tested, with the format whoever receives it is going to ask for and checking that it opens on a machine with nothing installed. It is the most used thing in a public installation and the one that never gets tested beforehand.
  • The migration: the previous history does not come across, as with none of them. Running side by side read-only while its retention expires, or exporting what is essential, with its cost in the budget. And the handover tests written beforehand: switch off a server, fill a drive on purpose, open the real number of remote sessions expected and measure.
  • And maintenance with a calendar, which here has one task that is the one that really matters: keeping the forty sites on the same version, with the date of the manufacturer's support plan inside. Plus the documentation: an inventory per site, the naming scheme, a map of licences and tiers, the retention calculation, the export procedure and the administrator passwords in the customer's name.

Who operates it afterwards.

Of these six it is the easiest to leave entirely in the customer's hands, and in an installation with a single administrator that is worth money.

  • IT keeps the servers, the drives, the backups, the accounts, the video network and the updates. They are ordinary Windows servers, so there is nothing to learn that is not known already; and there is one specific task that is not an office task: recording drives fill up and wear out on a different pattern from a management server's, and that gets watched separately.
  • And the task that decides whether this installation ages well: that the forty sites go on the same version. It is boring, nobody asks for it and it is the first thing to be dropped — and it is the reason why after three years an integration stopped working in twelve schools and not in the other twenty-eight.
  • Security keeps the operation: views, searches, alarms, retention by zone and export. And in a town council or a network of schools the export is the important decision: who takes images out, with what authorisation and what gets logged. That is data protection, not IT, and whoever answers for it has to be able to do it without opening a ticket.
  • The split of permissions by site is what gets configured wrong most: giving the head of a school access to their school and to none of the others is done with profiles from day one, because splitting it afterwards with four hundred cameras inside is done by hand.
  • The integrator is left with little installation and a fair amount of continuity: the version campaigns across the forty sites, adding new camera models when a tender comes in, the growth of the storage and the diagnosis when a site stops being visible and it is not clear whether it is the line, the server or the building's network.
  • Short and well-documented training, which is what this platform allows: half a day for whoever watches, searches and exports, with a one-page script for the export; and a technical session with IT on servers, backups, the health watch and what to do when a machine does not come back. In writing, because in a public administration people move jobs.

Analytics: what comes with it, what you add and where the ceiling is.

It is the point where this platform is most modest, and this page says it better than a demonstration.

As standard, motion detection by zones —geometry over pixels that change, and the reason a shift fills up with alerts when the light changes—, plus the collection of the events the cameras generate on their own, search over what is recorded and bookmarks. It solves more than it looks: finding the moment when something changed.

And the consequence that has to be said to your face: the analytics you are going to have are decided by the cameras you buy, not by this software. In an installation that buys by tender, that means the camera specification is where it gets decided whether in two years' time there is counting or there is no counting. That sum is done when the specification is written and not when it is installed.

What you add: number plates and third-party analytics by integration, with a bigger warning than with the big open platforms — the one you want may exist or may not, and that gets checked before putting it in a quotation.

The ceiling, with no going round it: if what you need is to understand what is happening in the scene, this platform on its own is not where you are going to find it. It is a video management system and at that it is solid and sober. The understanding has to be brought in from outside.

And here comes the disclosure, because what follows is a recommendation with an interested party in it: in the same house there is IRIS Neural, the NVMS from Infinity Neural, the other company in the group. It is our own product, we make it, and saying so is the only way for everything above to still be worth something.

They live together, and the split is one of the most natural: CompleteView governs cameras, recording, retention, permissions and the health of the forty sites, which is what the customer needs and has already paid for; IRIS brings the understanding of the scene where it is needed, which is almost never the forty sites but three or four specific points. That is also cheaper than changing platform.

And the closing line, which holds for all twenty: if what is needed is what this software already does —record well, find fast and export with no argument—, this software is enough and there is nothing else to buy. We say it anyway.

What IRIS Neural is

Get started

How many sites, and who maintains them?

Tell us how many sites there are and what sizes, how many cameras and what makes, how many days have to be kept and how many IT people you have. With that we tell you whether this platform is the one you need, which tier, and the five-year sum with the support plan and the hardware refresh inside. If what you need is a bigger platform, we will tell you so with the number in front of you.