Do Not!

1. Schedules should not be set up in a way that when the Air Handling Unit AHU_1 turns on also it enables the VAV that are connected to it (VAV_1, VAV_2….VAV_N). This will be OSS Adapter job.

2. When a Schedule is connected to another Schedule and controls the device.

3. This is an Enum Scheduler that has a Point\ Mapper\Switch which controls the devices.

Do!

All the logic configurations in Jace that turn on the devices should be turned off, besides Schedulers that control both the base device and the reference device, otherwise, OSS can not control the devices.

OSS Adapter Navigation

Go to your company's KODE OS building then navigate to the OSS icon from the left main bar, and click on it.

Upon selecting the OSS tab you can see the Optimizations that are in place already (if applicable) with all the details.

On this page, you have the ability to select your OSS operation mode. There are three Operation Modes available: 

Comfort - The goal of Comfort is to have all zones on setpoints by the time occupancy starts. The focus is on occupant comfort.

Balanced – The goal is to have the third quartile of the zones on setpoint by the time occupancy starts. The focus is on occupant comfort as well as energy savings.

Energy Savings – The goal is to have the medium of the zones on setpoint by the time occupancy starts. The focus is on energy savings.

Adding Adapters

Click on the Adapters button on the upper right as highlighted in the screenshot, which will open the page with more details. 

To add a new Adapter, click on Add OSS Adapter, there are two options:

• Create a new Adapter

• Add from the existing (Templated Adapters) 

Adding a new Adapter

After clicking on Add new Adapter the page with these details will be displayed.

The process of creating a new Adapter is categorized as follows:

            1) Select Devices > 2) Add Points > 3) Review and verify

1) On the Select Devices page we have the Details with the Name, Description, Base Device, and Reference Device of the adapter:

See the below screenshot for more detail:

• Name of the Adapter: FCU with Effective Setpoints (the name can be customized to your liking, depending on the function).

• Description: Default FCU adapter with Effective Setpoints.

• Base Device: fcu_1 (devices can be added here, a kind reminder: devices are exclusive for one adapter).

• At the base Device, select the devices by choosing their Canonical Types. Also, select the Entities of your device and click save.
  

• Reference Device:  Is filled depending on the type of device that is chosen for the OSS Adapter. For example, VAVs are referenced to an AHU and in order for OSS to work properly we need data points from both device types.  If a chosen device is not connected to any other device we can ignore the Reference Device option. If a device is connected to another device then we can use the Reference Device feature.

2) On the second page Add Points, as per the name, points should be added to the Base Device for each of the fields presented. Upon selecting Choose Points, you can select the Points for the sensors and add them. 

• Zone Air Temperature Sensor

• Zone Air Temperature Cooling Setpoint

• Zone Air Temperature Heating Setpoint

• Run Status

• Occupied Mode(should be writable)
  
  If a Reference Device is selected in step one then another two options will be added for the Reference Device:

• Run status

• Occupied mode 

Let's take an example when creating an adapter for VAV-AHU devices with Zone Air Temperature Setpoint. With Base Device a VAV and the Reference Device an AHU. 

At the Add Point tab, we will have seven fields of points to fill in.

Base Device:

• At Zone Air Temperature Sensor select zone air temperature sensor.

• At Zone Air Temperature Cooling Setpoint select zone air temperature setpoint.

• At Zone Air Temperature Heating Setpoint select zone air temperature setpoint.

• At Run status select occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

• At Occupied mode elect occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

Reference Device

• Run status select occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

• Occupied mode elect occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

Let's take another example when creating an adapter for VAV-AHU with Effective Setpoints. This will be an Adapter for devices that use Effective Cooling/Heating Temperature Setpoints. With Base Device a VAV and the Reference Device an AHU. 

At the Add Point tab, we will have seven fields of points to fill in.

Base Device:

• At Zone Air Temperature Sensor select zone air temperature sensor.

• At Zone Air Temperature Cooling Setpoint select effective cooling zone air temperature setpoint.

• At Zone Air Temperature Heating Setpoint select effective heating zone air temperature setpoint.

• At Run status select occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

• At Occupied mode elect occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

Reference Device

• Run status select occupied mode or any other point that will give the device status, for ON status choose Occupied, and for OFF choose Unoccupied. 

• Occupied mode elect occupied mode and for ON status choose Occupied, for OFF choose Unoccupied.

If a device has more than one point of the same field, select the Aggregation function. The Aggregate function performs a calculation on a set of values and returns a single value. At  Zone Air Temperature Cooling Setpoint and Zone Air Temperature Heating Setpoint, besides that we have an Aggregation function there is also an upper band and a lower band which represent the time when the device will start cooling or heating.

If the Zone Air Temperature Setpoint for example is 23 Celsius, the Avg function is plus 1 for the Cooling Setpoint, and the Avg function is minus 1  for the Heating Setpoint, then the upper bound will be 24 Celsius and the lower bound will be 22 Celsius.

At the Run Status and Occupied Mode enums can be mapped, this maps the values coming from these points to occupied and unoccupied. 

There is a requirement to have at least one occupied_mode as a writable point on either the  Optimizing or Reference device, having two or more occupied_mode points is acceptable too.

To Edit the point selected click on the icon, once clicking, it will open the tab with the points from where you can modify and add more points, or edit the point aggregation.

3) The last page is Review and Verify

This page is split into two tabs: Completed Devices and Devices With Issues.

The first tab, Completed Devices shows all the devices which meet OSS requirements fully, this means they have all of the required points, they have schedules in place and referenced to devices, and OC mode points are writable.

For the process to be completed we must select the devices which we want to include on the Adapter and click Save.

Navigate back to Operation Mode and see in the Bottom right the icon for OSS activation.

Click on Activate and wait for some minutes until the OSS will be active. After that, the OSS Adapter will turn on for the devices that we have selected.

The second tab Devices With Issue shows devices that do not meet OSS requirements fully. From this page, you can click on devices directly and continue to make necessary adjustments.

After filling in the data in the Select Devices, Add Points and saving them on the Review and Verify page the adapter process will be completed. See below an example of an OSS Adapter.

Adding an existing Adapter

Click on Add from Existing, and a window will open with the Adapters from the library. Here you may select a specific template and click on Add From Existing to save.

Our team has created adapter templates for every supported use case. In the below screenshot, you can find a list of templates that are provided by default.

After adding the Adapter from the existing templates, steps 1 and 2 of the adapter creation process will be prefilled from the templates. Also, keep in mind that you will have to create new OSS Adapters for each building.

Existing templates are editable. After choosing the specific template, the process of creating the adapter will start from the beginning, only with the first and second steps prefilled. In the first and second steps (Selecting Devices and Add Points) changes can be made and then saved in the third step (Review and Verify).

Edit and Delete OSS Adapter

To Delete OSS Adapter, click on the three dots on the upper right and select the trash icon 

From there the confirm page for deletion will be open:

To Edit OSS Adapter, click on the three dots icon at the far right of the Adapter name > from the drop-down menu select the Edit icon. From there you will be directed to the Edit OSS Adapter page from where you can modify it.