Who Should Commission, Own, and Receive Data From Shared vs. Private Building Systems?

Imagine a three‑story block where each floor houses a different business – a boutique café, a design studio, and a legal office. The lobby, elevator, fire‑alarm panel, and main‑line internet conduit run through the core and are used by everyone. Inside each suite there are separate lighting circuits, desk‑mounted cameras, and a private HVAC controller.

Shared infrastructure – The building owner (or a jointly‑appointed facilities manager) should commission the equipment, retain legal ownership, and collect all operational data. This arrangement keeps maintenance contracts simple, ensures compliance with fire‑code and insurance requirements, and prevents data‑privacy disputes because the data never leaves the common‑area network. Tenants receive only the service they need – for example, a notification that the elevator is out of service – without accessing the raw sensor logs.

Private‑area equipment – Each tenant should handle the purchase, installation, and commissioning of devices that stay inside their rented space. Ownership stays with the tenant, and the data stream is routed to their own dashboard or building‑management account. This gives the tenant full control over privacy settings, integration with their internal IT, and the ability to replace or upgrade without involving the landlord.

Conditional decision – If a device (e.g., a smart thermostat) straddles a boundary – it controls a shared HVAC plant but also provides individual zone data – the default is to let the landlord own the hardware and publish aggregated performance metrics, while each tenant signs a data‑sharing add‑on that grants them access to their own zone’s temperature history.

Alternative approach – The three businesses can form a small joint‑venture to fund a common‑area management platform. In that model the platform is owned collectively, each member contributes a proportionate share of the subscription, and data access rights are defined in a simple memorandum rather than a formal contract. This can reduce duplication if all tenants want the same analytics (e.g., energy‑use trends) while still preserving privacy for their internal systems.

The key is to map every piece of hardware to a physical zone, then ask: Does the device serve a shared function, or is it confined to a single tenant’s space? That question tells you who should pay, who should own, and who should receive the data.