The entire appeal of a Performance-as-a-Service (PaaS) or Zero CapEx model rests on one promise: The energy savings will pay for the system.

But the most common question from CFOs and finance directors is: "What if the technology fails and the savings don't materialize?"

In a traditional purchase (CapEx), the answer is grim: You lose money. In a true PaaS model, you are protected by a Performance Guarantee.

The Mechanics of the Performance Guarantee

Before a contract is signed, the provider conducts an audit and guarantees a minimum savings threshold (e.g., "We guarantee this system will save RM 10,000 per month").

Because you share a percentage of the actual savings (e.g., you keep 20%, the provider takes 80% to pay off the hardware), your payment is directly tied to the system's performance.

Scenario A: The System Underperforms

If the system only saves RM 6,000 in a month (due to a sensor glitch or hardware issue), the provider's invoice shrinks automatically. You still pay RM 0 out of pocket; the provider simply takes a massive hit to their ROI. The risk is entirely on their balance sheet.

Scenario B: The System Fails Completely

If a severe failure occurs and savings drop to zero, you owe the provider nothing. Furthermore, reputable SLAs include a Penalty Clause. If the provider fails to rectify the issue within a stipulated timeframe, they may be required to compensate you for the lost savings, ensuring they act urgently.

Shifting the Financial Risk

  • Risk of Hardware Failure: CapEx (Owner pays to fix) vs. PaaS (Provider fixes for free)
  • Risk of Lower Savings: CapEx (Owner's ROI is destroyed) vs. PaaS (Provider absorbs the financial loss)
  • Incentive to Fix Fast: CapEx (Low, contractor already got paid) vs. PaaS (Extremely High, provider loses money every hour the system is down)

FAQ: Frequently Asked Questions

Q: Can the provider blame us for the low savings? A: The IPMVP (International Performance Measurement and Verification Protocol) is used to prevent disputes. If your building's occupancy changes dramatically (e.g., a factory adds a night shift), the baseline is mathematically adjusted according to pre-agreed formulas to ensure fairness for both parties.

Q: Have there been cases where the savings were zero? A: With mature AIoT radar technology, it is virtually impossible for savings to hit zero unless the hardware is physically destroyed. Even a basic radar tube defaulting to 2W standby creates massive savings over a 36W fluorescent tube.