| alarm | A notification that a defined event has occurred or an indication that some value is not within an appropriate or expected range. For example, a security breach, temperature limit, or equipment malfunction can initiate an alarm notification. Text and icons on the Alarm Console identify alarm severity. |
| alarm console | A table view that lists all current alarms for an individual station. This view is available on the alarm recipient component (in the Alarm Service). |
| alarm portal | A table view that lists alarms collected from multiple stations. To access this view from the main menu, click . |
| category | A logical grouping of system objects (components, files and histories) by directly assigning objects to the category. For
example, basic categories may be used to group objects by geography (floor 1, floor 2, etc.) or type of object (lighting,
HVAC, etc.). Each category may be subject to separate user roles and permissions. Each new station has two default categories:
user (category 1) and Admin (category 2).
You manage categories using the CategoryService. |
| certificate | A PKI (Public Key Certificate) or digital certificate is an electronic document used to prove ownership of a public key. The certificate includes information about the key, the identity of its owner, and the digital signature of an entity that verified the validity of the certificate’s contents. If the signature is valid, and the client can trust the signer, the client can be confident that it can use the public key contained in the certificate to communicate with the server. |
| component | A piece of self-describing framework software that can be assembled like building blocks to create new applications. Components represent individual points—such as outside temperature, office temperature, occupancy, and schedules—that generate analog data for analysis within the system. Components differ from modules in that components comprise an implementation of the framework, whereas modules comprise the framework software itself. |
| config flag | A configuration flag is a boolean value that is stored as part of a bitmask on each slot of a Baja object. Some flags apply to all slot types, while others only have meaning for certain slot types. You access a slot’s config flags by right-clicking the slot and clicking ConfigFlags. |
| container | For example: WebWidget |
| control point | In the narrowest terms, control points refer to the eight point types found in the baja control palette under the Points folder. In broader terms, control points include components from the control and kitControl palettes. Most of these components are based on the eight basic point types. They inherit from BooleanPoint, EnumPoint, NumericPoint,
and StringPoint.
ControlPoint is the base class for all point types in the Baja control architecture. A ControlPoint maps to one value that a driver reads or writes. All ControlPoints have a StatusValue property called Out. If the predefined proxyExt is not a NullProxyEct, the system considers the point a proxy point. This means that it is a local representation of a point that actually exists in an external device. The framework uses the driver to maintain synchronization. |
| framework | Software that provides generic functionality. The framework can be customized by adding user-written code. |
| history | An ordered collection of timestamped records. Each history is identified by a unique id. Histories can be periodically archived to a remote history database (archive). A history database is a set of histories. History is also used as a scheme in ORDs to refer to collective histories. |
| niagarad | The Niagara daemon (niagarad) is a server process used to communicate between
|
| node |
|
| object | An object is the base class required for all system entities that conform to the baja model. Objects group information used to construct a model that includes building devices, virtual devices, individual points, users, system features and services. Objects appear in the Nav tree as files, modules, installers, administrators, copiers, drivers and apps. Metadata associated with objects, including categories, roles (permissions), and hierarchies, provide access control and configuration options to manage automated buildings efficiently. |
| ORD | An ORD is an “Object Resolution Descriptor”. The ORD is the
|
| palette |
The palette provides a hierarchical view of available components. You copy or drag a component from a palette and paste it or drop it where you need it — on a wire sheet, property sheet, Px View, or in the palette Nav side bar pane. |
| point extension | A component that extends control of point behavior in a consistent manner. Each property of a ControlPoint that exists as a subclass of a PointExtension is considered an extension on the point. Extensions allow plug-in functionality, such as alarming and historical data collection via special hooks that a ControlPoint provides to the PointExtension. |
| PX Editor | A tool for creating graphical representations of ducting, piping, and the equipment used in a building. The editor allows the creation of PC and mobile views. |
| template | A deployable package of
|