opus 58 user guide - novar v5-8... · opus supervisor user guide user guide 2/1/2012 3 for the...

USER GUIDE 2/1/2012 1 For the latest technical documentation, visit www.novar.com/manuals

Opus Supervisor User Guide

Table of Contents About Opus ..................................................................................2

Opening the Station......................................................................4

Adding a New Group ...................................................................5

Adding a New Site .......................................................................7

Adding New XCM .......................................................................9

Simulation ....................................................................................13

Adding Network...........................................................................14

Assign XCM IP Address ..............................................................17

Platform Tunneling ......................................................................20

Baseline Configuration ................................................................23

Download .....................................................................................24

Importing Deployed Sites ............................................................26

Backup .........................................................................................29

Restore .........................................................................................33

Adding Template .........................................................................34

Importing a template ....................................................................36

Exporting a template ....................................................................37

Batch Service and Operations ......................................................37

Configuring LDAP in Opus Supervisor .......................................49

Profiled Workbench Single Sign-On ...........................................53

Opus Upgrade Tool ......................................................................54

Customizing Opus ........................................................................56

Quick Connect .............................................................................57

Navigation ....................................................................................60

Disconnect Supervisor .................................................................61

User Management ........................................................................61

About Opus History and Alarms..................................................65

Alarms ..........................................................................................69

Configuring Opus SQL Driver.....................................................76

Conditional Alarm Channels........................................................82

Identifying Opus Control Entities ................................................87

History Configuration ..................................................................88

History View ................................................................................96

Live History View........................................................................100

Boolean Shifted Schedule ............................................................105

Boolean Daily Shifted Schedule ..................................................108

Curve Fit ......................................................................................112

Installing Theater Schedule..........................................................112

Configure Theater Schedule ........................................................113

Using Theater Schedule ...............................................................114

Theater File Requirements ...........................................................117

Thin Client ...................................................................................121

Viewing Hx Profile ......................................................................124


2 USER GUIDE 2/1/2012 For the latest technical documentation, visit www.novar.com/manuals

Opening Supervisor Station .........................................................130

About Opus Schedules .................................................................136

About Opus weekly schedules .....................................................137

Opus Weekly Scheduler view ......................................................139

About Opus weekly shifted schedules .........................................147

Opus Weekly Scheduler view - shifted schedules .......................148

About Opus This document guides you through the installation and configuration of

Novar Opus® Supervisor.

Overview of Opus

The Opus Supervisor is a PC based software application that

provides the necessary functionality for single or multiple users to

configure, deploy, and monitor the Opus control system. Opus

provides a framework that allows you to organize your remote site

controllers in enterprise groups and site groups. This framework

makes it easier to manage hundreds and thousands of sites. You

can create control system configurations and deploy them in XCM

remote site controllers. Post deployment, you can adjust

operational parameters and monitor status of XCM site controllers.

You can use the Opus software as a desktop application as well as

access it through a web enabled portal. Opus also supports a device

driver framework, which enables communications with field

devices through protocols including LonWorks, BACNet, Modbus,

and NovarNet.

This version of Opus provides extended features to aid in the

management of multi-site control and monitoring.

Key features include:

� Manage site and group configuration

� Configure sites offline

� Deploy sites

� Monitor sites remotely

� Receive alarms

� Retrieve Trend logs

Opus provides:

� Graphical environment to program the XCM controllers



� Tree hierarchy to organize the components that are added

� Facility to create backups and templates of the station logic that

can be reused in future

� Ability to simulate the logic before downloading to the

controller

Figure 1

Domain Dictionary

Term Definition

XCM The embedded controller that runs the core runtime station

with direct support for field device integration plus enterprise

LAN connectivity

Fox The proprietary protocol for communication between the Opus

Supervisor and remote Opus XCM controllers.

Station The station provides the environment to configure, manage,

and run control applications and services required for building

management.

Download The process of downloading the control system device specific

and application logic from the Opus Supervisor to the remote

Opus XCM.

Group The logical grouping of sites.

Site The site location name at which you have installed the XCM

controllers.

Simulation The process of simulating an XCM controller station within the

Opus Supervisor.



Opening the Station

The Station is the configuration management server of the Opus

Supervisor. The Opus Supervisor Station provides the environment

to configure, manage, and run a single database of nodes and the

services required to support a control application. The Opus

Supervisor installed on a centralized host PC can support multiple

users managing a common set of group and site configurations.

These users can install the Opus Architect which provides the

client access to this centralized Opus Supervisor. The Opus

Explorer provides Opus Supervisor specific functionality when

connected to the Opus Supervisor station. This functionality does

not exist when connecting directly to an XCM station.

To connect to a running Opus Supervisor station

Step Procedure

1 In left pane of the Profiled workbench, right-click the root node in

Opus Explorer and select Open Station.

The Open Station dialog box appears.

Figure 2



Step Procedure

2 Type the IP address of the Opus Supervisor host computer. The host

computer is the computer on which the Opus Supervisor was

installed.

Figure 3

Note: If you have installed Opus Supervisor, then the host IP is the IP

address of your computer.

3 Type the Username. The default username is admin.

4 Type the Password. The default password is blank.

Note: The Remember these credentials check box is selected by

default.

5 Click OK to open the station. The Group Directory screen appears

in the right pane.

Disconnect Supervisor

To disconnect a Supervisor

Step Procedure

1 Right-click Opus Systems in the Opus Explorer list, in the left pane.

2 Select Disconnect Supervisor from the list. The supervisor is

disconnected.

Adding a New Group

You can create the enterprise hierarchy structure comprising of

groups, sites, and XCM controllers in the Opus explorer. Each

group consists of logically grouped sites. You may create groups

that separate sites by size, region, line of business or any domain

oriented grouping specific to the enterprise. When creating a

group, make sure that the group name is unique and that there are

no spaces in the group name.



You can find all groups that are added to the Opus Explorer under

Opus Systems.

To add a new group

Step Procedure

1 Right-click Opus Systems in the Opus Explorer list and select Add

New Group.

A dialog box appears, prompting you for a Group Name.

Figure 4

2 Type the Group Name.

The next available Group Number is automatically assigned to the

group by the tool.

Note: The group number is a unique number assigned to the group.

You can provide a group number of your choice. If you provide an

existing group number, an error message appears, prompting you to

enter a new number.

3 Click OK. The new group is added under Opus Systems in the Opus

Explorer.

4 Double-click Opus Systems in the Opus Explorer to view the group.

The group name and number is displayed in the right pane.

Or

Expand Opus Systems in the Opus Explorer to view the group you

have added.

Edit group number

You can edit the group number of the new group you have added. Once a

site has been deployed the group number cannot be changed to prevent a

data mismatch between the supervisor and the deployed site XCM

controllers.



To edit the group number of the new group

Step Procedure

1 Right-click the group under Opus Systems and select Property

Sheet. The sheet displays the properties of the group.

Figure 5

Note: You cannot edit the group name.

2 Click Edit next to the Group Number box. A dialog box appears

prompting you to enter the group number.

3 Type the group number of your choice.

4 Click OK. The new group number is updated in the Group Number

box of the property sheet.

5 Click Save on the property sheet to save the changes made to the

group.

Adding a New Site Sites contain logically grouped XCM controllers. Multiple sites are

created together to form a group. A site represents a geographical

location where one or more XCM site controllers are deployed. You may

want the site name to reflect the location for easy identification. When

creating a site, make sure that the site name is unique and that there are

no spaces in the site name.

To add a new site

Step Procedure

1 Expand Opus Systems in the Opus Explorer list.

Figure 6



Step Procedure

2 Right-click the group and select Add New Site. A dialog box appears,

prompting you for the Site Number, State and City.

3 Type the Site Number. The Country is selected as US by default.

Note: The site number is a unique number assigned to the site. You

can provide a site number of your choice. If you provide an existing

site number, an error message appears, prompting you to enter a new

number.

4 Select the State from the list.

5 Type the name of the City in the text box.

6 Click OK. The new site is added under the group node in the Opus

Explorer.

Note: The site name is displayed in the format,

<sitenumber><city><state>.

7 Double-click the group in the Opus Explorer to view the site. The

site number, city, state, and the control system information are

displayed in the right pane.

Or

Expand the group under Opus Systems in the Opus Explorer to

view the site you have added.

Edit site number

You can edit the site number of the new site. Once a site has been

deployed the site number cannot be changed to prevent a data mismatch

between the supervisor and the deployed site XCM controllers.

To edit the site number of the new site

Step Procedure

1 Right-click the site that you want to edit in the Opus Explorer and

select Property Sheet. The sheet displays the properties of the site.

Figure 7

Note: You cannot edit the site name

2 Click Edit next to the Site Number box. A dialog box appears

prompting you to enter the site number.

3 Type the site number of your choice.

4 Click OK. The new Site Number is updated in the site number box

of the property sheet.



Step Procedure

5 Click Save on the property sheet, to save the changes made to the site.

A prominent feature on the property sheet of the site is the auto loading

of State or Province names. When a Country is selected, all the states

and provinces in the country appear in the State or Province list. This

feature currently works if the country is selected as US.

Adding New XCM The Opus XCM controllers are site controllers providing direct support

for field device integration, site level services and enterprise LAN

connectivity. An XCM provides the station environment to add the

controls logic, schedules, alarms and history configurations that are

specific to the target building environment.

In the Opus Explorer, you can create XCM nodes, configure the site

specific application logic while running in simulation within the Opus

Supervisor, and then download the XCM station configuration from the

Opus Supervisor to the XCM site controllers. When creating an XCM,

make sure that the XCM name is unique and that there are no spaces in

the XCM name.

To add a new XCM controller

Step Procedure


Figure 8

2 Right-click the site and select Add New XCM from the list. A dialog

box appears prompting you to enter the XCM Name and XCM

Number.

3 Type the XCM Name.

4 Type the XCM Number.

Note: The XCM number is a unique number assigned to the XCM

controller. You can provide an XCM number of your choice. If you

provide an existing XCM number, an error message appears,

prompting you to enter a new number.



Step Procedure

5 Click OK. An authentication dialog box appears. The default

Username appears as administrator along with a default Password.

6 Click OK.

Note: A station with a default user name admin and a blank password

is created for the XCM controller station.

The XCM controller station is automatically started in simulation

within the Opus Supervisor. An authentication dialog box appears

prompting you to enter the user name and password for the XCM

controller. Once entered, then user will be connected to this simulated

XCM controller station.

7 Type the Username and the Password. Click OK. The new XCM

controller with the station is added under the site node in the Opus

Explorer.

8 Double-click the site in the Opus Explorer to view the XCM

controller. The XCM name, port, and the download status information

are displayed in the right pane.

Or

Expand the site in the Opus Explorer to view the XCM you have

added.

Note: The download status of the XCM controller is displayed as

True, if the XCM station has been downloaded to the remote XCM

controller.

Edit XCM number

You can edit the XCM number of the XCM controller. Once an XCM

has been deployed the XCM number cannot be changed to prevent a data

mismatch between the supervisor and the deployed site XCM controllers.

To edit the XCM number of the XCM controller

Step Procedure

1 Right-click the XCM that you want to edit in the Opus Explorer and

select Property Sheet. The sheet displays the properties of the XCM

controller.

Figure 9

Note: You cannot edit the XCM name.

USER GUIDE 2/1/2012 For the latest technical documentation, visit www.novar.com/manuals

Step

2 Click

prompting you to enter the XCM number.

3 Type the

4 Click

field of the property s

5 Click

XCM controller.

Start/Stop XCM controller station

You can

station. These options are available until after the XCM sta

configuration has been downloaded to the remote XCM.

To stop running the XCM controller station

Step

1 Right

select

2 Click

To resume running the XCM controller station

Step

1 Right

select

prompting for the user name and password for the XCM controller.

2 Ty

NOTE!

XCM AutoDiscovery

Using this feature you can discover all the downloaded XCMs on the

network tha

Step

1 Right


www.novar.com/manuals

Procedure

Click Edit next to the XCM Number. A dialog box appears

prompting you to enter the XCM number.

Type the XCM number of your choice.

Click OK. The new XCM Number is updated in the XCM number

field of the property sheet.

Click Save on the property sheet to save the changes made to the

XCM controller.

You can start and stop the simulation Run Mode of the XCM controller

station. These options are available until after the XCM sta


To stop running the XCM controller station

Procedure

Right-click the XCM you want to stop in the Opus Explorer

select Stop Run Mode. A confirmation message appears.

Click Yes.

resume running the XCM controller station

Procedure

Right-click the XCM you want to resume in the Opus Explorer

select Start Run Mode. An authentication dialog box appears


Type the Username and the Password. Click OK.

The Opus Supervisor can support up to 30 XCM controllers

simultaneously running in the simulation mode.


network that are accessible to the supervisor.

Procedure

Right-click Opus Systems on the Opus Explorer.


11

. A dialog box appears

. The new XCM Number is updated in the XCM number

on the property sheet to save the changes made to the

op the simulation Run Mode of the XCM controller

station. These options are available until after the XCM station


Opus Explorer and

. A confirmation message appears.

Opus Explorer and

. An authentication dialog box appears


The Opus Supervisor can support up to 30 XCM controllers




Step Procedure

2 Select XCM AutoDiscovery from the list. The Import Niagara

Network dialog box is displays the list of downloaded XCMs

accessible by the supervisor.

3 Check the stations you would like to import to your Opus client.

or

Click the Check All button to select all the stations in the list.

Figure 10

4 Click OK. An authentication dialog box appears prompting you for

the user name and the password of the XCM you are importing.

5 Type the Username and Password and click OK. The controller is

displayed in the Opus Explorer of your Opus client.

XCM Auto Discovery Service

You can use this feature to enable XCM Auto Discovery. The

downloaded stations that are discovered are added to the Opus Enterprise

hierarchy if the station is not present in the hierarchy.

To enable XCMAutoDiscoveryService

Step Procedure

1 On the Opus Explorer, browse to the supervisor station and expand it.

2 Expand Config > Services > OpusEnterpriseService and double-click

XCMAutoDiscoveryService.The property sheet of XCM Auto

Discovery Service is displayed on the right pane.

3 Type the Job Trigger Time which is the time in minutes at which the

service discovers the downloaded stations on the network, if enabled.



Step Procedure

4 Set Enabled to True to activate the service.

Figure 11

Using this feature you can perform the following actions.

� Restart Timer - Click this option to restart the timer for the time

set under Job Trigger Time on the property sheet.

� Monitor Now - Click this option to start discovering the

downloaded stations immediately. Irrespective of the time

mentioned under Job Trigger Time on the property sheet, the

stations are discovered and added to the hierarchy.

Step Procedure

1 Right-click XCMAutoDiscoveryService and select Actions to view

the list of actions that you can perform.

Simulation The Opus Supervisor allows you to simulate and test the XCM controller

station configuration before downloading to the remote XCM site

controller. You can provide input values to the control logic to observe

the outputs. You can change the station configuration as needed while in

the simulation mode. The station operates in simulation mode by default

when it first created with the Adding New XCM option. When a station

configuration is downloaded to a remote XCM controller, the simulation

is stopped and is no longer available within the Opus Supervisor. At any

point prior to downloading, you may start and stop an XCM station

simulation with the Start Run Mode and Stop Run Mode menu options

available in the Opus Explorer.



Start/Stop simulation

To start XCM station in simulation mode:

Step Procedure

1 Right-click the XCM controller in the Opus Explorer list.

2 Select Start Run Mode from the list. An authentication dialog box

appears with the default station user name and password.

3 Click OK.

To stop XCM station in simulation mode

Step Procedure


2 Select Stop Run Mode from the list. A confirmation message

appears.

3 Click Yes to stop running the station.

Adding Network A network provides an interface between XCM stations and site field

controllers. You can add the Novar network and the Bacnet network

drivers to the XCM controller station. These drivers identify the XCM

stations and site field controllers on the Novar or Bacnet networks.

To add a Novar network to the XCM controller station

Step Procedure

1 Click Palette at the lower left of the window.

If it is not available, choose Window > Side Bars > Palette from the

toolbar.

Figure 12



Step Procedure

2 Click the Open Palette button on the Palette. The Open Palette

dialog box appears.

Figure 13

3 Select novarNet from the list (if available) and click OK.

or

Click Browse and select the novarNet folder from the File Chooser

dialog box. novarNet appears under Palette in the left pane.

4 Expand Config under the XCM controller station in the Opus

Explorer list in the left pane, to display Drivers.

5 Select NovarnetNetwork from the Palette and drag it to Drivers in

the Opus Explorer.

Figure 14

6 Type a name for the Novar network you are adding and click OK.

Expand Drivers and verify if the Novar network is added.



Adding a Bacnet network

To add a Bacnet network to the XCM controller station

Step Procedure

1 Click the Open Palette button on the Palette. The Open Palette

dialog box appears.

2 Select bacnet from the list (if available) and click OK.

or

Click Browse and select the bacnet folder from the File Chooser

dialog box. bacnet appears under Palette in the left pane.

3 Expand Config under the XCM controller station in the Opus

Explorer list in the left pane, to display Drivers.

4 Select BacnetNetwork from the Palette and drag it to Drivers in the

Opus Explorer list.

5 Type a name for the Bacnet network you are adding and click OK.

Expand Drivers and verify if the Bacnet network is added.

Adding Field Controllers

To add a field controller to the network

Step Procedure

1 Expand Station > Config > Drivers in the Opus Explorer list in the

left pane.

2 Double-click the network under Drivers.

Figure 15



Step Procedure

3 Click the New button in the right pane. A dialog box appears where

the following details can be typed or selected from the list:

� Name: A default name for the controller appears in the text box.

Type a name of your choice.

� Type: A default type of the controller appears in the text box. Select

a type from the list.

� Address: A unique number provided to the controller. If you

provide an existing number, an error message appears stating that

the number is in use.

� Baud Rate: A baud rate is the communications rate to the specific

XCM field controller.

� Enabled: Displays the status of the controller as True or False.

True indicates that the controller is enabled.

4 Click OK. The field controller appears in the Opus Explorer list.

The field controller details are displayed in the view in the right pane.

Editing field controller details

To edit the field controller details

Step Procedure

1 Expand Station > Config > Drivers, under the Opus Explorer list in

the left pane.

2 Double-click the network under Drivers.

3 Select the controller from the right pane.

4 Click the Edit button in the right pane. A dialog box appears with the

controller details.

5 Type a Name of your choice. You cannot edit the Type.

6 Type a unique Address. If you provide an existing number, an error

message appears stating that the number is in use.

7 Select the Baud Rate based on the XCM field controller being used.

8 Select the status as True to enable the controller.

9 Click OK. The controller details are updated in the view.

Assign XCM IP Address

An XCM controller provides the environment to configure the site

controller. Once the XCM IP Address is set, you can connect to the

remote XCM for downloading, configuring or monitoring. You can

specify the IP address of an XCM controller in one of two methods:

� Assign the IP address using the property sheet of the XCM controller.

� Initiate a download to the XCM station to the site controller and

specify the IP address of the site controller.


18

From the Property sheet

To assign an XCM IP address from the property sheet

Step

1 Select the XCM controller in the

2 Right

list. The property sheet of the XCM is displayed in the right pane.

3 Type the IP address of the XCM in the

4 Click

When downloading

To assign an XCM IP address while downloading

Step

1 Select the XCM controller you want to download to the field

controller in th

2 Right

dialog box appears prompting you for the XCM IP address.

3 Type the IP address of the XCM controller to which you are

downloading the station.

4 Click

For more details on downloading, see

Show Platform

Platform provides access to the XCM controller hardware setup and

operating system properties of the XCM site cont

provides you the ability to upgrade the XCM software using the

Commissioning Wizard. These upgrades and property settings should be

established prior to downloading the XCM station configuration.

Accessing the platform is done usin

NOTE!

USER GUIDE For the latest technical documentation, visit www.novar.com/manuals

gn an XCM IP address from the property sheet

Procedure

Select the XCM controller in the Opus Explorer list.

Right-click the XCM controller and select Property Sheet


Type the IP address of the XCM in the XCM IP Address

Click Save on the property sheet.

To assign an XCM IP address while downloading

Procedure

Select the XCM controller you want to download to the field

controller in the Opus Explorer list.

Right-click the XCM controller and select Download


Type the IP address of the XCM controller to which you are

downloading the station.

Click OK. The IP address is saved in the property sheet of the XCM.

For more details on downloading, see Download.


operating system properties of the XCM site controller. This access also




Accessing the platform is done using Show XCM Platform

The Show XCM Platform option is enabled only when the IP

address is assigned to the XCM controller property sheet prior

to the XCM station download.

USER GUIDE 2/1/2012 www.novar.com/manuals

list.

Property Sheet from the


XCM IP Address box.

Select the XCM controller you want to download to the field

Download from the list. A


Type the IP address of the XCM controller to which you are

address is saved in the property sheet of the XCM.


roller. This access also




Show XCM Platform option.

The Show XCM Platform option is enabled only when the IP

address is assigned to the XCM controller property sheet prior



To Access the XCM Platform using Show Platform menu option

Step Procedure


Figure 16

2 Select Show XCM Platform from the list. The XCM controller

station is replaced by the XCM platform.

3 Double-click the platform under the XCM controller. An

authentication dialog box appears with the default XCM platform

name and password.

4 Click OK. The platform objects are displayed in the right pane. These

objects are used for setting the XCM controller configuration.

Figure 17

Returning to Off-line XCM station

To return to an off-line XCM station within the Opus Supervisor

Step Procedure




Step Procedure

2 Select Start Run Mode from the list. The XCM controller station

appears in simulation mode.

3 Download the station to the controller, if necessary.

Platform Tunneling

Opus provides you a feature where an Opus client can establish a

workbench connection to one or more XCMs using a connection that is

established using a Supervisor station. This is done by allowing the

requesting station (client) to communicate through a Supervisor station

that has a connection to the XCMs and acts as a proxy server for those

targeted hosts. This feature is called Platform tunneling. The figure

below provides an overview on platform tunneling.

Figure 18

In Supervisor Station

To enable Platform tunneling in the Supervisor station

Step Procedure

1 Expand Station > Config > Services in the Supervisor station in the

Opus Explorer list.



Step Procedure

2 Right-click WebServices and select Views > Opus Property Sheet.

The property sheet of Web Service is displayed on the right pane.

Figure 19

3 Under Tunneling Enabled, select true to enable platform tunneling.

In XCM

To enable Platform Tunneling in XCM

Step Procedure


2 Right-click the XCM and select Property Sheet. The property sheet

of the XCM is displayed on the right pane.

Figure 20

3 Under XCM IPAddress, type the IP address of the XCM. For

example, type 199.63.214.115.


22

Step

4 Under

platform. For example, type

NOTE!

Opening Tunneled Station

Step

1 In left pane of the P

Opus Explorer

dialog box appears.

2 An authentication dialog box appears with the default station user

name and password.

3 Click


Procedure

Under Tunnel Platform Port, type the port number of the tunneled

platform. For example, type 8080.

Opus client can establish a workbench connection to one or

more XCMs using NAT (Network Address Translation) IP. A

NAT IP acts as an alias IP address which the Opus client uses

to communicate to the XCM through Opus Supervisor.

Procedure

In left pane of the Profiled workbench, right-click the root node in

Opus Explorer and select Open Station Tunnel. The

dialog box appears.

Figure 21

An authentication dialog box appears with the default station user

name and password.

Figure 22

Click OK.


, type the port number of the tunneled

connection to one or

more XCMs using NAT (Network Address Translation) IP. A

NAT IP acts as an alias IP address which the Opus client uses

to communicate to the XCM through Opus Supervisor.

click the root node in

. The Open Station

An authentication dialog box appears with the default station user



Opening Tunneled XCM

Step Procedure


2 Select Start Run Mode from the list. An authentication dialog box

appears with the default station user name and password.

Figure 23

3 Click OK.

Baseline Configuration

The Opus Supervisor provides you the feature of creating a new XCM

controller detailed in the Adding New XCM help page. When you invoke

the 'Add New XCM' menu command a new XCM station is created from

an internal Baseline XCM configuration. This initial Baseline

configuration has only the minimum configuration structure. This

Baseline Configuration option allows you to replace the internal Baseline

XCM configuration with one that you have customized with pre-set

configurations that you would like to have established at the time of

creation of a new XCM.

To establish a new baseline to the XCM

Step Procedure

1 Double-click an offline or non-deployed XCM controller in the Opus

Explorer list whose configuration you want to be set as the new

baseline.

2 Click the ChangeBaseLine button on the toolbar. A confirmation

message appears.

3 Click Yes.



The Opus Supervisor will now use this new XCM Baseline configuration

when the 'Add New XCM' menu command is invoked.

The baseline configuration files are stored in the Opus Supervisor

in the BasicStation folder in the following path:

Drive:\Novar\Opus-5.x\stations\OpusSupervisorStation\resources.

When the baseline configuration is changed, a backup of the

original baseline configuration files is moved into the

BackupOfBasicStation folder also under the resources folder. To

restore to a previous Baseline, you can select all the files from a

backup and copy back into the BasicStation folder.

Download When you have completed the site specific configurations of the XCM

station within the Opus Supervisor you can initiate the download to the

XCM controller. The download XCM option automates the process of

transferring the XCM station configuration created in the Opus

Supervisor to a remote XCM site controller. Upon completion of the

transfer, the remote XCM site controller will contain and execute the

controls application you configured. The XCM station is no longer

resident in the Opus Supervisor but a link exists that allows you

seamlessly navigate and connect to the deployed XCM.

To download a station

Step Procedure

1 Right-click the XCM controller under the site in the Opus Explorer

list.

Figure 24

2 Select Download from the list. If the XCM station does not have an

IP Address specified in the property sheet, a dialog box appears

prompting you to type the IP address of the XCM site controller.

3 Type the IP address of the XCM field controller to which the station

needs to be downloaded.



Step Procedure

4 Click OK. A message box appears with the list of the steps performed

during to accomplish the download.

Figure 25



Step Procedure

5 Click Yes to proceed with downloading the station. A different

message box appears which displays the status of the steps being

performed. The following list shows the steps performed during the

download.

� Stop Simulated Station: If the selected XCM station is in the Run

Mode within the Opus Supervisor, the XCM station is stopped.

� Connect to XCM Platform: A connection dialog to the selected

XCM station is displayed prompting the user the XCM platform

username and password.

� Stop Existing XCM Station: If an XCM station is currently

running in the remote XCM controller, this station is stopped.

� Delete Existing XCM Station: If an XCM station currently exists

in the remote XCM controller, this station is deleted.

� Software Dependency Check: The XCM station configuration

entries you added have dependencies on certain software modules,

referred to as JAR files. In this step the download examines the

remote XCM controller to ensure it has all the required JAR files

loaded. If not, the user will be prompted to approve the missing JAR

files to be sent to the remote XCM controller.

� Download XCM Station: The XCM station configuration files

within the Opus Supervisor are transferred to the remote XCM

controller.

� Reboot XCM: The XCM controller is rebooted.

� Start XCM Station: The XCM station downloaded to the XCM

controller is started and the Opus Supervisor automatically re-

establishes a connection. Click OK on the authentication dialog box

which has the default user name and password of the station.

� Backup XCM Station: A backup of the XCM station configuration

is automatically performed after the download. This provides you

with a full configuration backup in the event the remote XCM

controller needs to be restored.

Note that the download status window messages provide the

following states:

� When the step is not initiated, the status is displayed as Not

Started.

� When the step is being performed, the status is displayed as

Running.

� When the step is completed successfully, the status is displayed as

Success.

6 Click Close on the message box when the download is complete.

Importing Deployed Sites

The Opus Supervisor provides a feature to import an XCM controller

station configuration from a remote XCM that has already been

deployed. This is done by using the Import XCM Station option. You can



import XCM stations that have been downloaded with a current Opus

Supervisor and also those that were deployed with Opus Supervisor prior

to version 5.0.2. Those prior to this version do not have the multi-site

enterprise component configuration. Note below the Import XCM

Station menu command behaves differently for these two scenarios.

To import an XCM controller station into the Opus Supervisor

Step Procedure

1 Right-click Opus Systems node in the Opus Explorer, in the left

pane.

Figure 26

2 Select Import XCM Station from the list. The Open Station dialog

box appears.

3 Type the IP address of the remote XCM whose station needs to be

imported.


5 Type the Password. The default password for the username admin is

blank.

6 Click OK.


default.

If the remote XCM has been deployed with Opus Supervisor prior to

5.0.2 follow steps 7 through 13, otherwise skip to step 14 below.

7 The Import Deployed XCM dialog box appears.



Step Procedure

8 You need to supply the Group, Site and XCM name and numbers for

this remote XCM.

Figure 27

9 Type the group name and number in the Group Name and Group

Number text boxes.

10 Type the site number in the Site Number text box. The Country is

selected as US by default.

11 Select the State or Province from the list.

12 Type the name of the City in the text box.

13 Type the XCM name and number in the XCM Name and XCM

Number text boxes.

14 Click OK. The XCM station is imported to the Opus Supervisor

station within the specified multi-site enterprise components.

Note: This XCM station configuration has been imported into the

Opus Supervisor as a non-deployed site. You need to proceed to

Download the XCM so it will have the multi-site enterprise

components resident in the XCM.

Figure 28

If the remote XCM has been deployed with Opus Supervisor on or

after version 5.0.2.



Step Procedure

15 The remote XCM station configuration is imported into the Opus

Supervisor as being already downloaded.

Figure 29

You are not required to re-download this remote XCM station as it

already has the multi-site enterprise components.

Backup Once an XCM site controller has been downloaded, the supervisor

considers the configuration in the remote XCM controller to be the

master copy. The supervisor no longer maintains a synchronized copy of

the configuration files. As you access the XCM site controller and make

adjustments, those changes are only persisted to the XCM controller. The

remote XCM controllers can have their current station configuration files

backed up into the supervisor. The backup process will connect to the

remote XCM controller, collect all the configuration files archive these

files into a single file and store within the Opus Supervisor. These

backups allow you to capture the configurations that may change over

time and are able to restore a configuration to the remote XCM controller

if needed. Periodic backups should be performed to ensure the latest

configurations are backed up. The supervisor provides backup services

that allow the configuration files to be archived, either manually or based

on a time schedule, into the supervisors file system.

Manual Backup

To take a manual backup of the XCM controller station

Step Procedure


2 Select Backup From XCM from the list.

3 Click OK on the message box. A progress bar appears which displays

the percentage of progress of the backup being taken.

4 Click OK on the message box. The backup file appears in the default

Backups folder under the downloaded station.

The number of backup files that can be stored in the Backups folder

depends on the value mentioned in the site property sheet under the field

Maximum No Of Backup Files. On exceeding the maximum number of

backup files, the next backup file overwrites the earliest backup file in

the folder.



Scheduled Backup

To take a scheduled backup of the XCM controller station

Step Procedure

1 Expand Global Services in the Opus Explorer list.

2 Right-click BackupSchedules and select NewBackupSchedule. A

dialog box appears.

Figure 30

3 Type a name for the backup folder in the dialog box and click OK.

4 Expand BackupSchedules to view the backup folder you have just

created.

5 Expand the backup folder you have just created to view the two

options for schedule backup, TriggerSchedule and

NiagaraNetworkJobPrototype.

Figure 31



Backing Up using the Trigger Schedule option

You can use the Trigger Schedule option to initiate a scheduled

backup.

Step Procedure

1 Double-click Trigger Schedule under Global Services in the Opus

Explorer list. The trigger schedule appears in the right pane.

Figure 32

2 Click the Add button at the lower-left of the screen. The Add dialog

box appears.

3 Type the Name for the schedule event.

4 Select the period as Date/Date Range/Week And Day/Custom type

from the Type list.

Based on the type selected for the schedule, select the date or period

of the event.

5 Click OK. The event and the period are displayed in the view under

Name and Summary fields.

6 Select the time of the event on the lower-right of the screen.

Or

Select Range to provide the time range and interval of the event.

7 Click the Add button. The time appears in the view.

8 Select the time provided in the view and the event name and date.

9 Click the Save button on the screen. The schedule date and time is

updated in the tool. A backup of the station is taken at the schedule

date and time.


32

NOTE!

Backing Up using the Niagara Network Job Prototype option

You can use the Niagara Network Job Schedule option to take a

scheduled backup.

Step

1 Double

the

The schedule appears in the right pane.

2 Click the

Job Step

3 Select the

the view under

4 Click the

Device

supervisor.

5 Check the devices to be added to the job and click

controllers selected appear in the view under

the job.

6 Click

7 Click the

station immediately.

8 Right

Opus Explorer

9 Select


The Trigger Schedule screen provides a view of the calendar.

The scheduled dates are highlighted in green in the calendar


scheduled backup.

Procedure

Double-click NiagaraNetworkJobPrototype under Global Services

the Opus Explorer list.

The schedule appears in the right pane.

Figure 33

Click the Add button under Steps to run for each station. The

Job Step dialog box appears.

Select the Backup Stations type and click OK. The type appears in

the view under Steps to run for each station.

Click the Add button under Stations to include in the job. The

Device dialog box appears with all the XCM controllers in the

supervisor.

Check the devices to be added to the job and click OK

controllers selected appear in the view under Stations

the job.

Click Save to save the controllers selected for the job.

Click the Run Now button to take a backup of the XCM controller

station immediately.

Right-click the Backups folder under the XCM controller in the

Opus Explorer list.

Select Sync to view the backup file.


The Trigger Schedule screen provides a view of the calendar.

en in the calendar.


Global Services in

button under Steps to run for each station. The New

. The type appears in

to include in the job. The Add

dialog box appears with all the XCM controllers in the

OK. The XCM

Stations to include in

to save the controllers selected for the job.

button to take a backup of the XCM controller

lder under the XCM controller in the



Restore Backup files contain remote XCM station configuration. These files are

periodically captured into the Opus Supervisor to ensure the latest

configuration changes are archived. In the event that a remote XCM

controller was to be replaced, these backup files can be used to restore

the latest XCM station configuration back into the remote XCM

controller. Backup files can be restored using the Restore To XCM

menu option available in the Opus Explorer.

Restore To XCM The Restore To XCM option allows you to restore the selected backup

file into the XCM site controller.

To restore the backup file

Step Procedure

1 Using the Opus Explorer navigate to and expand the deployed XCM

node.

2 Select and expand the Backups folder.

3 Select and right-click the backup file you want to restore and select

Restore To XCM. A list of backup files appears in the right pane.

Figure 34

4 Select the file from the list that needs to be restored and click the

Install button in the view. The Distribution File Installer dialog box

appears.

5 Click Next on the dialog box and click Finish. The following tasks

are performed during the restore:

� Stop running application(s): An existing remote XCM controller

station is stopped.

� Install software: The backup files are installed into the remote

XCM controller.

� Reboot host: The XCM controller is restarted.

6 Click Close on the message box when the installation is complete.

The remote XCM controller may take a few minutes to restart.



Restore For Re-Download

The Restore For Re-Download option allows you to convert the

selected backup file into a non-deployed, offline XCM station within the

Opus Supervisor. This would be used if you wanted to make XCM

station configuration changes within the supervisor prior to re-

downloading back to the remote XCM controller.

To restore using Restore for Re-Download

Step Procedure

1 Using the Opus Explorer navigate to and expand the deployed XCM

node.

2 Select and expand the Backups folder.

3 Right-click the backup file you want to restore and select Restore

For Re-Download. This makes the XCM station a non-deployed

XCM station in the supervisor.

4 The XCM station is started in the Simulation mode where you can

access to make necessary configuration changes.

5 Once changes are complete, you proceed to do Download to the

remote XCM controller.

Adding Template The Opus Supervisor provides a Template Library. You can customize

the template library with folders to catalog your templates into logical

groups or categories. Templates are created as pre-set configurations that

will be available for quick reuse in a future site configuration. A template

can be a site template which contains the configuration from the site

level down inclusive of one or more XCM site controllers configured

under that selected site. This includes all control logic and all custom

views created under the selected node. A template could also be made

from the XCM controller level as the top level node. Also, a template

could be made from some controller configuration sub-system within an

XCM controller. This subsystem might be a field controller network or a

custom strategy created within a wiresheet.



To create a Template Folder in Opus

Step Procedure

1 Right-click OpusTemplates in the Opus Explorer list and select

Add Template Folder. The New Template Folder name dialog box

appears.

Figure 35

2 Type a name for the new template folder.

3 Click OK. The folder appears in the Opus Explorer list under

OpusTemplates.

Note: Do not add space between the letters of the folder name.

Adding to a template folder

To add a template to a template folder in Opus

Step Procedure

1 In the Opus Explorer, navigate to the site, XCM or the configuration

sub-system that you want to add as a new template.

2 Drag the selection from the Opus Explorer into the template folder

you have just created. The selected configuration is collected into a

single file and stored as a template in the template folder.

Reusing a template

To reuse a existing template in Opus

Step Procedure

1 Navigate to and select a template in template library.

2 Drag the template from the template folder into the target location

within the Opus Explorer. A site template can be dropped under an

existing Group node. An XCM template can be dropped under an

existing Site node. A controller sub-system can be dropped under an

existing XCM station.

3 When dropping a site template, you will be prompted to supply

unique site information. When dropping an XCM template, you will

be prompted to supply unique XCM information.

4 Click OK. The new configuration is added under the target node in

the Opus Explorer.


36

NOTE!

Importing a template

Templates created within the Template Library can be shared with others

that may no

template. You can use a template from a different Opus Supervisor by

using the Import Template feature to import a template from a file

location on your computer or a shared file server location.

templates can then be imported into a Template Library folder within

your Opus Supervisor.

To import a template

Step

1 Navigate to and right

Templates

2 Select

appears.

3 Select the file you want to import to the template folder and click

Open

confirmation message appears.

4 Click

NOTE!


If you provide an existing site or XCM number, an error

message appears, prompting you to enter a new number.


that may not have access to the same Opus Supervisor that contains your



location on your computer or a shared file server location.


your Opus Supervisor.

Figure 36

To import a template

Procedure

Navigate to and right-click the target template folder in the

Templates folders.

Select Import Template from the list. The File Chooser

appears.

Select the file you want to import to the template folder and click

Open. The template is imported to the import folder and a

confirmation message appears.

Click OK.

If the import fails, an error message appears stating that the

template already exists.


If you provide an existing site or XCM number, an error

message appears, prompting you to enter a new number.


t have access to the same Opus Supervisor that contains your



location on your computer or a shared file server location. These


click the target template folder in the Opus

File Chooser dialog box

Select the file you want to import to the template folder and click

. The template is imported to the import folder and a

If the import fails, an error message appears stating that the


Exporting a template


that may not have access to the same Opus Supervisor that contain

template. You can use the Export Template feature to export a template

to a file location on your computer or a shared file server location for

purposes of distribution. These templates can then be imported into a

separate instance of an Opus Superv

To export a template

Step

1 Expand the templates folder in the

2 Navigate to the template you want to export.

3 Right

The

4 Select the folder to which you want to export the template and click

Save

5 Click

NOTE!

Batch Service and Operations

Opus supervisor allows you to apply common setpoint changes or




that may not have access to the same Opus Supervisor that contain




separate instance of an Opus Supervisor for reuse.

Figure 37

To export a template

Procedure

Expand the templates folder in the OpusTemplates.

Navigate to the template you want to export.

Right-click the selected template and select Export Template

The File Chooser dialog box appears.

Select the folder to which you want to export the template and click

Save. A confirmation message appears.

Click OK to export the file to the desired folder.

If the export fails, an error message appears stating that the

template is not exported.



37


that may not have access to the same Opus Supervisor that contains your




Export Template.

Select the folder to which you want to export the template and click

rs stating that the



38

schedule changes across multiple sites. You can select one or more

control entities from these sites and create batc

changes. A historical report of the batch jobs is generated at the end of

every job.

The tool provides you with options to select the groups, sites, XCMs, and

field controllers to which changes need to be made. You can add, view,

edit

Batch Service A downloaded Supervisor station contains a default service called

OpusBatchService. You can enable the service to run at intervals and

update the schedule and setpoint entities.

To access the batch service

Step

1 On the Opus Explorer, expand

view the supervisor station.

2 Expand Station>Config>Services to view the OpusBatchService

option.

3 Double

service is displ

NOTE!



control entities from these sites and create batch jobs to perform the


every job.



edit, and delete these batch jobs.

A downloaded Supervisor station contains a default service called


update the schedule and setpoint entities.

To access the batch service

Procedure

On the Opus Explorer, expand Opus Systems>group>site>XCM

view the supervisor station.

Expand Station>Config>Services to view the OpusBatchService

option.

Double-click OpusBatchService. The property sheet of the batch

service is displayed on the right pane.

Figure 38



h jobs to perform the




A downloaded Supervisor station contains a default service called


Opus Systems>group>site>XCM to

Expand Station>Config>Services to view the OpusBatchService

click OpusBatchService. The property sheet of the batch



You can add the OpusBatchService feature under the

supervisor station, if it is not displayed under services.

To add the OpusBatchService feature

Step Procedure

1 On the Palette, click the Open Palette button. The Open Palette dialog

box appears.

2 Browse to OpusEnterprise and click OK. The contents of the Opus

Enterprise folder appear under Palette.

3 Drag OpusBatchService under Services.

The property sheet of the batch service provides information on the scan

time, status of the batch service (enabled or disabled), and the supervisor

station on which the service is running.

The following fields are available on the property sheet of

OpusBatchService.

� Update Scan Trigger Time: You can set the time duration in

minutes at which the service runs on the supervisor station. The

default value is 1minute.

� Enabled: Setting this parameter to True enables the batch service

feature. If this parameter is set to False, the service will not run.

� Supervisor Station: You can select the supervisor station from

the list on which the batch service will run.

The following options are available when you right-click

OpusBatchService and select Actions.

� Restart Timer: This option updates the Update Scan Trigger

Time that has been set to run the service.

� Force Update: This option updates the batch setpoint and

schedule entities on the selected supervisor station.

Batch Setpoint A setpoint control entity must be selected and configured to the field

controller on the Novarnet network.

To configure a site control entity

Step Procedure

1 Drag a Novarnet Network from the Palette on to the Opus Explorer,

under the OpusSupervisorStation > Config > Drivers.

See Adding Network for more details on adding a Novarnet Network.

2 Add a field controller to the network.

See the "Adding Field Controllers" section of Adding Network for

more details on adding a field controller.



Step Procedure


box appears.

4 Browse to OpusEnterprise and click OK. The contents of the Opus

Enterprise folder appear under Palette.

5 Drag OpusControlEntity onto the field controller you have added on

the Opus Explorer.

A dialog box appears prompting you for a name for the control entity.

6 Type the name of the control entity in the text box and click OK.

7 Double-click the field controller. The property sheet of the field

controller is displayed on the right pane.

The Opus Control Entity you have added is displayed on the property

sheet.

8 Select the control entity type from the list and click Save. The control

entity is configured to the selected type.

9

Figure 39

Now you need to select the setpoint components to which setpoint

changes need to be made. These setpoints are added to a batch.

To add the setpoint components to a batch

Step Procedure

1 On the Opus Explorer, expand Load under the field controller.



Step Procedure

2 Right-click Control Settings and choose Views > Opus Slot Sheet.

Figure 40

3 Select the setpoint components from the slot sheet that needs to be

added to the batch setpoint list.

4 Click SlotSheet on the menu bar and select Add for Batch. A dialog

box appears prompting you for the parent control entity.

By default the control entity you have added is displayed in the text

box.

Figure 41

5 Click OK to add the batch containing the selected slots to the control

entity.

6 From the Opus Enterprise on the Palette, expand OpusEnterprise >

OpusEnterpriseServiceProperty.

7 Drag OpusBatchService under OpusEnterpriseServiceProperty onto

Station > Config > Services.



To create Batch Setpoints for batch setpoint changes

Step Procedure

1 Click the Batch Setpoint button

on the toolbar. The Batch Setpoint Jobs screen is displayed on

the right pane.

2 Click the New button on the screen to add a new setpoint job. The

Batch Setpoint screen is displayed.

Figure 42

3 Type the Job Name and the Job Description in the text boxes.

4 Select the groups from the list. The list of sites under the selected

groups is displayed under Site.

5 Select the categories from the list. The list of sites under the selected


6 Select the sites from the list. The list of XCMs under the selected sites

is displayed under XCM.

7 Select the XCMs from the list. The list of field controllers under the

selected XCMs is displayed under Controller.

8 Select the field controllers from the list whose setpoints need to be

changed.

or

Select the text box and type the first few characters of the controller

name followed by a * or ? to select all the controllers starting with the

provided characters.

9 Click Next. The Batch Setpoint screen displays the Batch setpoint

components.



Step Procedure

10 Type the setpoint value in the text box for each of the components

and check the box next to the text box to select it.

Figure 43

Note: If the component is not selected, the setpoint values are not

updated to the selected controllers.



Step Procedure

11 Click Run Now to update the selected setpoint components with the

new value.

The Executing Job screen displays the status of the task.

or

Click Schedule Later to schedule the setpoint job.

You can add an event using the Add button and schedule the time at

which the setpoint job must be performed.

Figure 44

12 Click Home to return to the Batch Setpoint Jobs screen. The setpoint

job is added to the list.

Figure 45

Note: The View/Edit button is provided to edit a setpoint job. A job

can be deleted from the list using the Delete button.



Step Procedure

13 Click the job in the list to view the Batch Job History screen. The

screen displays the list of jobs that are executed until that instance.

The execution time and status of the executed setpoint jobs are

displayed.

Figure 46

14 Click the job in the job history list to view the details of the executed

job in the Batch Job History screen.

Figure 47

15 Click Home to return to the Batch Setpoint Jobs screen.

or

Click Back to return to the previous screen.

Batch Schedule

A schedule entity must be selected and configured to the field controller

on the Novarnet network.



To configure a schedule entity

Step Procedure

1 On the Opus Explorer, right-click Novarnet Network and select New

> Folder.

A dialog box appears prompting you for the folder name.

2 Type the folder name in the text box and click OK.


box appears.

4 Browse to Schedule and click OK.

The various schedule types such as Booleanschedule, Enumschedule,

Numericschedule as so on appear under Palette.

5 Drag the schedule types that require batch scheduling, onto the folder

you have created on the Opus Explorer.

Figure 48


box appears.

7 Browse to OpusEnterprise and click OK.

8 Drag an OpusScheduleEntity under each of the schedule types in the

folder on the Opus Explorer.

A dialog box appears prompting you for a name for the schedule

entity.

9 Type the name of the schedule entity in the text box and click OK.

10 Right-click a schedule type such as Booleanschedule, on the Opus

Explorer and choose Views > Opus Property Sheet.

The property sheet on the right pane displays the Opus Schedule

entity in the list.



To create Batch Schedules for batch schedule changes

Step Procedure

1 Click the Batch Schedule button on the toolbar. The Batch

Schedule Jobs screen is displayed on the right pane.

2 Click the New button on the screen to add a new schedule job. The

Batch Schedule screen is displayed.

Figure 49

3 Type the Job Name and the Job Description in the text boxes.

4 Select the groups from the list. The list of sites under the selected


5 Select the categories from the list. The list of sites under the selected

categories is displayed under the Site box.

6 Select the sites from the list. The list of XCMs under the selected sites

is displayed under XCM.

7 Select the XCMs from the list. The list of field controllers under the

selected XCMs is displayed under Controller.

8 Select the field controllers from the list whose setpoints need to be

changed.

or

Select the text box and type the first few characters of the controller

name followed by a * or ? to select all the controllers starting with the

provided characters.

9 Select the Special Events check box to schedule events to be

performed on a specific day.

10 Click Next. The BatchSchedule screen displays the weekly schedules

set for the selected field controllers.

The schedules that are active, display the status True.



Step Procedure

11 Select the time duration for a day on the Batch Schedule screen, to set

a batch schedule.

Figure 50

12 Click Run Now to update the schedule to the selected controllers. The

Executing Job screen displays the status of the task.

or

Click Schedule Later to update the schedule at a specified time.

You can add an event using the Add button and schedule the time at

which the schedule job you have set must be updated.

Figure 51

13 Click Home to return to the Batch Schedule Jobs screen. The schedule

job is added to the list.

Note: The View/Edit button is provided to edit a setpoint job. A job

can be deleted from the list using the Delete button.


Step

14 Click the job in the list to



displayed.

15 Click the job in the job history list to view the details of the


16 Click Home to return to the Batch Schedule Jobs screen.

or


Configuring LDAP in Opus Supervisor

Opus supports LDAP authentication where the user can connect to

Opus Supervisor station and access the details of any XCM, with single

supervisor credentials. For example, if the Supervisor station is

configured for LDAP, the user can access the XCM details under the

Supervisor station, without logging in to each

NOTE!

In Supervisor Station

Configuring the LDAP in Supervisor Station

Step

1 Connect to a running Opus Supervisor station as an administrator.

See

2 Expand

left pane.



Procedure

Click the job in the list to view the Batch Job History screen. The



displayed.

Click the job in the job history list to view the details of the


Click Home to return to the Batch Schedule Jobs screen.

or


Opus supports LDAP authentication where the user can connect to




Supervisor station, without logging in to each individual XCM.

Opus supports both local and remote LDAP users.

Configuring the LDAP in Supervisor Station

Procedure

Connect to a running Opus Supervisor station as an administrator.

See Opening the station section for more details.

Expand Station > Config > Drivers in the Opus Explorer list in the

left pane.


49

view the Batch Job History screen. The



Click the job in the job history list to view the details of the executed

Click Home to return to the Batch Schedule Jobs screen.

Opus supports LDAP authentication where the user can connect to the




individual XCM.

oth local and remote LDAP users.

Connect to a running Opus Supervisor station as an administrator.

in the Opus Explorer list in the



Step Procedure

3 Right-click NiagaraNetwork and select Views > Opus Property

Sheet. The property sheet of Niagara Network is displayed on the

right pane.

Figure 52

4 Expand Fox Service and under Authentication Policy select Basic.

Figure 53



Step Procedure

5 Open the ldap module in the palette.

Figure 54

6 Right-click LdapUserService and select Copy.

7 Paste the LdapUserService under Station > Config > Services.

8 Right-click UserService and select Delete.

9 Configure the LDAP server.

10 Expand Station > Config > Services > LdapUserService > User

Prototypes in the Opus Explorer list in the left pane.

11 Right-click Default Prototype and select Views > Opus Property

Sheet. The property sheet of Default Prototype is displayed on the

right pane.

Figure 55

12 Under Permissions, select the Super User check box.

13 Click Save to save the changes made to the Default Prototype.

14 Right-click the Opus Supervisor station and select Save Station.

15 Right-click the Opus Supervisor station and select Close.

16 Login to the station as an LDAP user.



Configuring LDAP Server

Configuring the LDAP Server

Step Procedure

1 Expand Station > Config > Services > LdapUserService in the

Opus Explorer list in the left pane.

2 Right-click LdapConfig and select Views > Opus Property Sheet.

The property sheet of Ldap Config is displayed on the right pane.

Figure 56

3 In the Connection Url box, enter the URL of the LDAP server.

4 In the Connection User box, enter the username which is used to

login to the LDAP server.

5 In the Connection Pwd box, enter the password for the connection.

6 SSL has two properties "True" and "False". Setting SSL "True" will

make the user information private, such as user passwords that are

sent over the network between the LDAP directory and Opus

Supervisor (or) XCM. Setting "False" will not be secure and LDAP

password can be accessed through Network. In default it will be

False.

If we use https we need to ensure that SSL also to be in secure.SSL

requires a special license option which must be provided per request.

Inside the Firewall SSL might not be required and the property can be

set as false.

7 In the User Base box, enter the domain server components.

8 In the Attr Email box, enter the e-mail address of the user.

Note: In the Connection User field, enter the correct attributes while

configuring the LDAP server.

After the Supervisor Station is configured for LDAP, if a new XCM is

added, the LDAP is automatically configured on the new XCM.


Profiled Workbench Single Sign-On

The Single Sign

with single Supervisor credentials.

Configuring the Supervisor station for Profiled Workbench Single Sign

Step

1 In the Opus Explorer list, expand

2 Select

displayed on the right pane.

3 Under

4 Click

5 In t

6 In the

7 In the

Note



The Single Sign-On (SSO) feature allows a user to login to any XCM,

with single Supervisor credentials.

Configuring the Supervisor station for Profiled Workbench Single Sign-On

Procedure

In the Opus Explorer list, expand Station and right-click

Select Views > Property Sheet. The property sheet of Config is


Figure 57

Under Sys Info, click . The Config Facets dialog box opens.

Figure 58

Click to add a new facet row.

In the Key box, click and select realms.

In the Type box, click and select String.

In the Value box, type the name of the realm.

Note: The realm value must be the same for all stations.


53

eature allows a user to login to any XCM,

On

click Config.

. The property sheet of Config is

dialog box opens.

: The realm value must be the same for all stations.



Step Procedure

8 Click OK to add the facet.

Figure 59

After the Supervisor Station is configured for SSO, if a new XCM is

added, the SSO is automatically configured on the new XCM.

Opus Upgrade Tool

Opus provides you a set of tools to detect and upgrade existing Opus

configurations and data from a previous Opus version (Opus 5.2, 5.4, 5.5

and 5.6) to Opus 5.8. You can upgrade the following configuration items:

� Enterprise hierarchy and stations

� Niagara network devices

� RDBMS network (SQL drivers)

� User service (login profiles)

� Global services

� Batch job service

� Opus alarm service

� Opus history service

� Templates library

� Missing modules

� Alarm Viewer user settings

� History Viewer user settings

� Opus client themes

� Niagara users and their credentials

� Supervisor PX files

� Supervisor image files

� Supervisor HTML files

� XcmLCD images

� Email Service

� Report Service

� TimeSync Service


To upgrade the OPUS Supervisor configuration

NOTE!

Step

1 On the menu bar, click

Upgrade Locations

2 In the Previous Installation directory box, click

Directory Chooser

3 Navigate to the folder where a previous instance of Opus Supervisor

is installed.

Note

different host PC, then you need to map the drive in which it is

installed and then navigate to the folder containing the previous

instance of Opus Supervisor.

4 In the

Directo

5 Navigate to the folder where the current instance of Opus Supervisor

is installed.



� Category Service

� LDAP User Service

� TomcatWeb Service

� Web Service

� Weather Service

� AutoDRSupervisor Service

To upgrade the OPUS Supervisor configuration

Before upgrading the Opus configurations, ensure that you have

stopped the Supervisor station in both the current and previ

versions of Opus supervisor.

Procedure

On the menu bar, click Tools > Opus Upgrade Tool. The

Upgrade Locations dialog box appears.

Figure 60

In the Previous Installation directory box, click Choose

Directory Chooser dialog box appears.

Navigate to the folder where a previous instance of Opus Supervisor

is installed.

Note: If the previous version of Opus Supervisor is installed in a



instance of Opus Supervisor.

In the Current Installation directory box, click Choose

Directory Chooser dialog box appears.

Navigate to the folder where the current instance of Opus Supervisor

is installed.


55

onfigurations, ensure that you have

stopped the Supervisor station in both the current and previous

. The Opus

Choose. The

Navigate to the folder where a previous instance of Opus Supervisor

rvisor is installed in a



Choose. The

Navigate to the folder where the current instance of Opus Supervisor



Step Procedure

6 Click Next. The Opus Upgrade Steps dialog box appears. By

default, all the options are selected.

Figure 61

7 Select the required configurations to be upgraded and click Start

Upgrade.

8 The selected configuration items are imported from the previous

installation to the current installation.

Figure 62

9 Click Save Report to save the report in a desired output format.

Customizing Opus You can customize the font and color schemes in Opus using the Style

Configurator option. The screens can be set to different colors and fonts

based on your selection.

Use the following procedure to customize your Opus client.



Step Procedure

1 Click on Settings on the menu bar.

2 Select Style Configurator from the list. The Style Configurator dialog

box appears.

Figure 63

3 Select the colors, font sizes and styles you would like to set for your

Opus screen.

4 Click Save to save the changes.

� Click Preview. A preview of the selected settings is displayed on

the screen.

� Click Reset Styles. The screen colors, styles, and fonts are reset to

the last saved settings.

� Click Default Styles. The screen colors, styles, and fonts are set to

the default settings that come with Opus profile workbench.

� Click Cancel. The last saved screen settings are restored and the

Style Configurator dialog box is closed.

Quick Connect The Opus Supervisor provides a Quick Connect feature to quickly

connect to a downloaded remote XCM station. This feature is invoked

using an easily accessible toolbar icon. If you know the site number of

the XCM station you need to connect to, using this feature will provide a

method to supply this site number and be automatically connected and

routed to the remote XCM. This eliminates the need to use the hierarchal

Navigation options in the Opus Supervisor.

To connect to a station using Quick Connect

Step Procedure

1 Be connected to the Opus Supervisor station as described in Opening

the Station.


58

Step

2 Click the

dialog box appears

3 Select the

present in the Opus Supervisor.

4 Type the

5 Type the

site.

6 Click

station user name and password.

7 Click

NOTE!

Connect/Disconnect Station View

You can connect to or disconnect from the remote XCM station in the

Opus Explorer

To disconnect a station view

Step

1 Right

2 Select

3 Click


Procedure

Click the Quick Connect button on the toolbar. The Quick Connect

dialog box appears.

Figure 64

Select the Group Name from the list. The list contains all the groups

present in the Opus Supervisor.

Type the Site Number of the site from the selected group.

Type the XCM Number of the XCM controller from the selected

site.

Click OK. An authentication dialog box appears with the default

station user name and password.

Click OK. You are connected to the station.

The Quick Connect dialog remembers and displays the name of

the last quick connected group and XCM number. Therefore, if

you are commonly returning to the same group, all you will

need to re-enter is the site number.


Opus Explorer list using the Connect and Disconnect

To disconnect a station view

Procedure

Right-click the downloaded station in the Opus Explorer

Select Disconnect from the list. A confirmation message appears.

Click Yes.


Quick Connect

from the list. The list contains all the groups

of the site from the selected group.

of the XCM controller from the selected

. An authentication dialog box appears with the default

The Quick Connect dialog remembers and displays the name of

umber. Therefore, if

you are commonly returning to the same group, all you will


Disconnect options.

Opus Explorer list.

from the list. A confirmation message appears.



To connect to a station view

Step Procedure

1 Right-click the downloaded station in the Opus Explorer list.

2 Select Connect from the list. An authentication dialog box appears

with the default station user name and password.

3 Click OK.

Quick Disconnect Using the Quick Disconnect feature, you can instantly disconnect all the

connected platforms and stations. This option is available on the toolbar

of Opus client. When you click the Quick Disconnect button on the

tool bar, a dialog box appears with a list of connected stations and

platforms. Although, the supervisor stations would not be displayed in

the list.

Figure 65

To disconnect from the station or platform

Step Procedure

1 Select the station or platform under Connected Sessions and click the

right arrow.

The selected station or platform is displayed in the Selected Sessions

list.

2 Click Disconnect.


60

NOTE!

Navigation The Opus Supervisor maintains a multi

hierarchy which consists of the Groups, Sites, and XCM controllers that

are created using this application. You can navigate to the XCM

controllers by traversing the Opus Systems hierarchal tree within the

Opus Explorer or the naviga

XCM directories displayed in the main window pane at the root of the

Opus Systems.

Using Opus Explorer

To navigate to an XCM controller using the Opus Explorer

Step

1 Expand

Supervisor

2 Expand the group node to view the list of sites added to the group.

3 Expand the site node to view the list of XCM controllers added to the

site.

4 Expand the XCM controller node to view the XCM controller station

node.

5 Double click on the station node and you will be connected and

routed to the remote XCM station.


The Disconnect All button disconnects all the sessions under

Connected Sessions.

The Opus Supervisor maintains a multi-site enterprise component




Opus Explorer or the navigation lists provided in the Group, Site and


Opus Systems.

To navigate to an XCM controller using the Opus Explorer

Procedure

Expand Opus Systems to view the list of groups in the

Supervisor.

Expand the group node to view the list of sites added to the group.

Expand the site node to view the list of XCM controllers added to the

site.

Expand the XCM controller node to view the XCM controller station

node.

Figure 66

Double click on the station node and you will be connected and



disconnects all the sessions under

e enterprise component




tion lists provided in the Group, Site and


st of groups in the Opus

Expand the group node to view the list of sites added to the group.

Expand the site node to view the list of XCM controllers added to the

Expand the XCM controller node to view the XCM controller station

Double click on the station node and you will be connected and



Using navigation directories

To navigate to an XCM controller using the navigation directories

Step Procedure

1 Double-click Opus Systems in the Opus Explorer list. The main

window pane on the right pane displays the list of groups in the Opus

Supervisor.

Figure 67

2 Double-click a group name in the Group Directory to view the list of

sites added to the group.

3 Double-click a site name in the Site Directory to view the list of

XCM controllers added to the site.

4 Double-click an XCM name in the XCM Directory to connect and be



To disconnect a Supervisor:

Step Procedure

1 Right-click Opus Systems in the Opus Explorer list, in the left pane.


disconnected.

User Management

User management provides a service to only allow a single write enabled

user access to the XCM's within a site. The OpusSingleUserService

operates within the Opus XCMs and the OpusSingleUserClientService

operates within the Opus Architect client application. The

OpusSingleUserService service is available in the OpusEnterprise

module. When configured in all the XCMâ€™s within a site, these

services will allow only the first write capable user's client application to

establish a connection to an XCM within the site.

The services will prevent secondary write capable users from being

connected to any XCM within the site. When the secondary write user

connects, they will be informed that another user (by name) is connected

and they will be logged in with read only privileges. If a user is already

configured as read only permission, they will not be impacted by this



feature.

Key features of single user access:

• Allows the single user write access across all XCM within

a single site. When a write-only user connects to an XCM,

the user will have sole write access to connected XCM and

other XCMs within the same site.

• The secondary user will re-login as read-only permission

user or if a guest user is enabled and configured for read-

only the feature will automatically connect the secondary

user as guest.

• The secondary read-only users are not impacted.

• The OpusSingleUserService is applicable for both Opus

Architect client and thin web browser client access.



To configure single user access

Step Procedure

1 Open Opus Enterprise module in a Palette.

2 Drag and Drop OpusSingleUserService in XCM station under

services. It allows only one opus sync service to be in station.

Figure 68



3 Opus sync service registers and syncs with other stations (adds

the remote user details under the local Opus Single User Service).

Figure 69

4 Note: This feature only works if all XCM within a site have their

Niagara networks configured with the other XCM on site.

5 Browse to OpusProgramService and click OK. OpusProgram

appears under Palette.

Login User Once login is complete, the OpusSingleUserService checks current user

permissions.

Key features of single user access

• Allows the single user write access across all XCM within a

single site. When a write-only user connects to an XCM,

the user will have sole write access to connected XCM and

other XCMs within the same site.

• The secondary user will re-login as read-only permission

user or if a guest user is enabled and configured for read-

only the feature will automatically connect the secondary

user as guest.

• The secondary read-only users are not impacted.

• The OpusSingleUserService is applicable for both Opus

Architect client and thin web browser client access


NOTE!

Logout User Once primary read/write user log outs of the site (i.e. one of the sites

xcm), the log out information will be synced with all other stations under

the site.

read/write access immediately.

About Opus History and Alarms

This module provides the supervisor station components for enterprise

alarm and history management.

Adding SqlServer database

Step

1 Drop the

the supervisor



The same read/write user (for example - admin)

login into other XCMs of the same site, if using the same

machine.

Once primary read/write user log outs of the site (i.e. one of the sites


the site. If the next read/write user tries to login, the user will get the

read/write access immediately.


alarm and history management.

Procedure

Drop the RdbmsNetwork from the palette into Config

the supervisor.

Figure 70


65

will be able to

login into other XCMs of the same site, if using the same

Once primary read/write user log outs of the site (i.e. one of the sites


If the next read/write user tries to login, the user will get the


Config > Drivers on



Step Procedure

2 Drop the OpusSqlServerDatabase into the RdbmsNetwork.

Figure 71

3 Open the property sheet for the OpusSqlServerDatabase and set

your DB connection information.

Figure 72



Adding Histories to the Database

You can either discover histories to add them selectively or add all

known histories.

Adding discovered histories

Histories are exported from the Niagara database to the SQL database via

the Novar Rdbms History Device Ext. This is an extension on the

NovalSqlServerDatabase.

Step Procedure

1 Double click on the extension named Histories to get the export

manager, then discover the histories and add them to the database

Figure 73

Using the OpusAlarmService

The OpusAlarmService replaces the stock Niagara AlarmService and

stores alarms in a SQL Server database instead of the Niagara database.



Step Procedure

1 On the supervisor station go to the Services nav tree and delete

Alarm Service, copy OpusAlarmService from the palette into

Services.

Figure 74

2 Open the property sheet for OpusAlarmService and pick your

database in the Driver property.

Figure 75



Alarms The Opus Supervisor provides you the ability to configure the remote

XCM controllers to generate alarm conditions and have those alarms

routed to the Opus Supervisor and archived into a relational database.

Alarm Configuration at Opus Supervisor

The Opus Supervisor can be configured to collect alarms from all of the

XCM controllers deployed throughout the enterprise. The alarms being

sent from the XCM controllers contain all the necessary data identifying

where the alarm source is located. This allows the Opus Supervisor to

simply route the alarm data to the database without needing to augment

the alarm data.

Create an Sql database schema

To manually create an Sql database schema

Step Procedure

1 Browse to the OpusSqlServerDatabase under RdbmsNetwork in the

Opus Explorer list.

2 Right-click OpusSqlServerDatabase and choose Actions > Database

Scripts.

Figure 76



Step Procedure

3 On clicking Database Scripts, a dialog box is displayed with the

database creation script.

Figure 77

4 Select the script in the dialog box and copy the content into a SQL

query execution tool.

5 Execute the script to manually create the SQL schema.

Routing Alarms to Database Driver

The Opus Supervisor routes the incoming alarms to the configured

database driver through the Opus Alarm Service. This service needs to be

configured to use the database driver.

Step Procedure

1 Expand Station > Config > Services in the Opus Supervisor station in


2 Right-click OpusAlarmService and select Views > Property Sheet.



Step Procedure

3 Select the database driver from the list in the Driver field.

Figure 78

4 Click the Save button on the property sheet.

Alarm Configuration at XCM

The XCM controller requires specific configurations to be performed to

properly report alarms to the Opus Supervisor. The alarm routing

configuration and individual alarm point setups are required.

Route Alarms to the Opus Supervisor

The XCM controller has an Alarm Service that manages the routing of

the alarms generated within an XCM to a remote destination. The

following will describe how to configure this service.

Step Procedure

1 Browse and connect to the XCM station configuration.


72

Step

2 Browse

wiresheet view.

3 In the palette, open the OpusHistoryAlarmME module.

4 Drag the OpusEnterpriseRecipient onto the wiresheet.

5 Connect a link from the Default Alarm class object to the

OpusEnterpriseRecipient

6 Select the OpusEnterpriseRecipient object and select the Property

sheet view.

7 Use the drop

OpusSupervisorStation

NOTE!

The Opus Supervisor c

more reporting channels using the OpusEnterpriseRecepient component.

Refer


Procedure

Browse to the Services directory and open the Alarm Service

wiresheet view.

Figure 79

In the palette, open the OpusHistoryAlarmME module.

Drag the OpusEnterpriseRecipient onto the wiresheet.

Connect a link from the Default Alarm class object to the

OpusEnterpriseRecipient.

Select the OpusEnterpriseRecipient object and select the Property

sheet view.

Figure 80

Use the drop-down list and set the Remote Station to the

OpusSupervisorStation.

If there is no OpusSupervisorStation in the drop down list, you

must first ensure the Opus Supervisor station node has been

configured and is communicating in the Niagara Network of the

XCM.

The Opus Supervisor can be configured to route alarms out of one or


Refer Conditional Alarm Channels for more details.


Alarm Service

In the palette, open the OpusHistoryAlarmME module.

Drag the OpusEnterpriseRecipient onto the wiresheet.

Connect a link from the Default Alarm class object to the

Select the OpusEnterpriseRecipient object and select the Property

on to the

If there is no OpusSupervisorStation in the drop down list, you

must first ensure the Opus Supervisor station node has been

configured and is communicating in the Niagara Network of the

an be configured to route alarms out of one or




Configure an Opus Alarm Extension

Step Procedure


2 Browse to the Opus Control entity that requires an alarm setup.

Figure 81

3 If the Opus Control entity has not been identified, drag the

OpusControlEntity component from the OpusEnterprise palette.

4 Browse to the I/O point or value you want an alarm on

Figure 82

5 From the OpusEnterprise palette, select the Opus Alarm

Extension type and drag it onto the point or value property sheet.

6 Type a Name for the alarm extension on the dialog box and click

OK.



Step Procedure

7 View the Opus Alarm Extension in the property sheet. The Parent

Control Entity field should have automatically associated with the

Opus Control entity that is the closest ancestral parent of the point.

Note: The Parent Control Entity field is read-only. Changing the

Opus Control Entity name in the ancestral parent updates the name in

the Parent control entity field of the Opus Alarm Extension. Also, if

the point is to be associated with a different Opus Control Entity, use

the 'OpusControlEntity' button to navigate to and select the correct

parent control entity.

8 Expand Offnormal Algorithm in the property sheet of the alarm

extension.

9 Set the High Limit and Low Limit values for the alarm extension.

10 Type the text message that would appear for of an alarm in the High

Limit Text and Low Limit Text boxes.

11 Select highLimitEnable and lowLimitEnable to set the alarm for the

high and low limit values.

12 Enter the Alarm Type. The list populates the default alarm types.

Note: You can custom create alarm types by typing the alarm type in

the text box and clicking the Save button. The custom created alarm

types are preceded by an * which makes it easy to distinguish the

custom alarm type from the default type. The alarm types created by

you can be deleted whereas, the default alarm types cannot be deleted

from the list.


Alarm Console View

The Opus Alarm Console View displays the XCM controller alarms

directly from the XCM or from the Opus Supervisor. The view provides

customization features allowing the user to alter the tabular layout of the

alarm properties. You can add, remove or re-order the columns by using

the Setup Columns feature. Once the setup is complete, you can view the

alarms in the tabular format based on the customizations provided.

Figure 83


NOTE!

You can use Se

view

To setup columns:

Step

1 Select the parameters from

to move to

2 Click OK to apply the changes

NOTE!

The

station. These customizations are applied each time the user returns to

the Opus Alarm Console view



If the alarm is highlighted in red, then the alarm is triggered

You can use Setup Columns to customize the table for alarms console

view.

Figure 84

Procedure

Select the parameters from All Columns, and then click

to move to Current Columns.

Click OK to apply the changes

You can select multiple options at a time.

The table customizations are saved within the Opus Supervisor/XCM


the Opus Alarm Console view.


75

If the alarm is highlighted in red, then the alarm is triggered.

tup Columns to customize the table for alarms console

and then click

table customizations are saved within the Opus Supervisor/XCM




Configuring Opus SQL Driver

The Opus Supervisor provides drivers for alarms to be written to a either

Microsoft SQL database (minimum: MS-SQL 2005).

To Configure Opus SQL Driver:

Step Procedure

1 Expand Station > Config > Drivers in the supervisor station in the

Opus Explorer list.

2 Under Palette in the left pane, click the Open Palette

button. The Open Palette dialog box appears.

3 Select OpusHistoryAlarmSE from the list and click OK.

Figure 85

4 Drag RdbmsNetwork from the Palette onto Drivers in the Opus

Explorer list.

5 Drag OpusSqlServerDatabase from the Palette onto RdbmsNetwork

in the Opus Explorer list, if you are using Microsoft SQL database

server.

Note: If you are using Opus SQL Server Database driver, you must

configure the Opus Enterprise Service properties in order to store all

the alarms and histories into the SQL database.

See To configure Opus Enterprise Service for SQL Database driver

section for more details.



Step Procedure

6 Double-click the database node in the Opus Explorer list, to view the

property sheet of the database driver.

Figure 86

7 Type the IP address of the database server to which the alarms would

be stored in the Host Address field.

8 Type the database User Name and Password.

9 If required, type the database server instance name in the Instance

Name field.

10 Type the name of the database to which the alarms would be stored in

the Database Name field.

11 Set the Auto Create Schema to True to enable the database driver

which automatically creates database tables, indexes, and constraints

in the specified SQL database.

Note: If the Auto Create Schema is set to False, you need 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.

See To manually create an Sql database schema section for more

details.



Step Procedure

12 Set Windows authentication if required. By default, this is set false to

use SQL authentication. When set true, the Opus SQL driver will use

Windows authentication for accessing the SQL Server.

Note: If Windows authentication is selected, the login User Name and

Password utilized is NOT the fields User Name and Password entered

in this view, but the user specified in the Niagara service User Log On

Account as seen below. Additionally, this Windows user must be

assigned as a valid user of the target database in the SQL Server.

Figure 87

13 Click the Save button on the property sheet. The Status is displayed

as OK.

A connection is established between the database server and the

supervisor.

Configure Opus Enterprise Service

To configure Opus Enterprise Service for SQL Database driver

Step Procedure

1 On the Opus Explorer, expand the supervisor station.



Step Procedure

2 Expand Config > Services and double-click OpusEnterpriseService.

The property sheet of the Opus Enterprise Service is displayed on the

right pane.

3 Type the Enterprise Name and Enterprise Code in the text boxes.

Figure 88

4 Click Save to save the 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.

Create an Sql database schema

To manually create an Sql database schema

Step Procedure

1 Browse to the OpusSqlServerDatabase under RdbmsNetwork in the

Opus Explorer list.



Step Procedure

2 Right-click OpusSqlServerDatabase and choose Actions > Database

Scripts.

Figure 89

3 On clicking Database Scripts, a dialog box is displayed with the

database creation script.

Figure 90

4 Select the script in the dialog box and copy the content into a SQL

query execution tool.

5 Execute the script to manually create the SQL schema.

Persist Enterprise Model Data

Persist Enterprise Model Data exports the Opus Enterprise Model Data

(EMD) which is resided in the Opus Supervisor to the Opus MS-SQL

database. The following EMD data are exported to the database:

� Enterprise

� Group



� Site

� XCM

� Alarm types

To export Enterprise Model Data to SQL database

Step Procedure

1 Browse to the OpusSqlServerDatabase under RdbmsNetwork in


2 Right-click OpusSqlServerDatabase and choose Actions > Persist

Enterprise Model Data.

Figure 91

3 On clicking Persist Enterprise Model Data, a dialog box is

displayed with the status of the DB script execution.

Figure 92


82

Conditional Alarm Channels

This feature enables the user to configure the Alarm service within the

XCM. So the primary logic created for the alarm can be applied to the

reporting channels. Multiple OpusEnterpriseRecepient components can

be cascaded together to support fail saf

secondary and tertiary Opus Supervisor alarm collectors

Configure Conditional Alarms

To configure conditional alarms:

Step

1 On the Nav palette, expand OpusSystems and browse to the station of

the XCM which needs to

2 Expand Station > Config > Services.

3 Right

wiresheet of the Alarm service displays the default configuration

components on the right pane.

4 Drag an

to Alarm Configuration at XCM section of

adding an OpusEnterpriseRecepient component.

5 Link the components on the wiresheet as shown in the image

NOTE!





be cascaded together to support fail safe alarm report channels to

secondary and tertiary Opus Supervisor alarm collectors

To configure conditional alarms:

Procedure

On the Nav palette, expand OpusSystems and browse to the station of

the XCM which needs to be configured with a secondary supervisor.

Expand Station > Config > Services.

Right-click AlarmService and select Views > Opus Wire Sheet. The


components on the right pane.

Drag an OpusEnterpriseRecepient component from the palette. Refer

to Alarm Configuration at XCM section of Alarms for more details on

adding an OpusEnterpriseRecepient component.

Link the components on the wiresheet as shown in the image

Figure 93

If the Status is ok, the output of Status is true and when the

Status is in fault state, the output is false.

If the Inverted Status is ok, the output of Inverted Status is false





e alarm report channels to

secondary and tertiary Opus Supervisor alarm collectors.

On the Nav palette, expand OpusSystems and browse to the station of

be configured with a secondary supervisor.

click AlarmService and select Views > Opus Wire Sheet. The


OpusEnterpriseRecepient component from the palette. Refer

for more details on

Link the components on the wiresheet as shown in the image.

If the Status is ok, the output of Status is true and when the

If the Inverted Status is ok, the output of Inverted Status is false



and when the Inverted Status is in fault state, the output is true.

Both the status outputs are made available to customize the

required operational logic on the Alarm Service wiresheet.

Alarm Filter The Opus Alarm Console Filter enables you to filter which alarms are

viewed from the Opus Supervisor or Opus XCM alarm database. The

user may create multiple filter configurations customized to specific

application requirements. For example, filters for lighting controls alarm

types can be created and saved for future re-use. The Opus Alarm

Console Filter provides the alarm property selections on the following

Opus Filter, Time Filter and Alarm Data Filter tabs

OPUS Filter Opus Filter property selections are related to the Opus enterprise model

properties identifying the source of the alarm. In this tab, you can select

filters for the alarm on the basis of Group Name, Category Type/Name,

Site Number, Alarm Type, State, City, Country, XCM Name, Entity

Name, Entity Type, Entity Controller, Entity Equipment, or Point Name.

To filter the alarms

Step Procedure

1 From Opus Explorer list, click the Alarms node. The Opus Supervisor

Alarm Console screen appears.

2 Click Filter. The Opus Filter dialog box displays.

Figure 94



Step Procedure

3 You can filter the alarm on the basis of below selection parameters.

Note: You can select multiple options at a time.

Select the Group Name, and then click

to choose the groups.

Select the Category Type/Name, and then click

to choose the category.

Enter the Site Number.

Select the Alarm Type, and then click

to choose the alarm type.

Select the State, and then click

to choose the state name.

Select the City, and then click

to choose the city name.

Select the Country, and then click

to choose the country name.

Select the XCM Name, and then click

to choose the XCM name.

Select the Entity Name, and then click

to choose the entity name.

Select the Entity Type, and then click

to choose the entity type.

Select the Entity Controller, and then click

to choose the entity controller.

Select the Entity Equipment, and then click

to choose the entity equipment.

Select the Point Name, and then click

to choose the point name

4 Click Apply to use filter in the current alarm view.

5 Click New to reset and make a new opus filter.



Step Procedure

6 Click Cancel to exit the filter dialog. .

7 Click Delete to delete the current alarm filter selection.

8 Click Delete to delete the current alarm filter selection.

9 Click Save to save the alarm filter selection. The "Filter saved

successfully" message displays.

Figure 95

Time Filter Time filter enables you to filter the alarms based on parameters such as

Timestamp (alarm occurrence time), Normal Time (alarm returned to

normal state), Ack Time (alarm acknowledgement) and Last Update (last

time an alarm record changed).

To filter the alarms

Step Procedure

1 From the Opus Explorer list, select the OpusSupervisorStation >

Open Alarm Sources.



Step Procedure

2 Click Filter. The Opus Filter dialog box displays.

Figure 96

3 Below are the selection parameters to filter the alarms: Note:

You can select multiple options at a time.

Source State - This data field displays the current alarm state; for

example, "High Limit" or "Normal". Ack State - This data field

displays either "Acked" or "Unacked" to indicate whether the alarm

has been acknowledged. Ack Required - This data field displays

either "True" or "False" to indicate whether or not an

acknowledgement is required for this alarm. Source - This data field

displays the alarm source name. Alarm Class - This data field

identifies the name of the alarm class that the extension is assigned to

(defaultAlarmClass or other class). Priority - This data field displays

the priority number of the alarm. User - This data field identifies the

name of the user that acknowledged the alarm. An unacknowledged

alarm will display "unknown" in this field. Alarm Data - This data

field presents a detailed list of auxiliary alarm data. Alarm

Transition - This data field displays the last transition state of the

alarm.



Step Procedure

4 You can view the Filter button in red color, when the alarm is filtered.

Click Clear Filter to remove the filter application in the current alarm

view.

Figure 97

Identifying Opus Control Entities

The Opus XCM station configuration can consist of numerous control

subsystems or entities. These control subsystems are each an instance of

building controls equipment that the XCM is configured to control.

Examples of these control subsystems are Roof Top Hvac Unit field

controllers under the Novarnet driver or a BacNet driver or a custom

lighting control strategy created in an Opus wiresheet. A control entity

should be considered any control sub-system that has I/O points or

values to be alarmed or logged. By applying this identifier to the control

entity, the Opus Supervisor will be able to manage the settings, alarms

and logs of these entities in a consistent manner, regardless of the type of

control entity.

Also, the control entity identifier will allow you to specify the

application of the control entity. For example, for a Roof Top Unit

controls, if you create an ETM-2024 field controller named RTU-17,

using the control entity identifier you can specify the application is for

the 'Pharmacy' and it is of type 'Hvac'. The Opus control entity identifier

stores the application name entered into a common list within the Opus

Supervisor. This will allow you to be consistent in naming when by

reusing application names from this drop down list when configuring all

of your site XCM controllers.


88

To identify an Opus Control Entity

Step

1 Expand

2 Navigate to a field controller in the XCM sta

3 Open the

4 Drag and

controller property sheet.

5 Enter a new

drop down list.

6 Enter a new

down list.

7 Click

NOTE!

History Configuration

The Opus Supervisor provides you the ability to configure the

remote XCM controllers to generate trend logs and have those logs

collected by the Opus

database. Once these logs are store in the database they can be

viewed from the History Viewer in the Opus Supervisor.


To identify an Opus Control Entity

Procedure

Expand Opus Systems in the Opus Explorer list.

Figure 98

Navigate to a field controller in the XCM station configuration

Open the OpusEnterprise module in the palette.

Drag and drop the OpusControlEntity component to the field

controller property sheet.

Enter a new Application Name or select previous name from

drop down list.

Enter a new Application Type or select previous type from drop

down list.

Click Save to save the changes.

It is recommended you always assign the control entity identity

to the root level of each XCM station configuration. This is so

global network inputs can be associated to the XCM entity and

therefore maintaining a consistent model.



collected by the Opus Supervisor and archived into a relational




tion configuration

component to the field

or select previous name from the

or select previous type from drop

It is recommended you always assign the control entity identity

to the root level of each XCM station configuration. This is so

can be associated to the XCM entity and



Supervisor and archived into a relational





Alternately, the Novar Toolset application will provide an

enhanced set of history reporting features for the Opus logs.

History Configuration at XCM

The XCM controller requires specific configurations to be

performed to properly allow history trend logs to be archived by

the Opus Supervisor.

Configure an Opus History Extension

Step Procedure


2 Browse to the Opus Control entity that requires a trend log setup.

Figure 99

3 If the Opus Control entity has not been identified, drag and drop the

OpusControlEntity component from the OpusEnterprise palette.



Step Procedure

4 Browse to the I/O point or value you want a trend log on.

Figure 100

5 From the OpusEnterprise palette, select the Opus History

Extension type and drag and drop onto the point or value property

sheet.

6 Type a Name for the history extension on the dialog box and click

OK.

7 View the Opus History Extension in the property sheet. The Parent

Control Entity field should have automatically associated with the

Opus Control entity that is the closest ancestral parent of the point.

8 The Point Group Name property is used by the Novar Toolset

application to place the history points in general categories.

Note: The Parent Control Entity field is read-only. Changing the

Opus Control Entity name in the ancestral parent updates the name in

the Parent control entity field of the Opus History Extension. Also,

if the point is to be associated with a different Opus Control Entity,

use the OpusControlEntity button to navigate to and select the

correct parent control entity.

9 Expand Offnormal Algorithm in the property sheet of the history

extension.

10 Set the Interval value for the history extension.

11 Execute the Update History ID action on the history extension.

12 Set the Enabled value to true for the history extension

13 Enter the Point Group Name. The list populates the default alarm

types.

Note: You can custom create point groups by typing the point group

name in the text box and clicking the Save button. The custom created

point groups are preceded by an * which makes it easy to distinguish

the custom created point groups from the default groups.

The point groups created by you can be deleted whereas; the default

point groups cannot be deleted from the list.



Step Procedure


History Configuration at OpusSupervisor

When importing histories from XCM, we can choose the database

endpoint to which histories is imported. The selection can be done

under supervisor station > services > OpusHistoryService > driver

as shown in the figure below.

Figure 101

If no driver is selected, the imported histories will be going to the

supervisor file system. If a sql driver is chosen as explained below,

the histories will be going to the respective sql database. Once we

make a change we need to force save and restart of supervisor

station.

Once the history trend logs have been activated in the remote

XCM stations.You can now configure the Opus Supervisor to

import and archive these trend logs.

Transfer History Logs to the Opus Supervisor

The Opus Supervisor first imports the trend logs into the Opus

Supervisor file system. The following are the steps to configure.

Choosing History Import data source

Step Procedure

1 Browse to the Niagara Network of the Opus Supervisor station.



Step Procedure

2 Browse to the remote XCM station under the Niagara Network.

3 Expand the XCM station node and double click on the Histories

node under the station.

Figure 102

4 Click the Discover button to find all the available histories in the

remote XCM.

5 Select the histories that you would like to import.

6 Click the Add button to import into the Opus Supervisor. A dialog

box appears prompting you to setup an interval to perform subsequent

history imports. This completes transferring the histories.


Step

7 Along with transferring h

file by the name HistoryMetaInfo.xml is updated with Opus EMD

data of XCM at resources/history folder under supervisor station. This

file is referenced to show enterprise data in History Wizard selection

screens,

There is a Sync action provided under Services

called as Sync History Viewer, which can be used in case the

HistoryMetaInfo.xml is corrupted or not in sync with local history in

file system. Before doing this action remove the HistoryMetaInfo.xml

from station. Once the action is invoked the xml is updated and kept

in sync.

Export Trend Logs to database

Configuring the Database Driver

Step

1 Expand

Opus Explorer

2 Under

Open Palette



Procedure

Along with transferring histories to Supervisor File system, an xml




screens, when the chosen database is Local Supervisor file system.

There is a Sync action provided under Services->OpusHistoryService,





in sync.

Figure 103

Configuring the Database Driver

The Opus Supervisor provides drivers for alarms to be written

to an either Microsoft SQL database (minimum: MS

2005).

Procedure

Expand Station > Config > Drivers in the supervisor station in the

Opus Explorer list.

Under Palette in the left pane, click the Open Palette

Open Palette dialog box appears.


93

istories to Supervisor File system, an xml




when the chosen database is Local Supervisor file system.

>OpusHistoryService,





r alarms to be written

to an either Microsoft SQL database (minimum: MS-SQL

in the supervisor station in the

Open Palette button. The



Step Procedure

3 Select OpusHistoryAlarmSE from the list and click OK.

Figure 104

4 Drag RdbmsNetwork from the Palette onto Drivers in the Opus

Explorer list.

5 Drag OpusSqlServerDatabase from the Palette onto RdbmsNetwork

in the Opus Explorer list, if you are using Microsoft SQL database

server.

Note: If you are using Opus SQL Server Database driver, you must

configure the Opus Enterprise Service properties in order to store all

the alarms and histories into the SQL database.

See Configure Opus Enterprise Service section for more details.



Step Procedure

6 Double-click the database node in the Opus Explorer list, to view the

property sheet of the database driver.

Figure 105

7 Type the IP address of the database server to which the alarms would

be stored in the Host Address field.

8 Type the database User Name and Password.

9 If required, type the database server instance name in the Instance

Name field.

10 Type the name of the database to which the alarms would be stored in

the Database Name field.

11 Set the Auto Create Schema to True to enable the database driver

which automatically creates database tables, indexes, and constraints

in the specified SQL database.

Note: If the Auto Create Schema is set to False, you need 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.

See Create an Sql database schema section for more details.

12 Click the Save button on the property sheet. The Status is displayed

as OK. A connection is established between the database server and

the supervisor.

Archive Histories to Database Driver

The Opus Supervisor maintains the imported trend logs in its local file

system. To archive the trend logs into the database can be performed in

two ways.



Step Procedure

1 Browse to the OpusSqlServerDatabase in the Opus Supervisor station.

2 Expand the node and double click on the Histories node.

Figure 106

3 Click the Discover button to find all the available histories in the

Opus Supervisor.

4 Select the histories that you would like to archive.

5 Click the Add button to archive into the database.

6 A dialog box appears requesting you to setup an interval to perform

subsequent history archiving.

The second approach is to allow configuration in such a way to

export directly to the SQL driver whenever Niagara Network

history imports are executed. The history database is selected using

a pull-down menu on the property Page of the OpusHistoryService

in the Supervisor. This will help to avoid executing the first

approach.

History View The History View enables you to view history points residing within the

history database, which is either in the Supervisor file system or from a

SQL database. The selection made under Station > Services >

OpusHistoryService > Driver decides this data source. You can select

Groups, Sites, XCMs, and Control Entities present in the enterprise

hierarchy to filter the history points. The history points within the

selection are displayed in the view. You can select individual history

points and view them on the chart builder either in form of tables or

charts.

See Choosing History Import data source for more details.



To graphically view the history in Opus:

Step Procedure

1 From Opus Explorer list, select Station > History. Double click on

the History node.

Figure 107

2 Click New.

Figure 108

3 The History View enterprise selection page appears.

Figure 109

4 Enter the Name and Description of user or site.


98

Step

5 Select one or more groups

associated to the selected groups is displayed under the

column.

6 Select one or more sites from the

associated to the selected sites is displayed under

7 Select the XCMs from the

associated to the selected XCMs is displayed under

Tip

Type the initial characters of the control entity and click

All the control entities beginning from those characters are listed.

However, the filtered site category entity names are listed only in

the Categories column.

8 Select the

Next. The following page appears.

9 Select one or more point names from the

10 Select the

available options are Chart and Table.

11 Select the Show option from the

gridlines on the chart. The available options are Show and Hide.


Procedure

Select one or more groups from the Group list. A list of sites

associated to the selected groups is displayed under the

column.

Select one or more sites from the Site list. A list of XCMs

associated to the selected sites is displayed under XCM

Select the XCMs from the XCM list. A list of control entities

associated to the selected XCMs is displayed under

Tip: Use the Filter option to quickly search for a Co

Type the initial characters of the control entity and click



the Categories column.

Select the control entities from the Controller column and click

Next. The following page appears.

Figure 110

Select one or more point names from the Point Names

NOTE!

Select the button in the header row to select all

the point names simultaneously.

Select the Chart option from the Default View list. The

available options are Chart and Table.

Select the Show option from the Gridlines list to view the



list. A list of sites

associated to the selected groups is displayed under the Site

t. A list of XCMs

XCM.

list. A list of control entities

associated to the selected XCMs is displayed under Controller.

Control Entity.

Type the initial characters of the control entity and click Filter.



control entities from the Controller column and click

Point Names column.

button in the header row to select all

list. The

list to view the




Step Procedure

12 Select the table output option from the Default Stacking list. The

available options are Control Entity, XCM and Site.

13 Click Save View to save the settings. Click Home. The following

page appears.

Figure 111

14 Click View/Edit to change the settings again.

15 Click Build. The Chart View page appears. The data for the

selected points is displayed graphically in the form of a chart.

Figure 112



Step Procedure

16 Click Table View. The Table View page appears. You can view

the tabular data for the selected points.

Figure 113

Live History View

Live history view provides Live History Chart View and Live

History Table View that is similar to the Static History Chart view

and Static History Table View. The live history view updates the

data on chart and table according to a configurable sample rate.

Live History Chart/Table View

The key feature of the Live History view is that it combines the

graphical historical plot of the History log with a continuing live

plot that updates according to a configurable sample rate.

To view the Live History

Step Procedure

1 From OpusEnterprise Module Pallete, select History Live View >

Opus History Point List

2 Drag and drop the History Point List list to anywhere in the XCM

station folder.



Step Procedure

3 Drag and drop the History Point List list Item below History Point

List list in XCM station folder. The following page appears.

Figure 114

4 Enter the History Extension path.

5 Select the True option from the Display on Standup list.

6 Select the start time from Start Time list.

7 Select the Auto option from the Sample Rate list.

8 Select the Fixed option from the Min Value Range list or enter

the minimum value range of history point list item.

9 Select the Fixed option from the Max Value Range list or enter

the maximum value range of history point list item.

10 Select the Line Color.

11 Select the Pen characteristics.



Step Procedure

12 Click Save. Go to OpusHistoryPointList properties page.

Figure 115

13 Enter the maximum number of samples for history point items.

14 Select the time range from Time Window list.

15 Click to select the background of the chart/table.

16 Select True to view the horizontal gridlines from Show

Horizontal Gridlines list.

17 Select True to view the vertical gridlines from Show Vertical

Gridlines list.



Step Procedure

18 Double click on the OpusHistoryPointList node in the station,

depending on the default view, the Live History Chart or the Live

History Table view page appears.

Figure 116

19 Click Switch to Chart. The Live Chart View page appears.

Figure 117

20 Click to view the difference between two consecutive points in

table rows or on charts.



Step Procedure

21 Export to PDF/CSV formats: a) Right click on the Chart/Table view,

select Export. An Export pop-up appears. b) Select Opus Table to

CSV on Exporter option. Click OK. The configured

HistoryPointListItems appears in PDF or in CSV format.

Figure 118

22 You can hide or unhide the HistoryPointListItems from being

displayed on chart or table view with the help of Point Select option.

You can use the Point Select option in two ways-a) On the

Chart/Table view page, click Point Select to select the

HistoryPointListItems.b) Select False from Display on Startup list

on HistoryPointListItem property page. You can select the table and

chart HistoryPointListItems here.

Figure 119



Boolean Shifted Schedule

The OpusApplications module provides two components for shifting the

False-to-True and True-to-False transitions of a Boolean Schedule.

The Boolean Shifted Schedule allows the user to define False-to-True

and True-to-False shifts that are applied to the weekly schedule and all

special events of the referenced Boolean schedule.

The Boolean Daily Shifted Schedule allows the user to define False-to-

True and True-to-False shifts for each day of the week and for the


Figure 120

It is possible to shift the schedule transition earlier or later than the time

defined by the reference schedule. Entering a positive value for the shift

will cause the transition to occur later; a negative value will cause the

transition to occur earlier.

Before configuring either shifted schedule type, the user should create at

least one Boolean Schedule.

Adding Boolean Shifted Schedule

To add a Boolean Shifted Schedule

Step Procedure

1 In the Palette side bar, click the Open Palette button.



Step Procedure

2 Select the OpusApplications module from the Open Palette

dialog box.

3 In the Opus Explorer side bar, locate the component to which the

shifted schedule will be added.

4 Double-click on the component to display its' Wire Sheet view.

5 Drag-and-drop a BooleanShiftedSchedule onto the Wire Sheet.

6 A dialog box will prompt for a component name; enter a name for

the Boolean Shifted Schedule and click OK.

Configuring Boolean Shifted Schedule

To configure a Boolean Shifted Schedule

Step Procedure

1 In the Opus Explorer, right-click on the Boolean Shifted Schedule

and select Property Sheet from the Views sub-menu.

Figure 121



Step Procedure

2 On the "Ref" property, click the drop-down list and select

Component Chooser:

Figure 122

The Select Ord dialog box will be displayed.

Figure 123

3 Locate the reference Boolean Schedule in the component tree;

highlight the schedule and click OK. The Ord of the selected

schedule will be displayed in the "Ref" text box.

4 Set the required shifts for the "False To True" and "True To

False" transitions.

5 Set "Update Time" which defines the frequency with which the

reference schedule is checked for changes.

6 Click Save to commit the changes.



In the Opus Explorer side bar, double-click on the Boolean Shifted

Schedule component to display the Scheduler view which shows the

shifted Boolean schedule.

Boolean Daily Shifted Schedule

The OpusApplications module provides two components for shifting the

False-to-True and True-to-False transitions of a Boolean Schedule.

The Boolean Daily Shifted Schedule allows the user to define False-to-

True and True-to-False shifts for each day of the week and for the


The Boolean Shifted Schedule allows the user to define False-to-True

and True-to-False shifts that are applied to the weekly schedule and all


Figure 124



It is possible to shift the schedule transition earlier or later than the time

defined by the reference schedule. Entering a positive value for the shift

will cause the transition to occur later; a negative value will cause the

transition to occur earlier.

Before configuring either shifted schedule type, the user should create at

least one Boolean Schedule.

Adding Boolean Daily Shifted Schedule

To add a Boolean Daily Shifted Schedule

Step Procedure

1 In the Palette side bar, click the Open Palette button.

2 Select the OpusApplications module from the Open Palette dialog

box.

3 In the Opus Explorer side bar, locate the component to which the

shifted schedule will be added.

4 Double-click on the component to display its' Wire Sheet view.

5 Drag-and-drop a BooleanDailyShiftedSchedule onto the Wire Sheet.

6 A dialog box will prompt for a component name; enter a name for the

Boolean Daily Shifted Schedule and click OK.



Configuring Boolean Shifted Schedule

To configure a Boolean Daily Shifted Schedule

Step Procedure

1 In the Opus Explorer, right-click on the Boolean Daily Shifted

Schedule and select Property Sheet from the Views sub-menu.

Figure 125



Step Procedure

2 On the Ref property, click the drop-down list and select

Component Chooser.

Figure 126

The Select Ord dialog box will be displayed.

Figure 127

3 Locate the reference Boolean Schedule in the component tree;

highlight the schedule and click OK. The Ord of the selected

schedule will be displayed in the "Ref" text box.

4 For each day of the week, set the required shifts for the "False To

True" and "True To False" transitions.



Step Procedure

5 For special events, set the required shifts for the "False To True"

and "True To False" transitions.

6 Set "Update Time" which defines the frequency with which the

reference schedule is checked for changes.

7 Click Save to commit the changes.

In the Opus Explorer side bar, double-click on the Boolean Daily

Shifted Schedule component to display the Scheduler view which shows

the shifted Boolean schedule.

Curve Fit Drop the CurveFit component into your wire sheet. Create a text file

containing x,y coordinate points. Each line of the file should contain one

x,y pair delimited with a space, tab, or comma. In the property sheet for

CurveFit, point to the file. Now it is ready to be wired up.

Figure 128

Installing Theater Schedule

The Opus Theater Schedule is provided in a separate software module

named OpusTheater. Once installed, this software module is accessible

through the Opus Supervisor palette window and can be selected and

added to an Opus XCM. Once the Theater Schedule has been installed, it

should be configured and the subsequently used for the required control

operations.

Accessing Theater Schedule

To install Theater Schedule

Step Procedure

1 On the Palette, click the Open Palette button. The Open Palette

dialog box appears.

2 Browse to Theater and click OK. TheaterSchedule appears under

Palette.

3 On the Opus Explorer, browse to Station and expand it to view

Services.

4 Drag the TheaterSchedule block under Services. A dialog box

appears prompting you for a theater schedule name.



Step Procedure

5 Type a name for the theater schedule and click OK. The theater

schedule appears under Services.

Figure 129

Configure Theater Schedule

To configure Theater Schedule

Step Procedure

1 Double-click the TheaterSchedule block under Services to view the

property sheet on the right pane.

2 Click the browse button next to Resource File and browse to the

theater file. The file path is displayed in the field.

3 Click Save to save the selected file path.



Step Procedure

4 Right-click the TheaterSchedule block under Services and select

Actions > Trigger Now. The Status field displays the current status

of the imported theater file. The auditoriums defined in the theater file

are displayed on the property sheet hierarchically.

Note:

� If the selected theater file misses any nodes or attributes and is

invalid, or if an incorrect file is selected then the status field

displays an error.

� If the Novar license is invalid then the hierarchy is not created.

5 Type the Job Trigger Time in minutes.

Note: A default clock with a time period of 1 minute is set internally,

to monitor the hierarchy. This time period is non-editable.

6 Type the Pre Show Offset time in minutes.

7 Type the Post Show Offset time in minutes.

8 Click Save to save the settings.

Figure 130

The Theater Schedule requires configuration for use in the Opus XCM.

An external source will provide a theater file to the Opus XCM. The

theater file will be updated periodically by the external source. The

following settings are required to actively monitor the provided theater

data and to provide runtime status for control operations.

Using Theater Schedule

The property sheet of Theater Schedule provides the following features.

� Status: Displays the current status of the imported theater file.

This field is non-editable.



� Theater File: Displays the path within the Opus XCM to the

theater file.

� Job Trigger Time: The frequency at which the application

refreshes the hierarchy to display the latest frequency with which

the Theater Schedules re-loads the contents of the theater file.

� Pre Show Offset: The time in minutes before show time, when

the Theater Schedule activates the auditorium Active State.

� Post Show Offset: The time in minutes after show time, when

the Theater Schedule de-activates the auditorium Active State.

Figure 131

Once the Theater Schedule has been installed and configured, you can

manage the operation of the Theater Schedule as well as create control

operations in the XCM that make use of the run time status generated by

the Theater Schedule.

The following Actions can be performed by right-clicking the Theater

Schedule module under Services.

� Trigger Now: Perform this action to build and display the

hierarchy on the property sheet of Theater Schedule. The Status

field is refreshed to display the current status of the theater file.

� Stop Timer: Perform this action to stop the timer for Job

Trigger Time.

� Restart Timer: Perform this action to restart the timer for Job

Trigger Time.



Figure 132

When the Theater Schedule timer triggers and the current theater file are

loaded, the auditorium properties are populated with the latest

information. The following show the structure of the Theater information

and runtime status provided.

� Auditorium - The name and status of the auditorium.

� Schedule Day - The date on which the show is scheduled.

� Film - The name of the show.

� Performance - The time of the show and seating details.



Figure 133

Theater File Requirements

The theater file is an XML formatted file provided by an external source

within the theater facility into the XCM. The standard method for

updating this file in the Opus XCM is to use the FTP protocol service of

the IT network. The target folder location within the XCM is left to the

discretion of the user.

The following details are available in the theater file.

� Auditorium name

� Auditorium number

� Auditorium state (current)

� Show Name

� Show time

� Show code

� Show Rating

� Show start time

� Show stop time / (or duration)

� Sold out status



� Cancelled status

� Low Seating status

XML Schema

The validity of an theater file is determined by a set of rules or XML

Schema. An imported theater file is valid only if,

1. The following nodes are always present in the following

sequence.

a) <schedule>

b) <scheduleDay>

c) <film>

d) <performance/>

e) </film>

f) <scheduleDay

g) <schedule>

2. The following attributes are associated with the nodes.

a) <scheduleDay day>

b) <film title>

c) <performance showTime/>

d) </film>

e) <scheduleDay>

3. The film node has runtime attributes which are used in setting

the auditorium to active status. For example, <film

runtimeMinutes='111'>.

4. The performance node has auditorium attributes which are

used in creating the auditorium hierarchy. For example,

<performance auditoriumNumber='5'/>.

5. The attribute showTime is in the date format, YYYY-MM-

DDThh:mm:ss.For example, <performance showTime='2009-

09-10T20:20:00-0600'>

6. The attribute day is in the date format, YYYY-MM-DD.For

example, <scheduleDay day='2009-09-10'>

If the XML file has special characters, the refine XML will clean the XML

file. Currently only "&" is handled.

The following is a sample theater file limited to only two auditoriums

numbered 5 and 12 and two theater dates of 23rd

and 24th

of August-

2009.

<?xml version="1.0" ?>

<schedule lastUpdate="2009-08-21T07:05:20-0600">

<scheduleDay day="2009-08-23-0600">








</film>

<film title="Title 2" titleMedium=" Title 2" titleShort=" Title 2" runtimeMinutes="106" rating="R">







</film>

</scheduleDay>

</schedule>



Thin Client The Opus Supervisor provides access to use a thin client browser and

monitor the downloaded XCM controllers.

Opus Web Browser Access Configuration

User login setup

The Web Browser access must be configured for a user to login in the

Opus Supervisor station using a thin client browser.

Step Procedure

1 Navigate to User Services under the Services directory of the Opus

Supervisor station.

2 Select the user name of who you want to configure.

3 View the property sheet of the user.

Figure 134

4 In the Web Profile property, select the Web Novar Appliance Profile.



Opus Web Browsing

User login page

Step Procedure

1 The URL link to connect to the Opus Supervisor server is similar to http

://<supervisorIPaddress>/login, where the IP address is that of the host

PC of the Opus Supervisor server station. Enter your credentials to

logon.

Figure 135

Opus System browsing

Step Procedure

1 Browse the deployed XCM stations through the Opus Explorer or the

Group, Site and XCM Directories in the main window pane.

Figure 136


Connect to the XCM controller station

Step

1 Double

dialog box appears prompting you to type the station user name and

password.

2 Type the st

NOTE!



to the XCM controller station

Procedure

Double-click the station in the Opus Explorer list. An authentication


password.

Type the station user name and password. Click OK.

The supervisor station must be running, to connect to the thin

client. Only downloaded XCM controller stations can be

viewed using the thin client.

The group, site, and XCM details are non-editable. The

option available on right-clicking the group, site, or XCM is

Refresh Tree Node. The Platforms and Station nodes do not

appear in the Opus Explorer list.

Backups and templates are not accessible through thin client.

However, Alarms and History are editable.


123

list. An authentication



Only downloaded XCM controller stations can be

editable. The only

clicking the group, site, or XCM is

The Platforms and Station nodes do not




Viewing Hx Profile The Thin Client provides access to Hx Web Profile which is quicker and

easier to view. Using the HX Profile, you can log into the Opus

Supervisor station. The web client has hyperlinks to the variuos nodes in

the station hierarchy.

To access Hx Profile, you must set up the Hx profile in your Opus client.

Setting up Hx Profile

To setup Hx Profile

Step Procedure

1 Connect to the supervisor station on the Opus client.

See the Opening the Station section for more details on connecting to

Supervisor Station.

2 On the Opus Explorer, expand the OpusSupervisorStation.

3 Expand Config > Services > UserService.

4 Double-click Admin. The property sheet of the admin user is


5 In the Web Profile property section, select the Type as Novar Hx

Appliance Profile.

6 Click Save to save the changes.

You can now connect to the Hx Web Profile. The URL link to connect to

the Opus Supervisor server is similar to

http://<supervisorIPaddress>:8080, where the IP address is that of the

host PC of the Opus Supervisor server station.

Connecting to Hx Web Profile

To connect Hx Web Profile

Step Procedure

1 Type the Opus Supervisor station Username and Password.

2

You can view the Supervisor station hierarchy which includes groups,

sites, and XCMs only if the XCM station is downloaded to the XCM

controller in the field.

Figure 137



Step Procedure

1 Double-click the group to view the sites within the group.

2 Double-click the site to view the XCMs within the site.

Figure 138

3 Double-click the XCM. A dialog box appears prompting you for the

XCM station Username and Password.

Figure 139

4 Type the username and password in the text boxes and click Login. A

security warning dialog box appears.

5 Click OK to proceed.

The Hx Profile web page displays a hyperlink path to the group, site, and

XCM you have selected. To traverse back to the list of XCMs or sites or

groups, you can click on the hyperlink on the top of the screen.

Using Opus History and Alarm Module

This module provides the supervisor station components for

enterprise alarm and history management.



Adding a SqlServer database

Step Procedure

1 Drop the RdbmsNetwork from the palette into Config->Drivers

on the supervisor.

Figure 140

2 Drop the OpusSqlServerDatabase into the RdbmsNetwork.

Figure 141



Step Procedure

3 Open the property sheet for the OpusSqlServerDatabase and set

your DB connection information.

Figure 142

Adding Histories to the Database

You can either discover histories to add them selectively or add all

known histories.

Adding Discovered Histories

Histories are exported from the Niagara database to the SQL database via

the Opus Rdbms History Device Ext. This is an extension on the

NovalSqlServerDatabase.



Step Procedure

1 Double click on the extension named Histories to get the export

manager, then discover the histories and add them to the database.

Figure 143

Using the OpusAlarmService

The OpusAlarmService replaces the stock Niagara AlarmService and

stores alarms in a SQL Server database instead of the Niagara database.



Step Procedure

1 On the supervisor station go to the Services nav tree and delete Alarm

Service, copy OpusAlarmService from the palette into Services.

Figure 144

2 Open the property sheet for OpusAlarmService and pick your database

in the Driver property.

Figure 145




Step Procedure



Figure 146

Opening Supervisor Station

The Station is the configuration management server of the Opus

Supervisor. The Opus Supervisor Station provides the environment to

configure, manage, and run a single database of nodes and the services

required to support a control application.

The Opus Supervisor installed on a centralized host PC can support

multiple users managing a common set of group and site configurations.

These users can install the Opus Architect which provides the client

access to this centralized Opus Supervisor. The Opus Explorer provides

Opus Supervisor specific functionality when connected to the Opus

Supervisor station. This functionality does not exist when connecting

directly to an XCM station.



To connect to a running Opus Supervisor station

Step Procedure

1 In left pane of the Profiled workbench, right-click the root node in

Opus Explorer and select Open Station. The Open Station dialog box

appears.

Figure 147

2 Type the IP address of the Opus Supervisor host computer. The host

computer is the computer on which the Opus Supervisor was

installed.

Figure 148.

Note: If you have installed Opus Supervisor, then the host IP is the IP

address of your computer.


4 Type the Password. The default password is blank.


default.

5 Click OK to open the station. The Group Directory screen appears in

the right pane.




To disconnect a Supervisor

Step Procedure

1 Right-click Opus Systems in the Opus Explorer list, in the left

pane.


disconnected.

Opus Web Browsing User Login Page

The URL link to connect to the Opus Supervisor server is similar to

http://<supervisorIPaddress>/login, where the IP address is that of the

host PC of the Opus Supervisor server station.

Figure 149

Enter your user login credentials.



Step


Group, Site and XCM Directories in th

To connect to the XCM controller station

Step

1 Double


password.

2 Type the station

NOTE!



Procedure

Browse the deployed XCM stations through the Opus Explorer or the


Figure 150

To connect to the XCM controller station

Procedure

Double-click the station in the Opus Explorer list. An authentication


password.

Type the station user name and password. Click OK.


client. Only downloaded XCM controller stations can be

viewed using the thin client.

The group, site, and XCM details are non-editable. The only

option available on right-clicking the group, site, or XCM is

Refresh Tree Node. The Platforms and Station nodes do not

appear in the Opus Explorer list.


However, Alarms and History are editable.


133

Browse the deployed XCM stations through the Opus Explorer or the

e main window pane.

list. An authentication



Only downloaded XCM controller stations can be

editable. The only

clicking the group, site, or XCM is

The Platforms and Station nodes do not



134

Add New PX View

A PX view is the configuration information that appears on the right

pane when you select a node from the Opus Explorer. You can create PX

Views, using the

To add a new PX View

Step

1 Click the Views but

2 Select New View from the list. The New PX View dialog box

appears.

3 Type a name for the view in the View Name field on the dialog box.

View Icon displays the file path where the view would be stored

4 Click OK. A canvas pane is

sidebar on the right. The PX View is in the edit mode

5 Double

You can set the background and alignment of the canvas pane

6 Click the Toggle View/Edi

new PX View.

7 Right

controller and select Save Station

NOTE!




Views, using the New View feature.

To add a new PX View

Procedure

Click the Views button on the toolbar.

Select New View from the list. The New PX View dialog box

appears.

Type a name for the view in the View Name field on the dialog box.

View Icon displays the file path where the view would be stored

Click OK. A canvas pane is displayed on the screen along with a

sidebar on the right. The PX View is in the edit mode

Double-click on the canvas pane to view the Properties dialog box.

You can set the background and alignment of the canvas pane

Figure 151

Click the Toggle View/Edit View button on the toolbar to view the

new PX View.

Right-click the station which is downloaded to the XCM field

controller and select Save Station.

You must save the online station every time a task is performed

or a modification is made to any of the components.




Select New View from the list. The New PX View dialog box

Type a name for the view in the View Name field on the dialog box.

View Icon displays the file path where the view would be stored.

displayed on the screen along with a

.

click on the canvas pane to view the Properties dialog box.

You can set the background and alignment of the canvas pane.

t View button on the toolbar to view the

click the station which is downloaded to the XCM field

You must save the online station every time a task is performed

to any of the components.



Auto Logoff Auto logoff will disconnect the inactive Opus Architect (client) to XCM

connections. The OpusAutoLogOff service establishes an auto logoff

period in minutes which is the maximum allowable period of inactivity.

When this time has expired, the user will be prompted about the inactive

sessions that are about to be closed. If the user does not respond to the

prompt, the Force disconnect time will expire and all connections will be

closed.

To configure auto logoff

Step Procedure

1 Browse to the OpusSupervisor in the Opus Explorer list, and then

select Station > Config > Services > OpusAutoLogOffService.

Figure 152

2 From Auto Log Off Enable list, select the True option. This action

activates the OpusAutoLogOffService.

3 Enter Notification Period. The Notification Period is how long the

activity timer waits before the client shows the Auto Log Off dialog

box message.



Step Procedure

4 Enter Force Disconnect Period. The Force Disconnect Period is the

time from when the dialog is displayed to where the client will

forcibly disconnect all XCM stations, if you do not respond to the

Auto Log Off dialog box message.

Figure 153

5 Select the stations, and then click OK. The selected stations will be

reset.

Note: You can select multiple stations at a time.

About Opus Schedules

The OpusSchedule module contains weekly schedule components which

have advanced scheduling features.

� Opus weekly schedule components are enhanced versions of the

NiagaraAX schedule types.

� Opus weekly shifted schedule components provide functionality

not available with NiagaraAX. For a complete understanding of scheduling and schedule components,

users are encouraged to read About Scheduling in the NiagaraAX User

Guide.

Opus schedule components are available in the OpusSchedule palette:


The following sections provide more details:

� About Opus weekly schedules

� About Opus weekly shifted schedules

About Opus weekly schedules

Opus weekly schedules build upon the NiagaraAX scheduling model to

provide enhanced features and behavior.

NOTE!

The Opus weekly schedule component types are:

� OpusBooleanSchedule

� OpusEnumSchedule

� OpusNumericSchedule

� OpusStringSchedule

These schedule components are identical except for the data val

category (Boolean, Enum, Numeric, String) of each type's output ("Out"

slot) and input ("In" slot).

The weekly schedule model has been extended to provide the following:

� Alternate Schedules

� Today and Tomorrow Special Events

� Special Event default beh



Figure 154

The following sections provide more details:

About Opus weekly schedules

About Opus weekly shifted schedules


provide enhanced features and behavior.

For information on weekly schedule concepts, see the About

weekly schedules section of the NiagaraAX User Guide

The Opus weekly schedule component types are:

OpusBooleanSchedule

OpusEnumSchedule

OpusNumericSchedule

OpusStringSchedule

These schedule components are identical except for the data val




Alternate Schedules

Today and Tomorrow Special Events

Special Event default behavior


137


For information on weekly schedule concepts, see the About

NiagaraAX User Guide.

These schedule components are identical except for the data value





� Modified Output Processing

� Integrated Opus Schedule Entity

� Enhanced User Interface Alternate Schedules

An alternate schedule defines a date range during which a user-defined

alternate weekly schedule is in effect. During the effective date range,

the alternate schedule supersedes the default schedule.

Today and Tomorrow Special Events

Permanent placeholders that follow the calendar date. As indicated by

the event names, the user is able to override the schedule for today and

tomorrow. At midnight, the Tomorrow schedule is assigned to the Today

special event and Tomorrow becomes unscheduled.

Special Event default behavior

The "Special Event Default" property allows the user to adjust the

behavior of special events during any unscheduled time within a special

event's one-day schedule. The default behavior settings are:

� Unscheduled - for any unscheduled time, the modified output

processing priority scheme is followed to determine the schedule's

output value.

� Default Output - the special event holds the schedule in the user-

defined default output state during any unscheduled time. The exception to this user-selectable behavior is the Today and

Tomorrow special events. These events are always unscheduled if there

are no events defined for the one-day schedule; if at least one event has

been defined, then the unscheduled time will adhere to the user-selected

behavior.

Modified Output Processing

For a given date and time, an Opus weekly schedule's output value is

determined by the following priority scheme:

1: A non-null value at the "In" slot is immediately passed to the

schedule's "Out" slot.

2: If the schedule is not effective, "Out" is set to the value of the

schedule's "Default Output" property.

3: The highest priority special event that is effective. Special event

effectiveness is determined by scheduled events, if any, and the special

event default behavior .

4: The highest priority alternate schedule that is effective. If an effective

alternate schedule exists, that schedule determines the output value.

5: The active event in the default schedule (if any).

6: The "Default Output" value.



See Weekly schedule output processing in the NiagaraAX User Guide

for additional details.

Integrated Opus Schedule Entity

To assist with site configuration, the Opus Schedule Entity is a property

of each weekly schedule type. The entity property can be viewed and

edited on the Properties tab of the Opus weekly Scheduler.

Enhanced User Interface

Opus weekly schedule components are supported by a custom Opus

Weekly Scheduler view.

The following sections of the NiagaraAX User Guide contain additional

information on the scheduling model and weekly schedule concepts:

� About Scheduling

� About weekly schedules

� Using schedules

Opus Weekly Scheduler view

Opus Scheduler is an enhanced user interface for viewing and editing

Opus weekly schedule components.

The Weekly Scheduler view section of the NiagaraAX User Guide

provides details on basic Scheduler view functionality. Opus Scheduler

extends the basic view to support the advanced features of the Opus

Schedule components.



Opus Scheduler view for weekly schedule

Figure 155

The enhancements to, and differences from, the basic Scheduler view are

as follows:

� Default Schedule


� Special Events

� Properties

� Summary

Default Schedule

This tab is equivalent to the Weekly Schedule tab in the NiagaraAX

Scheduler view and supports all of its features. The following

enhancements have been added:

� Mouseover scheduled events

� Right-click menu

When the mouse moves over a scheduled event, a pop-up box displays

the event's start and end times.



Figure 156

Mouseover effect on a scheduled event.

This mouseover feature is also available when viewing Alternate

Schedules and Special Events.

Right-click in the default schedule area for a menu. This menu provides

the most commands if an event is selected.

Right-click menu with event selected

Figure 157

All options from the NiagaraAX Scheduler view's Right-click menus are

available. The event menu has been extended to include:

� Apply M-Sat - Copies all events in the selected day to Mon,

Tue, Wed, Thu, Fri and Sat (and overwrites any existing events on

those days). Alternate Schedules

This tab is used to create alternates to the schedule's default schedule.

For general information, see Alternate Schedules.


142

NOTE!

Existing alternate schedules are listed by name and summary.

alternate schedule is selected, its week schedule is displayed.

Alternate Schedules tab in Opus weekly Scheduler

Use of the Alternate Schedules

� Adding alternate schedules

� Alternate schedule priorities


� Right

Adding alternate schedules

Click the

appears.


Based on its effective period, an alternate schedule will take

precedence over the default schedule according to the Opus

weekly schedule's modified output processing priority scheme.

Existing alternate schedules are listed by name and summary.


Alternate Schedules tab in Opus weekly Scheduler

Figure 158

Use of the Alternate Schedules tab is as follows:


Alternate schedule priorities

Mouseover scheduled events

Right-click menu


Click the Add button to add a new alternate schedule. An add dialog

appears.


Based on its effective period, an alternate schedule will take

precedence over the default schedule according to the Opus

output processing priority scheme.

Existing alternate schedules are listed by name and summary. When an


An add dialog


Alternate Schedules Add

Dialog options are:

� Name

� Date Range

period for the alternate schedule. Each date is a combination of

day, month, year.

After the name and date

alternate schedule. It will remain selected for entering events.

the alternate schedule are added and modified the same as events in the

Default Schedule tab.


NOTE!


See Mouseover schedul

description of this feature.

Right-click menu

Right



Alternate Schedules Add dialog

Figure 159

Dialog options are:

Name - A descriptive name for the alternate schedule.

Date Range - The start and end date which define the effective


day, month, year.

After the name and date range have been assigned, click OK to add the

alternate schedule. It will remain selected for entering events.


Default Schedule tab.


• Effective alternate schedules take priority over the default

schedule. Among multiple effective alternate schedules,

priority is determined by the listed order in the Alternate

Schedules table. Highest priority is at the top of the list.

• An alternate schedule's priority can be changed by selecting

it and using the priority arrow buttons to move the schedule

higher or lower in the list.

An alternate schedules effectiveness is determined by its date

range.


See Mouseover scheduled events in the Default Schedule section for a


click menu

Right-click in the alternate schedules table for a menu.


143

A descriptive name for the alternate schedule.

The start and end date which define the effective


range have been assigned, click OK to add the

alternate schedule. It will remain selected for entering events. Events for


ve alternate schedules take priority over the default

schedule. Among multiple effective alternate schedules,

priority is determined by the listed order in the Alternate

Schedules table. Highest priority is at the top of the list.

priority can be changed by selecting

it and using the priority arrow buttons to move the schedule

An alternate schedules effectiveness is determined by its date

ed events in the Default Schedule section for a

This menu



provides the most commands if an alternate schedule is selected.

Right-click menu with alternate schedule selected

Figure 160

Alternate schedule menu options may include:

� Add - Add a new alternate schedule (same as using Add button).

� Edit - Edit selected schedule's effective date range (same as

using Edit button).

� Rename - Change selected schedule's name (same as using

Rename button).

� Priority (up) - Move alternate schedule up in priority list (same

as using Priority button).

� Priority (down) - Move alternate schedule down in priority list

(same as using Priority button).

� Delete - Remove selected alternate schedule (same as using

Delete button). Special Events

This tab's functionality is the same as the Special Events tab in the

NiagaraAX Scheduler view. The following enhancements have been

added:

� Today and Tomorrow special events


Today and Tomorrow special events

The user is prevented from changing the priority (or listed order) of the

Today and Tomorrow special events. Also, these events may not be

renamed or deleted.

Special Events tab in Opus weekly Scheduler



Figure 161

For general information, see Today and Tomorrow Special Events.




Properties

This tab offers the same capabilities as the Properties tab in the

NiagaraAX Scheduler view. Additionally, this tab is where users specify

the Opus weekly schedule's:

� Special Event Default

� Schedule Entity



Properties tab in Opus weekly Scheduler

Figure 162

For general information, see About Opus weekly schedules.

Special Event Default

This property is either Unscheduled (default) or Default Output.

� If Unscheduled, the modified output processing priority scheme

is followed to determine the schedule's output value during any

unscheduled time.

� If Default Output, the special event holds the schedule in the

user-defined default output state during any unscheduled time. for additional details, see Special Event default behavior .

Schedule Entity

When navigating from Opus Supervisor, the user may select from a list

of existing schedule entities or enter a new entity name. If the user is

accessing their system from a web browser, this property will be read-

only.

For additional details, see Integrated Opus Schedule Entity.

Summary

This tab offers the same functionality as the Summary tab in the


NiagaraAX Scheduler view.

Summary tab in Opus weekly Scheduler

NOTE!

About Opus weekly shifted schedules

Opus weekly shifted schedule components provide functionality not

available with NiagaraAX weekly schedules.

The weekly shifted schedule component types are:

� OpusBooleanShiftedSchedule

� OpusEnumShiftedSchedule

� OpusNumericShiftedSchedule

� OpusStringShiftedSchedule

The shifted schedule components are identical except for the data value




NiagaraAX Scheduler view.

Summary tab in Opus weekly Scheduler

Figure 163

The Source column will indicate if the Opus weekly schedule's

output value is being controlled by the Default Schedule, an

Alternate Schedule, or a Special Event.


available with NiagaraAX weekly schedules.

The weekly shifted schedule component types are:

OpusBooleanShiftedSchedule

OpusEnumShiftedSchedule

OpusNumericShiftedSchedule

OpusStringShiftedSchedule




147

column will indicate if the Opus weekly schedule's

t Schedule, an







These schedule types shift the start and end times of events within a user-

selected reference schedule. A start offset and end offset are configured

for each weekday, the Today special event, the Tomorrow special event,

and other special events. The weekday offsets are applied to the default

schedule and all alternate schedules.

As the applicable offsets are applied to each reference event, a new event

is created in the shifted schedule. Once the default schedule, all alternate

schedules, and all special events have been shifted, the resulting schedule

functions in the same way as an Opus weekly schedule.

It should be noted that the actual events of a shifted schedule are always

calculated based on the user-selected reference schedule and the user-

defined shift offsets. The user is never able to directly create an event or

directly modify the start and end times of an event in a shifted schedule.

Opus weekly shifted schedule components are supported by the Opus

Weekly Scheduler view.

The following sections of the NiagaraAX User Guide contain additional

information on the scheduling model and weekly schedule concepts:

� About Scheduling

� About weekly schedules

� Using schedules

Opus Weekly Scheduler view - shifted schedules

Opus Scheduler provides a user interface for viewing and editing Opus

weekly shifted schedule components.



Opus Scheduler view for weekly shifted schedule

Figure 164

Viewing and editing of weekly shifted schedules is as follows:

� Default Schedule


� Special Events

� Properties

� Summary Default Schedule

Use this tab to:

� Select a Reference Schedule

� Define start and end offsets


� Right-click menu

Select a Reference Schedule

The drop-down box will display a list of the available schedules which

are compatible with the data value category (Boolean, Enum, Numeric,

String) of the shifted schedule.

Reference Schedule drop-down selector


150

Once a reference schedule has been selected, the shifted schedule will

shift the reference eve

schedule. This process is performed for events in the reference schedule's

default schedule, alternate schedules, and special events.

NOTE!

Define start and end offsets

Upon initial selection of the reference schedule, all events in the shifted

schedule will be unshifted; that is, the start and end

"00h 00m".

The shift offsets can be adjusted in the same way that regular scheduled

events are modified. Click on the shifted events top or bottom and drag

to adjust the start or end offset. The start offset is displayed at the top

the shifted event and the end offset is displayed at the bottom of the

shifted event.

Start and end offsets can also be defined using the numeric fields

displayed beneath each weekday.

When a shifted event is clicked on, the relevant event details

displayed at the bottom of the tabbed pane. This includes the start and

finish time of the reference event, the shift offsets for the appropriate

weekday, and the resulting start and finish time for the shifted event.


Figure 165


shift the reference events and add the shifted events to the shifted



If the reference schedule is selected before shift offsets have

been defined, the events added to the shifted schedule will be

identical to the reference events.


schedule will be unshifted; that is, the start and end offsets will all be

"00h 00m".



to adjust the start or end offset. The start offset is displayed at the top


shifted event.


displayed beneath each weekday.

When a shifted event is clicked on, the relevant event details






nts and add the shifted events to the shifted



If the reference schedule is selected before shift offsets have

n defined, the events added to the shifted schedule will be


offsets will all be



to adjust the start or end offset. The start offset is displayed at the top of



When a shifted event is clicked on, the relevant event details will be






Start and End Offsets

Figure 166


When the mouse moves over a scheduled event in the reference schedule,

a pop-up box displays the reference event's start and end times.

Mouseover effect on a reference event

When the mouse moves over a scheduled event in the reference schedule,

a pop-up box displays the reference event's start and end times.

Mouseover effect on a reference event



Figure 167

When the mouse moves over a scheduled event in the shifted schedule, a

pop-up box displays the shifted event's start and end times.

Mouseover effect on a shifted schedule event

Figure 168

These mouseover features are also available when viewing Alternate

Schedules and Special Events.

Right-click menu

Right-click in the default schedule area for a menu. This menu provides



the most commands if an event is selected.

Right-click menu with event selected

Figure 169

The weekly schedule Right-click menu is replaced by a menu of actions

that support shifted schedule functionality. For shifted schedules, the

event menu includes:

� Apply Shifts M-F - Copies all events in the selected day to Mon,


those days).

� Apply Shifts M-Sat - Copies all events in the selected day to

Mon, Tue, Wed, Thu, Fri and Sat (and overwrites any existing

events on those days).

� Copy Day Shifts - Copies all events in the selected day to Mon,


those days).

� Clear Day Shifts - Copies all events in the selected day to Mon,


those days).

� Clear Week Shifts - Copies all events in the selected day to

Mon, Tue, Wed, Thu, Fri and Sat (and overwrites any existing

events on those days).

Alternate Schedules

This tab is used to view any alternates to the shifted schedule's default

schedule. Shifted alternate schedules are calculated by applying the user-

defined weekday offsets to any alternate schedules in the reference

schedule. The weekday shift offsets are modified from the Default

Schedule tab. For additional information on alternate schedules, refer to

Alternate Schedules in the Opus Weekly Scheduler view description.

When an alternate schedule is selected from the list in the Alternate

Schedules table, the view is similar to the Default Schedule tab.



Alternate Schedules tab for Shifted Schedule in Opus weekly Scheduler

Figure 170

Special Events

Use this tab to:

� Define start and end offsets for Today and Tomorrow special

events

� Define start and end offsets for other special events

� Mouseover scheduled events Special Events tab for Shifted Schedule in Opus weekly Scheduler



Figure 171

Define start and end offsets for Today and Tomorrow special events

Select either Today or Tomorrow from the Special Event table to modify

the shift offsets for that special event. The offsets are adjusted in the

same way as the weekday shift offsets on the Default Schedule tab. See

Define start and end offsets for details.

Define start and end offsets for other special events

A single set of shift offsets is applied to all other special events. Select a

special event (not Today or Tomorrow) from the Special Event table to

modify the shift offsets. The offsets are adjusted in the same way as the

weekday shift offsets on the Default Schedule tab. See Define start and

end offsets for details.




Properties Opus Scheduler displays the same Properties tab regardless of schedule

type (weekly or weekly shifted). When viewing an Opus weekly shifted

schedule, the Default Output and Special Event Default properties cannot

be modified; these settings are inherited from the user-selected reference



schedule.

For further details, refer to Properties in the Opus Weekly Scheduler

view description.

Summary The underlying scheduling mechanism for Opus weekly schedules and

Opus weekly shifted schedules is the same. This means that Opus

Scheduler displays the same Summary tab regardless of schedule type

(weekly or weekly shifted).

For further details, refer to Summary in the Opus Weekly Scheduler view

description.

Components in OpusSchedule module

The OpusSchedule module contains weekly schedule components which

have advanced scheduling features. See About Opus Schedules for more

information on using Opus schedules.

� OpusBooleanSchedule

� OpusEnumSchedule

� OpusNumericSchedule

� OpusStringSchedule

� OpusBooleanShiftedSchedule

� OpusEnumShiftedSchedule

� OpusNumericShiftedSchedule

� OpusStringShiftedSchedule OpusSchedule-OpusBooleanSchedule

A deployable Opus weekly schedule that provides a continuous

StatusBoolean output. The other Opus weekly schedule types are

OpusEnumSchedule, OpusNumericSchedule, and OpusStringSchedule.

See About Opus weekly schedules for more details.

If the "in" property is linked and its value is non-null, then "in" overrides

the scheduled output state.

The OpusBooleanSchedule component is available in the OpusSchedule

palette.

OpusSchedule-OpusBooleanShiftedSchedule

A deployable Opus weekly shifted schedule that provides a continuous

StatusBoolean output. The other Opus weekly shifted schedule types are

OpusEnumShiftedSchedule, OpusNumericShiftedSchedule, and

OpusStringShiftedSchedule. See About Opus weekly shifted schedules

for more details.





The OpusBooleanShiftedSchedule component is available in the

OpusSchedule palette.

OpusSchedule-OpusEnumSchedule


StatusEnum output. The other Opus weekly schedule types are

OpusBooleanSchedule, OpusNumericSchedule, and

OpusStringSchedule. See About Opus weekly schedules for more details.



The OpusEnumSchedule component is available in the OpusSchedule

palette.

OpusSchedule-OpusEnumShiftedSchedule


StatusEnum output. The other Opus weekly shifted schedule types are

OpusBooleanShiftedSchedule, OpusNumericShiftedSchedule, and


for more details.



The OpusEnumShiftedSchedule component is available in the


OpusSchedule-OpusNumericSchedule


StatusNumeric output. The other Opus weekly schedule types are

OpusBooleanSchedule, OpusEnumSchedule, and OpusStringSchedule.

See About Opus weekly schedules for more details.



The OpusNumericSchedule component is available in the OpusSchedule

palette.

OpusSchedule-OpusNumericShiftedSchedule


StatusNumeric output. The other Opus weekly shifted schedule types are

OpusBooleanShiftedSchedule, OpusEnumShiftedSchedule, and


for more details.





The OpusNumericShiftedSchedule component is available in the


OpusSchedule-OpusStringSchedule


StatusString output. The other Opus weekly schedule types are

OpusBooleanSchedule, OpusEnumSchedule, and

OpusNumericSchedule. See About Opus weekly schedules for more

details.



The OpusStringSchedule component is available in the OpusSchedule

palette.

OpusSchedule-OpusStringShiftedSchedule


StatusString output. The other Opus weekly shifted schedule types are

OpusBooleanShiftedSchedule, OpusEnumShiftedSchedule, and

OpusNumericShiftedSchedule. See About Opus weekly shifted

schedules for more details.



The OpusStringShiftedSchedule component is available in the




Spectrum® is a registered trademark of Novar Opus™ is a trademark of Honeywell International

Ethernet® is a registered trademark of Xerox Corporation MODBUS® is a registered trademark of Schneider Electric

The material in this document is for information purposes only. The contents and the product it describes

are subject to change without notice. Novar makes no representations or warranties with respect to this document. In no event shall Novar be liable for technical or editorial omissions or mistakes in this document, nor shall it be liable for any damages, direct or incidental, arising out of or related to the use of this document. No part of this document

may be reproduced in any form or by any means without prior written permission from Novar.

Copyright © 2011 by Honeywell International, Inc.. All Rights Reserved.

Novar 6060 Rockside Woods Blvd.,

Cleveland, OH 44131 Phone: 1.800.348.1235

www.novar.com.

opus 58 user guide - novar v5-8... · opus supervisor user guide user guide 2/1/2012 3 for the...

Documents