Building Operations

The operations screen for a building you already model: what is tripping right now, and what tripped overnight. Drop an IFC and click Derive zones — every IFCSPACE becomes a named, translucent volume that colours itself from one sensor path, so readings bind to rooms instead of to whichever wall mesh happens to enclose them. Connect feeds and threshold rules, and the alarm list becomes the primary surface: an entry stays until it is both cleared and acknowledged, so a trip that self-recovered while nobody was watching is still there in the morning. Extends the AEC twin, so datasource feeds, bindings, telemetry widgets, the timeline clock and discipline filters all come with it. A studio building block — compose it with your own model and sensor paths, then publish or embed. Serves facilities and energy operations, and is the seed of a data-centre DCIM plate. The spaces print as a PDF schedule — volume, sensor path and colour band per space, plus the IFC element each was derived from — which is the operations handover document, and the live readings deliberately stay off it because they are never persisted.