Points
A point is a single value in a building system - a temperature sensor, a fan command, a setpoint, an energy meter reading. Points are what you read, trend, and write in Novant.
Points are defined by the source map bound to a source, so every device of the same model shares the same point list. Each point is given a semantic point type that describes what it measures or controls, independent of how the device names it.
Point Fields
The available point level fields are:
| Field | Required | Description |
|---|---|---|
| Name | Yes | Human readable name of this point |
| ID | Yes | Unique ID of this point within this source map |
| Address | Yes | Protocol specific address to access this point |
| Type | Yes | Semantic type for this point |
| Unit | No | Unit for this point value |
| Enum | No | List of states for enumerated point values |
| Formula | No | Formula to use for calculated points |
| Description | No | Human readable description of this point |
Points may also carry properties such as
schedule or mode that qualify what the point
represents.
Source vs Calculated Points
Each point is either a source or a calculated point:
A source point stores live or historical data from a device or system, using a protocol-specific address to read and write values.
A calculated point computes its value on demand using a formula, optionally referencing other points in the same source map.
Only calculated points may include a formula, and their address field
must begin with the calc. prefix. See Calculated Points for more
information.
Point Values
Source points are read and written through their source. For more on current values, see Live Data; for writing and releasing values, see Point Writes; and for historical data, see Trending. To find the condition points that describe a room or area, see Space Points.