> ## Documentation Index > Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Systems > Organize and monitor devices by functional system groupings such as HVAC, Lighting, Fire, and Electrical in Cloud BMS. Systems is a building-level module. Select a building from the [sites list](/products/kode-os/sites-and-map) to access its systems. Systems are logical groupings of devices organized by function. A building may contain HVAC, lighting, fire detection, electrical, plumbing, and other systems. Each system provides a centralized view of system-level health, making it easier to monitor, troubleshoot, and manage building operations. ## Navigate to systems Click `Sites` in the left navigation bar and select the building you want to manage. Click `Systems` in the left sidebar menu. The systems list displays all configured systems for the selected building. Systems list showing HWS and chilled water system entries with Name, Type, and Tags columns, a Reorder Systems dropdown, and a Create System button Search for or select a system from the list to open its details view. ## Create a system Click `+ Create System` to open the creation dialog. Create System dialog with fields for System Name, Type dropdown, and Tags Enter a descriptive name for the system (for example, `Boiler 01`). Select the system type from the dropdown (for example, `Boiler`, `HWS`, `CHWS`). Add tags to categorize and filter the system. Type a tag name and press enter to add it. After saving, the new system opens in its details view. The canvas is empty with a `+ Create New` button to add a graphic. Use the icons on the right sidebar to switch between views and access system details. Empty system view for chilled water system showing a Create New button in the center and view icons on the right sidebar To reorder systems in the list, click `Reorder Systems` and drag them into the desired sequence. ## View options When you select a system, the system details view provides several perspectives. Switch between views using the icons on the right navigation bar. ### Graphics view The Graphics view displays the system schematic with live data overlaid on equipment components. Point values update in real time on the diagram. Systems Graphics view showing a chilled water system schematic with pipes, pumps, and chillers, and a data table with live point values Click a writable point value on the graphic to open the command panel. The panel displays the device's variables on the left and the action form on the right. Command panel for HWS system showing Chilled Water Valve Percent Cmd, Hot Water Valve Percent Cmd, and Valve Closed Cmd variables on the left, with action fields for Priority, Value, Duration, Reason, and Specific Reason on the right, and current Level and Value at the bottom * **Priority** -- select the command priority level (for example, `Override`) * **Value** -- set the target value. Use the dropdown for enumerated values (for example, `On` or `Off`). * **Duration** -- specify how long the command remains active. Check `Permanent` for an indefinite override. * **Reason** -- select a predefined reason from the dropdown * **Specific Reason** -- enter a custom reason for the change The bottom of the panel displays the current priority levels and values. Click `Save Changes` to send the command, or `Close` to cancel. Click `Activity Log` in the upper right corner to view the command history. ### Command actions and priority levels Cloud BMS uses a BACnet-inspired priority model for writable points. The same command dialog appears for BACnet and non-BACnet integrations, such as REST API thermostats. How each action maps on the device depends on the connector. BACnet points that accept commands have **16 priority levels** (1 is highest, 16 is lowest). When every level is empty (`null`), the point uses a **fallback / default** value (`Relinquish_Default` in BACnet). That fallback is **not** a 17th BACnet priority. Some interfaces label it as level 17 for display only. `Override` and `Set` turn different knobs under the hood, even when the visible value looks the same. | Action | What it writes\* | Description | | ---------- | -------------------- | ------------------------------------------------------------------------------------------- | | `Override` | Priority 8\* | Temporary exception in the priority array. Takes precedence over lower-priority automation. | | `Set` | Fallback / default\* | Changes the fallback or default value. | | `Auto` | — | Clears an `Override` | | `Release` | — | Clears a `Set` | \*Typical for most BACnet and Niagara deployments. Connectors and site standards can differ. `Override`, `Auto`, and `Set` borrow Niagara-style action names. `Release` is a Cloud BMS action that clears a `Set`. In Niagara-style control, `Set` keeps a non-null fallback so sequences and logic keep a reliable baseline. Use the priority array (including `Override`) for programmed automation and temporary exceptions. To make `Set` write to priority 16 instead of the fallback or default, enable **`Set in Slot16`** (Niagara) on the point. Configure that option from [device details](/products/kode-os/devices/devices#view-and-edit-points), [device templates](/products/kode-os/devices/device-templates), or [points batch update](/products/kode-os/points/points-batch-update). ### Dashboard view The Dashboard view charts system points over time, grouped by category (Temperature, Flowrate, and others). Each chart shows sensor and setpoint values with a configurable time range. Dashboard view showing a Temperature trend chart for Discharge Air Temp over the last two days, with a Flowrate section below ### Widget view The Widget view displays all system devices as cards with their current point values. Each card shows the device name and its key readings. Widget view showing device cards for VAV_101, AHU_3, FCU_102, and FCU_101 with their current point values ## System details Click the information icon on the right sidebar to view the About System panel. About System panel showing system name HWS, type HWS, tags, and a Connected Systems section The panel contains two tabs: * **Information** -- displays the system name, type, tags, and connected systems * **Attachments** -- upload and manage photos, documents (submittals, O\&M manuals, as-built drawings), and notes Click the edit icon at the upper right of the panel to modify system properties. ### System devices Click the devices icon on the right sidebar to view all devices associated with the system. The panel lists each device with tabs for quick switching between them. System Devices panel showing VAV_101 details with tabs for AHU_3, FCU_102, and FCU_101 Click a device tab to view its details: Data Sources, Device Name, Location, Type, Area, and Tags. ## System-level health indicators Each system displays aggregate health information: * **Total devices** in the system * **Percentage online** showing the ratio of communicating devices * **Active alarms** indicating fault conditions across the system's equipment * **Communication score** reflecting overall data source reliability for the system ## Edit system graphics Click the three-dot menu on the right side of the Graphics view and select `Edit` to enter edit mode. You can also select `Delete` to remove the graphic. HWS system Graphics view showing a piping schematic with a three-dot menu expanded with Edit and Delete options To modify the system graphic or add devices to the visual layout: Click `Edit` from the three-dot menu to open the system graphic in the editor. Upload a new system graphic, reposition existing devices, or add devices from the device list onto the schematic. See the [Graphic Tool](/products/kode-os/graphics/graphic-tool) for details on building system schematics with drawings, markers, and layers. Click `Save` to apply your changes to the system graphic. System graphics provide a visual way to identify faults and monitor performance. Color-coded indicators on the graphic highlight online, offline, and alarming devices, making it fast to pinpoint issues without navigating to individual device details. ## How systems support fault detection Systems feed directly into Fault Detection and Diagnostics (FDD). When FDD rules are configured, the system grouping determines which devices are evaluated together. For example, an HVAC system's AHUs and VAVs are analyzed as a connected group, enabling detection of cascading faults that affect multiple devices. ## Next steps View devices organized by physical location rather than system function. Create and interact with schematic diagrams of building systems.