Technical systems and calendar: technical schema, floor plan and scheduling

These three views put data where the building actually is: on the schematic, on the plan, and on the clock.

Technical schema

A technical schema is a drawing of an installation with live values placed on it. You add timeseries, KPIs, labels and links onto a background image, so instead of reading a table of sensor names you read the actual system: supply and return, outdoor and room, fan and coil, each showing its current value in position.

Schemas keep an audit trail — creation, background changes, and every added or removed timeseries, KPI, label and link is recorded with who did it. That matters on a schema several people maintain.

Schemas can be copied across sub-buildings, which saves rebuilding the same air handling unit five times, and there is a draft mode so you can work on one without others seeing a half-finished drawing. Timeseries can be renamed directly from the schema screen.

The schema list, with live values shown directly in the table.

A ventilation schema with live values, setpoints and the governing calendar on the drawing itself.

Clicking a value on the schema opens its history without leaving the drawing.

Floor plan

The floor plan does the same for rooms. Drag and drop a sensor onto the plan to place it, then read temperature, CO₂ or humidity where the room actually is — which makes a cold corner or a stuffy meeting room obvious in a way a sorted table is not.

Floor plans support a sub-building filter, a shortcut for changing the room view, and a KPI table view. Selecting a room is also how annotations get their sensor suggestions.

If sensors disappear from a plan, it is usually because a building update changed sensor IDs. Add the sensors again, or contact support with the Feedback button.

A floor plan with room temperatures in place. Switch the rooms view to show CO₂ or humidity instead.

Calendar

The calendar is where scheduling lives. Add events for ventilation and other installations, either once or on a recurring schedule, and view them by plan, week or month. Calendars can be grouped, and you can select or clear several at once when a building has many.

Two behaviours are worth understanding:

• Each setpoint has a default value. The calendar uses that value unless an event overrides it — so an empty calendar is not "no control", it is "default all the time".
  

• Sync pushes calendar changes to and from the selected facilities. Until a sync runs, a change exists in Properate but not yet in the plant.
  

Deleting a calendar group keeps its calendars as individual calendars. A deleted calendar can be added again later from the setpoint.

The building calendar. Choose which calendars to show on the right, and use Run sync to push changes to the installation.

Good to know

• Setpoints only appear as controllable where the timeseries is marked writable.
  

• Cloud automations attached to a schema show up in the FDV overview under the relevant system — useful for seeing at a glance whether a system is on a calendar, an automation, or both.