Opus Magnum Data Aggregator

USER GUIDE
Content
OPUS DATA AGGREGATOR ............................................................................................................................................................... 2
Configuration Window .......................................................................................................................................................... 2
Site List ......................................................................................................................................................................................... 3
Network List ............................................................................................................................................................................... 6
Model Manager ........................................................................................................................................................................ 9
History Point Enabling ........................................................................................................................................................17
Opus SQL Tab .........................................................................................................................................................................18
Add SQL Driver Component in Opus Magnum Data Aggregator Station Alarm and History
Services ......................................................................................................................................................................................19
Data Server Tab ......................................................................................................................................................................20
User Service Tab.....................................................................................................................................................................20
Batch Job Support for LogicOne Sites .......................................................................................................................20

1 31-00408-01
Opus Data Aggregator

Opus Data Aggregator

Opus Data Aggregator is an intelligent mechanism developed by Honeywell to collect the histories
data from various legacy controllers, executives and push the data to a database depending on the
system load. It can automatically adjust the number of parallel histories depending on average CPU
usage. Some major advantages of the Opus Data Aggregator are:
1. Multiple Logic One executives can communicate with multiple networks to collect the data.
2. IoT Model service has in-built model mapper and point validation tool pointing to NHml tag
dictionary to import the site and tag the required equipment and points that are pushed to SQL
DB.
3. Automatic association of control entities to equipment and alarm/histories or both to point
source.
4. Use the same SQL database used by Opus AX supervisor to store all the Alarm & Histories logs.

Configuration Window
The Configuration window is used to add a site component and all the points/devices to the Opus Data
Aggregator. It contains several useful tabs for complete site configuration.
Following are the list of the tabs included in Configuration window:
• Site List
• Network List
• Model Manager
• Opus SQL
• Data Server
• User Service
This section explains the application procedures of each tab required for setting up the site.

Open Configuration window

1. In the Niagara workbench, go to Station and double click on the Home node.
2. The Opus Data Aggregator Homepage is displayed.
3. Click on the Config button on the top of the home page.

31-00408-01 2
Opus Data Aggregator

Site List
This tab helps to add a Site and all the Meta data information of a site to the gateway. An Application
engineer or a site technician must follow the below steps to configure and add a site to the Site List.

To Add a Site
1. Click Add Site to open the Add Site property sheet.

3 31-00408-01
Opus Data Aggregator

2. Enter the required Opus enterprise site Meta data information of remote HML executive to
fetch the entire site information.
• Enterprise Name: Mandate
• Enterprise Code: Mandate
• Group Name: Mandate
• Group Number: Mandate
• Site Number: Mandate. You must ensure that the Site Number is unique across the
Opus system.
• Site Type: By default, it would be Logic one if user does not define anything.
• City: Mandate
• State: Mandate
• Country: Mandate
• Time Zone: Mandate. User needs to specify the time zone of remote executive.
• Coordinates: Optional
• Network Type: By default, it would be Logic One Network.
• Enable Opus Meta Data: Set to true.

NOTE:
By default, “Enable Opus Meta Data” will be set to “False”. You must set this property to “True”. Ena-
bling Opus Meta Data property will add the control entities to equipment reference which in turn will be
attached to alarms and history names. If it is set to “False”, only the tags are fetched but not the Alarms
and Histories extensions. For more details. refer “Importance of Control entity and Meta data section”.

3. Click OK to add the site.

The site is added to the Site List.

To Verify/Modify the Details of the Added Site

1. Double click on the site in Site List.
2. In the Property Sheet, verify that the opus enterprise site meta data what is defined matches.
Refer below example displaying a site property sheet.

31-00408-01 4
Opus Data Aggregator

NOTE
The meta data entered will further be used to associate history name. In Niagara 4, a history name
should not exceed 44 characters. Ensure to follow the character count rules when entering site meta
data. Refer Meta data rules section for more details.

3. Expand Logic One Network and then Customer Vendor property.

4. Enter desired customer name as shown below. By default, Vendor name will be logic One.

5 31-00408-01
Opus Data Aggregator

NOTE
A model file is present under the Station in nav tree based on the customer name. Therefore, it is
mandatory to enter customer name. It is also important to maintain name consistency for a cus-
tomer, so that a single Opus Data Aggregator instance for a customer can be configured to com-
municate with multiple executives and multiple networks/stores.

5. Click Save to save the updated information.

This information serves as a root level node definition for all alarms and histories that are
logged from this instance of the Opus Supervisor.

Importance of Control Entity and Opus Site Meta data

In Opus Data Aggregator, control entity is added to the controller and alarm and history extension will
be added to point reference.
For example, when an alarm is generated, the Metadata will help to identify from where the source when
dealing multiple site with single supervisor and when the alarm generated, from which customer, group,
site, equipment the alarm was generated. Because of the multi-site concept, it is important to have
metadata info associated to all the alarm and history extensions generated in Opus system.

Network List
After completion of the above steps under Site List tab and save the site information, the site is auto-
matically listed under the Network List tab. User can add a new executive in this tab.

31-00408-01 6
Opus Data Aggregator

To Add New Executive

1. Double click on the newly added LogicOneNetwork.
2. Click New to create a “New Executive”.

3. Enter the required executive information in the text box.

• Name: Name is automatically fetched from the entered Site meta data.
• Type: Select the type name as HVAC/L from the drop-down menu.
For the initial release, only HVAC/L is supported. Refrigeration is also supported but
not for this release.
• Address: Enter an address between 0 to 31.
• IP Address: Enter the IP address of your remote Logic One executive which we would like
to import.
• IP Port: By default, 23400 port number is specified in the text box. User need not change
the IP Port number.
• Direct IP Connect: By default, it will be set to “False”. User must set it as “True” by selecting
the option from the drop-down menu.
• Equipment Name: Give a name to your equipment based on its type (this is user defined
and it would be HML).

7 31-00408-01
Opus Data Aggregator

4. Click “Ok” to add the new executive.

NOTE
To fetch data from an executive/site, user should enter the above executive details as per the con-
figuration done in the existing LogicOne site.

Importing LogicOne Executive Details to Opus Data Aggregator

The newly added executive will now appear under the Network List Database. Right click on the new
executive and click Actions Discover Modules as shown below.

31-00408-01 8
Opus Data Aggregator

All data from the executive, including details of every module physically connected to down-the-line
controller, is discovered and added to the Opus Data Aggregator instance under given executive.

NOTE
This configuration allows multiple executive to communicate with multiple networks/stores.

Model Manager
Model Manager in the Opus Data Aggregator helps to perform Site modeling in few simple steps. To
apply tags to all equipment and points in an executive, user can use simple Objective selection in Model
mapper filters. After filtering the required equipment or points using the Pattern/rule/type filter, user
can apply the tag to all the filtered results in one single click. Follow the below steps to configure Model
mapping service.

Configuring Model Mapping Service

1. Click on Model Mgr tab in the Opus Data Aggregator Config window.
2. Click on Network or Device property folder drop-down and select Component Chooser.

3. Select LogicOneNetwork and click OK.

9 31-00408-01
Opus Data Aggregator

4. By default, select Dictionary as NHml from the drop-down menu.

5. Click on Edit Model Mapper to open the Model Mapper window.

6. Based on Customer site template, multiple components will be present for control point asso-
ciation. All those components (equipment, point, etc.) are displayed under the Model Mapper’s
Model Entity drop-down menu.

Applying Model Mapper Filters

The Model Mapper filters allow to filter out specific entity based on its type using simple patterns and
rules. After filtering the exact entities, user can apply tags to all those entities at once.
In the Model Mapper Window, Select a Model Entity from the drop-down menu. For example, rooftop.

31-00408-01 10
Opus Data Aggregator

Model Mapper User Interface

Interface Description

The ORD for a network It selects which network or device the model mapper will search through when dis-
(site) or device playing results for the selected model entity.

The brand (or cus- This is automatically populated by the mapper when an ORD is selected, and a valid
tomer) associated site is found. Selected devices will use the site component located in the network.
with a site

The BAS vendor asso- This is automatically populated by the mapper when an ORD is selected, and a valid
ciated with a site site is found. Selected devices will use the site component located in the network.

The model entity that This drop-down list is generated automatically when an ORD is selected. Selecting
the users want to view an option in the dropdown list will load the corresponding file and display the
or edit. search results. The previously selected file will NOT be saved automatically.

Search results pane. The number of matches found is displayed in the label. This will list the display
names and the type of all components found underneath the network or device
ORD that fit the rules specified. See items 6, 7, 8, and 9 for how searching works.

List of patterns used These patterns are checked against the display name of the component. Inclusion
toinclude compo- patterns are checked after types and exclusion patterns. Inclusion patterns are
nents in the search re- checked along with property rules and are an OR condition. If a component is not
excluded and matches any rule in either the inclusion patterns or the property rules,
sults.
it will be included in the results. Right click in the pane to add a new entry. Right
click on a row in the table to edit or delete the entry, or to add a new entry.
Include pattern is added with few check boxes (starts with, ends with, contains and
case insensitive) that adds regular expression upon selecting and adding to the

11 31-00408-01
Opus Data Aggregator

entries. You can simply write a tag rule by selection of any of these combinations to
filter for matching entities.

List of property rules The rule must have the following format: [bformat] like [regular expression]. Note
that will check to see that the bformat should NOT contain % signs, i.e. parent. pointType like .*Temp.
that a bformat The model mapper handles adding the % signs to the beginning and the end of the
string. Property rules are checked after types and exclusion patterns. Property rules
matches the supplied
are checked along with inclusion patterns and use an OR condition. If a component
expression
is not excluded and matches any rule in either the property rules or the inclusion
patterns, it will be included in the results. Right click in the pane to add a new entry.
Right click on a row in the table to edit or delete the entry, or to add a new entry.

List of included types If there are no entries in the list, then all component types will be considered for
in the search. matching. If there is at least one entry in the list, then a component being tested for
the model entity must be at least one of the types in the list. Note that components
who are subtypes of a listed type will pass the type test. This means that adding
control: ControlPoint to the type list will find both NumericWritables and Boolean-
Writables. Entries should be in the standard Niagara form for types [modu-
leName]:[typeName]. Right click in the pane to add a new entry. Right click on a row
in the table to edit or delete the entry, or to add a new entry.

List of patterns to ex- Any point with a display name that fits any one of the exclusion patterns will not be
clude points. included in the results. This can be used to filter out results based on display name.
Right click in the pane to add a new entry. Right click on a row in the table to edit or
delete the entry, or to add a new entry.
Exclude pattern is added with few check boxes (starts with, ends with, contains and
case insensitive) that adds regular expression upon selecting and adding to the
entries. You can simply write a tag rule by selection of any of these combinations to
filter for unwanted entities.

Load File button The Load File button will reload the file for the currently selected model entity. This
will erase any changes that the user has made that have not been saved. This can
be used to quickly revert changes that are no longer wanted.

Save to File The Save to File button will save the current entries in all tables to the file. Changes
must be saved to the file before the newly added or deleted rules will be used for
tagging.

Apply Filters The Apply Filters button will run a search using the entries that are currently in the
tables. This is useful for seeing how the search results change as you modify the
rules, without overwriting the old file. Using the Apply Filters button allows the user
to revert the changes; using the Load File button if changes have not been saved.

Included Patterns
1. Under the Filters pane, right click to add expressions/Included Patterns to filter all rooftop units
in the site.

31-00408-01 12
Opus Data Aggregator

2. In the Add Included Pattern dialog, enter any few characters that are present in the name of all
the rooftop units in the site. For example, if all the rooftop unit’s name starts with “RG”:
3. enter rg in Model Entry text box.
4. Select the Starts with and Case Insensitive check boxes.
5. Click OK.

6. The Model Mapper will now automatically populate required regular expressions to set the rules
for filtering the results. Click on Apply Filters.

7. All the matched results are displayed under Matched Entities.

13 31-00408-01
Opus Data Aggregator

8. User can notice that the count (76 in above example) of the results displayed is also displayed
next to Matched Entities. You may use the other filter options to get the desired exact entities.

Included Types
1. In the above example, the results displayed also include control points for IMCLoad. To exclude
the unwanted entities, use the Included Types filter option.
2. Right click on the Included Types (type:class) under Filters pane and click Add New Entry.

3. Enter logicOneExec:LogicOneModule in the New Model Entry text box.

4. Click Apply Filters. All the IMCLoad entities are excluded and only the LogicOneModule entities
are displayed.

31-00408-01 14
Opus Data Aggregator

5. Notice that the Matched Entities count is now 38 and only the rooftop units are displayed.

Apply Tags
1. Once the desired results are displayed under the Matched Entities, click Save to File and then
Load File buttons.

2. Close the Model Mapper window.

3. Click on Apply tags button to apply rooftop Control entity to all the saved results.

15 31-00408-01
Opus Data Aggregator

4. Once the Tags are applied, the tagged objects can be identified by the corresponding values in
the columns ‘Entity Type’ and ‘Entity Class’.

Property Rules
*Add zonetemp example with images.

Excluded Patterns:
User can also use Excluded Patterns (expressions) to refine your filter results.
1. Right click on the Excluded Patterns and click Add to add a filter.
2. Enter the characters that you need to exclude from the existing filter results.
3. Click OK and then Apply Filters to exclude the unwanted control points.

Verifying Applied Rule

User can verify that all the required control points have Tag rules applied and ensure that the
correct rules are applied under the NHml property in the Niagara Tag Dictionary service.
1. Go to your Niagara Station. Click Config -> Services -> TagDictionaryService.

2. Right click TagDictonaryService and navigate to Views->AX Property Sheet.

3. Expand NHml property and then expand ModelMapperRules folder.

31-00408-01 16
Opus Data Aggregator

4. All the points with Tag Model Rules applied are displayed.

History Point Enabling

Enable Collection for History Point Extension
The above executive configuration and Model Mapping rules applied need to be enabled.
1. Once the executive is configured, close the Opus Data Aggregator Configuration window.
2. Go to OpusHistoryService and select all the points in the list.
3. Right click and enable collection.

17 31-00408-01
Opus Data Aggregator

Add History or Alarm Extension to Missing Points

To attach history or alarm extension for the points that are missing in Tag dictionary or NHml dictionary,
you may use either of the below ways to add the points.
1. Drag and drop the component to point from Opus enterprise palette enclosed under OpusDefault-
Properties, as shown below.

2. Re-use the extension by duplicating other available points. Ensure the extension being reused is
appropriate. For example, all Boolean points will have percentage symbol (%) on their history ex-
tension, all Numeric points will have Numeric interval extension associated and all Energy related
points will be associated with Average interval history extension.

NOTE
• For history extension, the Point group name must be unique from the control entity ref-
erence.
• For alarm extension, correct limits must be specified.

For example, if you would like to add a point which is missing from the existing NHml tag dictionary,
you can duplicate a point and make sure the point group name is unique for history extension and
correct limits are specified for alarm extension.

Opus SQL Tab

The Opus Magnum supports encrypted connection to SQL server for more secured connections. The
Opus SQL tab allows you to configure the SQL Database to save all the associated Alarms and histories
of the executive. Enter required information in the property sheet to establish connection with the SQL
Server.
• Host Address: Type the IP address of the database server.
• Username: Type the windows authentication username.
• Password: Type the windows authentication password.

Instance Name
Extra Connection Properties: User should enter the database name with a Prefix. Database-
name:xxxx

31-00408-01 18
Opus Data Aggregator

Windows authentication: By default, it is set as False. Set the Direct IP to True. This will enable direct
connection to the above SQL database and to store all the required data.
Set Windows authentication if required. When set true, the Opus SQL driver will use Windows authen-
tication for accessing the SQL Server.
Auto Create Schema: By default, it will be set as True. If it is set to False, user needs to manually create
the SQL database schema. If the database schema is not created, the Opus Supervisor will not save the
alarms to the SQL database successfully.

Add SQL Driver Component in Opus Magnum Data Aggregator Station Alarm and
History Services
Once the executive is configured in Opus Data Aggregator and an SQL database is defined to save the
executives data, you need to enable the Opus Data Aggregator to store all the Alarm and history service
data to the SQL database.
1. Go to Niagara Station->Config->Services->OpusAlarmService->Driver Component.
2. Select the SQL database that was added from the drop-down menu.

3. Go to OpusHistoryService->Driver Component.
4. Select the SQL database again from the drop-down menu.
5. Once both the services are enables to store data to the SQL database, go to Station-> Right
click->click Save Station.
6. Go to the Niagara Platform->Application Director.
7. Right click on the Station and select Restart.

19 31-00408-01
Opus Data Aggregator

NOTE
User is recommended to use Sql History Push Service to route the history logs efficiently.

Data Server Tab

This information is provided as a reference for the user to identify the geographical locations of the
data from multiple executives and networks. User can have a single virtual machine in a geographical
location connected to multiple executives and networks.
User reference details of Data server need to be added accordingly.

NOTE
TCP/IP Platform Service Plugin: There is no application in the current scenario.

User Service Tab

1. The User Service tab enables to manage Users and their permissions, to access the Opus Data
Aggregator. The Opus Data Aggregator uses default Niagara User Service to manage the User
authentication.
2. Refer to “Tridium documentation” for more details.

Batch Job Support for LogicOne Sites

OpusDataAggregator Configurations
Discover LogicOne site in OpusDataAggregator station
Controller Setpoints:
• User can find LogicOne Site modules load in the newly created Load folder hierarchy.
• Inside the Load – Module Load- Settings folder -All Batch setpoint control setting parameters
will be available.

31-00408-01 20
Opus Data Aggregator

Controller Schedules:
• User can find LogicOne Site schedules in the newly created Schedules folder hierarchy.
• User can find 2 separate folders under the Schedules folder which are Regular schedule and
IOM2 schedule.
• Regular schedule – Used in ETM series module for Rooftop units.
• IOM2 schedule – Used in IOM2 module for AHU units.

21 31-00408-01
Opus Data Aggregator

NOTE
IOM2 schedule retain the name as is from ESS32 during Discover module. But Regular sch is not.

For Regular Schedule -User must follow the following steps to retain same configured name
from ESS32 during Discover module option:
• Create LogicOne Site .XLS file by extracting from ISCOPE. (For .XLS file creation - Refer the
document from Installer location “Opus Help” module folder – “Steps to create .XLS file for
LogicOne Schedules from ISCOPE”).

NOTE
For further details please refer to “To configure name of regular schedule in opus magnum data
aggregator” document available in install package.

• Use “iScope To Opus HVACL Conversion.exe” to read .XLS file and convert that into .JSON file.

• Place the. JSON in the OpusDataAggregator Station location and Invoke LogicOne site Module
Discovery.

NOTE
The File Name for LogicOneSystem should be the same as in the above image.

31-00408-01 22
Opus Data Aggregator

• After the Module discover, User can find the same name which is retained for Regular sched-
ules.

23 31-00408-01
Opus Data Aggregator

NOTE
If No LogicOne Site JSON file used, then user get the default below names for the Regular Sched-
ules.

31-00408-01 24
Opus Data Aggregator

Tag Dictionary Service - NHml: - New Tag Module Created for “Load”.
This will help to create control entity for Load – Module control settings parameters and which also
includes the setup of the batch setpoint list. Control entities associated with respective module lodes
upon modeling/Tagging.

25 31-00408-01
Opus Data Aggregator

Apply Tag for LogicOne sites

Based on the site config (Naming convention), update the “load” model entity file.
Example:

31-00408-01 26
Opus Data Aggregator

NOTE
After apply Tag, Corresponding entity get added under the module load with same module
name and Included Batch Setpoint list for the control entity.

27 31-00408-01
Opus Data Aggregator

LogicOneSyncService
LogicOneSyncService will be available as default in OpusDataAggregator template station.

NOTE
User can drag the LogicOneSyncService from LogicOneExec module.

31-00408-01 28
Opus Data Aggregator

• Site Synch File Trigger Time - User can define Site Sync File trigger interval time in minutes
for Site updates which defined on Data Gateway ORD.
• Site Synch Enabled - User can make enable/disable the feature.
• XCM Controller File Trigger Time - User can define XCM Controller File trigger interval
time in minutes for Site updates which defined on Data Gateway ORD.
• XCM Controller Enabled - User can make enable/disable the feature.
• Data Gateway Ord : By default, it is set to “station:|slot:/Drivers/LogicOneGateway”

NOTE
User can Make Manual invoke also.

29 31-00408-01
Opus Data Aggregator

NOTE:
User can find the SiteSync and XCM Controller file in the Opus Data Aggregator Station Files loca-
tion.

Override option from Opus Data Aggregator Station:

NOTE:
This option is hidden as default. User can utilize this feature by unhiding right click menu Actions.

Schedule:
User can override individual site schedule from Opus Data Aggregator Station.
1. To make the Actions menu enabled, navigate to Slot Sheet-> Commit-> Config Flags, uncheck
the Hidden option.

31-00408-01 30
Opus Data Aggregator

2. Make the changes in Schedule.

(Refer the schedule number in ESS32 APP.)
3. Invoke LogicOne site right click menu-Action

31 31-00408-01
Opus Data Aggregator

4. User can find Commit Regular/IOM2 Schedule option.

5. Invoke Regular Schedule - User get Test Regular pop up window to provide the schedule num-
ber.
6. Provide the Schedule number and Click “Ok” (Refer the schedule number in ESS32 APP.)
The changes will get updated for the assigned Schedule number in the LogicOne executive.

31-00408-01 32
Opus Data Aggregator

Control setpoints:
User can override individual site Control setpoints from OpusDataAggregator Station.
1. Make the changes in Load – Module Load Control settings parameter.

2. To make the Actions menu enabled, navigate to load module-> Slot Sheet-> Commit-> Config
Flags, uncheck the Hidden option.

33 31-00408-01
Opus Data Aggregator

3. Invoke Module Load right click menu -Action and Commit.

31-00408-01 34
Opus Data Aggregator

The changes will get updated for the selected Module load control settings parameters in the
LogicOne executive.

Logicone sites bulk import by using .CSV Import file.

1. Place the logicone site import .CSV file in the below mentioned OpusDataAggregator Station
location.

NOTE
For bulk import .CSV file creation - Refer the document from Installer location “Opus Help”
module folder – “Steps to create .CSV file for logicone site bulk import”.

2. Right click LogiconeGateway and click Action -> Import site.

35 31-00408-01
Opus Data Aggregator

3. Set the .CSV import file location by using Import site browse folder menu option and click “Ok”.

31-00408-01 36
Opus Data Aggregator

4. User can find all Logicone sites got added under LogiconeGateway which extracted from .CSV
file.

37 31-00408-01
Opus Data Aggregator

Opus Magnum Configurations

1. Import Opus Data Aggregator Station under Opus Magnum Supervisor Niagara network.

31-00408-01 38
Opus Data Aggregator

NOTE
Approve the Imported Opus Data Aggregator Station SSL certificate to establish connection
between Opus Data Aggregator station and Opus Magnum Supervisor station.

2. In the Imported OpusDataAggregator Station – Files view, use New button to create Niagara
Import files for SiteSync and XCMController.
Following are the steps to create Niagara Import files for SiteSync and XCMController in Opus
Magnum supervisor:
Site Sync file Creation :
Double click Files in Imported Opus Data Aggregator Station and click New. A New window opens. Click
Ok.

39 31-00408-01
Opus Data Aggregator

Example:
file:^SiteSynchronize/OpusDataAggregatorStation
file:^SiteSYnchronize

XCM Controller file Creation:

Double click Files in Imported OpusDataAggregator Station and click New. A New window opens. Click
Ok.

31-00408-01 40
Opus Data Aggregator

Example:
file:^XCMControllers/OpusDataAggregatorStation
file:^XCMControllers

41 31-00408-01
Opus Data Aggregator

NOTE
In the created SiteSync/XCMController import file, User can define Update time interval as Daily/Inter-
val and Manual to get update.

NOTE
Files get created for SiteSync and XCMController in the below mentioned location. The be-
low folder and files get created based on defined schedule interval update or user manually
invoke Action execute on Files.

NOTE
If the user deletes a Site from the Logicone gateway node, the XMl files created for that site
in the XCM Controller node are not deleted. User must manually delete the XML files for
that Site.

31-00408-01 42
Opus Data Aggregator

Add “OpusProxySiteSyncService” in OpusMagnum Supervisor station services.

NOTE
Use Palette - Opus Supervisor Module - to get “OpusProxySiteSyncService” component.

43 31-00408-01
Opus Data Aggregator

OpusProxySiteSyncService - Use right click menu option and invoke Action – Process Site Sync
File.
This action will help to reflect logicone sites in the Batch Job wizard.

31-00408-01 44
Opus Data Aggregator

Batch Setpoint

45 31-00408-01
Opus Data Aggregator

Batch Schedule

31-00408-01 46
OPUS MAGNUM -USER GUIDE

Not Supported Features:

Batch Schedule Job:

1. Regular Schedule - Alternate schedule feature not applicable for LogicOne site schedules.
2. Special Event “Overnight” feature not applicable for LogicOne site schedules.
3. Special Event “Add” feature not applicable for LogicOne site schedules.
4. Regular Schedule – Only 4 events get applied for a day.
5. IOM2 Schedule - Only 8 events get applied for a day.
6. Special event (Today & Tomorrow) is not applicable for IOM2- weekly schedules
7. IOM2 Schedule - Alternate schedule feature not applicable for LogicOne site schedules.
8. IOM2 Schedule – Exception Schedule feature not applicable for LogicOne site schedules.
9. IOM2 Schedule – Force On/Off - User cannot override from Batch Job. (It’s only Read data)
Batch Setpoint Job:
1. Apply shift feature not applicable for LogicOne sites.

For more information

Honeywell Multisite Page

Honeywell Multisite
6060 Rockside Woods Blvd Suite
Cleveland, OH44131
31-00408 | Rev 1| 09/20
800.348.1235
2020 Honeywell International Inc.
www.novar.com