> ## 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.
# Mass write
> Write multiple points and update multiple schedules simultaneously across buildings or an entire portfolio.
Mass write is available at the portfolio level and at the building level. Portfolio workflows use the **Mass Write** module. Building-level workflows use **Mass Write Points** in the Points module or **Mass Write Schedules** in the Schedules module.
Mass write allows you to modify multiple points or schedules in a single operation across one or more buildings. Instead of editing each point or schedule individually, you select targets in bulk, configure the changes, and execute them as a tracked job.
At the portfolio level, the **Mass Write** module uses a left-side menu to switch between **Points** and **Schedules**.
## Enable mass write access
Mass write permissions must be activated on the user's KODE OS role before the module appears.
Navigate to `Launchpad` > `Apps` > `Cloud BMS` > `Roles` and select the role you want to update.
Edit the role and enable the following permissions:
| Permission | Purpose |
| ----------------------------- | --------------------------------------------------- |
| `Get points latest configs` | Enables the Mass Write module in the portfolio view |
| `Initiate points mass write` | Allows the user to execute a mass points write |
| `Schedule Mass Write (Read)` | Enables viewing mass write schedules |
| `Schedule Mass Write (Write)` | Allows the user to execute a mass schedule write |
Click `Save`. Users with this role see the `Mass Write` module in the portfolio view.
Only Launchpad administrators can update role permissions. If you do not have admin access, submit a support ticket to request the change.
## Mass write points
Use mass write points to send values to multiple writable points across buildings simultaneously.
### 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).
Common scenarios include:
* Adjusting temperature setpoints seasonally across the portfolio
* Releasing overrides so devices follow their schedules overnight
* Responding to peak demand by reducing setpoints by a set increment
* Disabling specific devices or systems during scheduled maintenance
### Access mass write points
1. From the portfolio view, open **`Mass Write`**.
2. Click **`Points`** in the left-side menu.
3. Click **`Write Points`** to start a new job or open an existing job from the list.
1. Select a building from the [sites list](/products/kode-os/sites-and-map).
2. Open **`Points`** in the left navigation.
3. Click **`Mass Write Points`** in the left sub-menu.
See [Mass write points](/products/kode-os/points/points#mass-write-points) in the Points article for the building-level workflow and screenshots.
### Selection and search
Only writable points appear in the mass write list. Points are not selected by default — select targets explicitly with row checkboxes.
Use **`Select all`** to include every point across all pages. After **`Select all`**, deselect individual exceptions as needed.
Use **Filters** to narrow the list by point type, canonical type, area, ontology field, data source type, and other attributes. To find non-templated points, set **Ontology Field** to **Not Assigned**.
Search supports three match modes — **Starts with**, **Contains**, and **Exact** — across these fields:
| Field | Description |
| ------------------ | ------------------------------ |
| **Point Name** | Display or raw point name |
| **Path** | Point path in the data source |
| **Ontology Field** | Normalized ontology field name |
| **Device Name** | Device that owns the point |
Toggle between **List** and **Grouped** view in the upper right.
#### Grouped selection
Grouped view simplifies selection for large point sets, especially non-templated points.
In grouped mode:
* Points are grouped by name and kind.
* Each group shows the group name, point count, and device count.
* Expand a group to review the underlying point list with the same columns as the standard table.
* Select entire groups. You cannot include or exclude individual points inside a group.
Filters still apply to the full list before grouping. Grouping does not replace filters.
When writing very large point sets, confirm that target data sources can handle the write volume. This matters when many buildings share a single data source.
### Write points
From the portfolio view, navigate to **`Mass Write`**, click **`Points`** in the left-side menu, then click **`Write Points`**.
Use the **Filters** panel on the left to select one or more buildings. You can filter by country, state, city, or building name. Click **`Apply`** to load the available points.
There is no limit to the number of sites you can select in a single job.
Use **Filters** to narrow the point list. Set **Ontology Field** to **Not Assigned** when you need non-templated points. Use search with **Starts with**, **Contains**, or **Exact** match modes.
Choose targets in **List** or **Grouped** view. Use row checkboxes or group checkboxes, or **`Select all`** across pages. Deselect any exceptions.
Click **`Continue to Set Values`** when the selection is final.
You cannot remove points from the list in later steps. Verify your selection before continuing.
Enter a **Name**, **Reason Type**, and **Reason Description**. These fields identify the job in the tracking history.
Points are grouped automatically by ontology field, unit, and accepted values or facets. You set values per group, not per individual point. Click the blue count next to a group name to see which points belong to it.
Expand a group and configure:
| Field | Description |
| ------------ | --------------------------------------------------------------------------------------------------- |
| **Priority** | Write priority: **Override**, **Auto**, **Set**, or **Release** |
| **Value** | Value to write to every point in the group. Negative values are supported for numeric points. |
| **Duration** | How long the value persists before reverting. Check **Permanent** to keep the value until released. |
Click **`Save`** for each group. Color highlights indicate missing information.
After saving all groups, click `Execute`. A confirmation dialog warns that changes are not reversible. Review your point selection, then click `Proceed` to start the write operation.
Cloud BMS begins writing values to every selected point. You are redirected to the job details page.
### Track job progress
The job details page shows:
* Creator and creation time
* Total number of points processed
* Success and failure counts per group
Click the blue counts to view individual points within each group and their write results. Completed jobs remain listed on the main **Mass Write** page for future reference.
Use the **`Export`** button to download job results as CSV. Enter a **File Name**, choose which **Columns** to include, then click **`Export`**.
The CSV export includes **Building ID**, **Building Name**, **Device ID**, **Device Name**, **Name**, **Field**, **Priority**, **Value**, **Duration**, **Status**, and **Failed Reason**.
From job details, use the three-dot menu to:
| Action | Behavior |
| -------------------------------- | ------------------------------------------------------------------------------------ |
| **Edit Details** | Update the job name or description |
| **Re-run Job** | Start a new run. Change the point selection and write configuration before executing |
| **Retry Job with failed points** | Re-execute immediately for failed points only |
## Mass write schedules
Use mass write schedules to update multiple schedules at once. Common scenarios include:
* Changing start or end times across schedules for seasonal daylight shifts
* Updating operational hours based on new tenant contracts
* Adding holiday special events to multiple schedules simultaneously
* Implementing building-wide or portfolio-wide schedule changes after emergencies
### Access mass write schedules
1. From the portfolio view, open **`Mass Write`**.
2. Click **`Schedules`** in the left-side menu.
3. Click **`Write Schedules`** to start a new job or open an existing job from the list.
1. Select a building from the [sites list](/products/kode-os/sites-and-map).
2. Open **`Schedules`** in the left navigation.
3. Click the three-dot menu in the top right.
4. Click **`Mass Write Schedules`**.
See [Schedules](/products/kode-os/schedules) for building-level schedule management.
### Selection and search
Every weekly schedule (excluding calendar schedules) appears in the list based on your filters. Schedules are not selected by default — select targets explicitly with row checkboxes.
Use **`Select all`** to include every schedule across all pages. After **`Select all`**, deselect individual exceptions as needed.
Use **Filters** to narrow by **Kind**, **Current Status**, or **Data Source**. Use the search bar to find schedules by name.
Toggle between **List** and **Grouped** view in the upper right.
#### Grouped selection
Grouped view simplifies selection for large schedule sets.
In grouped mode:
* Schedules are grouped by name and kind.
* Each group shows the group name and schedule count.
* Expand a group to review the underlying schedule list with the same columns as the standard table.
* Select entire groups. You cannot include or exclude individual schedules inside a group.
Filters still apply to the full list before grouping. Grouping does not replace filters.
When writing very large schedule sets, confirm that target data sources can handle the write volume. This matters when many buildings share a single data source.
### Write schedules
From the portfolio view, navigate to **`Mass Write`**, click **`Schedules`** in the left-side menu, then click **`Write Schedules`**.
Use the **Filters** panel to select one or more buildings by country, state, city, or building name. Click **`Apply`** to load the available schedules.
Use **Filters** to narrow the schedule list. Use the search bar to find schedules by name.
Choose targets in **List** or **Grouped** view. Use row checkboxes or group checkboxes, or **`Select all`** across pages. Deselect any exceptions.
The header updates to show the total count of selected schedules.
Click **`Continue to Set Values`** when the selection is final.
You cannot remove schedules from the list in later steps. Verify your selection before continuing.
Enter a **job name**, then choose the schedule type and update type.
| Option | Behavior |
| ------------------ | --------------------------------------------------------------------------- |
| **Weekly** | Updates only the weekly time slots on the selected schedules |
| **Special Events** | Adds only special events to the selected schedules |
| **Both** | Updates weekly time slots and adds special events (you must configure both) |
If you choose Weekly, existing special events remain untouched. If you choose Special Events, existing weekly time slots remain untouched.
| Option | Behavior |
| ----------- | ------------------------------------------------------------------------------------------------------------------------- |
| **Append** | Adds the new time slots or special events on top of existing ones without removing current entries |
| **Replace** | Replaces existing weekly time slots, special events, or both on all selected schedules with the values you configure here |
Use Replace with caution. Every selected schedule is replaced exactly with the schedule created here. Days left blank and existing special events are deleted.
If you are adding special events, choose a **priority** (Top or Bottom). This determines whether new events take precedence over or defer to existing events on the same date.
A weekly schedule calendar editor appears based on your selection. Click a day to open a context menu with options to **`Create Event`**, **`All Day Event`**, or **`Clear Week`**. Define the start and end times for each period.
Timeslot creation and value assignment are separate steps, but both happen on the same page. Values appear after you click into a timeslot. Side panels open automatically to guide the next step, especially for special events.
* If the update type is **Append**, these time slots are added alongside existing ones
* If the update type is **Replace**, all existing time slots are replaced with the ones you define here
* Days left blank are deleted from the selected schedules
For special events, create each event and define its time slot using the same workflow as individual schedule special events.
Click a time slot in the weekly schedule or a special event to assign values. The left panel shows all schedule groups with their facet values. Schedules are grouped by type (Boolean, Enum, Numeric, String) and facets.
Pick one value for each group per time slot. Use `Apply to all` to assign the same values across every time slot in the weekly schedule. Repeat for special events if applicable. Click `Save` at the bottom of the left panel.
Click `Save` at the top right (the button remains disabled until all time slots have assigned values). Cloud BMS updates every selected schedule and redirects you to the job details page.
Verify that only the intended schedules are selected. Changes are not revertible after execution.
### Track schedule job progress
The job details page shows the status, timestamp, schedule type, update type, and success and failure counts per group. The bottom section displays a preview of the weekly schedule with the applied time slots and values. An activity log tracks the execution history.
Click the blue counts to view individual schedules and their results. Completed jobs remain listed on the main **Mass Write** page.
Use the **`Export`** button to download job results as CSV. Enter a **File Name**, choose which **Columns** to include, then click **`Export`**.
The CSV export includes **Building ID**, **Building Name**, **Datasource ID**, **Datasource Name**, **Name**, **Type**, **Kind**, **Connector Type**, daily updates for **Monday** through **Sunday** when a weekly schedule is updated, **Special Events**, **Status**, and **Failed Reason**.
From job details, use the three-dot menu to:
| Action | Behavior |
| ----------------------------------- | --------------------------------------------------------------------------------- |
| **Edit Details** | Update the job name or description |
| **Re-run Job** | Start a new run. Change the schedule selection and configuration before executing |
| **Retry Job with failed schedules** | Re-execute immediately for failed schedules only |
## Mass write schedules with sheet
For scenarios where each schedule requires different times or effective dates, you can import updates from a spreadsheet instead of configuring a single template schedule.
From the `Write Schedules` flow, click the `Import Schedules with Sheet` button at the bottom of the left filter panel. A dialog opens with three steps: download the template, fill it out, and upload it.
Click `Download Template` in the dialog. The Excel template contains column headers for all required fields.
Complete the following columns for each row:
| Column | Format | Description |
| ----------------------------------- | -------------------------------------------- | ---------------------------------------------------------------------- |
| `Identifier` | Numeric (for example, `1210168`) | The store or site ID as defined in Launchpad |
| `EffectiveStart` | `MM/DD/YYYY` | The date when the schedule update takes effect (must be in the future) |
| `SaturdayStart` through `FridayEnd` | 24-hour time (for example, `07:00`, `22:00`) | Start and end times for each day of the week |
All days must have values. Each row can have a different effective date and different daily times.
Drag the completed file into the upload area or click `Attach or Drag to Upload` in the same dialog. Invalid or missing values are flagged during upload. Click `Import` to proceed.
After import, Cloud BMS selects the stores matching the identifiers and displays the available schedules. Select the schedules you want to update and click `Execute`.
The sheet import updates weekly schedule time slots only. Existing special events remain untouched.
## Next steps
Run mass write points at the building level from the Points module.
Set up individual building-level schedules before applying bulk changes.
Configure buildings, roles, and permissions at the portfolio level.