Project settings

Project-wide settings — locale and units, tag display, alarm defaults, history filtering, event exceptions, and server health alarms.

A project’s Settings control how the whole project behaves and how its data is presented. They’re grouped into the sections below.

General

  • Language — the project’s locale.
  • Time zone — the zone timestamps are shown in for this building’s data, so events and history line up with local time on site.
  • Engineering units — the unit system (metric or imperial) used across the project.

Tags

Defaults for how tag values are handled and shown:

  • Decimal limit — the maximum number of decimals shown for decimal values.
  • Error threshold — how many consecutive tag errors are ignored before an error is shown, which avoids flagging brief, transient glitches.
  • Require comments on value change — when on, a comment is required whenever someone changes a writable tag’s value, so there’s always a record of why.

Alarms

Project-wide defaults and policies for alarms:

  • Require comments on acknowledge — when on, acknowledging an alarm requires a comment.
  • Default priority — the priority new alarms start with (Low, Medium, or High).
  • Default activation / deactivation delays — the delays (in seconds) new alarms start with, so an alarm only fires after a condition has held, and only clears after things have been normal for a while.
  • Maintenance mode — suppresses all of the project’s alarm notifications for every user until turned off, for when you’re working on equipment.

Tag history

How tag history is filtered before it’s stored, to keep the database manageable:

  • Aggregate values — when on, values are summarized over a period using a function (for example average, minimum, maximum, or sum) instead of storing every reading.
  • Deadband — a duplicate filter: a change smaller than the deadband isn’t recorded, so a barely-moving value doesn’t fill history with near-identical points.

These act as the project’s defaults; an individual tag can override them in its own history settings.

Events

  • Exception dates — project-wide dates on which scheduled events are skipped (for example public holidays). An event can choose to honour this shared list rather than defining its own.

Server health alarms

Raise an alarm automatically when the on-site server is under strain — so you’re warned before resource problems disrupt data collection. There’s one for each resource:

  • CPU utilization alarm
  • Memory utilization alarm
  • Disk utilization alarm

Each is enabled independently and takes a threshold (a percentage, 0–100) and an activation delay (seconds), so a brief spike doesn’t trigger it.