What is already fitted sometimes stays. Pro-Watch talks to it.

It is the head end of a large access control system: the software holding the people, the permissions, the schedules and the log, sitting above the controllers that do the opening. What is unusual is where it comes from. The manufacturer bought up other access control brands over the years and, instead of forcing its clients to throw away what was installed, kept adding the ability to talk to those electronics. The result is a platform that drives its own line of controllers and also a long list of old families.

That puts it in a very particular place in the market: the installation that has been growing in pieces for twenty years. Three buildings, three suppliers, three systems that do not speak to each other, and a board that does not want to spend in one go what it costs to change the lot. Pro-Watch goes on top of that mess and gives you a single list of people and a single log while the field side is renewed.

You find it in corporate buildings, hospitals, industry, infrastructure and public administration, often alongside other systems from the same manufacturer: video, intruder detection and the management of the building itself. That is the other reason it turns up where it turns up.

Windows server, SQL database, installed clients and a web client for day-to-day work, with a card design and printing module inside. It is sold by editions: the same platform with a different reach depending on the size of the installation. That has to be looked at closely when sizing, because the feature somebody takes for granted may live in an edition above the one quoted. It is not a defect, it is how it is sold; the mistake is finding out late.

Its line of controllers belongs to the most widespread family in the upper range, the one several platforms of this class share, and underneath it runs the usual buses out to the reader boards. On top of that come the integration drivers for the old families it carries from its history. And it integrates with the video, the intruder detection and the building management of the same manufacturer, which allows genuinely useful things: the alarm knowing who has just come in on a valid credential, or the lighting and the air on a floor finding out there is nobody there.

On credentials, what you would expect: old card, encrypted card, phone, code and third-party biometrics. And the same decision as everywhere in its class, the reader protocol one: the classic, which cannot be supervised or encrypted, or the modern one, which can. In an installation that keeps old iron, that decision is taken zone by zone, and that is fine as long as it is written down which zones are the weak ones.

Keeping the old electronics saves money today and leaves the system resting on equipment in its last stretch of life: spares are scarce, firmware nobody touches any more, and security features that generation never had. The ceiling of the whole system becomes the ceiling of its oldest component, even if the head end is modern.

Used well, that is exactly what is needed: a two- or three-year plan where the head end is unified on day one and the field side is renewed building by building, with a budget and dates. Used badly, it becomes the excuse never to renew anything, and one day an eighteen-year-old board fails, cannot be replaced, and you have to sort out in a week what could have been planned over three years.

It fits the inherited installation: several different systems, iron from different eras, a need for one single list of people and one single log without stopping work or spending everything in the first year. And it fits buildings already running other systems from the same house, because there the integration is not a promise: it is a road already travelled.

It does not fit as well in a new installation from scratch with nothing to keep. There its great advantage goes unused and the choice is decided by other things: what video there is, what continuity is demanded, what administration model you want, who is going to maintain it. It is not that it is bad on a new build; it is that the main reason for choosing it is not present, and it is worth knowing that instead of inheriting the decision.

The day-to-day is run by the client without difficulty: people, credentials, schedules, permissions by zone, visitors, cards, reports. The web client covers that and can be fenced off by profile, so that HR touches people and security touches access. For most everyday tasks there is no difference between a new door and an inherited one, and that is exactly what is being bought.

Where there is a difference is in the configuration. The doors on the old electronics have fewer configurable things, and some are configured with tools of their era instead of from the platform. The client should not touch that, and should not discover it alone on a Tuesday afternoon either: it has to be written down which zones are like that and what can be done in each. The structural work —new doors, integrations, versions, emergencies— belongs to whoever maintains the system.

What has to be handed over, besides the model document, the client's own administrator accounts and the training by profile, is the map of the two halves: what is new, what is inherited, what each zone can do and what phase of the plan it is in. It is the most valuable document in this kind of installation and the one nobody hands over. Without it, in two years nobody knows why in building C you cannot do what you do in A, and the answer ends up being «this is very old», which is not an answer.

It is what it does best, with one condition: that the iron already fitted is on the list of what this platform knows how to drive, with the exact model and version. That is checked in the cabinet, not in a catalogue. When it fits, the migration keeps controllers, boards, readers and cabling, and what changes is the head end and the way of working. When it does not fit, at least the cabling and the building work are usually kept, which is not nothing.

Credentials can usually be reused, and here more often than in other migrations because the readers themselves are often kept. The care needed is the usual one with the card number: the format, the site code and the difference between the number printed on the card and the one the system stores. With three old systems living side by side, the normal thing is to find three different formats and the odd collision, and that is resolved before the load.