opus supervisor user guide - novar.com v5-5...user guide 4/15/2011 1 for the latest technical...

USER GUIDE 4/15/2011 1 For the latest technical documentation, visit www.novar.com/manuals

Opus Supervisor User Guide Table of Contents

About Opus ........................................................................................... 2 Opening the Station .............................................................................. 3 Adding a New Group ............................................................................ 5 Adding a New Site ................................................................................ 7 Adding New XCM ................................................................................ 8 Simulation ............................................................................................. 13 Adding Network ................................................................................... 13 Assign XCM IP Address....................................................................... 17 Platform Tunneling ............................................................................... 19 Baseline Configuration ......................................................................... 22 Download .............................................................................................. 23 Importing Deployed Sites ..................................................................... 26 Backup .................................................................................................. 28 Restore .................................................................................................. 32 Adding Template .................................................................................. 33 Importing a template ............................................................................. 35 Exporting a template ............................................................................. 35 Batch Service and Operations ............................................................... 36 Configuring LDAP in Opus Supervisor ................................................ 48 Profiled Workbench Single Sign-On .................................................... 51 Opus Upgrade Tool ............................................................................... 53 Customizing Opus ................................................................................ 55 Quick Connect ...................................................................................... 56 Quick Disconnect .................................................................................. 58 Navigation ............................................................................................. 58 Disconnect Supervisor .......................................................................... 60 About Opus History and Alarms .......................................................... 60 Alarms................................................................................................... 64 Configuring Opus SQL Driver ............................................................. 71 Conditional Alarm Channels ................................................................ 75 Identifying Opus Control Entities ......................................................... 77 History Configuration ........................................................................... 78 History View ......................................................................................... 86 Live History View ................................................................................ 89 Boolean Shifted Schedule ..................................................................... 94 Boolean Daily Shifted Schedule ........................................................... 97 Curve Fit ............................................................................................... 101 Installing Theater Schedule .................................................................. 101 Configure Theater Schedule ................................................................. 102 Using Theater Schedule ........................................................................ 103 Theater File Requirements .................................................................... 106 Thin Client ............................................................................................ 110 Viewing Hx Profile ............................................................................... 112

http://www.novar.com/manuals�

Opus Supervisor User Guide

2 USER GUIDE 4/15/2011 For the latest technical documentation, visit www.novar.com/manuals

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




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.

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

computer is the computer on which the Opus Supervisor was installed.

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.

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.




Step Procedure

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.

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.

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.

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. 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


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.

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.

Note: You cannot edit the XCM name.

2 Click Edit next to the XCM Number. A dialog box appears prompting you to enter the XCM number.

3 Type the XCM number of your choice. 4 Click OK. The new XCM Number is updated in the XCM number

field of the property sheet. 5 Click Save on the property sheet to save the changes made to the

XCM controller.

Start/Stop XCM controller station

You can start and stop the simulation Run Mode of the XCM controller station. These options are available until after the XCM station configuration has been downloaded to the remote XCM.

To stop running the XCM controller station

Step Procedure

1 Right-click the XCM you want to stop in the Opus Explorer and select Stop Run Mode. A confirmation message appears.

2 Click Yes.




To resume running the XCM controller station

Step Procedure

1 Right-click the XCM you want to resume in the Opus Explorer and select Start Run Mode. An authentication dialog box appears prompting for the user name and password for the XCM controller.

2 Type the Username and the Password. Click OK.

NOTE!

The Opus Supervisor can support up to 30 XCM controllers simultaneously running in the simulation mode.

XCM AutoDiscovery Using this feature you can discover all the downloaded XCMs on the network that are accessible to the supervisor.

Step Procedure

1 Right-click Opus Systems on the Opus Explorer. 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.

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.

4 Set Enabled to True to activate the service.

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

1 Right-click the XCM controller in the Opus Explorer list. 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.




Step Procedure

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

dialog box appears.

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.




Step Procedure

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

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.

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.

From the Property sheet

To assign an XCM IP address from the property sheet

Step Procedure

1 Select the XCM controller in the Opus Explorer list. 2 Right-click the XCM controller and select Property Sheet from the

list. The property sheet of the XCM is displayed in the right pane. 3 Type the IP address of the XCM in the XCM IP Address box. 4 Click Save on the property sheet.




When downloading

To assign an XCM IP address while downloading

Step Procedure

1 Select the XCM controller you want to download to the field controller in the Opus Explorer list.

2 Right-click the XCM controller and select Download from the list. A 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 OK. The IP address is saved in the property sheet of the XCM.

For more details on downloading, see Download. Show Platform

Platform provides access to the XCM controller hardware setup and operating system properties of the XCM site controller. This access also 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 using Show XCM Platform option.

NOTE!

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.

To Access the XCM Platform using Show Platform menu option

Step Procedure

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

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

station is replaced by the XCM platform.




Step Procedure

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.

Returning to Off-line XCM station

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

Step Procedure

1 Right-click the XCM controller in the Opus Explorer list. 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.




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.

2 Right-click WebServices and select Views > Opus Property Sheet. The property sheet of Web Service is displayed on the right pane.

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




In XCM

To enable Platform Tunneling in XCM

Step Procedure

1 Expand Opus Systems in the Opus Explorer list. 2 Right-click the XCM and select Property Sheet. The property sheet

of the XCM is displayed on the right pane.

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

example, type 199.63.214.115. 4 Under Tunnel Platform Port, type the port number of the tunneled

platform. For example, type 8080.

NOTE!

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.

Opening Tunneled Station

Step Procedure

1 In left pane of the Profiled workbench, right-click the root node in Opus Explorer and select Open Station Tunnel. The Open Station dialog box appears.

2 An authentication dialog box appears with the default station user

name and password.




Step Procedure

3 Click OK.

Opening Tunneled XCM

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.

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.




Step Procedure

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.

4 Click OK. A message box appears with the list of the steps performed during to accomplish the download.




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: 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.

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. 4 Type the Username. The default username is admin. 5 Type the Password. The default password for the username admin is

blank. 6 Click OK.

Note: The Remember these credentials check box is selected by 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. 8 You need to supply the Group, Site and XCM name and numbers for

this remote XCM.




Step Procedure

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.

If the remote XCM has been deployed with Opus Supervisor on or after version 5.0.2.

15 The remote XCM station configuration will be imported into the Opus Supervisor as being already downloaded.




Step Procedure

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

1 Right-click the XCM controller in the Opus Explorer list. 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.

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.

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.

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.

NOTE!

The Trigger Schedule screen provides a view of the calendar. The scheduled dates are highlighted in green in the calendar.




Backing Up using the Niagara Network Job Prototype option

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

Step Procedure

1 Double-click NiagaraNetworkJobPrototype under Global Services in the Opus Explorer list. The schedule appears in the right pane.

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

Job Step dialog box appears. 3 Select the Backup Stations type and click OK. The type appears in

the view under Steps to run for each station. 4 Click the Add button under Stations to include in the job. The Add

Device dialog box appears with all the XCM controllers in the supervisor.

5 Check the devices to be added to the job and click OK. The XCM controllers selected appear in the view under Stations to include in the job.

6 Click Save to save the controllers selected for the job. 7 Click the Run Now button to take a backup of the XCM controller

station immediately. 8 Right-click the Backups folder under the XCM controller in the

Opus Explorer list. 9 Select Sync to view the backup file.




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.

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.




Step Procedure

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.

NOTE!

If you provide an existing site or XCM number, an error message appears, prompting you to enter a new number.




Importing a template Templates created within the Template Library can be shared with others that may not have access to the same Opus Supervisor that contains your 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. These templates can then be imported into a Template Library folder within your Opus Supervisor.

To import a template

Step Procedure

1 Navigate to and right-click the target template folder in the Opus Templates folders.

2 Select Import Template from the list. The File Chooser dialog box appears.

3 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.

4 Click OK.

NOTE!

If the import fails, an error message appears stating that the template already exists.

Exporting a template Templates created within the Template Library can be shared with others that may not have access to the same Opus Supervisor that contains your 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 Supervisor for reuse.




To export a template

Step Procedure

1 Expand the templates folder in the OpusTemplates. 2 Navigate to the template you want to export. 3 Right-click the selected template and select Export Template.

The File Chooser dialog box appears. 4 Select the folder to which you want to export the template and click

Save. A confirmation message appears. 5 Click OK to export the file to the desired folder.

NOTE!

If the export fails, an error message appears stating that the template is not exported.

Batch Service and Operations

Opus supervisor allows you to apply common setpoint changes or schedule changes across multiple sites. You can select one or more control entities from these sites and create batch jobs to perform the changes. The tool also provides a service that can be run at specified intervals to update the setpoint and schedule entities. 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, and delete these batch jobs.




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 Procedure

1 On the Opus Explorer, expand Opus Systems>group>site>XCM to view the supervisor station.

2 Expand Station>Config>Services to view the OpusBatchService option.

3 Double-click OpusBatchService. The property sheet of the batch service is displayed on the right pane.

NOTE!

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), the supervisor station on which the service is running. The follwing 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 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.


4 Browse to OpusEnterprise and click OK. The contents of the Opus Enterprise folder appear under Palette.




Step Procedure

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.

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. 2 Right-click Control Settings and choose Views > Opus Slot Sheet.

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

added to the batch setpoint list. 4 Click SlotSheet on the menubar 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.

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.

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 sites from the list. The list of XCMs under the selected sites

is displayed under XCM. 6 Select the XCMs from the list. The list of field controllers under the

selected XCMs is displayed under Controller. 7 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.

8 Click Next. The Batch Setpoint screen displays the Batch setpoint components.




Step Procedure

9 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.

Note: If the component is not selected, the setpoint values are not updated to the selected controllers.

10 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.




Step Procedure

11 Click Home to return to the Batch Setpoint Jobs screen. The setpoint 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.

12 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.




Step Procedure

13 Click the job in the job history list to view the details of the executed job in the Batch Job History screen.

14 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. 3 On the Palette, click the Open Palette button. The Open Palette

dialog box appears. 4 Browse to Schedule and click OK.

The various schedule types such as Booleanschedule, Enumschedule, Numericschedule as so on appear under Palette.




Step Procedure

5 Drag the schedule types that require batch scheduling, onto the folder you have created on the Opus Explorer.

6 On the Palette, click the Open Palette button. The Open Palette

dialog 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.

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 sites from the list. The list of XCMs under the selected sites

is displayed under XCM. 6 Select the XCMs from the list. The list of field controllers under the

selected XCMs is displayed under Controller. 7 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.

8 Select the Special Events check box to schedule events to be performed on a specific day.

9 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

10 Select the time duration for a day on the Batch Schedule screen, to set a batch schedule.

11 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.

12 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 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.

14 Click the job in the job history list to view the details of the executed job in the Batch Job History screen.

15 Click Home to return to the Batch Schedule Jobs screen. or Click Back to return to the previous screen.

Configuring LDAP in Opus Supervisor

Opus supports LDAP authentication where the user can connect to the 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 individual XCM.

NOTE!

Opus supports both local and remote LDAP users.

In Supervisor Station

Configuring the LDAP in Supervisor Station

Step Procedure

1 Connect to a running Opus Supervisor station as an administrator. See Opening the station section for more details.

2 Expand Station > Config > Drivers in the Opus Explorer list in the left pane.

3 Right-click NiagaraNetwork and select Views > Opus Property Sheet. The property sheet of Niagara Network is displayed on the right pane.




Step Procedure

4 Expand Fox Service and under Authentication Policy select Basic.

5 Open the ldap module in the palette.

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.




Step Procedure

11 Right-click Default Prototype and select Views > Opus Property Sheet. The property sheet of Default Prototype is displayed on the right pane.

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.




Step Procedure

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 In the User Base box, enter the domain server components. 7 In the Attr Email box, enter the e-mail address of the user. 8 Click Save on the property sheet to save the changes.

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-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

Step Procedure

1 In the Opus Explorer list, expand Station and right-click Config. 2 Select Views > Property Sheet. The property sheet of Config is

displayed on the right pane.

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

4 Click to add a new facet row. 5 In the Key box, click and select realms. 6 In the Type box, click and select String. 7 In the Value box, type the name of the realm.

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

8 Click OK to add the facet.




Step Procedure

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 and 5.4) to Opus 5.5. 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 there credentials Supervisor PX files Supervisor image files Supervisor HTML files XcmLCD images




To upgrade the OPUS Supervisor configuration

NOTE!

Before upgrading the Opus configurations, ensure that you have stopped the Supervisor station in both the current and previous versions of Opus supervisor.

Step Procedure

1 On the menu bar, click Tools > Opus Upgrade Tool. The Opus Upgrade Locations dialog box appears.

2 In the Previous Installation directory box, click Choose. The

Directory Chooser dialog box appears. 3 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 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 Current Installation directory box, click Choose. The Directory Chooser dialog box appears.

5 Navigate to the folder where the current instance of Opus Supervisor is installed.

6 Click Next. The Opus Upgrade Steps dialog box appears. By default, all the options are selected.




Step Procedure

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.

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 menubar. 2 Select Style Configurator from the list. The Style Configurator




Step Procedure

dialog box appears.

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.

2 Click the Quick Connect button on the toolbar. The Quick Connect dialog box appears.




Step Procedure

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

present in the Opus Supervisor. 4 Type the Site Number of the site from the selected group. 5 Type the XCM Number of the XCM controller from the selected

site. 6 Click OK. An authentication dialog box appears with the default

station user name and password. 7 Click OK. You are connected to the station.

NOTE!

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.

Connect/Disconnect Station View

You can connect to or disconnect from the remote XCM station in the Opus Explorer list using the Connect and Disconnect options.

To disconnect a station view

Step Procedure

1 Right-click the downloaded station in the Opus Explorer list. 2 Select Disconnect from the list. A confirmation message appears. 3 Click Yes.

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.

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.

NOTE!

The Disconnect All button disconnects all the sessions under Connected Sessions.

Navigation The Opus Supervisor maintains a multi-site enterprise component 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 navigation lists provided in the Group, Site and 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 Procedure

1 Expand Opus Systems to view the list of groups in the Opus 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. 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.

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

routed to the remote XCM station.




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.

About Opus History and Alarms

This module provides the supervisor station components for enterprise alarm and history management.

Adding SqlServer database

Step Procedure

1 Drop the RdbmsNetwork from the palette into Config > Drivers on the supervisor.

2 Drop the OpusSqlServerDatabase into the RdbmsNetwork.




Step Procedure

3 Open the property sheet for the OpusSqlServerDatabase and set

your DB connection information.




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

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.




Step Procedure

2 Open the property sheet for OpusAlarmService and pick your

database in the Driver property.




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. Once these alarms are store in the database they can be viewed from the Alarm Console Viewer in the Opus Supervisor. Alternately, the Novar Alarm Pro application will provide an enhanced set of alarm management features for the Opus alarms.

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.

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

database creation script.




Step Procedure

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 will route 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 the Opus Explorer list.

2 Right-click OpusAlarmService and select Views > Property Sheet. 3 Select the database driver from the list in the Driver field.

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 Navigate to and connect to the XCM station configuration. 2 Navigate to the Services directory and open the Alarm Service

wiresheet view.

3 In the palette, open the OpusHistoryAlarmME module. 4 Drag and Drop 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 pull down list and set the Remote Station to the

OpusSupervisorStation.

NOTE!

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 more reporting channels using the OpusEnterpriseRecepient component. Refer Conditional Alarm Channels for more details.

Configure an Opus Alarm Extension

Step Procedure

1 Navigate to and connect to the XCM station configuration. 2 Navigate to the Opus Control entity that requires an alarm setup.

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

OpusControlEntity component from the OpusEnterprise palette. 4 Navigate to and find the I/O point or value you want an alarm on.

5 From the OpusEnterprise palette, select the Opus Alarm Extension

type and drag and drop 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 Alarm Console View displays the XCM controller alarms that are sent to the supervisor.

NOTE!

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

The view displays the alarm details such as, Timestamp Source State Ack State Source Alarm Class Priority Alarm Type

You can add more columns to the view by selecting the column name from the drop-down list.




Each of the columns in the Alarm Console view can be customized. The width of the columns can be increased or decreased by placing your cursor on the header and dragging the column to the right or left. The columns can be sorted in an ascending or descending order by clicking the column header. The columns in the view can be swapped by using the option Swap Columns from the list. The columns can be restored to their original size using Reset Column Widths from the list. The order of the columns can be restored to their default order using Reset to Default Column Order.




Configuring Opus SQL Driver

The Opus Supervisor provides drivers for alarms to be written to a either Microsoft SQL database (minimum: MS-SQL 2005) or the open source H2 database.

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.

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. or Drag OpusH2Database from the Palette onto RdbmsNetwork in the Opus Explorer list, if you are using H2 database server. The database node is displayed under RdbmsNetwork in the Opus Explorer list.




Step Procedure

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.

6 Double-click the database node in the Opus Explorer list, to view the property sheet of the database driver.

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.

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

A connection will be 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. 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.

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


2 Right-click OpusSqlServerDatabase and choose Actions > Database Scripts.




Step Procedure

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

database creation script.

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 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


2 Right-click OpusSqlServerDatabase and choose Actions > Persist Enterprise Model Data.

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

displayed with the status of the DB script execution.

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 safe alarm report channels to secondary and tertiary Opus Supervisor alarm collectors.

Configure Conditional Alarms

To configure conditional alarms:

Step Procedure

1 On the Nav palette, expand OpusSystems and browse to the station of the XCM which needs to be configured with a secondary supervisor.

2 Expand Station > Config > Services. 3 Right-click AlarmService and select Views > Opus Wire Sheet.

The wiresheet of the Alarm service displays the default configuration components on the right pane.

4 Drag an OpusEnterpriseRecepient component from the palette. Refer to Alarm Configuration at XCM section of Alarms for more details on adding an OpusEnterpriseRecepient component.

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




NOTE!

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 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.

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.

To identify an Opus Control Entity

Step Procedure





Step Procedure

2 Navigate to a field controller in the XCM station configuration 3 Open the OpusEnterprise module in the palette. 4 Drag and drop the OpusControlEntity component to the field

controller property sheet. 5 Enter a new Application Name or select previous name from the

drop down list. 6 Enter a new Application Type or select previous type from drop

down list. 7 Click Save.

NOTE!

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.

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 Supervisor and archived into a relational database. Once these logs are store in the database they can be viewed from the History Viewer in the Opus Supervisor. 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

1 Browse to and connect to the XCM station configuration. 2 Browse to the Opus Control entity that requires a trend log setup.

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

OpusControlEntity component from the OpusEnterprise palette. 4 Browse to the I/O point or value you want a trend log on.

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,




Step Procedure

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.


History Configuration at OpusSupervisor

Choosing History Import data source

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.

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.

Step Procedure

1 Browse to the Niagara Network of the Opus Supervisor station. 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.

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 transfering the histories.

7 Along with transferring histories to Supervisor File system, an xml 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, when the chosen database is Local Supervisor file system. There is a Sync action provided under Services->OpusHistoryService, 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




Step Procedure

in sync.

Export Trend Logs to database

Configuring the Database Driver

The Opus Supervisor provides drivers for alarms to be written to an either Microsoft SQL database (minimum: MS-SQL 2005).

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.




Step Procedure

3 Select OpusHistoryAlarmSE from the list and click OK.

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. or Drag OpusH2Database from the Palette onto RdbmsNetwork in the Opus Explorer list, if you are using H2 database server. The database node is displayed under RdbmsNetwork in the Opus Explorer list. 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.

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 will be 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 you must perform the following configuration steps.




Step Procedure

1 Browse to the OpusSqlServerDatabase in the Opus Supervisor station.

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

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.Use the following procedure to graphically view the history in Opus. 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.

2 Click New.

3 The History View enterprise selection page appears.




Step Procedure

4 Enter the Name and Description of user or site. 5 Select one or more groups from the Group list.

A list of sites associated to the selected groups is displayed under the Site column.

6 Select one or more sites from the Site list. A list of XCMs associated to the selected sites is displayed under XCM.

7 Select the XCMs from the XCM list. A list of control entities associated to the selected XCMs is displayed under Controller . Tip: Use the Filter option to quickly search for a Control Entity. Type the initial characters of the control entity and click Filter. 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 control enttities from the Controller column and click Next. The following page appears.




Step Procedure

9 Select one or more point names from the Point Names column.

NOTE!

Select the button in the header row to select all the point names simultaneously.

10 Select the Chart option from the Default View list. The available options are Chart and Table.

11 Select the Show option from the Gridlines list to view the gridlines on the chart. The available options are Show and Hide.

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.

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.




16 Click Table View. The Table View page appears. You can view

the tabular data for the selected points.

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 hostory 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.

3 Drag and drop the History Point List list Item below History Point List list in XCM station folder. The following page appears.

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. 12 Click Save. Go to OpusHistoryPointList properties page.




Step Procedure

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. 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.




Step Procedure

19 Click Switch to Chart. The Live Chart View page appears.

20 Click to view the difference between two consecutive points in

table rows or on charts. 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.




Step Procedure

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.




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 special events of the referenced boolean schedule.

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. 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.

2 On the Ref property, click the drop-down list and select

Component Chooser.




Step Procedure

The Select Ord dialog box will be displayed.

3 Locate the reference Boolean Schedule in the component tree;

hightlight 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 special events of the referenced 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.




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.




Step Procedure

2 On the Ref property, click the drop-down list and select

Component Chooser.

The Select Ord dialog box will be displayed.




Step Procedure

3 Locate the reference Boolean Schedule in the component tree;

hightlight 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 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.

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


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.

5 Type a name for the theater schedule and click OK. The theater schedule appears under Services.




Step Procedure

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. 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.




Step Procedure

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.

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.

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.




When the Theater Schedule timer triggers and the current theater file is 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.




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.

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.




Opus System browsing

Step Procedure

Browse the deployed XCM stations through the Opus Explorer or the Group, Site and XCM Directories in the main window pane.

Use the following procedure to connect to the XCM controller station

Step Procedure

1 Double-click the station in the Opus Explorer list. An authentication dialog box appears prompting you to type the station user name and password.

2 Type the station user name and password. Click OK.

NOTE!

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 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.

Backups and templates are not accessible through thin client.

However, Alarms and History are editable.




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

displayed on the right pane. 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.

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.




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.

3 Double-click the XCM. A dialog box appears prompting you for the

XCM station Username and Password.

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.

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 © 2010 by Honeywell International, Inc.. All Rights Reserved.

Novar 6060 Rockside Woods Blvd.,

Cleveland, OH 44131 Phone: 1.800.348.1235

www.novar.com.


http://www.novar.com/�

opus supervisor user guide - novar.com v5-5...user guide 4/15/2011 1 for the latest technical...

Documents