Home / Blog / Commercial & property
Commercial & property

Smart Building Capex, Opex and Service Charge in Malaysia: Who Actually Pays

Common-area corridor meeting a tenant's fitted-out office suite in a Malaysian commercial building, marking the landlord and tenant boundary

Answer up front — Most commercial smart projects stall at one line: the boundary between what the landlord owns and what the tenant fitted out. The decision sits there, the money sits there, and if the boundary is not written down before the first device goes in, it gets decided by whoever argues hardest. Classify each scope as capital or operating, document the demarcation, and put the responsibility matrix in the lease schedule — not in an email.

The line where smart projects actually die

Most owners will tell you the technical challenges are the hard part. In practice the technical part is usually solvable. What kills commercial smart deployments is a boundary dispute that surfaces three months into the programme, when the vendor is on site, the floor is open, and the argument is about whose money is being spent.

The boundary is straightforward on paper:

  • Landlord-owned — common areas, corridors, lift lobbies, staircases, main entrance, car park and drop-off, plant rooms, the building's own lighting and HVAC in those areas, risers, the incoming supply, the BMS.
  • Tenant-owned — the fit-out: raised floor, partitions, the tenant's own lighting, their own aircon units, their own network equipment, anything they paid for and remove at the end of the lease.

The hard part is not drawing the line. It is that automation decisions keep crossing it, and each crossing is a fresh negotiation.

The crossings that generate the arguments

The riser and the ceiling void. Your main network and the tenant's network are different systems with a demarcation point between them. Where does the smart system sit? If your monitoring platform needs to see a tenant's space state, someone has to agree to expose something. In many Malaysian fit-outs the only practical place for a hub or access point is the ceiling void above the tenant's ceiling tiles — and that void may be landlord structure, tenant structure, or a shared zone depending on the fit-out. Ask, and get the answer in writing.

The reader at the tenant's door. A card reader at a tenant's suite entrance is inside the tenant's demise, and also the only place the building's access control can see that tenant. Whose system is it? Who holds the credential database? Who gets access on the day the lease ends?

The BMS. If the building already has one, every smart control decision becomes a conversation about who is the master system. Two systems both claiming to control the same AHU is a fault waiting for a Tuesday afternoon.

Capital or operating — and why the answer changes the room

A facility manager can approve a maintenance contract. A capital request goes to a board, a committee or a lender, on a different cycle, with a different threshold and a different appetite. The classification is not an accounting detail; it determines who says yes, and how long you wait for it.

The general shape:

Capital expenditureOperating expenditure
Typical triggerNew system, new asset, capacity increase, upgrade that extends useful lifeConsumable, replacement of like-for-like, service contract, subscription, labour to keep it running
Where it landsFixed asset register, depreciated, funded from capital budgetAnnual opex, service charge, budget line
Who approvesBoard, investment committee, asset ownerFacility manager, building manager, within a delegated limit
SpeedMonthsWeeks
Recovery from tenantsUsually amortised into service charge over a term, or capitalised in the leaseDirectly recoverable through the service charge budget, often the same year
Smart building examplesCommon-area control system, access control at main doors, sub-meters, plant room integration, room panels in a fit-out scopeBattery replacement, sensor replacement, annual maintenance visit, firmware labour, subscription fee, spare device stock

Two traps on that table. Treating a whole deployment as one item — a system with capital and operating components should be split at the line, not averaged. And the pure-operating framing: a system installed as operating spend often never reaches the capital register, which means it never reaches the asset register either, and in three years nobody owns it, depreciates it, or replaces it. If your smart system is not on the asset register, it is not an asset.

Service charge treatment and how to word a schedule of works

Service charge is where the tenant conversation happens. Two rules, both about wording.

Rule one: state what is recoverable, from when, and for how long. "Capital works shall be recovered through the service charge over [n] years from [date]" survives a management committee. "Costs may be recovered as and when deemed appropriate" starts an argument in month seven.

Rule two: separate the ongoing service cost from the amortised capital recovery. They are different things with different justifications. A tenant will accept paying for a system that keeps working; a tenant will challenge paying a sinking fund for a system they were told was optional. If you cannot separate them in the schedule, you will be asked to explain them together, and you will lose both.

A schedule of works for a smart building rollout should state, per line item:

  • The scope and location, unambiguously enough to identify it in a corridor
  • Whether it is landlord-funded, tenant-funded, or amortised into service charge
  • The recovery start date and recovery period
  • Who carries the ongoing service and consumables
  • The demarcation point for anything touching tenant space or tenant systems
  • What happens to the asset at the end of the lease term or on sale of the building

That last line is the one that gets missed and the one that causes a valuation problem three years later. A smart system that is demised to a tenant and removed by the tenant at lease end is a depreciating liability in a building the landlord still owns the fabric of.

You may not do what you think you may do

This is the part that turns a technical project into a legal one, and it is worth being blunt.

You may not touch a tenant's equipment without consent, in writing, in advance. Not a sensor on their ceiling, not a relay on their lighting circuit, not a gateway on their network. It is their space, their asset and their risk, and a tenancy that discovers a landlord-installed device after the fact will treat it as a breach of the fit-out schedule. In most cases they will be right.

You may not remove a device a tenant installed without going through the termination provisions of the lease. Fit-out, cabling and equipment at lease end are contractual territory, not an operations decision.

You may not extend the building's network into tenant space without the same consent — and assume the tenant's IT provider will object on security grounds even when they have no commercial objection.

You may not assume the tenant will accept after-hours work. A commissioning window costs the tenant in noise, access and disruption, even when it produces no invoice. Put it in the programme and agree it.

The practical consequence: every smart decision that crosses the boundary needs documented consent before work starts, not notification after. One email, one signature, one line in the schedule. It takes an afternoon and it is the difference between a smooth programme and a dispute.

The responsibility matrix

Write this down before the first device goes in. Every row needs a name against it, not a role.

ItemTypical ownerLandlord or tenant fundedConsent needed before workDocument it as
Common-area lighting control (corridors, lobby, car park)LandlordLandlord, amortised into service chargeNot for the tenant, but notify occupantsSchedule of works + service charge budget
Main entrance access controlLandlordLandlord, capitalNot for tenants, but publish access rulesLease annex / building rules
Tenant suite entrance reader or keypadEither — decideWhichever funds itYes, both waysFit-out schedule amendment
Sub-metering of a tenant wingLandlordLandlord, capitalYes — installation access to tenant spaceSchedule of works + tenancy consent
Metering inside a tenant's own electrical roomTenantTenantYes, both waysTenant's own scope
In-suite lighting automationTenantTenantNot the landlord's decision, but must be declaredFit-out declaration
Tenant's own HVAC automationTenantTenantNot the landlord's decision, but must be declared to the BMS ownerFit-out declaration + BMS interface register
Hub, gateway or network point in a ceiling voidWhoever owns the voidLandlord, usuallyYes, if the void is inside the demiseAs-built drawing and demarcation schedule
Riser cable and main network equipmentLandlordLandlordNot for tenantsAs-built and asset register
Ongoing battery and consumable replacementWhoever owns the deviceOpex, service chargeNoMaintenance budget line
Firmware updates and device re-pairingWhoever holds the accountOpexNo, if the account is landlord-ownedMaintenance SOP
Removal or transfer at lease endWhoever installed itWhoever installed itYes, via lease termsExit condition schedule

Two rows in that table are where disputes actually originate: the ceiling void and the lease-end row. Both are cheap to settle in advance.

Where the boundary document goes

Not in the project folder. In three places: the schedule of works or service charge budget, so the cost recovery is authorised; the lease or fit-out schedule, so the tenant knows what is being done to their space and what happens to it later; and the asset register and as-built set, so a building that is sold, refinanced or handed to a new FM provider in ten years is a building someone can actually operate.

The handover documentation side is in the condo smart home handover specification. The costing frame, and the questions to ask before you fund anything, are in building a smart building business case.

Planning a project?

Tell us about your space. Our B2B team will reply within one business day with a recommended setup and quotation.

WhatsApp us →
[email protected]
+603-5880 5486