Video analytics processing dozens of camera feeds, digital-twin computation, and tenant AI services increasingly run in a comms-room-sized micro data centre inside the building itself, rather than a distant cloud region. For Australian precinct masterplans, this means treating on-site compute as a genuine floor-space and services allocation from the start, not an afterthought bolted into whatever spare comms room capacity exists.
Why the Workload Wants to Stay Local
Latency and bandwidth economics, not novelty, drive the shift to in-building compute. A security video analytics platform processing dozens of camera feeds in real time performs far better running on local compute than streaming every camera's raw feed to a distant cloud region and waiting on the round-trip latency for object detection results. The same logic applies to digital-twin processing needing sub-second response to sensor data, and to any AI service where continuity through an internet outage genuinely matters for building operations. Micro data centres sit at the point where the workload's latency and bandwidth requirements outweigh the convenience of pure cloud hosting.
Sizing the Floor-Space Allowance
- A typical in-building micro data centre for a mid-size Australian commercial precinct needs a comms-room-scale footprint — often 15-30 square metres — but this should be sized against the specific compute load rather than a generic allowance, since AI-heavy workloads push rack density well above a conventional comms room's original design intent.
- Rack-level cooling (in-row or rear-door heat exchangers) is more practical than room-level CRAC units at micro data centre scale, and should be coordinated with the base building's chilled water or condenser water availability at design stage.
- Access control for the micro data centre space should match the sensitivity of what it hosts — security video retention and building control data warrant the same access discipline as a larger, purpose-built facility, scaled down but not diluted.
- Dual-feed power and appropriately sized UPS backup should be specified for any micro data centre supporting genuinely critical functions, following the same criticality-tiering logic used for larger mission-critical ELV systems.
Design takeaway: Reserve floor space and services capacity for in-building edge compute at precinct masterplanning stage, sized against actual projected workload rather than a generic comms-room allowance — retrofitting adequate cooling and power into an undersized space after AI-driven demand outgrows it is a costly and disruptive correction.
Governance: Who Runs the Micro Data Centre?
For multi-tenant Australian precincts, deciding who operates the micro data centre — the landlord as base-building infrastructure, a specialist MSI, or a tenant-specific arrangement — needs resolving early, since it affects the access-control model, the service level commitments to different consuming applications, and how costs are apportioned across tenants benefiting from shared compute capacity.
Frequently Asked Questions
Why would a building run its own micro data centre instead of using the cloud?
Latency and bandwidth are the main drivers — video analytics processing dozens of camera feeds, or digital-twin processing needing sub-second response, perform better and cheaper running on local compute than streaming raw data to a distant cloud region and waiting on the round trip, especially where continuity through an internet outage also matters.
How much floor space should a precinct masterplan reserve for a micro data centre?
A typical in-building micro data centre for a mid-size Australian commercial precinct needs roughly a comms-room-sized footprint — often 15-30 square metres — but this should be confirmed against the specific compute load (rack count, cooling requirement) rather than assumed from a generic allowance, since AI-heavy workloads can push density well above a conventional comms room's design.
Does a micro data centre need the same dual-feed power as a full-scale facility?
For any micro data centre supporting genuinely critical functions — security video retention, life-safety-adjacent analytics — dual-feed power and UPS backup should be specified to the same standard as any other critical ELV system in the building, scaled to the smaller load rather than omitted because the facility itself is small.