Questions building committees ask.

Someone attends the building and records what is installed, where, and what condition it is in. That means opening riser cupboards and the head end rather than walking the lobby. The output is a written as-found record: a device schedule, the cabling type and route so far as it is accessible, what is already faulty, the retention settings as found, and what documentation the building holds. Everything afterwards — the scope, the price, the exclusions — is built on that record, which is why it comes first.

No. Working out what is wrong is part of the job. It does help to arrive with the pattern written down: which units are affected by number, which entrance or camera, when it started, whether it is constant or intermittent, and what has already been replaced. That pattern usually identifies which layer of the system the fault sits in before anyone opens a panel, which shortens the visit and lowers what it costs to find out.

No. The register records where work has been done; it is not a limit on where it can be. A building not on the list is treated exactly the same way: a survey, an as-found record, and a scope built from what is actually there rather than from an assumption. What the register is useful for is recognition — if a tower of similar age, height and layout is on it, the questions your building is about to ask are familiar ones.

That conversation starts with an as-found survey, because nobody can responsibly price responsibility for equipment they have not seen. The survey establishes what is installed, its condition, what already does not work, and whether the building actually holds administrative access to its own systems. Only then can a scope and a price be set, and only then can the exclusions be honest. What that survey finds at a particular building is not something anyone can answer from a desk.

Six things, all in writing: scheduled attendance, with the frequency and what is inspected and tested at each visit; reactive attendance, with how a fault is raised and what happens next; parts, split into included and charged; exclusions, named rather than implied; reporting, so the committee receives a record after each visit; and term and notice, including what is handed back at the end. A proposal detailed on the first and silent on the rest is the common shape, and the reactive half is the half a building relies on.

Because two proposals can look almost identical on what they include and be very different agreements. The common exclusions are legitimate — damage by other trades in shared risers, storm and lightning, reconfiguration by third parties, civil and builder's work. The problem is not that they exist. It is that a proposal listing none has not removed the risk, only declined to say where it sits, and the argument then happens later under worse conditions.

As-built drawings showing device positions and cable routes, a device schedule, configuration records including retention settings, administrative credentials held by the building rather than by a contractor, licence records for any software the system depends on, and a service history. Most buildings hold a warranty card and an invoice. Credentials are the item that most often strands a building: a system whose administrator password is held only by a contractor no longer engaged is not a system the building controls.

It describes the outcome and the conditions, not part numbers. State coverage by area and say whether the requirement is to observe that something happened or to identify who did it — they are different camera counts and different budgets. State retention in days. State what existing infrastructure is to be reused or replaced, the working hours, making good, testing and acceptance, and what documentation is handed over. A scope written from one vendor's model numbers ensures the other quotations are either non-compliant or a copy.

Not by the totals. Build one table of everything any proposal mentions and mark each proposal against every row, including the rows it is silent on — silence is information. Then add an exclusions column and a line for what the building would have to buy separately to make each proposal complete. Compare capability rather than brand, and price the second year as well as the first, because warranty and maintenance terms differ more than the equipment does.

Usually, but the stages have to be engineered rather than chopped by budget. The sequence that works is infrastructure first: cabling and containment, then head end, then devices. Done in the other order the building pays for the same riser access twice, because new devices get installed onto cabling that is replaced beneath them a year later. Ask for the whole programme to be priced with the stages shown separately, and for the scope to state what happens if a later stage is deferred.

Under Malaysian strata practice the maintenance account covers day-to-day upkeep and the sinking fund is the reserve for major, infrequent capital expenditure. Scheduled servicing and repairs to a working system usually fall in the first; end-of-life replacement and extending coverage to areas never covered usually fall in the second. The genuinely unclear cases are decisions for the committee with its managing agent. What a contractor can do is price the elements separately so the allocation can be made properly.

What is failing and the evidence for it, not an assertion. What options were considered — repair, partial replacement, full replacement — and why the recommendation won. What happens if nothing is done, stated plainly. The normalised comparison table with exclusions shown. The fund and the reasoning for drawing on it. And what the building will hold afterwards: drawings, credentials, a service arrangement. That last line is the one committees omit and owners appreciate most.

Extra Low Voltage: the building systems that carry signal rather than mains power. In a high-rise that is CCTV, access control, intercom, alarm handling and perimeter intrusion, pedestrian and vehicle access, guard tour, key management, and the structured networking underneath all of it, watched from a security control room. It is a trade category rather than a marketing one, which is why buildings usually meet the term in a tender document and nowhere else.

For an existing condominium the cabling in the riser usually decides it rather than the cameras. Sound coaxial cable throughout and a requirement for better images: a modern analogue standard over the existing cable is often the best value in the building. Coax at end of life, or absent where new coverage is needed: the cabling is being replaced anyway, so structured cabling and IP makes sense. Storage is the line most often under-specified, because raising resolution while holding retention constant raises it too.

Because the faults that matter in a high-rise live in the shared layer — the cabling, the risers and the power that every system depends on. With four contractors, each can demonstrate their own equipment is fine and the building is left holding a fault with no owner, plus a bill for each attendance that established nothing. The building should still hold its own credentials and documentation, so that a single arrangement stays voluntary rather than becoming dependence.

The company was established in 2010, having previously traded as Occhio Technology, a sole proprietorship. It is an Extra Low Voltage contractor based at Menara 1 Mont Kiara in Kuala Lumpur, and its published niche is the mid high to high end condominium market, where much of its work is service and maintenance. Twenty-nine buildings are named on its register, concentrated in Mont Kiara, Bangsar and KLCC.

Four have been published, each with the year it was granted where the source gives one. MicroEngine appointed Occhio Tec an Authorised System Installer in 2014. Panasonic Malaysia named it an Authorised Strategic Partner for ELV works in 2015. Astro offered Authorised Reseller status for IPTV and broadband in 2016. A fibre optics distributor appointment is recorded on the company’s own material as “TT Dotcom” and carries no year. Whether each is still current in 2026 is not something this site states, because the company has not published it. Separately, in 2015 Panasonic gave a global Best Seller Award for video intercom in the apartment market, presented by Mr Minami, Director of AVC Network.

That is not published, and deliberately so. The register names the buildings and records nothing else — no system, no date, no scope and no value against any one of them — because those details belong to the buildings and their management committees rather than to a contractor's website. If you need a reference for a specific kind of work, ask directly and it can be discussed with the building's permission rather than published.