What are rulesets?

Rulesets control when measurable.energy sockets automatically turn on or off. They let you define behaviour once and apply it consistently across your estate, from the entire organisation down to a single outlet.

Rulesets are time-based. At their simplest, they say:

Turn ON at this time
Turn OFF at this time

Once applied, sockets follow the ruleset automatically with no manual intervention needed. Rulesets can be applied at almost any level of the hierarchy:
- Organisation
- Site
- Building
- Floor / Zone
- Room / Space
- Individual socket
- Individual side of a double socket

Important exception: TGU / TGX units: a ruleset applied to a TGU or TGX controls the entire unit at once. You cannot independently control individual sockets within that unit.

Rulesets follow a strict priority model:
The lower the ruleset in the hierarchy, the higher the priority.

This allows broad, default behaviour to be set at higher levels, while still enabling precise exceptions where needed.

How priority works in practice

Site, building, or room rulesets act as defaults
Socket-level rulesets always win over everything above them

Example 1: Building shutdown with a room exception
Building ruleset: Turn OFF all sockets at 22:00
Server room ruleset: Always ON

Result:
Entire building powers down at night
Server room sockets remain powered

Example 2: Double socket control
Ruleset applied to one side of a double socket: Turn OFF at 20:00
Other side has no ruleset

Result:
One outlet turns off at 20:00
The other outlet follows any higher-level rules (or stays on if none exist)

Best Practice Guidance
Set broad behaviour high in the hierarchy (organisation or site)
Use lower levels sparingly for genuine exceptions
Avoid unnecessary socket-level rules — they increase complexity
Document critical overrides (e.g. medical, safety, or IT equipment)

A clean hierarchy keeps behaviour predictable and easy to manage.

Key Takeaways

Rulesets automate socket behaviour using time-based ON/OFF rules
They can be applied from organisation level down to individual socket outlets
Lower-level rules always take priority
TGU/TGX units switch as a whole, not per socket
If you remember one thing: defaults live at the top, exceptions live at the bottom.