Here the question is not whether it fits. It is whether you have it already.

It is not the manufacturer you choose for a forty-camera recorder. It is the one already inside the house when the house is a large hospital, a bank, a public administration or an industry with its own data centre: enterprise storage, systems for a lot of volume, long-term archiving and a department that has been working with it for years.

That changes the starting point. Everywhere else on this list the question is what to buy; here the question is almost always whether the video can live inside what already exists, how much of it it can use and at what internal price. Those are decisions taken with the client's storage team in the room, not in a security quotation.

And there is one area where this kind of house has something the others do not: tape archiving. Tape is no use for recording, because video is written non-stop and consulted at any moment, but it is very good for what has to be kept for years and almost never looked at: open case files, incidents with legal consequences, whatever a contract obliges you to keep.

On the second floor of the storage, not the first. The video of the last few days has to be on drives near the recorder, because it is written at all hours and consulted all at once. What is kept beyond that —by regulation, by contract or because of a case file— can go to enterprise storage or to an archive, and that is where this fits.

It also fits when there are many sites and a written retention policy, of the kind: thirty days at each site, and whatever is flagged as relevant goes up to the central archive and is kept five years. That is not a camera problem: it is a data management problem, and it is the natural conversation for this kind of manufacturer.

And it fits when the client already has it, which is the most frequent reason and the most sensible one. If there is a team that knows how to operate that array, has its contract and its backup procedure, putting the video inside what already works usually turns out better than raising a parallel storage that only the installer understands.

Video writes without a break and almost always sequentially. A corporate array is usually sized for something else: many small, scattered requests from databases and virtual machines. Putting thirty cameras writing at all hours into that place may cause no trouble at all, or it may disturb what was already living there. You measure beforehand, with the real bit rate, and you agree it with whoever administers the array.

Then there is the path. If the recording travels over the company's general network to the storage, that bit rate has to be counted for what it is: constant, not in bursts. And you have to decide what happens if that path is cut: the recorder needs enough local drive space to carry on recording on its own for a few hours, or you lose them.

And there is retention, which is what you are really buying here: retaining is not keeping. Retaining means somebody can prove in two years' time that this recording is the one from that day and that nobody has changed it. That is decided at the design stage, not when the request arrives.

In a medium-sized installation, no. Forty, sixty or eighty cameras across one or two sites are solved with servers and storage of another scale, and doing it that way is not settling for less: it is not paying for a data management capability nobody is going to use. Enterprise storage without a team to operate it is expensive twice over.

Nor would we fit it as the direct destination of the live recording if the path to it depends on the general network and nobody has measured it. Video does not forgive a tight path: it does not give you an error, it gives you gaps in the recording that nobody connects with the network.

And we would not fit it just because the brand inspires confidence. If the decision is to take the video to the corporate storage, there has to be somebody responsible for that storage who says yes, with an allocation and a procedure. Without that, what you have is a dependency with no owner.

Storage of this class is operated by the department that already operates it. It would make no sense for a security company to administer a hospital's corporate array, and we do not ask to. What is needed is for the video to go in there under the same rules as everything else: its allocation, its monitoring, its alerts and its place in the recovery plan.

The boundary is clear and worth writing down: from the camera to the recorder, and from the recorder to the place where the data is left, us. From there inwards —capacity, backups, replication, archiving— the client's team. And one meeting a year to review whether the retention policy is still the one that was written down, because cameras multiply and nobody goes back to look at the period.

What does have to stay in security's hands is who can pull a recording out and with what record kept. The data living in IT does not mean anybody in IT can look at it: that is decided separately and written down.