Taking over another contractor’s system.

Why so many buildings need a takeover, not an installation

Much of the ELV work in an established condominium is not new installation. The systems are already there — put in by the developer's contractor at completion, or by whoever won the last tender — and what the building actually needs is for someone else to look after them from here.

The reasons are ordinary. A maintenance contract ends and is not renewed. The original contractor is no longer trading, or no longer interested in a building of this size. Service quality declines and the committee decides to move. Or the developer's appointed contractor simply stops attending once the defect liability period closes and nobody replaces them.

In each case the building is asking a different question from the one a new installation answers. Not what should we install, but will someone take responsibility for what is already here, and on what terms. The wider position is set out in the guide to takeover and maintenance.

The as-found survey, item by item

The as-found survey is the foundation of everything that follows. It is a record of the position on the day, made before any commitment on either side, and it protects both parties: the building knows what it is asking someone to maintain, and the incoming contractor knows what they are accepting.

The last row is not a formality. A survey that quietly omits a riser it could not open, or a head end nobody had a key for, produces a scope with a hole in it, and that hole becomes a dispute later.

Documentation to ask the outgoing contractor for

There is usually a window around a handover in which documentation can still be obtained, and it closes. It is worth asking for all of it in writing, early, and recording what was and was not provided.

Realistically much of this will not exist. That is a finding rather than a failure. A building starting from nothing is starting a record, not recovering one. What matters is that the gaps are known and written down at the start rather than discovered during an incident.

Passwords, licences and the things that strand a building

The single most disruptive thing a departing contractor can leave behind is a system nobody can administer. Equipment that works perfectly is close to useless if no one can add a card, pull footage, or change a door schedule.

1. Administrative passwords for recorders, controllers, intercom exchanges and management software. Held by the building, not only by the contractor.
2. Software licences registered to the building or the management body rather than to a contractor's account.
3. Proprietary programming tools, and whether operating the system depends on them.
4. Cloud or remote-access accounts, and in whose name they sit.
5. Encoding or credential formats for access cards, without which new cards cannot be issued.

Where these cannot be recovered, the alternatives are a factory reset that loses configuration, or replacing the layer that is locked. Both cost real money and both are far better discovered during a survey than during an incident. A committee is entitled to insist that credentials sit with the building — it is common property, and the management body is accountable for it.

What can be kept, and what usually cannot

A takeover is not a replacement, and a proposal that arrives as a quotation to replace everything has not really surveyed anything. Most of what is in a building can normally stay.

Cabling and containment are almost always retained — they are the expensive, disruptive layer and they outlive the equipment attached to them. Door controllers, readers and locks are usually serviceable. Cameras and recorders are judged individually on condition and support position. What tends not to survive is anything the building cannot administer and anything already failing repeatedly, since accepting maintenance responsibility for either means accepting an open-ended commitment.

Being explicit about the split matters, because it is what makes two proposals comparable at all. Repair or replace sets out how that judgement is made item by item.

How the survey becomes a scope, and the scope a price

The sequence is deliberate, and reversing it is where committees get quotations they cannot compare.

1. The survey establishes what is there and in what condition.
2. The scope states what will be maintained, at what frequency, with what response and what is excluded.
3. The rectification list separates pre-existing faults out of routine maintenance, priced individually.
4. The price follows from the scope, and can be read against it.

A price arrived at without the first two steps is a guess. It is also unarguable, because there is nothing written down to compare it against — which is precisely why quotations for what sounds like the same work can differ so widely. Three proposals built on three unstated scopes are three different jobs.

What a first-year takeover agreement should say

The first year of a takeover is different from a renewal, because neither side began with full knowledge of the installation. A sensible agreement says so.

• The as-found record is attached and forms the baseline.
• Pre-existing faults are listed and excluded from routine maintenance until rectified.
• Scope is stated per system, with frequency, and with exclusions written rather than implied.
• Response expectations are stated, including out of hours.
• Documentation obligations run both ways — what the contractor will produce, and what the building will hold.
• Credentials sit with the building, so the next handover is not another recovery exercise.
• Exit terms say what is handed over at the end, in what form.

That last point is the test of good faith. A contractor content to specify what they will hand over when they leave is a contractor not relying on making departure difficult.

What happens if the survey finds something serious

Occasionally a survey finds a condition that changes the question — cabling that will not support what is attached to it, a head end at the end of its supported life, or a fire-door or life-safety interface not working as it should. It is better for that to surface in a survey than during an incident, and it should be reported plainly even though it complicates the sale.

What follows is a different conversation: a rectification programme with its own funding route, sequenced by urgency, rather than a maintenance contract quietly absorbing a capital problem. Committees are not served by proposals that price around a defect and hope.

Occhio Tec describes its niche as high-end condominiums in the Mont Kiara, Bangsar and KLCC areas for service and maintenance, and lists maintenance and consulting among its fourteen ELV services. What a takeover would involve at a specific building depends entirely on what is installed and what documentation survives, which is what a site survey establishes. Related pieces are collected in Insights.