Takeover and maintenance of an existing system.
Most buildings are not buying an installation. They already have one, and what they need is somebody to be responsible for it. That is a different transaction, and it starts in a different place.
QUESTION ANSWEREDWhat has to be recorded before a contractor can take responsibility for a system it did not install?
Taking over an existing building security system means one contractor becoming responsible for equipment they did not install. It begins with an as-found survey that records what is present, what works and what does not, because the scope and the price both depend on that record. Without it, a maintenance agreement is a guess written down.
Why most buildings are buying a takeover
A new tower gets its security systems from whoever the developer appointed. A few years later the building is running itself, the original contractor has moved on or been let go, and the management committee discovers that nobody is actually responsible for the intercom. Nothing has been installed wrongly. There is simply no arrangement.
This is the ordinary condition of most established buildings, and it is why the useful question is rarely “what would a new system cost”. It is “will somebody look after the one we have, and on what terms”. Very little has been written about how that actually works, which is why committees so often end up comparing three maintenance prices with no idea what any of them covers.
No arrangement is not the same as no duty. The by-laws in the Third Schedule to the 2015 Regulations apply to a joint management body as much as to a management corporation, and the first function they give the management body is this one:
maintain in a state of good and serviceable repair, and, where necessary, renew or upgrade, the fixtures and fittings, lifts, installations, equipment, devices and appliances existing in the development area and used or capable of being used or enjoyed by occupiers of two or more parcels
The by-law names no system and prescribes no contract. It puts the duty on the management body itself, so a committee with nobody responsible for the intercom is carrying that duty on its own. What an agreement has to say before it is worth signing is set out in what a maintenance contract should cover.
The as-found survey comes first
No contractor can honestly price responsibility for equipment they have never seen. The first step in any takeover is a survey that records what is actually installed, what condition it is in, and what still works — the as-found position. Everything after it depends on it: the scope, the price, the exclusions, and the argument you will otherwise have in month four about whether a fault predates the agreement. The step-by-step version is in taking over a system another contractor installed.
- N01Devices, by type, location and countSCHEDULE
- N02Make and model where legibleRECORDED
- N03Cabling type and route, so far as accessibleRECORDED
- N04Head end, controllers and recordersIDENTIFIED
- N05What is already faulty at handoverLISTED
- N06Retention and settings as foundREAD OFF
- N07Documentation held by the buildingLISTED
- N08Administrative access and passwordsTESTED
A survey that produces this is worth paying for even if the building appoints somebody else afterwards. It is the only document that lets three quotations be compared on the same basis.
The documentation a building should hold
Ask a committee for its security system documentation and the usual answer is a folder with a warranty card and an invoice. The list below is what the building ought to have. Where an item is missing, the survey is often the only practical way to reconstruct it.
- As-built drawings showing device positions and cable routes.
- A device schedule — what is installed, where, and when.
- Configuration records for controllers and recorders, including retention settings.
- Administrative credentials, held by the building rather than by a contractor.
- Licence records for any software the system depends on.
- A service history — what has failed, what was done, when.
Credentials are the item that most often strands a building. A system whose administrator password is held only by a contractor who is no longer engaged is not a system the building controls, and recovering it can cost more than the fault that exposed the problem.
For a building that has only recently left the developer’s hands, part of that folder is owed to it by law. Among the documents section 15(3) of the Strata Management Act 2013 requires the developer to deliver to the joint management body are copies of:
all warranties, manuals, schematic drawings, operating instructions, service guides, manufacturer’s documentation and other similar information in respect of the construction, installation, operation, maintenance, repair and servicing of any common property…
The section reaches “any common property” and names no system, so the request has to do the naming — the controllers, the door stations, the recorders. What a joint management body should ask for, and check, in its first months is set out in what a JMB inherits from the developer’s contractor.
What a maintenance agreement should oblige
Most maintenance agreements are specific about attendance and vague about everything else, which is how a building can hold a signed contract and still receive a separate quotation for every real repair. A committee should expect each of the following to be written down.
| Head | What it must actually say |
|---|---|
| Scheduled attendance | How often, which systems, what is inspected and tested at each visit — not simply “periodic servicing”. |
| Reactive attendance | How a fault is raised, what happens next, and whether attendance is included or charged. |
| Parts | What is included, what is charged, and how a price is established for anything not on either list. |
| Exclusions | Named, not implied. Cabling, civil works, storm damage and third-party interference are the usual ones. |
| Reporting | What the committee receives after each visit, and in what form. |
| Term and notice | How long, how it ends, and what is handed back at the end. |
Each of those rows is a clause, and a clause that is present but vague is worth about as much as one that is missing. The version of this table with the failure mode written beside every row — what actually happens when an agreement is silent on it — is in what a maintenance contract should cover.
Two of those heads can be written as a number rather than an adjective, and each has a published figure behind it. On reliability, Singapore’s standard for video surveillance in buildings sets system availability at 95% over a 12-month time frame and asks that faults be rectified within 24 hours; Malaysia publishes no equivalent. On parts, the mechanism worth copying is in a Malaysian public tender: Iskandar Puteri City Council’s CCTV maintenance contract carries spare parts as a provisional sum of RM 50,000, money set aside inside the contract price and drawn down against actual failures rather than argued over after the first one.
Neither figure is a commitment Occhio Tec is making here — the availability a specific building can be held to is an output of the as-found survey, not of a web page. They are useful the other way round: as numbers a committee can put into its own tender, so that every proposal answers the same question.
Why the exclusions matter more than the inclusions
Two maintenance proposals can look almost identical on their inclusions and be very different agreements. The difference is nearly always in what has been left out, and a committee reviewing proposals should read the exclusions first.
The common ones are legitimate. No contractor can carry the risk of cabling damaged by another trade, or of a lightning strike, or of a system being reconfigured by someone else between visits. The problem is not that exclusions exist; it is that a proposal with no exclusions listed has not removed the risk, it has simply not told you where it sits. When the first substantial failure arrives, the argument starts there.
Handover from a previous contractor
Where a building is changing contractors rather than appointing one for the first time, there is a short window in which the outgoing party is still obliged and still reachable. Use it.
- Request the documentation list above in writing, before the final invoice is settled.
- Change every administrative credential to one the building holds.
- Establish what spares exist, and whether they belong to the building or to the contractor.
- Get the outstanding fault list acknowledged by both sides before the incoming contractor takes responsibility.
How to compare maintenance proposals
Because scopes differ, prices are not directly comparable. The practical method is to build a single table of everything any of the proposals mentions, and mark each proposal against it — including the rows it is silent on. Silence is information. The same technique applies to capital works and is set out in specifying and funding the work.
Where this leads
Occhio Tec has worked in high-end condominiums in the Mont Kiara, Bangsar and KLCC areas for service and maintenance, which the company describes as its niche. Occhio Tec was established in 2012. What a takeover would involve at a particular building is not something that can be answered from a desk: it depends on what is installed, what condition it is in, and what documentation survives.
None of that can be settled from a desk. A site survey is what any building needs before it can put the schedule above out to price.