Determine how values are formatted for display depending on the context and the type of data. Examples include engineering units and decimal precision for numeric types, and descriptive value (state) text for boolean and enum types.

With the exception of proxy points (with possible defined device facets), point facets do not affect how the framework processes the point’s value.

Besides control points, various other components have facets too. For example, many kitControl and schedule components have facets. Details about point facets apply to these components too, unless especially noted.

You access facets by clicking an Edit button or a chevron >>. Both open an Edit Facets window.

Indicate from where the point’s value originates, including details specific to the parentage of the point’s network and communications (driver).

null indicates that the point is an empty placeholder.

Displays the current value of the proxy point including facets and status.

The value depends on the type of control point.

Facets define how the value displays, including the value’s number of decimal places, engineering units, or text descriptors for Boolean/enum states. You can edit point facets to poll for additional properties, such as the native statusFlags and/or priorityArray level.

Status reports the current health and validity of the value. Status is specified by a combination of status flags, such as fault, overridden, alarm, and so on. If no status flag is set, status is considered normal and reports {ok}.

Activates (true) and deactivates (false) use of the object (network, device, point, component, table, schedule, descriptor, etc.).

Reports the frequency of updates.

Defines the port number on the controller or computer used to connect to the network.

If using fox streaming, which uses the station to render the video stream, this port should be different from the station’s fox port. If you are not using fox streaming, this port should be the same as the station’s fox port.