andover continuum

7/16/2019 Andover Continuum

http://slidepdf.com/reader/full/andover-continuum-563385882b44d 1/746

Andover Continuum CyberStation

Configurator’s Guide for Version 1.8



TAC ii

© 2006, TAC

All Rights Reserved

No part of this publication may be reproduced, read or stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying,recording, or otherwise, without prior written permission of TAC.

This document is produced in the United States of America.

Infinity is a trademark of TAC. All other trademarks are the property of their respectiveowners.

Andover Continuum CyberStation Configurator’s Guide for Version 1.8 December , 2006

TAC part number: 30-3001-781

The information in this document is furnished for informational purposes only, is subjectto change without notice, and should not be construed as a commitment by TAC. TACassumes no liability for any errors or inaccuracies that may appear in this document.

TAC, Inc.One High Street

North Andover, MA 01845(978) 470-0555Fax: (978) 975-9782http://www.tac.com



Andover Continuum CyberStation Configurator’s Guide iii

Contents

1 Introduction ................................................................................................................ 1 About this Guide...........................................................................................................1 Key Concepts ............................................................................................................... 3 Andover Continuum Product Description..................................................................... 5 CyberStation............................................................................................................... 12 Starting CyberStation .................................................................................................14 Closing CyberStation..................................................................................................15

2 Menu Pages .............................................................................................................. 17 The CyberStation Main Menu .................................................................................... 17 Accessing the Online Help System............................................................................ 22 Menu Page Selections ...............................................................................................23 Configuring New Menu Pages ................................................................................... 32 Button Wizard............................................................................................................. 36

3 Continuum Explorer................................................................................................. 39 Objects in Continuum Explorer .................................................................................. 39 Starting Continuum Explorer ......................................................................................45 Dropdown Menus ....................................................................................................... 46 Quick Picks Toolbar ...................................................................................................54 Popup Menus ............................................................................................................. 55 Continuum Explorer Window...................................................................................... 55 Explorer Views ........................................................................................................... 58 Creating Objects......................................................................................................... 62 Importing from ASCII Dump Files ..............................................................................65

Importing from CSV Files ........................................................................................... 66 Creating CSV Files for CyberStation.......................................................................... 67 Updating or Creating Personnel Objects from CSV Files ..........................................68 CyberStation Object Editors....................................................................................... 70 Access Security Rules in Continuum Explorer ...........................................................70

4 Security ..................................................................................................................... 73 Security Groups.......................................................................................................... 73 Configuring Object-Level Security.............................................................................. 80



TAC iv

Folder and Device Level Security...............................................................................85 5 Configuring Users ....................................................................................................89

What Are Users? ........................................................................................................89 Customizing the User Environment............................................................................ 89 Before Configuring Users ........................................................................................... 90 Creating a User Object...............................................................................................90 Groups Tab – User Editor .......................................................................................... 93

SecurityLevel Tab – User Editor................................................................................. 93 Setting up the General and CFR Preferences ........................................................... 94 Creating a ControllerUser Object ............................................................................. 100

6 Configuring a Network........................................................................................... 103 Creating a Network Object .......................................................................................104 Assigning a Network Object to a Default Folder .....................................................105

7 Configuring Controllers......................................................................................... 107 Commissioning a Controller .....................................................................................108 Creating an InfinityController Object ........................................................................109 Creating a bCX1 (40x0) or b4920 Controller............................................................122 Sending Controller Data to the CyberStation Database .......................................... 123 Working With Infinet Controllers ..............................................................................124 Creating an Infinity Infinet Controller Object ............................................................125 Creating an Infinet Controller Offline........................................................................ 126 Editing an Infinet Controller Object .......................................................................... 126

8 Configuring Comm Ports....................................................................................... 131 Supported Device Types ..........................................................................................131 Configuring a Comm Port for a Terminal .................................................................132

Configuring a Comm Port for a Printer .....................................................................133 Configuring a Comm Port for a LBus .......................................................................133 Configuring a Comm Port for a TankNet..................................................................134 Configuring a Comm Port for XDrviers..................................................................... 134 Configuring a Comm Port for Infinet, MS/TP, or Wireless ....................................... 135

Configuring a Comm Port......................................................................................... 137



Andover Continuum CyberStation Configurator’s Guide v

9 Creating IOU Module Objects ............................................................................... 147

Creating an IOU Module Object ...............................................................................148 Commissioning an IOU Module ...............................................................................149 Replacing an IOU Module ........................................................................................150

10 Configuring Alarms................................................................................................ 151 Considering the Alarm System................................................................................. 151 Alarms and BACnet.................................................................................................. 151 Considering the Alarm System................................................................................. 151 Basic Steps for Setting Up Alarms .......................................................................... 152 About EventNotification Objects ..............................................................................152 About Configuring Alarm System Components ....................................................... 152 Using the EventNotification Editor............................................................................ 154

Distributing Tasks to Several Workstations.............................................................. 163 About AlarmEnrollment ............................................................................................ 168 Using the AlarmEnrollment Editor ............................................................................ 169 Writing Alarm Messages .......................................................................................... 175 Attaching Alarms to a Point ......................................................................................176 Active Alarm View .................................................................................................... 180 Infinet Intrinsic Alarms.............................................................................................. 196 Database Fault Detection Alarm .............................................................................. 199

11 Configuring Reports .............................................................................................. 201 Overview................................................................................................................... 201 Source Tab............................................................................................................... 204 Configuring Columns for a Report............................................................................ 212 Filter Tab .................................................................................................................. 215 Output Tab ............................................................................................................... 219 Scheduling Automatic Reports................................................................................. 224 What Are Extended Logs? .......................................................................................230 The ReportViewer ....................................................................................................230

12 Templates................................................................................................................ 237 About CyberStation Templates ................................................................................237



TAC vi

Creating a Template Object ..................................................................................... 239 Creating an Object from a Template ........................................................................241 Editing an Object Created from a Template .............................................................240

13 Points, Logs, and Triggers.................................................................................... 243 What is a Point? ....................................................................................................... 243 About InfinityInput and InfinityOutput Points ............................................................244 Before You Start....................................................................................................... 245

Creating an InfinityInput Object ................................................................................245

InfinityOutput Points .................................................................................................261 Creating an InfinityOutput Object .............................................................................261 About Infinity Software Points .................................................................................. 267 Creating Infinity Software Points ..............................................................................267 About BACnet Points................................................................................................ 273

14 BACnet .................................................................................................................... 275 What is BACnet? ...................................................................................................... 275 Andover Continuum’s BACnet Product Line ............................................................277 BACnet-Related Documentation ..............................................................................277 Post Installation System Integration......................................................................... 278 The Device Editor..................................................................................................... 288 Configuring BACnet Alarms .....................................................................................311 BACnet Defined Objects ..........................................................................................330 Infinity and BACnet Object Editors........................................................................... 333

15 Configuring Schedules and Calendars................................................................371 Schedule Views – Finding Your Way Around .......................................................... 372 Configuration Tab..................................................................................................... 376 Working with Exception Schedules .......................................................................... 383 Working with Standard Days and User-defined Days.............................................. 391 Current State Tab..................................................................................................... 399 Proprietary Schedule Properties for Programs ........................................................400 Mass Create – Populating Devices with a Schedule ...............................................401 Mass Change – Updating Multiple Schedules .........................................................404 Calendars and the Calendar Editor.......................................................................... 406



Andover Continuum CyberStation Configurator’s Guide vii

16 Configuring Loops .................................................................................................411 Overview................................................................................................................... 411 General Tab ............................................................................................................. 412 Tuning Tab ............................................................................................................... 416 What Is PID? ............................................................................................................ 419 Tuning the PID Loop ................................................................................................421 Customizing the PID Graph......................................................................................422

Basic Alarms Tab and Advanced Alarms Tab..........................................................429

17 Configuring Trend Loops ...................................................................................... 433 Overview................................................................................................................... 433 General Tab ............................................................................................................. 434 Data Tab...................................................................................................................437 Extended Logging Tab ............................................................................................. 440 Basic Alarms Tab ..................................................................................................... 441

18 Configuring Areas and Doors ............................................................................... 447 Configuring Andover Continuum for Security and Access Control .......................... 447 Key Terms for Access Control .................................................................................447 About Areas, Doors, and Personnel.........................................................................449 Sequence for Creating Access Control Objects....................................................... 451 Creating an Area Object........................................................................................... 452 Creating a Door Object............................................................................................. 452 Data that Defines a Door Object ..............................................................................452 General Tab – Door Editor .......................................................................................453 Card Formats Tab – Door Editor.............................................................................. 454 Channels Tab – Door Editor.....................................................................................455 Options Tab – Door Editor........................................................................................460 XDriver Tab – Door Editor ........................................................................................461 Entry Reader Tab – Door Editor............................................................................... 462 Entry Options Tab – Door Editor ..............................................................................464

Entry Status Tab – Door Editor ................................................................................465 Exit Reader Tab – Door Editor ................................................................................. 466 Exit Options Tab – Door Editor ................................................................................468



TAC viii

Exit Status Tab – Door Editor...................................................................................469 Alarms Tab – Door Editor.........................................................................................469 Access Events Tab – Door Editor ............................................................................469 Using Area Lockdown ..............................................................................................470 More About Area Lockdown.....................................................................................470 What Happens During Lockdown.............................................................................471 Locking down an Area..............................................................................................471

Locking down Individual Doors................................................................................. 472 Controlling Access with Condition Levels ................................................................ 472 Sending a Condition Level Message to Controllers ................................................. 473 Restoring Controller Condition Levels to Previous Levels .......................................473 About Sending Condition Level Values to Individual Controllers ............................. 474

19 Personnel ................................................................................................................ 475 Personnel Manager .................................................................................................. 475 Enabling the Personnel Manager.............................................................................477 Adding New Personnel Objects................................................................................ 477 Editing a Personnel Object.......................................................................................480

Making/Editing a Badge ........................................................................................... 485 Reading Card Information ........................................................................................491 Replacing Card Information......................................................................................492 Issuing or Restoring a Temporary Card ...................................................................492 Marking a Card as Lost ............................................................................................ 493 Deleting Personnel Objects......................................................................................493 Working with Personnel Clearance Levels and Controller Condition Levels ........... 494 Configuring the Personnel Manager ........................................................................ 498 Creating a Personnel Profile .................................................................................... 500 Customizing Personnel Attributes ............................................................................506 Selecting Configuration Settings for the Personnel Manager ..................................508 Personnel Import Utility ............................................................................................ 510

What Can I do with the Personnel Import Utility?.....................................................511

Configuration Tab..................................................................................................... 515

Mapping Data Source Attributes to CyberStation Personnel Attributes................... 520



Andover Continuum CyberStation Configurator’s Guide ix

Previewing Data ....................................................................................................... 522

Data Source Data Tab.............................................................................................. 523

Transforming Data Using the XSLT File .................................................................. 524

Saving a Configuration and Importing Data into CyberStation ................................ 526

20 Managing Personnel Distribution......................................................................... 529 Access Distribution View.......................................................................................... 529 Launching and Populating the Access Distribution View ......................................... 531

Filtering Distribution Events in Access Distribution View ......................................... 532

Using Columns in the Access Distribution View....................................................... 535 Using Toolbar Buttons in Access Distribution View ................................................. 540 Distributing Personnel Immediately — Distribute Now ............................................ 540

21 Managing Configuration Files............................................................................... 543 Overview................................................................................................................... 543 General Tab ............................................................................................................. 544 Backing Up a Device’s Configuration....................................................................... 545 Restoring a Device’s Configuration.......................................................................... 547

22 Creating Groups .....................................................................................................549 What is a Group? ..................................................................................................... 549 What is a Graph? ..................................................................................................... 550 Using the Group Editor.............................................................................................551 Opening a Log Viewer..............................................................................................559 Editing a Group from the Log Viewer .......................................................................559

23 Creating ListViews ................................................................................................. 561 What is a ListView? .................................................................................................. 561 About Creating a New ListView................................................................................ 561 Using the ListView Editor ......................................................................................... 561 Test and Save ..........................................................................................................573 Creating a History or Graph of a ListView................................................................ 574

24 Creating EventViews.............................................................................................. 577 Overview................................................................................................................... 577 Before Creating an EventView ................................................................................. 578 Creating an EventView............................................................................................. 579



TAC x

The Active Event View ............................................................................................. 583 25 Configuring and Viewing Video ............................................................................ 593

Overview of Video Integration and Configuration.....................................................593 Using the VideoServer Editor ................................................................................... 596 Using the VideoLayout Editor...................................................................................597

26 Graphics Panels ..................................................................................................... 605

Introduction............................................................................................................... 605Pinpoint Environment ...............................................................................................613 Configuring a Pinpoint Panel....................................................................................615 Selecting Default Properties for Components ..........................................................618 Creating an Active Text Component ........................................................................ 619 Inserting Images....................................................................................................... 621 Creating an Active Switch Control............................................................................ 621

Creating an Active Rotation Control......................................................................... 622 Creating a Personnel Picture Switch Control ...........................................................623 Creating an Active Bar Control.................................................................................624 Creating an Active Button Control............................................................................625 Creating an Active n-Stage Animation Control.........................................................628 Creating an Active Animated Button Control............................................................632 Inserting a Scale.......................................................................................................636

Inserting a Gauge..................................................................................................... 637

Importing a Pinpoint Panel .......................................................................................639 Creating Windows Controls......................................................................................639

Controlling a Door .................................................................................................... 664 A Using the Personnel Editor ...................................................................................671

General Tab – Personnel Editor............................................................................... 672 Area List Tab – Personnel Editor .............................................................................674 Privileges Tab – Personnel Editor............................................................................678 Employee Info Tab – Personnel Editor ....................................................................678 Personnel Info Tab – Personnel Editor ....................................................................679

Current Status Tab – Personnel Editor ....................................................................680 Access Events Tab – Personnel Editor....................................................................681



Andover Continuum CyberStation Configurator’s Guide xi

Templates Tab – Personnel Editor...........................................................................681 Custom Attributes Tab – Personnel Editor............................................................... 682 Security Tab – Personnel Editor ..............................................................................682

B EpiBuilder Installation ...........................................................................................685

Installing EPIBuilder ................................................................................................. 686

C Personnel Import Utility Tables and Sample XSLT File .....................................687

Active Directory Attributes Table.............................................................................. 688Continuum Personnel Attributes Table .................................................................... 691

Card Type Table....................................................................................................... 695

Active Directory ........................................................................................................ 696

LDAP Protocol..........................................................................................................701

Sample XSLT File .................................................................................................... 704

D Scheduling Automatic Personnel Object Updates .............................................711

Working with Scheduled Tasks ................................................................................717

Selecting Global Options.......................................................................................... 718

E Custom Card Formats............................................................................................719

Configuring CyberStation for Custom ABA Card Access.........................................720

Multiple Custom Card Formats ................................................................................728

F Points – Electrical Types....................................................................................... 731

Infinity Electrical Types and BACnet Objects...........................................................732

InfinityInput Types ....................................................................................................732

InfinityOutput Types .................................................................................................735



TAC xii



Andover Continuum CyberStation Configurator’s Guide 1

Introduction

The chapter is an introduction to the Andover Continuum CyberStation Configurator’sGuide. This chapter also presents Andover Continuum’s hardware and software, keyconcepts that are important for a configurator to understand, an overview of CyberStation, and instructions on how to start and stop CyberStation.

About this Guide

This guide is designed to help you configure your building automation control system with Andover Continuum CyberStation software. This guide is based on the assumption thatCyberStation has already been successfully installed on your system in accordance withthe instructions contained in the Andover Continuum CyberStation Installation Guide, 30-3001-720. Once the installation has occurred, the system is ready to configure asdescribed in this guide.

Document Scope

This guide is a reference document for configuring the CyberStation software on your building control system. Chapters follow the typical sequence that is involved inconfiguring CyberStation on your Infinity or BACnet system.

How this Guide Is Organized

This guide is organized as follows:

Chapter/Appendix Description

Chapter 1 Introduction ⎯ Presents an introduction to this guide, brief descriptions of Andover Continuum’s product line, and overview of CyberStation, key concepts, and instructions for starting andstopping CyberStation.

Chapter 2 Menu Pages ⎯ Describes all the features available fromCyberStation’s main menu, how to create new menu pages andhot spots, and how to use the Button Wizard.

1



TAC 2


Chapter 3 Continuum Explorer ⎯ Explains how the Explorer is laid out, itsfour views, describes objects and how they are represented on theExplorer and how viewer access to it is determined by securityrules.

Chapter 4 Security

Chapter 5 Configuring Users

Chapter 6 Configuring a Network Chapter 7 Configuring Controllers

Chapter 8 Configuring Comm Ports

Chapter 9 Creating I/O Module Objects

Chapter 10 Configuring Alarms

Chapter 11 Configuring Reports

Chapter 12 Templates

Chapter 13 Points, Logs, and Triggers

Chapter 14 BACnet

Chapter 15 Configuring Schedules and Calendars

Chapter 16 Configuring Loops

Chapter 17 Configuring TrendLogs

Chapter 18 Configuring Areas and Doors

Chapter 19 Configuring Personnel

Chapter 20 Managing Personnel Distribution

Chapter 21 Managing Configuration Files

Chapter 22 Creating Groups

Chapter 23 Creating ListViewsChapter 24 Creating EventViews

Chapter 25 Configuring and Viewing Video

Chapter 26 Graphics Panels

Appendix A Using the Personnel Editor

Appendix B EpiBuilder Installation

Appendix C Personnel Import Utility Tables and Sample XSLT File

Appendix D Scheduling Automatic Personnel Object Updates





Appendix E Custom Card Formats

Appendix F Points – Electrical Types

Related Documentation

The following documents are related to this configurator’s guide:

Title Part Number

Andover Continuum CyberStation Installation Guide for Version 1.8

30-3001-720

Remote Communication Configuration Guide 30-3001-814

Command Terminal Configuration Guide 30-3001-843

RoamIO2 (BACnet service tool) User’s Guide 30-3001-910

RoamIO2 (Infinet service tool) User’s Guide 30-3001-989

SNMP Configuration Guide 30-3001-855

Introducing BACnet – A Guide for CyberStation Users 30-3001-863

Plain English Language Reference 30-3001-872

bCX1 Series Controller Technical Reference 30-3001-890

CyberStation includes an extensive online help system. This help system is described inmore detail in Chapter 2.

Intended Readers of this Guide

This guide is written for anyone at your site who is responsible for configuring theCyberStation software that controls the operation of your building control system. Thisperson is the configurator . Network administrators and operators may also need thisguide.

Key ConceptsThe design of the CyberStation system is based on several key concepts that areinvolved in the makeup of the software and hardware components of a building controlsystem. These key concepts are outlined below. More thorough descriptions may befound in subsequent chapters.

Site

Your building complex, or whatever you are controlling with the Andover Continuumsystem, is referred to as a site. In complex operations, you may have control of multiplesites.



TAC 4

Points

The control of equipment requires monitoring individual inputs and actuating individualoutputs. In Infinity and CyberStation systems, these discrete entities are referred to as point s. You’ll see references to “output point” or “input point” often.

Internal places within a controller or workstation’s memory are also referred to as points.These software-based points may be temporary storage locations for setpoints or thememory location where the current date and time are stored.

Events

During operation, things happen as a result of actions taken by users, by the controllers,or as the result of no action. These occurrences can include the triggering of an over-temperature warning or the discovery of a forced door entry. In Andover Continuumsystems, they are classified as events.

There are several types of events. Each type can be monitored and acted upon throughautomatic and programmed control. All events are stored by the system.

Alarms

Alarms are events that signal the controller of an unusual occurrence. Typical alarmsmight include temperature variations and intrusion attempts.

Schedules

Schedules allow the operation of the system to be regulated according to a particular day, week, month, year, or time of day.

User

The user or operator is the person or persons who manually acknowledge alarms,monitor system activity, and interact with the system on a daily basis. Users are alsoindividuals who have access to the CyberStation software.

Configurator

The configurator is the person who sets up (configures) the CyberStation software tomatch the physical devices of the site.

Programmer

The programmer is the person who determines the operational flow of the system. Theprogrammer writes programs in a BASIC-like language called Plain English.

Network

The network is a medium through which electronic hardware communicates. Andover Continuum products use several types of networks:

• Network controllers communicate with a user workstation and with each other via anEthernet TCP/IP network. Our products support physical wire and fiber versions of the Ethernet as well as wide-area wireless Ethernet.

• Andover Continuum controllers communicate with external input and output modulesthrough a variety of commercial and proprietary network products.




Controller

Controllers are small, dedicated computers that perform the logic necessary to readexternal inputs and operate external outputs. User-created programs that are loaded intothe controller define the controller’s personality.

There are two types of controllers:

• Network controllers communicate through an Ethernet network.

• Infinet controllers communicate through either the Andover Continuum proprietaryInfinet network or the Master-Slave/Token Passing (MS/TP) network for BACnetdevices.

Workstation

The user interacts with the Andover Continuum system through a personal computer called the workstation, which runs the CyberStation software. CyberStation is used toconfigure, program, monitor and operate the system. All workstations on the Andover Continuum system are BACnet-compliant BACnet Operator Workstations (B-OWS).

Enterprise

The entire Andover Continuum system configuration of workstations, servers andnetworks with attached controllers and I/Os is called an enterprise. An enterprise canconsist of an unlimited number of networks containing a total of up to 4 million controllers

and workstations.

Andover Continuum Product Description

Andover Continuum is a mixture of hardware and software that is designed to monitor and control the various functions of a building. These functions include, but are notlimited to, security, access control, lighting, heating, ventilation, and cooling.

The hardware consists of equipment controllers, network communication controllers,input and output interfaces. The CyberStation software is a computer program that allowsyou to communicate with, monitor and control the operation of the entire Andover Continuum system.

CyberStation Software

A key component of the Andover Continuum system is a Windows-based applicationprogram called CyberStation that runs on a PC workstation and interacts with the controlsystem. Andover Continuum’s second key software component is the database thatstores all the vital information pertaining to the building automation control system.

CyberStation

CyberStation provides a graphic user interface that can display and manipulate data thatallows the entire site management of adjusting schedules and setpoints, acknowledgingalarms, controlling doors, tracking personnel, and so on.

Andover Continuum allows you to connect several CyberStation workstationssimultaneously to provide for the most flexible configuration/control and monitoringoperation available.



TAC 6

Database

The information that describes the structure and operation of your building is stored in theCyberStation database. The values of each point in the system, the settings for limits, theconfiguration of the hardware, the personal data of the personnel granted access to your building, and more, are contained in the database.

The database engine that CyberStation uses is either Microsoft SQL server or MSDE2000.

Objects

The components associated with your site (networks, workstations, actuators, sensors,and so on) are created, monitored, and controlled as objects in CyberStation. For example, for every controller you have in a building, CyberStation stores a controller object. When you have created an object for a piece of hardware, you can monitor,disable, change the settings for, and enable that equipment using that object inCyberStation. Objects represent every aspect of Andover Continuum’s building controlsystem, whether it is building security, lighting, or HVAC control. Refer to Chapter 3 for more information about objects and how they are represented in CyberStation.

Attributes

An attribute is a characteristic of an object. All objects have attributes associated withthem. In most cases, there are several attributes that describe an object. (Attributes areknown as properties in BACnet objects.)

Andover Continuum Hardware Products

The Andover Continuum product line encompasses a wide variety of TAC componentsincluding Infinity CX 9XXX series controllers, NetControllers and NetController II networkcontrollers, 9702 Site controllers, bCX1 series controllers, Infinet and Infinet II controllers,BACnet controllers, local and expansion input/output IOU modules, display modules andsmart sensors. These components are networked to create a total building automationsystem.

Andover Continuum System Architecture

Depending upon the complexity of the site architecture, a system can range from asingle-user configuration with one workstation to a large, multi-user configuration with anetwork of multiple workstations, a file server, and numerous controllers.




Single-User Configuration

In single user configurations (shown below) the Andover Continuum product line consistsof a network controller (NetController or NetController II with optional input/outputmodules), a bCX1 or a 9702 Site Controller and a CyberStation workstation. The MSDEdatabase also resides on the workstation. The NetController/bCX1/9702 use EthernetTCP/IP protocol to communicate with the workstation. Field bus communication betweenthe network controller and the I/O modules is conducted over a special ACC I/O bus.There are two versions of the bCX1. One uses Infinet protocol and the other communicates over standard MS/TP BACnet.



TAC 8

Multi-User Configuration

The Andover Continuum system design is based on scalability, so expansion to a multi-user, larger network configuration is easily accomplished. The following figure belowshows such a configuration. In this configuration, the Ethernet LAN is expanded toinclude another workstation and an SQL database server.

Network Controllers

There are several types of Andover Continuum network controllers:

• Infinity CX 9000 series

• NetController II 96xx series

• NetController CX 94xx series

• 9702 Site Controller

• BACnet b4920 Gateway/Controller

• bCX1 series

All are Ethernet TCP/IP compatible. The first four contain at least one Infinet port to allowcommunication with Infinet application controllers. The b4920 includes one MS/TPnetwork for communicating with b3xxx BACnet controllers.




The Infinity CX9XXX series are connected to individual IOU modules via an RS-485cabling arrangement referred to as "LBUS".

The NetController, NetController II, and 9702 Site Controller are powerful CPUs withflash EPROM providing the central network management functions for Andover Continuum building automation system. These network controllers can be connected toindividual IOU modules via a different RE-485 protocol called ACC-LON.

The 9702 Site Controller includes the equivalent of a NetController, a power supply, andan AC-1 access controller in one small package.

The bCX1 is a series of Infinet and Native BACnet routers and controller/ routers. TheInfinet devices (96xx) function as Ethernet-to-Infinet field bus routers. The BACnetdevices (40x0) function as BACnet/IP-to-MS/TP field bus routers

Infinet Controllers

These controllers include combinations of inputs and outputs for the monitoring andcontrol of local sensors and devices. There is a wide variety of Infinet controllers; eachdevice is designed for a specific purpose.

Infinet controllers are connected to network controllers via the Infinet network.

BACnet Controllers

These controllers include combinations of inputs and outputs for the monitoring andcontrol of local sensors and devices. They are equivalent in function to the Infinet i2

series controllers mentioned above.

BACnet controllers are connected to a bCX1 or b4920 controller/gateway via the Master-Slave/Token Passing (MS/TP) network.

Workstations

A personal computer (PC) connected to the Continuum Ethernet network runs theCyberStation software and database. The system can contain a single workstation or multiple workstations, depending on the site configuration.

Networks

The Infinet is Andover Continuum’s high-performance, token-passing LAN that allows Infinet application controllers to communicate with each other and to a single network controller. With

repeaters, it is possible to have 127 Infinet controllers on one Infinet networkThe LBUS is the cable that connects IOU modules to a CX network controller or via theLA-1 (see Table 1-1) to a NetController or NetController II. Only one LBUS can beconnected to a CX network controller. Each LBUS can handle up to 16 IOUs.

The BACnet MS/TP network is an RS-485 based industry standard LAN that allowsBACnet b3 controllers to communicate with each other and to a single b4920 or bCX1. Itis possible to have 127 Infinet controllers on one MS/TP network.

NetController I/O Modules

NetController I/O modules are specialized units that receive sensor inputs and activateequipment (valves, fans, door locks, and so on) and perform access control functions.



TAC 10

The I/O modules, available in several configurations including input, output, mixed I/O,and display are listed in the following table.

Type Module Function

UI-8-10 and UI-10-10V

Universal Input Module

DI-6 AC and DI-6 AC HV

AC Digital Input Module

DI-8 Digital Input Module

DM-20 Digital Input/Output Module (for DIO-20)

Input

MI-6 MilliAmp Input Module

AO-4-8 Analog Output Module

AO-4-8-O Analog Output Module with override

DO-4-R Relay Output Module

DO-4-R-O Relay Output Module with override

DO-6-TR Triac Output Module

LO-2 Lighting Output Module

Output

LO-2-O Lighting Output Module with override

AC-1 Door, Access Control

AC-1A Door, Access Control

AC-1 Plus Door, Access Control

AccessControl

VS-8-4 Video Switch Module

LB-8 8-Channel LED Bar Display/w 8 Push buttons

LS-8 8-Channel, 3-Digit 7-Segment LED Display/w 16Buttons

LC-1 2-Line LCD Display/w 12 Push Buttons

Display

VM-1 Voice Record and Playback Module (requiresLC-1 Module)

VT-1 Voice module for use with touch-tone telephonesMiscellaneous

LA-1 Allows use of LBUS IOUs with a NetController or NetController II




Controller Expansion Modules

Expansion modules extend the I/O capability of certain i2, BACnet, and bCX1 controllers.

Type Expansion Module Function

xPUI4 4-Channel Universal Input Module

xPBD4 * 4-Channel Universal Input and 4-Channel DigitalOutput Module

Universal

xPBA4 * 4-Channel Universal Input and 4-Channel Analog Output Module

Input xPDI8 8-Channel Digital Input Module

xPAO2 2-Channel Analog Output Module

xPAO4 4-Channel Analog Output Module

xPDO2 2-Channel Relay Output Module

Output

xPD04 4-Channel Relay Output Module

xP Display Internal Mounted Keypad/Display Module (920only)

Display

xP Remote Display Externally Mounted Keypad/Display Module

*These modules expand the I/O of bCX1 series controllers only.



TAC 12

CyberStation

You use CyberStation software to configure, monitor and control the Andover Continuumand Infinity hardware. CyberStation has a collection of tools and applications that worktogether to help you create and interface with all the objects in the system. The figurebelow illustrates some of them.




Creation Tools

Editors

Every type of object has its own editor. An editor is a software tool that allows you tocreate an object of a specific type. Each object type is known as an object class. You canalso use editors to change object settings, such as the value of an output object.

Templates

Templates are objects that are used to create other objects. Templates look like editorsthat have been pre-configured with most or all of the information required to rapidlycreate multiple instances of the same object class. To create a new object, copy thetemplate, and change or add information as needed.

Configuration Wizard

The Configuration Wizard allows you to create and edit CyberStation templates. Itpresents a tab for each template subfolder contained in the template folder. Clicking on atab displays a listing of all the templates available in the subfolder.

CyberStation Online Help

Online help topics cover all CyberStation object class editors (including BACnet objectclass editors) and all major CyberStation features. Reference information on the PlainEnglish IDE programming environment, including a Plain English keyword reference, isalso provided. Help buttons, located in the CyberStation user interface — editors, dialogs,

live views, and so on — open help topics related to the CyberStation editor or feature inwhich you are working. You can also press the F1 key to bring up related help.

For more information about online help, please see: Accessing the Online Help System,Chapter 2.

Programming Tools

Plain English

Plain English is the programming language you or your programmer will use to writefunctions and programs that can automatically initiate and respond to activity in your building control system. You can also use the Plain English program to automate routinetasks, such as generating reports. The language is easy to use because its keywords arecommon, easy to understand words. The Plain English Editor also makes programming

easy by reducing most of the typing to mouse clicks.

Command Line

The command line is a simple text field interface that allows you to directly enter, via thekeyboard, Plain English commands. The command is executed immediately after entry.This tool is handy for trying commands before committing them to your program. You canalso review and use a running history of the commands you entered.

Message Window

The Message Window allows you to view the results of your Plain English programs asCyberStation processes them.



TAC 14

Monitoring Tools

Continuum Explorer

The Continuum Explorer is your main access window into CyberStation. It is similar to thestandard Windows explorer, and displays all the objects on your system in a hierarchicalview. This allows you to see the relationship between objects. The Continuum Explorer also provides access to all the object editors.

Menu Pages

Menu pages are the graphic screens you will see after logging into CyberStation. Menupages help you navigate to, as well as monitor, certain objects. These screens contain"hot spots" that you can click to move to another screen or to open an application. Menupages also display a status bar that shows the most recent alarm. The status bar includes an icon that provides access to the Active Alarm View.

Graphic Panels

Using a sophisticated Graphic Panel editor, you can create colorful screen-basedgraphics that simulate control panels, floor plans, and automated warnings or alerts.These panels can then become primary interfaces for your end users.

Active Event Views, Groups, and ListViews

These are all objects that you create for the purpose of monitoring other objects.

Starting CyberStation

Use the following procedure to start CyberStation:

1. Click the Start button in your task bar.

2. Select Programs.

3. Select Continuum in the list of programs, and then click Continuum in theprogram list.

The CyberStation splash screen and the main menu appear along with the followingdialog:

4. Enter your User Name and password.

5. Click OK.




Your administrator usually assigns authorizations to access the CyberStationsoftware. For unassigned users there is a default user name and password.

Note: Once you start CyberStation, you can create a Windows shortcut to openCyberStation from your desktop by clicking on the Continuum icon:

Closing CyberStationUse the following procedure to shut down CyberStation:

1. Right-click the Continuum icon in the taskbar at the lower right-hand corner of your screen.

2. Select Exit from the popup menu:

3. When prompted to confirm that you want to close the application, click Yes.

4. If prompted to add a comment, enter a comment in the Comment field, and thenenter your user name and password.



TAC 16

5. Click the OK button, and wait for all CyberStation processes to terminate.

If you do not wait for all processes to finish you risk losing system information.




Menu Pages

This chapter describes the features of the CyberStation user interface and explains howto use screen elements, such as “hot spots” and popup menus, to access information inCyberStation. This chapter also describes how to customize CyberStation menu pages tomeet your requirements.

The CyberStation Main MenuThe CyberStation Main Menu, shown on the next page, contains the following features:

• Title Bar - Shows the title for the current menu page.

• Menu Area - Covers the entire region in between the title bar and status line.

• Main Menu Links or “Hot Spots” – Displays menu selections for major features(Graphics, Schedules, Groups, and so on) along the left side of the window.

• Status Line - Displays information including user name, workstation name, currentdate and time, error messages, and prompts.

• Alarm Bar - Displays text that describes an active alarm condition.

2



TAC 18

All CyberStation menu pages share the same basic features as the Main Menu describedabove.

Selecting Items on the Main Menu

There are two ways to select items from the CyberStation Main Menu:

• Hot spots

• Popup menus

Hot Spot Links

Hot spots are selectable areas of a menu page. Clicking on the hot spot:

• Moves you to another menu page.

• Launches a CyberStation application, such as Schedules or Listviews.

• Runs a program.

• Creates new objects.

Hot spots may look like buttons clearly marked by text or icons, or they may simply beobjects, such as doors, boilers, or controllers, that are part of the overall graphic. You willalways know that a hot spot exists if the cursor arrow changes to the hand symbol.

Shortcut Popup Menu

You can also select certain items from the Main Menu using a popup menu:

Title Bar

Alarm Bar Status Line

Menu Area

Continuum Tooltray and Icons

“Hotspot”Menu Links




1. Move the cursor to any part of the menu area that is not a hotspot.

2. Right click to display the popup menu.

3. Select Change Page and then the item you want to open from the dropdown list. For example:

Tool Tray Items

CyberStation-related icons appear in the lower right-hand corner of the Windows taskbar, known as the tool tray:

Placing the cursor over each of these icons displays a message indicating the status of the item represented by the icon. Right click the icon to bring up a popup menu for eachitem.

The SQL Server Icon

The SQL server icon appears only on a machine that is also functioning as the MSDEServer.

Right click the icon to display a menu that allows you to start and stop the SQL server from CyberStation and determine whether it starts automatically with the OS

Note: The SQL Server Service Manager menu is usually restricted, and used only by thesystem administrator. Do not stop the SQL server without first consulting your administrator.

Distribution Server Icon

When you make changes to CyberStation objects, CyberStation immediately sends thenew configuration information to the controllers. This process is referred to as distributionand is performed by the CyberStation distribution server. The CyberStation distributionserver handles moves, copies, deletes, creating objects from templates and any other actions occurring between a workstation and a controller.

The distribution server icon in the tool tray provides feedback about the currentstatus of the distribution server.



TAC 20

When the distribution server is active, the icon animates to indicate the activity.

Connecting lines appear between the document and the controller, and a red dotanimates along the connecting lines.

For more detailed information, double click the icon (or right click) and select Propertiesfrom the icon’s popup menu to display a Distribution Properties dialog. This dialogprovides detailed information about the status of the server and the currently runningoperation.

Note: The Distribution View button in the Distribution Properties dialog launches a

powerful tool, the Access Distribution View, which allows you to monitor distribution-event transactions and perform an immediate distribution of apersonnel record. (See Chapter 20, Managing Personnel Distribution.)

Workstation Status Icon

The Workstation Status Icon indicates whether the CyberStation workstation is onlineor offline:

• When the workstation is online, CyberStation is communicating with controllers andother devices in the network. The workstation is typically online when CyberStation isrunning.

• When the workstation is offline, CyberStation does not send or receive messagesform the network. Changes that you make to CyberStation objects while the

workstation is offline are not sent to the controllers until you change the workstationstatus to online.

Double click or right click the icon to change the workstation status.

Continuum Icon

Right click the Continuum icon to display a popup menu with several options:

• Advanced CyberStation functions

• Access to online help and software version numbers

• Logoff and Logon options

• Exit option to close CyberStation

Alarm Icon

You can double click the Alarm icon to bring up the Active Alarm View:




You can also access the Active Alarm View from the popup menu for this icon.

Alarm Bar Selectable Items

When an alarm condition occurs, and the Active Alarm View is in the status line mode,text describing the alarm appears in the white status box in the alarm bar. To respond tothe alarm, you click the appropriate icon in the bar for the action you wish to perform:

• Acknowledge

• View a graphic panel

• View report

• Silence (mute) an audio alarm

• Execute a user-defined Plain English function for the alarm.

• Bring up the surveillance video monitor (the VideoLayout editor) when a pointgoes into an alarm. This is the VideoLayout object attached to the point for this alarm.(See Chapter 25, Configuring and Viewing Video.)

• Display the AlarmEnrollment or EventEnrollment editor associated with theselected alarm.

See the section, Active Alarm View , in Chapter 10 for complete details on the Active Alarm View modes: view mode and status line mode.



TAC 22

Accessing the Online Help System

Within CyberStation, an extensive online help system is readily accessible. From theCyberStation Main Menu, you may access the Help system in two ways:

• Press the F1 key as instructed in the status line.

• Right-click the Continuum icon in the tool tray, and select How Do I from thepopup menu.

Either method opens the online help and displays the home screen:

The CyberStation editors, live views, and other major dialogs have a Help button. Clickthe Help button (or press the F1 key) to display help topics related to the feature in whichyou are working.

To learn how to use all the features of the online help system, click the Contents tab inthe Help navigation pane, and then click the topic, How to Use this Online Help, asshown below:




When you access the online help system for the first time, please read the topic entitled,How to Use this Online Help. The help system has a navigation pane and a viewingpane. The navigation pane has a Contents tab, as well as an Index tab with a textsearch engine.

Though the CyberStation online help system contains some task-oriented “how to”information, the help topics, by design, are closely aligned with the user-interfaceattributes of CyberStation editors, dialogs, and other features that display Help buttons.

Menu Page Selections

The CyberStation main menu is a list of hotspots that you can select to display another menu page. Each page provides specific capabilities for annotating and controlling your building automation system.

Graphics

Click the hot spot to display a listview of all graphics files on thesystem. These graphics files contain Pinpoint panels, which are described in detail inChapter 26.



TAC 24

Each entry lists the name of the graphic object, its alias, and the ownership of the object,

as indicated by file path. Double click an entry to open the selected object in the Graphicseditor.

Schedules

Click the hot spot to display a listview of all schedules system. Clickan entry to open the selected schedule in the Schedule editor. Refer to Chapter 15 for adetailed discussion of Schedules.

Groups

Click the hot spot to display a listview of all groups on the system. Clickan entry to open the selected group in the Group editor. Refer to Chapter 22 for adetailed discussion of Groups.

Listviews

Click the hot spot to display the Listviews menu page:




Within this menu page many hot spots are arranged in five categories. Clicking on a hot

button produces a listview of the selected object.

Under Alarms you can request a list of all alarms on the system, as well as the alarmactivity for various time intervals. You can also create a list of all unacknowledged alarmsand view alarm acknowledgements.

The User Activity hot buttons each produce a listview of user activity on the system for aparticular time frame.

The User Logons hot buttons provide selections for the day, week, or month that createa listview of all user logons to CyberStation. Each entry indicates the time of logon, wherethe logon occurred (NodeName) and the name used (UserName) to logon with.



TAC 26

The Access Events hot buttons display listviews of access event activity on the systemfor a particular time frame. Valid and Invalid Access can also be reported by day, week,or month. The Invalid Access Listview provides a time stamp, event type, door, a personID, card number, and message for each invalid event occurring on the system. See alsoChapter 23, Creating Listviews and Chapter 11, Configuring Reports.




Personnel

Click the hot spot to display the Personnel menu page.

An example of the listview associated with the All Personnel hot spot is shown below.

The hot spots under the Prompted Lists heading let you search for a Personnel objectby entering a card number, a department number, a last name, a driver's license, or aSocial Security number.

Explorer

Click the hot spot to open Continuum Explorer.



TAC 28

Continuum Explorer is where you work with all the objects on your CyberStation system.From Continuum Explorer, you can open object editors, create new objects, openListviews and schedules, launch graphics panels and view the properties of objects. SeeChapter 3 for detailed information about working in Continuum Explorer.

System & Status

Click the hot spot to display the System & Status menu page.




Command Line

Click the hot spot to display the Command Line. The Command Line iswhere you enter Plain English statements for carrying out CyberStation system tasks. For example, you can run a report, print the values of system variables, or change inputsetpoints by typing the appropriate keywords for these actions at the Command Line.

The Command Line consists of a title bar, a button to expand the Command Line, abutton to open the explorer, an area in which to type commands, and a message windowin which messages and printed values display.

This is where you type Plain English Statements.

This title bar displays the current path to the controller youare working on

This button opens the Continuum Explorer navigation tree. This is where print requestsand messages display.

This button expands the Command

Line to a scrollable window

The title bar contains the path to the controller or device the Command Line is connectedto. To hide or display the title bar, right click it, and select Title Bar from the popup menu.

To view messages that are too long for the Command Line window, you can either resizethe command line, or place your cursor anywhere in the message text to display a pop upview of the entire message.

Plain English Editor

Click the hot spot to open the Plain English editor. You use thePlain English editor to write, edit, and debug your Plain English programs. Refer to the

online help for more information about Plain English and the Plain English editor. You canalso refer to the Plain English Language Reference Guide, 30-3001-872

Message Window

Click the hot spot to display brings up the Continuum MessageWindow.



TAC 30

The Continuum Message Window displays system messages and the results of printrequests generated from within programs.

Graphics Editor

Click the hot spot to display the Pinpoint graphics editor. Pinpoint, theCyberStation graphics application program, allows you to produce dynamic virtual controlpanels on your workstation. Refer to Chapter 26 for complete details on the use of Pinpoint.

Configuration Editor

Click the hot spot to display the Configuration Wizard.

The Configuration Wizard is a tool for using CyberStation templates. Templates arepredefined objects that you can drag and drop into container objects to create newobjects with the same attributes. The Configuration Wizard displays the templates thatare stored in the template folder. Each subfolder in the template folder creates a tab inthe Wizard. The Miscellaneous tab is created by the template folder itself. Refer toChapter 12 for a full discussion on templates.




Communication Status, Point Status and System Messages

The hot spots appearing along the bottom half of the System and Status page displaylistviews that report the status of system components and objects as well as all error messages.

Communication Status

The hot spots listed under Communication Status open listviews that indicate thecommunication status (on-line or off-line) of the system controllers and IOU modules. Anexample of the listview of IOU Modules is shown below.

Point Status

Under the Point Status heading, listviews are available for points. An example of thelistview for Doors is shown below.

System Messages

Under System Messages, hot spots link to error message listviews for the day, weekand month.



TAC 32

Windows Applications

The Windows Applications hot spot provides direct access toWindows applications.

Click a hot spot to open the corresponding Windows program.

Configuring New Menu Pages

As you configure your CyberStation system, you may want to create new menu pagesand add hot spots to them. For example, you may want to create a menu page of all thebuilding control objects that you need to access and create hot spots for each of them.

Creating a New Menu Page

1. In the CyberStation Main Menu page, place your cursor anywhere that is not a hotspot.

2. Right click to display the popup menu, and click Edit.

On the Main Menu page, dashed lines appear around the existing hot spots, like the

one shown below:

The Edit toolbar of options also appears.




3. Click the icon in the Edit toolbar. The current menu page changes to a blankpage and the Page Edit dialog appears:

Page Information

Enter a Name and a Description for the page. Users see the name you entered whenthey click Change Page in the shortcut menu and is the name that Change Page hotspots refer to. Name can be up to 132 characters (including spaces).

Select the Main Page checkbox if you want the page you are creating to be the first pagethe user sees.

Create aNew Page

Save RunHelp



TAC 34

Background File

The typical graphic file for a menu page has some sort of background or theme thatrepresents the purpose of the menu page and objects or text that can serve as hot spots. A Main Page graphic might also include the corporate image of your company.

Insert the name of a graphic file for the menu page into the Background File field:

Use the button to browse for a .bmp file. The default path for menu page files iswherever CyberStation was installed, in the UserProfile folder.

Select the file you want to use, and click the Open button.Audio

To add audio to the new menu page, proceed as follows:

1. In the File to Play field, click the button to browse for an audio file that playswhenever users move to this page.

2. Locate and select the audio (.wav) file that you want to use, and then click the Open button.

3. Select the Enable checkbox to enable the audio file.

4. Select the Use MS MPlayer checkbox to use Microsoft’s Media Player. If your workstations use another type of media player, clear this checkbox.

If you check the Use MS MPlayer box, a second checkbox appears, Show MPlayer .Check this box if you want the Microsoft Media Player to display on the screen:

Video

To add video to the new menu page, proceed as follows:

1. In the File to Play field, click the button to browse for a video file that playswhenever users move to this page.

2. Locate and select the video (.avi) file name, and click the Open button.

3. Check the Enable checkbox to enable the video file.

4. Check the Full Screen checkbox if you want the video to be the size of the monitor

screen. To have the video display in a window, clear this checkbox.Save and Run

1. Click OK to close the Page Edit dialog.

2. Save your changes by clicking the icon in the Edit toolbar.

3. Click the icon in the Edit toolbar, or display the shortcut menu and click Run.

You are now ready to add hot spots to the page you created.




Creating a Hot Spot to Run a Windows Program

To create a hot spot on the new menu page, perform the following steps.

1. Place your cursor anywhere that is not a hot spot, right click, and select Edit from thepopup menu.

2. Use your cursor to draw a rectangle around the area of the graphic or text that youwant to be the hot spot. Define a big enough hot spot so users can easily click it.

3. Place the cursor anywhere inside the dashed lines surrounding the hot spot just

created.4. Right click, and then select Properties to display the Edit HotSpot dialog:

5. Select the Execute radio button.

6. Click the browse button in the Open field.

7. Locate and select an executable program file.

For example, to open Excel you need to locate and select the executable file for Microsoft Excel on your workstation.

8. Click the Open button.

9. Check the Make hotspot look like a window button checkbox.

10. Enter a title for the button (for example “Excel”) in the Button field.

Creating a Change Page Hot Spot

You can create a hot spot that will send you to another menu page. For example, if youcreate a new menu page, you might like to have a hot spot on the main menu that takesyou to it.

1. Place your curser anywhere that is not a hot spot, right click, and select Edit from thepopup menu.



TAC 36

2. Use your curser to draw a rectangle around the area of the graphic or text that youwant to be the hot spot. Define a big enough hot spot so users can easily click it.

3. Place the curser anywhere inside the dashed lines surrounding the hot spot justcreated.

4. Right click, and then select Properties to display the Edit HotSpot dialog:

5. Select the Change Page radio button.

6. From the dropdown menu for the Open field, select the name of the new menu page.

7. Check the Make hotspot look like a window button checkbox.

8. Enter a title for the button in the Button field.

9. Click OK.

10. Click the Save icon in the Edit toolbar.

11. Click the Run icon in the Edit toolbar

The button should now appear on the menu page. Selecting it takes you to newmenu page.

Button Wizard

The Button Wizard is another method for creating buttons on menu pages. You can

create buttons to:

• Edit an existing object

• Create a new object

• Open an existing object

• Create a new object from an existing template object

The following procedure described how to use the Button Wizard to create a button thatopens a CyberStation object in the appropriate object editor.

1. Create a hot spot as previously described under Creating a Hotspot as a WindowsButton.

2. Right click inside the Hot Spot rectangle and select Button Wizard from the popupmenu.

You are presented with the following menu.




3. Select Open an existing object, and click Next.

4. Select I would like to select an object to open, and click Next.



TAC 38

5. From the dropdown menu, select the class of object to attach to the new button, andclick Next.

6. Using the browse button, select a location for the object, select whether users canbrowse to other locations to locate the objects, and click Next.

7. Enter a HotSpot name and description.

8. To display the hotspot as a button, check the checkbox and enter the text you wantdisplayed on the button.

9. Click the Finish button.

The button should now appear on the menu page and selecting it will open theselected object (in the above example, a listview).




Continuum

Explorer

Continuum Explorer is a tool that allows you to work with all the objects in your Andover Continuum system. It displays the controllers, inputs, outputs, and workstations and is themain environment in which you configure your system. From Explorer, you can openobject editors, create new objects, open listviews and schedules, launch graphics panels,and view the properties of objects.

Objects in Continuum Explorer Andover Continuum control system software is based on object-oriented programmingprinciples. Objects and classes are the basic building blocks of the Continuum system. Allthe items that make up the system, both the hardware and the software, are identified asobjects. Each item appearing in a Continuum Explorer screen represents an object.

Objects are organized in classes. For example, devices, points, personnel records,areas, graphics, doors, schedules, and programs are all examples of object classes.Some object classes, known as containers, can “own” other objects.

Container Objects and Object Ownership

Container objects and object ownership are terms that describe the relationshipsbetween objects in the Andover Continuum system.

Container Objects

Objects in CyberStation are arranged in a hierarchy. The Root object is always the primeobject at the top of the hierarchy. Objects at the top of the hierarchy contain, or own theobjects beneath them. Networks, Devices, InfinityControllers, InfinityInfinetControllers,BACnet Controllers and Folders are examples of Continuum container objects. Objectsthat are not container objects cannot own any other objects.

Object Ownership

Object ownership refers to the physical network connection between devices and towhere the objects are stored within the network.

3



TAC 40

For example, if an input point called Rm Temp 1 was attached to a CX 9XXX controller named CX1 which is connected to the Ethernet network called Building 1, you have thefollowing object hierarchy: the network object (Bldg1) owns the attached device object (controller CX1) which owns the input point object (Rm Temp1). These relationships areshown below.

Class Icons

Each class has a default icon associated with it so that you can easily identify the objectclass. Icons can represent a hardware object (for example, a controller or a workstation)or a software object, such as a schedule. The following table shows all the default object-class icons.

Note: In the following table, an asterisk (*) denotes an object class that may include or belimited to BACnet objects. Refer to Chapter 14 for more information on BACnet andBACnet icons.

Icon Object Class

AlarmEnrollment

AnalogInput *

AnalogOutput *

AnalogValue *

Network

Bldg1

Root

Input Point

Rm Temp1

Controller

CX1




Icon Object Class

Area

BinaryInput *

BinaryOutput *

BinaryValue *

Calendar *

ControllerUser

CommPort

DateTime

Device (Andover Continuum b4/b3 controller) *

Device (third-party BACnet controller) *

Device (Andover Continuum workstation) *

Device (third-party workstation) *

Door

EventEnrollment *

EventView

EventNotification * (equivalent to BACnet NotificationClass object)

File *

Filter



TAC 42

Icon Object Class

Folder (Continuum/Infinity)

Folder (BACnet)

Folder (Continuum/Infinity default class)

Folder (BACnet default class)

Function

Graphics

Group

InfinityController InfinityInfinetCtlr

InfinityInfinetCtlr (Infinity 2 only)

InfinityDateTime

InfinityFunction

InfinityInput

InfinityOutput

InfinityNumeric

InfinityProgram

InfinityString




Icon Object Class

InfinitySystemVariable

IOUModule

Listview

Loop *

MultistateInput *

MultistateOutput *

MultistateValue *

Network (Continuum/Infinity)

Network (BACnet) *

NetworkDialup

Personnel

Program *

Report

Schedule *

SecurityLevel

String

TrendLog *



TAC 44

Icon Object Class

User

VideoLayout

VideoServer

Object Names and Object Aliases

Each object in CyberStation has two identifiers, a name and an alias. An object name canbe lengthy and descriptive. Although an object name and alias can be the same, anobject alias must conform to stricter naming conventions.

Object Names

Descriptive object names help other users identify what the object is. For example, if youare creating an output point for operating fans, you might want to enter a name like FanStart/Stop.

The name can be up to 128 characters long, and can include spaces, underscores,dashes, slashes, and periods.

An object name is stored in the CyberStation database, but not at the controller.

Object Aliases

The alias is the name of the object used in programs and functions. CyberStation createsthe alias version of an object name for you as you type the object name when creating anew object. The alias is saved to the controller. The alias is also saved in theCyberStation database.

Alias Naming Conventions

An object alias can be up to 16 characters, and can use only alphanumeric (letters andnumbers) characters, periods, and underscores. Aliases must start with a letter, and haveno spaces. They also cannot be reserved words, or keywords, which are words that havea designated use in CyberStation or in the Plain English programming language.




Starting Continuum Explorer

On left-hand side of the Main Menu (Chapter 2) click the hot spot.

The Explorer includes the following elements:

• Title bar - indicates the path of the selected object, or the name of the selecteddevice or folder.

• Dropdown Menus – contains menus for Explorer tasks.

• Quick Picks toolbar

• Popup menus

• Command scroll box - always shows the path of the last selected object or thename of the selected device or folder. Clicking the down arrow of the scroll bar presents a history of all previous selections of objects, devices and folders.

•

Explorer Window – divided into the two main viewing areas: navigation pane andviewing pane.

• Status bar - indicates Explorer’s activity, either in the idle state (Ready) or displayingan active state. In the right-hand corner, indicates the number of objects appearing inthe viewing pane, and the number selected.

Title Bar

DropdownMenus

Quick Picks

Status Bar

Navigation Pane Viewing Pane

Command Scroll Box

Explorer Window



TAC 46

Dropdown Menus

Object Menu

The following table describes the selections in the Object dropdown menu, shown below.The number of selections that appears in the dropdown menu varies according to theobject selected.

Object menu options are also available from popup menus when you right click an object.

Selection PurposeOpen Opens the editor dialog corresponding to the first object that

appears in the viewing pane by default. If you select another object,the dialog that corresponds to that object appears.

Edit Opens the editor dialog corresponding to the first object thatappears in the viewing pane by default. If you select another object,the dialog that corresponds to that object appears.

Explore Opens another session of Continuum Explorer.

View Depending on what item is selected – a controller, default objectclass folder, object, and so on – clicking View may do one of twothings:

• Open a listview.

• Display submenu selections: History, Graph, and Report. TheHistory and Graph submenus provide a LogView history. Inthese cases, you may chose a time range for the history log byspecifying the range in the Time Range for History dialog thatappears.

Selecting Report brings up the Report editor, from which youmay create, configure, and view a graphical or text report in theReportViewer. (See Chapter 11, Reports and the Report Editor .)

Import Into Causes the Open dialog to appear. You can select an ASCII dumpfile from which to import object settings

Find NewBACnetDevices

Searches the network for BACnet devices that have not beendeclared. The new devices then appear automatically on theExplorer.

Backup toInfinet2 Flash

Saves the Infinet 2 controller's RAM configuration to its flashmemory, in accordance with the attribute value that is set for the ACCRestartMode system variable. When you click this button, aConfirm Operation dialog appears.




Selection Purpose

BackupBACnetDevice

Backs up configuration information (stored in a special File objectcalled ACCConfiguration) for a single BACnet controller, or multiplecontrollers, and saves it to your CyberStation database, for BACnetdevices that support Backup/Restore (See Chapter 21, Managing Configuration Files.)

RestoreBACnetDevice

Restores configuration information from your database to one or more BACnet controllers, for BACnet devices that supportBackup/Restore. (See Chapter 21, Managing Configuration Files.)

DistributePersonnel

Sends all Personnel objects to a selected controller.

Send To When you click this menu item the following submenu itemsappear:

Text File: Opens the Save As dialog. Use the Save As dialog tosave Continuum Explorer data in the desired location.

Printer: This option is disabled in this version of ContinuumExplorer.

Controller : Appears whenever a controller icon is highlighted in theExplorer. Used in conjunction with the Send to Controller Options

selection in the Options menu to reload the controller. Database: Used in conjunction with the Send to DatabaseOptions selection in the Options menu to reload the database.

New Displays a submenu of object classes. Use this menu selection tocreate new objects.

Delete Deletes the selected object and all its container objects including allreferences and links to the database. It is a nonrecoverableoperation. A Confirm Operation dialog appears as a warning.Click OK or Cancel.

Rename Opens the Rename dialog so that you can rename the selectedobject.

Page Setup Sets up paper size and margins for the print commands.

Print Prints the viewing pane of Continuum Explorer on the defaultprinter. The printout dimensions depend on the default printer settings.

Properties Displays the Properties dialog for the currently selected object.

Exit Closes Continuum Explorer.



TAC 48

Edit Menu

Selection Purpose

Select All Selects all the objects currently displayed in the viewing pane.

Select None Clears the selection of all objects in the viewing pane.

Inverse Selection Reverses whatever the last selection was. For example, if youselected A, B, and C, but left D unselected, inverse selectioncauses D to be the only selection.

View Menu

Selection Purpose

Toolbar Displays or hides the Quick Picks toolbar.

Status Bar Displays or hides the Status Bar.

Explorer Bar Provides four different ways to view the Andover Continuumsystem. (See Explorer Views, later in this chapter.)

Class Folders Displays class folders in the viewing pane.

Show TACBACnet Device As

Provides three different ways to view an Andover ContinuumBACnet device. (See “Viewing Options” in Chapter 14.)

Objects Displays objects in the viewing pane.

Hide Out Of Services Devices

Allows you to hide out-of-service BACnet device objects on theExplorer tree. (Refer to “Hiding Out of Service Devices” inChapter 14.)

Icon Displays graphic images that represent a file, folder, subfolder,command, or object.

Small Icons Displays small icons in the viewing pane.

List Alphabetizes objects vertically rather than horizontally in theviewing pane.

Details Displays attributes in columns in the viewing pane – that is,name, alias, owner, and so on.

Up One Level Moves the cursor one level higher in the tree hierarchy in theleft pane.

Stop Halts user-initiated list building in the viewing pane.

Refresh Updates the content in the Explorer window to display newlyadded, deleted, or modified objects.

Refresh All Updates the content in the Explorer window to display all thelatest data.




Selection Purpose

ConfigurationWizard

Opens the Configuration Wizard dialog. You use theConfiguration Wizard to create objects from templates.

Options Menu

Selection Purpose

Copy Options Opens the General tab of the Copy Options dialog.

Import Into Options Opens the Import Into Options dialog.Send to Text FileOptions

Opens the Send To Text File Options dialog.

Send To Controller Options

Opens the Send To Controller Options dialog.

Send To DatabaseOptions

Opens the Send To Database Options dialog.

Copy Options Dialog

Continuum Explorer makes it easy to copy objects among containers. You can use copyand paste from the Edit menu, or you can drag objects from one container to another.

The Copy Options dialog helps you control how and when objects can be copied inContinuum Explorer.

Note: After copying an object, ensure that the name and alias have changed. If the nameor alias has not changed, manually change the name or alias, as required.

The Copy Options dialog has the tabs described in the following table.

Tab Name Description

General Allows you to select Source Container and Source Object options.For more information about container and child objects, seeContainer Objects and Object Ownership earlier in this chapter.

Name Conflicts Allows you to decided what CyberStation does when it detectsobjects that have the same name in the source and target containers.

Class Filter Allows you to select how to copy source objects. You can copy all,include only certain classes, or exclude certain classes selected froma scroll-down list.

Import Into Options Dialog

Continuum Explorer allows you to set various skip, merge, replace, and area link options,when you import CyberStation object data from ASCII dump files and importing from CSVfiles. The Import Into Options dialog is displayed when you select the Import Into option from a menu in Continuum Explorer.

The following table describes selections on the Import Into Options dialog.



TAC 50

Skip, Merge, and Replace Options

Skip source objects with nameconflicts.

Click this radio button to stop the importoperation for an object when the name of thesource file object and the name of the targetobject are the same.

Merge target objects with nameconflicts if the source object is of thesame class, otherwise skip thesource object.

Click this radio button to merge the sourcefile object with the target object, if the sourceand target objects are of the same objectclass.

If the source and target objects are of different classes, stop the import operationfor the object.

Merge target objects with nameconflicts if the source object is of thesame class, otherwise replace thesource object.

Click this radio button to merge the sourcefile object with the target object, if the sourceand target objects are of the same objectclass.

If the source and target objects are of different classes, overwrite the source objectwith the target object.

Replace target objects with name

conflicts.

Click this radio button to replace the target

object with the source file object, when thenames of the source object and target objectare the same.

Area Link Options

Overwrite existing area links Click this radio button to overwrite the arealinks (Assigned areas) in the personnel targetobject with the area links in the personnelsource file object.

Append imported area links toexisting area links.

Click this radio button to add the personnelsource file object's area links to the area linksof the personnel target object.

Replace the area links from thepersonnel’s parent template, butleave all other area links unchanged.

Click this radio button to replace the arealinks in the parent template of a personnelobjec with the source file area links, andappend (or "import") these template links tothe target object, leaving all the other target-object links unchanged. The target objectthen has its own links plus the links from theupdated template.

All personnel objects that were created fromthis parent template are also refreshed torepresent the changed parent template.




Checkbox

Distribute personnel during anASCII import.

Check this checkbox to ensure the informationthat is newly imported into the CyberStationdatabase is distributed to all the controllers thatare affected by the modified Personnel objects.

Send to Text File Options

Continuum Explorer allows you to set various source-object options and text-file optionswhen you when you export CyberStation object data to ASCII dump files. The Send toText File Options dialog is displayed when you select the Export to option from aContinuum Explorer menu.

The following table describes selections on the Send to Text File Options dialog.

Source Object Options

Do not dump child objects. Click this radio button to export the data for theselected object, but not the child objects -- that is,not the objects contained within the controllersbelonging to the parent object in the devicehierarchy.

Dump child objects, but do notdump the children's children.

Click this radio button to export the data for theselected object, as well as all child objects – that

is, all objects contained within the controllersbelonging to the parent object in the devicehierarchy, but do not export the child objectswithin the controllers contained beneath those"child controllers" in the device hierarchy.

Dump child objects and thechildren's children.

Click this radio button to export a parent objectand everything beneath it. That is, this operationexports the parent object, all objects containedwithin

controllers belonging to the parent object, plus allobjects within the controllers contained beneaththose "child controllers" in the device hierarchy.

Text File Options

Overwrite the file if it alreadyexists.

Click this radio button to overwrite the data in thetarget text file with the data from the parentsource object.

Append to file if it already exists. Click this radio button to add the data from theparent source object to the data in the target textfile.



TAC 52

Checkbox

Dump pictures to separate files. Check this checkbox to export the graphicsin the source object into separate bitmapgraphics files. This operation results in onetext file for object data, plus individualgraphics files for the pictures.

Send To Controller Options

Continuum Explorer allows you to set source-object options when you perform "send-to-controller" operations – that is, when you update an object in the CyberStation databaseand need to distribute or "reload" the updated data to controllers that need to know aboutthe updates.

You can initiate send-to-controller operations from the Send To Controller selection inthe popup menu displayed when you right click a container object.

The following table describes selections in the Send To Controller Options dialog:


Do not reload attached objects. Click this radio button to reload the controller, butnot to reload the data from the attached objects.If this is used on a CX series Infinity controller,only the import/export table is reloaded.

Reload attached objects, but notattached controllers.

Click this radio button to reload the newlyupdated object data in the affected controllers,but not to reload the child objects belonging tothe controllers contained within this parent(attached) object in the device hierarchy.

Reload attached objects andcontrollers.

Click this radio button to reload the newlyupdated object data in the affected controllers,and also reload the data objects belonging to thecontrollers contained within this parent (attached)object in the device hierarchy.




Send To Database Options

Continuum Explorer allows you to set source-object options when you perform "send-to-database" operations. A send-to-database operation is needed if you have directlyupdated an object in a controller from a command terminal and need to notify systemadministrators that these updates must be synchronized with the CyberStation database.

You initiate Send-to-database operations from the Send To Database selection in thepopup menu displayed when you right click a container object.

The following table describes selections in the Send To Database Options dialog:


Do not save attached objects. Click this radio button to save the controller data tothe CyberStation database, not to save data fromattached objects.

Save attached objects, but notattached controllers.

Click this radio button to save the data in the objectthat you have just directly updated in a controller from the command terminal, but not to save thechild objects belonging to the controllers containedin this parent (attached) object in the devicehierarchy.

Save attached objects and

controllers.

Click this radio button to save, the data in the

object that you have just directly updated in acontroller from the command terminal, and also tosave the child objects belonging to the controllerscontained in this parent (attached) object in thedevice hierarchy.

CAUTION: Complete the following steps to ensure that the Send to Database operationis successful for controllers residing on a bCX1 40x0 controller for a fieldbus network.

"Learn" a bCX1 40x0 Controller before Sending to Database — Before performing aroutine Send to Database operation on a bCX1 40x0 series controller, you must firstperform a "learn" operation by clicking the Learn button on the Settings tab of the CommPort editor. (See Chapter 8.) This ensures that the bCX1 40x0 first knows about the

existence of its BACnet field bus controllers (b3 and third-party controllers). After thelearn, the Send to Database fetches object information from all controllers residing onthe field bus subnetwork and saves it to the CyberStation database. Before performingthe Send to Database operation, make sure you have also selected the Save attachedobjects and controllers radio button.



TAC 54

Help Menu

Selection Purpose

Contents Opens help topics for Continuum Explorer. (You may alsopress the F1 key.)

About ContinuumExplorer

Displays the CyberStation software version and copyrightinformation.

Quick Picks Toolbar

Button Description

Explorer bar. When you click the downward arrow to the right of theExplorer bar, a dropdown menu lists the Explorer bar viewing options.See “Using the Explorer Bars.”

View Class Folders. For additional information, see “UnderstandingObject Classes.”

View Objects. For additional information, see “Understanding ObjectClasses.”

Stops current process.

Refreshes, or updates, both panes with newly added, deleted, or modifiedobjects.

Moves the cursor one level higher in the tree hierarchy in the left pane.

Changes the views you see in the Continuum Explorer viewing pane. For additional information, see “Working with the Viewing Pane.”

Opens the Configuration Wizard.

Prints the viewing (right) pane of the Continuum Explorer on the defaultprinter. The dimensions depend on the default printer settings.

Command Scroll Box

The Command scroll box always shows the path of the last selected object. Clicking thescroll bar lists paths of all previously selected objects.




Popup Menus

Throughout CyberStation, in the Continuum Explorer and in almost all CyberStationapplications, right clicking displays a popup menu a popup menu.

Popup menus may interchangeably be referred to as shortcut menus.

The selection appearing in bold text in a popup menu is called the default verb for thatobject. When you double click an object in the Continuum Explorer or in a browse field,the action that takes place depends on the default verb for that object.

Continuum Explorer Window

The Continuum Explorer window is divided into two panes where objects appear:

• The navigation pane on the left

• The viewing pane on the right.

Navigation Pane

The navigation pane is a tree structure hierarchical representation of the root object andthe objects connected to it.

The first icon (the infinity symbol) that appears in the list is the root object. Below

the root object are device and folder objects. A plus sign (+) indicates that the objectcontains sub objects. Click the plus sign and the object icon opens, displaying itscontents.

In the above figure, the Network folder object is expanded, indicated by the fact that the +sign has been replaced by a minus sign (-). The Infinity 1 controller icon is displayed.When the + sign for the controller was clicked, the folder objects below it appeared. Clickthe minus sign (-) to collapse a list of objects or folders.



TAC 56

Viewing Pane

Use the viewing pane to view the contents of objects selected in the navigation pane andto find details about the objects you are viewing.

Selecting How Objects Will Be Displayed

You can use the viewing pane to display objects in four different ways by makingselections from the Views drop down menu, or by clicking the Views icon in the QuickPicks toolbar until the desired view appears.

Option Description Example

Icon Displayslarge icons inthe viewingpane

Small

Icon

Displays

small icons inthe viewingpane

List Displaysobjects in alist in theviewing pane

Details Displaysdetails of objects in theviewing pane




Details Options

The Details option provides the following information about CyberStation objects:

Column Description

Name Name of the object.

DeviceID or Owner

Identification of the attached folder or device.

Alias The name used to identify the object in programs and functions.When referring to an object, whether in a path or a program,always use the object alias.

Type The object class or type.

Last Change The date and time the object was last modified.

Changing the Width of Details View Columns

Place the cursor on a vertical line that separates two columns at the top of the DetailsView window:

When the cursor changes to look like this ,drag column boundaries to the left or right.

Class Folders or Objects

Use the class folder and object buttons in the Quick Picks toolbar to selecthow the viewing pane displays objects. You can display the class folders or the objects inthe class folders.

The picture on the left represents the class folder image of the objects pictured on theright.



TAC 58

Explorer Views

Continuum Explorer allows you to view your system in five different ways: All Paths,Networks, Folders, Templates, and BACnet View .

To change views, click the down arrow attached to the Explorer quick picks icon .

All Paths View

This is the default view for Continuum Explorer. It displays all elements in the Andover

Continuum system, including all devices, networks, folders, and templates. The Rootappears at the top of the navigation panel with all linked objects below it. The contents of any object selected in the navigation pane appear in the viewing pane.




Networks View

The Networks view shows the objects in your system in the viewing pane in relation tophysical hardware (workstations, controllers, and connected peripheral devices) thatcontains them in the navigation pane.

Folders View

The Folders view shows folders, subfolders and class folders in the navigation pane.

Folders, class folders, and objects are shown in the viewing pane.

The Folders view organizes objects in your system independent of their physicalconnection to each other. For example, suppose you have an Infinity Input point named

Room Temperature 1 attached to a controller named CX1 and you want to create a folder named Chiller Plant that contains all the objects having to do with cooling systems in abuilding. In Folder view, you place the CX1 controller in the Chiller Plant folder. (See thefollowing figure.)



TAC 60

In contrast to the Folders view, the Network view shows the objects in relation to their physical arrangement in the network. The figure below shows the comparison betweenthe two views back to the root object.

This arrangement is possible because CyberStation allows every object to have twoowners, an attached network device and a folder owner. In the figure, the input pointRoom Temperature 1 has two owners: Chiller Plant Folder and Attached Device CX1.The folder owner is optional.

Root

Root

Network

Building 1

Folder Owner

Chiller Plant

Attached Device

CX1

Infinity Input

Room Temperature 1

Folder View

Network View




Class Folders

CyberStation keeps track of the objects you create by storing them in class folders. Everytime you create a new object on a device, CyberStation either stores it in an existingclass folder, or, if the object is the first instance of a class, CyberStation creates theappropriate class folder for you. The picture below shows a device and all the classfolders that it owns:

Templates View

The Templates view displays the templates that are available in the CyberStation system.The templates (Chapter 12) appear as folders and subfolders in the navigation pane. Inthe viewing pane the templates are represented as folders and object icons.

BACnet View

In the BACnet view, only BACnet objects and devices are displayed. (Refer to Chapter 14.) For example:



TAC 62

Creating Objects

Here are some points to keep in mind before you create your first object:

• CyberStation automatically creates the appropriate class folders as you create your objects and stores the objects in the applicable views.

• You can store objects in more than one view at the same time.

• You may use either the navigation pane of Continuum Explorer or the New dialog tonavigate to the device that you want to attach.

Most objects must be attached to (stored in) a device such as a controller or workstation.The exceptions are:

Areas Folders Personnel

AlarmEnrollments Graphics Security Levels

Event Views Groups Templates

EventNotifications List Views Users

Creating a New Object

Perform the following steps to create a new object:

1. In the Continuum Explorer, select the Network or All Paths view.

2. Select the object to which you want to attach the new object. See the table on thefollowing page for a container object listing.

3. Right click the object or select New in the Object menu to display a pop up list of object classes.

4. Select the object class of the object you want to create.

For example, select InfinityNumeric to create an InfinityNumeric point object.

5. The New dialog appears, with the object type you selected displayed in the Objectsof type field. The following figure shows an InfinityNumeric object.

6. In the New dialog, enter the Object name field.




CyberStation fills in the Alias field, but you can change it.

7. Click Create to enter the editor of the object you are creating.

The following table lists the CyberStation objects that can be owned by container objects.

… Can Be Owned by this Container

This Object… Network InfinityController

InfinityInfinetController

Andover ContinuumWorkstation

InfinityFolder

BACnetDevice *

BACnet(Network)Folder **

AlarmEnrollment No No No Yes Yes No No

AnalogInput No No No Yes No Yes No

AnalogOutput No No No Yes No Yes No

AnalogValue No No No Yes No Yes No

Area No No No Yes Yes No No

BinaryInput No No No Yes Yes Yes No

BinaryOutput No No No Yes Yes Yes No

BinaryValue No No No Yes Yes Yes No

Calendar No No No No No Yes No

CommPort Yes Yes No No No No No

ControllerUser No Yes No No Yes No No

DateTime No No No Yes Yes No No

Device * No No No No No Yes Yes

Door No Yes Yes Yes Yes No No

EventEnrollment No Yes(b4/b3 only)

No No No Yes No

EventNotification No Yes(b4/b3 only)

No Yes Yes Yes No

EventView No No No No Yes No No

File No Yes Yes No No Yes No

Filter No No No No Yes No No

Folder No No No No Yes No No

Function No No No Yes Yes No No

Graphics No Yes Yes Yes Yes Yes No

Group No Yes Yes Yes Yes Yes No

InfinityController Yes No No No Yes No No

InfinityDateTime No Yes Yes No Yes No No

InfinityFunction No Yes Yes No Yes No No

InfinityInfinetCtlr No Yes No No Yes No No

InfinityInput No Yes Yes No Yes No No



TAC 64

… Can Be Owned by this Container

This Object… Network InfinityController

InfinityInfinetController

Andover ContinuumWorkstation

InfinityFolder

BACnetDevice *

BACnet(Network)Folder **

InfinityNumeric No Yes Yes No Yes No No

InfinityOutput No Yes Yes No Yes No No

InfinityProgram No Yes Yes No Yes No No

InfinityString No Yes Yes No Yes No No

InfinitySystemVariable

No Yes Yes No Yes No No

IOUModule No Yes No No* Yes No No

Listview No Yes Yes Yes Yes Yes No

Loop No Yes Yes No Yes No No

MultistateInput No No No Yes Yes Yes No

MultistateOutput No No No Yes Yes Yes No

MultistateValue No No No Yes Yes Yes No

Network No No No No Yes No No

NetworkDialup No No No Yes Yes No No

Personnel No No No No Yes No No

Program No Yes Yes Yes Yes Yes No

Report No Yes Yes Yes Yes No No

Schedule * No Yes Yes Yes Yes Yes No

SecurityLevel No No No No Yes No No

String No No No Yes Yes No No

TrendLog No Yes Yes No Yes Yes No

User No No No No Yes No No

VideoLayout No No No No Yes No No

VideoServer No No No No Yes No No

*Note: A Device is a BACnet object, viewed in the BACnet Devices portion of theContinuum Explorer. A BACnet Device object can be one of the following: Andover Continuum b4 or b3 controller device, third-party device, third-partyworkstation. Although Andover Continuum workstations are BACnet devices,they appear at the Root, not in the BACnet Devices network. Also, a Scheduleobject may or may not be owned by a third-party device, depending on whether the device supports Schedule.

**Note: A BACnet folder is a folder designated as a “network,” viewed in the BACnetDevices portion of the Continuum Explorer.




Importing from ASCII Dump Files

Importing from ASCII dump files is a process you can use to:

• Update or reload CyberStation objects with previously backed-up data.

• Create new objects.

You can update or create one CyberStation object from each ASCII file.

You may also set options for performing operations. See, Import Into Options Dialog earlier in this chapter.

Updating and Reloading Objects from ASCII Files

To update and reload data from ASCII files into existing CyberStation objects:

1. Right click the object that you want to update or reload.

2. From the popup menu, or from the Object dropdown menu, select Import Into.

3. In the Open dialog, locate and select the .DMP file that contains the back-up data for the object you want to reload, and

4. Click Open.

If your workstation is set up to confirm reloads, you'll see a confirmation dialog.

5. Click OK to start reloading the object.

If your workstation has been set up to monitor object loads, you will see a dialog that willshow you the load progress, as well as any errors that occur.

Creating Objects from ASCII Files

To create a CyberStation object from an ASCII file:

1. In the ASCII file, ensure that you specified the appropriate attribute values, such asName, Alias, Owner, Device ID, and Description for the object you want to create,and then save and close the file.

2. Right click the container where you want to store the new object, and select ImportInto... from the popup menu.

3. In the Open dialog, select the DMP files (*.DMP) you want to use and click Open.

If your workstation is set up to confirm load operations, you see a confirmation dialog.

4. Click OK to start loading the object.

If your workstation is set up to monitor object loads, you see a dialog that will showyou the load progress, as well as any errors that occur.



TAC 66

Exporting Object Data to ASCII Dump Files

Exporting data to ASCII dump files is a process by which all the information about anobject is sent to a text file.

To export data to an ASCII dump file for a CyberStation object:

1. From the Continuum Explorer, right click the object that you would like to export, andselect Send to... and then select Text File.

Note: If you right click an object that contains other objects, you will be exporting data

for all the contained objects as well as the object on which you clicked. Seealso Send To Text File Options Dialog, earlier in this chapter, for exportoptions involving an object's children and children's children.

2. In the Save As dialog, navigate to the folder that will store the file, and enter thename of the dump file, including a .DMP extension, in the File name field.

3. Click Save.

If your workstation is set up to confirm for ASCII dumps, a confirmation dialogappears.

4. Click OK.

If your workstation is set up to monitor ASCII dumps, you will see a dialog that will showyou how the dump is progressing, as well as any errors that might occur.

Importing from CSV Files

Importing from CSV files is a process you can use to:

• Update or reload objects.

• Update existing objects.

This feature allows the creation or update of one or more objects from a text filecontaining an object class name and a list of object attributes, one row per object.

All attributes and attribute values are separated by commas. CSV files are especiallyuseful for creating and loading Personnel objects for access control applications. A singleCSV file may include a list of Personnel records, each row containing, for example, LastName, First Name, Middle Initial, a template object name, photo file name, card number,and so on.

You may also set options for performing import operations. See: Import Into OptionsDialog earlier in this chapter.




Creating CSV Files for CyberStation

To create CyberStation objects from a CSV file, the file must contain an object classname, a list of object attributes, and one row for each object. The first line specifies theclass name of the objects to be imported. The second line, called the AttributeDefinition Line (ADL), defines the attributes to be imported by name. The third andsuccessive rows contain the objects themselves, called Attribute Value Lines (AVL),using the ADL as a template for what order the attributes are in. You can create and editCSV files in a text editor or a spreadsheet program.

An example of a CSV import file viewed through a text editor is as follows:

If you create or edit a CSV file with Microsoft Excel, you must open the CSV file with atext editor and remove all of the extra commas in the object class lines and at the end of any lines throughout the file that have extra commas at the end.

Object Class Attribute Definition Line

Attribute Value Lines

Extra

commas



TAC 68

Updating and Reloading Objects from CSV Files

To update and reload existing CyberStation objects from CSV files:

1. Right click the object that you want to update or reload, and select Import Into… from the popup menu.

2. In the Open dialog, select CSV Files (*.CSV) from the Files of type dropdown menu.

3. Locate and select the CSV file that you want to use, and then click Open.


4. Click OK to start reloading the object.

If your workstation is set up to monitor object loads, you'll see a dialog that will show youthe load progress, as well as any errors that occur.

Creating Objects from CSV Files

To create CyberStation objects from a CSV file:

1. Open the container object (root, folder, device or controller) that will contain theobject you are going to create, and right click the opened container object.

2. Select Import Into... from the popup menu.

3. In the Open dialog, select CSV Files (*.CSV) from the Files of type dropdown menu.

4. Locate and select the CSV file that you want to use, and then click Open.


5. Click OK to start loading the object.

If your workstation is set up to monitor object loads, you see a monitor dialog that willshow you the load progress, as well as any errors that occur.

Updating or Creating Personnel Objects from CSV Files

The CSV import of personnel objects follows the same format as that of other objects,except that there are three optional lines that can be added. The format includes thefollowing additional CSV keyword lines:

AutoNumber – This optional line automatically assigns CardType, SiteCode(for Non- ABA) and CardNumber for every personnel object imported. You can overwrite this auto-assignment for particular personnel by including CardType, SiteCode(For Non-ABA), andCardNumber in the attribute definition line and put non-empty values in the attribute valueline. If no value is specified in a line, auto-assignment will take place. This overwritefeature is useful when you want to change a personnel’s cardnumber with the Key linepresented and set to non-CardNumber.

Key – This optional line tries to resolve each attribute value line (personnel or user) byusing the unique key or keys specified in the key line. With this line, you can specify theattribute list that uniquely identifies personnel. Examples of Key lines are as follows:




• Key,firstname,lastname

• Key,socsecno

• Key,name

• Key,alias

• Key,cardnumber,sitecode,cardtype

• Key,name,socsecno

Note: Key must not be an attribute in any class. All attributes in the Key Definition Line(KDL) must also be in the Attribute Definition Line (ADL).

Option – This line has two options available, as follows:

• NoPhotoUpdate – This option does not update the personnel photo file.

• NoCardNumberCheck – This option does not check CardNumber duplication. Thiswill speed up personnel CSV import. Without this option, CSV import always checkCardNumber duplication.

The CSV import file format for personnel objects is as follows:

• ClassName

• AutoNumber ,CardType,SiteCode,BeginCardNumber

• Key,attribute1,attribute2,…

• Option,NoPhotoUpdate

• Attribute Definition Line

• Attribute Value Lines



TAC 70

CyberStation Object Editors

CyberStation object editors are dialogs you use for creating or modifying objects. Eachclass of CyberStation object has its own editor. Each editor shows the class name, objectname, and path in the title bar.

Opening an Object Editor

When you create an new object (described on the previous page) the object editor automatically appears on the CyberStation screen. Use one of the following methods toopen an editor for an object that already exists in Continuum Explorer.

• Double click the object in Continuum Explorer.

• Right click the object, and select Edit from the popup menu that appears.

Using CyberStation Object Editors

Each editor has a series of tabs containing text fields, buttons, and dropdown menus thatyou use to define or modify an object. You enter text in the fields, make choices byclicking buttons, and select from lists of possibilities.

The bottom of the dialog consists of five buttons: OK, Cancel, Apply, Refresh and Help:

Button Purpose

OK Save changes and exit the editor.

Cancel Exit the editor without saving changes.

Apply Apply and save changes without exiting the editor.

Refresh Update to current values.

Help Open online help topics for the object editor.

Access Security Rules in Continuum Explorer

The objects that appear in both the navigation and viewing panes of Continuum Explorer are determined by the user's security level settings for view access, as described below.

The navigation and viewing panes do not display objects to which the user does not haveview access. If users do not have view access to all the objects within a class folder, thefolder does not appear in the navigation path. For example, if a controller appears in thenavigation pane, and the user does not have view access to the InfinityNumeric objectsfor that controller, no InfinityNumeric class folder appears in the tree path beneath thecontroller.

Note: You cannot browse to individual objects for which you have view access if theobjects are contained within a class folder that you cannot access.

Multiple Path Lists

The security action "Multiple path lists" is included in the ListView class of the Securitymenu. (Refer to Chapter 4.)




Use this menu to determine whether or not a user has the ability to create listview objects

with a path type that shows objects for more than one path. This action should be usedwith the view access (above) to restrict users from seeing objects to which they do nothave access.



TAC 72




Security

Security groups and SecurityLevel objects are two CyberStation tools that you use todetermine the access privileges of CyberStation users.

• Security groups enable you to define the access privileges needed by different typesof CyberStation users. You can then assign users to appropriate security groups. Access privileges that you define for object classes in the Security editor apply to allobjects in that class (for example, all doors, all personnel).

• SecurityLevel objects are CyberStation objects that you attach to other CyberStationobjects or to containers. You use SecurityLevel objects if you want to further restrictsecurity group access to individual objects, or to actions, such as deleting or editing,that may be taken with the individual objects. You attach a SecurityLevel object toeach CyberStation container or object that you want to be controlled by thoseprivileges. Access privileges that you define in the SecurityLevel editor for SecurityLevel objects apply only to the individual objects or containers that you attachthem to. They do not apply to other objects in the same object class. For moreinformation, see SecurityLevel Editor.

Security Groups

A security group is a category of CyberStation privileges for using editors andapplications. Typically, a system administrator sets up security groups defined by certainaccess privileges and then assigns users to security groups in accordance with their needs.

The security groups are configured to allow or deny the user access to Continuumobjects. Security groups might include the following examples:

• Administrator ⎯ allowed access to all Continuum applications

• Security Guard ⎯ allowed full access to doors, areas, and personnel data but limitedto view only access to everything else.

• HVAC Technician ⎯ allowed access to all HVAC related objects, but denied accessto everything else.

4



TAC 74

Setting up CyberStation security groups has three major steps:

1. Configure security groups that allow or deny access to CyberStation object classesand actions.

2. Create a user object for each person who will be allowed access to a CyberStationworkstation.

3. Assign users to the appropriate security groups for the access each user requires.

This chapter explains the process of configuring the security groups. This chapter alsodescribes how to create SecurityLevel objects and use them with security groups to

further customize CyberStation security. See Chapter 5 to create user objects and assignthem to security groups.

Configuring User Security Groups

You use the Security editor to configure security groups. To access the Security editor,proceed as follows:

1. Right click the Continuum icon in your tooltray.

2. Select Security from the popup menu.

This displays the Security editor.

Displaying Security Groups

CyberStation provides 1024 security groups for which you can assign access privileges.By default, the first 128 groups are displayed. You can display the additional groups asneeded in multiples of 128 (256, 384, 512, and so on) up to 1024.

Note: If you reduce the number of displayed security groups, users assigned to groupsthat are no longer displayed lose all access to CyberStation. Be sure to assign allusers to security groups that are currently displayed.

Security groups that are not displayed retain their settings and user assignments. If youlater display these security groups, the settings in these groups will apply to any usersassigned to them.

1. In the Group Names tab, select a value from the dropdown list for Number of Security Groups.

2. Click the Change button.If you select a smaller number of groups, you are prompted to confirm the change.Click Yes to continue.

3. Click Apply or OK.

Renaming Security Groups

By default, the security group names are Group 01 through Group 1024. You can renamethe groups that you use, if you wish.

1. In the Group Names tab, use the vertical scroll bar to locate the security group namethat you want to change.

2. Double click the group name, enter a new name, and press the Enter key.




3. Repeat steps 1 and 2 to rename other security groups as needed.


Displaying Access Privileges in the Actions Tab

1. Select the Actions tab.

2. Expand a folder to display the object classes or tasks (actions) within that folder.Expand an object class to display the actions and editor tabs for that object class.

For example, expand the Area class to display the actions for Area objects and the

list of tabs in the Area editor.

Security groups are displayed to the right of the action or the tab name. The icon used toidentify each group indicates whether the group has access privileges for it:

• The Lock icon indicates that the users in the security group do not have access

privileges; that is, the action or tab is locked for this security group.

• The Key icon indicates that the users in the security group have access privileges;that is, the action or tab is unlocked for this security group.

Position your cursor over an icon to display the name of the security group and the actionor editor tab it represents. Group names are defined in the Group Names tab. You canedit the names as needed, and also select the number of security groups that aredisplayed.

Assigning Access Privileges for Security Groups

Use this procedure to assign or remove access privileges for security groups.



TAC 76

You can also assign and remove privileges by copying access settings to other securitygroups and by importing security groups. For more information, see Copying Security Groups and Importing and Exporting Security Groups later in this chapter.

Note: When you remove access privileges to view an object class for a security group,users in that group do not see that object in Continuum Explorer. If the objects arecontained within a class folder, the class folder is not displayed when any of theseusers are logged into CyberStation. For example, if a user belongs to a securitygroup that does not have access privileges to view Personnel objects, Personnelobjects and the Personnel class folder are not displayed in Continuum Explorer

when this user is logged into CyberStation.

1. Expand a view or folder. To assign access privileges to object classes, expand theClasses folder, and then expand an object class.

A list of actions is displayed. If you expanded an object class, a list of the tab namesin that object editor is displayed after the actions.

Use the vertical scroll bar to locate the action for which you would like to assignaccess privileges. In addition to actions specific to that object class, if any, thefollowing actions are listed for most object classes:

Change Out of Service — Users belonging to security groups with this privilege canenable and disable objects of this class.

Create —Users belonging to security groups with this privilege can create objects of

this class.

Delete —Users belonging to security groups with this privilege can delete objects of this class.

Edit —Users belonging to security groups with this privilege can open the editors of objects of this class, and modify object values in the editor.

View — Users belonging to security groups with this privilege can open the editors of objects of this class, but cannot modify any values unless they also have Editprivileges. These users will also be able to view the class folder for any objects for which they have view access (provided the users also have access to ContinuumExplorer).

Send To Text File — Users belonging to security groups with this privilege can

import and export object data to text files.

2. Assign or remove access privileges.

If you want to . . . Then . . .

assign an accessprivilege for an action or an editor tab to asecurity group

In the row that contains the action or tab name, click the

Lock icon for the security group that you want to havethe privileges.

The Key icon is now displayed for this security group,indicating that the group has access to the action or tab.





remove an accessprivilege for an action or an editor tab from asecurity group

In the row that contains the action or tab name, click theKey icon for the security group where you want to removethe privileges.

The Lock icon is now displayed for this securitygroup, indicating that the group does not have access tothe action or tab.

assign accessprivileges to all actionswithin a view, objectclass, or folder

Right click the view, object class, or folder, and selectUnlock Actions from the popup menu. In the UnlockActions for Groups dialog, select the checkbox next toeach security group that you want to have access, andclick OK.

The Key icon is now displayed for the selected securitygroups, indicating that the groups have access to all theactions (and editor tabs) in the view, object class, or folder.

remove accessprivileges to all actionswithin a view, object

class, or folder

Right click the view, object class, or folder, and selectLock Actions from the popup menu. In the Lock Actionsfor Groups dialog, select the checkbox next to each

security group that you do not want to have access, andclick OK.

The Lock icon is now displayed for the selectedsecurity groups, indicating that the groups do not haveaccess to any of the actions (and editor tabs) in the view,object class, or folder.

3. Click OK.

Copying Access Privileges Between Security Groups

Use this procedure to copy the access privileges assigned to one security group toanother security group. This is useful when you want to define privileges for a securitygroup that are only slightly different from another security group. When you paste the

copied access privileges to the destination security group, the privileges for all actions inall folders are replaced with the new privileges. You can then assign or remove privilegesas needed.

1. In the Actions tab, expand a view or folder.

2. If needed, use the horizontal scroll bar to display the icon for the security groupwhose access privileges you want to copy.

3. Right click the security group, and select Copy Group from the popup menu.



TAC 78

4. If needed, use the horizontal scroll bar to display the icon for the security groupwhere you want to paste the access privileges.

5. Right click the security group where you want to paste the privileges, and selectPaste Group from the popup menu.

6. Assign or remove privileges as needed for the security group where you copied theaccess privileges.


Exporting and Importing Security Groups

CyberStation provides backup and restore capabilities for the security group settings withits export and import features. These features export and import security group settingsusing dump files with the security dump file extension (.SDF).

The export feature exports the access privileges for all security groups. The importfeature imports the access privileges from a security dump file that you select. You canimport access privileges for all security groups or for a selected security group.

Exporting Security Groups

Use the following procedure to export access privileges for all security groups.

1. In the Actions tab, right click anywhere under Action or Locks, and select ExportAll from the popup menu.




2. In the Save As dialog, enter a filename, and click the Save button to create the .SDF

file.

Importing One Security Group

Use this procedure to import the access privileges for a selected security group from asecurity dump file (.SDF).

1. In the Actions tab, expand a view or folder, and right click the security group for which you want to import access privileges.

2. Select Import Group from the popup menu.

3. In the Open dialog, select the file containing the security group settings you want toimport, and click the Open button.

Note: Importing access privileges overwrites the previous access privileges for thesecurity group. Ensure that you have imported the access privileges that you

want to use before clicking Apply to save them in the Security editor.

4. Click Apply or OK to save the access privileges for the selected security group.

Importing All Security Groups

Use this procedure to import the access privileges for all security groups from a securitydump file (.SDF).

1. In the Actions tab, right click anywhere under Action or any white space, and selectImport All from the popup menu.

2. In the Open dialog, select the SDF file that contains the security group privileges thatyou want to import, and click the Open button.



TAC 80

Note: Importing all security group privileges overwrites the previous access privilegesfor the security groups. Ensure that you have imported the access privilegesthat you want to use before clicking Apply to save them in the Security editor.

3. Click Apply or OK save the security groups settings.

Configuring Object-Level Security

Use the SecurityLevel editor to define the security group access privileges in aSecurityLevel object. You can create multiple SecurityLevel objects, each with

customized access privileges. You then attach a SecurityLevel object to individualCyberStation objects or containers. Each of these is then accessible to users only asdefined in the SecurityLevel object attached to it. If you attach a SecurityLevel object to acontainer, such as a folder, all objects stored in the folder are accessible as defined in theSecurityLevel object.

This customized security is known as object-level security, and it works with the accessprivileges defined in security groups. In the Security editor, you set up security groupsand assign access privileges to those groups. These access privileges are defined for object classes rather than individual containers or objects. Object-level security further refines those access privileges by controlling access to individual containers or objects towhich SecurityLevel objects are attached.

Note: Object-level security can be more restricted than the access privileges defined in

the Security editor for security groups; it cannot be less restricted. For example, if users in a security group can edit Personnel objects, a SecurityLevel objectattached to selected Personnel objects can prevent the users from editing thoseobjects. However, the reverse is not permitted in CyberStation: if users in a securitygroup are prevented from editing Personnel objects, a SecurityLevel object withediting of Personnel objects unlocked does not allow the users to edit Personnelobjects to which the SecurityLevel object is attached. When user-level and object-level privileges differ for the same object class and action, CyberStation uses themore restricted setting.

Creating a SecurityLevel Object

Note: You cannot delete or move SecurityLevel objects. In Continuum Explorer, theymust reside in Root.

1. In Continuum Explorer, right click Root.

2. Select New, and then select SecurityLevel from the popup menu.

3. Enter a name for the object, and click Open.

4. The SecurityLevel editor is displayed. You define access privileges for theSecurityLevel object in the Security tab of this editor.

Displaying Access Privileges in the Security Tab

Expand Classes to display the object classes. Expand an object class to display theactions and editor tabs for that object class. For example, expand the Area class todisplay the actions for Area objects and the list of tabs in the Area editor.




Security groups are displayed to the right of the action or the tab name. The icon used toidentify each group indicates whether the group has access privileges for it:

• The Lock icon indicates that the users in the security group do not have accessprivileges; that is, the action or tab is locked for this security group.

• The Key icon indicates that the users in the security group have access privileges;that is, the action or tab is unlocked for this security group.

Position your cursor over an icon to display the name of the security group and the actionor editor tab it represents. Group names are defined in the Group Names tab of theSecurity editor.

Universal Unlock Folder

Using the Universal Unlock folder, you can deny one or more user groups universalaccess and viewing privileges to all features of all objects to which the SecurityLevelobject is attached. When you deny a security group access privileges (place a lock) inthis folder, it overrides any other key (unlock) on any features throughout the system for that security group. It is a quick way to prevent access to every object to which theSecurityLevel object is attached for users in the security group. (Users are assigned tosecurity groups in the Groups tab of the User editor.)

When the universal lock is unlocked, all objects owned by a parent (folder or device)inherit the security level of the parent; security levels of each class are applied. To deny

all access to any security group, lock the universal lock for that group. This simplifies thetask of locking all access for a security group from a folder or a device.

Assigning Access Privileges in a SecurityLevel Object

Use this procedure to assign access privileges to security groups in a SecurityLevelobject.

1. In the Security tab, expand the Classes folder, and then expand an object class.

A list of actions is displayed, followed by a list of the tab names in that object editor.

Use the vertical scroll bar to locate the action for which you would like to assignaccess privileges. In addition to actions specific to that object class, if any, thefollowing actions are listed for most object classes:

Change Out of Service — Users belonging to security groups with this privilege canenable and disable objects of this class.

Create —Users belonging to security groups with this privilege can create objects of this class.

Delete —Users belonging to security groups with this privilege can delete objects of this class.

Edit —Users belonging to security groups with this privilege can open the editors of objects of this class, and modify object values in the editor.



TAC 82

View — Users belonging to security groups with this privilege can open the editors of objects of this class, but cannot modify any values unless they also have Editprivileges. These users will also be able to view the class folder for any objects for which they have view access (provided the users also have access to ContinuumExplorer).

Send To Text File — Users belonging to security groups with this privilege canimport and export object data to text files.

2. Assign or remove access privileges.


assign an accessprivilege for an action or an editor tab to asecurity group

In the row that contains the action or tab name, click the

Lock icon for the security group that you want to havethe privileges.

The Key icon is now displayed for this security group,indicating that the group has access to the action or tab.

remove an accessprivilege for an action or an editor tab from asecurity group

In the row that contains the action or tab name, click theKey icon for the security group where you want to removethe privileges.

The Lock icon is now displayed for this securitygroup, indicating that the group does not have access tothe action or tab.

assign accessprivileges to all actionswithin a view, objectclass, or folder

Right click the view, object class, or folder, and selectUnlock Actions from the popup menu. In the UnlockActions for Groups dialog, select the checkbox next toeach security group that you want to have access, andclick OK.

The Key icon is now displayed for the selected securitygroups, indicating that the groups have access to all theactions (and editor tabs) in the view, object class, or folder.

remove accessprivileges to all actionswithin a view, objectclass, or folder

Right click the view, object class, or folder, and selectLock Actions from the popup menu. In the Lock Actionsfor Groups dialog, select the checkbox next to eachsecurity group that you do not want to have access, andclick OK.

The Lock icon is now displayed for the selectedsecurity groups, indicating that the groups do not haveaccess to any of the actions (and editor tabs) in the view,object class, or folder.




3. Click OK.

You attach a SecurityLevel object to individual CyberStation objects in theSecurityLevel tab in their respective object editors. For more information, see thehelp topics for SecurityLevel tabs in the editors.

Copying Access Privileges from a Single Security Group to Another Group

Use this procedure to copy the access privileges assigned to one security group toanother security group. This is useful when you want to define privileges for a security

group that are only slightly different from another security group. When you paste thecopied access privileges to the destination security group, the privileges for all actions inall folders are replaced with the new privileges. You can then assign or remove privilegesas needed.

1. In the Security tab, expand an object class.

2. If needed, use the horizontal scroll bar to display the icon for the security groupwhose access privileges you want to copy.

3. Right click the security group, and select Copy Group from the popup menu.

4. If needed, use the horizontal scroll bar to display the icon for the security groupwhere you want to paste the access privileges.

5. Right click the security group where you want to paste the privileges, and selectPaste Group from the popup menu.

6. Assign or remove privileges as needed for the security group where you copied theaccess privileges.




TAC 84

Copying Access Privileges from the Security Editor

Use this procedure to copy the access privileges for all security groups from the Securityeditor to a SecurityLevel object. You can paste the access privileges into a SecurityLevelobject in the SecurityLevel editor and then edit the access privileges as needed for theobject.

Note: You can also copy access privileges from another SecurityLevel object and pastethem into a different SecurityLevel object.

1. In the tool tray, right click the Continuum icon, and select Security from the popup

menu.

2. In the Actions tab, right click any white space (not over text or icons), and selectCopy All from the popup menu.

3. Click OK.

4. In Continuum Explorer, create or edit the SecurityLevel object where you want topaste the access privileges.

5. In the SecurityLevel editor, select the Security tab.

6. Right click any white space, and select Paste All from the popup menu.

7. Edit the access privileges as needed, and click Apply or OK.

Viewing Objects Controlled by a SecurityLevel ObjectUse this procedure to view a list of the CyberStation objects to which a specificSecurityLevel object is assigned.

1. In Continuum Explorer, expand the SecurityLevel folder, and double click theSecurityLevel object you want to view.

2. In the SecurityLevel editor, select the Attached Objects tab.

The list of objects to which this SecurityLevel object is attached is displayed.




Attaching a SecurityLevel Object to a Container or Object

Only one SecurityLevel object can be attached to an object or container. You can alsoremove a SecurityLevel object from an object.

1. Open the object to which you want to attach a SecurityLevel object in its editor.

2. Select the SecurityLevel tab.

3. Select the SecurityLevel object you want to attach to this object.

If you want to remove an attached SecurityLevel object without attaching another one, right click in the list of SecurityLevel objects, and select Clear Selection.

4. Click OK.

Folder and Device Level Security

Folder and device level (FDL) security allows you to apply a security level to a collectionof child objects by placing them in a folder or device object (the parent) so that the childobjects inherit the parent’s security level.

Note: FDL security does not apply to Root, since Root is not treated as a folder by FDL.

Attaching SecurityLevel Objects to Parent Objects and Folders

Your CyberStation system can include thousands of objects that you want to beaccessible only to the appropriate users. One efficient way to define access to theseobjects is to attach SecurityLevel objects to containers: parent objects and folders thatcan contain other objects. Child objects in the container inherit the access privilegesdefined in the SecurityLevel object attached to the container. Implementing security inthis way is referred to as folder and device-level (FDL) security.

For example, you can create a folder and place personnel, areas, doors, points, andprograms into it and then attach a security level object to the folder that gives viewaccess to one group of users, edit access to another group of users, and no access to athird group of users. You an also apply the same process to a network controller, anInfinet controller or a CyberStation workstation.



TAC 86

Guidelines for Using FDL Security

When you configure security at your site using FDL, consider the following factors:

• Roles ⎯ categories to which a user can be assigned (Administration, Guard,Maintenance, and so on)

• Partitions ⎯ division of site into physical areas (Building A, Building B, and so on)

• Security Groups ⎯ the combination of roles and partitions (BldgAAdmin,BldgAGuard, BldgAMaint, and so on)

The number of groups can be determined by the following formula:

Number of groups = Number of roles X Number of partitions

The use of these guidelines is illustrated in the following example.

Example of Using FDL Security

Consider the situation where you want to partition the security in a site that is located intwo separate buildings. Using the above guidelines, proceed as follows:

1. Determine the roles of the users. This example uses three categories:

• Administrators

• Guards

• Maintenance

2. Determine the partitions. This example uses two partitions:

• BuildingA

• BuildingB

3. Determine the number of security groups to configure:

Number of roles x Number of partitions = Number of groups

For example:

3 x 2 = 6 Security groups

4. Assign names to security groups in the Group Names tab of the Security editor:

BldgAAdmin BldgBAdmin

BldgAGuard BldgBGuard

BldgAMain BldgBMain

5. In the Actions tab, select security privileges for each group.

This should be role based. That is, all guards should have the same lock and keysettings. The same should be true for the maintenance personnel. Administratorsusually have keys to all objects and actions.

6. Create users, and assign each user to the appropriate group in the User editor. (SeeChapter 5.)

7. In Continuum Explorer, create two folders named BuildingA and BuildingB.




8. Create a SecurityLevel object for each folder named BldgAAccess and BldgBAccess,and define access as shown in the following table.

You can use the Universal Lock/Unlock feature in the SecurityLevel editor to quicklyassign access privileges to the security groups.

Folder Security LevelObject

Groups AllowedAccess

Groups DeniedAccess

BuildingA BldgAAccess BldgAAdminBldgAGuard

BldgAMain

BldgBAdminBldgBGuard

BldgBMain

BuildingB BldgBAccess BldgBAdminBldgBGuardBldgBMain

BldgAAdminBldgAGuardBldgAMain

9. Attach the SecurityLevel objects to the appropriate folders.

10. Place the objects associated with each building in the appropriate folders.

User Limitations

Users that do not have access privileges to certain folders/devices will not be able toaccess any objects contained in them. Pinpoint is the exception to this. Pinpoint will nothide controls based on FDL security. However, Pinpoint does prevent users from editingobjects that they have no access to.

The following table summarizes the effect of user access privileges with FDL security.

Function User Limitations

List Views The user will be able to see objects they don’t have access to, but willnot be able to access them.

Group Views The user will be able to see objects they don’t have access to, but willnot be able to access them.

Active AlarmView

The user will be able to see objects they don’t have access to, but willnot be able to access them.

Event View The user will be able to see objects they don’t have access to, but willnot be able to access them.

ContinuumExplorer

The user will not see any object that the user doesn’t have view accessto when using the Universal Lock. If the Universal Lock is unlocked, for a group and the view access of a device class or folder is locked, thenthe corresponding device/folder will not be viewable from explorer.

If a security level object is set up to allow viewing the folder but notviewing any child class under it, attaching this security level object to afolder would not prevent child class objects from showing under thatfolder in Continuum Explorer. When users click a child class objecthowever, an “access denied error” will show up. The use case of viewing a folder/device but not viewing children under that folder/devicein Explorer is not supported in current FDL implementation.



TAC 88

Function User Limitations

CommandLine

The user cannot change the value of any object or attribute if they donot have change value level.

Editors The user cannot edit any object that they do not have edit access to.This applies to all editors independently of where they are launched.

web.Client All applications in web.Client will mirror the corresponding CyberStationsecurity functionality.

Pinpoint Pinpoint will not apply view FDL security to controls. All controls willalways display. If the user does not have change value level, then theycannot modify values using in line controls. If they do not have editaccess, then they are denied from launching object editors. If they donot have access to other graphics that are linked using buttons, thenthey will be denied access to the graphics when clicking the button.




18Configuring

Users

What Are Users?

A user is a person who logs onto a CyberStation workstation on a command terminal tomonitor and manage their building control system. Users have passwords that allow themaccess to CyberStation, and they have security levels that restrict the kinds of changesthey can make, and actions they can take.

User Object

For every user in your company who is allowed access to your building control system,you must create a User object in CyberStation. User objects contain each user’spassword and security group assignment. If you choose to you can also record personalinformation, such as the Social Security number and address, about each user.

User objects are always created under the Root object. ControllerUser objects arecreated under the applicable NetController. ControllerUser cannot exist under Root.

ControllerUser Object

For every user in your company who is allowed access to a command terminal remotelyconnected to a NetController you must create a ControllerUser object in CyberStation.(See Creating a ControllerUser Object , later in this chapter.) Controller users are

separate from CyberStation users. Controller objects have a direct relationship with theNetController they are connected to.

Customizing the User Environment

In CyberStation, you can customize each user’s environment by specifying the following:

• Programs that start when the user logs in or out

• A graphic panel to display when the user logs in

• A menu-pages file to display when the user logs in

• A report program to run when the user logs in

Procedures for customizing the user’s environment begin below.

5



TAC 90

Additionally, the CyberStation can be configured to implement the features that assist insatisfying the requirements of Part 11 of Title 21 of the Code of Federal Regulationsentitled Electronic Records; Electronic Signatures (better known as 21 CFR 11).Procedures for setting features on the General Preferences and CFR Preferencesdialogs to implement these features are presented later in this chapter.

Before Configuring Users

You’ll use the User editor to configure each user of your system. Before using the editor,you need to know the following information about the person to whom you are giving

access to the system:• The user’s name. There are two name considerations: the name that is assigned to

the User object that is created for the user and the Full Name that is entered in theUser editor. The object name is the one that system recognizes.

• The password this user will use when logging on to CyberStation. (It must bebetween 0 and 16 alphanumeric characters as determined by the GeneralPreferences setting.)

• What programs, reports, menu pages, or graphics panels you want to run when thisUser logs on.

• The CyberStation User Security Group(s) that this user will be assigned to.

In order to use the User editor, you must first create a User object.

Creating a User ObjectCreate a user object for each person who requires access to the CyberStation software. At a minimum, you specify the following information:

• Object name, which is also the username the user enters to log on to CyberStation

• Password, which is also required to log on

• Security group or groups to which the user is assigned (See Chapter 4 for moreinformation about security groups.)

You can also enter personal information for the user.

Perform the following steps to create a User object:

1. In Continuum Explorer, right click the Root.

2. Select New, and then select User from the popup menu.

3. In the New dialog, enter the username in the Object name field.

CyberStation fills in the Alias field, but you can change it if needed.

4. Click the Create button.

General Tab – User Editor

In the General tab, you enter the user password. You can also enter personalinformation, such as the user’s full name and phone number.




Full Name Enter the user’s full name. You may use up to 32 characters,including spaces. The order of the first and last names is notimportant, but you should use the same format for all your users.Full Name is optional.

Users must enter their user name, to log into CyberStation. For example, if you create a user object named jbrown for Jim Brown,Jim must enter jbrown and his password to log in.

Password Enter the user’s password. The password must be between 0 and16 alphanumeric characters, including underscores and periods.The password must start with a letter. For security, the charactersyou type are displayed as asterisk marks (*). A password is optional,but highly recommended.

SocialSecurity

Enter the user’s Social Security number. You can use up to 11characters, including dashes. This is optional.

Address Enter up to 48 characters, including spaces, for the user’s address.This is optional.

Office Phone # Enter the user’s office phone number. You can use any charactersyou need, such as dashes and parenthesis. This is optional.

Home Phone # Enter the user’s home phone number. You can use any charactersyou need, such as dashes and parenthesis. This is optional.

Employee # Enter the user’s employee number. You can use up to 32characters, including spaces and dashes. The employee number can contain letters as well as numbers. This is optional.

Title Enter the user’s job title. You can use up to 32 characters, includingspaces. This is optional.

Security Tab – User Editor

In the Security tab, you can set up programs, reports, menu files, and graphic panels torun or display when this user logs on. These settings, in addition to access privilegesdefined in the security group(s) to which you assign each user, allow you to control theinformation users can view and change in CyberStation.

Personnel Record Not implemented in this release.

State Select either enabled or disabled from the dropdown menu.When a user object is disabled, the user will not be able to login. If you disable a user while he/she is logged on, that user isautomatically logged off. When a user object is enabled, theuser will be able to log in.



TAC 92

LogOn Program If you have a program that you would like to run every time theuser logs on, click the browse button to locate and select it.This displays a Browse dialog to help you find the right file.When you have located the file you want, select it and click theSelect button. This inserts the correct path and filename intothe Logon Program text field.

LogOff Program If you have a program that you would like to run every time theuser logs off, click the browse button to locate and select it.This displays a Browse dialog to help you find the right file.

When you have located the file you want, select it and click theSelect button. This inserts the correct path and filename intothe LogOff Program text field.

Report If you have a report that you would like to run every time theuser logs on, click the browse button to locate and select it.This displays a Browse dialog to help you find the right file.When you have located the file you want, select it and click theSelect button. This inserts the correct path and filename intothe Report text field.

Menu File If you have a file containing customized CyberStation menuoptions that you would like to run every time the user logs on,click the browse button to locate and select it. This displays a

Browse dialog to help you find the right file. When you havelocated the file you want, select it and click the Select button.This inserts the correct path and filename into the Menu Filetext field.

Graphic If you have a graphic panel that you would like to display everytime the user logs on, click the browse button to locate andselect it. This displays a Browse dialog to help you find the rightfile. When you have located the file you want, select it and clickthe Select button. This inserts the correct path and filenameinto the Graphic text field.

Inactivity Timer In this field, you enter the amount of time (in minutes) that nouser activity occurs in CyberStation before the user is

automatically logged off. All applications, such as theContinuum Explorer, the Plain English IDE, Pinpoint, and anyobject editor will be closed after the number of minutes.

Note: Keyboard entry and mouse clicks are considered user activity. Hovering the mouse over any CyberStationapplication is not considered user activity.

Enable Operator Text Prompt for changes

When checked, a comment dialog appears whenever this user modified any objects, persistent settings, etc. This option isenabled by default when a user object is created.




Enable Operator Text Prompt for AlarmAcknowledgement

When checked, a comment dialog appears whenever this user acknowledges an alarm.. This option is enabled by defaultwhen a user object is created.

Groups Tab – User Editor

In the Groups tab, you select the security groups that you want to assign the user.Security groups determine the objects this user can work with and the actions the user can perform with those objects. Users can belong to more than one security group.

Click the checkbox for each security group to which this user will belong. To remove theuser from a specific security group, click the checkbox to remove the check mark.

CyberStation provides you with 1024 security groups. By default, these security groupsare named Group 1 through Group 1024. You can rename security groups and specifyobject actions for each in the Security dialog.

SecurityLevel Tab – User Editor

For details in attaching or detaching SecurityLevel objects to CyberStation objects , seeChapter 4, Security .



TAC 94

Setting up the General and CFR Preferences

There are two separate preference menus that allow you to set up the user activity thatsatisfies the 21 CFR 11 requirements. Preferences for most requirements are included inthe main release of CyberStation and are covered under the General Preferences section(below). The remaining CFR features, which the customer may choose to purchase, arecovered under the CFR Preferences section, later in this chapter.

General Preferences

This section presents password management requirements and configuration of 21CFR 11. In order to implement the password management features of CyberStation, thefollowing requirements must be met:

• A General Preference setting for a password age of between 7 and 180 days mustexist for all users of the system.

• A General Preference setting for a password length of between 0 and 16alphanumeric characters must exist for all users of the system.

• A General Preference setting for the consecutive number of invalid login attempts of between 0 and 255 before an alarm is triggered must exist for all users of the system.

• A General Preference setting that tells CyberStation how far back in time to check auser’s password history – the number of previous passwords to check – in search of duplicate passwords. When a user changes the password, or the password expires,

and a duplicate password is found in his/her password history, the user receives anerror message.

• A General Preference setting to force a password change after the password of auser account has been modified must exist for all users of the system.

• An EventNotification object called LogonStatus must exist to trigger an Invalid Attempt Alarm.

• A means to allow any user of the system to change their own password at any time.

• A means to allow the system administrator to immediately disable the account of anyuser of the system.




Setting up Password Management Features

Perform the following steps to set up the password management features inCyberStation.

1. Right click the Continuum symbol located in the tool tray area of the Windowstask bar, and select General Preferences.

The General Preferences dialog appears. The first six preference attributes in the listapply to CyberStation password management.

2. In the Value column, enter or select your preference for each attribute.

Preference Value

Maximum password age Enter a value between 7 and 180 days. The defaultvalue is 0, which means it never expires.

Minimum password age Enter a value between 1 and 16 alphanumericcharacters. The default value is 0.

Maximum consecutive

invalid attempts beforealarm in triggered

Enter a numeric value. The default value is 5.

Note: Setting this column to zero (0) will prevent thealarm from being triggered for invalid logins witha valid User account.



TAC 96

Preference Value

Password History Depth Enter a value between 1 and 10. The default value is 1.

When a user changes his/her password, or when apassword expires, CyberStation used this number tolook for previous duplicate passwords in this userspassword history. This number tells CyberStation howfar back in time to check a password history (thenumber of previous passwords to check).

A value of 1 means the new password cannot be thesame as the old password. A value of 2 means the oldpassword cannot be the same as either of the twoprevious passwords, and son on.

CyberStation always stores every user’s last 10passwords. This mean that you, the administrator canuse this feature and enforce passwords immediately,rather than waiting for password histories toaccumulate.

Enable Operator TextPrompt for AlarmAcknowledgement

Select True. The default value is False.

Force password changeafter User accountpassword modification

Select True. The default value is True.

3. Click the Close button.

4. In Continuum Explorer, under Root in the All Paths view, double click theTemplates folder, and select EventNotification.

5. Double click LogonStatus EventNotification object in the Explorer’s viewing pane.

6. In the EventNotification editor, enter the appropriate settings for the LogonStatusobject as described in Using the EventNotification Editor in Chapter 10. Make surethat the applicable workstations are included in the Delivery tab as recipients of theLogonStatus object.

The CyberStation is now configured to implement password management.

General Preferences Settings for Extended-Log Reports

Your CyberStation administrator configures settings 7 through 10 in the GeneralPreferences dialog as part of the process of configuring extended logs. For moreinformation on setting up extended logs and descriptions of these General Preferencesettings, please see the subsection, Extended Logs, in the description of the point-editor Logs tab in Chapter 13. See also What Are Extended Logs? in Chapter 11.




CFR Preferences

The additional 21 CFR 11 features affects two separate areas of the CyberStationsystem:

• Audit Trail

• Alarm Log

Both of these areas are configured from CyberStation’s CFR Preferences dialog.

Setting Up Audit Trail Features

In order to implement the Audit Trail features of CyberStation, the following requirementsmust be met:

• The 21 CFR 11 bit of the Security hardware Key (supplied with the CyberStationinstallation kit) must be enabled in order for the CFR Preferences features of CyberStation to be available.

• An entry to the Activity Log when CyberStation starts up. The entry will not includeuser information since no user is logged on at that time.

• An entry to the Activity Log when CyberStation shuts down. The entry will includeuser information.

• A setting to enable an Operator Text Prompt for changes at both the CFRPreferences and user levels of the system.

•

A CFR Preferences setting that provides the user with the option to enable logging of all attribute values that are set when an object is created.

Perform the following steps to set up the Audit Trail features in CyberStation.

1. Right click the Continuum icon in the tool tray, and select CFR Preferences form theContinuum popup menu to access the CyberStation CFR Preferences dialog.

2. Verify that the value of item 2, Enable Operator Text Prompt for changes, is set toTrue.

3. For item 3, Log attribute values set at object time select either:

True to log the attributes that are set when an object is created.

False to not log the attributes that are set when an object is created.

4. Click Close.5. For each CyberStation user, verify that the Enable Operator Text Prompt for

Changes checkbox is checked in the Security tab of the User editor.

This is the default setting.

The CyberStation is now configured to implement the 21 CFR 11 Audit Trail features.



TAC 98

Setting up Alarm Log Features

In order to implement the Alarm Log features of CyberStation, the following requirementsmust be met:

• The CFR 11 bit of the Security hardware key (supplied with the CyberStationinstallation kit) must be enabled in order for the CFR Preferences features of CyberStation to be available.

• The user is forced to enter text comments along with user name and password to the Alarm log whenever alarms are acknowledged; this is covered under the General

Preferences dialog.The user name and password must match the logged on user ⎯ this only applieswhen the “Allow different user to sign off operator text” value is set to False in theCFR Preferences dialog.

• A CFR Preference setting that provides the option of allowing a user other than theoriginal user to sign off operator text dialogs.

Perform the following steps to set up the Alarm Log features in Continuum CyberStation.

1. Right click the Continuum icon in the tool tray, and select CFR Preferences from theContinuum popup menu to access the CyberStation CFR Preferences dialog.

2. For item 1, Allow different user to sign off operator text , select one of thefollowing settings:

True if you want operator text dialogs to accept any valid and enabled CyberStationuser name and password.

False if you want operator text dialogs to accept only the user name and password of the user that is logged on.

3. For each CyberStation user, verify that the Enable Operator Text Prompt for AlarmAcknowledgement checkbox is checked in the Security tab or the User editor.

This is the default setting.

The CyberStation is now configured to implement the 21 CFR 11 Alarm Log features.




Results of General and CFR Preference Settings

Once the features that affect the Password Management, Audit Trail and Activity Loggingactivities (previously described) have been implemented, the events discussed belowwill occur.

Invalid Login Attempts

When an invalid login attempt occurs at login, the following error message will appear.

When the maximum number of invalid logins (set in the General Preferences dialog) isexceeded, the following error message appears:

If the workstation is added to the list of recipients in the Delivery tab of theEventNotification editor (for the LogonStatus EventNotifcation object), this alarm isreported in the Active Alarm View. The user name and the workstation that was used for the logon attempts are displayed.

Also, any attempt to login at any workstation with a disabled account will fail and berecorded on the Activity log. This situation is shown in the second entry of the Active Alarm View log shown above.

Maximum Password Age Exceeded

Whenever the Maximum password age setting in the General Preferences dialog isexceeded for a user, the user is prompted to create a new password when the user nextattempts to log in.

Password Change and/or Password Length ExceededWhen either of these events occur:

• The password is changed in the General tab of the User editor, and the Force password change after User account password modification in the GeneralPreferences dialog is set to True.

• The Minimum password length setting in the General Preferences dialog isexceeded.

The user is not allowed to access the system until he/she successfully creates a newpassword. The new password must be different than the old one.



TAC 100

Duplicate Password Found in Password History

Whenever a user changes his/her password, or it expires, and CyberStation finds aduplicate password in a user’s password history (the depth of which is specified in thePassword History Depth setting of the General Preferences dialog) the user isprompted to create a different password.

Enabling Operator Text Prompts for Changes

Each time a modification is made to an object, or the user makes some other type of persistent change, and the Enable Operator Text Prompt for changes setting on the

CFR Preferences dialog is set to True, the user is prompted to enter a comment.

The user must enter explanatory text in the Comment field and then enter a valid user name and password in the appropriate text fields.

If the user tries to cancel comment entry, an entry is recorded in the log indicating thecanceled action. Also, the action indicated by the text entry will be canceled.

Enabling Operator Text Prompt for Alarm Acknowledgement

Whenever an alarm is acknowledged, or an audio alarm is silenced and the EnableOperator Text Prompt for Alarm Acknowledgement setting on the GeneralPreferences dialog is set to True, the user is prompted to add a comment as well astheir user name and password. The comments and the user name appear in theOperator Text column of the Active Alarm View.

Disabling a User Account

The CyberStation administrator can log any user out of all workstations by either of thefollowing methods:

• Right click the User object, and select Disable from the popup menu:

• In the User editor, select Disabled in the State dropdown menu on the Security tab.

Creating a ControllerUser Object

The ControllerUser object allows you to assign the security level permissions for userswho need access to a command terminal interface to a network controller. You can trackall changes in the CyberStation activity log. ControllerUser objects can be owned only bya network controller.

To create a ControllerUser object:1. In Continuum Explorer, right click the network controller where you want to create a

ControllerUser, and select New and ControllerUser from the popup menu.

2. In the New dialog, enter the name of the ControllerUser in the Object name field,and click the Create button.

3. In the General tab, enter information about the ControllerUser object as describedbelow.

Full Name Enter the full name of the controller user.

Password Enter the password of the controller user.




Login Program Use the browse button to search for the name of theCyberStation program that will run when the ControllerUser logs in. This program must be owned by the same controller that owns the UserController object.

LogoutProgram

Use the browse button to search for the name of theCyberStation program that will run when the ControllerUser logs out.

Controller Security Level

Select a security level from the drop down list

Refer to Object Level Security in Chapter 4 for details on how to attach aSecurityLevel object to a ControllerUser object.

4. Click OK.

You can use Continuum Explorer’s Copy and Paste features to place the sameControllerUser on other network controllers.



TAC 102




Configuring a

Network

A network is a system of one or many controllers and their connected peripheral devicesthat are linked together on an Ethernet communications network to share information. InCyberStation, a network object represents a network configuration of up to 190controllers that know about and exchange information with each other. This chapter describes the process of creating a network object.

6



TAC 104

Creating a Network Object

Create a Network object, as follows:

1. In the Continuum Explorer, right-click the Root object, select New, and then selectNetwork.

2. In the New dialog, enter a name for your network object in the Object Name field.


4. In the General of the Network editor, enter information about the network object.Description Enter a description of the Network object, up to 32

characters (including spaces).

Time ZoneDifference

Enter the Universal Time Coordinate (UTC) offset inminutes. This is the difference in minutes between your local time and Greenwich Mean Time.

• 300 means you are 300 minutes (5 hours) ahead of Greenwich Mean Time.

• -300 means you are 300 minutes (5 hours) behindGreenwich Mean Time.

The following are UTC offsets for the Continental United

States:• Eastern Standard Time (EST) -300

• Central Standard Time (CST) -360

• Rocky Mountain Standard Time (RMT) -420

• Pacific Standard Time (PST) -480

Default Folder All child objects of this network will be stored in the folder you select.

Note: If you do not designate a default folder for a newNetwork object, and you select Put object in folder when you created the Network object, all its childobjects will default to their respective class foldersunder the Root.

Click the browse button to display the Browse dialog.Select the folder that you want to hold the child objects for this network object, and, click the Select button.

Controller toCyberStationDBsync

Check this checkbox if you want changes made to thecontroller outside of CyberStation, such as through acommand terminal connection to the controller, to besynchronized with the CyberStation database. If a reload of the controller occurs, a flag appears on the controller iconin Continuum Explorer, indicating that a save to databasemust be performed.

5. Click the Alarms tab.




6. You can attach up to eight alarms to the network object. You may also attach agraphic panel and a report or other program to the object.

7. Click the corresponding browse button to select the AlarmEnrollment object, graphic,or program you want to attach.

8. If you selected AlarmEnrollment objects, click the Enabled checkbox next to the fieldto enable the alarm.

9. If you want to attach a SecurityLevel object to this network object, select theSecurityLevel tab and select a SecurityLevel object.

10. For details in attaching or detaching Security Levels, refer to Chapter 4.

11. Click OK.

Assigning a Network Object to a Default Folder

After you create a Network object, you need to create a link between that Network objectand its owner (folder). When you copy objects in Folder View, they are stored on thedesignated default device in Network View. When you create objects from a template inVirtual View (Folder or Template) and drop them on a parent folder, the objects arecreated in Network View (Network or Controller) on the assigned default device of thatfolder.

1. Select the default folder of the Network object, right-click the folder, and then select

Edit from the popup menu.

2. In the editor for the default folder, browse for the Default Device, the Network objectyou just created.

3. Select the Network object, and click the Select button. Click OK.



TAC 106




Configuring

Controllers

CyberStation allows you to create and configure controllers from a CyberStationworkstation. You do this by creating a new controller object and then using a controller editor to configure the controller. There is a separate editor for each type of controller:

• InfinityController (for CXxxxx, NetController, NetController II, bCX1 96xx, bCX1 40x0,or b4920)

• InfinityInfinet controller (for TCXxxx, i2xxx, or b3xxx)

Refer to Chapter 1 for a description of these controllers.

Network Secure Communication

TAC has a local network security policy that secures communication between certain Andover Continuum controllers and workstation. This secure communication ensuresauthentication, integrity, and encryption of IP data packets, using the Internet ProtocolSecurity (IPS) and the Internet Key Exchange (IKE).

Network security is a separately purchased option that is supported on the NetController II model 9680 and in the ACX controller models 5720 and 5740. For more information,please see Establishing Network Security for a Controller later in this chapter, and theNetwork Security Configuration Guide, 30-3001-996.

Andover Continuum’s Wireless ControllersCertain models of the Infinity controller series can also become parent wireless controller for an Active Continuum wireless mesh network.

• NetController II (model CX9680 or CX9681) configured with its wireless Infinet fieldcontrollers

• bCX1 9640 controller configured with its wireless Infinet field controllers

• bCX1 40x0 controller configured with its wireless BACnet b3 MS/TP field controllers.

Note: As a future enhancement, ACX 57xx series controllers will support Wirelesscommunication, much like the NetController II models 9680/9681.

See also the Andover Continuum Wireless Mesh Network Concepts and Best Practices Guide, 30-3001-912, the NetController II Operation and Technical Reference Guide, 30-

7



TAC 108

3001-995, the ACK 57xx Series Controller Operation and Technical Reference Guide,30-3001-999, and the bCX1 Series Controller Technical Reference Guide, 30-3001-890.

Note: In order to make one of these controllers a wireless controller, you must designateone of its comm ports as Wireless to establish wireless communication with thewireless mesh network.

Note: Andover Continuum BACnet-compliant controllers are included in the Andover Continuum product line. These are the bCX1 (40x0), b4920 and the b3xxx seriescontrollers. The b4 is created as an InfinityController object, and the b3 is created

as an InfinityInfinetCtlr object. Depending on which Continuum Explorer view youselect, b4 and b3 controllers may also be viewed as BACnet Device objects in theBACnet Devices portion of Explorer’s navigation pane, while also being viewed asInfinityController and InfinityInfinetCtlr objects in the Infinity portion of thenavigation pane. (Please refer to Chapter 14 for more information on BACnet andBACnet devices.)

Andover Continuum also supports third-party BACnet devices that are integrated into the Andover Continuum system.

By default, communication with Andover Continuum BACnet controllers is enabled onyour system. If you have no BACnet devices, or if you do not want exposure to BACnetclass objects, you may want to disable system communication with BACnet, wherebyCyberStation no longer sends or responds to BACnet communication requests. In this

case, only Infinity and InfinityInfinetCtlr controller objects are visible in ContinuumExplorer. For more information, please see Chapter 14.

All InfinityControllers, including b4 controllers, must be commissioned before they cancommunicate with CyberStation. bCX1 device commissioning is described in the bCX1Controller Technical Reference, 30-3001-890.

Once an InfinityController has been commissioned, a network controller object can becreated to represent it on the network.

Commissioning a Controller

In order for CyberStation to communicate with an Ethernet-level controller, you or your administrator must connect to the controller and enter its network address and other

identification information. This process is called controller commissioning . You cancommission most Andover Continuum controllers by accessing and entering informationon their embedded web pages. Some older controllers, such as the previous-generationNetController, require you to connect to the controller using a command terminalemulator, such as HyperTerminal. For more information, please see the manual for your controller:

• NetController II (968x series) – NetController II Operation and Technical ReferenceGuide, 30-3001-995, and its embedded web page online help.

• NetController (older generation – 990x, 994x, 920x series) – NetController TechnicalReference Guide, 30-3001-703

• ACX 57xx series – ACX 57xx Series Controller Operation and Technical ReferenceGuide, 30-3001-999




• bCX1 series (9640, 40xx) – bCX1 Series Controller Technical Reference Guide, 30-3001-890

• BACnet b4920 – b3 and b4920 Controller Technical Reference Guide, 30-3001-862

• CX 9702 – Commissioning information is detailed on the controller’s faceplate. (A9702 manual will be released as a future enhancement.)

Creating an InfinityController Object

Note: Before performing this procedure, you must commission the controller as described

in its product documentation.

To create an InfinityController object:

1. In Continuum Explorer, right click the Network object that will contain the newcontroller, select New, and then select InfinityController.

2. In the New dialog, enter a name for the controller in the Object name field, and clickthe Create button.

3. Refer to the following pages to enter information about this controller in the tabs of the InfintyControler editor, and click Apply to save your entries.

4. After you save the controller information, refer to “Teaching Network Controller” later in this chapter to exchange information about this controller in the network.

General Tab – InfinityController Editor Note: In CyberStation 1.8 or higher, you may be replacing your NetController (models

990x, 994x, 920x) with a newer NetController II model (model 9680 or 9681). If so,please so Guidelines for Converting a NetController to a NetController II later inthis chapter.

You begin configuring the InfinityController by entering information on theInfinityController’s General tab.

Note: Depending on the controller type, some editor attributes are not selectable. If anattribute is gray and is not selectable, it is not relevant to the type of controller youare creating.

Note: The InfintyController editor does not have a Backup to Flash button, which isused for NetController II controllers, ACX 57xx controllers, and bCX1 controllers.Instead, in Continuum Explorer, you can right click on the controller and selectBackup to Flash from the container popup menu.

Description Enter up to 32 characters of text to describe the physicalcharacteristics or functionality of the controller.

ACCNet ID Identifies each controller by a unique number between 1 and 190for the network. This number is set at the controller duringcommissioning.



TAC 110

Controller Type Select the controller model number from the dropdown menu. Andover Continuum BACnet-compliant controllers are designatedas bCX1 (40x0) or b4920. (See also the subsection, Creating an Andover Continuum bCX1 (b40x0) or b4920 Controller , later in thischapter.)

NetController II controllers are designated as 9680 and 9681. Older NetControllers are designated as 990x, 994x, and 920x. Selectionsfor 572x and 574x are ACX series controllers.

Comm Status CyberStation sets the comm status to OnLine or OffLine dependingon whether the workstation is in communication with the controller.

Out of Service Check this checkbox if you need to place the controller in an out-of-service (disabled) state. This creates a return-to-normal failurealarm on all CyberStations with the associated AlarmEnrollmenteditor’s Alarmed Attribute value set to OutOfService (see Using the AlarmEnrollment Editor in Chapter 10). It also allows the user toclear unwanted failure alarms from the alarm viewer and preventsany further failure alarms being reported from the controller. Also,personnel distribution cannot occur on the controller or itsassociated Infinet controllers.

Daylight Savings Check this checkbox if daylight savings time is in effect.

Network Security Check this checkbox to activate the TAC network security policy for this controller.

Note: Network security is supported only in the NetController IImodel 9680 and in the ACX controller models 5720 and5740.

The TAC network security policy is a local security policy,established and enabled through CyberStation, through theNetwork Security Configuration web page and other web pagesembedded in the controller, and through your Windows Administrative Tools. Network security secures communicationbetween the controller and a workstation using the Internet Security

Protocol (IPS) and the Internet Key Exchange (IKE). It ensuresauthentication, integrity, and encryptions of IP data packets.

For more information on how to implement network security inCyberStation, please see Establishing Network Security for aController later in this chapter. For complete instructions onconfiguring network security on the controller and in Windows,please see the Andover Continuum Network Security ConfigurationGuide, 30-3001-996.




Probe Time Enter the interval in seconds by which the Infinity controller checksthe comm status of its other connected CX series controllers andCyberStations. When the Infinity controller does not receive aresponse from another CX controller or CyberStation within theprobe time, it changes their comm status to Offline.

IOU Models Displays a list of IOU module connected to a CX9400 Controller.Not applicable to any other controllers.

UTC Offset Enter the Universal Time Coordinate (UTC) offset in minutes. Thisis the difference in minutes between your local time and GreenwichMean Time (GMT):

• 300 means you are 300 minutes, or 5 hours ahead of GMT.

• -300 means you are 300 minutes or 5 hours behind GMT.

BACnet Device Id Identifies the bCX1 (40x0) or b4920 BACnet controller by a uniqueinteger. Each controller must have a unique ID.

BacMaxMaster The Max Master property, which is of type Unsigned , is present if the device is a master node on a BACnet MSTP network. Enter aninteger in this field that equals the exact number of b3 and third-party BACnet controllers connected to this device. It must be lessthan or equal to 127 (the default).

Location Enter the location of the controller (optional).

Serial Number CyberStation retrieves the controller’s serial number from thehardware.

Network ID - UPD This integer displays the ID number of the BACnet/IP and EthernetTCP/IP network on which the controller resides.

Version CyberStation retrieves the controller’s version number from thehardware.

Network ID –Comm2

This integer displays the ID number of the BACnet Master-Slave/Token Passing (MS/TP) or Wireless network on which thebCX1 (40x0) or b4920 controller resides.

Default Folder Browse to select the folder where the child objects of this controller

will be stored (optional).Update OS You can upgrade the Infinity controller’s operating system by

clicking the Update OS button. You can then locate and select anupdate (.upd) file and click OK to load the new operating system tothe controller.



TAC 112

Update IOUs If you have loaded IOU module firmware updates received fromTAC, use the Update IOUs button to update the modules. Click theUpdate IOUs button. You can then locate and select an (.IOU) fileand click OK to update the IOU modules currently connected to thiscontroller.

Note: Make sure you select the .IOU file for the type of controller you want to update. Each .IOU file updates a single model of IOU module.

Update BACnetb3 OS

Click the Update BACnet b3 OS button to upgrade the operatingsystem of the Infinity Infinet BACnet b3 controllers currentlyconnected to this Infinity controller. When you click this button, anOpen dialog appears. This dialog helps you locate the update file(shipped with CyberStation) to send to the b3 controllers. Searchfor and select the file, and then click OK. The new operating systemis automatically downloaded to the controllers. There’s no need toreplace the microchip.

If you are creating or modifying an Infinity 9xxx controller, thisbutton changes to: Update Infinet 2 OS. (See below.)




Update Infinet 2OS

Click the Update Infinet 2 OS button to upgrade the operatingsystem of the Infinity Infinet 2 controllers currently connected to thisInfinity controller. The upgrade procedure is identical to that for a b3controller (described above).

When you click this button, an Open dialog appears. This dialoghelps you locate the update file (shipped with CyberStation) to sendto the Infinet 2 controllers. Search for and select the file, and thenclick OK. The new operating system is automatically loaded to thecontroller. There’s no need to replace the microchip.

Note: If this parent controller is a NetController II (modelCX9680/CX9681) and one comm port is configured for Infinetwhile another is configured for Wireless, be sure your updatefile matches the active medium (in this case, Infinet) of thecomm port to which the i2 controllers are attached. If it doesnot match, a warning message appears, telling you there is amismatch and asking you if you want to continue. If youcontinue with this mismatch, another message appears:

Upon successful update, all controllers that

participated in the update will now be

operating in Wireless mode. These controllers

will be offline until the selected comm port

mode is changed, the controller is connected by

proper medium, and the parent controller is

reloaded…Continue with update?

See also the description for the Wireless Update I2 OS button,below.

Wireless on ACX 57xx Series Controllers – As a futureenhancement, ACX 57xx series controllers will support Wirelesscommunication much like the NetController II 9680/9681.

When you are creating or modifying a BACnet bCX1 40x0 or b4920controller, this button changes to: Update BACnet b3 OS. (Seeabove.)



TAC 114

Update WirelessI2 OS

Click the Update Wireless i2 OS button to upgrade the operatingsystem of Infinity Infinet 2 (i2) controllers affixed with Wireless Adapters in a wireless mesh network and connected to this parentwireless Infinity controller.

Wireless on ACX 57xx Series Controllers – As a futureenhancement, ACX 57xx series controllers will support Wirelesscommunication much like the NetController II 9680/9681.

Note: The Update Wireless I2 OS button appears only when this

Infinet controller is a NetController II (CX9680/CX9681) andwhen its comm ports are configured in one of these ways:

• Comm1 is configured as Infinet and Comm2 is configuredas Wireless

OR

• Comm1 is configured as Wireless and Comm2 isconfigured as Infinet.

When you click this button, an Open dialog appears. This dialoghelps you locate the wireless-controller update file (shipped withCyberStation) to send to the wireless Infinet 2 controllers. Searchfor and select the file, then click OK. The new operating system isautomatically loaded to the controllers. There’s no need to replacethe microchip.

Note: Be sure your update file matches the active medium (in thiscase, Wireless) of the comm port to which the i2 controllersare attached. If it does not match, a warning messageappears, telling you there is a mismatch and asking you if youwant to continue. If you continue with this mismatch, another message appears:

Upon successful update, all controllers that

participated in the update will now be operating

in Infinet mode. These controllers will be offline

until the selected comm port mode is changed, the

controller is connected by proper medium, and the

parent controller is reloaded…Continue withupdate?

Reset Click the Reset button when you need to delete all programs andpoints stored on the controller. Use the Reset button with caution,and only after you have saved the programs and points to theCyberStation database. When you click the Reset button, a dialogappears and asks you if you want to continue. If you click OK, youwill not be able to retrieve the deleted programs and points exceptby reloading them from the CyberStation database.

Teach See “Teaching Network Controllers” later in this chapter for information about this button.




Network Tab - InfinityController Editor

Enter the following information on the InfinityController Network tab.

Note: Depending on the controller type, some editor attributes are not selectable. If anattribute is gray and is not selectable, it is not relevant to the type of controller youare creating.

TransportType

From the dropdown menu, select the type of network protocol throughwhich the controller communicates with workstations and other Ethernet-level controllers.

Selections are TCP, UPD, or TCP and UPD.

TCP stands for Transmission Control Protocol. TCP uses a connection-oriented byte stream and guarantees data delivery. TCP is used bynetwork applications that require guaranteed delivery and that cannotbe hampered by time-outs and retransmissions. TCP requires moreCPU and network bandwidth than UDP.

UDP stands for User Datagram Protocol. Many application protocolsuse UDP: for example, Network File System (NFS), Simple NetworkManagement Protocol (SNMP), and BACnet. UDP, which is aconnectionless datagram delivery service, does not maintain an end-to-end connection with the remote UDP module. UDP does not guaranteedelivery, whereas TCP does.

Ethernet ID The Ethernet ID number for the controller is assigned to the controller atthe factory. This number is retrieved from the controller.

IP Address,Subnet Mask,PPP IPAddress, andDefaultRouter

Enter the IP address, Subnet Mask, PPP IP address if using remoteaccess communications, and Default Router numbers provided by your network administrator. If you are operating a standalone system, besure that the Subnet Mask numbers on the workstation and controller match.

MaxResponseTime

This number is the number of seconds the controller will wait beforeresending a packet of information. In most situations, the default valueof 5 seconds is sufficient. You may want to increase the number of

seconds in the following situations:

• If your network nodes are far apart

• If the connection between nodes exhibits a slow transmission rate.

It is recommended that only your network administrator change thenumber of seconds.

Home Page This is the Plain English function path of this controller’s web page.This path is used by the web.Client application. When a user clicks acontroller, via the web.Client Web Pages feature, web.Client accessesthis path, and displays the appropriate web page in the browser. For example:

http://Andover/PE/WebSetSampl



TAC 116

Controller toCyberStationDBsync

Check this checkbox if you want changes made to the controller outsideof CyberStation, such as through a command terminal connection to thecontroller, to be synchronized with the CyberStation database. If areload of the controller occurs, a flag appears on the controller icon inContinuum Explorer, indicating that a save to database must bepreformed.

Options Tab – InfinityController Editor

In Options tab of the InfinityController editor. you can review the hardware optionsinstalled in the controller. This tab also lists the XDriver settings for each comm port, aswell as whether or not the TAC network security policy is enabled for a NetController II9680 or an ACX 57x0 controller. This tab displays read-only information.

X Driver X drivers can be enabled or disabled on each comm port. A value of 0000 means disabled. A value of 0001 means enabled. All other valuesin the 4-digit hex number shown for each comm port are X Driver-specific bits set at the factory.

Max InfinetControllers

The total number of controllers that can be attached to this controller.

LAN Indicates whether or not the LAN card is installed.




LON Indicates whether or not a 9900, 9400 or 9410 controller has a LON XDriver card installed.

Modem Indicates whether or not the controller has an installed modem.

PCB Revision The revision number of the controller's printed circuit board. Thisinformation may be requested by TAC Technical Services Department if you are calling in with a problem related to this controller.

Web Server Indicates whether or not the Web Server feature of the controller isturned on.

SNMP Indicates whether the advanced Simple Network Management Protocolis enabled. For more detailed information about SNMP, refer toContinuum SNMP Alarming MiniGuide (30-3001-855).

ACC_LON I/O Indicates whether the ACC_LON I/O has been selected.

L-BUS I/O In this example, indicates that ACC_LON I/O is disabled and L-BUS I/Ois enabled.

HCR Hardware Configuration Resource. Displays the current revision level of the hardware.

AreaLockdown

Displays whether or not the Area Lockdown feature is Enabled or Disabled.

ConditionLevel

Displays whether or not the Condition Level feature is Enabled or disabled.

Bootloader Version

Displays the version of the controller’s bootloader, represented by itsbootloader UPD file that you received from TAC.

NetworkSecurity

Indicates whether or not this controller may be configured for networksecurity, which is a separately purchased option from TAC.

If the entry says Enabled, it means your site has purchased this option.If it says Disabled, it means your site has not purchased this option.

Note: Only the NetController II model 9860, as well as the ACXcontroller models 5720 and 5740, can support Network Security.

For more information on network security, please see Establishing Network Security for a Controller later in this chapter.

SecurityLevel Tab – InfinityController Editor

For details in attaching or detaching Security Levels, see Chapter 4, Security .



TAC 118

Teaching Network Controllers

After you finish configuring the network controller, click Apply to save the information youhave entered into the fields of the InfinityController editor.

Network controllers need CyberStation information in order to send alarms and events tothose CyberStation workstations. They must also have network controller information if they reference points in other network controllers (for example, in Plain Englishprograms). Network controllers are organized into networks. The network controllers ineach network should know about each other, but they should not know about anynetwork controllers outside their network. To exchange this information, you use theTeach button in the InfinityController editor.

You click the Teach button when you add new network controllers or CyberStationworkstations to the system. It is automatically invoked when a network controller or CyberStation is deleted, and when a network controller is modified.

Note: During a teach, a controller queries through the system Ethernet network askingfor and receiving the IP addresses of up to 64 CyberStation workstations. Thecontroller can only be taught about workstations with a network ID number in therange of 191-254. Workstations with network IDs outside this range cannot betaught.

When you click the Teach button, a Select Teach Mode dialog appears containing the

following teach mode selections. Click the appropriate Teach Mode radio button andthen click OK.

Mode Description

InfinityController Teach

Teaches other network controllers in this network about this networkcontroller. It also teaches the network controller about all other network controllers on its Network and all the CyberStationworkstations in the system.

Network Teach Teaches all network controllers in a Network about all other netcontrollers is the same Network. It also teaches the networkcontrollers about all CyberStation workstations in the system.

Global Teach When there are multiple networks, choosing this teach mode has thesame effect as executing a Network Teach on each Network.

Establishing Network Security for a Controller

TAC’s network security policy is a local security policy that secures communicationbetween the controller and a workstation. You establish network security on an Andover Continuum system through CyberStation, through the Network Security Configuration web page embedded in the controller, and through you Windows Administrative Tools.

Note: Network security is supported only the NetController II model 9680 and in the ACXcontroller models 5720 and 5740. On Andover Continuum controller, networksecurity is not enabled by default, your site must purchase it as a separately soldoption from TAC.




For communication in an Andover Continuum system, network security ensuresauthentication, integrity, and encryption of IP data packets, using the Internet ProtocolSystem (IPS) and the Internet Key Exchange (IKE).

Main Configuration Tasks

Establishing network security involved the following four major configuration tasks.

Task Description Where It Is Configured

1: Determine if network security isenabled for thiscontroller.

Determines whether or not your site has purchased the networksecurity option for thisNetController II 9860 or ACX57x0.

CyberStation –InfinityController editor,Options tab

2: Configurenetwork securityon the controller

Configured network securitysettings inside the controller.

Web-page dialogsembedded in theNetController II 9860 or the ACX 57x0

3: Configurenetwork securityon the workstation

Imports, edits, assigns, andexports the local TAC networksecurity policy on the workstation.

Windows Control Panel – Administrative Tools –Local Security Settings

4: Activate

network securityfor the controller

Sets the Network Security

attributes for an existing controller or a new controller.

CyberStation –

InfinityController editor,General tab

Configuring Network Security

Perform the following procedure to establish network security.

For complete, in-depth instructions on configuring network security, please see the Andover Continuum Network Security Configuration Guide, 30-3001-996, theNetController II Operation and Technical Reference Guide, 30-3001-995, and the ACX 57xx Series Controller Operation and Technical Reference Guide, 30-3001-999.

1. Edit the online controller (bring up the InfinityController object editor) on which youwant to enable network security.

2. Select the Options tab of the InfinityController editor.If the Network Security entry says Enabled, it means your site has purchased thenetwork security option for your 9680 or 57x0 controller. Go to step 6.

If the entry says Disabled, it means your site has not purchased the network securityoption for your 9680 or 57x0 controller. In this case, go to the next step.

3. Purchase the network security option from TAC for this controller. In turn, TAC sendsyour site a UPD file.

4. On the General tab, click the Update OS button and load the appropriate UPD file toenable the network security option for this controller.

5. When the update is complete, verify that the controller has returned online. Go backto Option tab, and verify that the Network Security entry now says Enabled.



TAC 120

6. Access and configure the controller for your preferred security. To do so, you mustaccess and log in to the controller’s main embedded web configuration page, thennavigate to the Network Security Configuration embedded web page.

Note: For complete instructions on configuring network security, please see the Andover Continuum Network Security Configuration Guide, 30-3001-996, theNetController II Operation and Technical Reference Guide, 30-3001-995, andthe ACX 57xx Series Controller Operation and Technical Reference Guide, 30-3001-999.

7. If you have not imported the IPSec security policy, do so now. if you already have, goto the next step.

From the Windows Control Panel, open Administrative Tools, then Local SecurityPolicy, which launches the Local Security Policy dialog.

Note: For complete instructions, see the Andover Continuum Network Security Configuration Guide, 30-3001-996.

8. Edit the imported security policy. You do this via the Control Panel and the TACEncrypt and Authenticate dialog.


9. If necessary export the edited security policy to other workstation. This allows the useof the modified policy on other workstations without having to edit it on eachworkstation. You do this from the Launch Security Settings dialog.


10. Activate network security in an existing controller or on a new controller that you arecreating.

For an existing controller, enter CyberStation offline editing mode.

On the General tab of the InfinityController editor, check the Network Security checkbox.

11. Click Apply.

12. Enter online editing mode.

13. Verify that the controller is online.

14. From the General tab, click the Teach button to update the network.

Guidelines for Converting NetController to NetController II

CyberStation supports the conversion of a previous-general NetController (CX9680 andCX9681). A procedure over viewing this conversion follows.

1. Back up your SQL Server database. See the Andover Continuum CyberStationInstallation Guide, 30-3001-720, and Microsoft’s SQL Server documentation.




2. From Continuum Explorer, right click the controller, and select Send To Text Files.This dumps the controller object’s data into a text file.

3. Update your workstation with a version of CyberStation that supports the newer NetController models. (These models are supported in CyberStation Version 1.8 andhigher.) See the Andover Continuum CyberStation Installation Guide, 30-3001-720.

4. Physically remove the old NetController, and mount/connect your NetController II.

When you configure and commission the NetController II, use the same controller name, network IP address, and neting ID. This is performed via the controller’s

embedded web commissioning pages, via the General tab, and via the Network tab.

See the Andover Continuum NetController II Operation and Technical ReferenceGuide, 30-3001-995, and the Andover Continuum NetController II InstallationInstructions, 30-3001-994.

5. Switch to CyberStation offline editing mode (if you are not already there) in theInfinityController editor.

6. On the General tab, from the Controller Type dropdown menu, change the modelnumber to 9680 or 9681, depending on which NetController II you are installing.

7. Make sure you actually want to replace the NetController.

When you attempt to change the controller model, CyberStation displays a fewwarning messages:

• CyberStation warns that a model change is irreversible.

• CyberStation warns that, if an XDriver is used with this controller, not all XDriversare supported by the new model. This warning only occurs if an XDriver is loadedand enabled.

If you proceed, the XDriver links are left in place regardless of the availability of areplacement XDriver.

XDrivers on NetController II – In general, XDrivers that are available on the bCX1model 9640 are also supported on the NetController II.

For example, supported NetController II XDrivers include, but are not limited to, thefollowing:

•

Filter • XdTest

• Modbus TCP

• Modbus RTU

Note: XDrivers built for the previous-generation NetController will not run on theNetController II

What is an XDriver? An XDriver is special, customized software that your sitepurchases separately from TAC. This XDriver software allows your controller toconnect to and communicate with a special piece of third-party equipment needed atyour site. In the CommPort editor, you must configure a controller comm port for thisspecial device that the XDriver software enables.



TAC 122

When you leave the InfinityController editor, go back to online editing mode.

8. If necessary, provide an updated XDriver file compatible with your NetController II.CyberStation prompts you to do this.

Note: You can specify an XDriver on the General tab of the CommPort editor.Specify XDriver for the Default Mode, and use the browse button in theXDriver File Name field to search for and specifiy the path of the XDriver. See,Configuring Settings for an XDriver , later in this chapter.

9. Determine whether this NetController II has network security. If so, configure networksecurity for this controller. See, Establishing Network Security for a Controller , earlier in this chapter.

Note: Network Security is supported online in NetController II model 9680, as well as ACX controllers 5720 and 5740.

10. Restore (reload) data from your database into the new controller. From ContinuumExplorer, use the Object dropdown menu, or right click the controller and select Sentto Controller .

11. Back up to flash. In Continuum Explorer, right click the controller, and from thecontainer popup menu, select Backup to Flash. This saves the controller’s RAMconfiguration to its flash memory.

Creating a bCX1 (40x0) or b4920 Controller

Create a BACnet-compliant controller as an InfinityController, as follows:

1. In Continuum Explorer, right click a Network object, and select New from the popupmenu, and then select InfinityController .

2. In the New dialog, enter the name and alias of the new controller, and click theCreate button.

3. In the General tab, select b40x0 or b4920 from the Controller Type dropdownmenu.

4. Configure the BACnet attributes and other configuration attributes using the tabs of InfinityController editor.

See “Creating an InfinetController Object” earlier in this chapter for a description of each attribute and lock tab. See also Chapter 14 for more information on BACnetdevice operations.




Sending Controller Data to the CyberStation Database

If controller settings or data are changed outside of CyberStation (for example, through acommand terminal), you need to update the database with these changes. You do thisusing the send to database feature in Continuum Explorer.

1. Click the Options dropdown menu, and select Send To Database Options.

2. Select the appropriate radio button, and click OK. (See Chapter 3.)

3. In Continuum Explorer, right click the controller that was edited, select Send To, andthen select Database.

4. When prompted to confirm the operation, click OK to initiate the operation.

When the send to database is accomplished, you can click the Refresh icon to removethe exclamation flag next to the controller icon in Continuum Explorer.

Reloading a Controller from CyberStation

If a controller object is modified in CyberStation in the offline-editing mode, CyberStationcreates an event in the Activity Log and marks (with a flag) the object icon in the

Explorer. The flag presents a tool tip when the cursor is placed over it that indicatesthat the controller must be reloaded.

You can reload the controller with the Send To Controller operation.

1. In Continuum Explorer, open the Options dropdown menu, and select Send toController Options.



TAC 124

2. Select the appropriate radio button, and click OK.

3. In Continuum Explorer, right click the controller you want to update, select Send To,and then select Controller .

4. When prompted to confirm the operation, click OK to initiate the operation.

When the send to controller is accomplished, you can click the Refresh icon to removethe exclamation flag next to the controller icon.

Turning Off DB Sync

Note: Disabling these attributes should be restricted to the facility's system administrator.

Setting the value of the NetController and network Database Synchronization attributes toFALSE will disable the db sync message and prevent the warning flags from appearing inContinuum Explorer.

An event is created in the Activity Log each time CyberStation receives a db syncmessage as a result of a controller change.

Working With Infinet Controllers

Infinet controllers communicate with Infinity controllers through the Infinet network. Thesesubcontrollers, attached to Infinet networks, contain the various input and output pointsneeded to control building systems such as fans, boilers, chillers, and other electro-mechanical units.

Note: Andover Continuum provides a b3 series of BACnet controllers. Refer to Chapter 14 for a description of these controllers.

About Infinet 2 Controllers

Infinet 2 (i2) controllers store all user-created objects (points, programs, and so on) innon-volatile flash memory. All Infinet 2 controllers contain EPROM flash memory thatcan be upgraded electronically.

The Infinet 2 flash memory has two separate areas:




• A user backup area

• A warm start area

The user backup area is used to store a copy of the controller's original RAM database.The warm start area is used as a temporary storage region that stores the configurationof the controller's database at the time a reset or power failure occurred. How the data inflash memory is used depends on the mode in which the Controller restarts after a power failure reset:

• Cold Start: The Infinet 2 controller comes up, from a reset, with no user objects or

configuration in place.• Cool Start: The Infinet 2 controller comes up, from a reset, and restores a user

configuration from flash memory (the user backup area) that was initially saved bythe user. Cool start can be thought of as a “self reload.”

• Warm Start: The Infinet 2 controller comes up, from a reset, and restores theconfiguration that was present in the controller when it was reset and/or power waslost (restored from the warm start area of flash memory).

For each Infinet 2 controller, you can specify which restart mode to use as described in“Setting the ACCRestartMode Attribute” later in this chapter.

Flash Backup Notification

Andover Continuum provides a safeguard to ensure that you are aware of the need tobackup an Infinet 2 controller. This is true for the WarmToCool and CoolStartOnly modes.It does not apply to the WarmStartOnly mode.

When an Infinet 2 controller needs a backup, a flag in the form of an exclamation point

will appear over the controller's icon in Continuum Explorer. The flag presents a tooltip when you place the cursor over it.

To backup the controller you edit the controller and click the Backup to Flash button onthe InfinityInfinetCtlr General tab. (See next page for details.)

Creating an Infinity Infinet Controller Object

The usual method for configuring Infinet controllers into the system is known as “learning”them into the system. The “learning” procedure is as follows:

1. In Continuum Explorer, click the Explorer bar icon , and select the Networksview.

2. Select the InfinityController to which the Infinet controller is attached.

3. Click the + in the navigation pane to expand the icons beneath the InfinityController.

4. Open the CommPort object that corresponds to the communication port attached tothe Infinet controller.



TAC 126

The CommPort editor appears.

5. In the CommPort editor Settings tab, click the Learn button. This sends informationto the InfinityController about the Infinet controllers on the network connected to thiscommunication port. When the learn process completes, you can see the controllerson the Field Bus Controllers tab of the editor. (For more information, seeChapter 8.)

6. Click OK.

7. Refresh the Explorer by selecting Refresh from the View dropdown menu or theExplorer’s refresh button.

The new Infinet controller is now shown. You can now open the controller if you want toview or edit its attributes. See “Editing an Infinet Controller Object” later in this chapter.

Creating an Infinet Controller Offline

It is possible (but not recommended) for you to create Infinet controllers offline, using thefollowing procedure:

1. In Continuum Explorer, click the Explorer bar icon and select the Networks view.

2. In the Networks view, right click the InfinityController object under which you are

adding the Infinet controller, select New, and then InfinityInfinetCtlr .3. Name your controller in the Object name field.

4. Remove the check from the Put object in folder checkbox.


Enter the controller attributes, and click OK to save the controller object.

Editing an Infinet Controller Object

1. In Continuum Explorer, right click the controller you want to edit, and select Edit.

2. Refer to the following pages to enter information in the tabs of theInfinityInfinetController editor.

General Tab – InfintyInfinet Editor

In the General tab, you view and enter information that describes the controller and itslocation, and to which Infinity comm port it is connected.

Description Enter up to 32 characters of text that describes the physicalcharacteristics or functionality of the device.

Location Enter up to 32 characters of text that describes the location of thedevice.




Model Select the Infinet controller's model number from the dropdown menu.

Note: When you select a BACnet-compliant b36xx, b38xx, or b39xxcontroller, you are creating an Andover Continuum BACnet-compliant Device object, in addition to an InfinityInfinetCtlr object. To configure BACnet analog, binary, and multistateinputs, outputs, and values for this new BACnet device, youmust first create them as Infinity Input, Infinity Output, andInfinity Numeric points. A b3 controller must be reside on a b4controller. Otherwise the b3 controller selections will not be

available in the Model dropdown menu. (See also thesubsection, Creating an Andover Continuum b3 Controller , later in this chapter.)

CommPort Browse to locate the comm port to which this Infinet controller isconnected.

Infinet Id Enter an ID number for this controller if you are creating this controller offline. Normally, you let CyberStation assign one for you by clickingthe Learn button from the Comm Port editor (Chapter 8). This isknown as an “Infinet Learn.” An Infinet Learn checks for new Infinetcontrollers. If it finds one without an ID number, it assigns a number. If it finds an Infinet controller with an ID number that has been manuallyentered, it learns that number. You need to perform an Infinet Learn

only if your are adding a new Infinet controller. Do not do an InfinetLearn if you are replacing an existing controller.

BACnetDevice Id

Identifies the b3 BACnet controller by a unique integer. Each controller must have a unique ID.

Default Folder (Optional)

Click the browse button to select the default folder for this controller.

Status CyberStation displays either Online or Offline, depending on whether or not the Infinet controller is in communication with its attached Infinitycontroller.

Backup toFlash

Click this button to save the configuration to its flash memory inaccordance with the attribute value that is set for the ACCRestartMode

system variable.

UpdateINfinet2 OS

Click this button to upgrade the Infinet 2 controller’s operating system.You need to locate and select an update (.upd) file to sent o the Infinet2 controller to update its operating system.

Update b3 OS(replacesabove buttonfor BACnetcontrollers)

Click the button to upgrade the BACnet b3 controller’s operatingsystem. (See Chapter 14.) You need to locate and select an update(.upd) file to send to the BACnet b3 controller to update its operationsystem.



TAC 128

Runtime Tab – InfinityInfinetCtlr Editor

In the Runtime tab, you can:

• View information about the controller during runtime.

• Find the controller’s serial and version numbers, as well as information about anyerrors that may have occurred.

With the exception of Serial #, all of the information on this tab is read-only. In the caseof the Serial #, if for some reason the controller had to be replaced, you would enter thenew number in the Serial # field.

Serial # Displays the serial number that is filled in when you click the Learn button from the CommPort editor.

Version # Displays the version number that is filled in when you click the Learn button from the CommPort editor.

Error # Displays the last error to occur on the controller.

Error Time Displays the time and date that the last error occurred on the controller.

Error Count Displays the number of errors that have occurred on the controllerssince it was last set to zero. Totals up to 255 errors and remains set at255 until it is reset to zero. Use a Plain English program to reset thisattribute.




Reconfigs Displays the number of times the network has been reconfigured. Thenetwork automatically reconfigures itself when it detects acommunication error. If a high number of errors and a high number of reconfigs occur, your network may have a loose connection somewherethat is causing the communication error.

Reset The Reset button clears the controller’s memory.

Security Level Tab – InfinityInfinetCtlr Editor

For details in attaching or detaching Security Levels, see Chapter 4, Security.Setting the ACCRestartMode Attribute

To specify the restart mode to use, you must set the value of the Infinet 2 system variableACCRestartMode.

1. In the InfinitySystemVariable folder of the Infinet 2 controller, double click ACCRestartMode.

2. In the InfinitySystemVariable editor, enter the value that corresponds to the restartmode you want to use:

Enter this value… To use…

ACCWarmStartOnly The warm start area of the controller flash memory. Thesystem attempts automatically to restore the Infinet 2

controller’s RAM to the state it was in at the time of the resetor power failure. With this setting, the ACCStatusBackup isset to ACCBackupInactive.

ACCCoolStartOnly The user backup area of the controller flash memory. Theflash backup notification flag (see next page) appears in theExplorer tree when a change or reload occurs to RAM andyou must initiate the action by activating the Backup to Flash button which causes the controller’s RAN to be restored fromthe user backup flash area.

ACCWarmtoCool The flash notification flag, which appears in the Explorer treewhen a change or reload occurs to RAM. You must initiatethe action by editing the controller and clicking the Backup to

Flash button. The controller will first attempt a warm start,and if that fails it will attempt a cool start. This is the systemdefault setting.

3. Enter a description (optional.)

4. Select Enabled in the State dropdown menu.

5. Click the Apply and OK buttons.

Creating an Andover Continuum b3 Controller

The most common and suggested method for creating a BACnet-compliant b3 controller is to open the comm port on the b4 device and perform a learn. Another way to create ab3 controller is:



TAC 130

1. In Continuum Explorer, right click an Infinity controller.

2. Select New and then select InfinityInfinetCtlr ..

3. In the New dialog, enter the name and alias of the new controller, and click theCreate button.

4. In the General tab, from the Model dropdown menu, select a b36xx, b38xx, or b39xxcontroller. When you select a b3 model, notice that the BACnet field, BACnet DeviceId, becomes selectable.

Note: You must create a b3 controller residing on a b4 controller. Otherwise, the b3model selections are not available.

5. Configure the BACnet fields and other configuration attributes, using theInfinityInfinetCtlr editor.

For more information on these configuration attributes, see the attribute descriptions in“Editing an Infinet Controller Object” earlier in this chapter. See also Chapter 14 for moreinformation on BACnet operations.




Configuring

Comm Ports

After a controller is defined its communication ports need to be configured for the devicesconnect to them.

Each Andover Continuum network controller includes provisions for adding other devices.The network controllers include up to four programmable communications interfacescalled comm ports and a dedicated interface for the Continuum IOU modules.

A comm port is an electrical interface used to connect the controller to an external devicesuch as a printer or a terminal. When you create a controller object, CyberStationautomatically creates appropriate comm port objects for each of the comm ports of thatcontroller. You use the CommPort editor to provide settings that enable the comm port towork with the device attached to it.

Supported Device Types

CyberStation supports the following types of devices. Not all comm ports support all of these devices. Make sure that the port you are configuring includes support for the deviceyou select.

Printers Printers are typically used to produce hard copy of lists and logs.These devices interface with controllers via an RS-232 serial

connection.

Infinet,MS/TP,Wireless

Andover Continuum controllers and other equipment thatcommunicates over a proprietary version of an RS-485 networkcalled Infinet, a standard BACnet version called the Master-Slave/Token-Passing (MS/TP) network, or a wireless network with aWireless Adapter affixed to a bCX1 90xx (Infinet) controller or bCX140x0 (BACnet) controller.

XDriver XDrivers are custom interfaces that have been designed to providean interface between the controller and another device generallymanufactured by another company.

8



TAC 132

TankNet TankNet is another version of RS-485 developed for communicationbetween controllers and certain tank-mounted liquid level sensors.

L-BUS LBUS is the cable that connects IOU modules to a CX networkcontroller. Only one LBUS can be connected to a CX controller. EachLBUS can have up to 16 IOU modules on it.

Configuring a Comm Port for a Terminal

Terminals can be connected to controllers two ways:• Directly to the controller using up to 50 feet of RS-232 cable

• Remotely to the controller using a modem

The table below shows the comm port settings to use for each controller when youconnect a command terminal.

Setting Description

Comm PortNumber andDefault Mode

You can use the settings indicated for each of the followingcontroller models:

• 9200/9300: Use AutoSet or Window on COMM1, COMM2,COMM#, and COMM4. On 9300 models, you can also useCommand on these ports. AutoSet is the default on

COMM3.

• 9400: Use AutoSet, Window, or Command on COMM1,COMM2, COMM3, or COMM4. AutoSet is the default modeon COMM3.

• 9924: Use AutoSet, Window, or Command on COMM1and COMM2. AutoSet is the default mode on COMM2.

• NetController: Use AutoSet, Window, or Command onCOMM1, COMM2, COMM3, or COMM4. AutoSet is thedefault mode on COMM3.

Baud Rate The default baud rate setting is 9600. All baud rates are valid,however if you are experiencing communication problems,check the baud rate requirement for your equipment and

choose the matching baud rate.

Flow Control CyberStation automatically uses XonXoff for terminals,regardless of which flow control type you select.

Terminal Type Click the terminal type that you are using. If you are running aterminal emulation program on a computer, select VT100.

TrackCXD This attribute is automatically selected. Deselect it only if your terminal is connected directly to the controller (not through amodem).

Direct Connect Select this attribute only if your terminal is not connected to thecontroller over a modem. This is required.




Configuring a Comm Port for a Printer

The table below shows the comm port settings to use for each controller when youconnect to a printer.

Setting Description



• 9200: Use COMM1, COMM2, COMM3, or COMM4. Select

Printer for Default Mode. • 9400: Use COMM1, COMM2, COMM3, or COMM4. Select

Printer for Default Mode.

• 9924: Use COMM1 or COMM2. Select Printer for DefaultMode.

• NetController: Use COMM1, COMM2, COMM3, or COMM4. Select Printer for Default Mode.

• bcx1 Series: Use COMM1 or COMM2.

Baud Rate Set the baud rate to match the baud rate of the serial printer you are using. If you are unsure of the printer’s baud rate, setthe comm port baud rate at the lowest setting, then try to print.If the baud rate is set too low, something will usually print, but it

may be unintelligible. Change the comm port’s baud rate tonext higher settings and print again. Continue this process untilthe printer works properly.

Flow Control Depending on the flow control type required by your printer,select either NoFlowControl, XonXoff, CtsRts, or XonXoffCtsRts.

TrackCXD This attribute does not apply to printers.

Configuring a CommPort for an LBus

You can set up a comm port for an Lbus to communicate with one or more IOU modules.Once you set a comm port’s default mode to LBus, you can’t change it without resettingthe controller, so be sure to plan ahead.

The table below shows which comm port you should use:

Setting Description



• 9200: Use COMM4. Select LBus for Default Printer.

• 9400: There are no LBus comm ports on the 9400 series.

• 9924: There are no LBus comm ports on the 9924 series.

• NetController: Use COMM1. Select LBus for Default Printer.



TAC 134

Baud Rate The default baud rate is 19.2K. All baud rates are valid. If you arehaving communication problems, check the baud rate requirementsfor your equipment, and then make the appropriate selection here.Set to a lower baud rate if you require greater noise immunity.

Flow Control Flow control does not apply to LBus connections.

TrackCXD This attributes does not apply to LBus connections.

Configuring a Comm Port for a TankNet

You can configure a TankNet port to use for communicating with a network of Infinity RS-485 level-sensing probe through this port. There is a maximum of one TankNet per controller.

You can use the RS-485 connectors on the following ports for TankNet:

Setting Description


You can use the settings indicated for each of the following controller models:

• 9200: You COMM1, COMM2, COMM3, or COMM4. SelectTankNet for Default Mode.

• 9400: Use COMM1, COMM2, COMM3, or COMM4. SelectTankNet for Default Mode.

• 9924: Use CustomPort. TankNet is the default mode..

• NetController: Use COMM1, COMM2, COMM3, or COMM4.Select TankNet for Default Mode.

Baud Rate The default baud rate, 4800, is the only setting allowed for TankNet.

Flow Control Flow control does not apply to TankNet connections.

TrackCXD This attribute does not apply to TankNet probes.

Configuring a Comm Port for XDrivers

You can configure a comm port to connect to special equipment. To do this, you will needto purchase Andover Continuum customized software called an XDriver.

The table below shows which comm ports are available for XDrivers for each controller.

Setting Description


You can use the settings indicated for each of the following controller models:

• 9200: Use COMM1, COMM2, COMM3, or COMM4. SelectXDriver for Default Mode.

• 9400: Use COMM1, COMM2, COMM3, or COMM4. SelectXDriver for Default Mode.

• 9924: Use COMM1 or COMM2. Select XDriver for Default Mode.

• NetController: Use COMM1, COMM2, COMM3, or COMM4.




Select XDriver for Default Mode.

• NetController II: Use COMM1, COMM2, COMM3, or COMM4.Select XDriver for Default Mode.

• bxc1 Series: Use COMM1 or COMM2.

• ACX 57xx series: Use COMM1. (The ACX57xx controller has onlyone configurable RS-485 comm port). Select XDriver for DefaultMode.

Baud Rate The appropriate baud rate may vary depending on the XDriver

software. Refer to the instructions provided with the software.Flow Control Flow control does not apply to XDrivers.

TrackCXD In most cases, TrackCXD should be selected. However, this may varydepending on the device. Check the documentation that came with theXDriver to be sure.

What Additional Settings Do I Need to Make?

When the default mode is set to XDriver, the Settings tab contains the attributes shownbelow:

Baud Rate Refer to the documentation provided with the XDriver to select theappropriate setting.

Data Length Refer to the documentation provided with the XDriver to select theappropriate setting.

Parity Refer to the documentation provided with the XDriver to select theappropriate setting.

Stop Bits Refer to the documentation provided with the XDriver to select theappropriate setting.

Configuring a Comm Port for Infinet, MS/TP, or Wireless

You can configure a comm port to communicate with an Infinet controller, a BACnetMS/TP controller, or a bCX1 series controller equipped with a wireless adapter,communicating with a wireless subnetwork.

Note: The Wireless choice is available for the following parent controllers: Infinet bCX1Model 9640, BACnet bCX1 model 40x0, and NetController II models 9680 and9681. See the tables below.

Note: As a future enhancement, ACX 57xx series controllers will support Wireless, muchlike the NetController II models 9680 and 9680.

A bCX1 series controller can be either an Infinet controller (90x0 model) or a BACnetcontroller (40x0 model). The Wireless choice is available both the Infinet bCX1 and theBACnet bCX1. For more information, please see the bCX1 Series Controller TechnicalReference, 30-3001-890, and the Wireless Adapter Installation Sheet, 30-3001-887.

For each controller, the table below lists comm ports to use for Infinet or Infinet Wireless.



TAC 136

Note: Once you select Infinet and save for the default mode, you cannot change it.

9000 and 9200 Use COMM1 or COMM2. Select Infinet for Default Mode.

9400 Use COMM1 or COMM2. Select Infinet for Default Mode.

9924 Use the Infinet port. The default mode for this port is Infinet.

NetController (99xx)

Use COMM1 or COMM2. Select Infinet for Default Mode.

NetController II

(9680 and9681)

For both Infinet and Wireless, use COMM1 or COMM2.

When COMM1 is configured for Infinet and COMM2 is configured for Wireless (or vice versa) there are some special considerations for updating the operating system of the Infinet or Wireless fieldcontrollers. (See the descriptions for the buttons on the General tab of the InfinityController editor.)

ACX 57xxseries

Use COMM1. the ACX 57xx controller has only one configurable RS-485 comm port. The default mode for this port is AutoSet.

9702 Use COMM1. The default mode for this port is Infinet.

bCX1 9640 Use COMM2. Select Infinet or Wireless for Default Mode.

Which Comm Ports Should I Use for MS/TP or BACnet Wireless

b4920 Use COMM1. You must use MSTP for Default Mode.

bCX1 40x0 Use COMM2. You can select MS/TP or Wireless for Default Mode.

Baud Rate The default baud rate is 19.2K baud. Valid baud rates for Infinet alsoinclude 1200, 2400, 4800, and 9600. (MSTP also permits 9600 baud.Wireless also permits 19.2K.) Set the baud to a lower rate if yourequire greater noise immunity. If you are using an Infilink on theInfinet, be sure that their baud rates match.

Flow Control Flow control does not apply to Infinet connections.

TrackCXD This attribute does not apply to Infinet connections.

Completing Configuration of Controllers After you enter and apply settings to connect a controller to a comm port, you use theLearn button to create controller objects with configuration data for each controller connected to this comm port.

Learn also sends information about:

• All the network-connected Infinet controllers to the Infinity controller

• All the BACnet MS/TP network-connected b3 controllers and other BACnet third-party devices to the b4 or bCX1 40x0 controller.

• All the controllers connected through a wireless subnetwork to the wireless adapter affixed to the bCX1 9640 Infinet controller.




When the learn process completes, you will be able to see these controllers on the FieldBus Controllers tab.

Learn and bCX1 40x0 Controllers

Before performing a routine Send to Database operation on a bCX1 40x0 seriescontroller, you must first perform a "learn" operation. This ensures that the bCX1 40x0first knows about the existence of its BACnet field bus controllers (b3 and third-partycontrollers). After the learn, the Send to Database fetches object information from allcontrollers residing on the field bus subnetwork and saves it to the CyberStationdatabase.

Before performing the Send to Database operation, make sure you have also selectedthe Save attached objects and controllers radio button in the Send to Database Options dialog. This ensures that data from child objects in child controllers (attached to theparent bCX1 40x0) are also saved.

CAUTION: If you do not do these things, the Send to Database operation may fail for controllers residing on a bCX1 40x0 controller's field bus network.

See Chapter 3, Continuum Explorer , for more information on Send to Databaseoperations, and the Send to Database Options dialog.

Comm 1 and 2 of a network controller can be configured as Infinet ports. Each Infinet porton a network controller can support up to 127 regular (building automation) Infinetcontrollers and up to 31 priority (security access and display) Infinet controllers.

Configuring a Comm Port

The comm port you select to configure and the settings you choose in the CommPorteditor depend on the model of network controller and the device you want to connect to it.Refer to “Comm Port Settings for Specific Devices” to identify the appropriate settings touse for you devices.

To configure a comm port, follow these steps:

1. In Continuum Explorer, expand the network controller whose comm ports you want toconfigure.

2. CommPort objects appear in the list of objects in the viewing pane. Double click theCommPort class folder under the controller.

3. Double click the CommPort object you want to configure.

4. In the CommPort editor, select the appropriate settings in each tab as described onthe following pages.

5. Click OK.



TAC 138

General Tab – CommPort Editor

In the General tab, enter basic information about the comm port.

Note: When Infinet, MSTP, or Wireless is selected in the Default Mode field, another tab, Field Bus Controllers, appears. See Field Bus Controllers Tab, later in thischapter.

Description Type in a description for the comm port. You can use up to 32alphanumeric characters. This attribute is optional, but providing a gooddescription can aid other users.

Comm PortNumber

The CommPort attribute displays the number of the comm ports you areediting.

DefaultMode

Each comm port has a default mode. To change the default mode, selecta different one from the Default Mode dropdown menu. The Settings tabdisplays different attributes, depending on the default mode you select.

Note: In the event of a controller reset, each comm port reverts to itsoriginal default mode. For a complete list of default modes for eachcomm port on each controller, please see the section, Default Modes, later in this chapter.

Printer Select this option when connecting a serial printer to

this port.

Command Select this option when you are connecting a VT100or VT200 type terminal to this port and you want tohave the terminal to display a command line. If youwant the terminal to display windows and menus,select the Window option instead. To switchbetween Window and Command mode at theterminal, select the AutoSet option.

Infinet (Comm 1and 2 Only)

Select this option to set up this comm port as anInfinet port. An Infinet port connects an Infinitycontroller to an Infinet network. When the defaultmode is set to Infinet, another tab is added to the

CommPort editor: Field Bus Controllers.MSTP Select this option to set up this comm port as a

BACnet Master-Slave/Token-Passing (MS/TP) port.The MS/TP option is the only option available on theb4920. It is also available on bCX1 40x0 BACnetcontrollers. MS/TP is required for the b4920controller to communicate with other BACnetdevices, such as b3 controllers.




Wireless Select this option to use a Wireless Adapter on abCX1 96xx Infinet controller or a bCX1 40x0BACnet controller, communicating over a wirelesssubnetwork.

Lbus Select this option to set up communicationsbetween your controller and one or more IOUboards on an LBus. Lbus is supported for comm4on a CX9200 or CX9300 controller and comm1 on aNetController.

AutoSet Select this option when you are connecting a VT100or VT220 type terminal to this port and you want tobe able to switch between Window and Commandmode. This option provides you with a blank screenwhen the terminal is first turned on. Type either Window or Command at the blinking cursor to selecta mode.

TankNet Select this option to connect to an Infinity level-sensing probe.

XDriver (Support for anXDriver must be

purchased)

Select this option to use a customized externalequipment driver to connect to a special piece of equipment.

Note: Before you can select the XDriver, you mustfirst install it using the instructions providedwith the software.

To select an XDriver file, click the browse button tolocate and select the file for the XDriver. Dependingon how you installed the XDriver, the file may or may not have a file extension of .xdr.

NotConfigured Select this option if the comm port is available.Indicates that the port is not preset to any other default mode configuration.

Viewing the Status of an XDriver Device

In the General tab, click the XDriver Status button to view the status of the device that isusing the XDriver. The XDriver Status button displays the following read-onlyinformation:



TAC 140

Status Displays the status of the device, or XdrvNotInstalled when noXDriver file has been selected.

Error Displays the last error to occur on the device.

Error Time Displays the time and date that the last error occurred on thedevice.

Error Count Displays the number of errors that have occurred on the devicesince you last set it to zero. Increments to 255 errors and remainsset at 255 until you reset it to zero by clicking the Reset Countbutton.

Settings Tab – CommPort Editor

The Settings tab is where you view or edit the communications speed and handshakingsettings for the mode that you have chosen for the port.

Depending on which Default Mode you select on the General tab, some of the attributeson this tab may be unselectable (appear gray).




Baud Rate The Baud rate is the speed, measured in bits per second, at which thecontroller sends information to the device that you are connecting to the

comm port. Select the baud rate that matches that required by theequipment connected to this port.

Track CXD This option monitors a communications carrier detect signal called CXD.When selected, it enables the controller to detect when communicationwith connected objects has been lost.

Depending on your modem configuration, the CXD (sometimes calledDCD) signal (pin 8 on an RS-232 connector) is asserted "high" when thecommunications link is established between modems. Once the carrier signal is lost, CXD goes "low." Track CXD looks for this high-to-lowtransition and makes the controller reset this comm port to its defaultmode. Track CXD “cleans up” the comm port by logging off the last user.Track CXD is selected by default, and it is required for comm ports that are

connected to modems. If Track CXD is not selected, the controller cannotrespond to the loss of the CXD signal.



TAC 142

FlowControl

The flow control type determines how the comm port handles the flow of data between the controller and its attached device (usually a printer,modem or terminal). This process is also known as “handshaking.”

Select one of the following options from the dropdown menu:

NoFlowControl Select this flow control type if you do not want toregulate the flow of information between the controller and its attached printer, modem, or terminal. Without aflow control type, buffers that hold data that is beingtransmitted or received could overflow, and some datacould get lost.

CtsRts This flow control type uses hardware signals to send"clear to send" (Cts) and "request to send" (Rts)messages. Both of these messages must beacknowledged by the controller and its attached devicebefore information can be transmitted.

XonXoff This control flow type uses software signals in the formof characters that are sent as part of the data beingtransmitted. When the controller or its attached devicedetects that it has been sent an Xon character, itmakes itself available to receive data. It considers alldata received after the Xon character as valid. When it

detects an Xoff character at the end of the data stream,the controller or attached device knows thetransmission is complete.

XonXoffCtsRts This flow control type uses both the software (XonXoff)and hardware (CtsRts) handshake methods for regulating the flow of information between thecontroller and its attached device.

CurrentMode

This is a read-only attribute that shows you the default mode selected inthe General tab.

SecurityLevel Tab – CommPort Editor

Refer to Chapter 4 for details regarding attaching or detaching SecurityLevel objects.Field Bus Controllers Tab – CommPort Editor

When you set Default Mode on the General tab to Infinet, MSTP, or Wireless, on theField Bus Controllers tab is added to the CommPort editor appears.

This tab displays the controllers that reside on their respective field bus network —Infinet, BACnet MS/TP, or Wireless — connected to this comm port. The controllers willnot display, however, until you click the Learn button on the Settings tab.

The CommStatus column displays either Online or Offline for controllers listed in theName column. When a controller is Online, it is communicating with the rest of thenetwork. When a controller is Offline, it is not in communication with the rest of thenetwork.. This information is read only.




Summary of Comm Port Characteristics

The following table presents a summary of default modes and other modes for commports in the following controllers.

9200

InfinetPort

User Port COMM1 COMM2 COMM3 COMM4 COMM16 CustomPort

- - DefaultMode: NotConfigured

Other Modes:Window AutoSetInfinetTankNetXDriver Commandon 9300

DefaultMode: NotConfigured

Other Modes:Window AutoSetInfinetTankNetXDriver Commandon 9300

DefaultMode: AutoSet

Other Modes:WindowTankNetXDriver Commandon 9300


Other Modes:Window AutoSetLbusTankNetXDriver Commandon 9300

- -



TAC 144

9400

InfinetPort


- - DefaultMode: NotConfigured

Other Modes:WindowCommand AutoSet

InfinetTankNetXDriver



InfinetTankNetXDriver


Other Modes:WindowCommandPrinter

TankNetXDriver Command



TankNetXDriver

DefaultMode: LON

Other Modes:XDriver

9924

InfinetPort


DefaultMode:Infinet

Other Mode:

XDriver

- DefaultMode: NotConfigured

Other Modes:WindowCommand AutoSetXDriver


Other Modes:WindowCommand AutoSetXDriver

- - - Default Mode :

TankNet

Other Mode :

XDriver

9702

InfinetPort


- - Default andonly Mode:Infinet


Other Modes:Printer

- - -

NetController

InfinetPort


- - DefaultMode: NotConfiguredOther Modes:Window AutoSetInfinetTankNetXDriver CommandL-BUS

DefaultMode: NotConfiguredOther Modes:TankNetXDriver

DefaultMode: AutoSetOther Modes:WindowPrinter XDriver Command

DefaultMode: NotConfiguredOther Modes:XDriver

DefaultMode: LONOther Modes:XDriver

-




NetController II 9680 and 9681

InfinetPort


- - DefaultMode:

AutoSet

Other Modes:Printer Infinet

LbusLONPPPWirelessXDriver

DefaultMode:

AutoSet

Other Modes:Printer Infinet

WirelessXDriver

DefaultMode:

AutoSet

Other Modes:Printer PPP

XDriver

DefaultMode:

AutoSet

Other Modes:Printer ILbus

XDriver

DefaultMode:LONOther

Modes:XDriver

-

ACX 57XX Series

InfinetPort

UserPort COMM1 COMM2 COMM3 COMM4 COMM16 CustomPort

- - DefaultMode:

AutoSet

Other Modes:Infinet

WirelessXDriver

- - - - -

Note: Although Wireless is a selection for COMM1, ACX 57xx series controllers willsupport Wireless as a future enhancement.

bCX1 96xx

InfinetPort


- DefaultMode: AutoSet

Other Modes:Printer

PPP

Xdriver


Other Modes:Infinet

Wireless

Printer

Xdriver

- - - -



TAC 146

bCX1 40x0

InfinetPort


- DefaultMode: AutoSet

Other Modes:

Printer

DefaultMode: Autoset

Other Modes:MS/TP

Wireless

Printer

- - - -




Creating IOU

ModuleObjects

After you finish configuring a controller with the Comm port editor, you can define your input and output. Start by defining the IOU modules with the IOUModule editor.

IOU modules are electrical units that contain a number of input and/or output circuits thatare electrically and sometimes physically attached to controllers. They provide controllerswith the ability to interface with the outside world. There are four types of IOU Modules:

• Input modules

• Output modules

• Mixed input and output modules

• Special-purpose modules

9



TAC 148

Creating an IOU Module Object

The following steps allow you to add an IOU Module object for an IOU Module connectedto a controller.

1. Right click the controller that you want to own this module, select New, and thenselect IOUModule.

2. When the New dialog appears, name the IOUModule and click Create.

General Tab – IOUModule Editor Use the General tab to enter basic information about the IOU module.

Description The description is optional, but a good description of the IOUModuleobject helps others when they need to test, modify or manipulate thenetwork. To enter a description, type up to 32 characters (includingspaces) in the text field.

IOU Number Enter the IOU number here. You must manually assign a uniquenumber (between 1 and 32) for each IOU module on a networkcontroller.

Physically label the IOU modules with the numbers you assign. Thisnumber is not the same as the 12-digit module ID # assigned to theindividual module at the factory.

You will use this number when you configure points on this controller.

ModelNumber

The model number identifies the type of the IOUModule and is readfrom the module.




Comm Status This displays Online or Offline, depending on whether the controller isin communication with the module.

Module IDand ProgramID

These TAC-assigned numbers appear after the Learn process. Theonly time you will need these numbers is when speaking to a TACSupport Representative. These numbers will help our staff to answer your questions. You may manually enter the Module ID number in thisfield, (if you know it), rather than following the Learn process.

LearnUse the Learn button to commission the IOU module on the network.See “Commissioning an IOU Module” later in this chapter.

Wink Use the Wink button after commissioning the IOU module to confirmthat your system recognizes the IOU module.

Click the Wink button. The Status light on the IOU module should flash.This indicates the IOU module was successfully commissioned.

Update IOU Click the Update IOU button to browse for a *.iou file (a TAC-providedFlash File for individual modules) when updating IOU modules with newfirmware.

SecurityLevel Tab – IOUModule Editor

The SecurityLevel tab shows the object security level and access privileges for theobject. For more information, see Chapter 4, Security .

Commissioning an IOU Module

Perform this procedure after installing the IOU module on the controller.

1. In the IOUModule editor, click the Learn button.

A dialog displays requesting the operator to press the Commission button on thephysical module.

2. At the IOU Module, press the Commission button on the front panel.

The dialog at the workstation should disappear indicating that it received theinformation from the module.

If the module is not easily accessible, you can enter the module ID found on the labelinside the cover of the module into field, and click the Apply button.

3. In the IOUModule editor, click the Refresh button.

The ModuleID for commissioned module, the ProgramID field, and the IO model type(i.e., AO-4-8) are automatically entered. This information was received from themodule. Also, the Comm Status should be online.



TAC 150

Replacing an IOU Module

Proceed as follows:

1. Remove power from the I/O Bus where the module is to be installed.

2. Replace the module, and re-apply power.

3. In CyberStation, open the IOUModule editor for the module you are replacing, andclick the Learn button.

4. At the IOU Module, press the Commission button found on the front panel of themodule.

If the module is not easily accessible, you can enter the module ID found on the labelinside the cover of the module into the field, and click the Apply button.

5. In the IOUModule editor, click the Refresh button.

The Module ID for commissioned modules, the ProgramID field and the IO modeltype (that is, AO-4-8) are automatically entered. This information was received fromthe module. Also, the Comm Status should be on-line. Check that the version of the module reported on this screen is compatible with thecurrent version of CyberStation. The fourth field in the Program ID is the versionnumber. For example the Program ID of a DO-4 with version 10 is:

81:11:01:10:00:04:00:01

Version number




Configuring

Alarms

Considering the Alarm System

Before setting up your alarm system, you need to consider the following questions:

1. What points or network objects do I want to monitor — for example, space tempsensors?

2. What conditions would cause a point to be in an alarm state — high limit, low limit, oroff setpoint?

3. What actions do I would want to take place in the system in response to that pointmeeting those conditions? For example, alarms can be configured to send flashingalarm messages, play audio files, or send email in response to an alarm.

4. Who should be notified that an alarm condition exists?

The size of your system will help to determine how may different sets of actions youshould configure for alarms. If you have only one place to send alarms, you don’t need tocreate a lot of different sets of actions to be taken in response to alarms.

Once you have decided what points need to have alarms, what the alarms will do, andwho will be notified, you can begin using Continuum editors to create alarm system

objects. Alarm objects are configured in the reverse order of the steps used in thinkingabout the alarm system described above.

Alarms and BACnet

Alarms are created as AlarmEnrollments for Infinity objects, and they are created asBACnet EventEnrollments for BACnet objects. An EventEnrollment defines astandardized object that represents and contains the information required for managingevents within BACnet systems. You use the AlarmEnrollment editor to create, access,and edit AlarmEnrollment objects. Similarly, you use the EventEnrollment editor forBACnet EventEnrollment objects. (Please see Chapter 14 for a description ofEventEnrollments and the EventEnrollment editor.)

10



TAC 152

Basic Steps for Setting Up Alarms

To set up alarms for Continuum objects use the following basic steps:

1. Create the EventNotification object(s) you need.

2. Create the AlarmEnrollment or EventEnrollment object(s) you need, each of which isassociated with an EventNotification object.

3. On the Alarms tab (or Advanced Alarms tab) of an object editor, attachAlarmEnrollment objects to the point or network object.

About EventNotification Objects

EventNotification objects are linked to AlarmEnrollment objects, EventEnrollment(BACnet) objects, or basic alarms. One EventNotification can be associated with multiplealarm enrollment objects.

EventNotification objects define which workstations receive events. The event states thatare processed by Event Notification objects are: alarms, returns to normal, and alarmfaults. In addition to event routing, Event Notifications define which hours events will bereported, and what actions are taken upon receiving the event such as: emailing, paging,logging, printing, displaying the alarm view, displaying graphics, running programs,playing audio, blinking, and so on. Event Notification objects provide prioritization ofevents, repeat timer functionality, acknowledgement rules, color coding, and deactivationcriteria.

For example, a workstation can be configured to display events between the hours of 9-5,and use the paging feature during the hours of 5-9 only if the alarm remainsunacknowledged for the repeat interval.

EventNotification objects route alarms to different workstations based on the problemsource. For instance, security alarms can be routed to the guard workstation, HVACalarms can be routed to the maintenance workstation, and IOModuleStatus alarms canbe routed to the administrator’s station. Another usage is segmenting a site –EventNotifications can route alarms to different workstations based on the source of theevent. For instance, all events occurring in BuildingA can be routed to WorkstationA andall events occurring in BuildingB can be routed to WorkstationB.

We recommend you that you use EventNotification objects as severity levels. Forexample, create EventNotification objects named “Warning,” “Critical,” and “Alert,” andassociate appropriate events with them accordingly. Furthermore, if site segmentation isused, we recommend that the location is added to the name. For example, the nameBuildingACritical would be used in the example above.

Adding and removing recipients from an event notification can affect the way severalalarms are routed because a single event notification object can be attached to severalalarm enrollment objects.

About Configuring Alarm System Components

To complete the tabs of the EventNotification and AlarmEnrollment object editors, youtype information into text fields and make selections from dropdown menus in the tabs of




the editors. You then open a point editor and attach AlarmEnrollment objects to thepoint and set other alarm parameters.

To create an EventNotification object, you’ll make decisions based on the followingquestions:

Which colors and fonts will the notification have?

You’ll answer this question by specifying font styles and background colors for eachpossible event state.

Which notification actions will occur?You’ll answer this question by making selections from a list of possible notificationactions.

Who will be notified of the event?

You’ll answer this question by creating a list of workstations where notification of theevent will be delivered.

How will users remove the event from the active alarm view?

You’ll answer this question by selecting a condition that must exist before Continuumwill remove the event from the Active Alarm View.

Will Event Notification Include the Playing of Audio Files?

You’ll answer this question by deciding whether or not to associate an audio file witheach possible event state.

Who will have permission to make changes to the configuration of thisEventNotification?

Please refer to Chapter 4, Security .



TAC 154

Using the EventNotification Editor

The EventNotification editor is a series of tabs. Each tab contains text fields, buttons, anddropdown menus that you’ll use to define or modify the EventNotification object. You’llenter text in the text fields and make choices by clicking buttons and selecting from listsof possibilities.

Creating the EventNotification Object

To create an EventNotification object perform the following steps:

1. In the Explorer’s navigation pane, right click the Root or the folder to which you wantto add an EventNotification object.

2. From the New dialog select EventNotification:

3. When the New dialog appears enter a name for the EventNotification object in theObject name text field.

4. Click the Create button to create the object and bring up the EventNotification editor.

CAUTION

When working with EventNotification objects, please be aware thatwhen you edit existing attributes you are changing the way everyassociated basic alarm and AlarmEnrollment object is delivered.

! !




The EventNotification General Tab

In the General tab, you enter basic information about the event.

Description The description, although optional, is an important part of anEventNotification object. A good description helps future userschoose the correct EventNotification object to associate to aparticular event or alarm.

To enter a description, type it into the Description text field on theGeneral tab. Your description can be up to 32 characters (includingspaces) long.

Ack Required This section is used for BACnet controllers only. Check theappropriate checkbox to specify whether acknowledgement isrequired in notifications generated for the following event transitions:

Alarm

ReturnToNormal

Fault

Priority Priority numbers help sort events in the Active Alarm View. One ofthe benefits of sorting by priority number is that it is one way todisplay critical events at the top of the active list. In the Active AlarmView, you determine whether high or low priority numbers display atthe top by selecting either ascending or descending as your sortorder. The range of priority numbers is 0 to 254. Each event statereceives its own priority number. To enter a priority number for anevent state, type it in its text field on the General tab.



TAC 156

Colors andFonts

For every event state you can specify colors and font styles. Thecolors and fonts you select will display in the status bar and in theActive Event View or Active Alarm View when an event associatedwith this EventNotification is delivered.

To select colors and fonts, place your cursor in the Alarm Colors,

RTN Colors or Fault Colors area of the General tab.

Right click to display a pop-up menu.

To select a new font style and size, select Font.

The Font dialog appears. Select a font and font style from thescrollable lists. As you make your selections, you’ll see an example of

the font and all the settings you’ve chosen in the Sample text field.

For more help, click the button. Click specific area of the Fontdialog.

Click OK to save your font settings.

To select background color and text colors, select BackgroundColor or Text Color. Click a basic color, or click Define CustomColors if you don’t see a color you like. This adds a color matrix tothe dialog.

Define your color by changing the Hue, Sat, Lum, Red, Green, and Blue settings. You can enter either of these settings, or change themby clicking anywhere in the matrix and by moving the cursor. ClickAdd to Default Colors when you are finished.

For more help, click the button. Click specific area of the Colordialog.

Click OK to save your color settings.

Repeat The repeat interval specifies how many minutes the workstation willwait until re-issuing the event. When an event is re-issued, its repeatactions are carried out.

Re-issuing continues until the event is either silenced or

acknowledged. To enter a repeat interval, type the number of minutesinto the Repeat field on the General tab.




Ack Rules Acknowledgment rules simplify the task of acknowledging alarmswhose EventNotification objects are configured for multiple entries.From the General tab, select one of the following rules from the Ack Rules dropdown menu.

AckAll - Acknowledge all reported events for the same alarm.

AckUntilTime - Acknowledge the currently selected event and allevents reported before this one for the same alarm.

AckOnlyThisOne - Acknowledge only the currently selected event

for this alarm.

These acknowledgment rules apply to just one object at a time.

For example, if RoomTemp1 and RoomTemp2 both trigger an alarmnamed TooHot, when the operator acknowledges the alarm triggeredby RoomTemp1 the AckAll and AckUntilTime rules won’tacknowledge the alarm triggered by RoomTemp2.

EventConfiguration

Select either Multiple Entry or Single Entry. This determineswhether or not the Active Alarm View will display an additional entryevery time the event changes state. Single Entry is recommended,as this will decrease the number of entries in the Active Alarm View.If you select Multiple Entry, select an acknowledgment rule as well.

Understanding Alarms

Every reported event has an attribute named “ToState”. The value of this attribute isdetermined by the status of the alarm that triggered the event. At any given time, anevent has one of three possible statuses: Alarm, Return to Normal, and Fault. Listedbelow you’ll see an explanation of each state and how each one triggers an event.

Alarm When an object’s attributes changes to what has been previouslyestablished as being outside normal operating standards, the object’sevent state changes to Alarm. If the AlarmEnrollment object or the basicalarm associated with the object has the Alarm report option selected,the controller sends this out as an event. This event displays in theActive Alarm View with a ToState value of Alarm. How and to whom the

event is delivered is determined by the AlarmEnrollment object’sassociated EventNotification object.

Return toNormal

When an object’s attributes changes to what has been previouslyestablished as being normal, the object’s event state changes to Returnto Normal. If the AlarmEnrollment object or the basic alarm associatedwith the object has the Return to Normal report option selected, thecontroller sends this out as an event. This event displays in the ActiveAlarm View with a ToState value of Return to Normal. How and to whomthe event is delivered is determined by the AlarmEnrollment object’sassociated EventNotification object.



TAC 158

Fault When a device that is local to the object detects a fault, the object is saidto be in a Fault state. The ability to detect faults and the messagesassociated with faults vary depending on the device manufacturer. If theAlarmEnrollment object or the basic alarm associated with the objecthas the Fault report option selected, the controller sends this out as anevent. This event displays in the Active Alarm with a ToState value ofFault. How and to who the event is delivered is determined by theassociated EventNotification object.

Note: When installing more than 64 CyberStation workstations (NetworkID 191-254),

you will need to set the NetworkID to 0 and also set the DeviceID to a uniquenumber. Refer to “Setting Up Workstation Parameters” in the Continuum Installation Guide, 30-3001-720.

CyberStation workstations with NetworkID 0 shall receive alarms and participate as anormal CyberStation.

The EventNotification Actions Tab

The Actions tab lets you define how the event is enunciated.

Print Alarm If the event is in an Alarm state, sends event notification to thesystem printer. This action requires the Alarm report option to beselected, and it requires that a workstation is selected as aprinter in the Delivery tab.

Print Return toNormal

If the event is in a Return to Normal state, sends eventnotification to the system printer. This action requires the Returnto Normal report option to be selected, and it requires that aworkstation is selected as a printer in the Delivery tab.




Print Fault If the event is in a Fault state, sends event notification to thesystem printer. This action requires the Fault report option to beselected, and it requires that a workstation is selected as aprinter in the Delivery tab.

PrintAcknowledgment

Sends a message to the system printer when the event isacknowledged. The message contains the same informationthat is displayed in the alarm and event viewers. This actionrequires that a workstation be selected as a printer in the

Delivery tab.

Run Program Runs the Plain English program specified on the Alarms orAdvanced Alarms tabs of the alarmed object’s editor. Notavailable for Basic Alarms.

Remove fromAlarm Line onAcknowledged

Always removes the event from the status line alarm of theActive Alarm View, when acknowledged.

Beep on Alarm If the event is in an Alarm state, causes workstations to beepcontinuously when the event is delivered.

Beep on Return toNormal

If the event is in a Return to Normal state, causes workstationsto beep continuously when an event notification is delivered.

Beep on Fault If the event is in a Fault state, causes workstations to beepcontinuously when event is in a Fault state.

Play Audio onAlarm

Plays the alarm audio file selected from the EventNotification orAlarmEnrollment Feedback tab.

Play Audio onReturn to Normal

Plays the Return to Normal audio file selected from theFeedback tab.

Play Audio on

Fault

Plays the fault audio file selected from the Feedback tab.

Display Panel Displays the panel specified on the Alarms or AdvancedAlarms tabs of the object editor. Not available for Basic Alarms.

Display AlarmView

Displays the Active Alarm View when the event is received.

Note: The Active Alarm View’s View menu has an entry calledAlways on top. When this option is selected, the alarmview will always be the top most window.

Display Video Displays the surveillance video monitor (the VideoLayout editor)when this alarm event occurs. For more information onVideoLayouts, please see Chapter 25.

Blink on Alarm Causes events to blink in the status line of the Active AlarmView. Note that when Continuum is minimized, its task bar iconwill blink instead.



TAC 160

Email on Alarm Sends an Alarm event notification to all Email recipients in theEventNotification distribution list.

Note: When running under Windows XP this distribution list iscalled Contact.

Email on Return toNormal

Sends a Return to Normal event notification to all Emailrecipients in the EventNotification distribution list.

Email on Fault Sends a Fault event notification to all Email recipients in the

EventNotification distribution list.Email onAcknowledgement

Sends an event acknowledgement message to all Emailrecipients in the EventNotification distribution list.

Page on Alarm Sends an Alarm event notification to all pager recipients in theEventNotification distribution list.

Page on Return toNormal

Sends a Return to Normal event notification to all pagerrecipients in the EventNotification distribution list.

Page on Fault Sends a Fault event notification to all pager recipients in theEventNotification distribution list.

Page onAcknowledgement

Sends an event acknowledgement message to all pagerrecipients in the EventNotification distribution list.

The EventNotification Delivery Tab

The Delivery tab is where you create a recipient list. Every workstation in the list receivesand views events associated with this EventNotification object in the status line of theAlarm Bar and their Alarm View.




Via the Recipients Configuration dialog described on the next page, for eachworkstation that you add to the recipient list, you specify the following:

• The valid days the workstation will receive event notification.

• The valid time periods during which the workstation will receive notification.

• Which notification actions for which the workstation is responsible. Notificationactions include forwarding, printing, e-mailing, paging and logging. These actions areoptional; however, for compatibility with Infinity controllers, you must designate oneworkstation to forward events.

• Whether the workstation is designated as one that downloads and forwards alarmnotification messages to other BACnet recipient workstations. (At least oneworkstation recipient in the list must be designated this way. See the description ofthe Download To BACnet Device checkbox on the next page.)

To delete a recipient workstation from the list, select it and click Remove Recipient.

To add a recipient, click the Add Recipient button. This displays the RecipientsConfiguration dialog, shown and described on the next page.

Note: The Send to All Workstations checkbox is always unselectable and appears ingray. See the description of the Recipients Configuration dialog, next.

Recipient Click the button next to the Recipient field. This displays

Continuum’s Browse dialog for devices. Use this dialog to find theworkstation you want. Click Select to insert the correct path andworkstation name into the Recipient field.



TAC 162

BACnetAddress

To ensure that Continuum knows about a specific BACnet destinationrecipient, and to differentiate between a BACnet global broadcast anddelivery to a specific BACnet device, check this checkbox.

When you check this box, the Recipient field's browse button becomes adropdown menu, offering the following choices:

• Global Broadcast — Select this option to deliver event messagesas a global BACnet broadcast.

• Net:MAC — Select this option if the message must be delivered

to a specific BACnet destination recipient. When you select thisoption, Net:Mac appears in the Recipient field. Identify the deviceby entering the network number and the MAC address number forthe device in this field. The network number is an integer. TheMAC address number is hexadecimal. For example: 13:002B.

The hexadecimal MAC address number must have an even number

of digits, include leading zeros in the octet.

If you enter an odd number of digits, you will receive an error message.When you select the BACnet Address box, the Primary, Backup, andRepeat checkboxes become disabled.

Guarantee

Delivery

Check this checkbox to guarantee delivery of message, from a BACnetdevice to CyberStation recipients or other BACnet device recipients.

DownloadTo BACnetDevice

Check this checkbox to download and forward alarms from this recipientworkstation to other BACnet recipient workstations. This optionconserves memory in BACnet devices in the system. At least oneworkstation in the recipient list must be designated as a downloading andforwarding workstation. When this is checked for this recipient, theDownload column on the Delivery tab displays the value, True.

Valid Days Select the days on which this workstation will receive notification. Simplyclick the checkboxes next to the days you want.

From TimeTo Time

Enter the From and To times this workstation can receive eventnotification. Select the hour, minute, second, or AM/PM setting you wishto change. Type over the existing value, or click the up and down arrows

to change the value.

Noncontiguous times are supported such as:

From = 7pm

To = 6am

This is equivalent to

7pm – 11:59pm

12am – 6am




Primary,Backup,Repeat

Select forwarding, emailing and paging notification tasks to be carried outby the primary and/or backup workstations as described below.

Transitions In this section, select the event transition states for an event notificationthat is sent to this recipient workstation. Check the checkboxes forToOffNormal, ToFault, and ToNormal.

These selections specify which transitions control the delivery of an eventnotification to this recipient workstation. For example, you may not want

to notify a security guard about a device fault.

Distributing Tasks to Several Workstations

Each workstation in your recipient list can be assigned tasks such as printing the event orsending email about the event to a select group of people. By assigning different tasks todifferent workstations, you can distribute important tasks to your faster machines, andgive the less crucial tasks to slower machines. You can also designate a workstation aseither the primary or backup machine for each task. Primary workstations are simplyworkstations that are primarily responsible for the task. Backup workstations only performthe task if the primary workstation is off-line.

For this purpose, the Delivery tab’s Recipients Configuration dialog has three columnsof responsibilities, Primary, Backup, and Repeat, and a list of tasks, shown below:

To display the Recipient Configuration dialog, double-click a recipient you would like to

edit, or click the Add Recipient button to work on a new recipient.

To assign a task to a workstation, click in either the Primary or Backup column for thattask. If you would like the workstation to perform the task only if the event has beenrepeated, click in the Repeat column as well. The repeat interval is determined by whatyou set in minutes on the Repeat field on the General tab. (See EventNotification General Tab, earlier in this chapter.)

Each column contains the following actions:

Print Prints the notification.

Alarms, Returns to Normal, faults, and acknowledgements are sent todesignated alarm printers of the primary and backup workstations. You canassign the path to the alarm printer via the Continuum Preferences dialog.The Windows default printer is used if the field is left blank. If “suppressform feed” is selected, it is assumed that a raster printer is being used. Inthis case, the printer must be local to the printing workstation.



TAC 164

Forward Sends notification to the other workstations in the recipient l ist. This iscurrently used for all alarm acknowledgements, alarm silencing and BACnetalarms.

Log This is applicable to versions earlier than version 1.5, which implementedenhanced

alarm logging. If you have an old version (or if the Enhanced AlarmLogging checkbox on the Database Initialization dialog was not checkedduring Continuum installation) checking the Log box creates a log of events

in a Listview.E-mail Sends email to everyone in this EventNotification email distribution list.

Paging Pages everyone in this EventNotification page distribution list.

Creating an EventNotification Email and Page Distribution List

Requirements for forwarding CyberStation alarms via email or page:

• The CyberStation workstations that have been designated primary and backup emailand/or page handlers must have a MAPI-compliant email client such as MSExchange or Outlook.

• The email client application can communicate with an existing email serverapplication, such as MS Exchange Server.

• The primary or backup email/paging workstation must be running CyberStation at thetime an alarm is generated.

• Each EventNotification object associated with the alarms that you wish to email orpage must have its own email distribution list in the personal address book orContacts list of the client email application using a specified naming convention asoutlined in Step 4 below.

• This email distribution list must be stored in the first address book shown in the list ofavailable address books in the email client application. For example, if you create anEventNotification distribution list in the Personal Address Book in Microsoft Outlook,then the Personal Address Book must be the first one showing in the address listdropdown menu when you open the Address Book.

Creating an EventNotification Distribution List

To create an email or page distribution list, proceed as follows:

Note: The following steps are based on Microsoft Outlook. Other mail applications mayhave different menu names and choices but the general procedure is the same.

1. Open the Address Book for the email account on the CyberStation workstation thatwill be providing the email/paging service(s). Your toolbar may have a button for this.If not, use the Address Book option of the Tools menu.

2. Select New Entry from the Files menu.

3. Select the entry type Personal Distribution List and put this entry in the PersonalAddress Book .




4. In the Name field enter a name for the distribution list using the following format:

For Email: ACC.eventnotification_name

For Paging: ACC.page.eventnotification_name

For example, if your EventNotification object is named Severe, the personaldistribution list for email deliveries should be named: ACC.Severe. Likewise, yourpersonal distribution list for page deliveries should be named: ACC.page.Severe.

Note: Use the EventNotification object Name not the Alias, for example, Critical

Temp, not CriticalTemp.5. Add members (the email addresses or pager and service numbers of those to whomthe notification of the alarm will be sent) to your personal distribution lists.

6. Set address book options so that the address book where your personal distributionlists are stored is the first one to be searched when sending emails or pages. For

example, in Microsoft Exchange, select Options from the Tools menu. Click theAddressing tab. When sending mail, check names using these address lists in thefollowing order area, use the Add button, then the up or down arrow buttons to addthe correct address book to this field and position it at the top of the list.

The EventNotification Deactivate Tab

The Deactivate tab is where you select a condition that must exist before the controllerremoves the event from the Active Alarm View. To select a condition, click one of the

following options:



TAC 166

Acknowledged Removes the event when it is acknowledged

Returned to Normal Removes the event when the event status returns to normal

Acknowledged OR

Returned to Normal

Removes the event when either the event status returns tonormal, or is acknowledged

Acknowledged ANDReturned to Normal

Removes the event when both the event status returns tonormal and is acknowledged

Acknowledged AFTER

Returned to Normal

Removes the event when it is acknowledged only after its

status returns to normal.Note: You can use the deactivation criteria along with the reporting options in the alarm

enrollment editor to achieve the desired results.

The EventNotification Feedback Tab

Use the Feedback tab to associate an audio file to each event state.

You use audio files when you want a recorded message or sound to play on workstationswhen an event is delivered. You can associate a different audio file to each event state.This is useful for alerting and informing operators as to the specific and appropriateresponse for different event states. Here are some basic points to keep in mind whenassociating audio files:

• For every audio file you add to this tab, make sure you select the corresponding

action on the Actions tab. In other words, if you associate an audio file with theAlarm state, select Play Audio on Alarm on the Actions tab.

• You may also select audio f iles for AlarmEnrollment objects. Every AlarmEnrollmentobject has a designated EventNotification object that defines how the alarm will be




delivered. When an AlarmEnrollment object with audio has an EventNotification object with audio files, the AlarmEnrollment audio files take precedence.

• Some objects can have basic alarms in addition to associated AlarmEnrollmentobjects. Basic alarms are specific to one object, unlike AlarmEnrollment objects,which can be associated to many objects. Like AlarmEnrollment objects, basicalarms have designated EventNotification objects that define how the basic alarm willbe delivered. Consequently, the audio files you specify on this tab will apply to allbasic alarms associated with this EventNotification object.

• To associate an audio file to an Alarm, Return to Normal or Fault event state, click

the button next to the appropriate text field. This will display the dialog shownbelow:

Audio files have a .wav file extension. You may have to navigate to the system folderthat contains your audio files. Click the button, then click in the Look in field for

help on moving to different folders. Once you have found the file you want, select itand click the Open button. This will close the dialog and insert the correct path and

audio file name into the Feedback tab.

The EventNotification Security Level TabFor details in attaching or detaching Security Levels, see Chapter 4, Security .



TAC 168

About AlarmEnrollment

AlarmEnrollment objects define the set of conditions used to determine when a point is inan alarm state. They specify the text messages that appear in the Active Alarm View.

When you create objects in Continuum, you have the option to attach up to eight alarmsto it. For example, you could set up an InfinityInput object for a temperature sensor sothat an alarm goes off when the temperature gets too high.

Each AlarmEnrollment object is associated with an EventNotification object.

To create an AlarmEnrollment object, you’ll make decisions based on the followingquestions:

Which attributes will trigger this alarm?

You’ll answer this question by selecting an attribute on the General tab. Most of thetime alarms are set up to monitor the value attribute.

Who will be notified of this alarm?

You’ll answer this question by selecting an EventNotification object on the Generaltab. EventNotification objects determine, among other things, which workstationsreceive notification, and which methods are used for notification.

What Algorithm will this alarm use?

You’ll answer this question by selecting an algorithm and providing its parameters onthe Algorithms tab. An algorithm is a set of rules by which an alarm is evaluated.

What will operators see and hear when this alarm goes off?

You’ll answer this question by writing text messages and selecting audio files for eachevent state. The text messages you write will appear in the Active Alarm View, alarm log,emails, pages, and printer output.

After you have configured an alarm, you can review the details of the configuration withthe following:

• Active Alarm View

• All Alarms ListView

• Object editorsNote: Continuum provides coverage for BACnet compliant devices. Configuring alarms

for these devices requires a new object class called EventEnrollment. Refer toChapter 14 for more information on the EventEnrollment editor.




Using the AlarmEnrollment Editor

The AlarmEnrollment editor is a series of tabs. Each tab contains text fields, buttons, anddropdown menus that you use to define or modify AlarmEnrollment objects. You’ll entertext in the text fields, and make choices by clicking buttons and selecting from lists ofpossibilities.

The AlarmEnrollment General Tab

The General tab is where you’ll enter basic information about the event. You’ll provideinformation for the following attributes:

Description The description, although optional, is an important part of anAlarmEnrollment object. A good description helps future users.

To enter a description, type it into the Description text field on theGeneral tab. Your description can be up to 32 characters (includingspaces) long.

EventNotification

Browse for an EventNotification object. This will insert the correct pathand object name into the Event Notification text field.



TAC 170

AlarmedAttribute

Only used for workstation alarms. Select an attribute from the dropdownmenu. This is a list of all of the possible attributes from all object classes.

Based on the algorithm parameters you set on the Algorithms tab, thevalue of the attribute you select from this list triggers the alarm.

For security applications, the Alarmed Attribute will always be Value.Infinity always uses Value for a hi/lo limit or expression.

Send When checked, each Send option causes the event to be displayed tothe Active Alarm View and all recipients on the notification list when the

associated point changes to that status.

The Alarm option reports the alarm when the point goes into an alarmstate.

The Return to Normal option reports the alarm when the point returns tonormal.

The Fault option reports the alarm when a BACnet device local to thepoint detects and reports a mechanical fault.

For example, if both Alarm and Return to Normal are checked, the eventis displayed when the point first goes into alarm and again when itreturns to normal. If no option is checked, no events are reported.

Alarm Type The selection you make here determines what fields display on theAlgorithms tab of this editor.

The choices of Infinity alarm types are:

Expression

Infinity Low Limit

Infinity High Limit

*Change of State

*Command Failure

*Floating Limit

*Out of Range

*These alarms are only applicable to BACnet objects. Refer to “The

EventEnrollment Algorithms Tab” in Chapter 14.

NotificationType

From the dropdown menu, select a notification type. The notificationtype specifies whether the notification message appears in the ActiveAlarm View as an alarm message, an event message, or a message ofevent acknowledgement.




The AlarmEnrollment Algorithms Tab

The attributes on this tab change, depending on the Alarm Type you selected from theGeneral tab.

Time Delay Time Delay appears on the Algorithms tab for each of the choices ofAlarm Type.

In the Time Delay field, enter the number of seconds you want topostpone evaluating the alarm.

For example, you may decide that the point value can exceed or fallbelow its alarm boundaries for 30 seconds before the alarm goes off.

Note: The alarm must be active at the end of the time delay.

Using time delays cuts down on the number of active alarms and reducesboth system traffic and operator responsibility by filtering out somenuisance alarms

AlgorithmFields

The other fields that appear on the Algorithms tab differ according to theAlarm Type selected on the General tab. The above figure reflects anExpression Alarm Type selection.



TAC 172

Algorithm Parameters for an Infinity High Limit Alarm

Infinity High Limit Alarms can be attached to the following Infinity objects:

• InfinityNumeric

• InfinityInput

• InfinityOutput

• InfinityDateTime

• InfinitySystemVariable

When you select Infinity High Limit from the Alarm Type of the General tab, thefollowing fields appear on the Algorithms tab.

This algorithm is used with Infinity points to report an alarm if the alarmed attribute valuechanges to a value that is equal to or above a high limit that you specify. You’ll alsospecify a value that the value must change to (or below) before a Return to Normal statecan be reported.

To Use an Infinity High Limit Algorithm:

1. Enter a high limit value in the text field marked High Limit.

2. Enter a return to normal value in the text field marked Return to Normal.

Algorithm Parameters for an Infinity Low Limit Alarm

Infinity Low Limit Alarms can be attached to the following Infinity objects:

• InfinityNumeric

• InfinityInput

• InfinityOutput

• InfinityDateTime

• InfinitySystemVariable

When you select Infinity Low Limit from the Alarm Type of the General tab, thefollowing fields appear on the Algorithms tab:

This algorithm is used with Infinity points to report an alarm if the alarmed attribute valuechanges to a value that is equal to or below a low limit that you specify. You’ll alsospecify a value that the value must change to (or above) before a Return to Normal statecan be reported.




To Use an Infinity Low Limit Algorithm:

1. Enter a low limit value in the text field marked Low Limit.

2. Enter a return to normal value in the text field marked Return to Normal.

Algorithm Parameters for an Expression Alarm

When you select Expression from the Alarm Type dropdown menu of the General tab,the following field appears on the Algorithms tab:

To enter an expression, type it into the text field.

How Do Expression Alarms Work?

An expression algorithm tests for a condition that is not within normal operatingparameters. This condition is defined using an expression such as:

ABS(VALUE - Point1) > 3

If the expression results in a value of TRUE, the associated point reports an alarm. If theexpression results in a value of FALSE, the associated point does not report an alarm.

Alarm Points in Expressions — Alarm points allow you to attach an expression alarmto multiple points. The expression on the Algorithms tab does this by including a "point"variable name, rather than an actual point name. When this expression alarm, in turn, isattached to an object (for example, an AnalogInput or a Door) the alarm references up tofour alarm points, which are named Point 1, Point 2, Point 3, and Point 4.

Alarm point configuration is performed via the Alarm Points dialog:

The Alarm Points dialog is accessed from the Alarms tab or Advanced Alarms tab ofthe following object editors: AnalogInput, AnalogOutput, AnalogValue, BinaryInput,BinaryOutput, BinaryValue, Door, InfinityInput, InfinityNumeric, InfinitySystemVariable,MultistateInput, MultistateOutput, MultistateValue, or Network. (See: Attaching Alarms to a Point , later in this chapter.)



TAC 174

Using alarm points saves you the trouble of having to change the expression every timeyou attach an expression alarm to a different point.

You must configure these alarm points when you attach an alarm to an object. That is,you must specify the actual point names for every alarm point the expression references.The referenced point, for example, can be an input-point temperature reading.

The AlarmEnrollment Feedback Tab

The Feedback tab lets you write text messages for the Active Alarm View list and theAlarm Bar and to associate an audio file with each event state.

TextMessages

You can write a different message for each possible event state, Alarm,Return to Normal and Fault.

Continuum supports ‘wild card’ characters ‘%n’ and ‘%d’, which insertsthe corresponding name and description of the alarmed object. For

example, “%n went into alarm” yields: “mytempsensor went into alarm.”A good text messages alerts operators to the nature and severity of thealarm. For example, “Temperature is too high” or “Door Forced Open.”

For more on Text Messages, see the next section, Writing Alarm Messages .

Audio Files Use audio files when you want a recorded message or sound to play onworkstations when an event is delivered.

You can associate a different file with each event state. This is useful foralerting and informing operators as to the specific and appropriateresponse for different event states.




Note: For every audio file you add to this tab, select the correspondingaction on the Actions tab of the associated EventNotification object.In other words, if you associate an audio file with Alarm, make surethe associated EventNotification object has Play Audio on Alarmselected on its Actions tab.

Note: Some EventNotification objects have audio files associated withevent states as well. When an AlarmEnrollment object with audiohas an associated EventNotification object with audio files, theAlarmEnrollment audio files take precedence.

Writing Alarm Messages

Use the Feedback tab to write the text message that will appear in the active list and theAlarm Bar. You can write a different message for each possible state: Alarm, Return to

Normal, and Fault. Good text messages alert operators to the nature and severity of thealarm.

To enter a text message, type it into the appropriate text field.

Using the Name and Description Fields of Objects as Alarm MessageText

You can create custom alarm messages with the %D and %N features of Continuum,without creating custom AlarmEnrollment objects for each Alarm, Return to Normal, orFault:

%D is like a shortcut to the Description field of the object to which the AlarmEnrollment isattached.

%N is like a shortcut to the Name field of the object to which the AlarmEnrollment isattached.

Use %D or %N in your text messages in the Alarm, Return to Normal, or Fault fields onthe Feedback tab to insert the Description or Name of the object in alarm. When a pointalarm, return to normal, or fault is generated, the message in Active Alarm View (seepage 10-180) displays the point Description field inserted in place of the %D characterand the point Name field inserted in place of the %N character.

Example: A motion detector is configured as an InfinityInput named "Motion3B" and has a

Description field entry "motion detect in 3rd fl comp lab, bldg B". An AlarmEnrollmentobject for an after hours motion alarm is created with the alarm text message, "%N, the%d, is in alarm. Call the security desk at 978 470-0555".

When generated, the alarm will read "Motion3B, the motion detector in the 3rd floorcomputer lab, building B, is in alarm. Call the security desk at 978 470-0555".

Note: This feature is case-insensitive. %D is the same as %d, %N is the same as %n.



TAC 176

Attaching Alarms to a Point

Once you have created the appropriate EventNotification and AlarmEnrollment objects, you need to open a point object editor. From the navigation pane of theContinuum Explorer:

1. Double click the Infinity controller that contains the points you want to alarm.

2. In the viewing pane of Continuum Explorer, right click the icon for the point, andselect Open from the drop down menu.

The object editor for that point will appear.

3. Select the Alarms tab (or Advanced Alarms tab on some object editors).

The Alarms tab (or Advanced Alarms tab) appears. For example:




Using the Alarms / Advanced Alarms Tab of an Object Editor

Use the Alarms tab (or Advanced Alarms tab) to browse for up to eightAlarmEnrollment objects to attach to the point.

To attach an alarm to an object:

1. Click the browse button in one of the empty alarm fields.

2. Search and find the alarm you want.

3. Click the Select button.

4. Check the Enabled checkbox.

To delete an attached alarm, select its name in the text field and press the Delete key onyour keyboard.

Graphic Click the browse button in the Graphic field to search for the desired graphicpanel that you want to appear when the alarm goes off. Select the pagenumber of the graphic panel you want first to appear.

Program Click the browse button in the Program field to search for the desired reportprogram or any other Plain English program to this object.

Note: You cannot select an HTML report directly. To associate an HTMLreport with an object, you must select a program that uses the

SHOWREPORT keyword to run an HTML report. An example of theSHOWREPORT keyword is:

SHOWREPORT “C:\PROGRAM

FILES\CONTINUUM\REPORTS\SYSTEMCHK.HTM”

AlarmPoints

Alarm points allow any expression alarm that you attach on this tab toreference up to four "alarm points," named Point 1, Point 2, Point 3, and Point4. Using alarm points saves you the trouble of having to change theexpression (via the Algorithms tab of the AlarmEnrollment editor for thatalarm object) every time you attach an expression alarm to a different point:



TAC 178

See: Algorithm Parameters for an Expression Alarm , earlier in this chapter.

To configure these alarm points for an attached expression alarm, click the

Alarm Points button to bring up the Alarm Points dialog:

Using the Alarm Points dialog, you must specify the actual point names forevery alarm point the attached expression alarm references. The referencedpoint, for example, can be an input-point temperature reading. (See also:Using an Expression Algorithm.)

Follow this procedure:

1. In the General tab of the AlarmEnrollment editor, for the alarm you wantto attach, make sure that you select Expression for the Alarm Type.Any attached alarm to which you want to apply alarm points must be anexpression alarm.

2. In the Algorithms tab of the AlarmEnrollment editor, enter the expressionin the Expression field. When you want to use alarm points, the alarmpoint name (point1, point2, point3, or point4) must be part of theexpression. For example:

...value > point1 + 2...

5. Save the AlarmEnrolllment object after making these expression-alarmchanges.

6. On this tab of this editor, click the Alarm Points button to search for andselect the name of an object for every alarm point referenced by attached

expression alarm. The Alarm Points dialog appears, showing fields




where you may specify up to four point names, Point 1 through Point 4.

7. Click the browse button in one of the point's fields.

8. Once you have found the point you want, click the Select button. Thatpoint specified in the field will be associated with that alarm point andapplied to the attached expression alarm, which references the point.

9. Click OK.

Video

Points

Click the Video Points button to bring up the Video Points dialog:

Use the Video Points dialog to assign cameras to doors and points andconfigure parameters that control video images, via VideoLayout objects,

during alarm conditions.When the alarm goes off, a video layout is launched (if a VideoLayout objecthas been configured to work with video points) and displays the "video point"

camera images in the its video image frames. In the Video Points dialog,you may also configure a camera to record a video clip, for specified numberof seconds, when the alarm goes off.

For complete information about video layouts and video configuration, pleasesee Chapter 25, Configuring and Viewing Video .

Use the Video Points dialog to assign between one and four "video point"cameras — point 1 through point 4.

Use the Video Servers dropdown menu to select a video server on which the

camera is located. (A VideoServer object must be already configured and theserver online. See Using the Video Server Editor in Chapter 25.)

Use the Cameras dropdown menu to select a camera for the numbered videopoint. (The camera must be configured and enabled on the selected videoserver.)

Check the Rec. checkbox to enable the recording of a video clip from theselected camera. Recording begins at the moment the alarm goes off.

In the Duration field, use the up and down arrows to select the number ofseconds to record a video clip, once you check the Rec. checkbox.

In the PTZ field, select the number of the preset camera view. (These PTZ



TAC 180

(pan, tilt, zoom) capabilities are configured on the Integral video servers,using Integral software. See Overview of Integration and Configuration inChapter 25.)

If you are associating a VideoLayout with the video points for this object,then you must first reference these video points from the General tab of theVideoLayout editor. (See Chapter 25.)

Active Alarm View

The active alarm view window displays a list of active alarms. From this window you canperform the following basic tasks:

• Respond to alarms

• View information about alarms to which other operators have already responded

• Organize alarm information

The active alarm view is displayed one of two ways:

• Alarm View mode

• Status Line mode

The Active Alarm view is never displayed in both modes ⎯ it is always in one or the othermode selected by the user.

The Alarm View Mode

To enter the Active Alarm View mode:

1. Right click the alarm icon in the Windows tool tray.

2. From the popup menu, select Alarm Viewer.

The Active Alarm View window appears on the screen:

Components of the Active Alarm View

The Active Alarm View window contains a menu bar, a tool bar, and a list of alarms. Ahorizontal scroll bar at the bottom of the view is used to expand the Alarm List in order tocover all the information provided for each alarm. (See The Alarm List , later in thischapter.)




The Menu Bar

Just beneath the Active Alarm View title bar is the menu bar. The menu bar consists ofthe following menus:

• ObjectUsing_the_Object_Menu>(w95sec)

• View

• Acknowledge

• Mute

•

HelpEach of these menus is discussed below.

The Object Menu

The Object menu options are not available in this release:

The View Menu

The View menu consists of the following options. A check mark to the left of a menuoption indicates that option is selected:

Menu Option Description

Toolbar Displays the tool bar when selected. Hides the tool barwhen not selected.

Status Bar Displays the status bar when selected. Hides the statusbar when not selected.

Sort Displays the Sort Criteria dialog, which defines thecriteria for sorting the contents of the active alarm view.

Auto Sort Automatically sorts the contents of the active alarm viewwhenever a new alarm is received, according to thecriteria defined in the Sort Criteria dialog.



TAC 182


Freeze Stops alarm list scrolling when selected. Allows alarm listscrolling when not selected.

Add/Remove Columns Allows you to add or remove columns from the ActiveAlarm View.

Always on Top Upon opening the active alarm view, places the windowon top of all other windows on your desktop. When youmake this selection, you are prevented from clicking on

any other window or process and bringing it in front of theActive Alarm View window.

Hide Hides the active alarm view. When the active alarm viewis hidden, the alarm view icon blinks in the alarm tray.

Alarm Status Line Places the Active Alarm View into status line mode. Thealarm that appears in the alarm status line is the firstalarm (at the top of the list) that either has not beenacknowledged or has been acknowledged but does nothave the Remove From Status Line When Acknowledgedbox checked in the event notification object assigned tothe alarm. In status line mode, the active alarm view listnever appears. Likewise, in alarm view mode, the alarm

status line never appears.Alarm Enrollment… Displays the alarm enrollment editor associated with the

selected alarm.

Event Notification… Displays the event notification editor that is associatedwith the selected alarm.

Object… Displays the object editor of the object that is associatedwith the selected alarm.

Program Output… Displays and runs the report program that is attached tothe object that is associated with the selected alarm.

Graphic… Displays graphic panel of the object that is associatedwith the selected alarm.

Video Displays the surveillance video monitor (the VideoLayouteditor) for the selected alarm when its point goes intoalarm. This is the VideoLayout attached to the point forthis alarm. (See Chapter 25, Configuring and Viewing Video .)





Alarm Function Executes a user-defined Plain English function for the selectedalarm, to make something special happen, regarding the alarm.The alarm's attributes are passed as arguments into thefunction, and the function runs.

Note: See your Continuum CyberStation Release Notesfor specific instructions on creating a custom, user-defined alarm function.

The Acknowledge Menu

The Acknowledge menu provides two methods for acknowledging alarms:


Ack Selected Selects a single alarm in the Active Alarm View list toacknowledge.

Ack All Selects all the alarms in the Active Alarm View list toacknowledge.

The Mute! Button

This selection on the tool bar acts as a button since there is no menu associated with it.Clicking on it will mute (turn off) the sound of an audio alarm selected in the Alarm List ofthe Active Alarm View.

The Help Menu

Clicking on Help and then selecting Contents from the drop-down menu will take you toContinuum’s extensive online help system.



TAC 184

The Tool Bar

The below table provides you with the descriptions of the different Alarm View tool baricons. The use of these icons is described throughout the following pages.

Click This Icon… To . . .

Print Screen. Not available in this release.

Acknowledge all alarms.

Acknowledge selected alarms.

Freeze the scrolling list of active alarms.or

Restart the scrolling of active alarms.

Mute audio alarms.

Run a report previously defined on the Alarms page of the objectthat caused the alarm.

Bring up the surveillance video monitor (the VideoLayout editor)when a point goes into an alarm. This is the VideoLayout objectattached to the point for this alarm. (See Chapter 25, Configuring and Viewing Video .)

Display a graphics panel previously selected on Alarms page of theobject that caused the alarm.

Execute a user-defined Plain English function for an alarm in thelist, to make something special happen, regarding the alarm.

Select (highlight) an alarm, and click this alarm-function icon. Thealarm's attributes are passed as arguments into the function, andthe function runs.

Note: See your Continuum CyberStation Release Notes forspecific instructions on creating a custom, user-defined alarmfunction.

Object. Displays the object editor that is associated with theselected alarm

Event Notification. Displays the event notification editor that isassociated with the selected alarm.




Click This Icon… To . . .

Alarm Enrollment. Displays the AlarmEnrollment orEventEnrollment editor associated with the selected alarm.

Auto Sort. Automatically sort the contents of the Active Alarm Viewwhenever a new alarm is received, according to the criteria definedin the Sort Criteria dialog, which is accessed via the View menu.

Access the Help topics for Active Alarm View.

The Alarm List

The Active Alarm View displays the following information about each alarm appearing inthe Alarm List:

Column Heading Column Contents

Date/Time Date and time the alarm occurred.

Name Name of the object that triggered the alarm.

Value Value of the object that triggered the alarm.

To State State

Priority Priority number assigned to the alarm on the General tab of

the AlarmEnrollment object.

Type Type of alarm that was selected on the General tab of theAlarmEnrollment object.

Message Message typed in on the Feedback tab of theAlarmEnrollment object.

Event Notification Name of the EventNotification object.

Alarm Enrollment Name of the AlarmEnrollment object.

Operator Text Text entered by the operator to further explain actions takenin response to the alarm. An alternative is for the operator toclick the text field column of the alarm and type text in that

Alarm Viewer field.User Actions Dropdown menu of actions taken in response to each alarm.

Acknowledged By User name of the person who acknowledged the alarm. Thisis filled in automatically when the alarm is acknowledged.

Date/Time ofAcknowledgement

Date and time the alarm was acknowledged. This is filled inautomatically when the alarm is acknowledged.

Silenced By User name of the person who silenced the alarm. This isfilled in automatically when the alarm is acknowledged.



TAC 186

Column Heading Column Contents

Date/Time ofSilence

Date and time the alarm was silenced. This is filled inautomatically when the alarm is silenced.

Forcing the Alarm View to Display via Popup Menu

The Show on Active Alarm selection, located under Options in the alarm icon’s tooltray popup menu, allows you to force the active alarm view to display whenever an activealarm is triggered. To do this:

Right click the alarm icon in the tool tray, then select Options:

Show on Active Alarm is checked by default, so you must deselect it when you do notwant the active alarm view to display on an active alarm.

Selecting this option overrides the event notification for the active alarm, whenever theEvent Notification editor’s Display Alarm View option for the alarm is not selected.

Note: When neither the Show on Active Alarm option nor the EventNotification editor’sDisplay Alarm View option is selected for the active alarm, the active alarm view is notdisplayed. Instead, the alarm icon in the tool tray flashes.

The Status Line Mode

To enter the Active Alarm View mode:

1. Right click the alarm icon in the Windows tool tray.

2. From the popup menu, select Display and Alarm Status Line.

3. The Active Alarm Status Line appears in the Alarm Bar at the bottom of the

Continuum Explorer window.

When the active alarm view is in status line mode, the Active Alarm View windowdisappears.

In Status Line mode, the alarm that appears in the status field:

• Is the first alarm that would appear at the top of the Active Alarm View list.

• Has not been acknowledged.

• Has been acknowledged but does not have the Remove From Alarm Line onAcknowledged box checked in the Actions tab of the EventNotification editor.




You can also select the Status Line mode from the View menu by clicking on AlarmStatus Line.

In Status Line mode, you can right click the alarm icon in the Windows tool tray toaccess its context popup menu.


Hide Hides the status line.

Alarm Viewer Switches from status line mode to alarm view mode, displaying thecomplete active alarm view list.

Always on top Upon opening the active alarm view, places the active alarm viewwindow on top of all other windows on your desktop. When youmake this selection, you are prevented from bringing any otherwindow or process to the front of the active alarm view window.

To return to the Active Alarm View, click the alarm icon located at the right of theStatus Line field.

Working With the Features of the Active Alarm View

The Active Alarm View is designed to help you respond to and document the results ofeach alarm quickly and easily. You can perform the following tasks directly from theActive Alarm View:

Stop and StartScrolling theAlarm List

New alarms appear in the Active Alarm View as they occur. Whenthis happens the alarm list scrolls down to make room for newalarms. If you need to concentrate on a particular alarm, you canmomentarily stop the scrolling. This allows you to silence, addinformation or acknowledge that alarm without having to constantlyscroll up to find it. When you have finished working with the alarm,you can restart the scrolling. There are two methods for stopping

and starting the scrolling alarm list:

Click the icon in the Active Alarm View tool bar. The icon,

which resembles a traffic light, changes from a green to a red light,shown below:

Click this icon to resume scrolling, or select Freeze from the

View menu. Deselect it to resume scrolling.



TAC 188

Silence Alarms When an operator silences an alarm, it is silenced on all recipientworkstations and is logged in the alarm log. The User name, anddate and time of silence appear in the Silenced By and Date/Time of Silence columns of the Active Alarm View.

To Silence an Alarm:

Click the button to the left of the alarm. You don’t need toselect the alarm first. Once you have silenced an alarm, you cannot "un-silence" it. You should continue the recommended

acknowledgement process if you are playing audio files. Select theactions that have been taken in response to alarms.

Note: If an alarm is silenced when CFR is active, the user will beprompted to add comments. See Enabling Operator Text Prompt for Alarm Acknowledgement in Chapter 5.

DisplayGraphic PanelsAssociatedwith AlarmedObjects

Some alarms have an associated graphic panel. The panel helpsoperators view the source of the alarm, and in some cases, operatethe controls necessary to abate the alarm. To display an alarm’sassociated graphic panel, select the alarm by clicking on it. Next,

click the icon in the Active Alarm View toolbar.

or

Click Panel in the menu bar. Not all alarms have associatedpanels.

Running ReportPrograms

Some alarms have an associated report program. Although alarmreports vary depending on the programs that generate them, alarmreports commonly print or display information relating to the alarm.To run an alarm associated report program, select the alarm by

clicking on it. Next click the icon in the Active Alarm View

toolbar.

or

Click Program Output in the drop down View menu on the MenuBar.

Note: For you to run a report program, via this method, a programmust be attached to the point that is goes into the alarm.




AcknowledgingAlarms

Acknowledging an alarm lets other operators know that you haveseen the alarm and have taken the appropriate actions. When youuse one of the following methods to acknowledge an alarm, youruser name will appear in the alarm’s Acknowledged By column.

Note: Version 1.51 of Continuum provides the option in the CFRPreferences dialog to require operator response in the form ofexplanatory text whenever an alarm is acknowledged. See Enable Operator Text Prompt for Alarm Acknowledgement in Chapter 5 fordetails.

Click the ACK button to the left of the alarm that you wish toacknowledge.

or

Select an alarm by clicking on it, then click the Acknowledge

icon in the tool bar.

or

Click the Acknowledge all alarms icon in the tool bar to

acknowledge all active alarms in the list.

Note: If the “Enable Operator Text Prompt for Alarm

Acknowledgement” value is set to “True” in the CFR Preferencesdialog, (see Note, above) the Acknowledge all alarms options willbe disabled.

or

Select Ack Selected from the Acknowledge menu instead ofclicking on the icons mentioned above.

Viewing Alarm Information

No matter who responds to an alarm, the Active Alarm View columns allow all operatorsto view the following details:

Who Silenced the

Alarm?

Look in the Silenced By column for the user name of the

operator who silenced the alarm. This information can beverified in the Alarm Log.

What Action WasTaken?

Look in the User Action and Operator Text columns to seewhat action was taken by the person who silenced oracknowledged the alarm. This information can be verified in theAlarm Log.

Who Acknowledgedthe Alarm?

Look in the Acknowledged By column to see the user name ofthe operator who acknowledged the alarm. This information canbe verified in the Alarm Log.

You can also view the details of any alarm in the Details View dialog.



TAC 190

Displaying the Details View of an Alarm

If you want a quick way to look at alarm information without scrolling from side to side,double left click the mouse on the selected alarm. The Details View dialog shown belowcomes onscreen.

From Details View you can:

Display the following objects associated with the alarm:

• Alarmed object

• EventNotification object

• AlarmEnrollment object

• Acknowledged by user object

• Silenced by user object

Type messages to the Operator Text field. Entering operator text is an optional task youcan perform when responding to alarms. You can enter text that:

• Provides additional information about the alarm

• Describes the result of the action you took in response to the alarm

• Describes a user action not found in the User Action list

To enter operator text:




1. Enter comments in the Add field.

2. Click the Add button. The comments you have entered in the Add field now appearsin the Operator Text field.

or

In the Active Alarm View, click the Operator Text field for the alarm you want toenter text about.

3. Type in the desired comments.

4. Click the ACK button.

Creating a List of User Actions

Before you can select from a list of user actions, you or someone in your company willhave to create the list. To do this, create a text file named Alarm User Actions.txt.In this file, make a list of as many user actions as you like. Type each action on its ownline, as shown below:

• Repaired the unit

• Shut down the unit

• Called the fire department

• Started evacuation procedure

• Notified building security

• Confronted the intruder

• See Operator Text column

The order in which you type the actions determines the order in which the actions willappear in the dropdown menu.

Save or copy Alarm User Actions.txt to the following directory: Program Files\Continuum\

Tip: A complete list of user actions should include an entry such as See Operator Textto provide for unanticipated user actions. By providing this action, the respondingoperator need not leave the User Action column blank when special circumstancesarise. Additionally, directing other operators to the operator text avoids anyconfusion as to the action that was taken.

Select a User Action

Selecting a user action for an alarm lets other operators know what has been done inresponse to that alarm.

Locate the alarm in the Active Alarm View to which you would like to respond. Click theSelection control in the User Actions field to display the list. Click the user action of yourchoice.

You may also make your selection from the Details View of the alarm.



TAC 192

Note: If after displaying the list of user actions, you don’t see an action that accuratelydescribes your response to the alarm, type the action you took in the Operator Textcolumn or in the alarm Details View.

Click the ACK button to acknowledge the alarm and save the entries for Operator Textand User Actions.

Click the Cancel button to take no action here for the alarm.

Muting Workstation Alarms

Audio alarms play the audio files (.wav) selected in the EventNotification and/or AlarmEnrollment objects. When an audio alarm is triggered, the audio file plays on alldesignated recipient workstations. Some audio alarms are sent to loudspeakers.

Continuum’s Active Alarm View has a mute function that lets you turn off the sound ofalarms. Muting alarms stops the current sounds from playing on your workstation andconnected loudspeakers only. A mute is logged as an activity.

Important Note: Muting alarms is NOT the same as silencing an alarm.

MutingAlarms

There are three ways to turn off the sound of currently playing audio alarms:

Click the mute icon in the Active Alarm View toolbar

Click the mute icon in the Alarm Bar

Click Mute! in the Active Alarm View menu.

Configuring Alarm Messages in the Device Editor

There are six text (see below) files that can be configured in any editor and are assignedin the Preferences tab of the Device editor. (See Chapter 14.) The contents of thesefiles can contain any text (including HTML) and predefined XML tags that are used tosubstitute live alarm data automatically. You can use these XML tags to customize alarmmessages for:

• Printers

• Emails

• Pagers

Name Default value Purpose

NormalEmail normalemail.txt Alarm/RTN/Fault email messageNormalPager normalpager.txt Alarm/RTN/Fault pager message

NormalPrinter normalprinter.txt Alarm/RTN/Fault printer message

AcknowledgeEmail acknowledgeemail.txt Acknowledge email message

AcknowledgePager acknowledgepager.txt Acknowledge pager message

AcknowledgePrinter acknowledgeprinter.txt Acknowledge printer

Modifications to all these files will not take effect until Continuum is shut down andrestarted. The following table provides the predefined XML tags and their descriptions.




XML Tag Description

<\date> The date of the alarm.

Example: Tuesday, June 19, 2001

<\time> The time of the alarm.

Example: 4:37:59 PM

<\name> The name of the infinity object that generated the alarm.

<\value> The current value of the alarm.

Example: 190.00

<\state> The state of the alarm. The value can be alarm, return to normal,acknowledged, or fault.

<\priority> The current priority of the alarm.

<\type> The type of alarm that was triggered.

Example: “Continuum High Limit”

<\message> The message of the alarm. For alarms, this currently returns“alarm.”

<\eventnotification> The name of the event notification for this alarm.

<\alarmenrollment> The name of the alarm enrollment for this event.

<\operatortext> The operator text for this alarm (set by those who acknowledgedthis event.)

Organizing Alarm Information

The Active Alarm View provides so much information that you may want to make somechanges to make it easier to find the information you need most often. For example, youmay want to hide information you do not need, move the columns you read most to theleft, or change the order of the alarms to highlight certain trends. The follow list containsdifferent ways to organize alarm information.

• Hide or add columns of information

• Rename columns

• Move columns

• Resize columns

• Change the alarm sort order

Adding or Hiding an Alarm View List Column

1. To add or hide a column to the Active Alarm View Alarm list, put the cursor on anycolumn heading and right click the mouse to display a popup menu.

2. Click Hide or Add.



TAC 194

3. Select the checkbox for the column you want to add or hide in the alarm list.

4. Click OK.

Renaming an Alarm View List Column

To rename a column:

1. Right click the column heading to be to display a popup menu.

2. Click Rename Heading.

3. Type the new column name in the pop up dialog that appears.

Justifying an Alarm View List Column

To change the justification of a column entry:

1. Right click the column heading to be to display a popup menu.

2. Click Justify and select Left, Right or Center justification.

Formatting the Name ColumnTo determine the format of the entry that will appear in the Name column, put the cursoron the Name column heading and right click the mouse to display the above menu. ClickFormat to display the following menu and select the desired name format to appear inthe Active Alarm View.




Resizing Columns

Use the mouse to change the width of the Active Alarm View columns. Place your mouseon the vertical line that separates two columns:

Your cursor will change to look like this , indicating that you can move the column

boundary to the left or right.

Understanding Sort Order

For every column by which you sort, you’ll specify whether it’s the primary, secondary, ortertiary (third) column in the sort order. The sort order defines what happens when theActive Alarm View finds two or more alarms that have the same column values. Forexample, if the primary sort column is Name, how does the Active Alarm View order twoalarms for objects named RoomTemp1? Which one is listed first? If another column hasbeen set up as the secondary sort attribute, the Active Alarm View uses the value of thatsecond column to decide which alarm is listed first. The tertiary sort attribute works thesame way. That is, if the Active Alarm View finds two or more alarms with the same

primary column value and the same secondary column value, it uses the tertiary columnvalue to decide how to list the alarms. For example, the alarms listed below are sorted inascending order by Name, then by Value, then by To State.

Name Value To State

Door1 Unlocked Alarm

Door4 Locked Alarm

Door4 Locked Return to Normal

RoomTemp1 72 Return to Normal

RoomTemp1 85 Alarm

In our example, Name is the primary sort column, Value is the secondary sort column,

and To State is the tertiary sort column. First notice that the first three alarms are sortedby name. Next, notice that the two Door4 alarms are sorted by To State value becausethe values in the primary and secondary columns, Name and Value, are identical. Finally,notice that the RoomTemp1 alarms are sorted by value because they have the samename.

Tip: Sort order does not affect the order of your columns. For easier reading, wesuggest positioning your columns by their sort order. In other words, make sureyour primary column is the first column, the secondary column is the secondcolumn, and the tertiary column is the third.



TAC 196

Changing Alarm Sort Order

You can sort alarms by the values of up to three columns. This is useful for groupingalarms to look for trends in, for example, the source of alarms, types of alarms, and whichoperators are responding most often. You’ll select which columns to by which to sortalarms in the Sort Criteria dialog shown below.

To Sort Alarms by Columns:

1. Select Sort from the Active Alarm View menu to display the Sort Criteria dialog.

2. Select up to three columns from the Primary, Secondary and Tertiary dropdownmenus.

The columns you select establish the sort order that the Active Alarm View needs tosort by more than one column.

3. Click the Ascending checkbox to sort in ascending order, or clear it to sort bydescending order (see below).

4. Click OK.

Sorting in Ascending or Descending Order

For every column by which you sort, you’ll specify either ascending or descending order(step 3, above). Ascending order starts with the lowest value and ends with the highestvalue.

For time values, ascending order places the oldest events on top, descending orderplaces the most recent events on top.

For text, ascending order is A to Z. For numbers ascending order is 0 to the highestnumeric value. Descending order starts with the highest value and ends with the lowestvalue. For text, descending value is Z to A.

For numbers, descending value is the highest value to 0. Note that column values suchas Active, Inactive, ON, OFF, Online, Offline, Enabled and Disabled are represented toContinuum by 1 and 0 respectively. These values will be sorted just like numeric values.

Infinet Intrinsic Alarms

When an intrinsic alarm occurs, the notification of an alarm is done in the Explorer’sNavigation pane and also in the Active Alarm View as described in this section.




The following four conditions cause an intrinsic alarm notification to occur.

• Communication Status

• Database Backup Needed (Infinet 2 devices only)

• Database Backup Disabled (Infinet 2 devices only)

• Database Backup Failed (Infinet 2 devices only)

The table below provides a description of the intrinsic alarm conditions.

Note: Intrinsic alarms conditions are cleared both automatically and manually.

AlarmCondition

Cause of Alarm Where is AlarmDisplayed

Return to NormalCondition

CommunicationStatus

The NetControllerdetecting the Infinetcontroller is offline.

In the Active Alarm Viewif the Infinet StatusEvent Notificationtemplate object wasconfigured.

The NetControllerdetecting the Infinetcontroller is online.

DatabaseBackup Needed

The Infinet 2 devicedatabase needs tobe backed up.

The alarm is logged tothe object statusdictionary attribute. TheExplorer displays anoverlay icon and tooltip

text based on thisattribute. To read thetooltip, hover yourmouse over the icon.

When the databasehas successfullybeen backed upand the Explorer isrefreshed and

removes theoverlay icon andtooltip text based onthis attribute.



TAC 198

AlarmCondition

Cause of Alarm Where is AlarmDisplayed

Return to NormalCondition

DatabaseBackupDisabled

The Infinet 2database has beenbacked up 10,000times, thustriggering the flashcircuit breaker.

The alarm is logged tothe object statusdictionary attribute, andan alarm is displayed inthe Active Alarm Viewusing the InfinetStatusEvent Notification

template object. Themessage displayed is:

Backup disabled due to excessive use (Requires manual enable).

The Explorer displaysan overlay icon andtooltip text based on thisattribute.

You have tomanually re-enablethe backup. Also,the alarm is loggedto the object statusdictionary attribute,and an alarm is

displayed in theActive Alarm Viewusing theInfinetStatusEventNotificationtemplate object.The messagedisplayed is:

Backup re-enabled .

The Explorerdisplays an overlayicon and tooltip text

based on thisattribute.

DatabaseBackup Failed

An attempt wasmade to back upthe Infinet 2database, but wasnot successful dueto an internal error(e.g., flash devicefailure).

In the Active AlarmView using theInfinetStatusEventNotificationtemplate object. Themessage displayed is:

Unable to backup controller due to unknown failure.

The database hassuccessfully beenbacked up. Also, thealarm is displayed inthe Active AlarmView only if theInfinetStatus EventNotification templateobject wasconfigured. Themessage displayed

is:

Backup failure corrected; backup completed.




Other Conditions that Cause an Intrinsic Alarm Notification

In addition to the above four intrinsic alarms, the following conditions will also cause anintrinsic alarm notification to occur:

• Offline editing

• OS update failure

• When a “Save from Controller” is required

Database Fault Detection AlarmConfiguration Requirements

Continuum automatically responds to database faults. There are no configurationrequirements involved in order to have the system detect, respond to, and recover from adatabase fault. However, you must be specified as a recipient in the FaultStatusEventNotification template object in order to receive the database fault alarm.

The workstation DatabaseStatus system variable settings on the Basic Alarms tab areshown below. Normally, you should not need to edit it, since it is configured this way bydefault.



TAC 200

Database Faults

A database fault occurs whenever there is a problem accessing information from thedatabase. This can happen for two reasons:

• The connection between the Continuum workstation and the SQL database becomesdefective.

• The SQL database server is experiencing problems.

Fault Detection

When a database fault is detected, the system is set into a "warning state for fiveseconds while the fault is verified. If the fault continues past that time, the system entersa "no database mode". (It may take up to 2 minutes to verify the database fault.) When

this occurs an icon will appear in the Explorer task bar at the bottom right-handcorner of the screen and a fault dialog will popup. A database fault message is written tothe NT Event Log (see below) stating that the system has entered a "no database mode".

Both the icon and the dialog will remain until the system recovers from the fault.However, clicking on the OK button will remove the dialog from the screen and send anentry to the NT Event Log (see below) stating that the dialog was acknowledged. Also, adatabase fault alarm will be displayed in the Active Alarm View window.

Emails (optional) can be sent out to notify selected users that there is a database fault.This requires that the FaultStatus EventNotification object be configured with a recipient.

If you log off the system during the "no database mode" a message is written to the NTEvent Log indicating your action.

Message: DATABASE FAULT! Continuum workstation is unable to communicate

with the Continuum database server. The database may be offline, or the

network connection to the server may be down.




ConfiguringReports

With version 1.7 and higher, CyberStation provides a powerful, versatile, graphical suiteof features, called Reports, that allows you to gather, view, and compare data values,locally or remotely, manually or automatically, from virtually anywhere in your Continuumsystem.

Overview

This section provides an overview of Reports and the Report editor. Specifically:

• What can I do with Reports?

• What is the Report editor?

• What is the ReportViewer?

• What are preconfigured vs. ad hoc reports?

• Before getting started — activating reportsNote: To use any of the report features, your users must be given access to these

features via the Security editor.

What Can I Do with Reports?

Using Reports, you may collect and filter data from a multiple number of dynamicbuilding-control data sources (including extended logs) then display this data ingraphically attractive bar charts, pie charts, trend charts, or columned text charts. Withreports, you can:

• Display report data using one of several data formats.

• Display two or more reports simultaneously.

11



TAC 202

• Modify report configurations on the fly while viewing them.

• Schedule reports to run automatically at a specified time.

• Save a report to a file, manually and/or automatically.

• Email a report, manually and/or automatically.

• Print a report.

What Is the Report Editor?

The Report editor is a powerful editor that you use to configure the class object, Report ,

allowing you to:

• Select a report data source and report type, including a point's current value,extended log data, activity events, access events, alarms, and errors. (See: SourceTab.)

• Select a chart type, including plotted trend charts, bar charts, pie charts, and textreports. (See: Source Tab.)

• Filter point-object data that you want to show in the report, based on day/time, andvarious object characteristics. (See: Filter Tab.)

• Build and modify a list of member objects, whose values you want to display in thereport. (See: Filter Tab.)

• Configure the "look and feel" of the report's output text headings, text captions, plotand scale configuration, and so on. (See: Output Tab.)

• Specify the data format you wish to display — for example, Adobe PDF and webformats. (See: Output Tab.)

• Specify how you wish to distribute a report automatically — to email addresses, to aprinter, to a file, and so on. (See: Output Tab and Scheduling Automatic Reports.)

• Configure, add, and remove columns for text reports. (See: Configuring Columns for Reports.)

What Is the Report Viewer?

When you run a report (easily accomplished via the Report editor or by double clicking ona Report object) the report is displayed in a special application window, called theReportViewer . The ReportViewer allows you to:

• View data via one of several data formats, such as HTML, XML, scalable vector graphics (SVG), and PDF.

• View multiple reports.

• Email, print, save, or reload the report you are viewing.

• Zoom in, zoom out, and adjust the view of the chart you are viewing.

• For more information, please see the help topic for the ReportViewer.




What Are Preconfigured and Ad Hoc Reports?

At any given time, you work with reports using one of two general methods:

• Preconfigured reports

• Ad hoc reports

Preconfigured reports — If you need to view report data for a specific set of valuesregularly, and the data sources, report type, output setup generally remain the same,then configure a Report object that can be accessed, run in the ReportViewer, and/or distributed at any time, manually or automatically. In Continuum Explorer, Report objectfiles are placed in a Report object class folder, as other CyberStation objects are. Withpreconfigured reports, you may modify the configuration at any time.

To create/modify a preconfigured report:

1. In Continuum Explorer, right click a folder or device, and select New, and then selectReport, from the popup menu.

2. Enter a name for the Report object, and click the Create button. The Report editor appears.

3. Configure the Report object, using the Source, Filter , and Output tabs, and clickApply or OK.

Note: To modify an existing Report object, right click the Report object in Explorer,

and select Edit from the popup menu. Also, while in the ReportViewer, youmay edit the parent object of the displayed report, thereby bringing up theReport editor.

4. To preview/run the report, click the View Report button. The report appears in theReportViewer as you configured it.

Ad Hoc Reports — If you need to view reports on the fly, without creating a Reportobject, then you may quickly locate the point (for example, an Infinity input) and run areport on it. Use ad hoc reports when you know you do not need to run a report regularly,when a Report object is not already created for the data you need to see.

To create/modify an ad hoc report:

1. In Continuum Explorer, find the location of the point or points whose values you want

to display in a report.2. Right click the object.

3. From the popup menu, select View, then Report. The Report editor appears.

4. Configure the ad hoc report for that object, using the Source, Filter , and Outputtabs.

5. In the Filter tab, be sure to add additional objects to the object member list, if necessary.

6. Click Apply, then click View Report.

The report appears in the ReportViewer as you configured it.



TAC 204

Note: As an option, you may save the ad hoc report to a file. (See: Output Tab.)

Before You Get Started – Activating Reports

Before using reports in CyberStation, you must activate reports in the CyberStationinstallation (database initialization) process in version 1.7 or higher. CyberStationsupplies many Report templates that include bar-chart templates, pie-chart templates,and trend templates — giving Reports a certain default "look and feel." To use thesetemplates (and thus, reports in general) you must import them during the CyberStationinstallation process, in version 1.7 or higher. In the Database Initialization dialog, you

must check the Create/Update Graphical Report Settings checkbox. (For moreinformation, please see the CyberStation Installation Guide, 30-3001-720.) If you do notcheck this checkbox then reports are not available.

Since some reports use extended-log data, please be aware that there are tasksindirectly related to extended logging. These are:

• Choosing extended logging backwards compatibility, so that "old" (pre-Version 1.7)extended logs are used with “new” reports based on extended-log data. This is donein the database initialization procedure.

• Configuring several General Preference settings (6, 7, 8, and 9).

• Designating one or more workstations to upload extended log data from the controller to the CyberStation database, via settings 21 and 22 of the Preferences tab of Device editor.

For complete information, please see the subsection, Extended Logs, in Chapter 13, thedescription of the Device editor’s Preferences tab in Chapter 14 and the Andover CyberStation Installation Guide, 30-3001-720.

Source Tab

In the Source tab, shown below, you select the source and type of data on which youwant to report — for example, extended log data, alarm event data, error event data, andso on. You also select the type of chart on which to plot your data — for example, piechart, bar chart, trend chart, and so on. The settings on this tab work together with thesettings on the other tabs of the Report editor (Filter and Output) to define the content of the report, before you run it in the ReportViewer.




Source Tab Attributes

The following table describes the attributes on the Source tab.

Editor Attribute Meaning

Description Enter a text description of this Report object. Since thisdescription may be used in an actual report output, be creative.

Data Source From the dropdown menu, select one of the following sources of data, on which you want to report:

• CurrentValue – This is a snapshot of the current value of anobject at any given time. This includes any object that has avalue.

• ExtendedLog – This is a collection of additional point values,uploaded from a log on a controller to a workstation'sCyberStation database. It is an extension of a "local" log,whose values are stored on a point's controller. Typically,Extended-log is selected for LAN controllers. See theextended log settings in the General Preferences dialog.

See also: What Are Extended Logs? and descriptions of theLogs tab in the InfinityDateTime, InfinityInput, InfinityOutput,InfinityNumeric, and InfinityString editors.

• Refreshed-Extended-Log — The extended-log values areupdated or "refreshed" immediately — uploaded from thecontroller to the workstation's database — before they appear in the report. Use this data source when you want to see the



TAC 206


most "up-to-the-minute" extended log entries, not the entriesbased on the last specified update interval. Typically, this isused for remote (RAS) controllers, which require dial-upaccess for database uploads. See the extended log settingsin the General Preferences dialog.

See also: What Are Extended Logs? and descriptions of theLogs tab in the InfinityDateTime, InfinityInput, InfinityOutput,InfinityNumeric, and InfinityString editors.

• AccessEvent — This is data associated with access attempts.There are many types of access-event data from which tochoose. For example, you can see "most accessed doors" or "most active persons". Please see the section, Matching DataSources, Report Types, Chart Types, and Chart Subtypes,later in this chapter. The names of these access events areself-explanatory.

• AlarmEvent — This is data associated with system alarms.There are 22 available types of alarm data from which tochoose. For example, you can see "most active alarmedobjects" or "active alarms under a network". Please see thesection, Matching Data Sources, Report Types, Chart Types,

and Chart Subtypes, later in this chapter. The names of thesealarm events are self explanatory.

• ActivityEvent — This is data associated with systemactivities. There are 11 available types of activity data fromwhich to choose. For example, you can see "login attemptsper user" or "most common activities". Please see thesection, Matching Data Sources, Report Types, Chart Types,and Chart Subtypes, later in this chapter. The names of theseactivity events are self-explanatory.

• ErrorEvent — This is data associated with system errors.There are six available types of error data from which tochoose. For example, you can see "error events per workstation" or "most common errors". Please see the

section, Matching Data Sources, Report Types, Chart Types,and Chart Subtypes, later in this chapter. The names of theseerror events are self-explanatory.

• ListView — This is the content of a ListView object, whichyou specify in the member object list on the Filter tab. Thissource has only one Report Type (ListView) and can oneChart Type (Text). Please see the section, Matching DataSources, Report Types, Chart Types, and Chart Subtypes,later in this chapter.

The text report that is generated looks similar to aCyberStation ListView.





Note: When you select this source, the Configure Columns buttonis unselectable. The columns of the ListView object areduplicated in the text report. To configure the ListViewreport columns, do so from the ListView editor.

Note: On the Filter tab, only one ListView object is selected.

Note: The selections in the other three fields, Report Type, ChartType, and Chart Subtype, change, depending on whichData Source you choose. Please see the section, MatchingData Sources, Report Types, Chart Types, and ChartSubtypes, later in this chapter.

Report Type This narrows down the type of data on which you want to report,based on the Data Source. Select a report type from thedropdown menu.

There are many report types available, for many different eventscenario. This makes Reports a very powerful and useful tool.

If you choose ExtendedLog or Refreshed-Extended-Log, thenthree report types are available:

• The object value

• The minimum and maximum object values

• The average object value

The CurrentValue has two report types, the snapshot of anobject's value at any given time or the snapshot of a TrendLogbuffer content.

The other data sources have many report types from which tochoose. For a list,

please see: Matching Data Sources, Report Types, Chart Types,and Chart Subtypes, later in this chapter. The names of thesereport types are self-explanatory.

Note: The selections in the remaining fields, Chart Type andChart Subtype, change, depending on what you choose.See the table below.

Maximum number of values in thereport

Enter an integer, representing the maximum number of values toplot in your report when you run it. The default is 100. You mayneed to experiment with this number to get the right amount of plotted data so that it makes the most sense, visually.



TAC 208


Chart Type Depending on which Data Source and/or Report Type, select Bar,Pie, Text, Trend, Minmax, or Clustered Bar, from the dropdownmenu. Please see the section, Matching Data Sources, Report Types, Chart Types, and Chart Subtypes, later in this chapter.

Chart Subtype Select the subtype compatible with your Chart Type. The Textchart has two subtypes available. All the others have one. Pleasesee the section, Matching Data Sources, Report Types, Chart Types, and Chart Subtypes, later in this chapter.

Note: When you select the Chart Type, the box on the right-hand side of the Source tab displays a graphic example of what this type of chart will look like. For example, if you select a pie chart, a pie graphic appears. If you choose aClustered Bar chart, a clustered bar graphic appears.

Configure Columns Click this button to launch the Selectable Columns dialog andadd, remove, and sort columns for your report. The columnsthat are available for any given report change, depending onhow you configure the Source tab. This applies only to textreports. (See Configuring Columns for a Report , later in thischapter.)

View Report Click this button to run your report, based on all the criteria you

have configured in the entire Report editor. When you run areport, it is displayed in the ReportViewer. (See TheReportViewer , later in this chapter.)

Apply Click this button to save your Report configuration changesimmediately, while remaining in the Report editor. (Click OK tosave changes and dismiss the Report editor.)

Matching Data Sources, Report Types, Chart Types, and ChartSubtypes

When you select a data source, certain report types become selectable. In turn,depending on the Data Source/Report Type combination you choose, certain chart typesand chart subtypes become selectable.

The table on the next page shows you which reports are available on the Source tab,depending on the combination you select.

Note: Two report types, Snapshot-of-object value and Snapshot-of-Trend-Log-buffer-content, are available for the CurrentValue source.

Note: A "clustered" bar chart is a special two-dimensional chart, where a member objectis associated with one or more related objects — for example, when you select aReport Type like Alarms-for-an-event-object-with-event-notification or Most-active-persons-entering-selected-door. In this bar chart, therefore, the "associated"objects are displayed next to (or "clustered" with) their member object.




To differentiate the member-object bar from its "satellite" object bars, theReportViewer displays each bar in the cluster in a different color. TheReportViewer also displays a color key at the bottom of the report, listing thecolor, name, and type of object in the cluster.

Data Source REPORT TYPE ChartType

ChartSubtype

Bar AccBarChart

Pie AccPieChart

Snapshot-of-object-value

Text AccTextHtmlAccTextXML

Trend AccTrend

CurrentValue

Snapshot-of-Trend-Log-buffer-content


Trend AccTrendObject-value

Text AccTextHtml AccTextXML

Minmax AccMinMaxMin-max-of-object-value


Bar AccBarChart

Pie AccPieChart

ExtendedLog

Average-of-object-value


Refreshed-Extended-Log Same as ExtendedLog



TAC 210


ChartSubtype

Bar AccBarChart

Pie AccPieChart

Most-accessed-doors

Most-accessed-areas

Most-accessed-controllers

Most-active-persons

Access-events-per-person

Access-events-per-area

Access-events-per-door

Invalid-attempts-of-a-person

Invalid-attempts-of-a-door

Invalid-attempts-of-an-area

Valid-and-invalid-attempts-of-a-person

Lock-unlock-events-per-door

Channel-override-events-per-door

Persons-accessed-the-selected-area

Areas-accessed-by-the-selected-person

Access-equipment-fault-report


ClusteredBar

AccClusteredBar

Door-use-by-person

Area-use-by-person

Controller-use-by-person

Most-active-persons-entering-selected-area(s)

Most-active-persons-entering-selected-door(s)


Bar AccBarChart

AccessEvent

Access-events-under-a-controller






ChartSubtype

Bar AccBarChart

Pie AccPieChart

Alarm-transitions-per-object

Most-active-alarmed-objects

Offline-alarms-per-controller

Offline-alarms-per-IOU-module

Offline-alarms-per-field-controller

Most-alarm(s)-acking-workstation

Most-alarm(s)-silencing-workstation

Most-alarm(s)-logging-workstation

Most-alarm(s)-acking-user

Most-alarm(s)-silencing-user

Active-alarms-under-a-controller

Active-alarms-under-a-field-controller Active-alarms-per-object

Active-alarms-under-a-network

Most-offline-IOU

Most-offline-controller

Most-offline-field-controller

Active-unACKed-alarms-per-controller


ClusteredBar

AccClusteredBar

AlarmEvent

Alarms-for-an-event-object-with-alarm-enrollment

Alarms-for-an-event-object-with-event-notification

RTNs-for-an-event-object-with-alarm-enrollment

RTNs-for-an-event-object-with-event-notification




TAC 212


ChartSubtype

Bar AccBarChart

Pie AccPieChart

ActivityEvent Activity-events-per-object

Login-attempts-per-user

Failed-login-attempts-per-user

Failed-login-attempts-per-workstation

Objects-created/saved-events-per-user

Most-common-activities

Activity-events-per-activity-type

Activity-events-per-workstation

Activity-events-per-controller

Activity-events-per-controller-with-children

Activity-events-per-user

Text AccTextHtml

AccTextXML

Bar AccBarChart

Pie AccPieChart

ErrorEvent Error-events-per-object

Error-events-per-workstation

Error-events-per-controller

Error-events-per-controller-with-children

Error-events-per-user

Most-common-errors


Configuring Columns for a Report

When you click the Configure Columns button on the Source tab, the SelectableColumns dialog, shown below, appears. This applies only to text reports.

Note: When you select a ListView as the Data Source on the Source tab, the Configure

Columns button on the Source tab is unselectable. The columns of the ListViewobject are duplicated in the text report. To configure the ListView report columns,do so from the ListView editor. (See Chapter 23.)




From this dialog, you may add and remove columns for your report. You may also sortthe order of columns. The columns that are available for any given report change,depending on which Data Source and/or Report Type you select on the Source tab.



TAC 214

The following table describes the attributes of the Selectable Columns dialog.

Dialog Attribute Meaning

Columns

UnselectedSelected

The columns available to display in your report, based on your settings on the Source tab, appear in these windows.

The columns that initially appear in your report, by default, arelisted in the Selected window. Other columns that are available,

but not yet selected, appear in the Unselected window.

AddRemove

Adding a column – In the Unselected window, highlight theunselected column name you want to add, and click the Addbutton. This column moves to the Selected window.

Removing a column – In the Selected window, highlight thecolumn you do not want to appear in the report, and click theRemove button. This column moves to the Unselected window.

UpDown

In a report, columns appear from left to right, according to theorder in the Selected window, whereby the first in the list is theleftmost column, and the last in the list is the rightmost column.

To change a column's place in the report, highlight its column

name, and click the Up or Down button to move the column upone position or down one position, respectively.

Sort BySort Attribute You may sort events according to three columns. The report

displays several columns of information, according to the sortcriteria you select here. Sorting is useful to look for trend.

From the Primary, Secondary, and Tertiary dropdown menus,select up to three columns. The columns you select establish thesort order that the report uses.

Sort Direction The checkboxes beside the Primary, Secondary, and Tertiaryfields specify the sort direction for the column values. There aretwo directions: Ascending and Descending. For descending

order, check the Descending checkbox. Ascending order is thedefault (no check). The following table describes the meaning of ascending and descending:

For thisvalue…

…Descending and Ascending mean this

Time values Ascending order places the oldest events ontop. Descending order places the mostrecent events on top.

Text Ascending order is from A to Z. Descendingorder is from Z to A.




Numbers Ascending order is 0 to the highest numericvalue. Descending order starts with thehighest value and ends with the lowestvalue.

Binary values Columns with binary values, such as On andOff, are represented by 1 and 0, respectively.These values are sorted just like numericvalues.

Filter Tab

In the Filter tab, shown below, there are two types of data on which you may apply a filter for your report:

• Time data

• Object data

The Log Filter and the Time Interval attributes allow you to filter time by selecting a timefilter or by setting up a specific "custom" time range. A log filter is an existingCyberStation-supplied filter object, such as Today and Last Week. For more informationon these time-data attributes, please see the descriptions in the table below.

You also build an object member list by filtering object data. Using the object member list,you specify individual objects on which to report. If you have thousands of objects, thenselecting certain subsets of objects for your report becomes an important task. You may



TAC 216

browse for and add one or more new members to the list via the Add button. Similarly,you may highlight one or more members in the list and remove them via the Removebutton.

Using the Path field, you may also specify the path of a controller to run (view) a reporton the member-list objects within that controller in your system. For more information,please see the attribute descriptions, below.

The settings on this tab work together with the settings on the other tabs of the Reporteditor (Source and Output) to define the content of the report, before you run it in theReportViewer.


Log Filter Select this radio button when you want to specify a time rangefor the report, based on a CyberStation system-supplied filter.

To do so, click the Log Filter field's browse button. The Browse dialog appears, displaying all the filters in the Root directory or any folder you specify. Select the filter you want, and click theSelect button. The name of this filter appears in the Log Filter field.

Time Interval Select this radio button when you want to define a specific"custom" time range for the report.

To do so, select a specific starting date and time and a specificending date and time, via the Start and End fields.

Using the calendar — Click the Start or End field dropdownmenu, and select a start date or end date, respectively, on thecalendar that appears. Click the day of the month to select it.The selected day appears in a blue oval. (The current dateappears in a red circle.) Use the right-arrow and left-arrowbuttons at the top of the calendar to display the next month or previous month, respectively. When you click a day, the dayappears in the field, and the calendar is dismissed.

As an alternative to the calendar, you may "key in" the date.Click and highlight the day, month, or year in the Start or End

field and enter the integers for month, day, and year.

For example:

12/23/2003

1/15/2004

2/ 8/2004

Keying in a time To select a start and end time, click andhighlight the hour, minute, or second field, and enter the integersfor the hour, minute, or second to start or end. Also, you clickPM/AM to specify afternoon/evening or morning.





Member object list The member object list window contains a collection of points onwhich you want to run a report.

At any one time, you may add or remove one or more objectsfrom the list. For each member, the member object list columnsdisplay the object name and object class type. For eachmember, it also displays either the device ID (the name of thedevice to which the object belongs) or the owner name (the

name of the folder in which the object resides).

Note: To add an object to the member object list, you may either drag and drop an object from a Continuum Explorer window to the member object list window in this Filter tab,or use the Add button, described below.

Add Click this button to add one object, or a multiple number of objects, to the member object list. When you click the Add button, the Browse dialog appears.

Note: As an alternative you may also drag and drop an objectfrom Continuum Explorer to the member object listwindow.

From the Browse dialog, search for and select the object(s) youwant to add. You may select several consecutive objects, just asyou would do in Microsoft Windows Explorer. For example, clickand highlight the first one in the tree, press and hold the Shiftkey, and click the last one in the tree. All the objects in betweenare highlighted. Similarly, you may select two or more individual,non-consecutive objects, just as you would do in WindowsExplorer. For example, click and highlight the first one, thenpress and hold the Ctrl key, and click additional objects, one at atime, to add them to the collection. Click the Select button. Thenewly added objects appear in the member object list.

Note: In the Browse dialog, you may use the network viewbutton, folder-view button, and other buttons, as well as

the Folder dropdown menu to expose the tree (as youwould in Continuum Explorer) to adjust view of directorypaths and available objects.

Note: In the Browse dialog, you may also use the Objects of type dropdown menu to select only objects of a certainobject class type. For example, if you select InfinityInput,only InfinityInput points appear in the Browse dialogwindow in the network view. In folder view, only the folderscontaining InfinityInput points appear. This is a powerfulfeature that narrows down your list.



TAC 218


Remove To remove one or more objects in the member object list, clickand highlight the object(s) you want to remove, and click theRemove button. The members are immediately removed fromthe list.

You may select multiple consecutive and non-consecutiveobjects in the member object list, as you would in MicrosoftWindows Explorer. For details, please see the description under

the Add attribute, above.

Path Use the Path dropdown menu to search for and select, from thetree, a specific system controller whose member-list objects onwhich you want to run (view) a report.

Specifying the path of a controller here is necessary when youhave two or more controllers containing objects that have thesame names from controller to controller. For example, onemoment you may want to run a report on FanInput1 throughFanInput8 residing on one fan controller, and the next momentrun another report on the same named points on another fancontroller.

To switch views in the tree, right click the dropdown-menu down

arrow and select Network View or Folder View from the popup.

Configure AttributeFilter

Click this button to bring up the Attribute Filter Configurationdialog, where you can filter values according to object attributes.When you select specific attributes for a specific object, their values appear in the report.

From this dialog, beneath Unselected, from the Choose objectclass here dropdown menu, select an object whose attributesyou want to filter. The attributes available for that object appear in the Unselected window.

Note: The attributes in the Unselected list change, according towhich object you select.

To select one or more attributes, so that their values appear inthe report, highlight the attribute, and click the >> button. Theattribute appears in the right-hand Selected window. (Likewise toremove an attribute, highlight it in the Selected window, and clickthe << button. It moves back to the Unselected window.)

When you have finished configuring the attributes, click OK.

View Report Click this button to run your report, based on all the criteria youhave configured in the entire Report editor. When you run areport, it is displayed in the ReportViewer.





Apply Click this button to save your Report configuration changesimmediately, while remaining in the Report editor. (Click OK tosave changes and close the Report editor.)

Output Tab

In the Output tab, shown below, you configure the "look and feel" of the report output to

appear in the ReportViewer — text headings, captions, plot and scale configuration, andso on as well as how the report is generated and outputted. The settings on this tab worktogether with the settings on the other tabs of the Report editor (Filter and Source) todefine the content of the report, before you run it in the ReportViewer.

Two fields on this tab, Output report to email address and Output report to file in path,work with automatic reports. That is, via a special tool, a report can be set up to runautomatically at regularly scheduled times and then sent to the email addresses and/or file specified in these fields. See descriptions of these fields, below.



TAC 220


Heading Enter a text heading to appear at the top of the report. Youmay use wildcards in the text. (See the table of availablewildcards, below.)

The default is:

%r

where the wildcard %r is the report type.

Subheading Enter a text subheading to appear beneath the heading, if desired. The default is:

Report created at %t

where the wildcard %t is the time when the report isgenerated. You may use wildcards in the text. (See the tableof available wildcards, below.)

X-caption Enter a text caption that describes the values along the X(horizontal) axis of the plot.

You may use wildcards in the text. (See the table of availablewildcards, below.)

Y-caption Enter a text caption that describes the values along the Y

(vertical) axis of the plot.

You may use wildcards in the text. (See the table of availablewildcards, below.)

Z-caption Enter a text caption for the Z (for clustered bar chart). Youmay use wildcards in the text. (See the table of availablewildcards, below.)

Note: This field is selectable only when you run a report as aclustered bar chart. A clustered bar chart is only availablewith some Report Types belonging to the AccessEvent and AlarmEvent Data Sources. (See the table for these types inthe Source tab.)

Footnote Enter a text footnote, if desired. The default is:

%p

where the wildcard %p is the report page number.

You may use wildcards in the text. (See the table of wildcards.)






The default is:

%r


Selectable Text Fields: The Heading, Subheading, and Footnote fields are selectablefor all chart types. However, the X-caption, Y-caption, and Z-caption fields are notselectable for a pie chart or text chart because they are relevant only for trend, bar,and clustered bar charts.

Default Values in Caption Fields: The default values that appear in the X-caption, Y-caption, and Z-caption fields vary according to the Data Source, Report Type, andChart Type that you have selected. For example, when you have a trend, the X-captionis Time, and the Y-caption is Value. For example, when you select an ActivityEventdata source and a Most-common-activities report type, the bar chart X-caption is Activity Type, and the Y-caption is Number of Activities. For example, when you selectan AlarmEvent data source and a Most-alarm(s)-acking-workstation report type, thebar chart X-caption is Workstation, and the Y-caption is Number of ACKed Alarms.

Available Wildcards for Text FieldsWildcard Description

%r The report type

%n The first five names of objects in the object member list

%t The time that the report was generated

%p The report page number

%c Configuration data

Showing configuration data is especially important whenarchiving printed reports, whereby it provides a better description of what the report is and what it contains.

%d The description taken from the text in the Description field of the Source tab.

%u The units that are described for the first object in the objectmember list.

Display the full pathin the report

Check the checkbox to show object names or full pathnamesin the report output.



TAC 222



The default is:

%r


One plot for all This radio button is selectable only when you run a trend-chart report – that is, when you select ExtendedLog as aData Source and Object-value as a Report Type on the Source tab.

Click this radio button when you want to compare the trendsof multiple points with different scales on one X-and-Y plot.

One plot per member This radio button is only selectable when you run a Reportonly for trend data.

That is, when you select ExtendedLog as a Data Source andObject-value as a Report Type on the Source tab.

Click this radio button when you want to place each point with

its own scale on one X-and-Y plot.For example, if the trend data from point to point were verydissimilar, and they were unrelated, you would select one plotper member. For example, you could compare analog valueswith different scales to digital values with different scales —for example, digital values of 0 and 1 (off and on) and analogtemperature values between 60 and 80 degrees. Based onthis data, you may, for example, set a room-occupancy flag,which would then trigger the heating in your room, wherebythe trend comparisons on one plot indicate how quickly your room heated up based on occupancy.

Report Format Select either a "web" format or a PDF file format that youwish to display when you run your report in the ReportViewer:

Web — Click this radio button if you are displaying agraphical (scalable vector graphics) image, such as a trendchart, bar chart, or pie chart, in the ReportViewer. Use theweb format for HTML displays also.

PDF — Click this radio button if you are outputting a report toan Adobe Acrobat PDF file. With this option, the content of the PDF file is immediately displayed in the ReportViewer.The Acrobat Reader is actually launched and embedded inthe ReportViewer.






The default is:

%r


Fixed Scale Click this radio button and enter integers in the From and Tofields to designate the low and high limits of your scale,based for the units of the point values that are plotted. For example, the report could show a fixed temperature scalebetween 60 and 80 degrees.

Use fixed scales when you do not want the system to set itsown scales automatically, based on the point data beingplotted.

Output report toemail address

Check the checkbox and enter the email addresses of one or more email recipients who need to receive an automaticreport. This is used by the report command line tool thatschedules a report to run automatically, at a specific regular

time. When this report runs automatically, it is emailed to theaddresses in this field. Delimit email addresses with asemicolon.

For more information, see Scheduling Automatic Reports.

The email recipients listed here are also the default recipientsused when you email a report manually, via the email buttonon the ReportViewer.



TAC 224



The default is:

%r


Output report to filein path

Check the checkbox when you want to send an automaticreport to a file.

This is used by the report command line tool that schedules areport to run automatically, at a specific regular time. Whenthis report runs automatically, it is saved to the file whosepath is specified in this field.

Click the browse button to search for and select the path inwhich you want save report file. (Or, as an alternative, youmay enter the path in the field.)

The system generates a file, with a unique filename, basedon the name of the report and a timestamp. At the time thereport is run, a timestamp is appended to the end of the

filename (the Report object name).

For more information, see Scheduling Automatic Reports.

The file path listed here is also the default path used whenyou save a report to a file manually, via the Save As buttonon the ReportViewer.

View Report Click this button to run your report, based on all the criteriayou have configured in the entire Report editor. When yourun a report, it is displayed in the ReportViewer.

Apply Click this button to save your Report configuration changesimmediately, while remaining in the Report editor. (Click OKto save changes and dismiss the Report editor.)

Scheduling Automatic Reports

Using a special application, ReportCmdLine, and the Microsoft Windows Scheduler, youmay regularly run any report automatically at a specified time. When the report runsautomatically, you may also have it automatically emailed to one or more email recipientsand/or saved to a file.

Note: On the Output tab, check the Output report to email address and Output reportto file in path checkboxes, and specify the email addresses that should receivethe automatic report, as well as the path of the file to which it should be saved.




Note: CyberStation must be running when you use the ReportCmdLine application.

To set up and run a report automatically, perform this procedure:

1. If you want to email this report when it runs automatically, check the Output reportto email address checkbox on the Output tab, and enter email recipients.

Likewise, if you want to save the report to a file when it runs automatically, check theOutput report to file in path checkbox, and enter the path of the file.

2. From the Start menu, select Programs\Accessories\System Tools\ScheduledTasks.

The Scheduled Tasks dialog appears:

Note: User interfaces are self-explanatory.

3. In the Schedule Tasks dialog, double click Add Scheduled Task. The ScheduledTask Wizard appears:

Click Next.

4. In the next screen, search for the program you want to run (ReportCndLine). Click theBrowse button. In the Select Program to Schedule dialog, navigate to and open theProgram Files\Continuum folder, and select ReportCmdLine.exe.

5. The Scheduled Task Wizard displays the application name, ReportCmdLine, in theprogram naming field. If you wish, change this name from ReportCmdLine to another scheduled-task name in this field:



TAC 226

6. On the same screen, select one of the radio buttons to specify how often you wantthis report to run automatically, and click Next.

7. On the next screen, select the time and day you want this scheduled task to start,and click Next.

Enter a start time and start date, in their respective fields.

Also use the radio buttons to make this task run every day, only on weekdays, or as arecurring day. The user-interface is self-explanatory:

7. On the next screen (shown on the next page) enter the name and password of a user in the Enter the user name and Enter the password fields, respectively, and clickNext.

The task will run automatically, as if it were started by that user.




8. The next screen informs you that the task has been successfully scheduled. It alsoprovides the time and frequency of the task and the day it begins:

If you want to configure more advanced properties for this scheduled task, check thecheckbox entitled, Open advanced properties for this task when I click finish.

9. Click Finish.

The ReportCmdLine (or whatever program name you designated earlier) dialogappears:



TAC 228

This dialog contains the "advanced" properties for this task, as mentioned in theprevious step. If you do not check this box in the previous step, the scheduled-tasksetup completes, and the ReportCmdLine dialog does not appear.

10. On the Task tab of the ReportCmdLine dialog (shown above) in the Run field, enter the command line syntax, as follows:

"C:\Program Files\Continuum\ReportCmdLine.exe" /o ObjectName

/u UserName /t Type

Note: When entering the command from here, please make sure you set theparameters outside the quotes surrounding the path name.

If the ObjectName and/or UserName path contains a space, then you must alsoplace quotes around those items. For example:

"C:\Program Files\Continuum\ReportCmdLine.exe" /o "ObjectName"/u "UserName" /t Type

If ObjectName or UserName (when it contains a space) is not enclosed in quotes, thereport does not run.

Parameter Description

/oObjectName

Enter the path name of the Report object you want to runautomatically. It is recommended you use a full path, insteadof the just the name of the object file.




Parameter Description

/uUserName

Enter the CyberStation user name.

/tType

Enter an integer to specify the type of distribution:

0 — Save to a file

1 — Email

2 — Save to a file and email

The email recipients and file path are specified on the Outputtab. See step 1.

11. On the Task tab, in the Start in field, enter the path of the folder in which you arestarting the application. In this case:

"C:\Program Files\Continuum"

12. Select the Schedule tab.

13. Click the Advanced button to bring up the Advanced Schedule Options dialog. Asneeded, configure more advanced settings, then click OK.

14. In the ReportCmdLine dialog, configure other advanced settings, as needed, on theTask, Schedule, and Settings tabs.



TAC 230

15. Click OK to complete the setup.

What Are Extended Logs?

The Report editor allows you to view CyberStation extended log data in the ReportViewer in the form of an extended log report. This is associated with "new" extended logging,with Version 1.7 and higher. Before version 1.7, you created "old" extended logging —that is, created Plain English programs for extended logs. These programs facilitatedextended log tables in the database, one table per controller. With version 1.7 and higher,you may use either type of extended logging, or both.

Note: During CyberStation installation of version 1.7 or higher, in the databaseinitialization process (the Database Initialization dialog) you check the ExtendedLogging Backwards Compatibility checkbox to retain the pre 1.7 method for creating extended logs, while also enabling new extended logging functionality. If you do not check this box, then you may not use the old (pre 1.7) method. For more information, please see the CyberStation Installation Guide, 30-3001-720.

"Logs" vs. "Extended Logs"

Logs store values for an Infinity point on the local controller. These non-extended "shortterm" logs are established via attributes on the Logs tab for InfinityInput, InfinityOutput,InfinityNumeric, and InfinityString. (For more information on logs, please see the Logs tab description for InfinityInput in Chapter 13.)

CyberStation offloads the local-controller “extra” log entries for this point and stores themin the database. This happens once the maximum number of controller log entries isfilled. You activate an extended log for a point by checking the Extended Logging checkbox on the Logs tab of its point editor. When you activate extended logs, theadditional "extra" entries are transferred (uploaded) to the database before the entriesare overwritten in the controller.

The extended log is an extension of a log that continues recording values where the logleaves off. It records values depending on how you set up the short-term log via the Logstab attributes for a point — number of entries, log type, and time interval — as well as theextended-log settings in the General Preferences dialog.

For more information on extended logs and the General Preference dialog settings,please see Chapter 13.

The ReportViewer

You run, view, compare, and distribute reports in the CyberStation ReportViewer, apowerful and versatile tool. This section describes the following:

• Viewing various report data formats

• Running a report in the ReportViewer

• Displaying multiple reports in the ReportViewer

• Using the ReportViewer toolbar — emailing, printing, reloading, saving a report




Note: To use any of the report features, your users must be given access to thesefeatures via the Security editor.

Viewing Report Data Formats

The ReportViewer displays a report using the following data formats, depending on whichtype of report you have configured in the Report editor.

For each report displayed in the ReportViewer, a format icon also appears on each reportwindow tab along the bottom of the ReportViewer:

Icon Data FormatDisplays a scalable vector graphics (SVG) format. This includes bar charts,clustered bar charts, pie charts, and trend charts.

Displays an HTML text format, in the form of a table.

Displays an XML text format, in the form of XML code.

Displays the content of a PDF file, where the Adobe Acrobat PDF reader actually launches, and is embedded in, the ReportViewer window.

Note: You may use the Adobe Acrobat PDF reader toolbar functions, such asEmail, Print, Save and Copy, Search, zoom, text touch-up functions, andother Adobe functions, as if you were running the PDF reader.

You specify PDF format on the Output tab of the Report editor.



TAC 232

Here are several examples of the ReportViewer displaying a pie chart, bar chart, textchart, XML code, and a trend chart:



TAC 234

Here is an example of the ReportViewer displaying the content of a PDF file, with the

PDF reader embedded in the ReportViewer:




Running a Report in the ReportViewer

You may run and view a report in the ReportViewer in one of the following ways:

• Double click a preconfigured report object in Continuum Explorer to launch theReportViewer.

• Right click a preconfigured report object in Continuum Explorer, and from the popupmenu select Open, to launch the ReportViewer.

• Right click a preconfigured report object in Continuum Explorer, and from the popupmenu, select Edit, to launch the Report editor.

• Modify the report configuration, if desired, and click the View Report button in theReport editor to launch the ReportViewer.

• Right click a CyberStation object for which you want to view an ad hoc report, andfrom the popup menu click View then Report to launch the Report editor.

• Configure the report, and click the View Report button in the Report editor to launchthe ReportViewer.

• Schedule a report to run automatically, and have it emailed or saved to a file. (SeeScheduling Automatic Reports, earlier in this chapter.)

Note: If you run a report and no data is available to display in the report, based on your Report editor configuration, the following message appears in the ReportViewer:

No data was returned for this report. Please check the

report time interval and filter.

Edit the parent object to ensure that your source, filter, and output settings feeddata into the report.

Displaying Multiple Reports in Report Viewer

Within the ReportViewer, you may run and view two or more reports, whereby eachreport has its own report window and each window has its own tab, which you selectalong the bottom of the ReportViewer. The tab label states the name of the object.

Note: In the ReportViewer, you may edit the parent object — that is, create differentlyconfigured variations of the same Report object — and display them as separatereports for the same object within the ReportViewer. When two or more reports for the same object are displayed, the object-name tab labels are numbered. For

example: MyReport, MyReport(2), MyReport(3), and so on. Likewise, you maylaunch reports for additional Report objects and display separate reports (in thesame ReportViewer) for the different objects.

When you configure and run two or more reports, the first report window tab appears atthe left margin of the ReportViewer, while subsequent report tabs appear to the right of the previous tab, as they are created.

Initially, as you create two or more reports, the report whose tab you have selectedappears alone, hiding the other reports. However, just as in Microsoft Windows, you maycascade and tile the report windows within the ReportViewer, via the Window dropdownmenu, which gives you three choices: Cascade, Tile Horizontally, and Tile Vertically.



TAC 236

Here is an example of multiple tiled reports:

To select an individual report, either click its window or click its tab.

Using the Toolbar — Emailing, Printing, Saving a Report

The following table describes the buttons on the ReportViewer toolbar.

Button Description

Launches the Report editor for the parent Report object representing thisreport. You may edit the Report's configuration and run the report again.

Reloads/refreshes the graphical report in the ReportViewer.

Opens the Microsoft Print dialog, allowing you to print the report.

Opens an email window, and either attaches the report as a file, or embedsthe report content in the email window. The default email recipients are the

ones you listed on the Output tab of the Report editor.Opens the Microsoft Save As dialog, allowing you, by default, to save thecontent of the report in an scalable vector graphics (.SVG) file, .HTML file,.XML file, or .PDF file, depending on how you configured your report andwhat data format you selected. The default file path is the one you listed onthe Output tab of the Report editor.

Opens the Open dialog, allowing you to search for a Report object in your system, then run it (via the Open button) in the ReportViewer.




Templates

About CyberStation Templates

A template is an object with pre-defined attributes that you use to create new objects withthe same attribute settings. Templates let you quickly, easily, and consistently create new

objects of the same class. Templates are a powerful tool for ongoing maintenance of your system.

You can use templates to create objects such as points, controllers, alarms, andprograms. When you use a template to create a new object, most of the work is alreadydone. A template includes values for most or all of the attributes of the object.

About Copied, Inherited, and Specified by User Attribute Values

When you create a template, you specify values for attributes. In addition, you specify thesource of attribute values in objects created from the template:

When an attribute is copied from a template, that attribute value is passed to the newobject being created from the template. That attribute can be changed afterward in theobject without affecting the template. Any changes to that attribute in the template do not

affect the copied attribute in any object created from that template.• Attributes inherited from a template retain a link to the template. Changes to these

attributes in the template affect all objects created from that template. These inheritedattributes are an easy way to maintain consistent attribute values across objects of the same class. If you try to change an inherited attribute in an object created from atemplate, CyberStation protects the link and offers several choices of actions,including updating the template or breaking the link to it.

Note: If you create Personnel objects from a template, any attribute values with theinherited from Template data source cannot be edited in the PersonnelManager.

12



TAC 238

• If the source of an attribute is Specified By User, CyberStation prompts you for theattribute value when you use the template to create the object.

Creating a Template Object

The following steps provide a general description of how to create a new template. Thetabs that are displayed and the attributes for which you can enter values are determinedby the type of object.

Note: Do not attempt to create a template for any of the following BACnet point objects:

AnalogInput BinaryInput Multi-stateInput

AnalogOutput BinaryOutput Multi-stateOutput

AnalogValue BinaryValue Multi-stateValue

However, you may create templates for BACnet EventEnrollment andEventNotification objects. Configuration of EventEnrollments andEventNotifications at a large site can be a big job. It is recommended you createtemplates for these objects to save a lot of time and effort. (See “Considerations for EventEnrollment Templates,” later in this chapter. See also Chapter 14.)

1. In Continuum Explorer, open the Template folder.

2. Select the template subfolder where you want to store this template, or create a new

subfolder.Note: When you create a personnel template, store it in the Personnel Templates

folder, which is a subfolder of the Templates folder. Personnel templates storedelsewhere within CyberStation cannot be attached to profiles or to existingPersonnel objects.

3. Right click the folder, select NewTemplate, and select the object class that you wishto create the template for from the popup menu.

4. Type the Object name and Alias in the New Template dialog that appears, and thenclick the Create button.

5. In the Template editor, specify the necessary information on the various tabs of theeditor.

6. When you are finished, click OK.

Entering Template Information

The Template Information tab is where you’ll enter a name and alias for all objects thatwill be created from this template.

When deciding on a name, try to be as descriptive as possible. Descriptive names helpfuture users choose the correct templates to create objects from. For example, if you arecreating an output point for operating fans, you might want to enter a name like“Turn_Fan On/Off.”

Entering an alias is optional. If you leave this field blank, CyberStation will use thetemplate’s alias.




CyberStation automatically avoids conflicts that are caused by duplicate object nameswhen you create multiple objects using the template. If CyberStation detects an existingobject with the same name, it appends an underscore and a number to the name of thenew object.

When CyberStation finds an existing object (for example, an alarm named alarm3), itrenames the new object (for example, alarm3_1). The next time the same template isused to create an object in the same container, CyberStation will give the new object aname of alarm3_2.

Entering Attribute Data SourcesThe Attribute Data Source tab is where you’ll choose a data source for the value for each attribute of the objects created from this template. See “About Copied, Inherited,and Specified by User Attribute Values” earlier in this chapter.

Considerations for BACnet EventEnrollment Templates

When you create templates for BACnet EventEnrollments, please be aware of thefollowing:

• Some fields are disabled in EventEnrollment template objects, and can be specifiedonly in the objects created from the template.

• The event type (Event Type field on General tab of EventEnrollment editor) cannotbe changed once the template object is created.

• If an inherited object is deleted from a third-party device in CyberStation, and theobject is re-learned, the inheritance is broken.

• Some event types are not supported on the Andover Continuum b4 and b3controllers. (See Using the EventEnrollment Editor, in Chapter 14.)

• In the Attribute Data Source tab, some EventEnrolllment attributes cannot bechanged. These are:

Setpoint Reference – Attribute (Algorithms tab in EventEnrollment editor, whenthe Floating Limit event type is selected.)

Setpoint Reference – Object (Algorithms tab in EventEnrollment editor, when theFloating Limit event type is selected)

Object (General tab in EventEnrollment editor)

Attribute (the Event Property attribute, General tab in EventEnrollment editor)

Creating an Object from a Template

1. In the Configuration Wizard (discussed in Chapter 2) click the tab with the templateyou want to use.

2. Drag the object icon or folder icon from the page of the Wizard to the container objectin Continuum Explorer.

You will be prompted by the Enter Attribute Values dialog for any attributes that hadbeen designated as SpecifiedbyUser in the template(s).



TAC 240

3. Enter the attribute value, and click the Next button for each prompted attribute.

4. After you see the message “The operation is finished,” click the Close button in theCreating Objects from Templates dialog to complete the creation of your new object.

CyberStation automatically avoids conflicts that are caused by duplicate objectnames. If CyberStation detects an existing object with the same name, it appends anunderscore and a number to the name of the new object.

Once you have created a new object from a template you can review its attributes withthe object editor or its Properties dialog. When you review the properties of an objectcreated from a template, the name of the parent template appears at the bottom of theMain tab.

Editing an Object Created from a TemplateWhen an attribute value is inherited, it cannot be changed in the object without breakingthe link to the template. (Values inherited from a personnel template cannot be edited inthe Personnel Manager.) Attempts to edit an inherited attribute value result in thefollowing dialog, which requires users to select one of the options before they can makechanges to the object:

You can automatically change an inherited attribute in all objects created from a templateby editing the attribute in the template.




Note: If you select the third option, Break the connection between this object and thetemplate object…, you break the connection to the template for all attribute of theobject itself, not just for the attribute you wanted to change.

If you break the link between an object and a template, you cannot link the object to thetemplate.



TAC 242




Points, Logs,

and Triggers

What is a Point?

Throughout Andover Continuum literature you’ll see references to the word “point”. Insome cases its definition may be obvious; however there are instances where the term isnot familiar. Inputs and outputs are referred to as “points”. An input point is a particular connection at a unique channel where an input sensor is connected. An output point is a

particular channel where an actuator or other output device is connected. Points includeinternal memory locations that serve as “virtual” points. These locations act as storagelocations for values that our programs change. Because they can be read and set justlike inputs and outputs, we find it easier to refer to them in the same terms.

Types of Points

There are three types of points in the Andover Continuum system — hardware-defined,software-defined, and BACnet-defined.

Hardware-Defined

InfinityInput Connections to an Infinity input device

InfinityOutput Connections to an Infinity output device

Software-DefinedInfinityDateTime Storage location where the current system time and date are

available

InfinityNumeric Storage location where numeric (number) information is stored

InfinityString Storage location where ASCII text characters are stored

BACnet-Defined

CyberStation has nine points supported by BACnet devices. BACnet points are createdon third-party BACnet devices or when an InfinityInput, InfinityOutput, or InfinityNumericis created on an Andover Continuum b4920 or bCX1 40x0 InfinityController object or an Andover Continuum b3 InfinityInfinetCtlr object. BACnet points are:

13



TAC 244

• AnalogInput, BinaryInput, and MultistateInput (created from an InfinityInput)

• AnalogOutput, BinaryOutput, and MultistateOutput (created from an InfinityOutput)

• AnalogValue, BinaryValue, and MultistateValue (created from an InfinityNumeric)

Note: The term point is a CyberStation term. According to the BACnet standard, thesenine points are known as BACnet objects.

For more information, plase see About BACnet Objects, at the end of this chapter. Seealso Chapter 14, BACnet .

About InfinityInput and InfinityOutput Points

What Is an InfinityInput?

An InfinityInput is a connection to an Infinity or Infinet controller for monitoring incomingsignals from a sensor. Decisions we make during the configuration of an input determinehow the controller will interpret and present that sensor input. The controller reads inputvalues once per scan time and therefore can be updated automatically.

Input Types

CyberStation can monitor a variety of sensor types:

• Contact closures

• Thermistors

• Voltage and current transducers

• Current sensors

• DC voltage signals

• AC voltage signals

• Supervised security inputs

What Is an InfinityOutput?

An InfinityOutput is a connection to an Infinity or Infinet controller where signals are sentto controlled devices. Outputs turn things on and off, provide variable voltages, currents

or air pressures. Outputs also change value either by program control, the command line,or from a graphic panel control.

Output Types

Outputs send signals to controlled devices that are:

• Digital (On – Off, such as contact closures)

• Controlled by analog signals, voltage or current

• Air pressure controlled




Before You Start

Before creating input or output points you will need to know:

• Information about the IO Module

• IO card slot numbers (for CX 94xx controllers)

• IOU board Lbus number (for CX 92xx controllers and NetControllers)

• IOU modules used on L-Bus

• Andover Continuum IO module number (for NetControllers)

• Infinet device name and path (for InfinityInfinet Controllers)

• Channel numbers where the physical connections are made

• Information about the sensor (input) or controlled device (output)

• Electrical type

• Engineering units in which you want the data presented on the workstation

• Display format in which you want the data presented on the workstation

• Resistor type for supervised inputs

Creating an InfinityInput ObjectTo create an InfinityInput object:

1. In the navigation pane of the Continuum Explorer, locate the controller object thatyou want to add the InfinityInput object to.

2. Right-click the controller object.

3. Select New, then select InfinityInput to bring up the New dialog.

4. In the New dialog, name the InfinityInput in the Object name field.

5. Click the Create button to bring up the InfinityInput editor:



TAC 246

The InfinityInput General Tab

The General tab, shown on the previous page, has several attributes that you canprovide values for and a few attributes that are set by the control system. Attributes thatyou set include Units, Description and State.

Value If a point is enabled, input values are read from the sensor that the pointis attached to, updating the Value attribute with each system scan. For testing purposes, you can force an input to a pre-set value after you haveset the point’s State to Disabled.

Units Units, also known as engineering units, add meaning to the point value.When displayed on the workstation next to the value, as in 40 %Humidity , or 75 Deg F , units help users understand what the point is

doing. Enter up to 12 characters (including spaces) in the Units field.Don’t use double quotes.

The text you enter here can be anything you want it to be. It is just a textstring included to help the user. It has no affect on input point values.

Description The description is optional, but a good explanation of the point helpsothers if they need to test, modify or manipulate the point in the future.The Description characters take up memory space in the controller. Typeup to 32 characters (including spaces) in the Description field.




State Enabled means the point is under system control. When the point isEnabled, the control system reads the sensor and sets the Value attributeto the value taken from the environment.

Disabled means the system no longer updates the value. If we set thepoint to a different value, it holds that value as long as the point remainsdisabled.

Never set a point manually unless you are testing or repairing the system.

Exported If this point is referred to in a program on another controller or has an

alarm attached, you will see a check in this checkbox. The Exportedattribute is set by the control system. There is no user entry in this field.

Alarms This read-only attribute shows the number of active alarms associatedwith this point.

The InfinityInput Settings Tab

This tab, shown below, is where you define the following:

• The electrical type (ElecType) of the device connected to this point

• The input channel number

• The IOU number of the input module (if applicable)

• The format in which the value of this point is displayed on the workstation

• Specific settings related to certain ElecTypes



TAC 248

ElecType The electrical type specifies the ElecType attribute for all InfinityInputpoints. See Appendix B for a complete listing of the possible electricaltypes.

Note: If you are creating this input for an Andover Continuum b4, bCX140x0, or b3 controller, then a BACnet AnalogInput, BinaryInput, or MultistateInput is also created, when you select an analog, digital, or multistate (supervised) ElecType, respectively. See About BACnet Objects at the end of this chapter, and see Chapter 14, BACnet .

Invert If you select Digital as an electrical type, and want to invert the meanings of ON and OFF, click the Invert box (usually grayed out) to put a check markin it.

Channel Channel numbers are silkscreened onto the front of each type of IO unit onevery type of controller. Typical channel number markings are IN18(channel 18) on an Eclipse controller IO module or IN5 (channel 5) on an Andover Continuum IOU Module.




IOU Enter an IOU number for the following three types of controllers:

CX9200. Enter the number of the IOU board on Lbus.

A CX9400. Enter the slot number where the IO card is plugged in to thecard rack.

Andover Continuum NetController. Enter the number of the IO module or IOU board on Lbus that is sending the input.

Assign the appropriate number for the module you are configuring.

Format The format field is where you specify what display format you want to use topresent the Value attribute to the operator. The # sign is a placeholder.Examples

###.### would be a number with three decimal places

$### shows values greater than zero as ON, values equal to zero as OFFand values less than zero as –ON.

DigitalFilter

Enable or disable the digital filter by selecting True or False from thedropdown menu. When the Digital Filter is True, value updates are slightlydelayed in order to filter out sudden, radical changes in sensor readings(due to, for example, electrical surges). When the Digital Filter is False, thevalue is updated with every sensor reading. This provides slightly faster updates.



TAC 250

The InfinityInput Conversions Tab

The Conversions tab is where you enter information about how the controller convertsthe sensor readings (ElecValue) into engineering units

Enter a conversion formula in the Conversion field or use the Auto Conversion fields toset the top and bottom of scale values. Input signals are converted to temperatures,relative humidities, atmospheric pressures, and so on.

Threshold Enter the amount of change in engineering units that must occur before thepoint updates other objects such as programs, functions, alarms, reportsand exports to other controllers. A threshold of zero increases networktraffic, as all associated objects update with any change in point value.

Conversion You enter a conversion formula for either of the two following

circumstances:

The conversion between the sensor reading ElecValue and engineeringunits is non-linear. For example, enter the formulaSQRT(ELECVALUE)*500, if the square root of the ElecValue must bemultiplied by 500 to equal the correct engineering unit Value.

You want to limit or bias a linear conversion. For example, enter theformula (ELECVALUE + .5), to calibrate a temperature sensor reading.

Note: Do not include VALUE = in the formula you enter in the Conversionfield.




AutoConversion

Enter the top of scale for the engineering units in the Top field on theleft. For example, if you entered % Humidity in the Units field on theGeneral tab, your top of scale would most likely be 100, for 100%.

Enter the bottom of scale for the engineering units in the Bottom fieldon the left. For example, if you entered % Humidity in the Units field onthe General tab, your bottom of scale could be 0, for 0%.

The fields for ElecType values are on the right side of the AutoConversion section. The values you enter will be used in a linear conversion.

Enter the top of scale for the electrical units in the upper ElecType field on the right. For example, if you selected Voltage in theElecType dropdown menu on the Settings tab, your top of scalewould most likely be 5, as this is the highest reading possible for voltage on many controllers.

Enter the bottom of scale for the electrical units in the lower ElecType field on the right. For example, if you selected Voltage in theElecType dropdown menu on the Settings tab, your bottom of scalewould most likely be 0, as this is the lowest reading possible for voltage.

Formulas entered in the Conversion field take precedence over the

conversion generated by the Auto Conversion section, but the AutoConversion will recognize a limiting or biasing formula and use it in itsconversion.

Test the Point

Once you have completed the General, Settings and Conversions tabs of the editor,you have supplied enough information to create the point. Now is a good time to save thepoint and test your preliminary configuration.

Save the Point

Click InfinityInput editor’s OK button.

Verify Value

The Explorer’s Command Line should show the correct path to the controller .

Enter PRINT Pointname

You should see the current value of the point in the response line.

Verify ElecValue

From the Command Line, enter PRINT Pointname ELECVALUE

You should see the current input electrical value of the point in the response line.



TAC 252

InfinityInput Logs Tab

In the Logs tab, shown below, you define logs and extended logs for the point. A log is acollection of point values. The structure, also known as an array, looks like a two-columntable. The first column contains an index of entry numbers. The second column containsrecorded values.

In the Logs tab, you define and activate two types of logs for a point:

• Logs — Log entries are stored on the local controller that owns the point. See Logs,later in this section.

• Extended logs —CyberStation offloads the local-controller “extra” log entries for thispoint and stores them in the database. This happens once the maximum number of

controller log entries is filled. When you activate extended logs, the additional "extra"entries are transferred (uploaded) to a workstation's CyberStation database, tocapture them before they are deleted in the controller. The extended log, which is anextension of a log, continues recording values where the log leaves off. It recordsvalues depending on how you set up the short-term log. These extended log entriescan be uploaded from both local-area network (LAN) controllers and remote-accessservices (RAS) network controllers to the workstation. (See Extended Logs, later inthis section.)

Extended logs work according to the attribute settings on this tab, as well as:

• Extended-log settings on the Preferences tab of the Device editor for a workstation.(For more information on these settings, see Extended Logging , later in this section,and Chapter 14, BACnet .)




• Extended-log settings 7, 8, 9, and 10, in the General Preferences dialog. (For moreinformation on these settings, see Extended Logging , later in this section.)

Automatic Logs and Manual Logs

For Infinity Input, Output, Numeric, String, and DateTime points, you can set up one of two basic types of short-term logs:

• Logs that the system updates automatically

• Logs that you update manually

Automatic Logs — Automatic logs are generated by CyberStation at specific intervalsthat you define via the attribute settings on this tab, as well as the preference settings inthe General Preferences dialog. (See Extended Logs, later in this section, for GeneralPreference settings.)

For example, the following picture depicts an automatically updated log for a point namedSupplyAir:

CyberStation updates automatic logs by inserting new values into the first log entry.Every interval, a new value is stored in the first log entry, pushing existing values down tothe remaining entries. When the specified number of entries is full of values, the bottomvalue "drops off” when a new value is inserted.

When working with logs, you won’t actually see structures like the one shown above.Instead, you use point names and index numbers to retrieve values stored in logs. To dothis, simply enclose the index number in square brackets [ ] directly after the point name.

For example, to print the sixth entry (72) of the log for SupplyAir, use the following

command:PRINT SupplyAir[6]



TAC 254

Manual Logs — Unlike automatic logs, CyberStation cannot set manual logs. Manuallogs are set either from the Command Line editor or a Plain English program. To updatea manual log, simply enclose the index number in square brackets [ ] directly after thepoint name. The example below sets the third log entry of an array named MyNum:

SET MyNum[3] TO 12

Note: To perform calculations on logs, see the following Plain English keywords:

SUM

AVERAGE

MINIMUM

MAXIMUM

Logs

The following table describes the attributes in the Logs section of this tab. Thesesettings affect extended logs, when extended logging is activated.

Number of Entries

Enter an integer representing the number of entries.

The maximum number of entries allowed in a log depends on the memoryavailable on your controller, but cannot exceed 32,767 entries per log.

When this number is exceeded, and you have activated extended logging,

then the first-in-first-out log entries are transferred (uploaded) to aworkstation's CyberStation database. If extended logging is not activated,then the first-in-first-out log entries are deleted from the controller.

Type In the Type field, use the down arrow to show a list of available log typesand select one:

Manual Not set by CyberStation. Can be set only fromthe command line, a report, or a Plain Englishprogram

LogInstantaneous CyberStation stores the current value of thispoint at the beginning of every interval

LogAverageCyberStation calculates the average pointvalue over every interval, using a weightedaverage algorithm. Average values are storedat the end of every interval.

LogMinimum CyberStation compares all values over aninterval, finds the minimum and stores it at theend of every interval

LogMaximum CyberStation compares all values over aninterval, finds the maximum and stores it atthe end of every interval




Interval If the Type is not Manual, set the Interval. This determines how oftenCyberStation stores new values in the log. The values that you enter for days, hours, minutes and seconds are combined to create the totalinterval. For example, if you enter a 1 for days and a 12 for hours, the logwill be updated every 1.5 days. Similarly, if you need a 90-minute interval,enter a 1 for hours and a 30 for minutes.

Days – maximum value is 365

Hours – maximum value is 23

Minutes – maximum value is 59Seconds – maximum value is 59

Tip: In order to have a log updated at the same time every hour (every quarter hour, or every half hour, for example) your interval must be evenly divisible into one hour (1min, 2 min, 3 min, 4 min, 5 min, 6 min, 10 min, 12 min, 15 min, 20 min, or 30 min).

Extended Logs

To activate extended logs for this point, check the Extended Logging checkbox.

When you activate extended logs, the additional "extra" entries are transferred(uploaded) to a workstation's CyberStation database, to capture them before they aredeleted in the controller.

The extended log, which is an extension of a log, continues recording values where thelog leaves off. It records values depending on how you set up the short-term log. Theseextended log entries can be uploaded from both LAN controllers and RAS controllers tothe workstation.

In addition to checking the Extended Logging box and setting the Number of Entries,Type, and Interval attributes on a point's Logs tab, your administrator also configuressettings 7, 8, 9, and 10, in the General Preferences dialog.



TAC 256

The General Preferences dialog is shown below:

Setting 7, Extended Log Database Check Interval (minutes) — This is the timeinterval, in minutes, that CyberStation checks the database for points that are enabled for automatic extended logging, checks the extended logging table, and uploads the pointdata. The default is 5 minutes.

Increase for RAS Network: If you know you will be performing extended-log uploadingfrom controllers on a RAS (remote) network, it is good practice to increase the number of interval minutes because this process takes longer on such a network. Data is lost whenthis process takes longer than 5 minutes beyond the number of minutes specified here. Itis also good practice to decrease the Extended Log maximum RAS Buffer Percentage(see setting below).

Setting 8, Extended Log Maximum LAN Buffer Interval (minutes) — This is themaximum time interval, in minutes, that CyberStation may check each controller on a

LAN network for new extended logging data.

Setting 9, Extended Log Maximum RAS Buffer Percentage — This is the maximumamount (percentage) of new point log data allowed to accumulate in a controller on aRAS network, before it is downloaded automatically. It is a percentage of total controller log size. CyberStation knows the logging interval and the log buffer size on a RAScontroller, and it calculates when a certain percentage of the buffer in the controller isfilled. It dials into the controller when the percentage is exceeded to download the logdata. This may be any percentage between 0 and 100 percent.

Decrease to Ensure More Frequent Downloads: Make sure this percentage is smallenough to ensure more frequent downloading. Data is lost when a downloadingoperation takes longer than 5 minutes beyond the number of minutes specified in the




setting above, Extended Log Data Check Interval. It is also good practice to increasethe number of minutes in that setting (see above).

Setting 10, Extended Log Automatic Purge Interval (days) — This is the number of days to keep extended log data in the database before purging it. Extended log data isstored in a single internal table, so purging the data after a specified number of daysprevents this table from becoming too large. A value of 0 ensures that the data is never purged.

To access the General Preference dialog, right click the Continuum symbol

located in the bottom right-hand corner of the screen, and select General Preferences.Settings 1…6 of the General Preference dialog are related to password-managementconfiguration. For more information, please see Chapter 5.

Enabling a Workstation for Extended Logging — You may enable or disable anyworkstation to download extended log data from controllers on a local-area network(LAN) or from controllers on a remote-access services (RAS) network, to the workstation.This is done via settings 19 and 20 (Enable personnel distribution to controllers onthe LAN and Enable personnel distribution to RAS networks) on the Preferences tab of the Device editor for the workstation device that you wish to enable or disable.

Your must determine which workstations at your site are best suited to perform this task.For more information, see the Preferences tab of the Device editor, in Chapter 14.

Extended Logging Backwards Compatibility (“Old” and “New” Extended Logs) —Before version 1.7, you created Plain English programs for extended logs. Theseprograms facilitated extended log tables in the database, one table per controller.

During CyberStation installation of version 1.7 or higher, in the database initializationprocess (the Database Initialization dialog) you check the Extended LoggingBackwards Compatibility checkbox to retain the pre 1.7 method for creating extendedlogs, while also enabling new extended logging functionality. If you do not check thisbox, then you may not use the old (pre 1.7) method.

Note: The "old" extended log tables, created before your upgrade to version 1.7, remainin the database. When a "new" extended log table is created, if necessary, datafrom an "old" table are copied and merged with the data in the "new" table.

For more information, please see the CyberStation Installation Guide, 30-3001-720.

Extended Logs and Reports — Extended log data, as well as other report data sources,can be presented in a report and displayed in the form of attractive trend chart, text chart,bar chart, or pie chart. CyberStation supplies many Report object templates that includebar-chart templates, pie-chart templates, and trend templates — giving reports a certaindefault "look and feel."

To use these Report templates, your must import them (and thus activate reports) duringthe CyberStation installation process, in an upgrade to version 1.7 or higher. Duringinstallation, in the Database Initialization dialog, you must check the Create/UpdateGraphical Report Settings checkbox. If this box is not checked, then the TAC-suppliedReport templates are not available.

For more information, please see the CyberStation Installation Guide, 30-3001-720, aswell as descriptions of Reports and the Report editor in Chapter 11.



TAC 258

Setting 11 - Time Interval Between Requests

Setting 11 of the General Preferences dialog is the number of milliseconds thatCyberStation waits before it polls controllers and networks for value changes in pointsembedded in Pinpoint graphics panels. The default is 30 ms. This delay between pollrequests enhances performance by ensuring that a controller/network is not flooded withtoo many requests.

Note: This setting is applied globally, to all controllers/networks – to all Infinity controllers,Infinet controllers, Infinet networks, Andover Continuum BACnet controllers,BACnet networks, and third-party BACnet controllers. If a third-party requestinterval is longer than this global setting, the third-party interval overrides thissetting. If a third-party interval is shorter than this global setting, the global settingoverrides. (The longer interval prevails.) Remote access services (RAS) controller graphic points are polled synchronously, so this setting does not affect graphics onremote controllers.

Settings 12, 13 – Fieldbus Personnel Distributions

Setting 12: Number of Concurrent Fieldbus Personnel Distributions — This GeneralPreference setting is the number of concurrent personnel distributions that are sent fromeach workstation to controllers on each field bus network. The default (and minimum)value is 1. Maximum value is 4. This setting, which works in conjunction with setting13,improves performance by preventing or large numbers of personnel records from floodingfield bus controllers. See also Chapter 20, Managing Personnel Distribution.

Time Interval Between Fieldbus Personnel Distributions — This General Preferencesetting is the amount of time (in milliseconds) that CyberStation waits before it sendsanother personnel distribution to controllers on the same fieldbus network. The defaultvalue is 30. Minimum value is 0. Maximum value is 15000 (15 seconds). This setting,which works in conjunction with setting 12, improves performance by preventing largenumbers of records from flooding field bus controllers. It is also useful when there aremany workstations performing access distribution. (That is, set it higher if there are manyworkstations.) See also Chapter 20, Managing Personnel Distribution.

Settings 14, 15 – NetController Personnel Distributions

Setting 14: Number of Concurrent NetController Personnel Distributions – This isthe number of concurrent personnel distributions that are sent from each workstation toNetControllers and all other Ethernet-level controllers. The default (and maximum) valueis 4 and the minimum value is 1. This setting works in conjunction with setting 15.

Setting 15: Time Interval Between NetController Personnel Distributions -- This isthe amount of time (in milliseconds) that CyberStation waits before it sends another personnel distribution to NetControllers and all other Ethernet-level controllers. Thedefault (and minimum) value is 0 and the maximum value is 15000 (15 seconds). Thissetting, which works in conjunction with setting 14, improves performance by preventinglarge numbers of personnel records from flooding these Ethernet-level controllers. It isalso useful when there are many workstation performing access distribution.




The InfinityInput Triggers Tab

The Triggers tab is where you’ll associate triggers with a point. Triggers are PlainEnglish programs whose status changes to active when the point value changes by atleast the amount of the Threshold attribute setting. One point may have numeroustriggers associated with it. Conversely, one program can be triggered by many points.

To associate an Infinity program with a point, click the Add button. This will display aBrowse dialog for Plain English programs. Once you have found the Infinity program youwant, click the Select button, and that program will be added to the point’s trigger list.

To delete an Infinity program from the trigger list, click it, then click Remove button.



TAC 260

The InfinityInput XDriver Tab

If you have purchased a special device that you have connected to a controller, TAC candevelop special software that allows your device to work with the controller. The softwareis called an “XDriver.”

After you have connected your device to the controller, and installed the XDriver software, you need to specify the comm port that you used in the XDriver window.

Use the dropdown menu to select the desired comm port. Once the proper comm porthas been selected additional XDriver parameters will be required (see your XDriver documentation).

The InfinityInput Security Level Tab

Refer to Chapter 4 for details on entering information into the Security Level tab.




InfinityOutput Points

An InfinityOutput point is an object that you create on Infinity or Infinet controllers. Anoutput point changes or affects the environment by controlling a piece of equipment suchas a heater or fan.

Infinity controllers have numerous (the number varies depending on the type of controller)channels for output points. A channel in this case is simply an area in the controller thancan be physically connected to a device.

When you create an InfinityOutput point, you define it by specifying values for itsattributes. An attribute can be thought of as a characteristic of the point. For example,you have many attributes such as height, weight, hair color, and age. Some of theattributes for an InfinityOutput point include value, electrical type, display format,threshold.

You’ll specify values for these attributes and many more in the following tabs of theInfinityOutput editor.

Creating an InfinityOutput Object

You create an InfinityOutput object in the same way that you created an InfinityInputobject. Repeat the steps for an InfinityInput object, but replace the word InfinityInput withInfinityOutput throughout the steps. This brings up the InfinityOutput editor:



TAC 262

The InfinityOutput General Tab

The General tab has several attributes that you can provide values for and a fewattributes that are set by the control system.

Value When a point is enabled and active, the control system updates itautomatically. Never set a point’s value manually unless you are testing or repairing the system. Always disable a point before setting the valuemanually.

Units Units, also known as engineering units, add meaning to the point value.

When displayed on the workstation next to the value, as in % open, or PSI , units help users understand what the point is doing. Enter up to 12characters (including spaces) in the Units field. Don’t use double quotes.

The text you enter here can be anything you want it to be. It is just a textstring included to help the user. It has no affect on input point values.

Description The description is optional, but providing a good explanation will helpothers work with the point. Type up to 32 characters (including spaces) inthe Description field.

State Select Enabled or Disabled from the dropdown menu. When the point isenabled, the control system sets the value to the desired output setting.When the point is disabled, a program can't set the point. A user can set itfrom the Command Line or a control on a graphic panel. Never set a pointmanually unless you are testing or repairing the system.

Exported A check in the Exported checkbox means that programs or reports onanother controller use this point's value.

Alarms The Alarms attribute displays the number of active alarms associated withthis point.




The InfinityOutput Settings Tab

The Settings tab is where you specify various settings regarding the output point, suchas the channel number and the electrical type.

ElecType Select one of the electrical types from the dropdown menu.

Note: If you are creating this output for a b4, bCX1 40x0, or b3 controller,then a BACnet AnalogOutput, BinaryOutput, or MultistateOutput is alsocreated when you select an analog, digital, or multistate (tristate) ElecType,respectively. See About BACnet Objects at the end of this chapter, and seeChapter 14, BACnet .

Voltage The output point is a voltage type. Enter a conversionformula on the Conversions tab.

Digital The output point is an ON or OFF contact closure.You can use the Invert checkbox to invert themeanings of ON and OFF.

Current The output is a current type

Tristate The output is a tristate type (ON, OFF, −ON)

ACC_Pneumatic Not used



TAC 264

ReaderDoor (Infinity only)

The controller is an Infinet controller, other than a 700series, and the point is controlling a door or magstrike lock on a door with a card reader on an EMX190 or a CRM 100 module. This output type usuallyapplies only if you do not have the access controlversion of Infinity.

HiResVoltage The controller is an Infinet controller and the point is avoltage output on an EMX 151 or AOM 500.

HiResCurrent The controller is an Infinet controller and the point is acurrent output on an EMX 151 or an AOM 500.

PanelMeter The output is for an LED display on an Andover Continuum door-mounted display module .

Channel Channel numbers are silkscreened onto the front of each type of IO unit onevery type of controller. Typical channel number markings are OUT1(channel 1) on an Eclipse controller IO card or OUT3 (channel 3) on an Andover Continuum IO Module.

IOU Enter an IOU number for IO in the following three types of controllers:

CX9200: Enter the number of the IOU board on the Lbus. These IOU

numbers are set with dipswitches. Look at the dipswitches to determine theIOU number.

CX9400: Enter the slot number where the IO card is plugged in to the cardrack. The slots are numbered from left to right, starting with 1.

Andover Continuum NetController : Enter the number of the IO module or the IOU number on Lbus that is sending the output.

Assign the appropriate number for the module you are configuring. For example, for Andover Continuum IO modules, you may decide to number themodules from left to right, starting with the top DIN rail. NetControllers cancontrol up to 32 IOU modules.

Label the IOU modules with the numbers you assign. This number is not the

same as the 12-digit module ID # assigned to the individual module at thefactory.

Outputs created on any other types of controllers, will show the IOU fieldgrayed out.

Format The format field is where you specify what display format you want to use topresent the Value attribute to the operator. The display format $### showsvalues greater than zero as ON, values equal to zero as OFF and valuesless than zero as −ON.




About Displaying Percents

There are two ways to show percent values to the user, depending on how you configurethe Value and Units attributes for an output point.

1. On the General tab of the editor, include a % sign as the first character of the Unitsattribute. For example:

%RH

This will have no effect on the Value attribute of the point.

2. On the Settings tab of the editor, include a % sign in the Format field. For example:

%###.#

When the % sign is in the display format field this way, the Value of the point willautomatically be multiplied by 100 and a % sign added when the point is displayed.

Note: If using this method with an Auto Conversion, the ‘top of scale’ should be set to1, not 100.

This second method of showing percents is commonly used with analog outputs.

For example in the Plain English Language print statement:

Print “The value is set to ⏐%### open.”, WATER_VALVE

prints the value in numeric characters as a percentage of the scale for theWATER_VALVE point with the scale set from 0 to 1, where 0 is fully closed and 1 is fullyopen. So if the value is .45, the statement prints:

The value is set to 45% open.

The InfinityOutput Conversions Tab

The Conversions tab (shown on next page) is where you enter a conversion formula or set Auto Conversion fields to convert engineering units to control signals.

The output value is converted and displayed based on the formula in the Conversion or Auto Conversion fields. Value/10 in the Conversion field would carry out the sameconversion as shown in the Auto Conversion section.

Test the PointOnce you have completed the General, Settings and Conversions tabs of the editor, youhave supplied enough information to create the point. Now is a good time to save thepoint and test your preliminary configuration.

Save the Point

Click InfinityInput editor’s OK button.

Verify Value

The Explorer’s Command Line should show the correct path to the controller .

Enter PRINT Pointname

You should see the current value of the point in the response line.



TAC 266

Verify ElecValue

From the Command Line, enter PRINT Pointname ELECVALUE

You should see the current input electrical value of the point in the response line.

Continuing OnOnce you have tested the point, reopen the editor and complete the remaining tabs tofinish configuring the point.

Enter information into the Triggers, Alarms, Logs and XDriver tabs of the InfinityOutputeditor. Complete these tabs using the explanations provided earlier in this chapter for completing the same tabs of the InfinityInput editor.





About Infinity Software Points

Software points are holding places for information. They are numerics, datetimes, or strings. Infinity software points are those that exist on Infinity controllers (includingNetControllers) and Infinet controllers that are connected to the Andover Continuumsystem.

InfinityNumeric InfinityNumeric points are storage locations in an Infinitycontroller’s memory. They store numeric information, such astemperature setpoints. They can store the values ON, OFF and –ON as well as floating point numbers such as “1.52, 6.14” and soon. They are also used when configuring Andover Continuumenclosure door display modules.

InfinityDateTime InfinityDateTime points store date and time information used inschedules and are used to create time stamps.

InfinityString InfinityString points are storage locations for plain text messagesin an Infinity controller’s memory. These can include logical pathsto physical devices such as printers, or messages that aredisplayed to an operator.

Creating Infinity Software Points

To create new Infinity software points you type information into text fields and makeselections from dropdown menus in the tabs of the CyberStation InfinityNumeric,DateTime and String editors. Once you have created the new points, you can review thedetails of the configuration several different ways:

• Object editor

• Object Properties dialog, also called the Info Viewer

• ListView or class default ListView

• From the Command Line

Creating an InfinityNumeric Object

You create an InfinityNumeric object in the same way that you created an InfinityInputobject. Repeat the steps from the InfinityInput procedure, but replace the wordInfinityInput with InfinityNumeric throughout the steps. This brings up the InfinityNumericeditor, as shown on the next page.



TAC 268

Note: For instructions on how to use objects editors in general refer to Chapter 3.

The InfinityNumeric General Tab

Attributes that you can set for all InfinityNumeric points include Value, Units,Description, State, Format and Setpoint. For points connected to certain IOU modules,you also set the Channel and IOU numbers and Direction.

Value The initial value of a newly created InfinityNumeric point is 0.000.Enter value in the field or set it from the command line.

Units Units (engineering units) make clear the type of information the pointregisters. They display next to the Value, as in 72 Deg F, to helpusers. Other examples of engineering units are: % Humidity and DegC. Type up to 12 characters (including spaces). Don’t use quotationmarks.

Description A description of up to 32 characters (including spaces) is optional, buta good explanation helps users when they need to test, modify, or manipulate the point.

Channel andIOU Numbers

(NetControllersOnly)

Set channel and IOU numbers so the point’s value can be read or changed by a display module.

Enter the channel number as it is marked on the controller.

Enter an IOU number.




Direction Direction is required only if the point’s value can be read or be changedby a display module. Select one of the following from the Directiondropdown menu:

IOInput Allow changing the point value from the controller only.

IOOutput Allow changing the point value from the controlsystem only.

IOBidirectional Allow changing the point value from both the

controller and the control system.

BACnetObject Type

If this Infinity Numeric is associated with a BACnet device (b4, bCX140x0, or b3 controllers only) then it must become an AnalogValue,BinaryValue or MultistateValue object. From the dropdown menu, select AnalogValue, BinaryValue, or MultistateValue. See About BACnet Objects at the end of this chapter, and see Chapter 14, BACnet .

State Select Enabled or Disabled from the dropdown menu. The controlsystem can change an Enabled point from a program or report, but nota Disabled point.

Setpoint Check the Setpoint checkbox so the controller stores the current pointvalue in the CyberStation database.

Format The format field is where you specify what display format you want touse to present the Value attribute to the operator. The # sign is aplaceholder. Examples:

###.### would be a number with three decimal places

$### would equal on/off/-on.

Exported If Exported is checked, it means that programs or reports on another controller use this point's value or has an alarm attached.

Continuing On

Once you have tested the point, reopen the editor and complete the remaining tabs tofinish configuring the point.

Enter information into the Triggers, Alarms, Logs, and XDriver tabs of theInfinityNumeric editor. Complete these tabs using the explanations provided earlier in thischapter for completing the same tabs of the InfinityInput editor.


Creating an InfinityDateTime Object

You create an InfinityDateTime object in the same way that you created an InfinityInputobject. Repeat the steps for InfinityInput, but replace the word InfinityInput withInfinityDateTime throughout the steps. This brings up the InfinityDateTime editor:



TAC 270

Note: For instructions on how to use objects editors in general refer to Chapter 3.

The InfinityDateTime General TabInfinityDateTime points store date and time information used in schedules and are usedto create time stamps. They print from Plain English in the format: MM/DD/YY .

Value The initial value of a newly created InfinityDateTime point is 1/1/89.Enter value in the text field or set it from the command line.

Description A description of up to 32 characters (including spaces) is optional, buta good explanation helps users when they need to test, modify, or manipulate the point.

Channeland IOUNumbers


Enter the channel number as it is marked on the controller. Enter an

IOU number.

On 9200 CX controllers, IOU numbers are set with dipswitches. After you enter these numbers, select a direction, if applicable (NetController only).





IOInput Allow changing the point value from an Andover Continuum display module only.



Andover Continuum display module and thecontrol system.

State Select Enabled or Disabled from the dropdown menu. The controlsystem can change an enabled point from a program or report but nota disabled point.


Exported The Exported attribute is set by the control system. A check in theExported checkbox means that programs, reports, or alarms onanother controller use this point's value.

Continuing On

Once you have tested the point, reopen the editor and complete the remaining tabs tofinish configuring the point.

Enter information into the Triggers, Logs and XDriver tabs of the InfinityDateTime editor.Complete these tabs using the explanations provided earlier in this chapter for theInfinityInput editor.


Creating an InfinityString Object

You create an InfinityString object in the same way that you created an InfinityInputobject. Repeat the steps from the InfinityInput procedure, but replace the wordInfinityInput with InfinityString throughout the steps. This brings up the InfinityString

editor, shown on the next page.The InfinityString General Tab

InfinityString points are storage locations for plain text messages in an Infinity controller’smemory. These can include logical paths to physical devices such as printers, or messages that are displayed to an operator.



TAC 272

Value This field is blank in a newly created point.

Description A description of up to 32 characters (including spaces) is optional,but a good explanation helps users when they need to test, modify,or manipulate the point.

String Size The default InfinityString point size is 132 characters. You can set alower number, being sure to pad the size in case you later changethe string. The control system truncates characters that exceed thespecified string size.

Channel andIOU Numbers

(NetController Only)


Enter the channel number as it is marked on the controller.

Enter an IOU number.

On 9200 series CX controllers, IOU numbers are set withdipswitches.

After you enter these numbers, select a direction. (See below.)





IOInput Allow changing the point value from the controller only.



controller and the control system.State Select Enabled or Disabled from the dropdown menu. The control

system can change an enabled point from a program or report, but nota disabled point.


Continuing On

Once you have tested the point, reopen the editor and complete the remaining tabs tofinish configuring the point. Enter information into the Triggers, Logs and XDriver tabsof the InfinityString editor. Complete these tabs using the explanations provided earlier inthis chapter for the InfinityInput editor.


About BACnet Points

Just as Andover Continuum b4920, bCX1 40x0, and b3 BACnet devices must first becreated as InfinityController objects and InfinityInfinetCtlr objects, so too must the nineBACnet points, listed at the beginning of this chapter, first get created as Infinity points.Specifically, if they are attached to Andover Continuum BACnet controllers, they areinitially created as InfinityInputs, InfinityOutputs, and InfinityNumerics.

How Are BACnet Points Created?

When an InfinityController object is created for an Andover Continuum BACnet b4920 or

bCX1 40x0 controller, or when an InfinityInfinetCtlr object is created for an Andover Continuum BACnet b36xx, b38xx, or b39xx controller, both Infinity and BACnet points arecreated.



TAC 274

The following table illustrates this creation:

When you create this Infinity point for itsb4/bCX1 40x0 InfinityController or b3InfinityInfinetCtlr …

This BACnet object is also createdfor its corresponding b4/bCX140x0/b3 BACnet Device

InfinityInput (with analog electrical type) AnalogInput

InfinityInput (with digital electrical type) BinaryInput

InfinityInput (with multistate “supervised”electrical type)

MultistateInput

InfinityOutput (with analog electrical type) AnalogOutput

InfinityOutput (with digital electrical type) BinaryOutput

InfinityOutput (with multistate “tristate”electrical type)

MultistateOutput

InfinityNumeric (created as an AnalogValue) AnalogValue

InfinityNumeric (created as a BinaryValue) BinaryValue

InfinityNumeric (created as a MultistateValue) MultistateValue

BACnet Input and Output Objects – When you create an InfinityInput and select ananalog, binary, or multistate electrical type (via the ElecType field in the Settings tab of

the InfinityInput editor) a BACnet AnalogInput, BinaryInput, or MultistateInput is alsocreated, respectively.

BACnet Value Objects – When you create an InfinityNumeric and select AnalogValue,BinaryValue, or MultistateValue as the BACnet Device Type field in the General tab of the InfinityNumeric editor, a BACnet AnalogValue, BinaryValue, or MultistateValue is alsocreated, respectively.

These editors and their tabs are shown earlier in this chapter.

Note: For third-party BACnet devices that are integrated into the Andover Continuumsystem, AnalogInput, BinaryInput, and MultistateInput objects were already createdas objects on those third-party BACnet controllers.

When InfinityInputs, InfinityOutputs, and InfinityNumerics are first created, their BACnet

counterparts are not simultaneously created. The BACnet counterpart is created when,from Continuum Explorer, you highlight the BACnet controller (b4, bCX1 40x0, b3), rightclick, and from the popup menu select Send To Database. See Chapter 3 and Chapter 14.

In Continuum Explorer, after these BACnet points are created and learned into thesystem, they appear as Infinity points in the CyberStation/Infinity portion of the navigationpane, and as BACnet points in the BACnet Devices portion of the navigation pane. Onthe Infinity side, they appear in CyberStation/Infinity class folders beneath theInfinityController and InfinityInfinetCtlr object icons. Likewise, on the BACnet side, theyappear in BACnet default class folders beneath their Device icons. (See Chapter 3 andChapter 14 for more information on these Explorer views.)




BACnet

Andover Continuum fully supports the BACnet standard. Andover Continuum’s BACnetproduct line includes controllers, expansion IO modules, repeaters, routers, andCyberStation workstations modified as BACnet Operator Workstation (B-OWS). Thischapter describes CyberStation’s implementation of BACnet support, including BACnet-compliant editors and other BACnet features that help you successfully configure andintegrate BACnet devices into your building control system.

What is BACnet?

BACnet stands for Building Automation and Control network. It is a communicationprotocol, developed by the American Society of Heating, Refrigerating and Air-Conditioning Engineers, Inc. (ASHRAE), that allows products made by differentmanufacturers to be integrated into a single building automated control system. Thismeans that as long as they meet the ANSI/ASHRAE BACnet Standard, differentmanufacturers products can seamlessly communicate data to each other over a network.The types of products include controllers, workstations, actuators, and sensors. InBACnet, each of these products is referred to as a device.

In order for communications to occur between two different systems a common networktechnology is required. BACnet supports six different types of networks: Ethernet,

BACnet/IP, ARCNET, MS/TP, Point-to-Point, and LonTalk. Continuum supports MS/TP, atwisted-pair cabling arrangement based on the RS-485 standard, and BACnet/IP for itsBACnet networking requirements.

BACnet provides a standard to model each BACnet device in a building automationsystem network as a collection of software entities called objects. Each object ischaracterized by a set of attributes called properties. A third feature, called services, provides messages needed for manipulating the device’s objects and properties.

BACnet Objects

The BACnet protocol is based on objects, properties, and services. Objects are thelogical representation of system data. Objects may represent single physical points or

14



TAC 276

logical groupings/collections of points that perform a specific function. The BACnetstandard objects supported are:

AnalogInput AnalogOutput AnalogValueBinaryInputBinaryOutputBinaryValueCalendar

DeviceFileEventEnrollmentLoopMultistateInputMultistateOutputMultistateValueProgramScheduleTrendLogEventNotification (NotificationClass in the BACnet standard)

Properties

Objects are examined and controlled by a set of properties that belong to each object.BACnet properties are equivalent to attributes in CyberStation. (Refer to Key Concepts inChapter 1.) Examples of object properties are name, type, present value, status flags,high-limit, low limit, and so forth. The most commonly used property for interoperability isPresent Value.

Each BACnet device also has a device object containing properties that can be used toverify communications, identify the vendor, and identify software and firmware revisionand other characteristics of the device. The device object’s properties represent theexternally visible characteristics of a BACnet device.

Note: CyberStation provides object editors for most BACnet objects. The user interfacesin these editors have the same “look and feel” as other CyberStation/Infinity objecteditors. BACnet properties appear inside the editors, the way CyberStation

attributes do. (See the sections, BACnet Defined Objects and Infinity and BACnet Object Editors, later in this chapter.)

Important: While using these object editors, you will notice that certainproperties/attributes and, in some cases, entire sections and tabs areunselectable (appear gray). This means that they are not supported on or applicable to the device on which the object resides — for example, on Andover Continuum b4920, bCX1 (40x0 series), and b3 controllers, andcertain third-party BACnet devices.




Services

In order for two different devices to interoperate, a common set of services is required.BACnet services provide messages for accessing and manipulating properties of deviceobjects.

For example, the devices need to identify themselves (I Am, Who Is), read and write data(Read Property, Write Property), and so forth. BACnet defines 35 services that aregrouped into six categories:

Alarm and Event

Device ManagementFile Transfer Object AccessVirtual TerminalSecurity

Andover Continuum’s BACnet Product Line

The Andover Continuum line of BACnet products includes a variety of controllers,expansion modules, and other devices that conform to the ASHRAE standard’s BACnet Advanced Application Controller (B-AAC) device profile. Andover ContinuumCyberStation conforms to the ASHRAE B-OWS profile. Both the B-AAC controllers andthe B-OWS-enhanced CyberStation are classified as “native” BACnet devices, meaning

that they can interoperate directly with other manufacturers (third-party) BACnet devices.

BACnet-Related Documentation

For more information on BACnet, Andover Continuum’s BACnet product line, and Andover Continuum’s implementation of BACnet, please see the following:

• Introducing BACnet - A Guide for Continuum Users, 30-3001-863

• BACnet Controller Technical Reference, 30-3001-862

• bCX1 Series Controller Technical Reference, 30-3001-890

• ANSI/ASHRAE Standard 135-2004: BACnet A Data Communication Protocol for Building Automation and Control Networks

• BACnet PIC S ( P rotocol I mplementation C onformance Statements), located on theBACnet page of TAC’s tech support web site. PICS are detailed descriptions of adevice’s inherent BACnet capabilities. PICS tell a potential user what objects andBACnet services a device supports. It also details the type of communicationsnetwork, the baud rate, the range of values each object property expects andwhether or not a property is read-only. (This site’s BACnet page has many other useful BACnet documents.)

• CyberStation online help



TAC 278

Post Installation System Integration

Once the new BACnet hardware devices have been installed on your system andCyberStation software has been installed in accordance with the CyberStation InstallationGuide, 30-3001-720, start up CyberStation. (See Starting CyberStation in Chapter 1.)

Access the Continuum Explorer. Normally you will be in the All Paths view.

Locating BACnet Devices

To find new BACnet devices:

1. Ensure that setting 1, Enable BACnet , in the BACnet Preferences dialog is set to“True”. (See the BACnet Preferences dialog later in this chapter.)

2. Right click Root in the Explorer’s navigation pane.

The object dropdown menu appears:

3. Select Find New BACnet Devices.

The new BACnet network icon appears in the navigation pane.

4. Click the + sign next to display BACnet devices, folders, and other objects:

Note: You can also right click an InfinityController and select Find New BACnetDevices.

BACnet

Device Icons




BACnet Icons

In CyberStation, BACnet-related icons appear in the Explorer to differentiate betweenBACnet and non-BACnet devices. These icons are shown below.

BACnet Devices

Continuum Third Party Continuum i2 Third Party CyberStation

BACnet Device BACnet Device Workstation Workstation

(blue) (olive) (gray) (olive monitor) (blue monitor)

Folders

BACnet BACnet Default CyberStation Default

Folder Class Folder Class Folder (blue) (blue)

BACnet Class Objects

BACnet BACnet BACnet

AnalogInput AnalogOutput AnalogValue

BinaryInput BinaryOutput BinaryValue

MultistateInput MultistateOutput

Networks

BACnet

Network

Color differentiates between Andover Continuum (blue) and third-party (olive) BACnetdevices, folders, and workstations. Also, Andover Continuum i2 devices appear in gray.



TAC 280

The following illustration shows Continuum Explorer with many of these BACnet and non-BACnet icons. Note that the upper portion of the navigation pane shows Infinity (non-BACnet) icons, whereas the lower portion shows BACnet icons, beneath the BACnetnetwork icon:




Saving BACnet Devices to the Database

The new BACnet devices need to be added to CyberStation’s SQL database. By default,each new BACnet device icon has a yellow exclamation flag next to it. When you placethe cursor over the flag, the following tool tip appears:

Root\BACnet Device\ xxxxxxx requires a save to database.

CyberStation offers you two ways to accomplish this – manually or automatically.

Manual Save to Database

To manually save a BACnet device to the database:

1. Right click the BACnet device. A popup menu appears.

2. Select Send to Database option from the popup menu:

This causes the content of the device to be uploaded to the SQL database. Once theprocess is complete, select Refresh from the Explorer’s View menu (or click theExplorer’s refresh button) and the exclamation flag disappears from the device’s icon.

Automatic Save to Database

You can set up CyberStation so that each new BACnet device is automatically saved tothe database (upon learning of new BACnet devices) by performing the following

procedure:

1. Right click the Continuum icon in the window taskbar (tool tray).

2. Select BACnet Preferences from the popup menu:

3. In the BACnet Preferences dialog (shown on the next page) change the value of item 2, Automatically save new BACnet devices to the database, from False toTrue.



TAC 282

4. Find new BACnet devices. Right click over the Root directory in the Explorer, andfrom the popup menu, select Find New BACnet Devices. (See the procedure,Locating BACnet Devices, earlier in this chapter.)

Viewing Options

CyberStation offers you three ways to view Andover Continuum BACnet controllers in theExplorer. The choices are:

• As both Infinity/Infinet Controller objects and BACnet Device objects

• As BACnet devices only

• As a Infinity/Infinet controllers only

Viewing Both Infinity Controllers and BACnetDevices

To view Andover Continuum BACnet controllers as both Infinity/Infinet Controller objectsand as BACnet Device objects in the Explorer’s navigation pane:

1. From the Explorer’s View dropdown menu, select Show TAC BACnet Device As...

2. Select Infinity Controller and BACnet Device:




The navigation pane of the Explorer now reflects this viewing selection. For example:

Viewing BACnet Device Only

To view Andover Continuum BACnet controllers only as BACnet Device objects in theExplorer’s navigation pane:

1. From the Explorer’s View dropdown menu, select Show TAC BACnet Device As…

2. Select BACnet Device Only.

The navigation pane of the Explorer now reflects this viewing selection. For example:

Viewing Infinity Controller Only

To view Andover Continuum BACnet controllers as Infinity/Infinet Controller objects in theExplorer’s navigation pane:

1. From the View dropdown menu, select Show TAC BACnet Device As…

2. Select Infinity Controller Only.

b4920 controllers,b4Controller1 andb4Controller2 areshown with InfinityController icons in the

The same controllers(with the same names)are also shown with

bCX1 controllers, b4Controller1 andb4Controller2, do notappear as InfinityControllers in the Infinityportion of the tree.



TAC 284

The navigation pane now reflects this viewing selection. For example:

Disabling BACnet

The first setting (Enable BACnet) in the BACnet Preferences dialog allows you todisable communication with all BACnet devices on your system. To accomplish this:

1. Right click the Continuum icon in the window taskbar (tool tray).2. Select BACnet Preferences from the popup menu:

3. In the BACnet Preferences dialog, change the value on item 1, Enable BACnet,from True to False.

4. Change your viewing options to Infinity Controller Only:

Once you have performed this procedure, CyberStation no longer sends or responds toBACnet communication requests and works completely in the context of CyberStation/Infinity class objects.

To return to BACnet, change the Enable BACnet setting to True (its default setting) andchange your viewing option to Infinity Controller and BACnet Device.

bCX1 controllers,b4Controller1 andb4Controller2 , do not appear in the BACnet portion of the




BACnet View

The Explorer provides a BACnet View selection in its View dropdown menu. Thisselection shows only the BACnet portion of the Explorer tree. To use this view:

1. Click the down arrow attached to the Explorer bar icon in the quick pickstoolbar.

2. Select BACnet View from the dropdown menu:

The navigation pane shows the BACnet devices portion of the tree:

Hiding Out of Service DevicesYou can hide any out-of-service devices that you do not want to appear in the Explorer byperforming the following procedure:

1. In the Explorer, right click the device you wish to hide.

2. Select Open from the dropdown menu. The Device editor appears. (Refer to the nextpage.)

3. Check the Out of Service checkbox in the Device editor.

4. Click the editor’s OK button.

5. Select Hide Out of Service Devices from the Explorer’s View menu:

6. Select Refresh from the Explorer’s View menu, or click the Explorer’s refresh button

The selected device should not appear on the refreshed Explorer view.

Registering a BACnet Broadcast Management Device (BBMD)

If your workstation is designated as a BACnet Broadcast Management Device (BBMD),click the BBMD Registration button (located in the BACnet Preferences dialog) to viewthe BBMD Registration dialog, which is a list of system BBMDs that are registered withyour BBMD workstation — the other BBMDs that yours knows about. This list is aninternal table, known as the BBMD table. BBMDs ensure that broadcast messages aredelivered among all BACnet devices across subnetworks. Your BBMD must know aboutother BBMDs as part of the broadcast process. In addition to the BBMD table, eachBBMD also has a table of foreign devices. These are BACnet devices to which broadcastmessages are routed.



TAC 286

For each BBMD, the BBMD Registration dialog lists the IP address, network port,broadcast disk mask, and last "teach time" — the last time you used the Teach button toinform other BBMDs about the existence of your BBMD and BBMD table. (See Teaching BBMDs, below.)

Adding BBMDs

You may add a BBMD to your BBMD table, as follows:

1. From the BACnet Preferences dialog, click the BBMD Registration button:

The BBMD Registration dialog appears:

2. Click the Add button.

The Add BBMD dialog appears:




3. Enter the IP address, network port, and broadcast distribution mask of the BBMD.

Note: If you also want to learn about the BBMDs contained within the internal table of the BBMD you are adding, check the Import all BBMDs from device checkbox.The BBMDs from that table are added to the registered list (your table).

4. Click OK, then from the BBMD Registration dialog, click Refresh.

Teaching BBMDs

From the BBMD Registration dialog, you may teach other system BBMDs about theexistence of your BBMD (including the BBMDs listed in your internal BBMD table).

1. From the BACnet Preferences dialog (shown in previous section) click the BBMDRegistration button. The BBMD Registration dialog (shown in previous section)

appears.2. Click the Teach button. A window appears showing the progress of the teach

process, before the process completes. The Last Teach Time column in the BBMDRegistration dialog will reflect this teach.

Deleting BBMDs

From the BBMD Registration dialog, you may delete one or more BBMDs.

1. From the BACnet Preferences dialog, click the BBMD Registration button. TheBBMD Registration dialog appears.

2. Highlight (select) a BBMD entry in the list.

3. Click the Delete button, then click the Refresh button.



TAC 288

Note: Click the Exit button to dismiss the BBMD Registration dialog.

For important related BBMD information, see also the Details tab and the ForeignDevices tab of the Device editor, which is discussed next. For complete information onBBMDs, please see Introducing BACnet – A Guide for Continuum Users, 30-3001-863.

The Device Editor

Once a BACnet device has been saved to the CyberStation SQL database, you can openits Device editor. To do this, right click the Device icon in the Explorer’s navigation pane,

and select Open from the dropdown menu. The Device editor opens with the General tabdisplayed.

Note: When you are editing a BACnet Device object, fields in the editor will beunselectable (grayed-out) for those properties that the BACnet device does notsupport.

The General Tab

The general tab summarizes the network features of the device, most of which areautomatically supplied by the system. A few remaining inputs and actions are supplied bythe user. A summary of all the features on the tab is described below.

Description Name of the device and its node number.

BACnet NetworkNumber

Specifies the ID of the BACnet IP network




Model Name Displays a model name based on the information it receivesvia the BACnet protocol.

Device Node ID The node ID number assigned to the device

Device Status Based on the current status of the device, this displays one of the following:

Operational― indicates the device is working and is ready toreceive or transmit data.

DownloadRequired― indicates the device requires adownload of information

NonOperational― indicates the device is offline or that afault has been detected.

OperationalReadOnly― indicates the device is working andready to transmit data.

DownloadInProgress― indicates a download is in progressand the device will not be ready to transmit data until thedownload is complete.

Comm Status CyberStation sets the comm status to OnLine or OffLinedepending on whether the workstation is in communicationwith the device.

Primary AccessServer

Check this checkbox to designate this workstation as theprimary access server.

Secondary AccessServer

Check this checkbox to designate this workstation as thesecondary access server.

BACnet MAC Address The Media Access address assigned to the device.

Auto Download Enables a device to auto download schedules to controllers.

Probe Time Set the interval in seconds by which the device checks thecomm status of the other connected CX series controllers andCyberStation workstations. When the device does not receivea response from another CX controller or CyberStation within

the probe time, it changes their comm status to Offline.



TAC 290

Probe Type From the dropdown menu, select one of the following.

Note: Probe Type is used only for third-party BACnet devices.

Probe — Probing occurs at the interval specified in ProbeTime. The default is 60 seconds. The advantage of this is thatCyberStation detects a device going offline regardless of whether or not CyberStation is attempting communicationswith the device. The disadvantage is excess probe traffic for devices.

ProbeOnDemand — Probing does not occur unless acommunications transaction with the target device fails. Oncea transaction fails then probing occurs at the interval specifiedin Probe Time until the device comes back online. Theadvantage is that additional requests to the controller failimmediately. The disadvantage if that node failure is notdetected until a CyberStation application needs tocommunicate with a controller.

ProbeOff — Probing does not occur. The advantage is thatthere is never probe traffic to the device. The disadvantage isthat each request to the device fails only after the transactiontimes out.

BACnet Max Master The Max Master property is a value that specifies the highestpossible address for master nodes.

Out of Service When checked, hides the selected device. (See Hiding Out-of-Service Devices, earlier in this chapter.)

BACnet Workstation Add check in checkbox to identify a third-party device as aworkstation. It will show up as an olive computer icon in theExplorer.

Location Type in the physical location of the device (optional).

Container Type Enter up to 32 characters of text that indicates the container type (workstation).

Serial Number Specifies the controller’s serial number, which is retrieved

once the workstation is in communication with the controller and you have used the Teach button to update your network.

Default Folder Specifies the default folder under which the device will appear.

Reinitialize Device When selected, brings up the Reinitialize Device dialog. (Seebelow.)

Teach Invokes the teach mode (see next page)




Reinitializing Andover Continuum BACnetControllers

Andover Continuum BACnet controllers contain EPROM flash memory that can beupgraded electronically. Whenever a reset is desired or power failure occurs, thesecontrollers can be reinitialized. This can be accomplished as a cold start or a warm start,defined as follows:

• Cold Start — when the controller comes up from a reset and recalls a backup copyof the controller’s original RAM database

•

Warm Start — when the controller comes up from a reset and recalls a copy of thecontroller’s database at the time the reset or power failure occurred.

To reinitialize a controller proceed as follows:

1. Click the Reinitialize Device button (previous page) to bring up the ReinitializeDevice dialog:

2. Click the State field’s down-arrow button to open the dropdown menu.

3. Click the desired reinitialize state (Coldstart or Warmstart).

4. Enter your password in the Password field. (Enter password on third-party BACnetdevices only. Andover Continuum BACnet controllers do not require a password.)

5. Click the OK button.

Teach

Click this button to perform a manual "teach". This updates or "teaches" all Infinity

controllers (including Andover Continuum BACnet controllers) about this CyberStationdevice and teaches all Infinity controllers about each other and about all devices.

Note: The Teach feature is implemented on CyberStation devices only. It is notimplemented on BACnet devices.

When you click the Teach button, a Select Teach Mode dialog appears:



TAC 292

Teach supports two modes of operation:

Mode Description

Device Teach Click the Device Teach radio button to teach all Infinity controllers,including b4920/bCX1 (40x0 series) controllers, on the network aboutthe existence and properties of this device.

Global Teach Click the Global Teach radio button to teach everything – to teacheach Infinity Controller, and each b4920/bCX1 (40x0 series) controller,about the other Infinity controllers that are on the same network, and toteach all Infinity controllers about all devices.




The Details Tab

The Details tab supplies various information about the BACnet device. Two of the mostimportant items on this tab are the Supported Object Types and the SupportedServices windows, which list the objects and services that are supported by the device.This tab also allows you to designate this device as a BACnet Broadcast ManagementDevice (BBMD) or register this device as a foreign device with an existing BBMD.

Supported Services Lists the types of BACnet services that are supported bythe device.

Supported Object

Types

Lists BACnet objects that are supported by the device.

Vendor Name Displays the name of the vendor who manufactured thedevice.

Vendor ID Displays the vendor's corporate ID number.

Software Revision Displays the version number of the software applicationsupported by this device.

Firmware Revision Displays the version number of the device’s firmware.



TAC 294

Protocol Version Displays a number that indicates which specific set of standardized protocol services and object classes thisobject supports.

Protocol Revision Displays the version number of the firmware innate to thestandardized protocol services and object classes thisobject supports.

Database Revision Displays the version number of the CyberStation database.

Max APDU Length

Accepted

Represents the maximum number of octets that may be

contained in a single, indivisible application layer protocoldata unit.

APDU Retries Displays the maximum number of times that an APDU(application protocol data unit) shall be retransmitted. Thedefault value is 3. If you have access permission, you maychange the number in this field.

APDU Timeout Displays the amount of time in milliseconds betweenretransmission of an APDU requiring acknowledgment for which no acknowledgment has been received.

The default value is 60,000 milliseconds. If you haveaccess permission, you may change the number in thisfield.

Max Info Frames Specifies the maximum number of information frames thatmay be sent before the device must pass the token. Thefield is selectable (writable) if this device is a node on anMS/TP network. If it is not writable or otherwise user-configurable, its value shall be 1.

Segmentation Support Indicates whether or not this device supports segmentationof messages, and if so whether it supports segmentedtransmission, reception, or both. The possible values arelisted below:

Segmented Both – Supports both segmented transmissionand reception.

Segmented Received – Supports only segmentedreception.

SegmentedTransmit – Supports only segmentedtransmission.

NoSegmentation – Does not support segmentation.




Segment Timeout Displays the amount of time in milliseconds betweenretransmission of an ADPU segment. The default value is2000 milliseconds.

In order to achieve reliable communication, allintercommunicating devices should have the sameSegment timeout value.

If you have access permission, you may change thenumber in this field.

Max SegmentsAccepted

Displays an integer that represents the maximum number of message segments allowed.

Max # of AsyncRequests

Note: This attribute is used only for third-party BACnetdevices.

This attribute specifies how many concurrent requests willbe sent to the device. You may either:

Accept the default (1). This is non-concurrent.

Enter another integer that specifies the maximum number of concurrent requests that the Pinpoint graphicsapplication can send to this device to update the values of points and objects attached to graphic controls inside an

open Pinpoint graphics file.Accepting 1, the default — Accepting 1, the default,means that the requests (or the "polling" of point/objectvalues) occur one request at a time. When you accept 1,the request interval (time between requests) must also beset. (See Request Interval, below.)

Note: For the least impact on network performance, thedefault is recommended. This avoids heavy pollingtraffic.

Changing the Default Value — When you enter an integer of 2 or higher, Pinpoint polls the device in multiple,concurrent read-property requests. Use this feature if you

believe the Pinpoint data-value updates are too slow.

Concurrent polling works best for devices attached to anEthernet network. It is not recommended for devicesattached to a field-bus network, such as MS/TP.

Note: The Request Interval field (see below) is notselectable if you enter a value of 2 or higher. The Request Interval field is used only for sequential(non-concurrent) data polling (when the value is 1).



TAC 296

Request Interval Note: This attribute is used only for third-party BACnetdevices.

This field can be set only when the Max # of AsyncRequests is set to 1 (the default).

The request interval is the number of milliseconds thatelapse between two sequential (non-concurrent) data-valuerequests. (The Pinpoint graphics application sendsrequests to this device to update the values of points andobjects attached to graphic controls inside an open Pinpointgraphics file.

See also Max # of Async Requests, above.)

You may either:

Accept the default value (500 milliseconds).

Enter another value, in milliseconds.

Note: For best performance, the default (500 milliseconds)is recommended.




BACnet BroadcastManagement Device

Check this checkbox if the device is a BACnet BroadcastManagement Device (BBMD). A BBMD facilitates thedelivery of broadcast messages among BACnet deviceslocated on different TCP/IP subnetworks.

Note: As of this version, a workstation and a bCX1 40x0controller can be designated a BBMD.

By default, this checkbox is not checked. When it is notchecked, you may register this device (as a foreign device)with an existing BBMD.

Enter values in the fields of the Foreign DeviceRegistration section, located beneath the checkbox. Thesefields are described below.

A foreign device is a BACnet device that has an IP subnetaddress different than other BACnet devices with which itmust share broadcast communication.

When you check it, the Device editor also displays aForeign Devices tab, which lists foreign devices that areregistered — all the ones that the BBMD knows about. TheForeign Devices tab is described later in this chapter.(Each BBMD has an internal table of foreign devices, as

well as an internal table of other BBMDs.)Note: See also Registering a BACnet Broadcast Management Device (BBMD), earlier in this chapter.. TheBBMD Registration feature allows you to maintain aregistered list of other BBMDs (the internal table of BBMDs).

For complete information on BBMDs, please see Introducing BACnet - A Guide for Continuum User s, 30-3001-863.

Foreign Device Registration

BBMD IP Address Enter the IP address of the BBMD with which you want toregister this device as a foreign device. This field defaults to0.

BBMD Port Enter the BACnet network port (hexadecimal integer) of theBBMD with which you want to register this device as aforeign device. This field defaults to 0xBAC0.

Time to Live Enter the number of seconds that a foreign deviceregistration is active that is, how long it remains registeredin the table of foreign devices of the BBMD. If no re-registration occurs before the time expires, the foreigndevice is purged from the table when the time expires.

The default is 300 seconds (5 minutes).



TAC 298

Note: For complete information on all BACnet properties, please see ANSI/ASHRAE Standard 135-2004: BACnet A Data Communication Protocol for Building Automationand Control Networks.

The Backup/Restore Tab

Using the Backup/Restore tab, you can automatically back up configuration informationfrom this BACnet device to your database, as well as automatically restore it from thedatabase to this device. The configuration information resides in a special configurationfile, which is stored as an object — the BACnet class object, File. (See Chapter 21.) You

can also archive it locally in a text file (ASCII dump file.)

The backup selections on this tab — see also the editor attributes table below — allowyou to:

• Back up configuration information (stored in a special File object called ACCConfiguration) for this BACnet controller and save it to your CyberStationdatabase.

Note: You can also perform this operation for one or more devices via the right-clickcontainer popup menu in Continuum Explorer's navigation pane. Please seeBacking Up a Device's Configuration in Chapter 21.




• Back up configuration information for this controller from the database and archive itinto a text (ASCII dump) file.

• Simultaneously back up this controller's configuration information to the databaseand copy (archive) it to a text (ASCII dump) file.

The restore selections on this tab — see also the editor attributes table below —allow you to:

• Restore configuration information from your database to this BACnet controller.

Note: You can also perform this operation for one or more devices via the right-click

container popup menu in Continuum Explorer's navigation pane. Please seeRestoring a Device's Configuration in Chapter 21.

• Restore archived configuration information (contained in a text ASCII-dump file) toyour database.

• Simultaneously restore the archived configuration information (contained in a text ASCII-dump file) to your database and to this controller.

The File object — When a backup operation is performed for a BACnet device, a Fileobject (a BACnet class object) is created. This object, which is stored in the File objectclass folder residing in its respective BACnet controller, is named ACCConfiguration andit contains configuration information for that controller — all the configuration settings for objects in the controller.

For more information please see Chapter 21, Managing Configuration Files.

Backup To Database Time Displays the last date/time the configuration informationwas backed up from the controller to the database.

Backup Failure Timeout Enter the time to allow a backup to complete before abackup operation ends due to a timeout.

Last Restore To DeviceTime

Displays the date/time the configuration information waslast restored to the controller.

Last Restored Archive File Displays the path of the last archive (.dmp) file to berestored.



TAC 300

Backup Select one of the radio buttons to perform a backupoperation, as follows:

To Database — Back up the content of the ACCConfiguration file from this controller and save it toyour database.

Database To Archive — Back up the saved configurationin your database from the database to an archived(ASCII .dmp) file. In the Archive File Name field, clickthe browse button, search for, and select the file intowhich you want to archive the information.

To Database and Copy to Archive — Perform bothbackup operations. That is, back up ACCConfigurationfrom this controller to the database and archive it to an ASCII .dmp file. In the Archive File Name f ield, click thebrowse button, search for, and select the file into whichyou want to archive the information.

When you have selected the operation you want and (if needed) have selected an archive file, click the Backup button to execute the backup operation. For Andover Continuum BACnet controllers, the DistributionProperties dialog appears, showing progress messages

about the status of the backup operations.

For some third-party BACnet controllers, you are firstprompted to enter a password. If the password isaccepted, the operation begins.

Restore Select one of the radio buttons to perform a restoreoperation, as follows:

From Database — Restore the content of the ACCConfiguration file from your database to thiscontroller.

From Archive to Database — Back up the content of anarchive file to the database. In the Archive File Name

field, click the browse button, search for, and select thefile whose configuration information you want to restoreto the database.

From Archive To Database and Device — Back up thecontent of the archive file to the database and to thecontroller. In the Archive File Name field, click the browsebutton, search for, and select the file from which youwant to restore to both the database and controller.

Configuration Files In Archive — This window listsone or more ACCConfiguration file images containedwithin the particular archive (.dmp) file that you have




selected. It helps you identify whether or not this is thecorrect archive file that you want to restore.

Archive Backup Time — When you select the archive(.dmp) file that you want to restore, this field displays thelast time that the information in this archive file wasbacked up from the controller to the database. Thistimestamp helps determine whether or not this is thearchive file that you want to restore.

Note: You may use the restore operations on this tab torestore archive-file information to one or morecontrollers. To do so, access the Device editor for everycontroller to which you want to restore the archivedinformation.

When you have selected the operation you want and (if needed) have selected an archive file, click the Restore button to execute the restore operation. For Andover Continuum BACnet controllers, the DistributionProperties dialog appears, showing progress messagesabout the status of the restore operations.

For some third-party BACnet controllers, you are firstprompted to enter a password. If the password is

accepted, the operation begins.

The Known Devices Tab

The Known Devices tab lists the BACnet devices that exist on the network that can bemonitored by this device. Entries in the list identify the actual device addresses that areused when the device is accessed via a BACnet service request.



TAC 302

Device Displays the path of the device.

BACnetNetworkNumber Specifies the ID of the BACnet network.

BACnetMacAddress The Media Access address assigned to the device.

The Foreign Devices Tab

If this device is designated as a BACnet Broadcast Management Device (BBMD), thenthis Foreign Devices tab appears in the Device editor:

This tab lists all the foreign devices contained in the BBMD's internal foreign device table. A foreign device is a BACnet device that has an IP subnet address different from thosecomprising the BACnet/IP network. Foreign devices are registered with a BBMD. Thisregistration makes it possible for the BBMD to facilitate the delivery of broadcastmessages among registered BACnet devices located on different system subnetworks.

Note: The BACnet Broadcast Management Device checkbox on the Details tab mustbe checked for the Foreign Devices tab to appear.

For more information on BBMDs, please see Introducing BACnet – A Guide for Continuum Users, 30-3001-863.

For each foreign device listed, this tab displays the following information. The values inthis tab reflect the properties of subscriptions of foreign devices registered withCyberStation.

• IP Address — The IP address of the BBMD with which you want to register thisdevice as a foreign device. This is specified in the Details tab.

• Port — The BACnet network port (hexadecimal integer) of the BBMD with which youwant to register this device as a foreign device. This is specified in the Details tab.




• Time To Live — The total number of seconds that a foreign device registrationinactive – that is, how long it will be registered in the table of foreign devices of theBBMD. If no re-registration occurs before the time expires, the foreign device ispurged from the table when the time expires. This is specified in the Details tab.

• Time Remaining — The number of remaining seconds that a foreign device will beregistered in the table of foreign devices. If the foreign device is not re-registeredbefore this time expires, then it is purged from the table when the time expires.

The Time Tab

The Time tab is where you synchronize the BACnet device time and date to the systemslocal time and date:

Local Time Enter the local time – hour: minutes: seconds AM or PM

UTC Offset Enter the Universal Time Coordinate (UTC) offset in minutes. Thisis the difference in minutes between your local time and GreenwichMean Time.

Note: When entering this number, use the opposite sign (negativeor positive) from what you actually want the system to write.For example, if you are 300 minutes (5 hours) ahead of GMT,enter: -300 If you are -240 minutes (4 hours) behind GMT,enter: 240

Local Date Enter the date – month/ day/ year.

Daylight Savings Check if daylight savings time is in effect.

Synchronize toLocal Time andDate

Use the BACnetDevice window to locate the new BACnet device.(See below.)

To synchronize the new BACnet device with the system’s local time and date:

1. Scroll through the BACnetDevice window to locate the new BACnet device.



TAC 304

2. Click the device to highlight it.

3. Click the Add button.

4. Click the Sync Time button.

Note: To remove a BACnet device’s local time and date from the system, perform steps1 and 2 (above), and the click the Delete button.

The Alarms Summary Tab

This tab provides an alarm summary from the BACnet device each time the Refresh button is selected:

Event Object Displays the event object that caused the alarm.

Alarm State Displays the state of the alarm.

Acked Transitions Displays one of three alarm acknowledgement transitionevents:

ToOffnormal

ToFault

ToNormal

These are cleared upon the occurrence of the correspondingevent and set under any of these conditions:




Upon receipt of the corresponding acknowledgment

Upon the occurrence of the event if the corresponding flag isnot set (meaning event notifications will not be generated for this condition and thus no acknowledgment is expected)

Upon the occurrence of the event if the corresponding flag isset (meaning no acknowledgment is expected)

The Preferences Tab

Note: The Preferences tab is only applicable to CyberStation workstations. It is notsupported for Andover Continuum b3, b4920, and bCX1 (40x0 series) devices or for third-party BACnet devices.

This tab presents settings that you set by typing in values, selecting the location of filesand file paths from dropdown menus, or selecting true or false conditions.

Setting Description Value

1 Command Prompt in the Command Lineapplication

Command prompt for the CyberStationcommand lineapplication.

2 The location of the badge format files Select files from thebrowse dialog.

3 The default badge format Type in the format.



TAC 306


4 Default Report Viewer Type in the reportviewer file(notepad.exe, and soon)

5 Increment Report File Select True or False

6 Maximum entries in the Alarm Viewer Type in the number.

7 Maximum entries in the Access Event Viewer Type in the number.

8 The location of the Plain English Wizard files Type in the file path.

9 Path to the Alarm Printer Type in the file path.

10 Suppress form feeds when printing alarms Select True or False.

11 Use preset image cropping Select True or False.

12 thru14

Alarm, Return to Normal and Fault Email Formatfile path for each item

Use the Open dialog toselect the file path.

15 thru17

Acknowledge File Path for each item Use the Open dialog tocheck the path.

18 The file name of main menu Use the Open dialog to

check the path.19 Enables and disables the immediate distribution of

personnel records from this workstation tocontrollers on the local area network (LAN).

True (enabled) is the default. When this feature isenabled, the workstation inspects the status of thedatabase, and if there are pending distribution-event transactions, it performs the distributions.

Note: This preference should be set only by asystem administrator.

When to disable this preference — Typically, you

would set this preference to False if theworkstation is running a lot of applications, suchas graphics.

If there are several workstations at this site,disabling it on the web server may result in better performance. It also gives you the choice of turning it off for a workstation that is shut down atthe end of a day.

When to enable this preference — Typically, youwould set this preference to True for workstationsthat are dedicated servers (running 24 hours per day and seven days per week, typically in a back

Select True or False.





room) and for other workstations based on thenumber of distributions and throughput. The moreworkstations that are distributing, the faster thedistribution occurs.

For related information, please see Chapter 20,which describes the Access Distribution View .

20 Enables and disables the immediate distribution of

personnel records from this workstation tocontrollers on remote access services (RAS)networks.

True (enabled) is the default.

When this feature is enabled, the workstationinspects the status of the database, and if thereare pending access distributions, it performs thedistributions.


The guidelines for disabling and enabling this

preference (given in setting 19) also apply tosetting 20. Please see setting 19, above.

For related information, please see Chapter 20,which describes the Access Distribution View .


21 Enables and disables the downloading of extended log data from the controllers on the localarea network (LAN) to this workstation.

TRUE (enabled) is the default.


When to disable this preference — Typically, you

would set this preference to FALSE if theworkstation is running a lot of applications, suchas graphics. If there are several workstations atthis site, disabling it on the web server may resultin better performance. It also gives you the choiceof turning it off for a workstation that is shut downat the end of a day.

When to enable this preference — Typically, youwould set this preference to TRUE for workstations that are dedicated servers (running24 hours per day and seven days per week,typically in a back room) and for other




TAC 308


workstations based on the number of amount of downloading and throughput.

For more extended log preference settings,please see the description of the GeneralPreferences dialog in Chapter 13.

22 Enables and disables the downloading of extended log data from the controllers on a

remote access services (RAS) network to thisworkstation.

TRUE (enabled) is the default.


The guidelines for disabling and enabling thispreference (given in setting 21) also apply tosetting 22. Please see setting 21, above.

For more extended log preference settings,please see the description of the GeneralPreferences dialog in Chapter 13.


23 Establishes the data-refresh rate for an activegraphic in the web.Client Pinpoint graphicsapplication.

Note: Graphics objects are created inCyberStation, in Pinpoint “design” mode.You may not create, design, or modifygraphics objects in web.Client. However, inweb.Client you may open a graphic panel,monitor its values and, in “run” mode,dynamically adjusting those values. (Seethe web.Client online help.)

Enter the rate (in seconds) at which you want to

poll values in web.Client Pinpoint graphicscontinuously and automatically. When web.Clientgraphics are in use, they are automaticallyrefreshed at this rate. The default is 5 seconds.

Type in the number of seconds or accept thedefault.





24 This setting is used by the CyberStation Pinpointgraphics application.

Enter a rate (in milliseconds) at which you want topoll graphics panel values in real time and refreshthe canvas in a Pinpoint graphics object, when theapplication is active (selected in the foreground ona PC). The range of acceptable values is 20 msto 32000 ms (32 seconds). The default is 20.Setting a value outside this range generates anerror message.

Tips: Using the default or another low number means that graphics are constantlyrefreshed. However, some processors maybecome sluggish if they are less able tohandle such a rapid rate. In this case, youwould want to use a higher number, such as250 or 500 ms, to stabilize performance.

Enter the rate inmilliseconds.

25 This setting is used by the CyberStation Pinpointgraphics application.

Enter a rate (in milliseconds) at which you want topoll graphics panel values and refresh the canvasin a Pinpoint graphics object, when the applicationis inactive (not selected in the foreground on aPC). The range of acceptable values is 20 ms to32000 ms (32 seconds). The default is 20. Settinga value outside this range generates an error message.

For some usage tips, see the note in setting 24,above.

Enter the rate inmilliseconds.

26 Use Personnel Manager.

True is the default selection, indicating that the

Personnel Manager, a powerful and easy-to-usetool for creating, editing, and managing Personnelobjects is the editor for Personnel objects at thisworkstation. Select False if you want to use thePersonnel editor, a dialog similar to other CyberStation editors.




TAC 310

Security Level Tab

The access permissions configured in a security level allow you to customize(deny)access to individual CyberStation objects.

Security levels are actual CyberStation objects (Security Level objects) configured via theSecurity Level editor.

A security level can deny access to a CyberStation object editor on a page-by-page basisusing object-level security. Object-level security is a way to deny user groups the abilityto create, delete, or change individual CyberStation objects. Every object editor inCyberStation has a Security Level tab that displays a list of all existing security levelobjects. Selecting a security level object here attaches that security level to the objectbeing edited.

To attach a security level to this point, locate the security level in the Name column andclick the radio button next to it. To detach a security level from this point, locate thesecurity level in the Name column and double-click the radio button to remove the blackdot it contains. Or you can right click the security level in the Name column to bring up a

popup menu. Click Clear Selection in the popup menu.Refer to Chapter 4 for information on the attaching security levels to a BACnet device.

The Next Step

Once you are finished with the BACnet Device editor, you can begin to configure alarmsfor your BACnet devices.




Configuring BACnet Alarms

Configuring alarms for BACnet devices deviates somewhat from the standardCyberStation alarm configuring procedure described in detail in Chapter 10. Basically, toconfigure a standard CyberStation alarm you:

• Create the EventNotification object(s)

• Create the AlarmEnrollment object(s) associated with the EventNotification object

• Attach AlarmEnrollment objects to the point to be monitored

However for configuring BACnet devices the BACnet object class, EventEnrollment, replaces the AlarmEnrollment object.

The EventEnrollment Object

The EventEnrollment object is required for BACnet systems. It defines a standardizedobject that represents and contains the information required for managing events withinBACnet systems. An EventEnrollment defines criteria that, when applied to the attachedobject, will generate an event and transmit an event message to recipients defined by theattached EventNotification. The EventEnrollment object contains the event-typedescription, the parameters needed to determine if the event has occurred, and a link toan EventNotification object and the object to which the event applies. You use theEventEnrollment editor to access and edit EventEnrollment objects.

Creating The EventEnrollment Object

To create an EventEnrollment object, perform the following procedure:

1. In the Explorer’s navigation pane, right click the icon of the device to which you wantto add an EventEnrollment.

Note: For Andover Continuum b4920, bCX1 (40x0 series), and b3 controllers, rightclick its InfinityController or InfinityInfinetController object icon, respectively, inthe upper Infinity portion of the navigation tree. For third-party devices, rightclick its Device object icon in the BACnet portion of the navigation tree. Youcannot create an EventEnrollment for a b4920, bCX1 (40x0 series), or b3controller via its BACnet Device object.

2. From the New dialog, select EventEnrollment:

3. When the New dialog appears, enter a name for the EventEnrollment object in the

Object name field.4. Click the Create button to create the object and bring up the EventEnrollment editor.



TAC 312

Using the EventEnrollment Editor

The EventEnrollment editor contains four tabs that you use to define the event object. Indoing this you will make decisions based on the following questions:

Which property will trigger this event?

You’ll answer this question by selecting an Event Property on the General tab. Most

of the time alarms are set up to monitor the value event.

Who will be notified of this alarm?

You’ll answer this question by making selections in the EventNotification and

Recipient dropdown menus on the General tab. EventNotification objects determine,

among other things, which workstations receive notification, and which methods are

used for notification. (Refer to About EventNotification Objects in Chapter 10.)

What Algorithm will this event use?

You’ll answer this question by selecting an algorithm and providing its parameters on

the Algorithms tab. An algorithm is a set of rules by which an alarm is evaluated.

The type of algorithm is determined by the Event Type selection you make on the

General tab.

What will operators see and hear when this alarm goes off?

You’ll answer this question by writing text messages and selecting audio files for each event state. The text messages you write appear in the Active Alarm View,

alarm status bar, alarm log, emails, pages, and printer output. (Refer to Active Alarm

View in Chapter 10.)




The EventEnrollment General Tab

The General tab is where you enter basic information about the event.

Description Type a description of the EventEnrollment object. It can be up to32 characters (including spaces) in length.

Event Notification Browse for an EventNotification object. This will insert the correctpath and object name into the Event Notification field.

Object Browse for the applicable event object.

Event Property Browse the BACnet properties listing in the dropdown menu, andselect a property. The list includes all of the properties for all of the BACnet objects. Except for the TrendLog object, Andover Continuum only supports the Value property. For a TrendLogobject, the Event Property may also be LogBuffer.

Send When checked, each Send option causes the event to bedisplayed in the Active Alarm View and all recipients on thenotification list when the associated point changes to that status.

The Alarm option reports the alarm when the point goes into analarm (OffNormal) state.

The Return to Normal option reports the alarm when the pointreturns to normal.

The Fault option reports the alarm when a BACnet device local tothe point detects and reports a mechanical fault.



TAC 314

Event Type The selection you make here determines what fields display onthe Algorithms tab of this editor.

The choices of BACnet event types are:

Change of Bitstring

Change of State

Change of Value

Command Failure

Floating Limit

Out of Range

Buffer Ready (for TrendLogs – Chapter 17)

Note: The Change of Bitstring and Command Failure algorithmsare selectable for third-party BACnet devices only. They are notavailable for Andover Continuum b4920, bCX1 (40x0 series), andb3 BACnet devices.

When you attach a TrendLog as an object, Buffer Ready isalways displayed in this field, and LogBuffer is always displayedin the Event Property field. (Please see a related procedure inChapter 17, Configuring TrendLogs, for configuring algorithmic

notifications for TrendLogs.)

Notification Type From the dropdown menu, select a notification type. Thenotification type specifies whether the notification messagebecomes an alarm message, an event message, or a message of event acknowledgement.

AlmNotification – Defines the event as type alarm, appearing inthe Active Alarm View when the event occurs.

EvtNotification – Defines the event as type event , appearing in Active Alarm View when the event occurs.

Acks – Defines the event as type ack-notification, appearing inthe Active Alarm View when the event occurs.

*Recipient Select workstation to receive the alarm from the browse dialog.

*Process Id Identifies the process in the receiving device for which notificationis intended.

*Priority Property of type Unsigned that convey the priority to be usedwhen issuing event notifications in the case when a NotificationClass object is not used. The purpose of prioritization is toprovide a means to ensure that alarms or event notifications withcritical time considerations are not unnecessarily delayed. Thepossible range of priorities is 0 - 255. A lower number indicates ahigher priority.




*ConfirmedNotification

Property of type BOOLEAN , shall convey whether confirmed(TRUE) or unconfirmed (FALSE) event notifications shall beissued when a Notification Class object is not used.

*Only applicable to third party devices. Grayed out for all Andover Continuum devices.

The EventEnrollment Algorithms Tab

The Algorithms tab is where you set the parameters for the algorithm that will be used toevaluate the event. The appearance of this tab is determined by the Event Type selection that was made on the General tab.

Time Delay Time Delay appears on the Algorithms tab for all of the Event Typeselections, except Buffer Ready. (See the General tab.)

Type the number of seconds in the Time Delay field you want topostpone evaluating the alarm.

For example, you may decide that the point value can exceed or fallbelow its alarm boundaries for 30 seconds before the alarm goes off. If at the end of the 30 seconds, the object is in alarm, the alarm goes off regardless of its state during the 30-second delay.

Using time delays cuts down on the number of active alarms andreduces both system traffic and operator responsibility by filtering outsome nuisance alarms.

Algorithm Parameters

The other fields that appear on the Algorithms tab differ according to the Event Type selected on the General tab. The above figure reflects an Out of Range Event Typeselection. The algorithm parameters that you set for each of the event types aredescribed on the following pages.



TAC 316

Algorithm Parameters for an Out of Range Event

When you select Out of Range from the Event Type on the General tab, the fieldsshown below appear on the Algorithms tab:

High and Low Limits

The high and low limits simply establish boundaries for the point value. When the pointvalue either exceeds the high limit or falls below the low limit, the alarm goes off.

To enter these limits, type them into the fields.

Dead Band Value

The dead band value establishes a range, known as a dead band, within the high andlow limits. This range is used to define a subset of acceptable or normal values.

The dead band value that you supply is subtracted from the high limit and added to thelow limit. The resulting values form the high and low ends of the range of normal values.

To enter a dead band value, type it into the Deadband field.

The following figure shows a range of normal values formed by a dead band value of 1.The low and high limits are 45 and 74, respectively. The normal range is 46 to 73,because 45 + 1 = 46, and 74 - 1 = 73:

Note that the dead band value is optional. If you leave this value at 0, then all valuesbetween the high and low limits are considered normal. When the associated pointattribute exceeds or falls below the normal range, its Event State attribute changes toHigh Limit or Low Limit, respectively.




Algorithm Parameters for a Change of BitstringEvent

When you select Change of Bitstring from the Event Type on the General tab, theAlgorithms tab appears, as shown below.

A change of bitstring occurs when:

• The value of the referenced property becomes equal to one of the values containedin the Bitstring Values list, after applying the Bitmask.

• That value remains equal for the duration of seconds displayed in the Time Delay field.

The change of bitstring generates a ToOffnormal transition, and an event notificationis sent.

A change of bitstring clears (transitions ToNormal) when:

• The value of the referenced event property is no longer equal to one of the valuescontained in the Bitstring Values list, after applying the Bitmask.

• That value remains not equal for the duration of seconds in the Time Delay field.

Time Delay Time Delay appears on the Algorithms tab for each of the choices of Event Type on the General tab.






TAC 318

Bitmask This field represents a bitmask that is used to indicate which bits in thereferenced property are to be monitored by the algorithm.

A value of 1 in a bit position indicates that the bit in this position in thereferenced property is to be monitored by the algorithm.

A value of 0 in a bit position indicates that the bit in this position in thereferenced property is not significant for the purpose of detecting thischange of bitstring.

Bitstring

Values

This is list of bitstrings that apply to this event algorithm. This list of

bitstrings defines the set of states for which the referenced property isOffNormal. Only the bits indicated by the Bitmask are significant.

If the value of the referenced property changes to one of the values inthis bitstring list, then the referenced property of this EventEnrollmentobject makes a ToOffnormal transition, and appropriate notificationsare sent.

Algorithm Parameters for a Change of State Event

This algorithm detects changes of state in a specific event object. When you selectChange of State from the Event Type on the General tab, the Algorithms tab appears,as shown below:




A change of state occurs when:

• The value of the referenced property becomes equal to one of the values containedin list of values in the Alarm On field.

• That value remains equal for the duration of seconds displayed in the Time Delay field.

This type of event may only be applied to a property that has discrete or enumeratedvalues, including Boolean.

The change of state generates a ToOffnormal transition, and an event notification

is sent.

A change of state clears (transitions ToNormal) when:

• The value of the referenced property is no longer equal to one of the values in the list

• That value remains not equal for the duration of seconds in the Time Delay field.



For example, you may decide that the point value can exceed or fallbelow its alarm boundaries for 30 seconds before the alarm goes off. If at the end of the 30 seconds, the object is in alarm, the alarm goes off regardless of its state during the 30-second delay.


Alarm On This is a list of values that apply to the referenced property. The typesof values here may only be discrete or enumerated values, includingBoolean.



TAC 320

Algorithm Parameters for a Change of Value Event

When you select Change of Value from the Event Type scroll box on the General tabpage the Algorithms tab page will appear as shown below.

A change of value always generates a ToNormal transition and occurs when:

• The absolute value of the referenced property changes by an amount equal to or greater than the value displayed in the Reference Property Increment field.

• That amount remains equal to or greater than this value for the duration of secondsdisplayed in the Time Delay field.

If the referenced property is a bitstring data type, then the change of value occurs when:

• Any of the bits defined in the Bitmask field changes state.

• The bits remain changed for the duration of seconds in the Time Delay field.





Bitstring Check this checkbox if the referenced property is a bitstring. When youcheck this checkbox, the Bitmask field becomes selectable, and theReference Property Increment field becomes non-selectable.

Reference This is the increment by which the referenced property must change in




PropertyIncrement

order for the event to occur.

Bitmask This field represents a bitmask that is used to indicate which bits in thereferenced property are to be monitored by the algorithm.

A value of 1 in a bit position indicates that the bit in this position in thereferenced property is to be monitored by the algorithm.

A value of 0 in a bit position indicates that the bit in this position in thereferenced property is not significant for the purpose of detecting this

change of bitstring.

Algorithm Parameters for a Command Failure Event

When you select Command Failure from the Event Type on the General tab, theAlgorithms tab appears, as shown below.

A command failure occurs when the value of the referenced property differs from thevalue of the attribute specified in the Feedback Reference section, for the duration of seconds displayed in the Time Delay field.

This algorithm may be used, for example, to verify that a process change has occurredafter writing to a property.

This type of event shall only be applied to a property that has a discrete value.

The command failure generates a ToOffnormal transition, and an event notificationis sent.



TAC 322

A command failure clears (transitions ToNormal) when the value of the referencedproperty becomes equal to the value of the attribute specified in the FeedbackReference section, for the duration of seconds in the Time Delay field.



For example, you may decide that the point value can exceed or fall

below its alarm boundaries for 30 seconds before the alarm goes off.


FeedbackReference

This is used to select an attribute of an object with which the attribute of this EventEnrollment will be associated.

Object Displays the name of the object, whose value is being compared to thevalue of the attribute that is selected in the Attribute field.

Attribute From the dropdown menu, select a Feedback Reference attribute,whose value is to be compared with the value of the referencedproperty of the attached object.

Algorithm Parameters for a Floating Limit Event

The Floating Limit Algorithm tests to see if the alarmed attribute deviates from a range of values. A setpoint reference, high and low differential limits, and a dead band determinethis range of values. This is known as a floating limit because the range of values isdetermined by the current value of the setpoint.

How Do Floating Limit Algorithms Work?

A Floating Limit algorithm causes the associated point to report changes in the alarmedattributes value using the examples discussed below.

Example of High Diff Limit Floating Limit

Equation

Alarm states are reported when:

attribute value > set point reference value + High Diff Limit for Time Delay seconds




Assumptions

• Selected Alarmed Attribute = Value

• Point associated with this EventEnrollment object = AnalogInput named RoomTemp1

• Current set point = 70

• High Diff Limit = 4

• Low Diff Limit = 25

Discussion

For example, suppose the value for RoomTemp1 changes from 72 to 75. This changewould result in an alarm state, because the following floating limit equation results inTRUE:

attribute value > set point reference value + High Diff Limit

OR

75 > 70 + 4

DiagramThis diagram shows how a Floating Limit algorithm detects an alarm state.

Example of Low Diff Limit Floating Limit

Equation Alarm states are reported when:

attribute value < set point reference value - Low Diff Limit for Time Delay seconds



TAC 324

Assumptions






Discussion

Now suppose the value for RoomTemp1 changes to 44. This change would also result inan alarm state because the following floating limit equation also results in TRUE:

attribute value < set point reference value - Low Diff Limit

OR

44 < 70 - 25

DiagramSame as above.

Example of Floating Limit Using the Deadband

Equation Alarm states are reported when:

attribute value > (set point reference value - Low Diff Limit) + dead band value for TimeDelay seconds

Assumptions






• Deadband = 1

Discussion

For example, suppose the value for RoomTemp1 changes from 75 to 72. This changewould result in a normal state, because the following floating limit equations result inTRUE:

attribute value < (set point reference value + High Diff Limit) - dead band value

OR

72 < 70 + 4 – 1

and

attribute value > set point reference value - Low Diff Limit + dead band value

OR




72 > 70 - 20 + 1

Diagram

When you select Floating Limit from the Event Type on the General tab, theAlgorithms tab appears, as shown below.







TAC 326

High Diff Limit

This field establishes the value amount that is allowed above the highlimit of the acceptable range of values (deadband). This "diff" amount isadded to the value of the Setpoint Reference attribute.

The reference property value is then compared with the attribute valueto determine if a floating high-limit event has occurred.

Low Diff Limit This field establishes the value amount that is allowed below the lowlimit of the acceptable range of values (deadband).

This "diff" amount is subtracted from the value of the Setpoint

Reference attribute. The reference property value is then comparedwith the attribute value to determine if a floating low-limit event hasoccurred.

Deadband The value in the Deadband field establishes a range, known asdeadband , within the high and low limits. This range defines a subset of acceptable, normal values.

The deadband value that you supply is subtracted from the high limitand added to the low limit. The resulting values form the high and lowends of the range of normal values. Enter a value in the Deadband field.

Object Search for and select a Setpoint Reference object, whose attributevalue you want to compare with the value of the referenced property.

Attribute Select an attribute of the selected Setpoint Reference object. Thisvalue is compared with the value of the referenced property. Value isthe default.

To use a Floating Limit algorithm:

1. Type in the High Diff and Low Diff differential limits.

2. Type in a Deadband value (optional).

3. Next, select a Setpoint Reference.

4. Click the button in the Object field. The Browse dialog appears.

5. In the Browse dialog, click the object you want to highlight it.

6. Click the Select button in the Browse dialog, and the correct path and object name

will be inserted into the Object field.7. Finally, select an attribute from the Attribute dropdown menu.

Buffer Ready

The Buffer Ready type is used only when you have attached a TrendLog object in theObject field of the General tab. In this case, this EventEnrollment algorithmaccommodates workstation recipients who need to be notified when new records areadded to a TrendLog object, so that the records can get downloaded to eachworkstation's database. (Please also see a related procedure, in Chapter 17, Configuring TrendLogs, for configuring algorithmic notifications for a TrendLog.)




The Current State Tab

The Current State tab is a read-only page that indicates the present (current) state of theEventEnrollment object.

Event State Indicates the current state of the event.

Last TimeStamp

Indicates the times of the last event notifications for the three listedconditions.

To OffNormal Indicates the last time that the event transitioned to the OffNormal state.

To Normal Indicates the last time that the event transitioned to the Normal state.

To Fault Indicates the last time that the event transitioned to the Fault state.

The Security Level Tab

See Chapter 4 for details regarding the attachment of security levels to a BACnet device.

The Next Step

Once you are finished configuring alarms for your BACnet devices, you will need toconsider the assignment of BACnet command priorities to certain object properties andthe creation of objects with BACnet object editors.

Using Templates for EventEnrollment and EventNotification Objects

It is recommended that you use CyberStation templates to create EventEnrollment andEventNotification objects that share similar information. At large sites, configuration of EventEnrollments and EventNotifications can be a very big job. Templates save a lot of time and effort. Please see Chapter 12, as well as help topics for templates in theCyberStation online help system.



TAC 328

Command Prioritization

In a building control system, an object may be manipulated by any number of differentapplications. Each such application program has a well-defined function it needs toperform. When the actions of two or more application programs conflict with regard to thevalue of an object’s property, a decision process must be implemented to determinewhich application has priority.

Commandable Properties

In a BACnet system, a prioritization scheme is used to assign varying levels of priorities

to object properties (referred to as “commandable properties”). At present, the objectsthat have commandable properties are:

Object Commandable Property

Analog Output Present_Value

Binary Output Present_Value

Multi-state Output Present_Value

Analog Value Present_Value

Binary Value Present_Value

Multi-State Value Present_Value

Each of these objects is responsible for acting upon its commandable property inaccordance with a command priority list.

Application Priority Assignments

Command priorities are assigned priority levels from 1 (highest) to 16 (lowest). Thestandard command priority array list from the ANSI/ASHRAE Standard 135-2004 isshown below.

Priority Level Application Priority Level Application

1 Manual-Life Safety 9 Available

2 Automatic-Life Safety 10 Available

3 Available 11 Available


5 Critical EquipmentControl

13 Available

6 Minimum On/Off 14 Available


8 Manual Operator 16 Available




For interoperability between BACnet systems, it is necessary that all BACnet devicesimplement the same priority scheme. In CyberStation, this requirement is implemented byincorporating the 16 priorities in the BACnet Preferences dialog.

The standard command priority list is reflected in a dropdown menu on the Value columnof the CyberStation BACnet Preferences dialog:

The seven applications that require BACnet command priority level assignments are:

• CyberStation programs • Command Line

• Editor • ListView

• web.Client • Other

• Pinpoint

To assign BACnet command priorities to these applications:

1. Right click the Continuum icon in the window task bar (tool tray).

2. Select BACnet Preferences from the popup menu.

3. Scroll down to setting 4 – BACnet Command Priority for CyberStation Programs.

4. Click the entry in the Value column to open the priority list scroll box.

5. Scroll to the desired priority and click it.

6. For settings 5 through 10, repeat steps 4 and 5 for the remaining BACnetcommand priorities.

CAUTION

The assignment of BACnet command priorities described in the followingsteps should only be accomplished by the system administrator.



TAC 330

BACnet Defined Objects

In Infinity, there are two types of points:

Hardware-Defined

InfinityInput Connections to an Infinity input device

InfinityOutput Connections to an Infinity output device

Software-Defined

InfinityDateTime Storage location where the current system time and date are available

InfinityNumeric Storage location where numeric (number) information is stored

InfinityString Storage location where ASCII text characters are stored

Note: Refer to Chapter 13 for a discussion of each of the above points.

BACnet devices support ASHRAE Standard 135-2004, which means that they supportthese corresponding object classes:

BACnet Defined

AnalogInput BinaryInput MultistateInput

AnalogOutput BinaryOutput MultistateOutput

AnalogValue BinaryValue MultistateValue

Mapping Infinity Points to BACnet Objects

In order to provide compatibility with Andover Continuum b4920, bCX1 (40x0 series), andb3 controllers, mapping between Infinity points and BACnet objects is necessary, asshown in the following table:

Infinity Point Values Maps to BACnet

Voltage, Current, Temperature AnalogInput

Digital BinaryInput

InfinityInput

Counter, supervised MultistateInput

Voltage, Current AnalogOutput

Digital BinaryOutput

InfinityOutput

Tristate MultistateOutput

AnalogValue

BinaryValue

InfinityNumeric

MultistateValue

InfinityString Plain text messages No equivalent

InfinityDateTime Date and time data No equivalent




To become accustomed to this concept, start by viewing objects on the ContinuumExplorer. Some examples are given on the following pages.

There are two views shown of each example. The first shows the Infinity view, and thesecond shows the BACnet view.

InfinityInput to AnalogInput

The point-mapping table on the previous page shows that an InfinityInput point maps to aBACnet AnalogInput object. An example of this relationship is show below:

InfinityInput

AnalogInput

One of the Infinity points, PhotoCell , did not map because it did not fit the BACnet profilefor an AnalogInput.

InfinityOutput to BinaryOutput

The point-mapping table shows that an InfinityOutput point maps to a BACnetBinaryOutput object. An example of this relationship is show below:



TAC 332

InfinityOutput

BinaryOutput

In the above example, only the FanStart InfinityOutput point mapped to a BinaryOutputobject. Neither the ValueControl point (an analog type) nor the TriStateValue point (amultistate type) fit the BACnet profile for a BinaryOutput.

InfinityNumeric to AnalogValue

The point-mapping table shows that an InfinityNumeric point maps to a BACnet AnalogValue object. An example of this relationship is shown below:




InfinityNumeric

AnalogValue

In this example, all four InfinityNumeric points fit the BACnet profile AnalogValue objects.

Infinity and BACnet Object Editors

In Infinity, there are Infinity point editors: InfinityInput, InfinityOutput, InfinityNumeric,

InfinityString and InfinityDateTime. (See Chapter 13.) In CyberStation, Andover Continuum introduces BACnet object editors — one for each of the BACnet objects listedin the mapping table earlier in this chapter. There is no BACnet equivalent for InfinityString and InfinityDateTime points.

BACnet object editors are described on the following pages.

Using BACnet Object Editors

In an Andover Continuum system containing Andover Continuum BACnet-compliantb4920, bCX1 (40x0 series), and b3 controllers, you typically configure controllers andtheir attached points using the Infinity view, with Infinity point editors. BACnet objecteditors are used primarily to view and modify objects created on third-party BACnetdevices that have been integrated into the system. They also allow all users to view



TAC 334

Andover Continuum BACnet objects, on b3, bCX1 (40x0 series), and b4920 devices, asthird-party devices would see them. However, if your system has no third-party devices,but does have b4920, bCX1 (40x0 series), and b3 controllers, there would normally be noreason to view them as BACnet objects in the BACnet Devices portion of the ContinuumExplorer navigation pane.

Although the combined Infinity/BACnet view is enabled by default, you would normallyconfigure, view, and work with Andover Continuum BACnet-compliant controllers andtheir objects using the Infinity Controller Only view option via the Explorer’s Viewdropdown menu, described earlier in this chapter. That is, you would view and work with

InfinityController and InfinityInfinetCtlr objects, instead of b4920, bCX1 (40x0 series), andb3 BACnet Device objects. You would view and work with InfinityInputs, InfinityOutputs,and InfinityNumeric points, instead of AnalogInput/Output/Value objects, BinaryInputs/Outputs/Value objects, and MultistateInputs/Outputs/Value objects.

Note: Although you would view and work with them on the Andover Continuum side, youstill must find and save them into the BACnet side for proper configuration andoperation. See the section, Post-Installation System Integration, earlier in thischapter.

If you are viewing third-party BACnet devices, you may also find out which objects andservices are supported for the device, using the Details tab of the Device editor,described earlier in this chapter.

New BACnet objects on a b4920, bCX1 (40x0 series), or b3 controller are created from

Infinity point editors — that is, entirely from the Infinity view. Before creating BACnetobjects as InfinityInputs, InfinityOutputs, and InfinityNumerics, you will have:

• Installed and commissioned a new Andover Continuum b4920 or bCX1 (40x0 series)controller in the system. (See Appendix A for information on commissioning a newcontroller.)

• Created and fully configured one or more InfinityController objects. (See Creating anInfinityController Object in Chapter 7.)

• Created one or more InfinityInfinetContrller (b3) objects.

• Within the Explorer, selected Find New BACnet Devices to locate the newcontrollers. (This is described earlier in this chapter.)

• Within the Explorer, performed a Send To Database operation. (This is described

earlier in this chapter.)To configure Infinity points attached to the new b4920, bCX1 (40x0 series), and b3controllers, you do so in the Infinity view on the Explorer. For example, you create anInfinityInput point from the InfinityInput editor, then select an electrical type that makes itanalog, binary, or multistate. (Refer to Chapter 13.)

Note: BACnet objects in third-party BACnet devices become visible and incorporatedwithin the system when the Find New BACnet Devices and Send To Database operations are performed. They do not require the use of an InfinityInput,InfinityOutput or InfinityNumeric editor, and are always listed as BACnet objects,with their BACnet devices, in the BACnet Devices portion of the Explorer viewingpane.




For example, assume that you have created an InfinityInput point called Fan1Status, andthat it was assigned to a sensor that would supply electrical-current input signals to thecontroller. It would therefore have been assigned Voltage in the Elec Type field of theInfinityInput editor’s Settings tab. (See InfinityInput Settings Tab in Chapter 13.) In theBACnet view, if you were to decide to use it, this InfinityInput point would map, as an AnalogInput, to the corresponding BACnet Device object that corresponds to the b4920,bCX1 (40x0 series), or b3 controller.

If you decide to use the BACnet view, once you have configured and saved the object,you may view it from its BACnet device, as follows:

1. Click the + next to the BACnet devices icon in the Explorer’s navigation pane.

2. Click the + sign next to the Andover Continuum BACnet controller device icon toexpand it.

3. An AnalogInput BACnet folder should appear beneath the device icon. Click thefolder to open it:

4. The Fan1Status InfinityInput object that you created should appear in the Explorer’s

viewing pane, as an AnalogInput:

5. Double click this icon to open the BACnet AnalogInput editor.

From this BACnet editor, you may modify this object.

BACnet AnalogInput Editor

You use the BACnet AnalogInput editor to refine the object (created as an InfinityInput ona b4920, bCX1 (40x0 series), or b3 controller or as an AnalogInput on a third-partyBACnet device). It represents analog values such as voltage, current, temperature, andso on. This editor has five tabs that let you type in or select information, or in some cases

supply you with data.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for allBACnet objects because they are enabled only for CyberStation/Infinity objects only. Also, the Basic Alarms tab is supported for BACnet objects attached to third-partyBACnet devices, not for objects attached to Andover Continuum b4920, bCX1 (40x0series), and b3 controller devices.

AnalogInput General Tab

The General tab has several properties for which you provide values, and a fewproperties that will be set by the control system.



TAC 336

Value View or enter a value into this field.

Units Select a unit of measure from the dropdown menu.

UpdateInterval

Enter an integer to specify the maximum time (in hundredths of asecond) between updates to the value, when the input is notoverridden and not out-of-service.

Description Enter up to 32 characters (including spaces) in this field.

Device Type Indicates the type of device that is connected to this AnalogInput.

Out of Service Check this checkbox to put this object out of service so that it losescommunication with its attached device. Putting the object out of service is a good way to test the object and the functions that rely on it.You can simulate various situations by manually changing the value or

reliability attributes. This allows you to see how associated functionsreact to these changes.

Format Enter a numeric display format. For example: ###.###

Status Provides information on the object's condition. The condition can beone of the following:

InAlarm ⎯ indicates that the Event State has a value other thannormal.

Overridden ⎯ indicates that a local device has manually overriddenthe point.




OutOfService ⎯ indicates that the object is disabled.

Fault ⎯ indicates that the Reliability property has a value other thanNoFaultDetected.

Reliability Provides an indication of whether or not the controller has detected amalfunction that might compromise the integrity of the object's presentvalue. The attribute can be one of the following:

NoFaultDetected ⎯ indicates that the present value is reliable andthat no fault is detected.

OverRange ― indicates that the sensor is reading a value that ishigher than the normal operating range.

OpenLoop ⎯ indicates that the connection between the object andthe device is providing a value resulting from an open circuit.

UnreliableOther ⎯ Indicates that the controller detects an unreliablepresent value and that none of the above conditions describe thenature of the problem.

NoSensor ⎯ indicates that no sensor is connected to the AnalogOutput point.

UnderRange ⎯ indicates that the sensor is reading a value that is

lower than the normal operating range.ShortedLoop ⎯ indicates that the connection between the object andthe device is providing a value resulting from a closed circuit.

AnalogInput Basic Alarms Tab

The Basic Alarms tab is where intrinsic alarms are defined specifically for this object.

Note: This is enabled for BACnet objects attached to third-party BACnet devices. It is notsupported on Andover Continuum b4920, bCX1 (40x0 series), and b3 controllers. An example of a Basic Alarms tab, populated with information for a third-partydevice, is shown below.

The information here determines when the alarm will go off, and what happens when itdoes. Information that determines what happens when the alarm goes off is built into the

EventNotification object that you associate with this alarm. (Refer to EventNotification inChapter 10.) The EventNotification object defines how and to whom the alarm is sent.



TAC 338

Event State Displays the value of the To State attribute which is set by the controlsystem. If you have set up this object to report alarms, this attribute

displays Normal when the object is not in an alarm state andOffNormal when it is. If you have not set up the object to reportalarms, this attribute always displays NORMAL.

AcknowledgeReceived For

Displays the value of the Acknowledge Received For property.Displays ALARM, FAULT, or NORMAL if acknowledgements havebeen received for reported alarms, faults, or return-to-normal events,respectively. These values display only if both of the followingconditions are true:

You have selected the report options for these events.

The associated EventNotification object requires acknowledgement for these events.

COVIncrement

Enter the number of units — for example, degrees — that mustincrease or decrease before a COV is triggered, and COV notificationis sent to a client . An increment of 0 appears by default.

CAUTION: Set this increment high enough so that the subscriber isnot inundated with too many COV notifications. Even the tiniest valuechanges can trigger too many COVs. Do not accept the default, 0.Leaving it at 0 will produce negative results.

High Limit Enter a high limit for the object. Check the Enable checkbox to theright to enable the high limit. The high and low limits establishboundaries for the object value. When the object value exceeds thehigh limit, or falls below the low limit, the alarm goes off.




Low Limit Enter a low limit for the object. Check the Enable checkbox to the rightto enable the low limit.

Time Delay Enter a time delay in seconds. The time delay postpones the alarm for the amount of time you specify. For example, you may decide that theobject value can exceed or fall below its boundaries for 30 secondsbefore the alarm goes off. Using time delays cuts down on the number of active alarms and reduces both system traffic and operator responsibility.

Dead Band Enter a dead band value. The dead band value establishes a range,known as a dead band, within the high and low limits. This range isused to define a subset of acceptable, or normal, values. The deadband value that you supply is subtracted from the high limit, and addedto the low limit. The resulting values form the high and low ends of therange of normal values.

Report In the Report section, you may select up to three report options:Alarm, Return to Normal, and Fault. When selected, these optionstrigger the basic alarm in the following situations:

The Alarm option triggers the basic alarm when the object's EventState changes to OffNormal.

The Return To Normal option triggers the basic alarm when the

object's Event State changes to Normal.The Fault option triggers the basic alarm when a local device detects afault.

NotificationType

From the dropdown menu, select a notification type. The notificationtype specifies whether the notification message becomes an alarmmessage, an event message, or a message of eventacknowledgement.

AlmNotification – Defines the event as type alarm, appearing in the Active Alarm View when the event occurs.

EvtNotification – Defines the event as type event , appearing in Active Alarm View when the event occurs.

Acks – Defines the event as type ack-notification, appearing in the Active Alarm View when the event occurs.

EventNotification

Select an EventNotification object by clicking the browse button. TheBrowse dialog appears. Locate the Event Notification object that youwant. Select it and click the Select button. This will insert the correctpath and EventNotification name into the Notification class field.



TAC 340

AnalogInput Advanced Alarms Tab

The Advanced Alarms tab allows you to attach up to eight alarms to an object. (See Attaching Alarms to a Point in Chapter 10.)

Note: This tab is only enabled for CyberStation/Infinity objects. It is disabled for allBACnet objects.

You may also use this page to attach a graphic panel and a report or other program tothe object, via the Graphic and Program fields, respectively. When an AnalogInputobject generates an alarm, either via an associated EventEnrollment, Basic Alarm or

Advanced Alarm, the associated graphic can be programmed to automatically launch.(See Graphic below.) The graphic can also be manually launched via the Alarm ViewGraphic button. (See View Menu in Chapter 10.)

Similarly, a program can be configured to run automatically when this object goes intoalarm and can also be run manually via the corresponding Alarm View Program Outputbutton. (See Program below and View Menu in Chapter 10.)

Graphic Browse for the graphic panel program file that you want to displaywhen the object goes into an alarm state.

Program Browse for the program that you want to run when the object goes intoan alarm state.




Alarm Points Alarm points allow any expression alarm that you attach on this tab toreference up to four "alarm points," named Point 1, Point 2, Point 3,and Point 4. Using alarm points saves you the trouble of having tochange the expression (via the Algorithms tab of the AlarmEnrollmenteditor for that alarm object) every time you attach an expression alarmto a different point. For complete information, please see the section,Using the Alarms/Advanced Alarms Tab of an Object Editor , inChapter 10.

Video

Video Points

Video points allow you to assign cameras to doors and points and

configure parameters that control video images, via VideoLayoutobjects, during alarm conditions. When the alarm goes off, a videolayout is launched (if a VideoLayout object has been configured towork with video points) and displays the "video point" camera imagesin the its video image frames. In the Video Points dialog, you mayalso configure a camera to record a video clip, for specified number of seconds, when the alarm goes off.

For complete information on this field, and how to use Video Points,please see the section, Using the Alarms/Advanced Alarms Tab of anObject Editor , in Chapter 10. See also Chapter 25, Configuring and Viewing Video.

AnalogInput Triggers Tab

The Triggers tab is not applicable to BACnet devices. Triggers are not supported for objects associated with Andover Continuum b3, b4920, and bCX1 (40x0 series)controllers or third party BACnet devices. It is applicable to CyberStation/Infinity objectsonly. (Refer to InfinityInput Triggers Tab in Chapter 13.)

AnalogInput Security Level Tab

The access permissions configured in a security level allow you to customize (deny)access to individual CyberStation objects. Security levels are actual CyberStation objects(Security Level objects) configured via the Security Level editor. (See Chapter 4.)

A security level can deny access to a CyberStation object editor on a page-by-page basisusing object-level security. Object-level security is a way to deny user groups the abilityto create, delete, or change individual CyberStation objects. Every object editor inCyberStation has a Security Level tab, shown on the next page, that displays a list of allexisting security level objects. Selecting a security level object here attaches that securitylevel to the object being edited.



TAC 342

To attach a security level to this point, locate the security level in the Name column andclick the radio button next to it.

To detach a security level from this point, locate the security level in the Name columnand double-click the radio button to remove the black dot it contains. Or you can rightclick the security level in the Name column to bring up a popup menu. Click Clear Selection in the popup menu.

BACnet AnalogOutput Editor

An AnalogOutput is a BACnet object that is created with the InfinityOutput editor. (SeeChapter 13) They can also be learned in from a third-party device, or created via the AnalogOutput editor. AnalogOutputs are associated with BACnet devices.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for allBACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-party BACnet devices, not for objects attached to Andover Continuum b4920,bCX1 (40x0 series), and b3 controller devices.

When you create an InfinityOutput object for an Infinity b4920 or bCX1 (40x0 series)controller, or an Infinity Infinet b3 series controller, and select an analog electrical type viathe Settings tab of the InfinityOutput editor, a BACnet AnalogOutput is created. (Refer toChapter 13.)

AnalogOutput General Tab

The General tab has several attributes that you can provide values for, and a fewattributes that are set by the control system. Many fields on this tab are also view-only.




Present Value This field displays this object's present value that the current priority(the priority level that appears in the Present Priority field) is currentlycommanding to this object. This field is non-editable.

PresentPriority

This field displays the current priority level that is currentlycommanding the present value of this object. This field is non-editable.

CommandValue

This field is used for setting the value of the analog output at thedefault command priority displayed in the Command Priority field. Bydefault, the command priority is set to the command value establishedin the BACnet Preferences dialog. The default is Manual Operator . If you have access permission, you may change the value in this field for this command priority level.

Command

Priority

This field displays the default command priority value that is used

when setting and relinquishing the value. By default, this field is set tothe command value established in the BACnet Preferences dialog.This field is non-editable.

Set Click this button to assign the new value (the value that you justchanged in the Command Value field) to this object.



TAC 344

Relinquish Click this button to relinquish the non-NULL value of the priority levelthat appears in the Command Priority field.

Note: Relinquishing the value means changing it to NULL, so that thenext higher-numbered priority level that holds a non-NULL valuebegins to command its value to the object.

From the Command Priority tab, your administrator may relinquishvalues at all command priorities.

Units Select a unit of measure from the dropdown menu.

Description Enter up to 32 characters (including spaces) in this field to describe theobject.

Device Type Enter the type of device that is connected to this analog output object.

UpdateInterval

Enter an integer to specify the maximum time (in hundredths of asecond) between updates to the value, when the input is notoverridden and not out-of-service.

Out of Service Check this checkbox to put the object out of service, so that it losescommunication with its attached device. Putting the object out of service is a good way to test the object and the functions that rely on it.You can simulate various situations by manually changing the value or reliability attributes. This allows you to see how associated functions

react to these changes.Format Enter a numeric display format. For example: ###.###

Status Provides information on the object's condition. The condition can beone of the following:

InAlarm ⎯ indicates that the Event State property has a value other than NORMAL.

Overridden ⎯ indicates that a local device has manually overriddenthe object.

Fault ⎯ indicates that the Reliability property has a value other thanNoFaultDetected

Out of Service ⎯ indicates that the object is disabled.




Reliability Provides an indication of whether or not the controller has detected amalfunction that might compromise the integrity of the object's presentvalue. The attribute can read one of the following:

NoFaultDetected ⎯ indicates that the present value is reliable andthat no fault is detected.

OpenLoop ⎯ indicates that the connection between the object andthe device is providing a value resulting from an open circuit.

Unreliable Other ⎯ indicates that the controller detects an unreliable

present value and that none of the above conditions describe thenature of the problem.

NoOutput ⎯ indicates that no sensor is connected to the AnalogOutput object.

ShortedLoop ⎯ indicates that the connection between the object andthe device is providing a value resulting from a closed circuit

AnalogOutput Command Priority Tab

In this tab page you may view members of the BACnet priority array (a list of prioritylevels) and their values for this BACnet object. You may also select a priority level for thisBACnet object and change the level's value (thereby overriding its current commandedvalue) as well as relinquish a priority level — set it to NULL — so that:

• It no longer commands a value to this BACnet object at the select priority level.

• The next highest priority level may command a non-NULL value.

When first configuring your system, also remember to set the value in the RelinquishDefault field, located at the bottom of this tab. This default value is commanded to theobject when all priority level values are relinquished (in other words, when they becomeall NULL). This protects against users who inappropriately click the Relinquish button onthe General tab and/or on this tab.

See the subsection, Application Priority Assignments, earlier in this chapter, for commandpriority levels.

CAUTIONOnly system administrators should be granted security accesspermission to use this tab page.



TAC 346

Present Value This field displays the object’s present value that the current priority

(the priority level that appears in the Present Priority field) is currentlycommanding to this object. This field is non-editable.

PresentPriority

This field displays the current priority level that is currentlycommanding the present value to this object. This field is non-editable.

CommandValue

This field is used for setting the value of the analog output at thedefault command priority displayed in the Command Priority field. Bydefault, this field is set to the command value established in theBACnet Preferences dialog. The default is Manual Operator . If youhave access permission, you may change the value in this field for thiscommand priority level.

CommandPriority

This field displays the default command priority level value. By default,this field is set to the command value established in the BACnet

Preferences dialog. From this field's dropdown menu, you maychange this level's value, which appears in the Command Value field. Also, from the Command Priority dropdown menu, you may selectany other priority level, and also change its value.

Set Click this button to assign the new value (the value that you justchanged) to this object at the corresponding command priority.




Relinquish Click this button to relinquish the non-NULL value of the priority levelthat appears in the Command Priority field.

Note: Relinquishing the value means changing it to NULL, so that thenext higher-numbered priority level that holds a non-NULL valuebegins to command its value to the object.

To relinquish any level's value, first use the Command Priority dropdown menu to select the priority level whose value you want torelinquish, thenclick Relinquish.

Priority ArrayWindow

This window contains the BACnet priority array — a list of the namesof all 16 BACnet protocol command priority levels, along with the valuethat each level in the array is currently commanding.

RelinquishDefault

Enter a value to command to this object when all command prioritylevels have been relinquished (when all values become NULL). Thisensures the object has a value at all times. Set this field when you firstconfigure the system.

Basic Alarms, Advanced Alarms, Triggers, and Security Level Tabs

These tabs are covered under the AnalogInput editor.

BACnet AnalogValue Editor

An AnalogValue is a BACnet object that is created via the InfinityNumeric editor. (Refer toChapter 13.) They can also be learned in from a third-party device, or created via the AnalogValue editor. AnalogValues are associated with BACnet devices.


When you create an InfinityNumeric point for an Infinity b4920 or bCX1 (40x0 series)controller, or an Infinity b3 series controller, and select AnalogValue in the BACnetObject Type field of the InfinityNumeric editor’s General tab, a BACnet AnalogValue is

created. (Refer to Chapter 13.) AnalogValue points are temporary storage locations in thecontroller’s memory that store floating-point numbers.

AnalogValue General Tab

With the exception of Units (discussed below) the remainder of items on this tab iscovered under AnalogOutput General Tab.



TAC 348

Units Select a unit from the dropdown menu. When displayed next to the value,

as in 72 Degrees F, or 17 Employees, units help users understand whatthe point is doing.

Format Enter a numeric display format. The default is: ###.###

Basic Alarms, Advanced Alarms, Triggers andSecurity Level Tabs


BACnet BinaryInput Editor

A BinaryInput is a BACnet object that is created via the InfinityInput editor, or on third-party devices. They can be learned from a third-party device, or created via the

BinaryInput editor. BinaryInputs are associated with BACnet devices.Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for all

BACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-party BACnet devices, not for objects attached to Andover Continuum b4920,bCX1 (40x0 series), and b3 controller devices.

When you create an Infinity Input point for an Infinity b4920 or bCX1 (40x0 series)controller, or an Infinity b3 series controller, and select a digital/binary electrical type onthe Settings tab of the InfinityInput editor, a BACnet BinaryInput point is created.Typically, these inputs are used to detect whether a particular piece of equipment, like afan or a pump is running or idle. The ON state usually indicates the equipment is running,whereas the OFF state usually indicates the equipment is idle.




BinaryInput General Tab

Value Select ON or OFF from the dropdown menu.

Description Enter up to 32 characters (including spaces) in this field.

Device Type Enter the type of device that is connected to this input.

Out of Service See Out of Service covered under AnalogOutput General Tab.

Status See Status covered under AnalogOutput General Tab.

Reliability See Reliability covered under AnalogOutput General Tab.



TAC 350

BinaryInput Settings Tab

Inactive Text Enter text for an inactive state. This text is displayed as the value whenthe binary input is in the inactive state.

Active Text Enter text for an active state. This text is displayed as the value whenthe binary input is in the active state.

Polarity Select either Normal or Reverse from the Polarity dropdown menu.

BinaryInput Counters Tab

In the Counters tab, you find the amount of time the point has been in an active state,and the date and time the state changed last. You can also find out when this informationwas last reset. This tab is divided into two sections:

• Active Time

• Change of State




Active Time Elapsed Time― Shows the number of seconds since the point's status

changed from Inactive to Active.

Last Reset― Shows the date and time the elapsed time was last reset.

Reset Elapsed Active Time on Next Save― For the controller reset theElapsed Active Time the next time data are saved, check this checkbox.

Change of State

Value Changed at― Shows the date and time the state last changed.

Change-of-State Count― Shows you how much time the state haschanged.

Last Reset― Shows the time when this count was last reset to zero.

Reset Change-of-State Count on Next Save―

For the controller resetthe Change of State Count the next time data are saved, check thischeckbox.



TAC 352

BinaryInput Basic Alarms Tab


Note: This is enabled for BACnet objects attached to third-party BACnet devices. It is notsupported on Andover Continuum b4920, bCX1 (40x0 series), and b3 controllers.

The information here determines when the alarm will go off, and what happens when itdoes. Information that determines what happens when the alarm goes off is built into theEventNotification object that you associate with this alarm. (Refer to EventNotification inChapter 10.) The EventNotification object defines how and to whom the alarm is

broadcast.

Keep in mind that basic alarms apply only to the object in which they were created. Another way to configure alarms in BACnet is to use the EventEnrollment class.

Event State See Event State under AnalogInput Basic Alarms Tab.

AcknowledgementReceived For

See Acknowledgement Received For under AnalogInput Basic Alarms Tab.

Alarm WhereValue Is

Select Off or On from the dropdown menu. An alarm is triggeredbased on this value.

Report See Report under AnalogInput Basic Alarms Tab.

Time Delay Enter a time delay in seconds. The time delay postpones the

alarm for the amount of time you specify. For example, you maydecide that the point value can exceed or fall below itsboundaries for 30 seconds before the alarm goes off. Using timedelays cuts down on the number of active alarms and reducesboth system traffic and operator responsibility.

Notification Type See Notification Type under AnalogInput Basic Alarms Tab.

Event Notification See Event Notification under AnalogInput Basic Alarms Tab.

BinaryInput Advanced Alarms, Triggers, andSecurity Level Tabs





BACnet BinaryOutput Editor

A BinaryOutput is a BACnet object that is created with the InfinityOutput editor, or onthird-party devices. They can be learned from a third-party device, or created via theBinaryOutput editor. BinaryOutputs are associated with BACnet devices.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for allBACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-party BACnet devices, not for objects attached to Andover Continuum b4920,

bCX1 (40x0 series), and b3 controller devices.

When you create an InfinityOutput for an Infinity b4920 or bCX1 (40x0 series) controller,or an Infinity b3 series controller, and select a digital/binary electrical type via theSettings tab of the InfinityOutput editor, a BACnet BinaryOutput is created. (Refer toChapter 13.)

Typically these outputs are used to switch a particular piece of equipment, like a fan or apump, ON or OFF (the equivalent BACnet values are active and inactive).

BinaryOutput General Tab

The General tab has several properties that you can provide values for, and a fewattributes that are set by the control system. The fields on this tab are view-only if theparticular device does not support them.



TAC 354

Refer to AnalogOutput General Tab for a description of all the items that appear on this tab.

BinaryOutput Settings Tab

The Settings tab has the following properties, described below.

Inactive Text Enter text for an inactive state. This text will help future operatorsdetermine the meaning of values for this point.

Active Text Enter text for an active state. This text will help future operatorsdetermine the meaning of values for this point.

Minimum OnTime

Enter the minimum time in seconds that the point will remain activeafter it has been changed to active.

Minimum Off

Time

Enter the minimum time in seconds that the point will remain inactive

after it has been changed to inactive.Polarity Select either Normal or Reverse from the Polarity dropdown menu.




BinaryOutput Counters and Basic Alarms Tab Pages

Refer to BinaryInput Counters Tab. Refer also to BinaryInput Basic Alarms Tab, exceptfor the Feedback Value property (described below).

FeedbackValue

Select the inactive entry or the active entry from the dropdown menu.The object must equal this value for an alarm to occur. (Theseselections represent text set in fields on the Settings tab.)

BinaryOutput Command Priority Tab

The items on this tab are covered under the AnalogOutput editor.

BinaryOutput Advanced Alarms, Triggers, andSecurity Level Tabs

The items on these tab pages are covered under the AnalogInput editor.

BACnet BinaryValue Editor

A BinaryValue is a BACnet point object that is created via the InfinityNumeric editor, or onthird-party devices. They can be learned from a third-party device, or created via theBinaryValue editor. BinaryValues are associated with BACnet devices.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for all

BACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-party BACnet devices, not for objects attached to Andover Continuum b4920,bCX1 (40x0 series), and b3 controller devices.

When you create an InfinityNumeric for an Infinity b4920 or bCX1 (40x0 series) controller,or an Infinity b3 series controller, and select BinaryValue in the BACnet Object Type field of the InfinityNumeric editor's General tab, a BinaryValue is created if the Infinity or Infinet controller on which it resides was created as a BACnet device. (Refer to Chapter 13.) Typically, BinaryValues are used as control system parameters that have only one of two possible values that you define.



TAC 356

BinaryValue General Tab

This tab is covered under the BinaryOutput editor.

BinaryValue Settings, Counters, and Basic AlarmsTabs

These tabs are covered under the BinaryInput editor.

BinaryValue Command Priority Tab

This tab page is covered under the AnalogOutput editor.

BinaryValue Advanced Alarms, Triggers andSecurity Level Tabs


BACnet MultistateInput Editor

A MultistateInput is a BACnet object that is created via the InfinityInput editor, or on third-party devices. (Refer also to Chapter 13.) They can be learned from a third-party device,or created via the MultistateInput editor. MultistateInputs are associated with BACnetdevices.

When you create an InfinityInput for an Infinity controller, and select a multistate(Supervised) electrical type, via the Settings tab of the InfinityInput editor, a BACnetMultistateInput is created if the controller on which it resides was created as a Andover Continuum BACnet-compliant device — specifically:

• As a b4920 or bCX1 (40x0 series) controller

• As a b36xx, b38xx, or b39xx controller




In these cases, a MultistateInput is created with three states: On, Off , and Trouble. Seealso the subsection, MultistateInput States Tab.

Note: For third-party BACnet devices that become part of the Andover Continuumsystem, MultistateInput objects were already created as objects on those third-party BACnet controllers. Therefore, Continuum Explorer already lists these objectsas MultistateInputs within third-party devices.

Controllers have channels for sensors. A channel in this case is an area in the controller that can be physically connected to a sensor. A sensor is a device that measures andreports on specific environmental factors, such as temperature, humidity, water pressure,and air flow.

MultistateInput values represent one of a specific set of possible states that you define.Each state that you define has its own numeric value. The state text is what users see as

the object’s value.




TAC 358

MultistateInput General Tab

The items on this tab, shown below, are covered under the BinaryInput editor.




MultistateInput States Tab

This tab lists the number of states this object has, as well as the text values of each state.Depending on the type of BACnet device on which the input was configured, anddepending on how the MultistateInput itself was configured, the number and types of states may vary.

If it was configured as an InfinityInput object for a Andover Continuum b4920 or b3controller, with a Supervised multistate electrical type — ElecType on the Settings tab of the InfinityInput editor — then the MultistateInput has three states named Off, On, andTrouble, as shown below:

However, if the MultistateInput was configured on a third-party BACnet device, it mayhave a different number of states, configured with text names from that device. For

example, a third-party MultistateInput might have four states named Quiet, Active, Fault,and Disabled.

Note: You may change the state of this MultistateInput via the Value field’s dropdownmenu on the General tab.

Each state listed in the State Text field has a its own text and numeric value beginningwith 1:

1 <= value <= number of states



TAC 360

Number of States

This is an integer that defines the number of states for this object. Thenumber must be greater than zero.

State Text This is a BACnet array of character strings (text values) representingall possible states of the object. The number of text values matchesthe number of states defined in the Number of States field.

MultistateInput Basic Alarms Tab

With the exception of Alarm Values and Faults Values (described below) the remainder of the properties on this tab is covered under the AnalogInput editor.

Alarm Values This list specifies the states that the MultistateInput must equal beforea ToOffnormal event is generated. This is required if intrinsic reportingis supported by this object.

Fault Values As an option, this list specifies the states that the MultistateInput mustequal before a ToFault event is generated. If it becomes equal to anyof the states in the list, and no physical fault has been detected, thenReliability (General tab) has the value, MultistateFault. This isrequired if intrinsic reporting is supported by this object.

MultistateInput Advanced Alarms, Triggers, andSecurity Level Tabs

The properties on these tabs are covered under the AnalogInput editor.




BACnet MultistateOutput Editor

A MultistateOutput is a BACnet object that is created via the InfinityOutput editor, or onthird-party devices. (Refer also to Chapter 13.) They can be learned from a third-partydevice, or created via the MultistateOutput editor. MultistateOutputs are associated withBACnet devices.

When you create an InfinityOutput for an Infinity controller and select a multistate(Tristate) electrical type via the Settings tab of the InfinityOutput editor, a BACnetMultistateOutput is created if the controller on which it resides was created as an

Andover Continuum BACnet device — specifically:

• As a b4920 controller or bCX1 (40x0 series) controller


In these cases, a MultistateOutput is created with three states: On, Off , and -On. Seealso the subsection, MultistateOutput States Tab.

Note: For third-party BACnet devices that become part of the Andover Continuumsystem, MultistateOutput objects were already created as objects on those third-party BACnet controllers. Therefore, Continuum Explorer already lists these objectsas MultistateOutputs within third-party devices.

An output object changes or affects the environment by controlling a piece of equipment,such as a heater or fan.

MultistateOutput values represent one of a specific set of possible states that you define.Each state that you define has its own numeric value. The state text is what users see asthe object's value.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for allBACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-party BACnet devices, not for objects attached to Andover Continuum b4920 ,bCX1 (40x0 series), and b3 controller devices.



TAC 362

MultistateOutput General Tab

Refer to BinaryOutput General Tab for a description of all the properties that appear onthis tab.




MultistateOutput States Tab

This tab lists the number of states this object has, as well as the text values of each state.Depending on the type of BACnet device on which the input was configured, anddepending on how the MultistateOutput itself was configured, the number and types of states may vary.

If it was configured as an InfinityOutput object for an Andover Continuum b4920, bCX1(40x0 series), or b3 controller, with a Tristate multistate electrical type — ElecType on theSettings tab of the InfinityOutput editor — then the MultistateOutput has three states

named Off, On, and -On, as shown below:

However, if the MultistateOutput was configured on a third-party BACnet device, it mayhave a different number of states, configured with text names from that device.

Note: You may change the state of this MultistateOutput via the Present Value field onthe General tab.



TAC 364

Each state listed in the State Text field has a its own text and numeric value beginningwith 1:

1 <= value <= number of states

Number of States

This is an integer that defines the number of states for this object. Thenumber must be greater than zero.

State Text This is a BACnet array of character strings (text values) representingall possible states of the object. The number of text values matchesthe number of states defined in the Number of States field.

MultistateOutput Basic Alarms Tab

With the exception of Feedback Value (described below) the remainder of properties onthis tab is covered under BinaryInput Basic Alarms Tab.

FeedbackValue

This specifies the value that the MultistateOutput must equal for analarm to occur.

MultistateOutput Advance Alarms, Triggers, andSecurity Level Tabs

These tabs are covered under AnalogInput Basic Alarms Tab.

BACnet MultistateValue Editor

A MultistateValue is a BACnet object that is created, and assigned state values, via theInfinityNumeric editor and third-party BACnet devices. (Refer also to Chapter 13.) Theycan be learned from a third-party device, or created via the MultistateValue editor.MultistateValues are associated with BACnet devices. When you create anInfinityNumeric for an Infinity controller and select MultistateValue in the BACnet ObjectType field of the InfinityNumeric editor's General tab, a BACnet MultistateValue is createdif the controller on which it resides was created as an Andover Continuum BACnet device— specifically:

• As a b4920 or bCX1 (40x0 series) controller


Note: For third-party BACnet devices that become part of the Andover Continuumsystem, MultistateValue objects were already created as objects on those third-party BACnet controllers. Therefore, Continuum Explorer already lists these objectsas MultistateValues within third-party devices.

Typically, a MultistateValue is used as a control system parameter whose value can beany one of a set that you define. For example, you can create a MultistateValue objectnamed DayofWeek whose value can be Monday, Tuesday, Wednesday, Thursday,Friday, Saturday, or Sunday.

Note: The Triggers and Advanced Alarms tabs are unselectable (appear gray) for allBACnet objects because they are enabled only for CyberStation/Infinity objectsonly. Also, the Basic Alarms tab is supported for BACnet objects attached to third-




party BACnet devices, not for objects attached to Andover Continuum b4920,bCX1 (40x0 series), and b3 controller devices.

Creating and Assigning State Values for aMultistateValue

As mentioned on the previous page, on an Andover Continuum b4920, bCX1 (40x0series), or b3 controller, you create a MultistateValue object as an InfinityNumeric point.For example:

As shown above, on the General tab of the InfinityNumeric editor, select MultistateValue from the BACnet Object Type field’s dropdown menu. Enter a value, in the Value field,and select the corresponding units of measure from the dropdown menu in the Units field.

A MultistateValue, when it is created as an InfinityNumeric, can have a wide variety of different sets or “clusters” of values. In addition to assigning an integer or floating-pointnumeric value and units, you may also assign such things as days of the week, or months of the year, or other non-numeric (text) state values. In the Value field, when youenter a non-numeric text value, such as “Monday,” CyberStation searches its internalSystem Value Cluster (SVC) tables for the cluster of states to which “Monday” belongs —in this case, a cluster that lists seven states (index 1…7). In the MultistateValue editor,you may change the Present Value field of the General tab to select another cluster member. (See the subsection, MultistateValue General Tab.)

An InfinityNumeric that has been designated as a MultistateValue can also be assigned a“value cluster” that resembles a binary object. For example, it can have three states(index of 3) with state values of On, Off , and –On. Or, it can have two states with state



TAC 366

values of Active and Inactive. Entering “On” or “Inactive” in the Value field triggers anautomatic search to the CyberStation SVC tables, for the appropriate multistate cluster member. Those values are then reflected in the MultistateValue object editor.

CAUTION: You must assign a value for multistate objects (in this case, a cluster type) inthe InfinityNumeric editor. You may reassign a state (a member of a cluster) in aMultistate editor, but you cannot assign a cluster itself. If you do not assign a value in theInfinityNumeric editor, then by default, the MultistateValue is assigned a dummy value of “State-1” with an index of 256 — State-1 through State-256.

MultistateValue General Tab

Refer to BinaryOutput General Tab for a description of all the items that appear on thistab. (Note that this tab does not have the Device Type field that appears on theBinaryOutput and MultistateOutput General tabs.)

MultistateValue States Tab

If the MultistateValue was created as an InfinityNumeric for an Andover Continuumb4920, bCX1 (40x0 series), or b3 controller, the States tab reflects the multistate cluster value that you entered on the General tab of the InfinityNumeric editor. For example, if you entered “Wednesday,” the cluster representing days of the week is shown in theMultistateValue editor. The integer 7 appears in the Number of States field, and thevalues Sunday through Saturday appear in the State Text field. As mentioned earlier in




this section, in the InfinityNumeric editor, you can assign a wide variety of differentclusters of values.

MultistateValue Basic Alarms Tab

The items on this tab are covered under the MultistateInput editor.

MultistateValue Command Priority Tab

This tab is covered under the AnalogOutput editor.

MultistateValue Advanced Alarms, Triggers andSecurity Level Tabs




TAC 368

BACnet Program Editor

The Program Editor allows you to run, suspend, restart, halt, and check the status of BACnet programs, running on Andover Continuum BACnet devices – b4920, bCX1 (40x0series) and b3 controllers – and third-party BACnet devices.

Note: On third-party BACnet devices, you can also load and unload BACnet programsvia the Program Editor, depending on whether the third-party device supports thesecapabilities. You cannot load and unload programs on Andover Continuum BACnetdevices.

The properties on the General tab are compliant with the BACnet standard.

If an InfinityProgram object is created on a b4920, bCX1 (40x0 series), or b3 controller via the Plain English IDE then the program can be viewed in two places in theCyberStation system because:

• b4920, bCX1 (40x0 series), and b3 controllers exist as Infinity controller andInfinityInfinet controller objects, respectively, on the "Infinity side" of the system. Inthis case, the program is an InfinityProgram object.

• b4920, bCX1 (40x0 series), and b3 controllers also can be viewed as Device objects.In this case, the program is a BACnet Program object.




Note: Refer to the Plain English Language Reference Guide, 30-3001-872, for completedetails on the IDE.

The Program Editor General Tab

The General tab provides you with the following information, some are read only andothers you fill in.

Program State This status line displays the current state of the process executing theBACnet program. One of the following values is displayed:

Idle — The process is not executing

Loading — The program is being loaded

Running — The program is currently executing

Waiting — The program is waiting for some external event.

Halted — The program is halted because of some error condition.

Unloading — The program has been requested to terminate.

Reason for Halt andDescription of Halt

These status lines display a numeric error code, a text value, and atext description, of an error that has caused the executing program tohalt. (It also tells you when the program is executing normally.)

Reason for Halt — The Reason for Halt status line displays an

integer plus one of the following values:Normal — The program is not halted due to any error condition.

Load Failed — The program could not complete loading.

Internal — The program is halted by some internal mechanism.

Program — The program is halted by a program-change request.

Other — The program is halted for some other reason.

Description of Halt — The Description of Halt field displays a user-written text description (originating in the local BACnet device on whichthe application program resides) that accompanies to the error codeand value displayed in Reason for Halt.

ProgramLocation

Depending on the local BACnet device and programming environment,this field may display the line of code that is currently executing (or thatis halted) within the program. For example, it may display a linenumber, program label, or section name. The content of what isdisplayed is defined locally.

Instance of Displays the local name (originating in the local BACnet device) of theprogram being executed. The content of what is displayed is definedlocally.

Load andUpload

Loads and unloads the content of a program, are available only insome third-party BACnet devices. They are not available on Andover Continuum BACnet devices.



TAC 370

Run Executes the program.

Restart Restarts execution of the program after it has been halted.

Halt Halts the program while it is executing.

Description Describes the application being carried out by this process.

Out of Service Check this checkbox if you wish to put this program out of service(disable it). You must check this box while the program is running.

When it is out of service, it loses communication with its attached

device. It is a good way to test the program and the processes that relyon it.

Status Displays one of four flags that indicate the general status of theprogram. Three of the flags are associated with the values of other properties of this object. A more detailed status could be determinedby reading the properties that are linked to these flags. The four flagsare:

In_Alarm — The program is in an alarm state.

Fault — The program is in a fault state.

Overridden — The program has been overridden by a mechanismthat is local to the corresponding BACnet device.

Out_Of_Service — The program is in an out-of-service (disabled)state.

Reliability Displays information about whether or not the controller has detected amalfunction that might compromise the integrity of the program.




Configuring

Schedulesand Calendars

The Schedule editor allows you to create Continuum Infinity and/or BACnet Scheduleobjects. A schedule is essentially a collection of scheduled events that typicallydetermine, for example, when equipment runs, processes occur, personnel have access

to an area, doors are locked or unlocked, and so on. A schedule comprises standarddays and user defined standard days, such as holidays. A schedule also includesBACnet exception schedules, special calendar entries based on the BACnet Calendar object, which Continuum supports. These Calendar entries can be single days, a range of days, or recurring days, in accordance with the BACnet standard. You can thereforecreate or reference Calendar object values and integrate them into a Schedule object.

This chapter covers:

• Schedule views – finding your way around

• The Configuration tab

• Working with exception schedules

• Working with standard days and user-defined days

• The Current State tab

• Proprietary Schedule properties for programs

• Mass Create – populating devices with a schedule

• Mass Change – updating multiple schedules

• Calendars and the Calendar editor

15



TAC 372

Schedule Views – Finding Your Way Around

This section discusses the various schedule views, and also offers some information for finding your way around in the Schedule editor.

Schedule Views

The Schedule editor presents yearly, weekly, and daily views. To see each view, simplyclick the Yearly, Weekly, or Daily tab, respectively:



TAC 374

To move to the next/previous year, week, or month, click the right-arrow button (next) or left-arrow button (previous) at the top of the respective tab.

On these various views, there are scheduled events for standard days and user-definedstandard days, as well as exception schedule calendar entries. Continuum supplies onlyone default user-defined day — Holiday. You may create other user-defined standarddays. The standard days, Monday through Friday, appear in one default color (light blue)while the weekend standard days, Saturday and Sunday, appear in another default color (medium blue). The user-defined day, Holiday, appears in red, by default.

Note: You may change the color of a standard or user-defined day when you edit one of these days.

Note: To see more of the schedule events on the weekly and daily views, increase thesize of your Schedule editor window, as you would increase the size of anyMicrosoft window.

Exception and Standard Day Tabs

On the left side of the Schedule editor, you see two tabs — Exception and StandardDays. Each tab shows an expandable tree structure. For example:

The Standard Days tab lists the Weekly Schedule tree (Monday through Sunday) aswell as the User Defined Days tree (Holiday by default, plus any other user-definedstandard day you create). For more information, see: Working with Standard Days and User-defined Days, later in this chapter.




The Exception tab lists the Exception Schedule tree, which includes calendar entries(single days, ranges of days, recurring days) that have been assigned (selected) or referenced. The Exception Schedule tree includes user-defined standard days. For more information, see: Working with Exception Schedules, later in this chapter.

Note: An exception-schedule entry is sometimes based on the BACnet Calendar object,which Continuum supports, in accordance with the BACnet standard. TheseCalendar object values can be integrated into a Schedule object. (See Calendarsand the Calendar Editor , later in this chapter.)

Note: To see more of the entries in the Exception and Standard Day trees, increase thesize of your Schedule editor window, as you would increase the size of anyMicrosoft window.

Configuration

You configure all Schedules, both for Infinity and BACnet controllers, using theConfiguration tab. The attributes on this tab define a schedule, when and where it takeseffect, when it is enabled or disabled, how it is downloaded to a controller, and so on.When you create a Schedule object on a BACnet controller, such as an Andover Continuum b4 controller, the Infinity-related attributes on the Configuration tab are notvisible. Likewise, when you create a Schedule object on an Infinity controller, theBACnet-related attributes are not visible. For more information, see: Configuration Tab,on the next page.

Note: When you create a Schedule object on a BACnet controller, such as an Andover Continuum b4 controller, the Infinity-related attributes in the Schedule editor, suchas some attributes on the Configuration tab, are not visible. Likewise, when youcreate a Schedule object on an Infinity controller, the BACnet-related attributes arenot visible.

Note: When you make changes to standard days in a schedule, they take effect globallyfor all years within the schedule and affect all objects set by that schedule.

Current State

The Current State tab, which is visible only for a BACnet controller’s Schedule object,displays information about the value of the current event. For more information, seeCurrent State Tab later in this chapter.



TAC 376

Mass Create and Mass Change

The Schedule editor allows you to copy and distribute (populate) a Schedule object totwo or more devices on your system. It also allows you to make Schedule-object changesto many other Schedule objects.

Click the Copy button to expose the Mass Create and Mass Change tabs appended tothe right side of the editor. These tabs are normally hidden. To expand and retract thewidth of the Mass Create/Mass Change tab area, place your cursor on the right edge of the yearly, weekly, or daily view (typically the yearly view) until it becomes a double right-

left arrow cursor. Drag this cursor left or right to expand or retract, respectively. To closethe Mass Create/Mass Change tab area, click the X button.

For more information, see Mass Create - Populating Devices with a Schedul e and MassChange - Updating Multiple Schedules, later in this chapter.

Configuration Tab

Use the Configuration tab to configure schedules, both for Infinity and BACnetcontrollers. The attributes on this tab define a schedule, when and where it takes effect,when it is enabled or disabled, how it is downloaded to a controller, and so on.

Note: When you create a Schedule object on a BACnet controller, such as an Andover Continuum b4 controller, the Infinity-related attributes on this tab are not visible.Likewise, when you create a Schedule object on an Infinity controller, the BACnet-

related attributes are not visible.

The Configuration tab attributes on a BACnet controller are shown on the next page.




The following table provides descriptions of attributes that appear on the tab for aSchedule object created on a BACnet controller.


Description Enter a description for this Schedule object.

Clear PastEvents

Check this box when you need to delete BACnet special eventsthat no longer impact an exception schedule. This may becomenecessary to conserve memory in controllers on your systemwhen updated exception schedules are sent to controllers.

By default, this box is not checked. When you check this box,

save the Schedule, and re-open the editor, the box is checked.

Important things to know about this feature:

• If you do not check this box, exception schedule event data(everything ever created) are re-sent to controllers. This canquickly consume memory, especially in controllers withlimited memory capacities.

• Events must be at least three days old before they areautomatically removed. Continuum calculates this bycomparing the day on which the event expires to the currentworkstation time.



TAC 378


Of the four types of exception choices (Date, Range of Dates,Recurrence, and Calendar Reference) only Date and Range of Dates may be automatically removed.

Newly created exceptions that take effect and expire in thepast are removed immediately — Exception entries that meetthe above criteria are automatically removed from view either when the box is initially checked or when the editor opens withthe box already checked. If you inadvertently add new exceptionswhose expiration dates are in the past (more than three days old)these expired events will also be removed from view the nexttime the editor opens.

In all cases, the exception value is written as it appears in theview when you click the OK or Apply button.

In addition to using this checkbox, you can also conservememory by creating partial-day exception schedules. SeePartial-Day Exception Schedules, later in this chapter.

EffectiveFrom/To

Using Effective From and To fields to select a day thatdesignates when the schedule becomes active and inactive. Clickthe dropdown-menu down arrow to use the calendar to select a

day that designates when the schedule becomes active andinactive. Or, as an alternative, click (highlight) the month, day, or year field and enter the digits for the month, day, or year.

Show BACnet Date Fields — Check this checkbox to use theBACnet properties for these date fields. (Remove the check touse the "system" Effective From/To.) The BACnet date fields,which are self-explanatory, allow you to enter any month, day,year, and day of week. Using the month dropdown menu, youmay select a specific month, Any month, Even months, or Oddmonths. Using the day-of-week dropdown menu, you may selecta specific day or Any day.

Note: To select any day or any year, simply enter the word "Any"into the day or year field, respectively.

Right-click switching between fields — To switch between theBACnet fields and From/To (or "system") fields, right clickanywhere in or near the fields, and select BACnet or System fromthe popup menu, depending on which fields you prefer.

Priority Using the dropdown menu, select a BACnet command priority for this Schedule object.





Time Scale From the dropdown menu, select the number of minutes withwhich you want to partition an hour in the daily and weekly views.Selections are: 5 minutes, 6 minutes, 10 minutes, 15 minutes, 30minutes, 60 minutes. The time scale applies to the entireschedule.

For example, if you select 15 Minutes, four time slots(demarcated by gray lines) appear within each hour in the dailyand weekly views throughout the schedule. For example, if youselect 5 Minutes, 12 time slots (demarcated by gray lines) appear within each hour in the daily and weekly views.

Default DataType

To apply a certain data type to all new Schedule events bydefault, select a type from the dropdown menu.

Note: It is recommended that you first assign a default data typebefore creating new events for this schedule. BACnetstandard revision 2004 requires that one data type isspecified for schedule events.

The data types of old events are not affected by this selection.However, when you assign a default data type, a messageappears, telling you that some existing scheduled events have

different (non-default) data types. If you receive this message,you should manually delete them.

When you set this default type, it also assigns this type as thedefault in the Value Type fields in the Schedule Default sectionand in the "apply at midnight" section.

Schedule DefaultValue

Value Type

This section (enabled only for devices that support the BACnetstandard revision 2004 and higher) displays a default value/typefor the entire schedule when no other value is assigned. That is,the scheduled default is used as a "last resort" for the presentvalue when no other exception or weekly scheduled event is incontrol. Check the NULL checkbox to relinquish control of acommanded property when no scheduled events are in effect.

Note: When you set the Default Data Type (see above) theschedule default value type is set to that default data typeautomatically.

Note: The Schedule Default value also works with partial-dayexception schedules. Please see Partial-day exceptionschedules , later in this chapter.



TAC 380


Apply value andtype to allSchedule eventsat midnight.

ValueValue Type

Check this checkbox to ensure that all weekly and exceptionSchedule events are reset at midnight to the value and data typespecified in the Value and Value Type fields. An event isscheduled at midnight automatically so that you do not have to doit manually.

Note: This checkbox is checked by default for pre-revision 2004schedules. If your schedules do not support revision 2004,do not remove the check from this box. This ensures that avalue/type are applied at midnight, thereby allowing a"whole day" schedule.

Note: With the introduction of the Schedule Default in revision2004, you can use the Schedule Default section (seeabove) to apply a value/type, whereby this schedule defaultis applied to events at midnight automatically, in absenceof any other event in control at midnight.

When this box is checked, the value/type specified here takeseffect at midnight (00:00) for any new exception schedule thatyou create. (See also: Working with Exception Schedules andWorking with Standard and User-defined Days.)

Enter a value, and from the dropdown menu select a data type, tobe applied at midnight to all weekday and schedule event entries.They must be applied at midnight to comply with the BACnetstandard. (For more information on Value, Value Type, and theTime Value dialog, please see: Working with ExceptionSchedules and Working with Standard and User-defined Days.)

Note: These fields are selectable only when the Apply this valueand type to all Schedule events at midnight checkbox ischecked.

Object PropertyList

This window lists BACnet objects that are set by this schedule.To add a schedule to the list, click the Add button and from theSearch for an object property reference dialog, search for andselect an object, then click the Select button. The selectionappears in the list. To remove an object from the list, highlight it inthe list, then click Delete.




The Configuration tab attributes on an Infinity controller look like this:



TAC 382

The following table provides descriptions of attributes that appear on this tab for aSchedule object created on an Infinity controller.


Description Enter a description for this Schedule object.

State Use the dropdown menu to enable or disable the schedule.

PointConfiguration

In the Occupancy field, enter the path or click the browse buttonto search for Infinity DateTime point that designates when theschedule becomes active. In the Unoccupancy field, enter thepath or click the browse button to search for an Infinity DateTimepoint that designate when the schedule becomes inactive. In theOccupancy Point field, enter the path or click the browse buttonto search for the InfinityNumeric or InfinityOutput object that willbe set by this schedule.

A schedule is used to turn the object on (active) or off (inactive).

Time Scale From the dropdown menu, select the number of minutes withwhich you want to partition an hour in the daily and weekly views.Selections are: 5 minutes, 6 minutes, 10 minutes, 15 minutes, 30minutes, 60 minutes. The time scale applies to the entireschedule.

For example, if you select 15 Minutes, four time slots(demarcated by gray lines) appear within each hour in the dailyand weekly views throughout the schedule. For example, if youselect 5 Minutes, 12 time slots (demarcated by gray lines) appear within each hour in the daily and weekly views.

Events These five fields display current information about this schedule'sevents.

Present Value — Displays the current event value: Active or Inactive.

Occupancy Time — Displays the specified occupancy time fromOccupancy time field, above.

Unoccupancy Time — Displays the specified unoccupancy timefrom Unoccupancy time field, above.

Next Occupancy Time — Displays the next day/time theschedule becomes active.

Next Unoccupancy Time — Displays the next day/time theschedule becomes inactive.

Note Enter information about this schedule. This note appears inweekly and daily calendar views.





AutomaticScheduleDownload

Check this checkbox, and select a day and time, to download thisschedule's values automatically from the workstation database tothe controller on which this schedule was opened. Use the daydropdown menu to select a day.

To select a time, click and highlight the hours, minutes, seconds,or AM/PM field to select the hour, minute, second, and AM/PM,you want the automatic download to occur. Use the up and downarrows to move to the previous hour/minute/second and to select AM or PM.

Action To download this schedule’s values to the controller immediately(and not wait for the designated download day/time) click theDownload Events to Controller NOW button.

Working with Exception Schedules

This section covers:

• Overview

• Creating an exception entry

• Partial-day exception schedules

• Exception schedule icons

• Editing, deleting, and moving an exception entry

• Making user-defined standard days exception schedules

• Creating an exception entry via Daily and Weekly tabs

• Selecting (highlighting) an entire month or an entire week on the yearly view

Overview

Using the Exception tab, you may create and/or reference a BACnet exception scheduleto your Schedule object. An exception schedule is a special schedule entry that issometimes based on the BACnet Calendar object, which Continuum supports. Theseexception entries can be single days, a range of days, recurring days, or a referenced

Calendar object, in accordance with the BACnet standard. You can therefore integrateCalendar object values into a Schedule object.

Note: Exception schedules can also be partial days, as of the implementation of theBACnet protocol revision 4. That is, you can create two or more exceptionschedules for the same day. See also Partial-day exception schedules, later in thischapter.

Note: You may not use a recurring-day entry or referenced Calendar-object exceptionentry for a schedule created on an Infinity controller — only a BACnet controller.

The Exception tab lists the Exception Schedule tree, which includes single days,ranges of days, recurring days, and referenced calendar days that have been assigned



TAC 384

(selected). This includes the assignment of user-defined days, as well as any newexception entry that you create or reference via the Exception Schedule tree.

Creating an Exception Entry

To create a new exception entry, follow this procedure:

1. Click the New Exception button beneath the Exception Schedule tree (or right clickException Schedule and select New Exception from the popup). The SpecialEvent dialog (or BACnet Special Event dialog for BACnet controllers) appears:

2. In the Entry Type section, select one of the following radio buttons:

Date

Range of dates

Recurrence

Calendar Reference

Notice the data fields on the right side of the dialog are different for each selection.

Note: The Recurrence and Calendar Reference radio button selections do notappear for a Schedule on an Infinity controller.

3. Enter the desired information in the data fields on the right side of the dialog. Thesefields are self-explanatory.




Note: For year, month, day, and day of week, you can select "any," as opposed to aspecific selection. To do so, check the respective Any checkboxes. Also, for Month, you may use the dropdown menu to select Odd Months or EventMonths, as opposed to a specific month.

For range, enter a starting and ending date.

For recurrence, enter a recurring weekday for a particular month. For example, if youwere defining "Thanksgiving," you could choose Last, Thursday, and November.

For a calendar reference, click the Calendar Reference Object field's browse

button. The Select an object dialog appears. Search for and select the Calendar object (on a BACnet controller) that you want to reference and integrate into your Schedule object. Click the Select button. The Calendar object path appears in theCalendar Reference Object field.

4. Select either the Time Value List radio button (when you want to add one or moreunique time values to apply to the new entry) or the User Defined Standard Day radio button when you want select the time value of an existing user-defined day,such as Holiday.

If you select Time Value List, go to step 5. If you select User Defined StandardDay, go to step 6.

5. Click the Add button. The Time Value dialog appears:

In the Time field, select a time at which you want this entry's event to apply a value— hour, minute, second.

Note: If you want to use BACnet time fields (in which you can specify a specific time or any time) check the BACnet Time Fields checkbox. There are four BACnet timefields. From left to right, enter the hour, minute, second, and hundredth of second. To enter any hour, any minute, any second, or any hundredth of second,enter the word "Any" in the desired field.

In the Value field and Value Type field (schedule on a BACnet controller) enter a valueand value type. For example, on a BACnet controller, for a temperature value, you couldenter a real number and select Real from the Value Type field's dropdown menu. For example, you could enter a text value, then select Character String as a value type.



TAC 386

For a schedule on a BACnet controller, choices for Value Type are:

Boolean

Unsigned Integer

Signed Integer

Enumerated

Date

Time

Character String

Real

BACnet Object Identifier

Double

Octet String

Bit String

Note: Check the NULL checkbox to relinquish control of a commanded property when noscheduled events are in effect.

Note: The Value Type field is not available for a schedule on an Infinity controller. Value field choices on an Infinity controller are Active and Inactive (on/off). For example:

In the Notes field, describe the entry's event. These notes, along with the values, appear in the weekly and daily views. Click OK. The time/value entry appears in the Time ValueList window in the Special Event dialog.

Repeat this procedure if you want to apply two or more times/values for this entry. For example, you may create one time/value to raise the temperature at 7:00 a.m. to 70degrees, and another to lower the temperature at 9:00 pm to 55 degrees.




CAUTION: Too many exception-entry events scheduled on one day can createtime/value conflicts. If this happens, the following warning appears on the Daily tab,as well as the Weekly tab for each conflicted day:

There are too many events in this day. Please double-click

to see details.

Double click over this warning on the Daily or Weekly tab. The Time Values for Day dialog appears, displaying a list of times/values for events scheduled on that day.

Note: The values you select are applied to the attached objects listed in the ObjectProperty List (BACnet controller) on the Configuration tab. On an Infinitycontroller, values are applied to the InfinityNumeric or InfinityOutput pointspecified in the Occupancy Point field on the Configuration tab.

Note: You may also access the Time Value dialog (and create a new exceptionevent) by clicking in the time margin or a non-event slot in the Daily or Weekly tab. The Time Value dialog accessed from those tabs asks for a start-timeevent, as well as an end-time event. For example:

"Rest of the day" end time — As described above, when you access the Time

Value dialog on the Daily or Weekly tab, and you are asked to specify both a start

time and an end time. Here you have the option of specifying a midnight end time by

checking the Rest of the day checkbox. Check this box when this event needs to be

active for the remainder of the day. It also saves you the time of filling in the End

time fields.

Again, if you want to use BACnet time fields (in which you can specify a specific time

or any time) check the BACnet Time Fields checkbox.

Go to step 7.



TAC 388

6. From the dropdown menu, select the user-defined standard day whose value youwant to apply to this new entry.


7. In the Event Priority field of the BACnet Special Event dialog, select a BACnetcommand priority (1...16) from the dropdown menu. This priority is useful if there areexception schedule event conflicts. For more information on BACnet commandpriority, see the Help topic, Working with Command Priorities, in your Continuumonline help, and Chapter 14, BACnet , and your BACnet Standard.

8. In the Name field, enter a name or description of the day, range, recurrence, or referenced entry. This name appears for this entry in tree.

9. Click OK. The new entry is added to the tree.

Note: At this point, you may right click the Daily or Weekly tab and from the popupmenu and select the number of minutes with which you want to partition anhour in the daily and weekly views. Selections are: 5 minutes, 6 minutes, 10minutes, 15 minutes, 30 minutes, 60 minutes. (This is known as the TimeScale, which you may also set on the Configuration tab.) The time scaleapplies to the entire schedule.

For example, if you select 15 Minutes, four time slots (demarcated by gray lines) appear within each hour in the daily and weekly views throughout the schedule. For example, if you select 5 Minutes, 12 time slots (demarcated by gray lines) appear within each hour inthe daily and weekly views.

Partial-Day Exception Schedules

The BACnet standard, revision 2004, introduces partial-day exception schedules. Beforerevision 2004, an exception schedule governed an entire day, an entire day for each dayin a range or days, or an entire day for each day of recurring days. This meant that anexception schedule would stay in control for an entire day and never relinquish controlback to weekly scheduled events for that day, since a weekly schedule yields to anexception schedule.

Passing Control Back to Weekly Schedule on Same Day -- Partial-day exceptionscheduling allows you to control a portion of a given day, rather than the whole day. Thismeans that exception events and weekly events can be integrated into the same day, asneeded. Important one-time exception events now can temporarily interrupt the weeklyschedule (for only as many hours as it needs to) and then hand control back to theweekly schedule. That is, regularly scheduled events are no longer completely ignoredwhen a weekly and exception schedule fall on the same day.

Before revision 2004, to overcome this dilemma, weekly schedule events were oftenincluded in the exception schedule. This was the only way to add additional events to thatday.




For example, take a classroom that is normally controlled by a weekly schedule, wherethe room is occupied from 9:00 a.m. to 3:00 p.m. But suppose that one particular Wednesday a special lab takes place from 6:00 to 8:00. Before revision 2004, if anexception schedule were added to allow this room to be occupied from 6:00 to 8:00 on aparticular Wednesday, that exception would also need to specify the room as occupiedfrom 9:00 to 3:00 because all Wednesday's normal events would be overridden.

Partial-day scheduling removes that limitation. When an exception event ends, controlcan be passed back to the weekly schedule. In the classroom example, this allows you tospecify an exception entry only from 6:00 to 8:00. You can pass control from the

exception back to the weekly schedule by specifying a special value (NULL) in theexception's time value list. In the classroom case, it means that the exception could looklike this:

• 6:00 a.m. - Specify the value (for example, turn on heat or light) that makes the roomoccupied.

• 8:00 a.m. - Specify the value that makes the room not occupied.

• At a time after 8:00, but before 9:00 - Specify NULL.

Note: The exception and weekly schedule properties can also interact with the ScheduleDefault property, which might allow the above schedule to be specified differently,but control identically. See also the Configuration tab.

Using Two Exception Schedules on the Same Day -- Before revision 2004, it was not

possible to use different exceptions to control different parts of the same day. Now, oneexception can control a morning's events and another exception control the evening'sevents. Using the previous classroom example, suppose that, on a Sunday, the roommust be occupied from 6:00 a.m. to 8:00 a.m., and again from 9:00 to 3:00 p.m. Noweekly schedule is in effect for Sunday. This means that the exceptions could look likethis:

Exception 1

• 6:00 a.m. - Specify the value that makes the room occupied.

• 8:00 a.m. - Specify the value that makes the room not occupied.

• At a time after 8:00, but before 9:00 - Specify NULL.

Exception 2• 9:00 a.m. - Specify the value that makes the room occupied.

• 3:00 p.m. - Specify the value that makes the room not occupied.

Partial-Day Exceptions and Schedule Default -- Partial-day exception schedules canalso work with the schedule default value, established in the property, Schedule Default.(See also the Configuration tab.) The value of the schedule default is the value theschedule takes at any moment where there are no exception or weekly events incontrol. Using the first classroom example (exception vs. weekly events), the 8:00 value,which makes the room unoccupied, is not necessary if the schedule default has the same



TAC 390

value. Instead, the exception can just specify the NULL value and cause the scheduledefault to take control because there are no weekly events at 8:00 a.m.

Exception Schedule Icons

As you add exception entries, the Exception Schedule tree identifies them in the list withthe following icons:

Single day

Range of days

Recurring days

Calendar object reference

When you expand an entry, its time values and command priorities appear in the tree.The exception entries are highlighted on the yearly view and noted in the weekly anddaily views.

Note: Dates listed in the tree appear in red on the yearly view. If you select a day in thetree, it appears in blue on the yearly view.

Note: When you click and select a date in the yearly view, you may right click and assign

a user-defined standard day. Any day that is assigned in this manner also appearsin the tree. See also: Working with Standard Days and User-defined Days, later inthis chapter.

Editing, Deleting, and Moving an Exception Entry

Editing an Entry — To edit an existing exception entry in the Exception Schedule tree,simply right click its icon/entry in the tree, and select Edit from the popup menu. TheSpecial Event dialog appears. Use the procedure for creating an exception entry, above,as guidelines.

Deleting an Entry — To delete an exception entry in the Exception Schedule, simplyright click its icon/entry in the tree, and select Delete from the popup menu. The entry isremoved from the tree and the calendar view.

Moving an Entry in the Tree — To move an entry up or down in the tree, simply rightclick its icon/entry, and select Up or Down from the popup menu. The entry is insertedabove the previous or next entry in the tree, respectively.

Making User-Defined Standard Days Exception Entries

From the Standard Day tab, in the User Defined Day tree, when you assign a user-defined standard day (or a range of user-defined standard days) on the yearly view, theday or range also becomes part of the exception schedule. For more information, see:Working with Standard and User-defined Days, later in this chapter.




Creating an Exception Entry via Daily and Weekly Tabs

On the Daily and Weekly tabs of the Schedule editor, you may click inside a time slot, or the time margin, to bring up the Time Value dialog and add a time/value event. (Seeprocedures above for information on the Time Value dialog.) When you access the TimeValue dialog from these tabs, it provides two sections for the Start time and End time.Hence you are creating two time/value events in using one dialog — a start event and anend event.

Selecting an Entire Month or Entire Week on the Yearly View

To select (highlight) an entire month or an entire week:

1. Select the Yearly tab.

2. To select (highlight) an entire month, click inside the day initials for that month (S M TW T F S). To select (highlight) an entire week, click to the left of that week (to the leftof Sunday "S" of that week).

Working with Standard Days and User-defined Days

This section covers the following:

• Overview

• Editing a weekly standard day

• Creating and editing a user-defined standard day

• Assigning one or more single user-defined standard days

• Assigning a range of user-defined standard days in the yearly view

• Resetting a user-defined standard day as a weekly standard day

• Deleting a user-defined standard day

• Using exception schedules exclusively (deleting weekly standard day events)

• Selecting (highlighting) an entire month or an entire week from Yearly tab

Overview

The Schedule editor, by default, supplies weekly standard days (Monday throughSunday). These standard days are listed on the Standard Day tab, in the Weekly

Schedule tree.

You may modify any weekly standard day. Within each standard day, you add and editevents, specifying the time these events become active and inactive during the day, aswell as values for these events — for example, temperature values, on/off switches, andso on.



TAC 392

Note: For schedules on an Infinity controller, an event value can only be either on(active) or off (inactive). However, on a BACnet controller, you may apply manydifferent types of event values — for example, real numbers, character strings,arrays, Boolean values, and so on, and change these values during the course of aday, as needed.

Event information, including notes on and the current state of each event, appears withinthe daily and weekly calendar view of a weekly standard day.

Also on the Standard Day tab, in the User Defined Day tree, you may create user-defined standard days. Only one user-defined standard day is supplied by default —Holiday.

Note: When you edit standard days and user-defined standard days, you make globalchanges that affect all weeks of all years within that schedule, and all objects thatare attached to that schedule.

Editing a Weekly Standard Day

To edit a standard day and add/modify events within that standard day, perform thisprocedure:

1. Select the Standard Day tab.

2. In the Weekly Schedule tree, right click the standard day you want to edit(Monday...Sunday) and select Edit from the popup. The standard day dialog

appears. (The name of the standard weekday is the title of the dialog.)

3. Check the background color, and change this color, if desired.

If you wish to pick a new color for this weekday, click the color box. From the Color dialog, select a new color, as you would in Microsoft Windows. Click OK, after selecting the new color.

This color is shown in all the views, as well as in the Standard Day tab, for thisweekday.

4. To add a new standard-day event, click the Add button.

To edit an existing standard-day event, in the Event List highlight the event you wantto change, and click the Edit button.

The Time Value dialog appears.Note: To delete an existing standard-day event, in the Event List highlight the event

you want to delete, and click the Delete button. The event is removed from thelist.

In the Time Value dialog:

In the Time field, select a time at which you want this event to apply a value — hour,minute, second.

Note: On a BACnet controller, if you want to use BACnet time fields (in which youcan specify a specific time or any time) check the BACnet Time Fields checkbox. There are four BACnet time fields. From left to right, enter the hour,




minute, second, and hundredth of second. To enter any hour, any minute, anysecond, or any hundredth of second, enter the word "Any" in the desired field.

In the Value field and Value Type field (schedule on a BACnet controller) enter avalue and value type. For example, on a BACnet controller, for a temperature value,you could enter a real number and select Real from the Value Type field's dropdownmenu. For example, you could enter a text value, then select Character String as avalue type.

Note: The Value Type field is not available for a schedule on an Infinity controller.Value field choices on an Infinity controller are Active and Inactive (on/off).


Boolean

Unsigned Integer

Signed Integer

Enumerated

Date

Time

Character String

RealBACnet Object Identifier

Double

Octet String

Bit String

Check the NULL checkbox to relinquish control of a commanded property when noscheduled events are in effect.

In the Notes field, describe the entry's event. These notes, along with the values, appear in the weekly and daily views.

Click OK. The event appears in the Event List window in the standard day dialog.

Repeat this procedure if you want to apply two or more time/value events for this entry.For example, you may create one time/value to raise the temperature at 7:00 a.m. to 70degrees, and another to lower the temperature at 9:00 pm to 55 degrees.

Note: The values you select are applied to the attached objects listed in the ObjectProperty List (BACnet controller) on the Configuration tab. On an Infinitycontroller, values are applied to the InfinityNumeric or InfinityOutput point specifiedin the Occupancy Point field on the Configuration tab.

Note: You may also access the Time Value dialog (and create a new event) by clickingin the time margin or a non-event slot in the Daily or Weekly tab. The Time Value dialog accessed from those tabs asks for a start-time event, as well as an end-timeevent. For example:



TAC 394

"Rest of the day" end time — As described above, when you access the TimeValue dialog on the Daily or Weekly tab, and you are asked to specify both a start

time and an end time. Here you have the option of specifying a midnight end time by

checking the Rest of the day checkbox. Check this box when this event needs to be

active for the remainder of the day. It also saves you the time of filling in the End

time fields.

5. Check the Apply events to all weekdays in weekly schedule checkbox to copy thisweekday's events to all other weekdays.

6. Click OK.

The standard day changes appear throughout the Schedule editor.

Note: At this point, you may right click the Daily or Weekly tab and from the popup

menu select the number of minutes with which you want to partition an hour inthe daily and weekly views. Selections are: 5 minutes, 6 minutes, 10 minutes,15 minutes, 30 minutes, 60 minutes. (This is known as the Time Scale, whichyou may also set on the Configuration tab.) The time scale applies to theentire schedule.

For example, if you select 15 Minutes, four time slots (demarcated by gray lines) appear within each hour in the daily and weekly views throughout the schedule. For example, if you select 5 Minutes, 12 time slots (demarcated by gray lines) appear within each hour inthe daily and weekly views.




Creating and Modifying a User-defined Standard Day

To create a new user-defined standard day, or modify an existing one, perform thisprocedure:


2. To add a new user-defined standard day: Click the New User Defined Day buttonbeneath the User Defined Day tree (or right click User Defined Day, and select New from the popup).

To edit an existing standard day: In the User Defined Day tree, right click the nameof the user-defined standard day you wish to change.

The Standard Day dialog appears.

Note: Only one user-defined standard day is provided, by default — Holiday.

3. Check the background color, and change this color, if desired.

If you wish to pick a new color for this user-defined standard day, click the color box.From the Color dialog, select a new color, as you would in Microsoft Windows. ClickOK, after selecting the new color.

This color is shown in all the views, as well as in the Standard Day tab, for this user-defined standard day.

Note: The default color for Holiday is red.

4. To add a new user-defined-standard day event, click the Add button.

To edit an existing user-defined standard day event, in the Event List, highlight theevent you want to change, and click the Edit button.

The Time Value dialog appears.

Note: To delete an existing user-defined standard day event, in the Event Listhighlight the event you want to delete, and click the Delete button. The event isremoved from the list.

In the Time Value dialog:

In the Time field, select a time at which you want this event to apply a value — hour,minute, second.

Note: On a BACnet controller, if you want to use BACnet time fields (in which youcan specify a specific time or any time) check the BACnet Time Fields checkbox. There are four BACnet time fields. From left to right, enter the hour,minute, second, and hundredth of second. To enter any hour, any minute, anysecond, or any hundredth of second, enter the word "Any" in the desired field.

In the Value field and Value Type field (schedule on a BACnet controller) enter avalue and value type. For example, on a BACnet controller, for a temperature value,you could enter a real number and select Real from the Value Type field's dropdownmenu. For example, you could enter a text value, then select Character String as avalue type.



TAC 396

Note: The Value Type field is not available for a schedule on an Infinity controller.Value field choices on an Infinity controller are Active and Inactive (on/off).


Boolean

Unsigned Integer

Signed Integer

Enumerated

Date

Time

Character String

Real

BACnet Object Identifier

Double

Octet String

Bit String

Check the NULL checkbox to relinquish control of a commanded property when noscheduled events are in effect.

In the Notes field, describe the entry's event. These notes, along with the values, appear in the weekly and daily views.

Click OK. The event appears in the Event List window in the Standard Day dialog.

Repeat this procedure if you want to apply two or more time/value events for this entry.For example, you may create one time/value to raise the temperature at 7:00 a.m. to 70degrees, and another to lower the temperature at 9:00 pm to 55 degrees.

CAUTION: Too many exception-entry events scheduled on one day can createtime/value conflicts. If this happens, the following warning appears on the Daily tab,as well as the Weekly tab for each conflicted day:

There are too many events in this day. Please double-click to see details.

Double click over this warning on the Daily or Weekly tab. The Time Values for Daydialog appears, displaying a list of times/values for events scheduled on that day.


Note: You may also access the Time Value dialog (and create a new event) byclicking in the time margin or a non-event slot in the Daily or Weekly tab. The




Time Value dialog accessed from those tabs asks for a start-time event, aswell as an end-time event.

5. Click OK.

The user-defined standard day changes appear throughout the Schedule editor.

Note: At this point, you may right click the Daily or Weekly tab and from the popupmenu select the number of minutes with which you want to partition an hour inthe daily and weekly views. Selections are: 5 minutes, 6 minutes, 10 minutes,15 minutes, 30 minutes, 60 minutes. (This is known as the Time Scale, which

you may also set on the Configuration tab.) The time scale applies to theentire schedule.

For example, if you select 15 Minutes, four time slots (demarcated by gray lines)appear within each hour in the daily and weekly views throughout the schedule. For example, if you select 5 Minutes, 12 time slots (demarcated by gray lines) appear within each hour in the daily and weekly views.

Assigning One or More Single User-defined Standard Days

To assign one or more single user-defined standard days in your schedule:


2. In the yearly view, select (left click) the day you wish to assign, and then right click.From the popup menu, select Assign a User Defined Standard Day, as well as thename of the user-defined day you wish to assign.

The yearly view shows that day as the user-defined day you selected, in itsdesignated color.

The Exception Schedule tree also lists that day as a single exception day, with itssingle-day icon. (See: Working with Exception Schedules, earlier in this chapter.)

Note: To assign two or more individual (non-consecutive) user-defined standarddays, hold down the CTRL key, and click (highlight) the individual days youwish to assign. Right click, and proceed as described, above. (Holding theSHIFT key in this way allows you to assign two or more consecutive days.)

Assigning a Range of User-defined Standard Days in Yearly View

To assign a range of user-defined standard days:


2. In the yearly view, click and hold the mouse button on the first day of the range (for example, February 15).

3. Drag the cursor on the calendar to the last day of the range (for example, February22). The range (February 15...22) is highlighted.

4. Right click, and from the popup menu, select Assign a User Defined Standard Day,as well as the name of the user-defined day you wish to assign for that range.

The yearly view shows a range of that user-defined day, in the designated color.



TAC 398

The Exception Schedule tree also lists these days as an exception range of days,with its range icon. (See: Working with Exception Schedules, earlier in this chapter)

Resetting a User-defined Standard Day to a Standard Day

To reset a user-defined standard day to a weekly standard day:


2. In the yearly view, select (left click) on the user-defined day you wish to set back to aweekly standard day, and then right click.

3. From the popup, select Reset to weekly schedule.

Note: This also applies to ranges and recurrences.

Deleting a User-defined Standard Day

To delete a user-defined standard day:


2. In the User Defined Day tree, right click the user-defined day you wish to delete.

3. From the popup menu, select Delete.

Caution: The user-defined standard day is deleted and removed from everywhereit is used, including the Exception Schedule.

Using Exception Schedules Exclusively (Deleting Weekly StandardDay Events)

If you do not wish to use the weekly standard day schedule (as listed in the WeeklySchedule tree), and want to use exception schedules exclusively, perform the followingprocedure. Using an exception schedule exclusively is beneficial when you need non-repetitive schedules — for example, when students are entering and leaving a laboratory,based on their course requirements and the amount of time it takes them to finish their work, rather than a weekly scheduled time-allotment.


2. Right click Weekly Schedule.

3. From the popup, select Delete Weekly Events.

WARNING: When you make this selection, all existing events in all weekly standarddays are removed from your schedule.

Selecting an Entire Month or Entire Week on Yearly View

To select an entire month or an entire week:


2. To select (highlight) an entire month, click inside the day initials for that month (S M TW T F S).




To select (highlight) an entire week, click to the left of that week (to the left of Sunday"S" of that week).

Current State Tab

This tab displays information about the value of the current event. This tab is not visibleon Schedules for Infinity controllers.


Present Value Displays the present value of the current event. This can be of anyBACnet time/value type. (See Working with Exception Schedulesand Working with Standard and User-defined Days.)

Reliability Indicates whether or not a malfunction has been detected,compromising the integrity of the present value of the currentevent. Possible reliability settings are:

• NoFaultDetected – Indicates that the present value is reliableand that no fault has been detected.

• UnderRange – Indicates that the sensor connected to theinput is reading a value that is lower than the normal operatingrange.

• OverRange – Indicates that the sensor connected to the input

is reading a value that is higher than the normal operatingrange.

• UnReliableOther – Indicates that the sensor has detectedthat the present value is unreliable and that none of the aboveconditions describes the nature of the problem.

Status Flags Provides information on the condition of the value of the currentevent. The condition can be one of the following:

• InAlarm – Indicates that the event state has a value other than NORMAL.

• Overridden – Indicates that a local device has manuallyoverridden the object.

• Fault – Indicates that the Reliability has a value other thanNoFaultDetected.

• OutOfService – Indicates that the object is disabled.

Transition Time Note: These Transition Time fields appear only on controllersthat support the BACnet Standard protocol revision 4.

Displays the day/time when objects in the object property list(Configuration tab) transition from one value to another.

Previous — Displays the last day/time objects transitioned(changed) from one value to another.

Next — Displays the next day/time that objects will transition



TAC 400


(change) from one value to another.

Following — Displays the day/time, following the next transition,that objects will transition (change) from one value to another.

Note: See also Proprietary Schedule Properties for Programs,below.

SetValue Check the Out Of Service checkbox when you want to assign afixed value to schedule event — when you do not want to computethe value from the weekly schedule, exception schedule, or schedule defaults.

When this box is not checked, the fields are not selectable.

Proprietary Schedule Properties for Programs

Andover Continuum BACnet controllers support proprietary Schedule-object propertiesthat are used in Plain English programs to optimize the start and stop times for scheduledevents in HVAC systems. These proprietary properties are based on scheduledoccupancy times — for example, when rooms need to be prepared with heating beforeoccupancy or when lights need to be shut off after occupancy.

Note: See also the Transition Time fields on the Current State tab.The properties are:

Property Identifier Meaning

PreviousTransitionTime 512 The time when the Schedule's Present_Valuemost recently changed value

NextTransitionTime 513 The time when the Schedule's Present_Valueis next scheduled to change value after thetime indicated by Next_Transition

FollowingTransitionTime 514 The time when the Schedule's Present_Valueis next scheduled to change value after thetime indicated by Next_Transition

These properties are unsigned integer values, each giving a date and time expressed asthe number of seconds.

Plain English, which specifies the behavior of Program objects, can compare these timeswith the present time and compute time intervals.

In a Plain English program, the value of the each property would be specified as follows:

ScheduleName PreviousTransitionTime

ScheduleName NextTransitionTime

ScheduleName FollowingTransitionTime




where ScheduleName is the name of the Schedule object, whose event start and stoptimes are being computed.

Each transition indicates a scheduled change in the value of the Schedule'sPresent_Value property. These values are stored as, and can be read or written as,InfinityDateTime objects.

Note: In a Plain English program, the ReadProperty function can be used to retrieve thevalues of these properties. (These properties are read-only.)

When determining a transition, time-value pairs that specify the same value as the

Schedule's PresentValue (that do not change the value) are not considered transitions.Similarly, if two or more time-value pairs have the same time, only the last pair with thattime is used for determining a transition.

For more information on Plain English, please see the Plain English LanguageReference, 30-3001-872, and the Continuum online help.

Mass Create – Populating Devices with a Schedule

Using the Schedule editor's Mass Create tab, you may immediately copy and distribute(populate) this Schedule object to other devices on your system. This is very useful whenother controllers throughout your system need to use this schedule.

In the Schedule editor, click the Copy button to expose expose the Mass Create tab and

Mass Change tab, appended to the right side of the editor. These tabs are normallyhidden, as shown below:



TAC 402

When you click the Copy button, the tabs become visible, as shown below:

To expand and retract the width of the Mass Create/Mass Change tabs, place your cursor on the left border of the tab area until it becomes a double-arrow cursor. Drag thiscursor left or right to expand or retract, respectively. When the tab area covers part of the Yearly, Weekly, or Daily view, as shown above, use the horizontal scroll bar to see theright side of the view.

To close the Mass Create/Mass Change tab area, click the X button, located in theupper-right corner of the tab area.

As the tab indicates, there are three general steps for populating a schedule:

• Search for controllers you want to populate.

• Select the controllers to receive this schedule.

• Populate (distribute) the schedule to the selected controllers.

To “mass create” a schedule, follow this procedure:

1. On the Mass Create tab, in the search field of Step 1 (Search for devices to

populate with this schedule), use the wildcard asterisk to enter an alphanumericstring contained in the paths of controllers that need to have this schedule.

For example, *fan* would list all the controllers whose paths have the string "fan".

Note: If you want to list all controllers, and not narrow the list, leave this field blank(with just the asterisk).

2. Click the Search button.

Based on what you enter in the search field, controller paths are listed under theDevice column in the window of Step 2.




Note: If your schedule is created on a BACnet controller, BACnet devices are listed.Likewise, if it is created on an Infinity controller, Infinity devices are listed.

3. In the list, highlight (select) one or more controllers with which you want to populatethis schedule. Also:

To select them all, right click a controller and choose Select All from the popup

menu.

To deselect them all, right click a controller and choose Select None from the popup

menu.

To remove entries from the list, highlight them and click the Remove button. (Or you

may right click an entry, and select Remove Devices from the popup menu.)

Adding a controller to the list — To add device entries to the list, click the Add button(or right click an entry and select Add Devices).

The Selection dialog appears.

Note: As an alternative you may also drag and drop device objects from ContinuumExplorer to the member object list window.

From the Selection dialog, search for and select the device objects you want to add.

Use the Objects of type dropdown menu to select the object class you want to add:InfinityController, InfinityInfinetCtrl, or Device. Only objects of that object class type

appear. (For Infinity schedules, the Device object is not available in this dropdown menu.)

Click the Select button. The paths of the newly added objects appear in mass-create list.

Note: In the Selection dialog, you may use the network view button, folder-view button,and other buttons, as well as the Folder dropdown menu to expose the tree (asyou would in Continuum Explorer) to adjust view of directory paths and availableobjects.

Click the Populate button (Step 3). The schedule is copied to the selected devices in thelist.

Note: Look at the Status column in the list in Step 2. For each list member, this columnstates whether the population process has succeeded or failed.

If the process fails — If the process fails, some possible explanations are:

• One or more controllers are offline.

• The schedule contains a Calendar object reference and you are attempting topopulate a BACnet controller that does not support Calendar objects.

• You are attempting to copy a schedule to your own controller (the one on which theschedule was created).

• You are attempting to copy a schedule to a controller that does contain the objectslisted in the Object Property List of the Configuration tab (BACnet) or that doescontain the attached Occupancy Point object of the Configuration tab (Infinity).



TAC 404

Mass Change – Updating Multiple Schedules

Note: In the Schedule editor, click the Copy button to expose expose the Mass Create tab and Mass Change tab, appended to the right side of the editor. These tabs arenormally hidden. For details on expanding and collapsing these tabs in the editor,please see the previous section, Mass Create.

Using the Schedule editor's Mass Change tab, you may immediately copy your Scheduleconfiguration to other Schedule objects on your system, thereby "updating" them. This isvery useful when other schedules require the exact same events, special calendar days,

attached objects, and so on. Click the right-arrow button in the right-hand corner of theeditor to expose the Mass Change tab (along with the Mass Create tab) appended tothe right side of the editor:

As the tab indicates, there are three general steps for updating a schedule:

• Search for schedules you wish to update.

• Select the schedules whose configurations need to be updated.

• Update the selected schedules by copying (overwriting) this schedule's configurationover theirs.

To “mass change” a schedule, follow this procedure:




1. On the Mass Change tab, in the search field of Step 1 (Search for schedules toupdate), use the wildcard asterisk to enter an alphanumeric string contained in thepaths of schedules that need to be updated. For example, *sched* would list all thecontrollers whose paths have the string "sched".

Note: If you want to list all schedules, and not narrow the list, leave this field blank(with just the asterisk).

2. Click the Search button.

Based on what you enter in the search field, schedule paths are listed under the

Device column in the window of Step 2, and the names of those Schedule objectslisted under the Schedule Name column.

3. In the list, select one or more schedules you want to update. Also:

To select them all, right click in the list and choose Select All from the popup menu.

To deselect them all, right click in the list and choose Select None from the popup

menu.

To remove entries from the list, highlight them and click the Remove button. (Or you

may right click an entry, and select Remove Devices from the popup menu.)

To edit any schedule in the list, right click the schedule you want to edit, and select

Edit Schedule from the popup menu (or simply double click the schedule).

The Schedule editor for that schedule appears with its current (last-saved)configuration. If at any time you wish to return to the original (previous) original

schedule, click the Return to path at the bottom, beneath Step 3.

Adding a schedule to the list — To add schedule entries to the list, click the Add

button (or right click an entry and select Add Schedules).

The Selection dialog appears.

Note: As an alternative, you may also drag and drop Schedule objects fromContinuum Explorer to the member object list window.

From the Selection dialog, search for and select the Schedule objects you want to

add.

Only objects of object class type, Schedule, appear.Click the Select button. The paths of the newly added objects appear in mass-

change list.

Note: In the Selection dialog, you may use the network view button, folder-viewbutton, and other buttons, as well as the Folder dropdown menu to expose thetree (as you would in Continuum Explorer) to adjust view of directory paths andavailable objects.

4. Click the Update button (Step 3).

Your schedule configuration overwrites the configurations of the selected schedulesin the list.



TAC 406

Note: Look at the Status column in the list in Step 2. For each list member, thiscolumn states whether the update process has succeeded or failed.

Calendars and the Calendar Editor

Calendar is a standard BACnet class object. A Calendar object is typically used with andreferenced by Schedule objects. You use Calendar simply to select a day on a yearlyview of a calendar, as you would according to the BACnet standard. Specifically, via theCalendar Entry dialog, you establish:

• A single-day• A range of dates

• A recurrence of a day

You create a Calendar object on an Infinity b4920, b40xx series, or b3 controller, in theInfinity view of the Continuum Explorer. A Calendar object, like other BACnet objects onthe Continuum system, is placed in both an Infinity Calendar class folder beneath the b4,b40xx series, or b3 controller, and in a BACnet Calendar class folder beneath itscorresponding b4, b40xx series, or b3 controller in the BACnet view.

Note: In the BACnet view, you may create a Calendar object on a third-party BACnetdevice, but not on an Andover Continuum BACnet device.

Note: Some BACnet controllers support a Schedule but do not support a Calendar.

Others support both objects. Infinity legacy (non b4 and b3) controllers supportSchedule objects, but not Calendar objects.




Adding or Removing a Calendar Entry

The Calendar editor's right-hand pane displays a yearly calendar on the Yearly View tab.The left-hand pane contains a Date List tree:

The Date List tree lists all established dates single days, ranges of days, and recurringdays and identifies them in the list with the following icons:

Single day

Range of days

Recurring days

Note: Dates listed in the Date List appear in light blue on the calendar. If you select aday in the Date List, it appears in yellow on the calendar.

The Present Value field displays the current value of the Calendar object.

Enter a description of the Calendar object in the Description field.

Adding and Removing a Single Day via Calendar Click — You may add a single dayto the Date List by clicking once on an individual day on the calendar. The single dayentry immediately appears in the Date List.



TAC 408

Note: When you add a day in this way, notice its entry is not named in the Date List. Toname it, right click its new Date List entry, and from the Calendar Entry dialog,enter a name in the Name field. (Or in the tree, you may simply click inside itsempty name field and enter a name the way you would for a file in MicrosoftWindows Explorer.)

Note: You may also use the yearly calendar to assign two or more individual (nonconsecutive) dates. Hold down the CTRL key, and click (highlight) the individualdays you wish to assign. Right click, and proceed as described, above.

You may also remove a day by clicking once on a single established "red" or "blue" dayon the calendar. When you do so, you are asked:

Do you want to remove all calendar entries that reference this date?

Click Yes to remove the date or No to keep it.

Adding Calendar Entries via Calendar Entry Dialog — Add a single day, range of days, or recurring days, using the Calendar Entry dialog. To add an entry:

1. Click the New Calendar Entry button, or right click an entry in the Date List, andselect New Calendar Entry.

The Calendar Entry dialog appears.

2. In the Entry Type section, select one of the following radio buttons.

DateRange of dates

Recurrence

Notice the calendar data fields on the right side of the dialog are different for eachselection.

3. Enter the desired information in the calendar data fields on the right side of thedialog. These fields are self-explanatory.

For range, enter a starting and ending date.

Note: You may also use the yearly calendar to assign a range of days. In the yearlyview, click and hold the mouse button on the first day of the range (for

example, February 15). Drag the cursor on the calendar to the last day of therange (for example, February 22). The range (February 15...22) is highlighted.Enter a name by editing its calendar entry in the Date List.

For recurrence, enter a recurring weekday for a particular month. For example, if youwere defining "Thanksgiving," you could choose Last, Thursday, and November.

4. In the Name field, enter a name or description of the day, range, or recurrence entry.This name appears for this entry in the Date List.

5. Click OK. The new entry is added to the Date List.




Editing or Removing an Entry via Date List — To edit an existing entry, right click theentry, and select Edit from the popup menu. The Calendar Entry dialog appears for thatentry. Modify the data as needed.

To remove an entry from the Date List tree, right click the entry, and select Remove fromthe popup menu. The entry is immediately removed from the tree and the calendar view.



TAC 410




Configuring

Loops

Overview

A Loop is a BACnet standard object that allows you to create a feedback system withoutmanually creating or editing Plain English code. The loop feedback system is comparableto cruise control for a car. Just as cruise control automatically adjusts variables to

maintain the desired speed, the loop object automatically adjusts input values to achievethe desired setpoint and remain at the setpoint indefinitely. The ultimate goal is for theinput to reach the setpoint in the shortest amount of time possible. It does so by using aPID (Proportional, Integral, and Derivative) control algorithm.

The controller obtains the value of the input when it polls the current value of the inputreference (sensor, valve, and so on.). Then, the controller uses the PID algorithm toadjust the input to come as close as possible to the setpoint. The result of the PIDalgorithm determines an output that is then assigned to the output reference, or an objectwhose values control such things as sensors and dampers. The controller continues toalter the value of the output to maintain the input value at the value of the setpoint.

The error, or the difference between the input value and the setpoint value, is used toadjust the output value. The PID algorithm uses the error's value to measure how muchthe loop should be adjusted. The Tuning tab gives you the opportunity to adjust thesevalues or to tune the loop to fit your particular preference.

You create a Loop-object feedback system using the Loop editor and its tabs. Using theGeneral tab, you can monitor and alter the current state of the loop. The Tuning tab alsocontains a dynamically updating graph that displays loop, output, input, and setpointvalues as they change over time. This tab is interactive because you can tune the loopand customize the graph to your liking.

This chapter presents the following topics:

• General Tab

• Tuning Tab

• What Is PID?

16



TAC 412

• Tuning the PID Loop

• Customizing the PID Graph

• Basic Alarms Tab and Advanced Alarms Tab

General Tab

The General tab allows you to view and/or alter the current state of the loop object.

Note: All output-reference, setpoint-reference, and input-reference values are referencesto objects that were originally created either as points on Andover Continuumcontrollers, or as BACnet objects on third-party BACnet controllers.




The following table describes the attributes on the General tab.


Description Enter up to 32 characters including spaces to describe the loop.

Units From the dropdown menu, select the type of units desired for theoutput value.

Present LoopValue

Displays the result of the most recent PID calculation. This valueis used to set the output reference object and the priority definedby the present pool priority.

Present OutputValue

Displays the present value of the output reference object. Thisvalue is usually equal to the present loop value. However, if theoutput reference object is commanded at a higher priority or disabled (out of service) then the present value of the outputmay have a different value.

Present LoopPriority

Specify the desired BACnet command priority of the Loop object.

Present OutputPriority

Displays the BACnet command priority of the object (outputreference) to which the loop is writing. This command priority isconfigured within the individual BACnet object, in its objecteditor.

Output Reference Select the object/attribute to which the loop writes.

Using the browse button, search for and select the object. Thenselect an object attribute, such as Value, from the dropdownmenu. The attributes that appear in the menu vary, according tothe object that is selected.

Note: The Index field is read-only and the user cannot alter thevalue. See also Index below.

Input Value Displays the current value of the input reference object

Input Reference Select the object from which the loop obtains the current value.

Using the browse button, search for and select the object. Then

select an attribute from the dropdown menu. The attributes thatappear in the menu vary, according to the object that is selected.

Index This field allows you to specify the element of a BACnet arrayproperty.

If you select an array as the input reference (PriorityArray fromthe dropdown menu) the Index field enables and allows you toreference a specific element of the array.

Specify the array element by selecting the up and down arrowsor by entering the desired array-element number.



TAC 414


Setpoint If you prefer to enter a specific setpoint value for this loop, selectthis radio button. When you select this button, the field enablesand the Setpoint Reference fields (see below) disable.

In this Setpoint field, you can only enter numeric values.Numbers with decimals are acceptable entries.

Setpoint Reference If you prefer instead to reference an object whose valuebecomes the loop's setpoint, select this radio button. When you

select this button, the fields enable and the Setpoint field (seeabove) disables.

Click the browse button, and search for and select the objectwhose property value become the setpoint. Use the dropdownmenu to select the type of property. The properties that appear in the menu vary, according to the object that is selected.

Index This field allows you to specify the element of a BACnet arrayproperty. If you select an array (the PriorityArray attribute fromthe dropdown menu) the Index field enables and allows you toreference a specific element of the array.

Specify the array element number by using the up and downarrows or by simply entering a number.

Update Interval Enter the time (in milliseconds) the PID loop should wait beforere-evaluating its output.

Note: Do not make this value too small because you want togive the environment a chance to react to the output.

If the loop updates the output too frequently, the equipment canburn out. Check the manufacturer's recommendations to avoidcausing harm to the equipment.

Out of Service Check this checkbox to indicate that the loop object is out of service and has lost communication with its attached device.

Putting the point out of service is a good way to test the pointand the functions that rely on it. You can simulate varioussituations by manually changing the value or reliability attributes.This allows you to see how associated functions react to thesechanges.





Status Provides information on the loop's condition. The condition canbe one of the following:

• InAlarm -- Indicates that the Event State attribute has avalue other than NORMAL.

• Overridden -- Indicates that a local device has manuallyoverridden the point.

• Fault -- Indicates that the Reliability property has a value

other than NoFaultDetected.• OutOfService -- Indicates that the point is disabled.

Reliability Provides an indication of whether or not the controller hasdetected a malfunction that might compromise the integrity of theloop's present value.

The attribute can read one of the following:

• NoFaultDetected -- Indicates that the present value isreliable and that no fault is detected.

• OpenLoop -- Indicates that the connection between thepoint and the device is providing a value resulting from an

open circuit.• UnReliableOther -- Indicates that the controller detects an

unreliable present value, and that none of the aboveconditions describes the nature of the problem.

More About an OpenLoop State – Here are some conditionsthat could cause an OpenLoop state: The Controlled_Variable_Reference or Manipulated_Variable_Reference properties reference an AnalogInput or AnalogOutput, where the Channel (Infinityproperty) is not configured. This causes the Out_Of_Serviceproperty for the AnalogInput or AnalogOutput to always have avalue of True, which in turn causes the Loop's Reliability

property to have a value of OpenLoop. • The Present Loop Value is different than the Present Output

Value, after the Loop updates the output value. This canoccur when the output value(Manipulated_Variable_Reference) is currently commandedby another process at a higher priority than that at which theLoop writes. This could be a common occurrence when theLoop is configured to write to the Present_Value property of an object that has a priority array, and the Loop is writing ata lower priority than something else.



TAC 416


• When the Loop is initially configured and saved, theReliablility property may initially be displayed as"OpenLoop", even though it is properly configured. If theeditor is refreshed (generally within a few seconds) theReliablity property should change to NoFaultDetected.

Note: The editor only shows the Priority Array attribute in the Input and Setpoint

Reference dropdown menus if the reference is an AnalogValue. The dropdownmenu also displays all attributes that are float values; therefore, it might showattributes that the controller does not support.

Tuning Tab

The Tuning tab contains all the PID (proportional, integral, derivative) loop variables. Italso contains a dynamically updating graph that displays loop, output, input, and setpointvalues as they change over time.

This tab is interactive. That is, you can tune the loop and customize the graph to your liking.

Before Version 1.73, Continuum users created Plain English programs to set the PIDgain constants and tune the loop. Now you can accomplish these tasks via the Tuningtab. (See also What Is PID? later in this chapter.)





Loop Value Check this checkbox to display the loop value on the graph.

Click the Loop Value hyperlink to bring up the GraphConfiguration dialog, where you can customize the graph's Loopplot properties.

Using the dialog's navigation tree, you can click Output, Input, or Setpoint to switch to those plot properties, respectively. ClickDisplay to show the graph's display properties.

The Loop Value field is read-only and cannot be changed.

See Customizing the PID Graph, later in this chapter.

Output Value Check this checkbox to display the output value on the graph.

Click the Output Value hyperlink to bring up the GraphConfiguration dialog, where you can customize the graph'sOutput plot properties.

Using the dialog's navigation tree, you can click Loop, Input, or Setpoint to switch to those plot properties, respectively. ClickDisplay to show the graph's display properties.

This field is read-only and cannot be changed. See Customizing

the PID Graph, later in this chapter.Input Value Check this checkbox to display the input value on the graph.

Click the Input Value hyperlink to bring up tthe GraphConfiguration dialog, where you can customize the graph's Inputplot properties.

Using the dialog's navigation tree, you can click Loop, Output, or Setpoint to switch to those plot properties, respectively. ClickDisplay to show the graph's display properties.

This field is read-only and cannot be changed. See Customizing the PID Graph, later in this chapter.

Setpoint Value Check this checkbox to display the setpoint value on the graph.

Click the Setpoint Value hyperlink to bring up the GraphConfiguration dialog, where you can customize the graph'sSetpoint plot properties.

Using the dialog's navigation tree, you can click Loop, Output, or Input to switch to those plot properties, respectively. ClickDisplay to show the graph's display properties.

This field is read-only and cannot be changed.

Note: In order to change the value of the setpoint, go to theGeneral tab and change the value. Select the Apply buttonto activate the value change.



TAC 418


Maximum LoopValue

Enter the maximum value that the PID algorithm can assign to theloop. If the output should never go above a certain value, set thelimit in this field.

Minimum LoopValue

Enter the minimum value that the PID algorithm can assign to theloop. If the output should never go below a certain value, set thelimit in this field.

Poll Frequency Specify the number of seconds the graph should wait before

polling the controller for the new setpoint and input values.

Sample Size Select the intervals of time for the X axis. The maximum samplesize is 10; the larger the sample size, the more points the graphdisplays.

Note: Non-default values that you select for Poll Frequency and Sample Size takeeffect immediately, as you manipulate a live graph in real time while the Loopeditor is open. Non-default values cannot be saved they revert back to the defaultvalues when you close the Loop editor because these attributes are technicallynot part of the Loop object. When you change these values, the Apply buttondoes not become selectable.

The Graph The graph displays the effects the PID algorithm has on the input,output, and setpoint values. The graph dynamically shows how

the values you assign to the proportional, integral, and derivativeconstants alter the value of the loop.

To start the graph, right click the graph and select Start from thepopup menu.

Double-click the graph (or right click the graph and selectMaximize from the popup menu) to maximize the graph into itsown separate window.

You can also customize the graph configuration by right clickingthe graph and selecting the Display from the popup menu.

Capturing the Graph: You may capture a screenshot of thecurrent graph (create a graphic file) by right clicking the graph

and selecting Save Screenshot. This feature makes it easy todistribute the graph to others and to illustrate documents.

See Customizing the PID Graph, later in this chapter.

Proportional Specify the value for the proportional constant in the Value fieldand select the type of units from the dropdown menu

Integral Specify the value for the integral constant in the Value field andselect the type of units from the dropdown menu.

Derivative Specify the value for the derivative constant in the Value field andselect the type of units from the dropdown menu.





Error This field displays the difference between the input and thesetpoint.

Last Error This field displays the previous difference between the input andthe setpoint.

Bias The bias is the amount of the initial value of the output reference.If the PID algorithm produces a value of X, then the final value of the loop will be X plus the bias. For example, if the valve starts at

10% open, as opposed to 0, you have to add that initial value (thebias) to the value of the loop.

Action Select one of the following from the dropdown menu.

• Direct — Select this when you want an increase in the outputvalue to cause an increase in the input value, and vice versa.For example, select this option if the valve must open in order to increase the temperature.

• Reverse — Select this when you want an increase in theoutput value to cause a decrease in the input value, and viceversa. For example, select this option if the valve must closein order to increase the temperature.

What Is PID?

Note: In order to tune a loop, you should already have some experience with PID andfeedback loops.

PID control refers to three types of control actions that are used in the process of modulating equipment, such as valves, dampers, and variable-speed devices. It isessentially a balancing act between the Proportional, Integral, and Derivative controls toreach the desired setpoint. These three types of controls are defined as follows:

• Proportional - Control based on how far the input is away from the setpoint.

• Integral - Control based on the average error over time. (The error is the

• difference between the input and the setpoint.)• Derivative - Control based on how quickly the input is approaching the setpoint.

PID control combines the three types of control actions, which improve control accuracyand lessens the time it takes for the input to reach the setpoint.

Note: The input is also referred to as the controlled variable because it is theenvironmental factor you want to control.

Proportional Control

Proportional control produces a control signal based on the difference between an actualcondition and a desired condition — for example, the difference between the actualtemperature and the setpoint. The controller sends a signal that is directly proportional tothis difference, or the error. (the difference between the input and the setpoint). Although



TAC 420

simple and fast, proportional action alone produces a small amount of error, or an"offset," which prevents the system from reaching the desired setpoint. The Proportionalcontrol algorithm is as follows:

Proportional = Kp * Err

where Kp is the Proportional Gain and Err is the error (the difference between the inputand the setpoint)

Proportional Integral (PI) Control

PI control sums the error over time, or takes the integral of the error. By adding the valueof the last error to the proportional signal, the control loop produces a control action over time. In turn, the current value moves closer to the setpoint value. Combining proportionaland integral actions reduces offset error but produces a different kind of error overshoot.Essentially, the integral action overcompensates, causing the value to go past thesetpoint. This is called the "overshoot."

Another limitation to the PI control is that the algorithm produces a problem called"integral windup." Integral windup occurs when the output and input reach their maximumvalues and cause a large error to exist. This persistent error causes the sum of errors tobecome very large, and this, in turn, requires a large error in the opposite direction tobring the sum back to zero. Integral windup is detrimental because the equipment isforced to stay at its extreme for long periods of time, which impacts comfort and results ina waste of energy. The PI algorithm is as follows:

PI = Ki * ∑Err δTime

where Ki is the Integral Gain, ∑Err is the sum of errors since the error became greater than the threshold, and δ Time is the change in error since the last PID update.

Proportional Integral Derivative (PID) Control

Derivative action provides an additional control action that anticipates the differencebetween the current and desired conditions. The derivative action significantly reducesovershoot by counteracting the result of the proportional and integral algorithm. Toreduce the overshoot, derivative action determines the rate of change of the error. Thecontroller then uses this derivative to pace the device, producing a more stable output.The PID algorithm is as follows:

Output = (Kp * Err) + ( Ki * ∑Err δTime) + (Kd * δErr / δTime) + Bias

where Output is the output of the controller, Kp is the Proportional Gain, Err is the error (the difference between the input and the setpoint), Ki is the Integral Gain, ∑Err is thesum of errors since the error became greater than the threshold, δ Time is the change inerror since the last PID update, Kd is the Derivative Gain, δ Err is the change in error since the last PID update, and the Bias is the offset adjustment parameter.




Tuning the PID Loop

The process of setting values to the Proportional, Integral, and Derivative (PID) gainconstants is called tuning the PID loop. (See Tuning Process below.)

Tuning configures a feedback loop so that the input value reaches the setpoint value inthe shortest amount of time possible. You perform this configuration by entering values inthe Loop editor's Tuning tab. The Tuning tab also includes a dynamic graph thatdisplays the realtime changes in the loop's values.

PID control tells the controller how much to adjust an output reference, such as a valve or damper setting, so that the setpoint value is reached in the shortest amount of timepossible. (See also Loop Tuning Hints later in this chapter.)

Note: To ensure a more effective result, it is recommended you test the loop beforestarting the actual tuning process. By testing the loop performance, you can avoidany problems that may arise when actually tuning the loop. Check the Out of Service checkbox on the General tab to test the loop without affecting the actualcomponents.

Tuning Process

Note: In order to tune a loop, you should already understand PID and have someexperience with feedback loops.

The most common method for tuning the loop is the process of trial and error — that is,tuning while observing the response to setpoint changes. After specifyingobjects/attributes for the Output, Input, and Setpoint sections on the General tab,perform the following procedure.

To tune a PID loop using the Loop editor, follow this procedure:

1. Modulate the output. That is, determine how often the controller should update theoutput. Enter a value in the Update Interval field on the General tab

2. Set the action of the output reference. Select either Direct or Reverse from theAction field's dropdown menu on the Tuning tab.

3. If you wish to enter an initial value for the output reference, insert the value in theBias field on the Tuning tab.

4. Enter the PID gain constants into the corresponding fields on the Tuning tab.

One way to ensure a steady control is to enter a value in the Proportional field andleave the Integral and Derivative values at 0. After you see the resulting outputchange on the graph and in the other fields on the Tuning tab, modify the integraland derivative gains until you achieve the result you want. Try entering the initialintegral value for the integral gain and reduce the value until you achieve a steadyloop. Do the same for the derivative value.

Note: The value of the proportional gain constant is usually 1.0 or below.



TAC 422

Loop Tuning Hints

Here are some general tips that might help you tune a loop:

• Eliminate the bias when the output is being ramped from the start point. The rampingacts as a slowly increasing bias.

• Eliminate the Derivative gain PID control loops that produce setpoint reset signals.For example, eliminate the derivative gain if a room temperature control loop resetsthe supply air temp setpoint or VAV flow setpoint. It is important to reset setpointssmoothly and slowly to reduce erratic secondary control responses.

• Some control loops cannot be accurately tuned by simply manipulating gain factors.There are other factors that influence the accuracy of control loops. Some of thesefactors are as follows:

o The controlled device (or output reference), such as a damper or a valve,must be sized properly.

o The difference between the controlled variable and the controlledmedium cannot be too extreme. For example, the control loop could becompromised if you are attempting to control a reheat coil for a 70-degree leaving air temp when the hot water supply temperature is 210degrees and the entering air temperature is 68 degrees.

o The sensor SPAN must be small enough to be sensitive to theapplication while no conditions fall outside the range's minimum and

maximum values.o The sensor position should be in a location that best represents the

average of the application. For example, duct temperature sensorsshould not be located close to heating coils to avoid heating by radiation.

Customizing the PID Graph

You can customize the "look and feel" of the graph displayed on the Tuning tab of theLoop editor to suit your own personal tastes. Specifically, using the Graph Configuration dialog, you can:

• Alter the display configuration

• Alter the plot configuration




Here are some examples of what a plotted graph looks like:



TAC 424

Copying a Graph Configuration

After customizing your graph, you can copy the graph configuration to another Loopobject. To do so, follow this procedure:

1. From the Tuning tab, right click the graph.

2. From the popup menu, select Copy then To.3. Choose the To option from the submenu.

4. Search for and select the Loop object to which you wish to copy the graph.

When you create a new Loop object, you can also copy a graph configuration from anexisting Loop object into the new Loop object. To do so, follow this procedure:

5. Create a new Loop object, and select the Tuning tab.

6. Right click the graph.

7. From the popup menu, select Copy, then From.

8. Search for and select the existing Loop object from which you want to copy a graph.

9. Search for and select the Loop object to which you wish to copy the graph.




Altering Display Configuration via Graph Configuration Dialog

To alter the graph's display properties, right click the graph, and select Display from thepopup menu. The Graph Configuration dialog for display appears.

The following table describes the attributes of the four major sections of the dialog.


Graph Properties In the Name field, enter up to 32 character (including spaces) todescribe the graph.

Enter the minimum and maximum values for the Y-axis in theMinimum and Maximum fields.

The Scroll Direction dropdown menu allows you to select thedirection from which the new value plots move on the graph — Right to left or Left to right.

Check the appropriate checkbox to display the following:

Display values on mouse over -- When this box is checked, youmay move your mouse cursor over a plot on the graph to displaya text tooltip that lists the current values for Loop, Output, Input,and Setpoint. Each entry appears in its designated color.

Display grid -- When this box is checked, the grid appears on thegraph. If the box is not checked, no grid appears.

Update y axis min and max values dynamically -- When thisbox is checked, the graph dynamically updates a range of valuesdisplayed on the Y axis, based on the minimum and maximumvalues currently plotted. To show all minimum/maximum values,check the "Display all min max values along the y axis" box.



TAC 426

Display notches along the x and y axis -- When this box ischecked, notch lines protrude on the outside of the X and Y axeswhere the grid lines meet the axis lines.

Display all min max values along the y axis -- When this box ischecked, the speciified minimum and maximum values (specifiedin Minimum and Maximum fields) appear on the Y axis. Thischeckbox is selectable only if the "Display notches along the xand y axis" box is checked.

Colors Customize the colors of the Background, Foreground, Axis,Text, and Grid by clicking the browse button next to thecorresponding field. Using the color-palette dialog, select thedesired color and click the OK. The color appears in the field.

X-Axis Properties Enter the X-axis label in the Name field.

Select the desired number of grid columns in the Columns fieldby clicking the up and down arrows or by entering the number manually.

Similarly, in the Label Interval field, choose the number of intervals between the labeled time increments on the X-axis. Clickthe up and down arrows to specify an amount or enter thenumber manually.

Y-Axis Properties Enter the Y-axis label in the Name field.

Select the desired number of grid rows in the Rows field byclicking the up and down arrows or by entering the number manually.

Similarly, in the Label Interval field, choose the number of intervals between the labeled time increments on the Y-axis. Clickthe up and down arrows to specify an amount or enter thenumber manually.




Altering Plot Configuration via Graph Configuration Dialog

To customize the graph for specific plots, bring up the Graph Configuration dialog inone of the following ways:

• On the Tuning tab, click the hyperlinked colored text of the plot you wish to configure:

Loop ValueOutput ValueInput ValueSetpoint Value

• Right click the graph, and select Plot Properties. The Graph Configuration dialogappears.

Depending on which plot you want to configure, select one of the following from thepopup menu:

Input ValueSetpoint ValueLoop ValueOutput Value

The Graph Configuration dialog for plots appears.

Using the navigational tree on the left-hand side of the dialog, you can expand Plot, andswitch from one plot configuration to another.



TAC 428

The following table describes the attributes of the four major sections of the dialog.


Plot Properties In the Label field, enter up to 32 characters (including spaces)to describe the plot.

In order to specify the minimum and maximum values for theplot check the appropriate checkbox. The Minimum andMaximum fields will enable and allow you to enter in the limits.

Check the Update this plots min and max valuesdynamically checkbox to automatically update the plot basedon the minimum and maximum values. This checkbox is onlyenabled if the Specify this plots min and max valuescheckbox is selected.

Line Properties Change the color of the line by clicking the browse button andthen selecting a specific color from the dialog. Click the OK button to finalize the change.

Assign a style to the line by selecting an option from thecorresponding dropdown menu.

Specify the width of the line by clicking the up and down arrowsor by entering the number manually.

Point Properties Change the color of the point by clicking the browse button andthen selecting a specific color from the dialog. Click the OK button to finalize the change.

Assign a style to the point by selecting an option from thecorresponding dropdown menu.

Specify the width of the point by clicking the up and downarrows or by entering the number manually.

Border Properties Change the color of the border by clicking the browse buttonand selecting a specific color from the dialog.

Specify the width of the border by clicking the up and downarrows or by entering the number manually.




Basic Alarms Tab and Advanced Alarms Tab


Note: This is enabled for some BACnet objects attached to third-party BACnet devices. Itis not currently supported on Andover Continuum BACnet controllers.

The information here determines when the alarm will go off, and what happens when itdoes. Information that determines what happens when the alarm goes off is built into theEventNotification object that you associate with this alarm. The EventNotification objectdefines how and to whom the alarm is broadcast.


Event State Displays the value of the To State attribute, which is set by thecontrol system. If you have set up this object to report alarms, thisattribute displays Normal when the object is not in an alarm stateand OffNormal when it is. If you have not set up the object toreport alarms, this attribute always displays NORMAL.



TAC 430


AcknowledgeReceived For

Displays the value of the Acknowledge Received For attribute.Displays ALARM, FAULT, or NORMAL if acknowledgementshave been received for reported alarms, faults, or return-to-normal events, respectively. These values display only if both of the following conditions are true:

• You have selected the report options for these events.

• The associated Event Notification object requires

acknowledgement for these events.COV Increment Specify a COV increment, or the minimum change in the present

value, for the object.

If the difference between the present value and the last presentvalue of the loop is greater then the COV increment, an alarm issent.

Error Limit Enter an error limit for the object. If the current error exceeds theset error limit, an alarm is sent.

Time Delay Enter a time delay in seconds.

The time delay postpones the alarm for the amount of time youspecify. For example, you may decide that the object value can

exceed or fall below its boundaries for 30 seconds before thealarm goes off. Using time delays cuts down on the number of active alarms and reduces both system traffic and operator responsibility.

Report In the Report section, you may select up to three report options:Alarm, Return to Normal, and Fault. When selected, theseoptions trigger the basic alarm in the following situations:

• The Alarm option triggers the basic alarm when the object'sEvent State changes to OffNormal.

• The Return To Normal option triggers the basic alarm whenthe object's Event State changes to Normal

• The Fault option triggers the basic alarm when a local device

detects a fault.





Notification Type From the dropdown menu, select a BACnet notification type. Thenotification type specifies whether the notification messagebecomes an alarm message, an event message, or a message of event acknowledgement.

AlmNotification — Defines the event as type alarm, appearing inthe Active Alarm View when the event occurs.

EvtNotification — Defines the event as type event, appearing in

Active Alarm View when the event occurs.

Acks — Defines the event as type ack-notification, appearing inthe Active Alarm View when the event occurs.

Event Notification Select an Event Notification object by clicking the browse button.The Browse dialog appears. Locate the Event Notification objectthat you want. Select it and click the Select button. This will insertthe correct path and Event Notification name into the Notificationclass field.

The Advanced Alarms tab is disabled for BACnet objects (b4, bCX1, b3, and third-party). They are supported for Infinity (non-BACnet) objects only. See the appropriateInfinity object editor.



TAC 432




Configuring

Trend Logs

Overview

A TrendLog is an object that allows you to configure the logging of data from otherBACnet object property. You can log data on an object/property using one of thesemethods:

• Change of values (COV) — When the object/property value is changed, theTrendLog is notified and another entry is added to the log. (See the General tab onthe next page.)

• Periodic polling of data — Entries are logged via regular continuous polling of an

object/property. (See the General tab.)

Each TrendLog object has an internal buffer, stored on the controller, whereby theTrendLog acquires data and stores it in its buffer. (See also the Data tab later in thischapter.) When entries are added to the log, workstations can be automatically notified ofnew entries, and workstations can automatically download them to their databases. (Seealso the Basic Alarms tab later in this chapter.)

The records in a TrendLog object can also be run as a trend report, displayed in theReportViewer, after the TrendLog object is specified in the Report editor. (See Chapter11, Configuring Reports .) It can be launched via the View Report button on the Data tab.

17



TAC 434

General Tab

On the General tab, configure basic information for this TrendLog. You also select eitherof the following logging methods:

• Change of Value (COV)

• Periodic poll

Guidelines for Choosing a Logging Method

Here are some guidelines for choosing a logging method. (See also the attributedescriptions in the table below.)

• Before choosing a method, perform an assessment of how the data will be changing,how the data will be used, and how much memory each method would use for anygiven application.

• COV is generally more accurate and can be more memory-efficient, depending onhow often the logged object reports a COV. BACnet objects (AnalogInput,AnalogOutput, AnalogValue) support a property called COV Increment. You mayadjust this value for logged objects, thereby allowing you to control how frequently aCOV is reported.

• For frequently changing values, periodic polling provides more predictable results. Ifthe COV Increment in the logged object is set to 0 (the default) room temperature

readings could produce thousands of records per day. Without changing the COVIncrement of the input, periodic polling (for example, every 30 minutes - 48 recordsper day) is more efficient.

Note: Be aware that the Threshold attribute (Conversions tab of InfinityInput objecteditor – Chapter 13) and the COV Increment property (Basic Alarms tab ofthe AnalogInput, AnalogOutput, and AnalogValue editors – Chapter 14) havetwo different effects. Setting the Threshold higher (for example, degreesFahrenheit) only affects the activity of the present value. It is the setting of theCOV Increment higher that reduces the number of COV events in the loggedobject.

• COV is generally a better choice for binary outputs that do not change their valuesmore than a few times per day. With periodic polling, you may not know when the

output value changes. For example, if you set polling to occur every 30 minutes, youknow only that the output is polled every 30 minutes -- that 48 records are storedeach day, even if their value changes, for example, only three times. With COV, younot only have three records stored but also know precisely when those records werestored (precisely when the values changed).

• Changing the COV Increment of the logged object (as opposed to changing the COVincrement of the TrendLog) is generally better for reducing network traffic. Thesystem filters events at the source, rather than at the TrendLog object, which mayreside on an external controller.




The following table describes the attributes on the General tab.


Description Enter a description of the TrendLog you are creating.

Enabled/Disabled Select Enabled to activate the TrendLog so that it logs entries,or Disabled, to disable all logging.

While the TrendLog is an enabled state, some TrendLogproperties cannot be modified (for example, Log Buffer Size).

Logged Object Click the browse button to search for and attach a BACnetobject whose property values you wish to log. The path of theobject appears in the field.

Logged Property From the dropdown menu, select the logged object's propertyfor which you want to create log entries, using the desiredlogging method. (See below.)

Note: The properties listed in this menu change, depending onwhich type of object you select, because properties differfrom object to object.



TAC 436


Index The index dropdown menu allows you to select an arrayelement of a BACnet array property. The integer represents thearray element (and a BACnet command priority) whose valuesyou want to log. (This field is not selectable if an array propertyis not designated as the logged property.)

Log Buffer Size This field indicates the maximum number of entries (or records)that you can store in a log. You may change this number only

when the TrendLog is disabled. Click Apply, and re-enable theTrendLog after changing the number, to reactivate logging. Thedefault is 10.

Some BACnet controllers may implement a limit on thisnumber. If you receive an error when changing the buffer size,the number may exceed the limit set by the controller. In thiscase, either lower the number in this field or create theTrendLog externally, on another BACnet device.

Note: While the TrendLog is enabled, you cannot change thisproperty.

Stop Logging WhenBuffer is Full

Check this checkbox if you want to disable logging when thisTrendLog's buffer gets full (when it reaches its maximum Log

Buffer Size.)To begin logging again, do one of the following, then re-enablethe log:

• Remove the check here.

• Increase the Log Buffer Size.

• Clear the content of the log buffer. (See the Data tab.)

Change of Value(COV)

See also Guidelines for Choosing a Logging Method, above.

If you want to log an entry when an object/property's valuechanges, select this

radio button. The controller on which this TrendLog runs usesCOV interval and increment values to subscribe to COVs onother controllers.

COV Resubscription Interval — The interval, in seconds, atwhich the COV subscriptions to other controllers are refreshed.The default is 320 seconds.

COV Increment — The increment in a value change (thenumber of units, for example, degrees) that must increase ordecrease before a COV is triggered. An increment of 1 appearsinitially in this field. When the Default checkbox is checked, itdefaults to whatever is appropriate for the BACnet controller —





usually 0 or NULL.

Note: The values in these fields cannot be changed if thisTrendLog resides on an Andover Continuum BACnetcontroller, only on some third-party BACnet controllers.

Periodic Poll See also Guidelines for Choosing a Logging Method, above.

If you want to log entries based on periodic polling of theobject/property, select this radio button.

Log Interval — Enter the frequency at which you want theTrendLog to request the value — the frequency of days, hours,minutes, seconds, and hundredths of seconds. For example, ifyou want the TrendLog to poll the value every 5 seconds, enter(or use the up/down arrow buttons to select) 05s in the secondsfield, and leave all other fields at 0.

Enable Start Time If you want logging to begin at a specific day and time, checkthis checkbox, select a day from the dropdown menu, and usethe up/down arrow buttons to select a time. To continue loggingindefinitely, without stopping, do not check the Enable Stop

Time checkbox.Enable Stop Time If you want logging to stop at a specific day and time, check this

checkbox and select a day from the dropdown menu, and usethe up/down arrow buttons to select a time. If logging is alreadyunderway and you do not need a start time, but do want itdisabled at a specific time, do not check the Enable Start Time checkbox.

Note: The Timed Activation settings are not based on recurring intervals. That is, youcannot set start/stop times for each day. They simply designate one period oftime, one begin time and one end time.

Data Tab

The Data tab displays the current entries in this TrendLog, as well as general informationabout the log. It also allows you to filter the logs that are displayed.



TAC 438


Record Count Displays the current number of records in the controller's internalbuffer for this TrendLog.

Record CountSince Creation

Displays the number of records that have been logged since thisTrendLog was created.

FilterLast

Check the Filter checkbox when you want to limit the number ofrecords manually downloaded and displayed in the record list (or"grid") on the lower half of this Data tab.

In the Last field, enter (or use the up/down arrows to select) thenumber of records to download and display in the list.

Important: Do not enter a number greater than 4000. The mostrecent records in a buffer are downloaded to a workstation'sdatabase, and the number of records that can be manuallydownloaded is capped at 4000. Therefore, this means that if abuffer has more than 4000 records, the least recent recordsresiding in the buffer (above the 4000 record count) are neverdownloaded.

Refresh Grid Click this button to refresh the list of records and display the mostrecent object/property values being logged.





Clear Records Click this button to remove all records in the TrendLog.

View Report Click this button to launch a graphical Trend report in theReportViewer. The report is a snapshot of contents of theTrendLog buffer. See also Reports and the Report Editor inChapter 11.

List of records The table in the lower half of the Data tab displays recordscurrently residing in the TrendLog's buffer.

TimeStamp column displays the date and time the record waslogged.

StatusFlags column displays a BACnet flag (InAlarm, Fault,Overridden, or Out_Of_Service). These are the logged object'sstatus flags, and they are not always available since a controllermay or may not associate these flags with the log record. Theflags appear here when they are set (True). For example, if all theflags are False, then the column is empty, even though theStatus_Flags property value is stored as part of that record.

LogDatum column displays the actual status message that islogged. It could be any BACnet data type, although mostcontrollers only support a few basic ones. LogDatum might alsocontain messages like "log-disabled," "failure," error messages,and so on.

For more information on status flags and LogDatum, please seethe BACnet Standard.



TAC 440

Extended Logging Tab

This tab displays information about the last time this TrendLog's records weredownloaded from its controller to a workstation database. The values displayed here arespecific to automatically downloaded records; manual downloads (via the Data tab) donot update this information.

Specifically:

• Last Download Time — Lists the day and time of the last time a workstationdownloaded records from the controller the database.

• Last CyberStation to Log Data — Lists the name of the workstation that performed

the last download.• Number of records downloaded — Lists the total number of records that the

workstation downloaded during the last download.




Basic Alarms Tab

You may configure the way that workstations receive notifications — as well as whichworkstations to notify — when new records are added to this TrendLog, so that the datais downloaded to each workstation's database.

There are two methods for reporting TrendLog data to workstations:

• Intrinsic notification — You configure TrendLog notifications using the attributes onthis tab, as well as the EventNotification editor, where you specify which workstationsto notify. (Please see the table of attribute descriptions below.)

Note: Intrinsic notifications are supported only on some third-party BACnetcontrollers. They are not supported on Andover Continuum BACnet controllers.If intrinsic notifications are not supported in this device, the attributes on thistab are disabled and unselectable.

• Algorithmic notification — You configure TrendLog notifications externally (outsidethe TrendLog editor) using the EventEnrollment editor. (Please see the procedure forconfiguring algorithmic notifications below.)

Note: Algorithmic notifications are supported on Andover Continuum BACnetcontrollers.



TAC 442


Event Notification Using the browse button, search for and attach anEventNotification object to this TrendLog.

This EventNotification specifies the workstation recipients tobe notified when new records are added to this TrendLog.(Please see the Delivery tab of the EventNotification editor.)

Notification Type From the dropdown menu, select a notification type. Thenotification type specifies whether the notification message

becomes an alarm message or an event message in theActive Alarm View.

• AlmNotification — Defines the event as type alarm,appearing in the Active Alarm View when the eventoccurs.

• EvtNotification — Defines the event as type event,appearing in Active Alarm View when the event occurs.

• Acks — Defines the event as type ack-notification,appearing in the Active Alarm View when the eventoccurs.

Note: Choosing AlmNotification or EvtNotification produces the same result. Acks has no function whenit is applied to TrendLogs, and it should be ignored.

Notification Threshold Enter the number of new records that must accumulate in theTrendLog before the workstations are notified. When new-record count reaches this number, a notification is sent.

New Records Displays the number of new records that have been added tothe TrendLog.





Last Notify Record

Previous Notify Record

Current Notify Record

Depending on which revision of the BACnet Standard issupported by the device, this tab displays either:

Last Notify Record

or:

Previous Notify Record

Current Notify Record

With the latest (2004) revision, Last Notify Record isdisplayed. With the previous (2001) revision, Previous NotifyRecord and Current Notify Record are displayed.

Last Notify Record displays the number of the last recordabout which workstations were notified. The record number isthe last record received in the notification. For example, if thelast record was the ninety-ninth in a series of records, therecord number would be 99.

Previous Notify Record and Current Notify Record displaytimestamps, whereby the date/time becomes the actualidentify of the record. Current Notify Record is the most

recent record received in the notification, and PreviousNotify Record is the last record (the one preceding thecurrent record) received in the notification.

To Normal / BufferReady Events

Check the Buffer Ready Event Enabled checkbox to enablethe delivery of notifications for this TrendLog. For intrinsicnotifications, this box must be checked so that workstationsreceive notifications according to the threshold and otherconfiguration settings.

Note: This is enabled only for third-party controllers thatsupport intrinsic notifications.

Active Event State is ready-only. When it is checked itsignifies the event state is in a Normal (Return To Normal)

state.

Last Notification Time is a read-only field that displays thedate/time the notification was delivered.

Notification Acknowledged is read-only. When it ischecked, it signifies that acknowledgements have beenreceived for return-to-normal events.



TAC 444


To Fault / COV FailureEvents

Check the COV Failure Event Enabled checkbox to send anotification if there is a failure with the COV subscription. This

is used when Change Of Value has been selected as thelogging method. (See the General tab.)

Note: This is enabled only for third-party controllers thatsupport intrinsic notifications.

Active Event State is ready-only. When it is checked it

signifies the event state is in a Fault (To Fault) state.

Last Notification Time is a read-only field that displays thedate/time a failure notification was delivered.

Notification Acknowledged is read-only. When it ischecked, it signifies that acknowledgements have beenreceived for the failure events.

Configuring Algorithmic Notifications

To configure external, algorithmic notification, perform the following procedure, using theEventEnrollment, EventNotification, and Device editors.

1. Create a TrendLog for which you want to configure an algorithmic notification.(Please see the other TrendLog editor help topics.)

2. On the General tab of the EventEnrollment editor, in the Event Notification field, clickthe browse button, and search for and attach an EventNotification object. (SeeChapter 14.)

3. On the General tab of the EventEnrollment editor, in the Object field, click the browsebutton, and search for and attach the TrendLog object whose records you want toreport to workstations, via the attached EventNotification object.

When you attach a TrendLog object, the following fields are automatically configured

• LogBuffer is entered in the Event Property field. LogBuffer represents the listof records displayed in the Data tab in the TrendLog editor.

•

Buffer Ready is entered in the Event Type field.• Return to Normal is checked in the Send section.

4. On the General tab of the EventEnrollment editor, from the Notification Typedropdown menu, select a type.

Note: This number serves the same purpose as the Notification Type field in theTrendLog editor (intrinsic method). See the description in the tab-attributestable above or in the General tab of the EventEnrollment editor.

5. On the Algorithms tab of the EventEnrollment editor, enter the number of newrecords that must accumulate in the attached TrendLog before the workstations arenotified. When new-record count reaches this number, a notification is sent. When




Buffer Ready is the Event Type, only one field, Notification Threshold, appears onthis tab.

Note: This number serves the same purpose as the Notification Threshold field inthe TrendLog editor (intrinsic method).

6. On the Delivery tab of the EventNotification editor, specify the workstations to benotified when new records are added to the attached TrendLog.

Note: Recipient workstations listed on the Delivery tab must be up and running inorder for records to get delivered to the database. If all workstations are

CyberStations, then one CyberStation must receive the information.See Chapter 10.

7. On the Preferences tab of the Device editor for each workstation, ensure thatpreference 21, Download Extended Log data from controllers on the LAN, is setto True.

8. For this device, perform a Send to -> Database operation.

Note: Failure to perform this step will prevent Continuum from downloadingTrendLog records.

9. During the process, in each editor, be sure to click Apply and/or OK to save yourwork.

See Chapter 14 for more information on the EventEnrollment and Device editors. SeeChapter 10 for more information on the EventNotification editor.



TAC 446




Configuring

Areas andDoors

Configuring Andover Continuum for Security and AccessControl

Areas and doors, with personnel, are the central elements of security and access controlin the Andover Continuum system. This chapter provides an overview of access control inyour Andover Continuum system. It also provides detailed information for configuringareas and doors in CyberStation, and for using two important access-control features,area lockdown and controller condition levels. Chapter 19 provides detailed informationabout creating and managing personnel information in CyberStation.

Key Terms for Access Control

Access Validation The process of checking conditions that must be met before aperson is allowed into an area. Access validation conditionsinclude, but are not limited to:

• Valid site number on the access card• Valid card number

• Valid personal identification number (PIN) for keypad entry

• Schedules that determine when doors can unlock and for whom

18



448 TAC

Anti-PassbackViolation

There are two types of Anti-Passback violations: area based andtime based:

• Area-based violations occur when personnel attempt accessfrom a non-adjacent area. This could occur if the persontailgated into an area. Adjacent Area objects have at leastone common door in their respective lists. As people movethrough areas, CyberStation keeps track of the last areaentered by each person. A person causes a violation when heor she tries to use a door that isn ’t in the list of the last known

area associated with the person’s card or key code.• The system can be configured to prevent the same card or

access code from being used more than once within a pre-determined time to enter the same area. A time-based anti-passback violation is an attempt to use the card or code twicebefore the anti-passback time configured in the door settingsexpires.

Clearance Level A value assigned in a Personnel object that determines whether aperson can access an area based on the condition level in effectfor the area. You can assign the same clearance level to all areasto which the person is allowed access, or you can assign differentvalues to different areas for the person.

For more information about clearance levels, see “PersonnelClearance Levels and Controller Condition Levels” in Chapter 19,Personnel .

Condition Level(not available for allcontrollers)

A controller variable that establishes the security alert level(sometimes called the “threat level”) in effect at doors in areasmanaged by the controller. The value of this variable is comparedto the clearance level for a person seeking access to determinewhether access is permitted. Clearance level is defined inPersonnel objects.

Executive Privilege(not available for allcontrollers)

An attribute you can select in a Personnel object to enable theperson to enter or exit areas to which he or she is assigned whenthose areas are in the Lockdown state.

Global ConditionLevel(not available for allcontrollers)

A CyberStation feature that enables you to send a new ConditionLevel value to all controllers that support the Condition Levelvariable. This changes the condition level at all the controllers.

Invalid Attempt An attempt to access an area by a person who is:

• Not authorized to enter the area

• Not authorized by schedule (for example, not authorized to bein the facility at night or on weekends)

• Not in the controller or CyberStation database




Lockdown(not available for allcontrollers)

The state in which doors to an area are locked, and remainlocked, until the Lockdown state is cleared. In the Lockdownstate, only personnel who are assigned executive privilegeaccess can enter or exit areas to which they have access. Thisfeature helps you quickly control area access in an emergency.

Passback The use of an authorized card by more than one person to gainaccess through a controlled door. For example, the card owner uses the card to gain access, and then "passes back" the card toanother person who can use the card to gain access through this

or another door.

Request-to-Exit(RTE) Device

A device, such as a pushbar, motion detector, or button, that isused instead of a card reader or keypad to pass through a door.

Supervised Input An input on a controller or expansion unit that monitors theresistance of the device attached to it. If the wiring is tamperedwith, the resistance of the circuit changes. This change inresistance causes the switch to go into a Trouble state. InCyberStation, you can configure Trouble conditions to trigger alarms.

Tailgating The practice of following another person into an area withoutswiping a card or entering an access code. If an individual hastailgated into an area, the system does not have an accurate

record of the individual’s location or of the number of occupants inan area.

About Areas, Doors, and Personnel

An area is a space that is accessed only by passing through an access control device,such as a card reader or keypad. An area can be accessed through one or more doors.

A door is a portal controlled by an access control device, leading to a specific area. Eachdoor becomes part of two different areas, one on each side. One or both sides can becontrolled by access control devices.

Personnel are the people in your facility who require access to various areas. APersonnel object is a CyberStation object that contains access control information,including access card data, area assignments, and other information, for one person.(Personnel objects can also contain other data, such as employee information,photograph, and personal information.) The controllers use the information in a Personnelobject to determine whether the person is allowed access.

When you configure a Door object, you assign each of its access control devices to anarea. The door name is then included in the Doors to Area tab in the Area editor for that Area object, as shown in the following illustration.



450 TAC

When you create Personnel objects, you assign the areas to which each person hasaccess. The Personnel object is then included in the People with access tab in the Areaeditor, as shown in the following illustration.




The following diagram is an example of how areas and doors can be defined andcontrolled.

Card Reader

Lab

Outside

Door 2

Office

Door 3

Lobby

Door 1

Request-to-Exit

Keypad

Glass BreakDetector

Motion

Detector

Motion

Detector

Door 4

Card Reader

Lab

Outside

Door 2

Office

Door 3

Lobby

Door 1

Request-to-Exit

Keypad

Glass BreakDetector

Motion

Detector

Motion

Detector

Door 4

In this example, Door 2 has both an entry reader and an exit reader. Personnel mustpresent their access cards to enter and exit the area labeled Lab. They can enter theOffice area through Door 3 by typing a code at a keypad. They can exit the Office area tothe Lobby area through Door 3 without using a card or keypad entry. They can also exitthe Office area through Door 4, which has a Request-to-Exit device.

Sequence for Creating Access Control Objects

Configure access control objects in the following order.

1. Create Area objects.2. Create Door objects, and associate each Door object with an Area object.

3. Create Personnel objects, and assign them to the Area objects to which they areallowed access.

When you finish, you have Area, Door, and Personnel objects that work together to checkwhich personnel can access which areas:

• Each Area object has a list of Door objects and a list of authorized personnel.

• Each Door object is configured with an entry reader and exit reader (optional) thatassociates each reader with one Area object. From the Door object, you can seewhich person was the last to go through.



452 TAC

• Each Personnel object has a list of Area objects to which the person is allowedaccess.

Creating an Area Object

The following procedure describes how to create an Area object.

1. In Continuum Explorer, right click the folder where you want to store your areas,select New, and then select Area from the popup menu.

2. Enter the area name, and click the Create button.

3. In the General tab of the Area editor, enter a description of the area.

4. If you want to assign a SecurityLevel object to the area, select the SecurityLevel tab,and then select a SecurityLevel object.

5. Click OK.

You can now assign doors and personnel to this Area object.

Creating a Door Object

The following sections describe how to configure a Door object using the Door editor tospecify schedule, area, and other information to control movement of people through thedoor.

The Entry Status and Exit Status tabs show read-only data on such details as lastperson admitted, time admitted, last invalid person, and entry count.

A door can provide access to two different areas (the areas on either side of the door).When you configure a door, you assign areas to it. The door name automatically appearsin the Doors to Area tab of those Area objects

Door objects are always created in the controller to which the door sensors, access cardreaders and keypads are wired. The exact configuration details for a Door editor dependon the model of the controller or IOU module to which your access control devices arewired.

1. In Continuum Explorer, right click the controller where you want to create the door,select New, and then select Door from the popup menu.

2. Enter the door name, and click the Create button.

3. Refer to the following sections to enter and save the appropriate settings in the Door editor.

Data that Defines a Door Object

You need to provide the following information when you configure a Door object:

• Site codes and format information for access control card sets

• IOU, channel and area information for entry and exit card reader and keypad inputs

• Type of validation (card, site, PIN, etc.)

• Channel numbers for the following Door outputs and inputs

o Door lock output




o Alarm output (optional)

o Exit request input (optional)

o Door switch input (optional)

o Bond sensor input (optional) (AC-1 Plus)

o ADA Input (optional) (AC-1 Plus)

o ADA Exit Request (optional) (AC-1 Plus)

• The schedules used to lock and unlock doors (optional)

• The InfinityNumeric objects that those schedules turn on and off (optional)

General Tab – Door Editor

The General tab lets you enter and monitor basic information about the door.

Description Enter up to 32 characters including spaces to describe this door.

A good description can help others realize the door's significance andphysically locate it and its access control equipment.

Door Lock Displays whether the door is locked or unlocked.

You can also lock or unlock the door by selecting Locked or Unlocked from the dropdown menu.

Changing this setting has no effect if the Lockdown state is present.Door Switch

Displays whether the door has been open, closed or tampered with.

The Door Switch is a supervisory input from the door you are assigning tothe controller. The field displays Open, Closed or Trouble. Trouble indicates that a problem, such as a cut wire or a shorted wire, is present atthe door switch.

Door State Select Disabled or Enabled.

Disabled means that no personnel access is allowed through the door.Enabled means valid access is permitted to authorized personnel.

OperatingMode

Not implemented in this version.



454 TAC

Card Formats Tab – Door Editor

Use the Card Formats tab to enter information about your access cards, and if needed,your keypad.

Note: For more information on the use of multiple custom formats with specificcontrollers, see Appendix E.

Site Codes Enter up to four site codes that are valid at this door.

If communication problems prevent the door from communicating withthe device controller or the access server that manages accesscontrol information in your network to validate individual cardnumbers, you can configure the door to allow access with a valid sitecode. You specify these settings on the Entry Reader and ExitReader tabs.

General Code Enter the keypad code that allows personnel access through aspecific door. Any personnel who know this general code will beallowed access through the door.

Arm Code Not implemented in this release.

Card Format Click either Wiegand or ABA.

ABA Formats Select either ABA Format 2 or Custom.

This format must match the card format used by the personnel.

Note: Andover Continuum supports custom ABA cards. Each custom ABA format must be defined as a special InfinityString object.See Appendix E.




WiegandFormats

Select the card format of the cards used by your personnel.

Channels Tab – Door Editor

Use the Channels tab to specify information about the access control hardware. ADA(Alternate Door Access) options allow you to configure a door to accommodate disabledpersons by allowing for longer than usual door unlock and open periods. A controller thatsupports these features, such as the AC-1 Plus, is required.

Door Output Channel Displays the channel number to which the door lock is wired.

For ACX 700 controllers, the value of this attribute dependson how the strike controlling the door has been wired to thecontroller or the expansion units. If one expansion unit hasbeen used with the 700, its Door Output Channel is 4. If twoexpansion units have been used, the second 190 Door Output Channel is 5.

On an AC-1 module the Door Output Channel is 1.

The door output relay can be a normally open (NO) or normally closed (NC) device.

Invert Click this checkbox to invert the meanings of Locked and

Unlocked.

Door Strike Seconds Enter the number of seconds the door is to remain unlockedafter a valid access.

Door Ajar Seconds Enter the number of seconds, 0 to 255, that you want thedoor to be ajar after the Door Strike Seconds have elapsed.

Forced Entry Delay Enter the number of seconds, 0 to 255, that you want to delaythe delivery of forced-entry alarms/events that are caused bynon-forced-entry "door bounce."

ADA Output Channel Enter the number of the ADA output channel number to whichan electronic door opener is wired.

You designate ADA status for individual personnel in thePersonnel object for each person who requires it.

ADA Output StrikeSeconds

Enter the number of seconds you want the door to remainunlocked after a valid access by personnel with disabilities.

ADA Door Ajar Seconds

Enter the number of seconds, 0 to 255, the door can be ajar after the ADA Output Strike Seconds have elapsed.



456 TAC

Alarm Output Channel Enter the channel number to which the alarm is wired if aflashing or beeping alarm for the door has been installed.

Channel 9 on an ACX 781 controller is a spare channel.Connect it to a light or some other signaling device physicallynear the door. In the event of an alarm, this channel will beactivated.

Use Channel 2 (Auxiliary) for alarm output on an AC-1.

Alarm Relay Seconds Enter the number of seconds the alarm output channel

remains energized when a Door attribute goes into alarm.

Exit Request InputChannel

Enter the channel number as it is marked on the controller.Every input connection area (channel) on every type of controller is numbered.

The Exit Request Input for an AC-1 is Channel 3.

Exit Request InputResistor Type

Select a resistor type (10K ohms) from the dropdown list.

Unlock on ExitRequest

Check this checkbox if you want to unlock the door every timean exit request occurs. Otherwise, clear the checkbox.

Note: If the door is in the Lockdown state, all requests to exitare ignored, even if this option is selected.

Door Switch InputChannel

Enter the channel number to which the door switch is wired.The door switch input channel monitors whether the door isopen or closed.

Every input connection area (channel) on every type of controller is numbered. Enter the channel number as it ismarked on the controller.

The Door Switch Input for an AC-1 is Channel 2.

Door Switch InputResistor Type

Select a resistor type from the dropdown list.

Relock upon Door

Closure

Check this checkbox to lock the door 1 second after it is

closed. If this checkbox is not checked, the door is locked 1second after the door switch is opened.

Bond Sensor InputChannel

Enter the channel number to which the bond sensor is wired.The bond sensor determines the physical latch position.

Every input connection area (channel) on every type of controller is numbered. Enter the channel number as it ismarked on the controller.

Bond Sensor InputResistor Type

Select a resistor type from the dropdown list.




ADA Exit RequestInput Channel

Enter the channel number to which the ADA Exit RequestInput is wired. The ADA Exit Request Input requests that thedoor be opened — when the request is transmitted thesystem presumes that the door is unlocked — to allow exitfrom a restricted area for a disabled person.

Every input connector area (channel) on every type of controller is numbered Enter the channel number as itappears on the controller.

ADA Exit RequestInput Resistor Type

Select a supervised input connection scheme from thedropdown list.

ADA Input Channel Enter the channel number to which the ADA Input is wired.

The ADA input requests that the door be opened — when therequest is transmitted the system presumes that the door isunlocked — providing a disabled person with entrance to arestricted area.

Every input connector area (channel) on every type of controller is numbered. Enter the channel number as itappears on the controller.

ADA Input Resistor Type

Select a supervised input connection scheme from thedropdown list. See the following sections for more information

about supervised inputs.

Supervised Input and Switch Types

If the wiring is tampered with, the resistance of the circuit changes. This change inresistance causes the switch to go into a Trouble state, which can cause the door to gointo an alarm condition. You should attach all supervised inputs to a Trouble alarm. Thenormal state of the switch is the state the switch is in when the door is closed.

All ACX700 / 780 controller series inputs are supervised inputs. ACX 57xx seriescontrollers also have supervised inputs. All inputs on an AC-1 are supervised inputs.



458 TAC

The table below summarizes the selections in the dropdown menus in these fields basedupon your switch configuration. Wiring configurations for each switch type are shown onthe following page.

Supervised Input Type Switch Type

NOSeries Normally-open switch with a resistor in series.

NOParallel Normally-open switch with a resistor in parallel.

NOSerPar Normally-open switch with a resistor in parallel andan added resistor in series.

NCSeries Normally-closed switch with a resistor in series.

NCParallel Normally-closed switch with a resistor in parallel.

NCSerPar Normally-closed switch with a resistor in parallel andan added resistor in series.

The table below summarizes the ACX781 door switch configuration options.

Supervised Inputs Controller and Expansion Unit

1 - 8 700 Series Inputs

9 or 10 First Expansion Unit Inputs

11 or 12 Second Expansion Unit Inputs

1 - 32 780/781 Controller Inputs




NC Series

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistor

10 KΩ

Sensor Switch

PositionResistanceValue

Value

Closed Closed 10 K Off

Open Open Infinite On

Shorted Zero K Trouble

Wire cut Infinite On

NC Parallel

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistor

10 KΩ

Sensor SwitchPosition

ResistanceValue

Value

Closed Closed Zero K Off

Open Open 10 K On

Shorted Zero K Off

Wire cut Infinite Trouble

NC Series and Parallel

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistors

10 KΩ

Sensor SwitchPosition

ResistanceValue

Value

Closed Closed 5 K Off

Open Open 10 K On



NO Series

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistor

10 KΩ

Sensor Switch


Value

Closed Open Infinite Off Open Closed 10 K On


Wire cut Infinite On

No Parallel

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistor

10 KΩ

Sensor Switch


Value

Closed Open 10K Off

Open Closed Zero K On

Shorted Zero K On


NO Series and Parallel

AUX

or

DOOR

or

REX

RET

Contact

Closure

External

Resistors

10 KΩ

Sensor Switch


Value

Closed Open 10K Off

Open Closed 5 K On





TAC 460

Options Tab – Door Editor

In the Options tab, you specify schedules to lock and unlock the door. You also selectthe types of access events sent from the controller to a CyberStation workstation for logging and viewing.

Note: If the door is in the Lockdown state, all schedules for locking and unlocking areignored. The schedules resume when the Lockdown state is cleared.

Door Force LockSchedule

Browse for and select an InfinityNumeric point controlled bythe schedule if you want to control this door with the following

conditions:

• When the schedule is on, the door is locked but access ispermitted to all personnel by card swipe and/or keypadentry. (Allow use of door.)

• When the schedule is off, the door is locked and cardreader and keypad access is denied to all personnel. (Noaccess through the door)

Door Force UnlockSchedule

Browse for and select an InfinityNumeric point controlled bythe schedule if you want to control this door with the followingconditions:

• When the schedule is on, the door is unlocked.

CyberStation ignores this door and any other schedulesattached on the Entry Reader and/or Exit Reader tabs of the Door editor.

• When the schedule is off, the door is locked but access ispermitted to all personnel by card swipe and/or keypadentry. (Allow use of door.)

Anti-Passback Control You can select a setting to control passback events.Passback is the use of an authorized card by more than oneperson to gain access through a controlled door. For example, the card owner uses the card to gain access, andthen "passes back" the card to another person who can usethe card to gain access through this or another door.

Anti-passback control settings allow you to specify whether the program checks where a card was recently used withinthe facility:

• Within Controller - Select this option to check whether acard was recently used at other doors assigned to thesame controller as this door.

• Network Wide - Select this option to check whether acard was recently used at another door in the network.



Andover Continuum CyberStation Configurator’s Guide461

Anti-Passback Type Area Based Control - This option enforces Anti-Passbackviolations based on areas.

Zone Number Based Control - Not implemented in thisrelease.

Send Access Events Select the events that you want to log for this door. You canview the logged events at the Access Events tab of the Door editor and in the Active Event View.

Select the checkbox next to each event that you want to log.

Valid Attempts Occurs when a card number or access code has beenaccepted as valid and the door switch detects that the door has opened.

Invalid Attempts Occurs when a card number or access code is rejected andaccess is denied.

Exit Requests Occurs when someone uses a keypad, card reader, motiondetector, or Request-to-Exit button to ask the system tounlock a door so the person can leave an area.

Forced Entries Occurs when the door switch detects that the door lock islocked and the doors with is open, or the input is tamperedwith (Trouble condition).

Door Ajar Occurs when a door remains open longer than the number of seconds specified for the Door Strike and Door Ajar attributes combined.

Valid Access -No Entry

Occurs when a card number or access code has beenaccepted as valid, and the door switch detects that the door has not opened.

About Associating Schedules with Doors

CyberStation offers many different ways to link schedules and doors. The controlrequirements of a particular building or area should determine how you configure theDoor editor to permit or deny access based on schedules. For example, a lobby door may have different locking requirements than one door of many into an auditorium.

The fields where you link Door objects to schedules are labeled as Schedule fields. Theobjects you attach in the Schedule fields are the InfinityNumeric points that are turned onand off by the schedules. You do not attach the Schedule objects themselves.

XDriver Tab – Door Editor

If you purchased a special device that you connected to a controller, TAC can developspecial software that allows your device to work with the controller. The software is calledan XDriver.

After you connect your device to the controller and install the XDriver software, you needto specify the comm port that you used in the XDriver window.



TAC 462

On the XDriver tab, select a comm port from the dropdown menu for the Commport field.

Entry Reader Tab – Door Editor

In the Entry Reader tab, you enter settings that identify the IOU module or controller thatcontrols the card reader or keypad. You make selections that determine what thecontroller does with information taken from the reader (and keypad, if used) and how itdetermines whether or not the door will open. If the door has a card reader or keypad onboth sides, enter settings for the second reader/keypad in the Exit Reader tab.

Note: If the door is in the Lockdown state, the door is locked, and these settings areignored. The settings resume when the Lockdown state is cleared.

Reader IOU Enter the number of the IOU module connected to the cardreader. You can find the IOU module number in the General tab of the IOUModule editor.

If the door is controlled by an Infinet controller, leave theReader IOU at zero.

Reader Channel Enter the channel number on the IOU module or controller thatis connected to the reader.

An AC-1 Reader Channel is 1.

Keypad Channel Enter the channel number on the IOU module or controller thatis connected to the keypad.

An AC-1 Keypad Channel is 1.




Area Click the browse button. In the Browse dialog, select the area towhich the door gives access.

When you save the settings for this door, CyberStationautomatically assigns the door to the area you selected.

Note: Selecting an area from the Browse dialog ensuresthat the full path name for the Area object is entered intothe field.

Validate Reader or

PIN

Not implemented in this release.

Access Validation Select one or more conditions the controller uses to decidewhether to open the door.

You can select one or more validation conditions for eachoperating mode. To gain access through this door, a personmust provide valid credentials for all the validation conditionsyou selected.

Use the Access Validation settings to determine how thecontroller validates access information from this reader/keypadin the following operating modes:

• Normal: Devices, controllers, and the CyberStation

workstation are communicating normally.• Comm Fail: The local controller and the CyberStation

workstation that manages access control information inyour network (the access server) are unable tocommunicate.

• No Database: The IOU module or controller is unable toobtain access information from the database at the networkcontroller. This can occur if communication between thetwo has failed. It also occurs if the network controller hasbeen reset so that its database has no access data toprovide.

Validate Site Select this condition if you want the controller to require a validsite code on the access card.

Validate Card Select this condition if you want the controller to require a validcard number on the access card.

Validate PIN Select this condition if you want the controller to check thenumbers pressed at the keypad to see if they form a validpersonal identification number (PIN).

General Code Check the numbers pressed at the keypad to see if they matchthe general code you entered in the Card Formats tab.



TAC 464

Door Forced LockSchedule

Check this checkbox to control this door with the followingconditions:

• When the schedule is on, the door is locked and cardreader and/or keypad access is denied to all personnel.

• When the schedule is off, the door is unlocked and accessis permitted to all personnel by card swipe and/or keypadentry.

Personnel Schedule Not implemented in this release.

Reader Schedule Not implemented in this release.

Entry Options Tab – Door Editor

In the Entry Options tab, you select options that help enforce the access validationchoices and reader options.

Note: If the door is in the Lockdown state, the door is locked, and all entry option settingsare ignored. The settings resume when the Lockdown state is cleared.

Reader EnableSchedule


Department Point Browse for the InfinityNumeric point that holds thedepartment number of the last person through the door.

This number is taken from the Personnel object created whenyou add a person to the system.




Timed Anti-PassbackMinutes

Enter the number of minutes during which an individualcannot enter through the same area again.

Zone Number Not implemented in this release.

Allow Entry on a TimedAnti-PassbackViolation

Allows re-entry to an area within the time in Timed Anti-Passback Minutes.

Anti-PassbackProtection

Makes the controller check for individuals who have tailgated.

A violation is logged when someone tries to gain accessthrough this door without obtaining valid access through other doors to reach this door. This can occur if a person entersthrough a door that was opened for someone else whoprovided valid access credentials.

Allow Entry on anAnti-PassbackViolation

Permits access even though it appears the individual hastailgated.

This checkbox is available when the Anti-PassbackProtection checkbox is selected.

PIN Duress Lets personnel signal a duress situation by entering a specialPIN when forced into an area by an unauthorized individual.

Reverse Card Duress Lets personnel signal a duress situation when an access card

is not swiped properly.

An alarm can be set to go off if this occurs.

Allow Entry on aReverse Card

Allows an entry when a card is swiped with the front of thecard facing the building rather than away from it.

(This does not work for proximity cards.)

Entry Status Tab – Door Editor

The Entry Status tab lets you view the following information about the door ’s entry status.

Current OperatingMode

Displays Card mode, Site mode and Card Mode, or PIN mode.

Last PersonAdmitted

Displays the name of the person associated with the last cardnumber or access code used to go through the door.

Time Admitted Displays the time the last person went through the door.

Last Person’sDepartment

Displays the last person's department number.

Last Invalid Person Displays the name of the person who last attempted to enter butwas not granted access.

Last Invalid Time Displays the time of the last invalid attempt.



TAC 466

Last Card Number Displays the number encoded in the last valid card swiped.

Last Site Number Displays the site code encoded in the last card swiped.

(Wiegand cards only, as the last card number for ABA cards isalways 0)

Entry Count Displays the total number of personnel that have entered throughthis door with valid access credentials. You can use a Plain Englishcommand to reset the door count. For example: Set DoorName

EntryCount to 0.

Exit Reader Tab – Door Editor

In the Exit Reader tab, you enter settings that identify the IOU module or controller thatcontrols the card reader and/or keypad used to exit the area that can be accessed usingthe reader/keypad specified in the Entry Reader tab. If no access validation is needed toexit the area, and no card reader or keypad is in use, you do not need to enter any valueson this tab.

This tab is configured the same way as the Entry Reader tab.

Note: If the door is in the Lockdown state, the door is locked, and these settings areignored. The settings resume when the Lockdown state is cleared.

Reader IOU Enter the number of the IOU module connected to the cardreader. You can find the IOU module number in the General tab of the IOUModule editor.

If the door is controlled by an Infinet controller, leave theReader IOU at zero.

Reader Channel Enter the channel number on the IOU module or controller thatis connected to the reader.

An AC-1 Reader Channel is 1.

Keypad Channel Enter the channel number on the IOU module or controller thatis connected to the keypad.

An AC-1 Keypad Channel is 1.

Area Click the browse button. In the Browse dialog, select the area towhich the door gives access.

When you save the settings for this door, CyberStationautomatically assigns the door to the area you selected.

Note: Selecting an area from the Browse dialog ensuresthat the full path name for the Area object is entered intothe field.

Validate Reader or PIN





Access Validation Select one or more conditions the controller uses to decidewhether to open the door.

You can select one or more validation conditions for eachoperating mode. To gain access through this door, a personmust provide valid credentials for all the validation conditionsyou selected.

Use the Access Validation settings to determine how thecontroller validates access information from this reader/keypadin the following operating modes:

• Normal: Devices, controllers, and the CyberStationworkstation are communicating normally.

• Comm Fail: The local controller and the CyberStationworkstation that manages access control information inyour network (the access server) are unable tocommunicate.

• No Database: The IOU module or controller is unable toobtain access information from the database at the networkcontroller. This can occur if communication between thetwo has failed. It also occurs if the network controller hasbeen reset so that its database has no access data toprovide.

Validate Site Select this condition if you want the controller to require a validsite code on the access card.

Validate Card Select this condition if you want the controller to require a validcard number on the access card.

Validate PIN Select this condition if you want the controller to check thenumbers pressed at the keypad to see if they form a validpersonal identification number (PIN).

General Code Check the numbers pressed at the keypad to see if they matchthe general code you entered in the Card Formats tab.

Door Forced LockSchedule

Check this checkbox to control this door with the followingconditions:

• When the schedule is on, the door is locked and cardreader and/or keypad access is denied to all personnel.

• When the schedule is off, the door is unlocked and accessis permitted to all personnel by card swipe and/or keypadentry.

Personnel Schedule Not implemented in this release.

Reader Schedule Not implemented in this release.



TAC 468

Exit Options Tab – Door Editor

In the Exit Options tab, you select options that help enforce the access validationchoices and reader options. If no card reader or keypad is configured in the Exit Reader tab, you do not need to select any options in this tab.

Note: If the door is in the Lockdown state, the door is locked, and all exit option settingsare ignored. The settings resume when the Lockdown state is cleared.

Reader EnableSchedule


Department Point Browse for the InfinityNumeric point that holds thedepartment number of the last person through the door.

This number is taken from the Personnel object created whenyou add a person to the system.

Timed Anti-PassbackMinutes

Enter the number of minutes during which an individualcannot enter through the same area again.

Zone Number Not implemented in this release.

Allow Entry on a TimedAnti-PassbackViolation

Allows re-entry to an area within the time in Timed Anti-Passback Minutes.

Anti-PassbackProtection

Makes the controller check for individuals who have tailgated.

A violation is logged when someone tries to gain accessthrough this door without obtaining valid access through other doors to reach this door. This can occur if a person entersthrough a door that was opened for someone else whoprovided valid access credentials.

Allow Entry on anAnti-PassbackViolation

Permits access even though it appears the individual hastailgated.

This checkbox is available when the Anti-PassbackProtection checkbox is selected.

PIN Duress Lets personnel signal a duress situation by entering a special

PIN when forced into an area by an unauthorized individual.

Reverse Card Duress Lets personnel signal a duress situation when an access cardis not swiped properly.

An alarm can be set to go off if this occurs.

Allow Entry on aReverse Card

Allows an entry when a card is swiped with the front of thecard facing the building rather than away from it.

(This does not work for proximity cards.)




Exit Status Tab – Door Editor

The Exit Status tab lets you view the following information about the door ’s exit status.

Current OperatingMode

Displays Card mode, Site mode and Card Mode, or PIN mode.

Last PersonAdmitted

Displays the name of the person associated with the last cardnumber or access code used to go through the door.

Time Admitted Displays the time the last person went through the door.

Last Person’sDepartment

Displays the last person's department number.

Last Invalid Person Displays the name of the person who last attempted to enter but was not granted access.

Last Invalid Time Displays the time of the last invalid attempt.

Last Card Number Displays the number encoded in the last valid card swiped.

Last Site Number Displays the site code encoded in the last card swiped.

(Wiegand cards only, as the last card number for ABA cards isalways 0)

Exit Count Displays the total number of personnel that have enteredthrough this door with valid access credentials. You can use aPlain English command to reset the door count. For example:Set DoorName EntryCount to 0.

Alarms Tab – Door Editor

Return to this tab to configure alarms after you have set other Door attributes and savedthe object. Alarms are discussed in Chapter 10, Configuring Alarms.

Access Events Tab – Door Editor

Use the Access Events tab of the Door editor to review the access activities for thisdoor. This tab is an event viewer for this door only, and shows access events as theyoccur.



TAC 470

Event Class The type or class of access event that has occurred.

Time Stamp The time at which the access event occurred.Person The name and path of the Personnel object for the person

causing the event.

Area The Area object associated with this event.

Using Area Lockdown

The area lockdown feature in the Area editor enables you to immediately prevent entry or exit through all doors to an area. When the Lockdown state is in effect, only personnelwith executive privilege access to the area can enter or leave it. You can also lock downindividual doors instead of an entire area.

The lockdown feature is supported in NetController II (models 9680 and 9681) networkcontrollers and ACX 57xx controllers. Area Lockdown must also be enabled in theCyberStation security key to use this feature. Issuing a lockdown message does notaffect access through doors controlled by other controllers.

More About Area Lockdown

The area lockdown feature is intended to help you quickly control area access inemergencies:

• You can issue a lockdown message to prevent access through all doors assigned toan area.

• You can clear the Lockdown state to restore routine access to an area.




• You can lock down and restore access to individual doors in an area that is notlocked down.

• You can view the lockdown status of an area and of the doors assigned to an area.

What Happens During Lockdown

When an area is locked down, the Lockdown state overrides the following access controlfeatures, and doors to the area are locked:

• Requests to exit, including pushing on crash bars

• Use of valid cards or keypad entries

• Schedules that unlock doors or allow access with valid cards or keypad entries

• Attempts to force unlock a door in the Door editor, through a Pinpoint control, or using a Plain English program

Only personnel who are assigned executive privilege access and are assigned accessrights to the area can enter or exit through a door in the lockdown state. You selectexecutive privilege access and assign area access rights in the Personnel object for eachperson that you want to have this access. For more information about executive privilege,see Chapter 19.

When the Lockdown state is cleared from an area, routine access resumes at doors tothe area (if adjacent areas are also not in the Lockdown state.)

Locking down an Area

Use this procedure to lock down all doors assigned to an Area object. This proceduredescribes how to lock down an area from the Area editor. Depending on how your CyberStation system is configured, you can also lock down areas using a Pinpoint areacontrol, a Plain English program, or command line entry.

1. Open the Area object for the area that you want to lockdown.

2. In the General tab of the Area editor, click the Lockdown Area button.

3. To verify that all doors to the area are locked down, select the Doors to Area tab,and view the lockdown status of each door:

• A door is locked down when the value for ForceLock is True.

• A door is not locked down when the value for ForceLock is False. The valuemay be false because the controller for the door did not receive the lockdownmessage, or because the controller does not support the area lockdown feature.

If a door could not respond to the lockdown message (for example, because itscontroller was temporarily offline), in the General tab you can click the LockdownArea button to send the message again.

4. To remove the Lockdown state from the area, in the General tab, click the Clear Lockdown Area button.

When you remove the Lockdown state, all doors to the area resume their normalstates. A door that provides access to another area that is still locked down remainslocked down until the Lockdown state is cleared from the other area.



TAC 472

Locking down Individual Doors

Use this procedure to lock down one or more doors that are assigned to an area that isnot locked down. This procedure describes how to lock down doors from the Area editor.Depending on how your CyberStation system is configured, you can also lock downdoors using a Pinpoint area control, a Plain English program, or command line entry.

1. Open the Area object for an area that is assigned the door that you want tolockdown.

2. Click the Doors to Area tab of the Area editor.

3. Select one or more doors, and click the Lockdown Selected Doors button.

You can select multiple doors by holding down the Ctrl key or the Shift key while youselect doors in the list.

4. To verify that all doors to the area are locked down, view the lockdown status of eachdoor:

• A door is locked down when the value for ForceLock is True.

• A door is not locked down when the value for ForceLock is False. The valuemay be false because the controller for the door did not receive the lockdownmessage, or because the controller does not support the area lockdown feature.

If a door could not respond to the lockdown message (for example, because itscontroller was temporarily offline), in the General tab you can click the Lockdown

Selected Doors button to send the message again.5. To remove the Lockdown state from doors, select one or more doors, and click the

Clear Lockdown Selected Doors button.

When you remove the Lockdown state, doors resume their normal states. A door thatprovides access to an area that is locked down remains locked down until theLockdown state is cleared from the other area.

Controlling Access with Condition Levels

Several Andover Continuum controllers support a system variable named ConditionLevel:

• NetController II 96xx models

• NetController 99xx models

• ACX 57xx models

If this system variable is supported in your controllers and is also enabled in theCyberStation security key, you can use this variable to rapidly control area access inemergencies.

A ConditionLevel value is stored at the controllers that manage access to the doors toeach area. Typically, the controller condition level corresponds to security alert levels thatyour company has established for emergencies. You use controller condition levels withpersonnel clearance levels to control access during different categories of emergency. Avalue of 1 for a controller condition level is the most severe alert level. A value of 255 isthe least severe.




You can quickly change the condition level at all controllers by sending a new value for ConditionLevel from the CyberStation workstation using the Global Condition Leveldialog. This is a faster method of changing the values than manually changing thecondition level at each controller. You can also restore the previous condition level at allcontrollers by selecting a ConditionLevel value of Local in this dialog.

For more information about condition levels, see “Personnel Clearance Levels andController Condition Levels” in Chapter 19, Personnel .

Sending a Condition Level Message to Controllers

Use this procedure to send a new value for the ConditionLevel system variable to allcontrollers. All controllers that receive the message and support the ConditionLevelsystem variable update the value of the variable with the new condition level.CyberStation also saves each controller's original value for ConditionLevel in the DBValue field in the CyberStation database.

1. In the CyberStation tool tray, right click the Continuum task icon, and select GlobalCondition Level.

2. Select a new condition level for Change To.

You can select Level_0 for the value if you do not want the controllers to use thecondition level value when validating access.

3. Click Change.

4. When prompted to confirm the change, click Yes.

5. When prompted that the condition level is changed, click OK.

Restoring Controller Condition Levels to Previous Levels

Use this procedure to send the ConditionLevel value that was saved in the DB Value field for each controller to the controllers.

This is the ConditionLevel value that was in effect at each controller before CyberStationsent the new ConditionLevel value. For example, if the value for ConditionLevel atController A was originally 4, the value at that controller is once again 4.

1. In the task bar, right click the Continuum task icon, and select Global ConditionLevel.

2. Select Local for Change To.

3. Click Change.

4. When prompted to confirm the change, click Yes.

5. When prompted that the condition level is changed, click OK.



TAC 474

About Sending Condition Level Values to IndividualControllers

Using the Global Condition Level dialog enables you to change the value for ConditionLevel at multiple controllers with one command. You can also change the valuefor individual controllers:

• You can edit the ConditionLevel variable in the InfinitySystemVariable editor.

• You can enter a command to change the value from the command line.

• You can use a Plain English (PE) program to change the value.

• You can use PE script attached to a Pinpoint control to change the value.

When you use the command line or a PE program to send a value for this variable, youmust use the numeric value that corresponds to the condition level that you want to set.Do not use a text string.

For example, if you want to use the SET command to change the value for ConditionLevel to Level 5, use the following syntax:

SET \[pathname]\ConditionLevel = 5




Personnel

This chapter covers two major topics, the Personnel Manager and the Personnel ImportUtility. The CyberStation Personnel Manager is a powerful and easy-to use tool for creating, viewing, and managing personnel records. The Personnel Import Utility allowsyou to import third-party personnel data that was created outside of an Andover Continuum system. It bridges the gap between other personnel databases andCyberStation personnel records by allowing you to import and upload personnel data in

large amounts and save the imported data as CyberStation Personnel objects.

Personnel Manager

Use the CyberStation Personnel Manager for entering, viewing, and managing personneldata:

• Security access information, such as card number and a list of the areas the personmay enter.

• Employee information, such as department name and number, supervisor name, andvehicle information.

• Personal information, such as name, blood type, emergency contact, height, weight,and hair color.

The data for each person is stored in a Personnel object. In the Personnel Manager, aPersonnel object can also be referred to as a record, card, or badge because the data inthe Personnel object may be associated with any of these.

19



TAC 476

Search Capability

In the Personnel Manager, you can quickly locate Personnel objects using the built-insearch feature. You can search by criteria such as first and last names, card number, andemployee number. You can enter full or partial information for the criteria. Search resultscan display thumbnail photos from employee badges, if available.

Customizable Profiles for Viewing and Entering Personnel DataThe Personnel Manager uses profiles to streamline the process of creating newPersonnel objects by providing predefined lists of area access rights. You can also useprofiles to determine the personnel data displayed when users view, edit, or createPersonnel objects. Profiles enable you to limit user access to sensitive personnel data,such as Social Security numbers and home phone numbers. The Personnel Manager also supports the use of CyberStation personnel templates.




Simplified Area Assignment

The Personnel Manager provides several methods for adding or editing the list of areasyou assign to Personnel objects:

• You can specify the areas in profiles. The areas are then assigned in any Personnelobjects created from the profile.

• You can replace the areas in a Personnel object with the areas from a profile or apersonnel template.

• You can add or remove individual areas as needed in Personnel objects.

Regardless of the method that you use, schedule and clearance level information can beincluded with the areas you assign to Personnel objects. This enables you to customizethe access rights for types of personnel (employee, contractor, visitor, etc.) or for individual personnel as needed in your facility.

Personnel Enrollment from Card Reader

The Personnel Manager can automatically create new Personnel objects usinginformation from an access card that is read at a card reader that you designate. You canedit these Personnel objects to enter additional information at any time. You can also usethis feature to identify the owner of an access card.

Enabling the Personnel Manager

The Personnel Manager is enabled by default at each CyberStation workstation.However, users can choose to enable the Personnel editor, a dialog similar to other CyberStation dialogs (used in earlier versions of CyberStation), instead of the PersonnelManager. If another user enabled the Personnel editor at your workstation, and you wantto resume using the Personnel Manager, complete the following steps.

1. In Continuum Explorer, right click your workstation folder, and click Open.

2. Select the Preferences tab of the Device editor.

3. Scroll down to the preference setting, Use Personnel Manager , and select True.

4. Click OK.

In Continuum Explorer, you can now double click a Personnel object to edit the object

in the Personnel Manager. The Personnel Manager also opens when you create anew Personnel object from Continuum Explorer.

Adding New Personnel Objects

You can add a new object from Continuum Explorer or from the Personnel Manager.When you add an object from the Personnel Manager, CyberStation automaticallygenerates the object ID and alias that are displayed when you view the list of Personnelobjects in Continuum Explorer.

Note: You can also use the Personal Import Utility to import personnel records fromanother application into CyberStation. Once imported, these records becomePersonnel objects that you can edit and manage in the Personnel Manager. For more information, see “Personnel Import Utility” later in this chapter.



TAC 478

Perform the following steps to add a new Personnel object.

1. If the Personnel Manager is open at your workstation, click Add Record, select aprofile from the popup menu, and proceed to step 4.

When the Personnel Manager is open, you can add and save multiple Personnelobjects without having to close and reopen the Personnel Manager each time.

2. If the Personnel Manager is not open, in Continuum Explorer, right click the folder that contains your Personnel objects. Select New from the popup menu, and thenselect Personnel. Proceed to step 3.

3. Enter a Personnel object name, and click the Create button.

4. In the Details tab, enter values for personnel attributes as needed.

Values for attributes marked with an asterisk (*) are required. If you try to save therecord without all required values, a warning message lists attributes that still requireentries.

If… Then…

You want to add card informationfrom an access card read at your

enrollment card reader (requires acard read designated in theconfiguration settings)

Swipe the card at the card designated reader.In the Personnel Manager, click the Read

Card Info button.

In the Card Information dialog, verify in thestatus line that the card is not assigned toany personnel record, and click the InsertData button.

In the Details tab, the Card Type, Site Code,and Card Number attributes are updated withthe information read from the card.




If… Then…

This person requires additionaltime to open and pass throughdoors

Check the ADA checkbox.

Use the Door editor to configure doors toallow extra time for entry for personnel with ADA access.

This person is a visitor to your facility

Check the Visitor checkbox.

If the Personnel object is associated with a template, you cannot change attributevalues inherited from that template.

5. Assign areas to this Personnel object, if needed.

Any areas that are assigned in the profile you used to create the Personnel objectare automatically assigned to the object. You can assign other areas to the object asneeded.

If you want to… Then…

Replace the currently assignedareas (if any) with the areas fromanother profile

Select the Profile radio button, select profilefrom the dropdown list, and click the ResetAccess Rights button.

When prompted, click Yes.

Any areas previously assigned to thisPersonnel object are removed when you addthe areas from the selected profile.

Replace the currently assignedareas (if any) with the areas from apersonnel template

Select the Template radio button, select atemplate from the dropdown list, and click theReset Access Rights button.


Any areas previously assigned to thisPersonnel object are removed when you addthe areas from the selected template.



TAC 480


Assign individual areas Under Access Rights, expand UnAssigned,and check the checkbox next to each areayou want to assign.

You can click the Filter by Folder button,and select a folder, to view only the areas inthat folder. You cannot filter by Root.

Remove access to an area Under Access Rights, expand Assigned,

and clear the checkbox next to each areayou want to remove.

6. If you want to attach a schedule point to one or more areas, expand an area, andclick the icon next to Add Schedule.

The Add Schedules dialog is displayed. If needed, select the browse button next toSchedule Points Location, and locate the folder or container with the schedulepoint you want to add.

Select a schedule point. Select the areas where you want to attach the schedulepoint, and click OK.

7. If you want to override this person's Default Clearance Level for an area, expand thearea, and click the icon next to Clearance Level.

In the Clearance Level dialog, enter a new value for the clearance level, and clickOK.

If the security key attached to the CyberStation workstation is not configured to viewcondition levels, condition level and clearance level attributes and values are notdisplayed or configurable in CyberStation. For more information about clearancelevels, see “Personnel Clearance Levels and Controller Condition Levels” later in thischapter.

8. Click Apply.

9. If needed, click Add Record, select a profile, and repeat this procedure from step 4to add another Personnel object.

10. Click OK to save changes and close the Personnel Manager.

Editing a Personnel Object

To open the Personnel Manager, double click any Personnel object in ContinuumExplorer. When the Personnel Manager is open, you can use its powerful search featureto locate a Personnel object that you want to edit. In the Personnel Manager, changes toa Personnel object are not saved until you click Apply or OK.

Searching for a Personnel Object

You can search for personnel by any of the following criteria: first or last name, SocialSecurity number, employee number, card number, department, and department code.




Note: You can also locate a Personnel object that you want to edit by scrolling throughthe list of Personnel objects in Continuum Explorer. You can then double click theobject to open it in the Personnel Manager and edit it as described in this topic.

Perform the following steps to search for a Personnel object.

1. In the Personnel Manager, click the New Search button, and enter search criteria.

The Personnel Manager can search for exactly what you type if you put the entry inquotes. If you do not enter quotes, the Personnel Manager searches for records withattributes that begin with what you type. The following table provides an example of

search criteria entered to locate a Personnel object by last name.

Typing… Searches for…

J Every last name that starts with the letter J

“Johnson” Records of personnel whose last name is Johnson

John Every last name that starts with John

You can limit the number of records returned by entering a value between 1 and 50for Maximum Results. If you do not enter a value, the Personnel Manager displaysthe first 50 records that match the search criteria that you entered.

2. Click the Find Now button.

If not already checked, check the Show Thumbnails checkbox if you want to display

photos in the search results.

3. Click a name in the search results to display the record details in the PersonnelManager.

To return to your search results, click the Search Results tab.

Assigning or Changing Access to Areas

Any areas in the profile you used to create a Personnel object are automatically added tothe object. If needed, you can assign other areas to the object, or remove areas, asdescribed in the following procedure.

1. In the Personnel Manager, search for the Personnel object that you want to edit, andselect the record from the search results.

2. Assign areas to this Personnel object.

If you want to ... Then...

Replace the currently assignedareas (if any) with the areas fromanother profile

Select the Profile radio button, select aprofile from the dropdown list, and click theReset Access Rights button.


Any areas previously assigned to thisPersonnel object are removed when youadd the areas from the selected profile.



TAC 482

If you want to ... Then...

Replace the currently assignedareas (if any) with the areas from apersonnel template

Select the Template radio button, select atemplate from the dropdown list, and clickthe Reset Access Rights button.


Any areas previously assigned to thisPersonnel object are removed when youadd the areas from the selected template.

Assign individual areas Under Access Rights, expandUnAssigned, and check the checkboxnext to each area you want to assign.

You can click the Filter by Folder button,and select a folder, to view only the areasin that folder. You cannot filter by Root.

Remove access to an area Under Access Rights, expand Assigned,and clear the checkbox next to each areayou want to remove.

Disable access to an area withoutremoving the area

Under Access Rights, expand Assigned,and expand the area for which you want to

disable access for this person. Clear the Enable Area checkbox.

The checkbox next to the area name

changes to . You can check the EnableArea checkbox to restore this person'saccess to the area.

Note: Areas assigned from a profile or template using the Reset Access Rights button described below do not maintain their association with the profile or template they came from. If you later edit the profile or template, existingPersonnel objects are not affected by the changes.

3. Click Apply.

Attaching a Schedule Point to an Area

Schedule points are associated with schedules that define specific time periods when aperson can access that area. You can attach only one schedule point to an area.However, you can attach the same schedule point to multiple areas. For more informationabout schedules, see Chapter 15, Configuring Schedules and Calendars.

Perform the following steps to attach a schedule point to an area assigned to a Personnelobject.


2. Under Access Rights, expand Assigned.




3. Expand the area that you wish to add a schedule point to.

4. Click the icon next to Add Schedule to display the Add Schedules dialog.

5. If needed, select the browse button next to Schedule Points Location, and locatethe folder or container with the schedule point you want to add.

6. Select a schedule point. Select the areas where you want to attach the schedulepoint, and click OK.

7. Click Apply.

Changing the Clearance Level of a Personnel Object

The Clearance Level for areas enables you to provide different access privileges todifferent areas assigned to the same person. The clearance level you assign to an areain a Personnel object does not affect the access of other personnel with access to thesame area.

The Default Clearance Level applies to all areas that you assign to the person, unlessyou choose to override this value with different values for individual areas. (To change

the Default Clearance Level, this attribute must be displayed in the profile assigned to thecurrent user. For more information about profiles, see “Working with Personnel Profilesand Templates” later in this chapter.)

Areas with a clearance level of zero use the value entered for the Default ClearanceLevel to determine access to the area for this person. For more information about howclearance levels control access to assigned areas, see “Personnel Clearance Levels andController Condition Levels” later in this chapter.

Note: If the security key attached to the CyberStation workstation is not configured toview condition levels, condition level and clearance level attributes and values arenot displayed or configurable in CyberStation.



TAC 484

Changing the Default Clearance Level

Perform the following steps to edit clearance levels for a Personnel object. Clearancelevel values are maintained in the Personnel object for each person:


2. In the Details tab, enter a value for Default Clearance Level.

Enter 0 if you do not want to assign a default clearance level to this person.

3. Click Apply.

Changing the Clearance Level of Specific Areas

The clearance level you enter for the area overrides the default clearance level for thePersonnel object. Perform the following steps to change the clearance level of a specificarea for a Personnel object.


2. Under Access Rights, expand Assigned.

3. Expand the area for which you want to change the clearance level.

4. Click the icon next to Clearance Level.

5. In the Clearance Level dialog, enter a new value for Clearance Level, and click OK.

6. Click Apply.

Assigning Executive Privilege to a Personnel Object

When the Lockdown state is in effect, only personnel who are assigned executiveprivilege can enter and exit the areas to which they have access. All other personnel,regardless of the areas and access right assigned to them, are prevented from enteringor leaving areas in the Lockdown state. For more information about the Lockdown state,see “Using Area Lockdown” in Chapter 18. Perform the following steps to assignexecutive privilege to a personnel object.


2. In the Details tab, select True for Executive Privilege.

3. Click Apply.




Disabling or Enabling a Personnel Object

When you disable a Personnel object, the access card for this person is no longer valid atany doors in areas to which the person is assigned. For example, you can disable thePersonnel object for a contract employee who is not working for your company but mayreturn in the future. You can enable a disabled Personnel object at any time. Perform thefollowing steps to disable or enable a Personnel object.


2. Disable or enable the object.To disable a Personnel object, clear the checkbox next to Card Enabled. The textturns red, indicating that person's card is disabled.

To enable a Personnel object, check the checkbox next to Card Enabled.

3. Click Apply.

Setting the Current Area

CyberStation determines the current area from the last-door-entered information, if available. In systems set up to prevent or discourage tailgating, you may occasionallyneed to override the displayed current area if the person accessed a different areawithout using his/her card or entering a PIN and is now prevented from leaving an area.Perform the following steps to specify the current location of the card holder associated

with a Personnel object.

1. In Continuum Explorer, open the folder that contains your Personnel objects.

2. Select the Personnel object that you want to edit, right click, and select Set CurrentArea from the popup menu.

3. In the Browse dialog, locate the area, and click the Select button.

4. When prompted, click OK.

Making or Editing a Badge

If you have already purchased the separately sold badging software product, Epibuilder ,you can create a badge by setting up a location for badge layout files and default badgeformats. See Appendix B for installation information.

Setting up a Badge Location and Format

Before you can create a badge, you must set up a location for badge layout files as wellas a default badge format.

1. In Continuum Explorer, right click your workstation icon, and select Open from thepopup menu. The Device editor appears.

2. Select the Preferences tab.



TAC 486

4. Click inside the Value column of this setting:

The location of the badge format files

From the browse dialog, search for and assign a default path for the folder in which

you want to store badge layout files.

5. Click inside the Value column of this setting:

The default badge format

Specify a default badge layout for the system to load when creating a new Personnel

object.

Note: This is unique to each user. For each user, repeat steps 4 and 5.

6. Click OK.

7. Assign and/or deny write privileges to users who will and won’t be making/editing

badges.

8. Open the Security editor. Right click the Continuum task icon in the icon tray, andselect Security from the popup menu.

9. Select the Actions tab, then scroll down to and expand the Personnel directory.

10. Scroll down to Edit Badge Layout, and assign or deny access privileges.

11. Assign a key symbol or a lock, respectively, to the appropriate user groups.




5. Click OK.

Creating or Editing a Badge

To create or modify a person’s badge, including layout photo, signature, and fingerprint,perform the following steps.

1. On the General tab of the Personnel editor, click the Make/Edit Badge button. (Fromthe Personnel Manager, click the Create/Edit Badge button.

2. In the Badge Layout field, specify a badge layout file. Either accept the default or click the browse button to search for and select another layout. (The default layoutmust be assigned in the Preferences tab of the Device editor.

EPIDesigner Compatible with Guard Draw: In Version 1.8 and higher, the

EPIDesigner application replaces Guard Draw, which was the layout tool used in

previous versions. Guard Draw files created in previous versions are compatible with

EPIDesigner. The Badge Layout field accepts either an EPIDesigner layout (.dgn

file) or a Guard Draw layout (.gdr file). You can easily open and save your existingGuard Draw layout in EPIDesigner. It is saved as a .dgn file.

3. Click the Edit Badge Layout button. The EPIDesigner application appears.



TAC 488

4. Use EPIDesigner (and its graphical layout window) to design or change the design of this person’s badge layout.

EPIDesigner Documentation: For complete instructions on how to use this

EPIDesigner application, access its online help using the Help dropdown menu in the

menu bar. Also consult the EPIDesigner 6.3 User’s Guide. This manual is available

as .PDF file via your Windows Start menu. (Click Start, select Programs, selectContinuum, and then select Documentation.)

5. From the Made/Edit Badge dialog, to capture a photo, signature, or fingerprint, asneeded, double click inside the photo, signature, or fingerprint window, respectively.




As an alternative, you can also:

Click the Capture Photo, Capture Signature, or Capture Fingerprint button,

respectively.

Use the Capture dropdown menu, and select Photo, Signature, or Fingerprint,

respectively

The Select Profile dialog appears.

6. From the Select Profile dialog, capture a source profile:

Capturing source profile for the first time – When you perform the previous step,

and the Select Profile dialog appears, you must capture the source. (If you have

installed a video capture device, select Twain.)

For further instructions, click the Help button in this Select Profile dialog, or see theEPIDesigner 6.3 User’s Guide.

Changing an existing source profile – To change an existing source profile, from the

Tools dropdown menu on the Make/Edit Badge dialog, select Set Photo Image

Source, Set Signature Image Source, or Set Fingerprint Image Source, respectively.

The Select Profile dialog appears.

For further instructions, click the Help button in this Select Profile dialog, or see the

EPIDesigner 6.3 User’s Guide.

7. From EPIDesigner (and its graphical layout window), you may bind a Personnelobject’s attributes to graphic layout elements.

Note: EPIDesigner imports all the attribute names from the Personnel object.



TAC 490

To do so:

In the graphical layout window, select an existing graphic element – or make a new

one and select it.

Select an attribute form the attribute dropdown menu, located next to Text dropdown

menu on the bottom toolbar.

The name of the attribute appears inside the selected graphic element.

EPIDesigner Documentation: For complete instructions on how to use this

EPIDesigner application, access its online help using the Help dropdown menu in themenu bar or consult the EPIDesigner 6.3 User’s Guide.

Print the current card (or multiple cards) if you wish to do so.

Printing a single card – To print the current card, from the File dropdown menu on

the Make/Edit Badge dialog, select Print Card. (You may also click the Print Badge

button.) To preview the current card before printing it, select Print Preview Card

from the File dropdown menu. The Print Preview dialog appears, displaying the card

you are about to print. When you print a card you are also “issuing” a card.

Printing more than one card – To print all cards that have not already been printed

– in other words, cards that have not yet been “issued” – select Batch Print Cards

from the File dropdown menu. This prints, or “issues,” all the non-printed cards. To

see all the cards that have not yet been issued, select Batch Preview Cards. ThePrint Preview dialog appears. Click the right-arrow button to scroll through all the

cards, one by one, that you are about to print. Click the left-arrow button to scroll

back.

Note: At any given time, each card carries a status of Issued or Unprinted (non-issued). To find out how many cards have been issued, look at the Issued fieldon the Make/Edit Badge dialog. If you want to change the status of the currentcard from Issued to Unprinted, open the Tools dropdown menu, and selectSet Card Unprinted. When you set an issued card to Unprinted, the number displayed in the Issued field is reduced by one, and that card is added to thelist on non-issued card in the Print Preview dialog.

8. Set up external card encoding if you wish to do so.

Configure your encoder settings by accessing the following dialogs:

From the Tools dropdown menu on the Make/Edit Badge dialog, select External

Card Encoder Setup. The External Encoders Setup dialog appears.

From the File dropdown menu in EPIDesigner, select Layout Properties. From the

Layout Properties dialog, select the General tab, and click the Encoding button.

The Card Encoding dialog appears.

Note: If you need instructions for configuring the settings on these dialogs, click theHelp button to access extensive online documentation, or consult theEPIDesigner 6.3 User’s Guide.

9. Set up card encoding for a printer if you wish to do so.




Configure our encoder settings by accessing the following dialogs:

From the Tools dropdown menu on the Make/Edit Badge dialog, select Printer Card

Encoder Setup. The Card Printer Encoder Setup dialog appears.

From the File dropdown menu in EPIDesigner, select Layout Properties. From the

Layout Properties dialog, select the General tab, and click the Encoding button. The

Card Encoding dialog appears.

Note: If you need instructions for configuring the settings on these dialogs, click the Helpbutton to access extensive online documentation, or consult the EPIDesigner 6.3

User’s Guide.

Reading Card Information

You can read card information in the Personnel Manager that you obtain by swipingaccess cards at a card reader designated in the configuration settings for the PersonnelManager. You may want to do this to look up the card holder of an unidentified accesscard. You can also do this to assign new cards to existing Personnel objects.

Note: To assign card information from a swiped card when you create new Personnelobjects, see “Adding New Personnel Objects,” earlier in this chapter.

1. If the Personnel Manager is not open, you can double click any Personnel object inContinuum Explorer to open the Personnel Manager.

2. Swipe the card at the designated card reader.

3. In the Personnel Manager, click the Read Card Info button to open the CardInformation dialog.

The Card Information dialog displays the values for the following attributes: Card

Type, Site Code, and Card Number . A message in the status bar of the dialog

indicates whether a record in the Personnel Manager matches the values for these

attributes.

If ... Then...

The card information matches apersonnel record, and you want toview the record

Check the Load the personnel record thatmatches the criteria checkbox, and clickClose.

The personnel record associated with theaccess card is displayed in the Details tab of the Personnel Manager.

You want to close the dialogwithout loading a personnel record

Click Close.



TAC 492

Replacing Card Information

Use this procedure to replace the current card information in a Personnel object withinformation read from a new access card.

Note: If you need to replace the access card information in a record because the card ismisplaced or lost, you may want to assign new card information as described in“Issuing or Restoring a Temporary Card” or “Marking a Card as Lost,” later in thischapter. Using either of those procedures ensures that the card you are replacing

cannot be used to access your facility.

1. In the Personnel Manager, search for the Personnel object you want to edit, andselect the personnel record from the search results.

2. If the Personnel Manager is not open, you can double click any Personnel object inContinuum Explorer to open the Personnel Manager.

3. Swipe the card at the designated card reader.

4. In the Personnel Manager, click the Read Card Info button to open the CardInformation dialog.

The Card Information dialog displays the values for the following attributes: CardType, Site Code, and Card Number . A message in the status bar of the dialogindicates whether a record in the Personnel Manager matches the values for these

attributes.

5. Click the Insert Data button.

In the Details tab of the Personnel Manager, the Card Type, Site Code, and CardNumber attributes in the personnel record are updated with the values from theaccess card.

6. Click Apply.

If you mistakenly assign card information already associated with a personnel recordto a different personnel record, an error message is displayed when you click Apply,indicating that the card information duplicates the information in another record. Thechanges are not saved in the current record.

Issuing or Restoring a Temporary CardUse this procedure to issue a temporary card.

Issuing a temporary card saves the card holder's current information and temporarilyassigns a new card number to the Personnel object. Issue a temporary card when youexpect to reinstate the original card in the future. Unlike marking a card as lost, issuing atemporary card enables you to restore the original card.

1. In the Personnel Manager, search for the Personnel object for which you want toissue a temporary card, and select the record from the search results.

If the Personnel Manager is not open, you can double click any Personnel object inContinuum Explorer to open the Personnel Manager.




2. Click the Issue Temp Card button, and enter a new card number when prompted.

When clicked, the button label changes to Restore Temp Card. You can click theRestore Temp Card button to restore card information that was saved by issuing atemporary card.

3. Click Apply.

Marking a Card as Lost

Use this procedure to mark a card as lost. A new record is then created automaticallywith all of the same personnel information and access rights with the exception of thecard number. A new card number is required.

Note: You cannot restore a card that you mark as lost.

1. In the Personnel Manager, search for the Personnel object for the lost card, andselect the record from the search results.


2. Click the Mark Card as Lost button.


3. In the New Card Number dialog, enter a new card number, and click OK.

The Personnel Manager renames the current record by appending ".Lost" to that

Personnel object's name. For example, "John Smith" would be the new record, and

"John Smith.Lost" would be the old record.

You can delete the .Lost record if you do not want it in your database.

Deleting Personnel Objects

You may want to delete a Personnel object when it is no longer needed or valid (for example, when a person leaves your company). This permanently removes thePersonnel object from CyberStation.

Note: When you delete a Personnel object, it is marked for deletion, but is not removedfrom CyberStation until the Personnel object can be removed from all controllersthat receive access distributions from CyberStation. If a controller cannot becontacted by CyberStation, the Personnel object remains in CyberStation untilcommunication between the controller and CyberStation resumes.

Deleting Personnel Objects in Continuum Explorer

1. In Continuum Explorer, open the folder that contains your Personnel objects.

2. Select the Personnel objects you want to delete.

To select multiple objects, hold down the Ctrl or Shift key while you select Personnelobjects.

3. Right click, and select Delete.



TAC 494

4. When prompted to confirm deletion, click OK.

Deleting Personnel Objects in the Personnel Manager

1. In the Personnel Manager, click the New Search button, and enter search criteria.

The Personnel Manager can search for exactly what you type if you put the entry inquotes. If you do not enter quotes, the Personnel Manager searches for records withattributes that begin with what you type. The following table provides an example of search criteria entered to locate a Personnel object by last name.

Typing… Searches for…J Every last name that starts with the letter J

“Johnson” Records of personnel whose last name is Johnson

John Every last name that starts with John

You can limit the number of records returned by entering a value between 1 and 50for Maximum Results. If you do not enter a value, the Personnel Manager displaysthe first 50 records that match the search criteria that you entered.

2. Click the Find Now button.

If not already checked, check the Show Thumbnails checkbox if you want to displayphotos in the search results.

3. Click a name in the search results to display the record details in the PersonnelManager.

To return to your search results, click the Search Results tab.

4. Click the Delete Record button.

5. When prompted to confirm deletion, click Yes.

6. To locate additional Personnel objects to delete, click the Search Results tab. Selectanother object to delete, or perform a new search.

Working with Personnel Clearance Levels and Controller Condition Levels

Clearance levels and condition levels are features of the Andover Continuum system thatenable you to rapidly control area access in emergencies. Clearance and condition levelswork with other security access features, such as the area lockdown feature and theaccess settings defined in Personnel objects. By configuring and managing thisinformation in CyberStation, you can respond quickly to changing circumstances.

Note: If the security key attached to the CyberStation workstation is not configured toview condition levels, condition level and clearance level attributes and values arenot displayed or configurable in CyberStation.




Personnel Clearance Levels

Clearance level values are maintained in the Personnel object for each person:

• The Default Clearance Level applies to all areas that you assign to the person,unless you choose to override this value with different values for individual areas.

• The Clearance Level for areas enables you to provide different access privileges todifferent areas assigned to the same person. The clearance level you assign to anarea in a Personnel object does not affect the access of other personnel with accessto the same area.

Controller Condition Levels

A value for Condition Level is stored at the controllers that manage access to the doors toeach area. Controllers that support the Condition Level variable include:

• NetController II

• NetController, models CX99xx

• ACX 57xx

The Condition Level variable must be enabled in the security key in order for thesecontrollers to use the variable and accept Condition Level values sent from CyberStation.

Typically, the controller condition level corresponds to security alert levels that your company has established for emergencies. You use controller condition levels with

personnel clearance levels to control access during different categories of emergency. Avalue of 1 for a controller condition level is the most severe alert level. A value of 255 isthe least severe. A value of 0 indicates that no condition level is in effect.

You can quickly change the condition level at all controllers by using the Global ConditionLevel dialog to send a new Condition Level value to the controllers from the CyberStationworkstation. This is a faster method of changing the values than manually changing thecondition level at each controller. You can also restore the previous condition level at allcontrollers using this feature.

The following figure is an example of how a new Condition Level is sent fromCyberStation changes condition levels at two controllers.



TAC 496

How Clearance Levels and Condition Levels Work Together

The condition level at a controller establishes the security alert level (sometimes calledthe "threat level") in effect at doors in areas managed by the controller. After verifyingaccess card information (or keypad entry) and that the current area is assigned to aperson requesting access, the controller compares its condition level to the clearancelevel of the person. For the controller to allow access, the value of the person's clearancelevel must be equal to or smaller than the condition level.

The following figure is an example of how a controller uses clearance and conditionlevels to validate access.




Implementing Clearance Levels and Condition Levels

The Andover Continuum system enables you to set up highly customized access that istailored to the needs of your facility and the people who need access in normal andemergency situations. You can define up to 255 clearance levels and condition levels:

• 1 is the clearance level that allows the most access. That is, when the condition levelis 1 (most severe alert), only personnel with a clearance level of 1 who are assignedto the area will have access.

• 255 is the clearance level that allows the least access. That is, the condition levelmust be 255 for personnel with a clearance level of 255 to be allowed access.



TAC 498

You can use as many of these levels as you need. For example, a public facility in theUnited States might define condition levels that correspond to the five levels of theDepartment of Homeland Security (DHS) Advisory System, as shown in the followingtable.

DHS Level DHS Color Condition Level Clearance LevelNeeded for Access

Severe Red Level_01 1

High Orange Level_02 2

Elevated Yellow Level_03 3

Guarded Blue Level_04 4

Low Green Level_05 5

In Personnel objects, you can specify clearance levels that correspond to these conditionlevels.

Configuring the Personnel Manager

The Personnel Manager has default settings so that you can immediately create and viewPersonnel objects. However, you can configure settings to customize many features,

enabling you to enter and manage personnel data more efficiently.

Working with Personnel Profiles and Templates

This topic contains information about using personnel profiles and templates to create,edit, and view data in Personnel objects.

Using Personnel Profiles

A personnel profile is a collection of settings that you use to create new Personnelobjects and to view existing objects in the Personnel Manager. A personnel profilecontains predefined settings and values for the following personnel information:

• The attributes displayed when a user creates, edits, or views a Personnel objects,including attribute labels, whether attributes are required or are read only, and default

values• The areas assigned to Personnel objects, which can also include schedule points

attached to the areas, clearance levels for individual areas, and whether the area isenabled or disabled

Profiles are similar to personnel templates. However, in addition to determining thepersonnel information that is predefined, profiles enable you to have more control over the personnel data that is entered, edited, and viewed in a Personnel object.

For example, you can assign a profile that does not display sensitive information, such asSocial Security numbers, to CyberStation users who do not need to see this information.Users who do require this information can be assigned a profile in which sensitiveattributes are displayed. You can also specify whether attribute values are editable or read only.




The Personnel Manager provides four predefined profiles: Employee, Contractor,Temporary Employee, and Visitor. You can customize these profiles and create your own. To create a personnel profile, see “Creating a Personnel Profile” later in thischapter.

How Profiles Are Applied

When a user creates a Personnel object:

The profile the user selects after clicking the Add Record button determines:

• The areas that are initially assigned to the Personnel object

• Any additional access rights associated with the areas, such as schedules andclearance levels

The user can edit the area assignments and access rights as needed in the Personnelobject.

The profile assigned to the user determines:

• The attributes displayed in the Details tab for the new object

• Any predefined properties of the attributes, such as default entries and requiredentries

• The folder where the Personnel object is saved

When a user edits an existing Personnel object, the profile assigned to the user

determines:

• The attributes displayed in the Details tab

• Any predefined properties of the attributes, such as read-only and required entries

Using CyberStation Personnel Templates

You can use a personnel template to create a Personnel object:

• In Continuum Explorer, you can use the Configuration Wizard to create a Personnelobject from a template that you select. You can also drag a personnel template to afolder containing your Personnel objects to create a new object.

• In the Personnel Manager, you can create a Personnel object from a profile that hasa template assigned to it, if you have customized a profile to include the Templateattribute. In the profile, you can also specify the personnel template to use.

When you edit the Personnel object, a message is displayed in the Personnel Manager status line indicating that a template is attached to the Personnel object. Any attributevalues that are inherited from the template are read-only in the Personnel Manager. Attribute values copied (not inherited) from the template are editable. The profileassigned to the CyberStation user determines which attributes are displayed, regardlessof the profile used to create the Personnel object.

If you edit a template that is already assigned to Personnel objects, any changes toinherited attributes will automatically be changed in the Personnel objects using thetemplate (Template content is displayed in the Personnel editor dialog rather than in thePersonnel Manager.). Changes to attribute values that are copied (not inherited) from thetemplate will not change in existing Personnel objects. New Personnel objects created



TAC 500

from the edited template will include the updated values for both inherited and copiedattributes.

Assigning Areas from Personnel Profiles and Templates

In the Personnel Manager, you can quickly assign areas specified in a profile or atemplate to a Personnel object. Any schedule points and clearance levels attached to theareas are also included in the Personnel object when you add the areas. Once in aPersonnel object, you can edit the areas list as needed for the individual.

Note: Area, schedule, and area clearance levels assigned to a Personnel object from a

profile or template using the Reset Access Rights button in the PersonnelManager completely replace any area information already in the Personnel object.

Creating a Personnel Profile

Use this procedure to create a personnel profile that defines the information that isentered and displayed for Personnel objects in the Personnel Manager.

Note: If you want Personnel objects created or edited using the profile to be associatedwith a personnel template, be sure to add the Template attribute to the Assigned Attributes list and select the template to use. For more information about creatingtemplates, see Chapter 12, Templates. If you want to be able to attach aSecurityLevel object to Personnel objects, add the SecurityLevel attribute to the Assigned Attributes list in the profile.

Store personnel templates in the Personnel Templates folder, which is a subfolder of theTemplates folder. Personnel templates stored elsewhere within CyberStation cannot beattached to Personnel profiles or objects.

Perform the following steps to create a personnel profile and specify its settings:

1. In the Personnel Manager, click the Configure button.


The Configure button is disabled unless a Personnel object is currently displayed inthe Personnel Manager.

2. In the Configuration dialog, click the New button.

3. In the New Profile dialog, enter a new profile name and a description (optional), andthen click OK.

4. In the Available Attributes list, select the attributes you want to include in your

profile, and then click the add attributes button ( ) to add the selected attributes tothe Assigned Attributes list.

You can select one attribute at a time, or select more than one by pressing the Ctrl or Shift key while selecting.

It is recommended that you always include First Name and Last Name in a profile,and make these attributes required entries.




5. Arrange the attributes in the Assigned Attributes list:

To remove an attribute, select it and click the remove attributes button ( ). Theselected attribute moves to the Available Attributes list.

To arrange the sequence of attributes in the Assigned Attributes list, select an

attribute, and click the up and down buttons ( , ) to move it within the list. Theorder you specify in this list determines the order in which the attributes are displayedin the Details tab when you add or edit a Personnel object using this profile.

6. Define the data entry properties of each attribute as needed.

Property Description

Required Check this checkbox to make an entry for this attribute required.

Read Only Check this checkbox to make this attribute value read only; thatis, not changeable. It is not recommended that an attribute beboth required and read only.

Default Enter a default value for this attribute.

Users can edit the value in Personnel objects created from theprofile if Read Only is not selected for the attribute and if thevalue is not inherited from a template.

7. Click the Assign Area button.

8. Expand UnAssigned, and check the checkbox next to each area that you want toassign.



TAC 502

9. Click the browse button next to Path for New Personnel, and select the folder whereyou want to save Personnel objects created from this profile.

Although it is not recommended, you can save Personnel objects in Root. If youselected a folder but want to select Root, click in the Path for New Personnel field,and press the Delete key or the Backspace key. Root is then displayed in the field.When you save the profile, you are prompted to confirm that you want to use Root.Click OK to continue.

10. Click OK.

Creating a Profile from an Existing ProfileUse this procedure to create a new profile by editing an existing profile and saving it witha new name:




2. In the Configuration dialog, select the profile that you want to edit.

3. Edit the profile as needed and click Save As.

4. In the New Profile dialog, enter a new profile name and description (optional), andthen click OK.

5. Click OK.

Assigning Areas, Schedules, and Clearance Levels to Profiles

Use the following procedures to assign specific areas, schedule points, and clearancelevels to a profile. When a new Personnel object is created from the profile, thisinformation is automatically included in the new object. Existing objects are not affectedby any changes to this information in the profile used to create the objects.

Note: The Configure button is disabled unless a Personnel object is currently displayedin the Personnel Manager.

Assigning Areas to Profiles

Use this procedure to assign one or more areas to a profile. For example, you may wantto assign only the lobby and cafeteria areas to the profile used to create Personnelobjects for visitors.


If the Personnel Manager is not open, you can double click any Personnel object inContinuum Explorer to open the Personnel Manager, and then click the Configure button.






4. In the Assign Areas dialog, expand UnAssigned.

5. Check the checkboxes next to the areas that you want to assign.

To remove access to an assigned area, clear the checkbox next to the area.

6. Click OK.

7. Click OK to save the profile.

Attaching Schedule Points to Profiles

Use this procedure to attach a schedule point to a specific area assigned to a profile.Schedule points are associated with schedules that define specific time periods when aperson can access that area. For example, you may want to allow contractors into thebuilding through the lobby only between the hours of 8 A.M. and 5 P.M.

You can attach only one schedule point to an area. However, you can attach the sameschedule point to multiple areas.





4. In the Assign Areas dialog, expand Assigned.

5. Expand the area to which you want to attach a schedule point.

6. Click the icon next to Add Schedule to display the Add Schedules dialog.

If needed, select the browse button next to Schedule Points Location, and locatethe folder or container with the schedule point you want to add.

7. Select a schedule point. Select one or more areas where you want to attach thisschedule point, and click OK.



TAC 504

8. Click OK.


Changing an Area Clearance Level in a Profile

Use this procedure to assign a clearance level to a specific area in a profile. When a newPersonnel object is created from this profile, the clearance level for the area is included inthe new object.

The predefined value for Clearance Level for all areas is zero, indicating that the valueentered for Default Clearance Level in the personnel attributes (shown on the Details tab)is the clearance level used for the area. If you want personnel to have access privilegesfor a certain area that are more or less restricted than the access provided by theperson's default clearance level, you can specify a different clearance level for that area.

If the security key attached to the CyberStation workstation is not configured to viewcondition levels, condition level and clearance level attributes and values are notdisplayed or configurable in CyberStation. For more information about clearance levels,see “Personnel Clearance Levels and Controller Condition Levels” earlier in this chapter.






4. In the Assign Areas dialog, expand Assigned.




5. Expand the area for which you want to change the clearance level.

6. Click the icon next to Clearance Level.

7. In the Clearance Level dialog, enter a new value, and click OK.

8. Click OK.


Assigning a Profile to a User

Use this procedure to assign a profile to a specific user. The user sees only the attributesdefined in the assigned profile when creating, editing, or viewing Personnel objects. Attributes that are not included in the assigned profile are not visible to the user.


If the Personnel Manager is not open, you can double click any Personnel object in

Continuum Explorer to open the Personnel Manager, and then click the Configure

button.


2. In the Configuration dialog, click the Assign Profile to User button.

3. In the User Profiles dialog, select a user from the Users list.

Users are listed alphabetically. Click the Users column heading to sort the list inascending or descending order.

4. Select a profile from the dropdown menu, and click OK.

5. Repeat steps 3 and 4 as needed to assign profiles to other users.

6. Click OK.

Deleting a Personnel Profile

Use this procedure to delete a profile from the Personnel Manager.




TAC 506

If the Personnel Manager is not open, you can double click any Personnel object inContinuum Explorer to open the Personnel Manager, and then click theConfiguration button.


2. In the Configuration dialog, select the profile that you want to delete.

3. Click the Delete button.

4. When prompted to confirm deletion, click Yes.

5. Click OK.

If the profile you deleted was assigned to any users, assign another profile to theusers as described in “Assigning a Profile to a User.” If you do not assign another profile, the profile selected in the configuration settings is used.

Customizing Personnel Attributes

Use this procedure to edit personnel attributes. You can change the attribute displayname, limit the values that can be selected, and create or edit a list of allowable valuesfor an attribute. The changes that you make to the attributes apply to all profiles andPersonnel objects that use the attributes.

The attributes Info1 through Info6 are user-definable. You can use them to capturepersonnel data that is specific to your company. For example, you can rename one of these attributes to First Responder with predefined values of Yes and No to identifyemployees to contact for assistance in emergencies.




2. In the Configuration dialog, click the Customize Attributes button to display theCustomize Attributes dialog.




3. In the Display Name column, edit attribute names as you want them to appear in thePersonnel Manager.

The Attribute column contains attribute names as they are defined in theCyberStation program. These names are not editable.

4. Check the corresponding Limit Allowable Values checkbox for each attribute whosevalues you want to limit.

If you select this option, users must select a value for the attribute from a dropdownlist whose entries you define. Users cannot enter values that are not in the list. For example, you can check the Limit Allowable Values checkbox for Department andthen enter a list of the departments in your company.

This option is available for attributes whose values are text strings. It is not availablefor attributes with numeric, date/time, or logical (True/False) values.

5. In the Edit Allowable Values column, click the blue button for the correspondingattribute to open the Edit Allowable Values dialog.

Note: If you did not check Limit Allowable Values for the attribute, the dropdown listyou create will not be displayed with the attribute when you create or edit aPersonnel object using this attribute.

6. Click in the Attribute Values field and enter the value(s) you want in the dropdownlist for this attribute.



TAC 508

When you start typing a value, a new line appears under your value. To add another value, press the Enter key.

To delete a value, check the Delete checkbox for that value. The value is deletedwhen you click OK. The value is not removed from any Personnel objects in which itis currently used.

7. Click OK to save the attribute values.

8. Click OK.

9. Click OK.

Selecting Configuration Settings for the PersonnelManager

Use this procedure to select the following settings for the Personnel Manager:

• Whether thumbnail images of personnel are displayed with search results

• The path for the card reader that you can use to read card information and display itin Personnel Manager

• The default paths for schedule points and new Personnel objects

• The profile that is used to display Personnel objects if no other profile is assigned to auser




2. In the Configuration dialog, select the Settings tab.




3. To display thumbnail images of personnel by default with search results, check theShow Thumbnails on startup checkbox.

You can also display or hide thumbnail images at any time in the Search Results tab.

4. To select a card reader that you can use to read card information in the PersonnelManager, check the Enrollment Reader checkbox and click the browse button.Select the Door object to which the reader is assigned, and click the Select button.

Note: The enrollment reader does not need to be physically connected to a door.

However, in CyberStation, you set up all card readers by entering their settingsin Door objects. For information about setting up a card reader, see Chapter 18.

5. Click the browse button for Schedule Location. In the Select Schedule Location dialog, select the folder or controller that contains schedule points for determiningwhen personnel can access specific areas, and click the Select button.

When you attach schedule points to areas in a profile or Personnel object, you canselect a different folder or controller, if needed.

6. Under Default Profile, select the profile that the Personnel Manager uses to displayPersonnel objects for any users who are not assigned another profile. The defaultassigned profile is Employee.

A personnel profile is a collection of settings that you can use to view existingPersonnel objects or to create new objects in the Personnel Manager. The profiledetermines what personnel data is visible to users. You can assign different profilesto different users as needed to prevent unauthorized access to sensitive personneldata. For more information, see “Assigning a Profile to a User.”

7. Click OK.



TAC 510

Personnel Import Utility

This topic provides an overview of the Personnel Import Utility, a table showing the entirestep-by-step data importing process, and links to specific functions in this utility —configuring and mapping data, previewing data, transforming data, and importing/savingdata.

What is the Personnel Import Utility?

In CyberStation, you have likely already used the Personnel Manager (or PersonnelEditor) and related editors to create and modify personnel accounts. However, in somecases, you may need to import third-party personnel data outside of an Andover Continuum system. The Personnel Import Utility allows you do so. The Personnel ImportUtility bridges the gap between other personnel databases and CyberStation personnelrecords by allowing you to import and upload personnel data in large amounts fromoutside the system. The Personnel Import Utility is also a conversion tool, as well as animport tool. It takes the "source" personnel attributes of non-CyberStation personnelrecords, and (via data filtering and special configuration files) converts them toCyberStation Personnel attributes.

Personnel Import Utility is a CyberStation application based on Active Directory. ActiveDirectory is a Microsoft Windows directory service that provides a unified view of complexnetworks. Active Directory is installed on a Microsoft Windows 2000 or Windows Server

2003 machine, known as the domain controller. CyberStation uses the LightweightDirectory Access Protocol (LDAP) to read and extract Active Directory user information.For more information on Active Directory and LDAP please see: What Is ActiveDirectory? and What Is the LDAP Protocol?.

Note: Your IT or system administrator is responsible for learning about and establishingthe Microsoft Active Directory service on a domain server. You must have thisMicrosoft service in order to use the Personnel Import Utility. For more informationon setting up Active Directory, please visit web sites such as these:

• http://www.serverwatch.com/tutorials/article.php/1474461

• http://www.windowsnetworking.com/articles_tutorials/w2ksvrin.html

• http://activedirectory.com

Note: You do not need to install anything on CyberStation to accommodate ActiveDirectory or LDAP; however the Personnel Import Utility is a separately purchasedoption, enabled via your CyberStation product key. It is launched from theContinuum task icon's popup menu, if you have a license. (See the import processbelow.)

Note: Throughout these topics, references to the Continuum Personnel editor can alsomean the Personnel Manager, depending on which one you are using.




What Can I do with the Personnel Import Utility?

The Personal Import Utility has many powerful features. With this application, you can:

• Define a folder location into which the transformed CyberStation Personnel objectswill be placed.

• Define an alias name and customize other attributes and constants.

Note: An alias has a limit of 16 characters an is usually made up of the following:

Any constant + FirstName

FirstName + LastName + SSN

• Add card types.

• Add site codes.

• Add personnel templates based on department.

• Specify a personnel template name to associate with Personnel objects.

• Add individual areas to a personnel record through a transformation file.

• Specify the number of records to view to avoid alias conflictions.

• View the Active Directory information before it is transformed.

• View the transformed data (the CyberStation Personnel object attributes) before theyare imported.

• Find disabled records.

• Use Windows Scheduler to define and schedule automatic personnel-record importoperations.

Import Process — the "Big Picture"

The following procedure presents the major steps you would typically perform to importpersonnel data using the Personnel Import Utility — an overview of the entire process.

1. Launch the Personnel Import Utility.

Right click on the Continuum icon in your tool tray, and select Personnel Import

Utility from the popup menu. This runs the CyberStation application,

PersonnelImportUtlity.exe, and the utility window appears.

2. Identify an Active Directory data source.

Specify a new path of the Active Directory domain server. (You do this from the Data

Source section of the Configuration tab.) In the Data Source section, you also

enter your User Name and Password to gain access to the domain server. (See

your IT or system administrator.)

3. Filter the number of personnel records you want to import.

If you do not want to import all records, you must filter the records according to the

specific criteria, such as record name, department, group, the time created or

modified, and so on. (You do this from the Filter Data Source section of the

Configuration tab.



TAC 512

4. Map the Active Directory data source attributes to the Continuum Personneleditor attributes.

When you lunch the Personnel Import Utility, attributes are automatically extracted

from a configuration file and populated in the mapping window of the Configuration

tab. In this mapping window, you can include, exclude, and add new attributes so

that they appear or do not appear in the imported Personnel records. For more

information on mapping attributes, see “Mapping Data Source Attributes to

Continuum Personnel Attributes” later in this chapter.

Note: When you launch the utility for the first time, data are extracted from a defaultconfiguration file, PersonnelImportUtility.exe.config. (You can enter your ownconfiguration file name when you save all configuration settings.) For moreinformation, see Step 8 below and the topic “Saving a Configuration andImporting Data into CyberStatioin.”

5. Edit your transformation file and specify the file name.

Use the browse button in the Transformation File Name field on the Configuration

tab to search for and edit the XSLT transformation file.

When you do this for the first time, you can open the default file,

PIUTransformation.xsl, which is located in:

Program Files\Continuum

or you may select your own XSLT file.

The XSLT file, written in xsl tag code, provides additional instructions that define and

customize personnel attributes in the transformation of personnel records. For

example, in this file it is recommended that you define an Alias name and define (or

accept the default for) the location of the folder into which imported personnel records

are stored.

Using this file, you can also modify mapped attributes, resulting in highly customized

records.

When finished, save your transformation file – either the default file or your own file. If

you choose, you can also rename the file and place it another directory.

6. Retrieve and preview your mapped data-source and transformed dataattributes.

You must look at the data-source and transformed data – that is, all the ActiveDirectory source attributes and the CyberStation Personnel attributes. (You do thisusing the Preview button on the Configuration tab. Source data attributes aredisplayed in the matrix on the Data Source Data tab. Transformed CyberStationPersonnel attributes are displayed in the matrix on the Transformed Data tab.)

Filter the number of records you want to preview using the Preview filters on theConfiguration tab.




7. Re-edit and apply transformation file, as needed.

If the transformed data in the preview are not to your satisfaction, repeat steps 5 and

6 until the attributes are the way you want them.

Excluding the first time, every time you edit your data in the XSLT transformation file,

you must click the Apply Transformation button to transform the data.

8. Save your configuration.

When you are satisfied with the mapped data on the Data Source Data tab and

Transformed Data tab, use the dropdown menu in the Configuration File Name field on the Configuration tab to select a configuration file, and then click the Save

Config File button.

Note: If you are configuring these settings for the first time, you must enter the nameof a configuration file in the Configuration File Name field, so that it is savedto the database. Subsequently, when users create/save additionalconfiguration files, they appear in this dropdown menu.

When you perform a save, all the settings on the Configuration tab are saved to the

CyberStation database. When you launch the utility again, following a save, these

saved settings populate all the sections of the Configuration tab.

9. Import the transformed records.

Only when you are satisfied with the entire Personnel Import Utility configuration,click the Import button at the bottom of the Configuration tab. A message box will

prompt you to import. Clicking Yes will execute the import operation and place new

and/or modified CyberStation Personnel records into the Personnel objects folder

that you specified.

10. View the Error Log.

After the import process is complete, you can view a CyberStation Error Log. This log

is located in:

Program Files \ Continuum \ PIUErrors290906161911 (this is PIUErrors + currentdate and time.

Errors are also stored in the ErrorEvent table in the CyberStation database.

11. As an option, schedule automatic imports.

As an option, you can use the Windows Scheduler to define and import automatic

personnel-record import operations at specific predefined times. (For more

information, see “Scheduling Automatic Personnel Object Updates.”)

The following is a flow chart that diagrams this entire process. Use this chart as a

quick reference to the import process procedure.



TAC 514




Configuration Tab - Personnel Import Utility

The Configuration tab is the first tab that appears when you open the Personnel ImportUtility. From this tab, you perform all operations, including:

• Filtering the records you want to import by different categories (name, department,group, or time)

• Previewing the data being imported, as well as the source data

• Creating and saving multiple configurations

• Locating disabled personnel• Mapping data source attributes to CyberStation personnel attributes

• Viewing the total number of filtered records and the total number of records that havesuccessfully been imported

• Transforming the data using the XSLT file (use the default or modify your own) to addor customize personnel attributes.

The following table describes the attributes on the Configuration tab.

Data Source Attributes

Attribute Description

Server Name The path of the Active Directory domain server, where the sourcepersonnel data to be imported resides.

The default server name is LDAP://testDC=test,DC=com.

The “test” next to “//” is the server name.

The “test” in “DC=test” is the domain name.

User Name Name of the user who can access the data source data on the ActiveDirectory.

Password The password that allows you to connect to the Active Directorydomain server.

Note: You will not be able to view or import your data unless youhave entered a valid user name and password. See you systemor IT administrator.



TAC 516

Filter Data source Attributes


All Records Select this radio button to get all the data source personnelrecords from the Active Directory domain server.

Filtered Records Select this radio button when you want to filter the data andget records based on record name, department, group,disabled records, and/or time.

By Record Name(Starts With)

Check this checkbox, then select Starts With from thedropdown menu to find all the users that start(s) with aletter(s). In Active Directory, a name is stored “FirstnameLastname.”

For example, to find “Tom Hanks,” type T or To or Tom.

This option is only enabled with Filtered Records is checked.

This is not case sensitive.

By Record Name(Is Exactly)

Check this checkbox, then select Is Exactly from thedropdown menu to find a user by typing her/her exact name.Exact name is “firstname space Lastname.”

This is not case sensitive.

This option is only enabled with Filtered Records is checked.

By Department Check this checkbox and enter a department name to get all





the users under that specific department. This option is onlyenabled when Filtered Records is checked.

By Group Check this checkbox and select a group from the dropdownmenu to get all the users under that specific group. Groupnames are provided from the Active Directory data source.This option is only enabled when Filtered Records ischecked.

To access the dropdown menu, you must first click in the field.

By Time Check this checkbox to get all the users created or modifiedduring that specific time period. This option is only enabledwhen Filtered Records is checked.

Created Select this radio button to get all the users created during thetime interval you supply, or by using a filter such as “LastHour,” “Last Week,” “Last Year,” “Last Month,” or “Last Run.”This selection works with the Time Filter dialog. See TimeFilter below. This option is only enabled when Filtered Records is checked.

The Last Run time is not updated until an import operationoccurs. It is only for an existing configuration.

“Last Run” is used for 2 cases:

• It gets the value when the last import occurred with thatconfiguration and the current time you are executing for the existing configurations. It searches within the timeframe.

• For new configuration or applications running without aconfiguration file, it takes the Start and End times as thecurrent time and you will not see any records.

Modified Select this radio button to get all the user modified during thetime interval you supply, or by using a filter such as “LastHour,” “Last Week,” “Last Year,” “Last Month,” or “Last Run.”

This selection works with the Time Filter dialog. See TimeFilter below. This option is only enabled when Filtered Records is checked.

The Last Run time is not updated until an import operationoccurs. It is only for an existing configuration.

“Last Run” is used for 2 cases:

• It gets the value when the last import occurred with thatconfiguration and the current time you are executing for the existing configurations. It searches within the timeframe.

• For new configuration or applications running without aconfiguration file, it takes the Start and End times as the



TAC 518


current time and you will not see any records.

Time Filter After selecting Created or Modified, click this button to launchthe Time Filter dialog and choose the time period in whichpersonnel records were created or modified. Records areretrieved strictly during the time you set. All times are adjustedto UTC.


Filter Select this radio button to select a timefilter (such as “Last Hour”) from thecorresponding dropdown menu.

Time Interval Select this radio button to select a Start time and an End time from thecorresponding dropdown calendars.

Disabled Records Check this checkbox to exclude all enabled users in the data.This option is only enabled when Filtered Records ischecked.

Preview Attributes





All Select this radio button to preview all records to beimported.

Some Select this radio button to preview only some of the usersbeing imported. The default number is 100. Accept thisnumber or enter your own number is the field provided.

Preview Click this button to see the results on the Data SourceData tab and, after the transformation is over, in the

Transformed Data tab. For more information on how topreview your data, see “Previewing Data” later in thischapter.

Other Attributes


Total Number of Filtered Records

This field shows how many records are to be importedbased on your filter settings.

Total Number of Imported Records

This field shows how many records have been importedafter the import process is complete or after you click theCancel button when an import operation is in progress.

Transformation FileName

This displays the path of the user-defined XSLT file after you have used the browse button to search for and selectthe file. This special file allows you to add and customizeattributes for the imported CyberStation personnel records.When you do this for the first time, you can open the defaultfile, PIUTransformation.xsl, which is located in:

Program Files \ Continuum

or open and edit your own file.

For more information on transforming your data and usingthe XSLT file, see “Transforming Data Using the XSLT File”later in this chapter.

ApplyTransformation Click this button to apply the changes in the XSLT file andsee the transformed data. For more information, see“Transforming Data Using the XSLT File” and theTransformed Data tab.

Configuration FileName

This is the configuration file (residing in the CyberStationdatabase) that contains all the saved settings of all sectionsof the Configuration tab. For the first time, enter a name inthis field; otherwise, use the dropdown menu to select oneof the existing files in the database. For more information,see “Saving a Configuration and Importing Data intoCyberStation.”

Note: If you click this button without entering anything in



TAC 520


the field, the Save Configuration dialog appears, askingyou to specify a name for the configuration file.

Map Data SourceAttributes toContinuumAttributes

In this window you see all the mapped data sourceattributes (Active Directory) and their correspondingCyberStation personnel record attributes. Mapping datasource attributes to CyberStation attributes allows you topick and choose attributes to be transformed. Theinformation that populates this window is extracted from thedefault configuration file. For more information onmanipulating attributes or adding more attributes, see“Mapping Data Source Attributes to CyberStation Personnel Attributes.”

Import Click this button to import your personnel records inCyberStation, only when the configuration is filled out toyour satisfaction. This is the last step to importingpersonnel. For more information on how to import your data, see “Saving a Configuration and Importing Data intoCyberStation.”

Cancel Click the button to cancel the operation at any time duringthe import/preview process.

Help Click this button to launch the Continuum help.

Mapping Data Source Attributes to CyberStation PersonnelAttributes

When you launch the Personnel Import Utility, it automatically extracts the attributes fromthe default configuration file and populates them on the Configuration tab in the windowentitled Map Data Source Attributes to Continuum Personnel Attributes. ActiveDirectory source attributes appear beneath the Data Source Attribute column, whiletheir CyberStation Personnel object counterparts appear in the Continuum PersonnelAttribute column.

Note: If you are doing this for the first time, data are extracted from a defaultconfiguration file supplied with CyberStation. You must subsequently specify thename of a configuration file (or select the name of an existing one) when you saveit.

This mapping window allows you to choose which attributes you want to include or exclude in your transformed personnel records. To include an attribute, check the box inthe Include column, in the row containing the attribute you want to include. To excludean attribute, either leave the checkbox blank or, if the box is already checked, remove thecheck from the box.




For example, if you want to include a person's name, but not his/her office telephonenumber, check these boxes:

givenname /First Namesn / Last Name

but do not check this box:

telephonenumber / Office Phone

In this mapping window, you may also use the dropdown menu (embedded in entrieswithin the Continuum Personnel Attribute column) to select another attribute tocorrespond with (or "map to") the data-source attribute. You do not need to accept thedefault mapping. Attributes in the dropdown menu represent those in CyberStationPersonnel objects.

You can further customize and add attributes by editing the XSLT file. For moreinformation, please see “Transforming Data Using the XSLT File.”

There are some rules to keep in mind when you’re mapping data source attributes toCyberStation personnel attributes:



TAC 522

• A single Active Directory attribute should not be mapped to more than oneCyberStation attribute.

• A single CyberStation attribute should not be mapped to more than one ActiveDirectory attribute.

• A single CyberStation attribute should be populated either by mapping an ActiveDirectory attribute or by specifying the attribute name as an XSLT tag, but not both.

• CyberStation attributes that are mapped to Active Directory attributes must alsoappear in the XSLT file's "copy-of select" list. (See sample XSLT file section for moreinformation.)

• The XSLT file should reference CyberStation attributes and not reference any ActiveDirectory attributes.

• When specifying CyberStation attribute names in the XSLT file, be aware thatCyberStation attribute names are case-sensitive (refer to table of Continuum attributenames for correct spelling).

• Through the use of XSLT tags, it is possible to set the value of one CyberStationattribute to the value of a different CyberStation attribute.

Attribute-mapping changes you make on the Configuration tab are saved with theconfiguration file.

The following table is a sample listing of data-source (Active Directory) attributes withtheir corresponding CyberStation Personnel object attributes. These are extracted from

the configuration file, but do not represent all the data-source attributes that reside on the Active Directory domain server.

Note: When the Active Directory server is also a Microsoft Exchange Server, ActiveDirectory stores 16 additional "extended" attributes that can map to ContinuumPersonnel attributes.

Previewing Data

Before importing transformed personnel records, you must preview your data via thePreview button, located on the Configuration tab. When previewing data, you can either preview all personnel by selecting the All radio button, or specify how many personnelrecords to preview by selecting Some. When Some is selected, the default number (100)is automatically filled in; however, you can enter another number.

Clicking the Preview button displays the data on the Data Source Data tab andTransformed Data tab. It is important to view your data first because you want to makesure everything is mapped correctly before you import all the data.

You should pay particular attention to the Alias attribute, since this attribute is the primarykey to the CyberStation Personnel creation mechanism. You should verify that all aliasesare unique and contain a value consistent with CyberStation naming conventions.

• Aliases need to be a maximum of 16 characters. The first character cannot benumeric, and the remaining characters are alpha, numeric, or one of "." or "_".

• The Personnel Import Utility will strip invalid characters and use the left-most sixteencharacters when creating an alias. Records with empty Alias values will not becreated.




If the aliases are not unique, subsequent records will be updated, rather than created.

If the personnel information is incorrect or you want to change something, you can goback to the Configuration tab, change it, then preview it again. You should alwayspreview your data before importing it.

If you make more changes, you must click the Apply Transformation button again inorder to display the changes. Personnel Import Utility will not make the changesautomatically.

Data Source Data Tab – Personnel Import Utility

When you click the Preview button on the Configuration tab, personnel information fromthe data source is displayed on the Data Source Data tab and the Transformed Datatab. The Data Source Data tab contains a table showing the raw data taken directly fromthe Active Directory domain server. These are the data source attributes.

Notice that these attributes are not the CyberStation attributes that you selected in theMap Data Source Attributes to CyberStation Attributes window on the Configurationtab. See “Mapping Data Source Attributes to CyberStation Personnel Attributes.”

In order to see the CyberStation attributes that you mapped on the Configuration tab,look at the Transformed Data tab.



TAC 524

Transforming Data Using the XSLT File

The XSLT file is a special user-defined file containing information that allows you totransform data-source attributes into CyberStation personnel record attributes. It isrecommended that this file, written in xsl tag language, define an Alias name. This filemust define the folder location where the transformed imported CyberStation Personnelobjects will reside. You can also use this file as a powerful data transformation tool,because you can add new attributes, as well as customize the existing attributes, so thatthey appear in the transformed Personnel records precisely the way you want them.

On the Configuration tab, using the browse button in the Transformation File Name field, search for and select your XSLT file. When you do this for the first time, you canspecify the default file that CyberStation provides — PIUTransformation.xsl, which islocated in:


or open and edit your own file.

Each time the file is changed, you must either apply the settings by clicking the ApplyTransformation button, or preview your data again by clicking the Preview button. Toview the updates, select the Transformed Data tab.

Note: You must preview your data at least once before clicking the ApplyTransformation button. Although the Apply Transformation button will be

enabled before you preview, an error message will inform you that you mustpreview your data first.

You can change this XSLT file using Notepad or other open-source tools, such as XRAY(http://www.download.com/xray-xml-editor/3000-72414-10166164.html) or Cook Top(http://xmlcooltop.com).

Uses of the XSLT File

You must use the XSLT file to:

• Define an owner folder location into which imported personnel records are placed (asContinuum Personnel objects).

• Add Area links (can be added only from the XSLT file)

• Have the attribute "State" in the "copy-of-select" list

You can also use this file to:

• Define the Alias name, which is used later to find that person in the database. Youshouldn't change this every time; it is a one-time process.

• Modify and customize attributes, as needed.

• Add attributes like Site Code, Card Name, and so on that may not be included inmapping, to supplement user information that comes from Active Directory.

• Convert the state names into two-character State abbreviations.

Refer to “Mapping Data Source Attributes to CyberStation Personnel Attributes” for a listof rules to keep in mind while mapping data source attributes to CyberStation personnelattributes.




Transformed Data Tab – Personnel Import Utility

When you click the Preview button on the Configuration tab, personnel information fromthe data source (Active Directory) is displayed on the Data Source Data tab. Likewise,the Transformed Data tab displays a table containing personnel attributes that willappear in the transformed CyberStation personnel records.

Note: If you specify another XSLT file, simply selecting a new file is not enough totransform the data; it does not transform automatically. You must click either theApple Transformation button or Preview button again.

The transformed data that appears on this tab represents the way you have:

• Mapped data source attributes to CyberStation personnel attributes.

• Filtered the records.

• Modified and customized your XSLT transformation file.

There are two important things to look for while viewing this tab:

• Each alias must be unique. If the aliases are not unique, subsequent records will beupdated with that record and a new record will not be created. (See “Saving aConfiguration and Importing Data into CyberStation.”) To verify this, when previewingyour data, make sure that every alias name under the "Alias" column is unique beforeimporting.



TAC 526

• Each person under the Owner Folder column must be assigned to a location. Thisattribute defines the folder where the record will reside in Continuum Explorer (for example, Root\Floor 1, Root\Lobby, and so on).

Remember, if you change the XSLT transformation file, you must click ApplyTransformation or the Preview button to update the information on this tab.

Saving a Configuration and Importing Data intoCyberStation

On the Configuration tab, after you have configured everything to your satisfaction, youcan save all your configuration settings in a configuration file.

For the first time, enter a name in the Configuration File Name field; otherwise, use thedropdown menu to select one of the existing files in the database. As users saveconfiguration files, and the files accumulate in the database, the names of these filesappear in the dropdown menu.

Note: When you enter the name of a configuration file — no file extension is required —or select one from the menu and click the Save Config File button, you receive the

following message: Do you want to read the Configuration of the Personnel

Import Utility from the selected Configuration file? Click Yes.

If you do not enter/select a filename, and click the Save Config File button, the SaveConfiguration dialog appears, asking you to enter a name in the field provided. Enter aname, and click OK.

When you save a configuration, all settings on the Configuration tab are saved — thefiltered data, server name, transformation file name, mapped attributes, and so on.(Remember, saving a configuration file does not save the information to the XSLT file —only to the configuration file.)

Importing Personnel Records into CyberStation

After clicking the Preview button, and only after being completely sure your data iscorrect, you should import your data into the CyberStation database as Personnelobjects.

To import data, click the Import button. When you click this button, a message boxappears asking "Do you want to Import data into Continuum?" Click Yes. A message window appears, showing the import progress — specifically, how manypersonnel records have been imported and how many there are left to import.

To stop this import process at any time, click the Cancel button. Canceling the importonly stops the process from importing more records. The records that have already beenimported are not erased from the database. For example, if you start to import 100records, and click the Cancel button halfway through, only the first 50 are imported.

On the Configuration tab, you are able to see the Total Number of Filtered Records(showing how many records to be imported based on your filter settings) and the Total




Number of Imported Records (showing how many records have been imported duringand after the import process).

Note: User accounts that are disabled in Active Directory will be disabled inCyberStation.

Error Logs and Activity Logs

After the import process completes, you can view a CyberStation Error Log. This log islocated in:

Program Files\Continuum\PIUErrors290906161911.txt (this is PIUErrors + current dateand time)

Errors are also stored in the Error Event table in the CyberStation database.

This lists the reasons why a record could not be imported. For example:

• You were unable to connect to the server.

• A duplicate alias was found.

• Incorrect user name and/or password was provided.

• An attribute was mapped incorrectly. (The log tells you the incorrect attribute.)

Along with the Error Log, the CyberStation Activity Log (Activity Event table in theCyberStation database) automatically tracks all user activities and logs all PersonnelImport Utility activities.



TAC 528

Some Activity Log information that could appear are:

• Personnel Import Utility started.

• Personnel Import Utility search started.

• Personnel Import Utility search ended.

• Personnel Import Utility Import into Continuum started.

• Personnel Import Utility Import into Continuum ended.

• Personnel Import Utility ended.




Managing

PersonnelDistribution

When personnel are assigned to areas and doors, their information is sent to the

controller hardware, where the doors are located. The act of sending this information iscalled distribution. Several things can get in the way of a clean distribution:

• The controller may be offline for some reason.

• The network may be down.

• There may be an error on the network during the distribution.

• The telephone line connecting a remote site to the main controller may be busy.

In all these cases, the distribution of a personnel object may not make it down to theproper controller immediately. Eventually, the distribution will go through, unless thememory capacity of the controller is exceeded. However, in the meantime, key personnelmay not be able to obtain entrance to the area.

Access Distribution ViewIn CyberStation, you may open a new Continuum application, the Access DistributionView , to display all distribution tasks (also known as distribution-event transactions) anddetermine their current status – that is, whether they have succeeded, failed, or are “inprocess.” The Access Distribution View is similar to the Active Alarm View and ActiveEvent View. Instead of active alarms and active events, the Access Distribution View listsactive personnel-distribution tasks.

The Access Distribution View is a powerful application. If necessary, you mayimmediately distribute a single personnel record, in any pending distribution transaction,to its proper controller. This is useful in urgent situations, when a personnel record mustbe sent to the controller but for some reason, such as those listed above, distribution isnot happening.

20



TAC 530

You may also designate multiple workstations to act as distribution servers. By havingmore than one workstation perform a distribution, there is less dependency on a singlePC. The workstations work together to assure that they do not perform multipledistributions of the same personnel object. The Access Distribution View displays theworkstation that is currently distributing or “handling” the distribution of any personnelobject. Distribution is enabled for every workstation, by default. To disable a workstation'sability to distribute records to controllers, set preference 19 (Enable personneldistribution to controllers on the LAN) and/or 20 (Enable personnel distribution toRAS networks) to FALSE on the Preferences tab of the Device editor for anyworkstation that should not be a distributing workstation. (See Chapter 14 for adescription of the settings on the Device editor’s Preferences tab.)

Using Continuum’s General Preferences dialog, you may also set the number of concurrent personnel distributions sent to controllers on each field bus network, as wellas set a time interval between these fieldbus distributions. This is done via GeneralPreference settings 12 and 13, as follows:

• Setting 12: Number of Concurrent Fieldbus Personnel Distributions — Thissetting is the number of concurrent personnel distributions that are sent from eachworkstation to controllers on each field bus network. The default (and minimum)value is 1. Maximum value is 4. This setting, which works in conjunction with setting13, improves performance by preventing or large numbers of personnel records fromflooding field bus controllers.

• Time Interval Between Fieldbus Personnel Distributions — This GeneralPreference setting is the amount of time (in milliseconds) that CyberStation waitsbefore it sends another personnel distribution to controllers on the same fieldbusnetwork. The default value is 30. Minimum value is 0. Maximum value is 15000 (15seconds). This setting, which works in conjunction with setting 12, improvesperformance by preventing large numbers of records from flooding field buscontrollers. It is also useful when there are many workstations performing accessdistribution. (That is, set it higher if there are many workstations.)

For more information on General Preferences, see the Continuum online help andChapter 13.




Launching and Populating the Access Distribution View

To launch and populate the Access Distribution View, please follow this procedure.

1. Double click the Distribution server icon located in your tool tray. The DistributionProperties dialog appears.

Note: For more information on the Distribution server, please see Chapter 2 or theContinuum online help.

2. Click the Access Distribution View button. The Access Distribution View Summary

appears.The summary view, which appears initially by default, displays the total number of transactions for each destination network, controller, door, or area based on thestatus of each transaction. That is, the summary view's columns display totalnumbers of each transaction, according to status — total failed, total successful, total“in process,” and so on. (See Using Columns in Access Distribution View , later inthis chapter.) Here is an example of the summary view:

If you wish to switch from summary view to full view (where individual transactionsare listed, instead of totals) go to step 3, and apply a filter.

Note: In order to use the Distribute Now function, you must switch to full view andapply a filter.

3. Switch from summary view to full view.

Select Edit filters from the Filters dropdown menu. The Filter dialog appears.

4. In the Filter dialog, remove the check from the Summary view checkbox, and applya filter. (See Filtering Distribution Events in Access Distribution View , next.)

Note: In summary view, Filter dialog attributes are not selectable, except twodestinations, Network and Controller .

5. Click OK. The full Access Distribution View appears.

6. Select Refresh from the View menu, or click the refresh button icon in the toolbar.

Note: Access Distribution View remembers your filter settings and launches in fullview at your next session.



TAC 532

Filtering Distribution Events in Access Distribution View

From the Filters dropdown menu, select Edit Filters. Via the Filter dialog, you mayselect certain criteria based on destination, personnel, and status, to display specifictypes of distribution-event transactions in the Access Distribution View. For example, youmay choose to see transactions for one person, for one area, for one controller, for failedtransactions, and so on. Filtering the list greatly narrows your search for anomalies.

Note: When you launch the Access Distribution View initially, the Access Distribution

View Summar y appears. To switch from summary view to full view, remove thecheck from the Summary view checkbox at the top of the Filter dialog. Thesummary view lists the total number of transactions for each destination, basedon the status of each transaction. The full view lists the actual, individualtransactions, instead of totals. You must apply a filter in order to use theDistribute Now feature. (See Launching and Populating the Access DistributionView , earlier in this chapter.)

Access Distribution View remembers your filter settings. Therefore, these settings areapplied in the full view in your next session.

The Filter dialog has three general types of filters:

• Destination

• Personnel

• Status

Destination Filter

Filter Description

Network Select the Network radio button, and click the browse button in theNetwork field, to search for and select a Network object. This displaysonly the transactions occurring in the selected network.

From the Browse dialog, use the dropdown menu in the Objects of type field to select Network. No other object class is selectable.

Highlight the network you want, and its name appears in the Objectname field. Click the Select button to select that network and dismiss the

Browse dialog. The Network object name appears in the Network field. As an option, you can apply an area to the selected network. (See Area,below.)




Controller Select the Controller radio button, and click the browse button in theController field, to search for and select an InfinityController or InfinityInfinetCtlr object. This displays only the transactions that arecontrolled by the selected controller.

From the Browse dialog, use the dropdown menu in the Objects of type field to select InfinityController to make just Infinity controllers selectable,select InfinityInfinetCtlr to make only Infinet controllers selectable, or select All classes to make them both selectable.

Highlight the controller you want, and its name appears in the Objectname field. Click the Select button to select that controller and dismissthe Browse dialog. The controller object name appears in the Controller field.

As an option, you can apply an area to the selected controller. (See Area,below.)

Door Select the Door radio button, and click the browse button in the Door field, to search for and select a Door object. This displays only thetransactions occurring at the selected door. From the Browse dialog, usethe dropdown menu in the Objects of type field to select Door. No other object class is selectable.

Highlight the door you want, and its name appears in the Object name

field. Click the Select button to select that door and dismiss the Browse dialog. The Door object name appears in the Door field.

As an option, you can apply an area to the selected door. (See Area,below.)

Note: You may deselect any and all radio buttons in the Destination filter section.You need not select any Destination radio button.

Area Check the Area checkbox, and click the browse button in the Area field,to search for and select an Area object. This displays only thetransactions that are happening in the selected area.

Note: You may select an area as a sole destination, or you may select anetwork, controller, or door, and then select an area with which toassociate it.

In the Browse dialog, use the dropdown menu in the Objects of type toselect Area. No other object class is selectable.

Highlight the area you want, and its name appears in the Object name field. Click the Select button to select that area and dismiss the Browsedialog. The Area object name appears in the Area field.

Personnel Filter

Filter Description

No PersonnelFilter

Select this radio button when you do not want to apply any personnelfilter, thereby allowing any personnel record to appear in the list of transactions.



TAC 534

Browse for Personnel

Select this radio button, and click the browse button in this field, tosearch for one personnel record that you wish to appear in the list of transactions. This path of this person's personnel record objectappears in this field.

Use filtersbelow

Select this radio button when you want to apply a filter, rather thanspecifying a personnel record. You may apply a filter according to:First Name, Last Name, Department, and Card Number , describedbelow.

First Name Check the First Name checkbox, and enter the first name in the field.

Select the Exact match radio button, and enter a complete first name,if you want to display transactions for all persons who have this firstname.

Select the Starts with radio button, and enter a string of characters, if you want to list transactions for all persons whose first names beginwith these characters. For example, if you enter KE, the filter findsmatches with persons named Kenneth, Kendra, Kelly, Kevin, and soon. Click OK to apply the filter.

Last Name Check the Last Name checkbox, and enter the last name in the field.

Select the Exact match radio button, and enter a complete last name,if you want to display transactions for all persons who have this last

name.

Select the Starts with radio button, and enter a string of characters, if you want to list transactions for all persons whose last names beginwith these characters. For example, if you enter SIMON, the filter findsmatches with persons with last names such as Simon, Simone,Simonson, Simonetti, and so on.

Click OK to apply the filter.

Department Check the Department checkbox, and enter the department name inthe field.

Select the Exact match radio button, and enter a completedepartment name, if you want to display transactions for all persons in

this department.

Select the Starts with radio button, and enter a string of characters, if you want to list transactions for all persons whose department namesbegin with these characters.


Card Number Check the Card Number checkbox, and enter the card number in thefield, to display transactions for the person who holds this cardnumber.





Status Filter

Filter Description

Success Check this checkbox to display successful transactions.

Failed Check this checkbox to display failed transactions.

In Process Check this checkbox to display transactions that are locked by aworkstation.

Available Check this checkbox to display transactions that are waiting to be

processed.

Controller out of service

Check this checkbox to display transactions that are ignored becausethe controller is out of service.

Note: For each transaction listed in the Access Distribution View, the Status columndisplays an icon that indicates one of these status conditions. For a description of these icons, please see Using Columns in the Access Distribution View , next.

Using Columns in the Access Distribution View

Like the Active Alarm View and Active Event View, the Access Distribution View lists itsinformation across many columns. As with the other views, you may add and hide thesecolumns in the Access Distribution View. You may also rename, resize, move, and

change the sort order of columns.

Note: You cannot add/hide columns in the summary view.

Use the following procedure to add or hide a full-view column.

1. In the full view, select Add/Remove Columns from the View menu.

The Add/Hide Columns dialog appears, showing you all the columns that areavailable in the Access Distribution View.

2. Check the column's checkbox to show this column in the view. Remove the check tohide the column.

3. Click OK in the Add/Remove Columns dialog to apply the change and add/hide thecolumn.

Note: You may also right click a column heading and select Add or Hide from thepopup menu. When you select Add, the Add/Hide Columns dialog appears. Inthis case, go to step 2. When youselect Hide, the column over which you have right-clicked is immediatelyremoved from the view.

For information on how to rename, resize, move, and change the sort order of columns,please see Organizing Information in Chapter 10, Configuring Alarms, and apply thatinformation to the Access Distribution View window.

See also: Changing Alarm Sort Order in Chapter 10. In the Continuum online help,please see the following topics: Organizing Information in the Active Alarm View , as wellas Changing the Sort Order , Understanding Sort Order , and Sorting in Ascending or Descending Order.



TAC 536

Full View Columns

The following table describes the information that appears in the columns of the full Access Distribution View. Here is an example of the full view:




Column Description

Status Shows the current status of the distribution-event transaction.Status conditions that appear in this column (along with their status icons) can be one of the following:

Status andStatus Icon

Description

Success

The transaction has completedsuccessfully.

Transactions can be personnel downloads,personnel deletes, or special transactionsthat set the controller out of "NoDatabase"mode after a reload.

Failed

The last attempt to process the transactionhas failed.

Transactions are degraded based on thenumber of consecutive failures, following anumber of retries. This means transactionsthat continue to fail are retried less often.This is done by setting the Next Retry.

In Process

A workstation has "locked" the transactionand is processing it.

The lock expires after a certain amount of time if the workstation has not unlockedthe transaction. (The default is 5 minutes.)Workstations do not process transactionsthat are locked by other workstations.

Available

The transaction needs to be processed.

This is the result of personnelmodifications, controller reloads, door/areaadditions, and so on.

Controller out of

service

The transaction is ignored because thecontroller is out of service.

Destination Displays the path of the controller to which the information isbeing distributed.

Area Displays the path of the area to which the person has access.

Department Displays the department of the person.

Door Displays the path of the door through which access is beingattempted.



TAC 538

Column Description

Personnel Displays the name of the person whose personnel record isinvolved in the distribution transaction.

Card Number Displays the card number of the person.

Card Type Displays the type of card that was specified (via the Personneleditor when the personnel record object was established) for theperson.

Site Code Displays the site code that is encoded on the card belonging tothe person.

Last Error Displays the text of the system error occurring in the most recent(or current) transaction. If the most recent transaction is asuccess, then the word "Success" appears.

Next Retry Displays the date and time of the next attempt to process thetransaction.

Each time a transaction fails, the failure count is incremented.The "next retry" time is based on the number of failures. Thetransaction is tried less and less frequently as this number of failures increases. For example, the Next Retry time is 10minutes from the current time for the first failure, 20 minutes for

the second failure, 40 minutes for the third failure, 80 minutes for the fourth failure, and so on. This ensures that reoccurringunsuccessful transactions do not have a negative impact on thesystem.

Priority Displays either Low or High for the transaction.

A Low priority denotes the "normal" operation of the distributionprocess. In an emergency situation (for example, when someoneis waiting to get into a building) an administrator may click theDistribute Now button to elevate the priority to High. This doesnot necessarily distribute immediately, but high-prioritytransactions are processed before low-priority transactions. This

is useful when a large distribution is occurring.

Transaction Type Displays the current type of transaction, which can be one of thefollowing:

• Update — Indicates that a new or modified personnel recordis being downloaded to the controller. See the status of thisdownload transaction in the Status column.

• Delete — Indicates that a personnel record is being deletedfrom the controller. See the status of this delete transactionin the Status column.

• AccessModeNormal — Indicates that the controller has justcompleted the reload of its database, and personnel records




Column Description

are being re-distributed to the controller, after its reload, torepopulate personnel in the controller. The transaction isresponsible for setting the SystemStatus variable back toNormal.

Number of Failures Displays an integer indicating the number of failed distributionattempts, including "retries."

Locking

Workstation

Displays the workstation that is currently processing or

"handling" the transaction, regardless of the status. If the lockingworkstation goes down, the lock on the transaction expires,allowing another workstation to process the transaction.

Summary View Columns

The summary view displays the total number of access-event transactions (an integer) for each destination — network, controller, door, or area, based on the status of eachtransaction. Summary view columns are:

Destination

Total Failed

Total Available

Total In Process

Total Successful

Total Out of Service



TAC 540

Using Toolbar Buttons in Access Distribution View

The following table describes the toolbar button icons in the Access Distribution View.

Button Description

DistributeNow

Opens the Pending Access Distribution dialog, which allowsimmediate distribution. This resolves a person's attempt to access anarea. (See Distributing Personnel Immediately –Distribute Now , next.)

Refresh

Refreshes the list so that information is up-to-date. (You may alsoselect Refresh from the View menu.)

Sort

Enables the column sort function. (You may also select Sor t from theView menu.)

The sort function works like the sort function in the Active Alarm Viewand the Active Event View. (Please see Using Columns in the AccessDistribution View , earlier in this chapter.)

Help

Opens the online help system. (You may also select Contents fromthe Help menu.)

Right-arrowand left-arrow

buttons

Displays the next "page" in the view, when the list of transactions islonger than the length of the window.

Note: The page status line at the bottom of the view (Page x of x) tellsyou what "page" you are currently viewing in a long list.

Click the inner right-arrow button to move to the next page. Click therightmost button to view the last page. Likewise, click the inner left-arrow button to view the previous page and the leftmost button to viewthe first page.

Note: You may move the Distribute Now, Refresh, Sort, and Help buttons as onetoolbar. Click and hold the left edge of the Distribute Now button, and drag thetoolbar to the desired location.

Click and drag the arrow buttons as one toolbar in the same way.

Distributing Personnel Immediately — Distribute Now

For any pending distribution-event transaction listed in the Access Distribution View, youmay immediately distribute a personnel record (representing the person who has accessan area) to a controller on the local area network (LAN) and/or a remote access services(RAS) network.

Note: Distribution is enabled for every workstation by default. To disable a workstation'sability to distribute records to controllers, set preference 19 and/or 20 to FALSE onthe Preferences tab of the Device editor for any workstation that should not be a




distributing workstation. (See Chapter 14 for a description of the settings on theDevice editor’s Preferences tab.)

Note: You cannot use this Distribute Now feature while in the summary view.

To distribute personnel using Distribute Now, follow this procedure.

1. In the full Access Distribution View, highlight the pending transaction.

2. Click the Distribute Now button in the toolbar, or double click any transactionlisted in the view.

The Pending Access Distribution dialog appears. For example:

Note: The Distribute Now button is enabled in the toolbar only when both the

personnel and controller object IDs are present. Both are needed to performthe distribution.

3. In the Pending Access Distribution dialog, make sure the person that appears inthe Personnel field is the one that you wish to distribute to the controller that appearsin the Controller field. If this is not the right person or controller, click Cancel todismiss this dialog.

Make sure information in the Door and Area fields is also correct.

4. If this is the right person and controller, click the Distribute Now button.

The personnel record is immediately distributed to the controller.

5. In the Access Distribution View, select Refresh from the View menu (or click therefresh button) to refresh the information in the window.

In the Status column, the status icon of this event is changed.



TAC 542




Managing

ConfigurationFiles

Overview

Continuum's file management system offers a powerful suite of features that manage

configuration information for BACnet devices. You can automatically back upconfiguration information from the BACnet device to your database, as well asautomatically restore it from the database to the device. The configuration informationresides in a special configuration file, which is stored as an object — the BACnet classobject, File. You can also archive it locally in a text file (ASCII dump .dmp file.)

Backup Capabilities

Specifically, file management backup features allow you to:

• Back up the configuration information (stored in a special File object called ACCConfiguration in Andover Continuum) for a single BACnet controller and save itto your Continuum database.

• Back up configuration information for multiple controllers (also stored in

ACCConfiguration files, each in its respective controller) and save the information for multiple controllers to your Continuum database.

• Back up configuration information from the database and archive it to a text

• (ASCII dump) file.

• Simultaneously back up a controller's configuration information to the database andcopy (archive) it to a text (ASCII dump) file.

Note: You perform these operations via either the right-click container popup menu inContinuum Explorer's navigation pane or the Backup/Restore tab in the Deviceeditor for that controller. For detailed information on backup operations, please seeBacking Up a Device's Configuration and the Device editor's Backup/Restore tab,Chapter 14.

21



TAC 544

Restore Capabilities

Specifically file management restore features allow you to:

• Restore configuration information from your database to a single BACnet controller.

• Restore configuration information from your database to multiple controllers.

• Restore the archived configuration information (contained in the text ASCII-dump file)to your database.

• Simultaneously restore the archived configuration information (contained in the text ASCII-dump .dmp file) to your database and to the controller.

Note: You perform these operations via either the right-click container popup menu inContinuum Explorer's navigation pane or the Backup/Restore tab in the Deviceeditor for that controller. For detailed information on restore operations, please seeRestoring a Device's Configuration and the Device editor's Backup/Restore tab,Chapter 14.

The File Object

When a backup operation (or send-to-database operation) is performed for a BACnetdevice, a File object (a BACnet class object) is created. This object, which is stored in theFile object class folder residing in its respective BACnet controller. It containsconfiguration information for objects residing on the controller.

Note: The number and names of these files and file names are determined by individualBACnet devices (Andover Continuum vs. third-party). On Andover Continuumdevices, the name of this file is ACCConfiguration.Because the BACnet File object is implemented in Continuum, this object has anobject editor consisting of two tabs: General and SecurityLevel. The General tabdisplays information about the file properties of the ACCConfiguration file.

General Tab

The File editor's General tab displays information about the file properties of the ACCConfiguration file.

Note: The General tab is read-only. You cannot change the values in its fields.

The following table describes the read-only attributes of the General tab. For moreinformation on these attributes, see the File object type section in the BACnet Standard.


Description This field is typically blank. However, if some third-partyBACnet devices support the Description property for the Fileobject, then the content of the description appears in this field.

Last Changed Displays the date/time that the configuration file was lastmodified.

Type Displays the class object type, File.





Size Displays the size of the file. The size changes whenever thefile is modified.

Access Method Displays either Stream_Access or Record_Access.

Record Count Displays the size of the file in records. This is displayed onlywhen AccessMethod is Record_Access.

Archive This box is checked if this is an archive file in the device.

Read Only This box is checked by default.

Backing Up a Device’s Configuration

File-management backup operations, listed below, are performed via the container popupmenu in Continuum Explorer's navigation pane and/or via the Backup/Restore tab in theDevice editor for that controller:

• Back up configuration information (stored in a special File object called ACCConfiguration) for a single BACnet controller and save it to your Continuumdatabase. (See the procedures below.)

• Back up configuration information for multiple controllers (also stored in

ACCConfiguration files, each in its respective controller) and save the information for multiple controllers to your Continuum database. (See the procedures below.)

• Back up configuration information from the database and archive it to a text (ASCIIdump) file. (See Backup/Restore tab of the Device editor, Chapter 14.)

• Simultaneously back up a controller's configuration information to the database andcopy (archive) it to a text (ASCII dump) file. (See Backup/Restore tab of the Deviceeditor, Chapter 14.)

Note: Backup/restore operations are not supported in the context menu if the devicedoes not support the BACnet property, AutomaticReadFile. Backup/restoreoperations are not supported on the Backup/Restore tab of Device editor if thedevice does not support the BACnet property BackupFailureTimeout.

ProceduresBacking up a single device — To back up a configuration for a single device, performthe following procedure:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the controller whose configuration information you want to back up.

2. Right click over the device, and from the popup menu select Backup BACnetDevice.

For Andover Continuum BACnet controllers, the backup operation begins and theDistribution Properties dialog appears, showing the progress of and informationabout the operation. (For more information on the Distribution Server and theDistribution Properties dialog, see Chapter 2.)



TAC 546

For some third-party BACnet controllers, you are first prompted to enter a password.If the password is accepted, the operation begins.

Backing up multiple devices — To back up configurations for multiple devices, performthe following procedure:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the controllerswhose configuration information you want to back up.

2. In the navigational tree, click the parent container containing the desired devices, sothat those controllers appear in the viewing pane.

For example, the parent container could be BACnet Devices or any BACnetcontroller that contains sub-devices.

3. Highlight (select) two or more controllers in the viewing pane.

4. Right click over the highlighted controllers, and from the popup menu select BackupBACnet Device.

For Andover Continuum BACnet controllers, the backup operation begins and theDistribution Properties dialog appears, showing progress messages about thestatus of the operations. For multiple controllers, information is backed up onecontroller at a time. The progress messages tell you when the backup operationfinishes for one controller and begins for the next. (For more information on theDistribution Server and the Distribution Properties dialog, see Chapter 2.)


Backing up all devices on a BACnet Network — You can back up configurations for alldevices residing in a BACnet network by right clicking over a BACnet Network folder:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the blueBACnet Network folder that contains the devices whose configurations you want toback up.

2. To back up all the devices contained in the Network, right click over Network folder,and from the popup menu select Backup BACnet Device.

To back up two or more controllers selectively (but not all of them), in the navigationtree, click the Network folder so that its controllers appear in the viewing pane. In the

viewing pane, highlight (select) the controllers you want to back up.

For Andover Continuum BACnet controllers, the backup operation begins and theDistribution Properties dialog appears, showing progress messages about thestatus of the operations. For multiple controllers, information is backed up onecontroller at a time. The progress messages tell you when the backup operationfinishes for one controller and begins for the next. (For more information on theDistribution Server and the Distribution Properties dialog, see Chapter 2.)





Restoring a Device’s Configuration

File-management restore operations, listed below, are performed via the container popupmenu in Continuum Explorer's navigation pane and/or via the Backup/Restore tab in theDevice editor for that controller:

Specifically file management restore features allow you to:

• Restore all configuration information from your database to a single BACnetcontroller. (See the procedures below.)

• Restore configuration information from your database to multiple controllers. (See theprocedures below.)

• Restore the archived configuration information (contained in the text ASCII-dump file)to your database. (See the Backup/Restore tab of the Device editor, Chapter 14.)

• Simultaneously restore the archived configuration information (contained in the text ASCII-dump file) to your database and to the controller. (See the Backup/Restoretab of the Device editor, Chapter 14.)

Note: Backup/restore operations are not supported in the context menu if the devicedoes not support the BACnet property, AutomicReadFile. Backup/restoreoperations are not supported on the Backup/Restore tab of Device editor if thedevice does not support the BACnet property BackupFailureTimeout.

ProceduresRestoring to a single device — To restore a configuration to a single device, performthe following procedure:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the controller whose configuration information you want to restore.

2. Right click over the device, and from the popup menu select Restore BACnetDevice.

For Andover Continuum BACnet controllers, the restore operation begins and theDistribution Properties dialog appears, showing the progress of and informationabout the operation. (For more information on the Distribution Server and theDistribution Properties dialog, see Chapter 2.)


Restoring to multiple devices — To restore configurations to multiple devices, performthe following procedure:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the controllerswhose configuration information you want to restore.

2. In the navigational tree, click the parent container containing the desired devices, sothat those controllers appear in the viewing pane.

For example, the parent container could be BACnet Devices or any BACnetcontroller that contains sub-devices.



TAC 548

3. Highlight (select) two or more controllers in the viewing pane.

4. Right click over the highlighted controllers, and from the popup menu select RestoreBACnet Device.

For Andover Continuum BACnet controllers, the restore operation begins and theDistribution Properties dialog appears, showing progress messages about thestatus of the operations. For multiple controllers, information is restored onecontroller at a time. The progress messages tell you when the restore operationfinishes for one controller and begins for the next. (For more information on theDistribution Server and the Distribution Properties dialog, see Chapter 2.)


Restoring to all devices on a Network — You can restore configurations to all devicesresiding in a BACnet network by right clicking over a BACnet Network folder:

1. On the BACnet side of Continuum Explorer's navigational pane, locate the blueBACnet Network folder that contains the devices whose configurations you want torestore.

2. To restore all the devices contained in the Network, right click over Network folder,and from the popup menu select Backup BACnet Device.

To restore two or more controllers selectively (but not all of them), in the navigation

tree, click the Network folder so that its controllers appear in the viewing pane. In theviewing pane, highlight (select) the controllers you want to restore.

For Andover Continuum BACnet controllers, the restore operation begins and theDistribution Properties dialog appears, showing progress messages about thestatus of the operations. For multiple controllers, information is restored onecontroller at a time. The progress messages tell you when the restore operationfinishes for one controller and begins for the next. (For more information on theDistribution Server and the Distribution Properties dialog, see Chapter 2.)





Creating

Groups

What is a Group?

A group is an object used to monitor other objects. Each group has its own list of objectsknown as “members.” Members can be objects from any class, and one group can have

members from different classes. Typically, you’ll create a member list by adding objectsthat have something in common. For example, you could create a group that monitors allthe objects stored on a particular controller. Similarly, you could use a group object tomonitor all the objects pertaining to a particular function, such as air handling or security.

Group objects provide three ways to monitor objects:

• You can view a group’s member list. The member list displays the name, class, andvalue of every object in the member list. For groups that consist entirely of personnelobjects, the member list displays the last name, first name and middle initial of theindividual, the last known location of the individual, and personnel object name.

• You can view a graph the group’s first 15 points. The graph plots logged values.

• You can view a history of the object values. The history displays a list of all the points

in the group, and the values logged for them over a particular period.

When creating a group, you’ll work with the group editor to build or modify its member list,and you make choices that will configure the group’s graph and history views.

22



TAC 550

What is a Graph?

The graph view plots logged values for a point, or the first 15 points and/or systemvariables in a group’s member list. You’ll see a vertical scale to the left of the graph. Along the bottom, you’ll see a horizontal line delineated by time periods. In most cases,you’ll see a horizontal scroll bar that allows you to move left and right along the time line.The vertical scale and the horizontal time line are also known as the vertical axis andhorizontal axis, respectively. The body of the graph displays one line for each point. Tothe right of the graph, you’ll see a legend. The legend lists the names of the points, each

in different color. The color of the point name matches the color of its respective line inthe graph.

Reading Graphs

Graphs differ from histories in that they depict trends as well as actual point values. For example, it’s easy to see whether temperatures tend to rise at noon. Simply find 12:00PM in the horizontal time line, then look at the lines above its tick mark in the body of thegraph. Do they spike up, or drop down? In a history view, you would have to compare allthe point values in the 12:00 PM row against values in other rows to retrieve the sameinformation.

As with a history view, a graph view also provides specific point values for specific times.To locate a point’s value, find the time you want in the horizontal axis. Next, imagine avertical line going from the time’s tick mark to the line that represents the point in which

you are interested. Finally, imagine a horizontal line going from the line to the verticalaxis. The value located where the horizontal line intersects the vertical axis is the value of the point for that particular time.

Working With Multiple Scales

A graph can be set up to use more than one scale. When points to be graphed usedifferent units (Deg F, CFM, Square Meters, etc.) multiple scales allow one graph to plotthe values for all. Graphs that use multiple scales display only one scale at a time. You’llknow that a graph uses multiple scales if the scale’s color matches the color of the firstpoint in the legend. That means the graph is currently displaying the scale for that point.To switch to another scale, use one of these methods:

• Click the scale to change its color and scale values. The scale will change to

according to the order of the points in the legend. Keep clicking until the scale’s color matches the color of the point whose scale you would like to see.

• Click a point name in the legend. This changes the scale color and the scale valuesto match the point on which you click.




What Are Automatic Logs?

Automatic logs are record-keeping devices that can be set up for every kind of pointexcept DateTime and String. There are four types of automatic logs:

• LogInstantaneous – Continuum stores the current value of points at the beginningof every interval.

• LogAverage – Continuum calculates average point values over every interval, usinga weighted average algorithm. Average values are stored at the end of every interval.

• LogMinimum – Continuum compares all values over an interval, and finds theminimum value. Minimum values are stored at the end of every interval.

• LogMaximum – Continuum compares all values over an interval, and finds themaximum value. Maximum values are stored at the end of every interval.

Log intervals determine how often to record the point value. These intervals are specifiedin the point’s editor, on the Logs tab. Logs store values in an array that group views useto create histories and graphs.

Using the Group Editor

The Group General Tab

You use the General tab to set up data sampling parameters for the group you are

configuring.



TAC 552

Description The text you enter in this field appears as the title of the graph andhistory of your group.

Default View Select the view of the group that you want to appear when you openthe Group object with the SHOW command.

Default TimeRange

Enter the Days, Hours or Minutes to specify what period of time your group graph or history will sample. For example, if you enter 1 hour,the group monitors group members for one hour. The time rangeselected on this tab does not affect the starting and stopping time for the group. These values are specified by you when you open a Historyor Graph view.

Member ListRefresh Rate

This is the polling rate. Enter the interval in seconds at which you wantthe system to update values for your group. Members will only berefreshed when the Member List is shown.

PersonnelOnly Member List


The Member List Tab

The Member List tab lets you add objects to or delete them from the group. You click theAdd button to browse for objects to add to the group. Remember, graph and history

views display only point objects that have automatic logs set up for them. From this tabyou can right-click any object in the list and select any of the following options:

• Open

• Edit

• View History or View Graph

• Send To Controller or Send To Text File

• Rename

• Properties

Use the Member List tab to add and delete members. You can also look the properties

for each member.Adding Members – To add a member, click the Add button. This displays a Browse dialog to help you locate the object you want. You can also add members by dragging theobjects from the viewing pane of the Explorer into the open member list. After you havefound the object you are looking for, select it, then click the Select button. When addingobjects, keep these points in mind:

• Graph and history views display only point objects that have automatic logs set up for them.

• If you are creating a group consisting entirely of Personnel objects, select PersonnelMembers Only on the General tab to insure that the member list displays theappropriate attributes.




When you add folder, ListView, or group objects, all the objects contained by or listedin these objects are added to the group as well.

Deleting Members – To delete a member, click it, then click the Delete button.

Viewing Member Properties – To view a member’s properties, click it, then click theProperties button.



TAC 554

The Graph Tab

This is the tab you use to set up the parameters of the graph view of this group. Use theGraph tab to configure the scale that will be used to plot the first 15 point values in themember list. Note that only points with automatic logs set up for them will be graphed. Tocomplete this tab, you’ll perform the following tasks:

Scale of VerticalAxis

Singular Scale: Use the Singular Scale option if all your points use thesame units.

Multiple Scale: Use the Multiple Scale option if you have a group of objects with different units.

VerticalAxis Scale

If you are using a single scale, you will need to define the vertical axis. Thevertical axis displays a range for the point values in your member list.

Top Enter the number that will show on the graph view as top of scale.

Bottom Enter the number that will show on the graph view as bottom of scale.

Units Enter the Unit nomenclature that will show as the label for the vertical axis,for example, Deg F.




The History Tab

Use the History tab to configure how the automatic log data for the objects in the groupwill appear in the group view:

DisplayHistoryValues

This view displays two types of values, actual and fill. Actualvalues are taken from automatic logs at the intervals defined for each log. Fill values occur at the interval defined by the TimeBetween Rows setting.



TAC 556

Filling Type Select the option for filling in values between the logged valueson the History chart. The history view displays two types of values: actual and interim.

Actual values are taken from automatic logs at the intervalsdefined for each log.

Interim values occur at the interval defined by the Time BetweenRows setting. If the Time Between Rows setting matches theautomatic log interval, all the values displayed are actual values.In most cases, however, the Time Between Rows setting is lessthan the log interval.

For example, the time between rows could be set to 10 seconds,and the log interval could be one minute. In this case, the historyview will display more rows than there are entries in the log. Infact, there will be 5 rows for every 1-log entry. To compensate for this, the history view uses interim values until it receives an actualvalue from the log.

Interim values are either repeated actual values, or “sloped” toshow the gradation between one actual value and the next. TheFilling Type determines how the History view will display theinterim values. Your Filling Type choices are as follows:

None – This option displays only the values taken at each loginterval. In other words, no interim values are displayed betweenrows. The following picture shows a history view using the Nonefilling type:

This filling type omits interim values from the history view. Toachieve this effect, click None on the History tab.




Repeat Values Until Change – This option repeats the last valueuntil the point value changes

The following picture shows a history view using the Repeat fillingtype:

This filing type repeats the last actual value until it changes. Toachieve this effect, click Repeat Values Until Change on theHistory tab.

Slope Between Values – This option displays gradations of values between the rows. Gradation calculations are based onthe difference between row values, and the number of refreshrate values between rows.



TAC 558

The following picture shows a history view using the Slope fillingtype:

Notice that this filling type shows gradations of one actual valueto the next. To achieve this effect, click Slope Between Values onthe History tab.

TimeBetweenRows

Enter the Hours, Minutes, or Seconds that will be the intervalbetween rows of values on the History chart.

Dim FillValues

When this checkbox is selected, the fill values between loggedvalues on the History chart are dimmed and appear gray insteadof black.




The following picture shows a history view with its interim valuesdimmed:

Notice that this filling type makes it easy to distinguish actual

values from interim, or fill, values. To achieve this effect, click DimFill Values on the History tab.

Opening a Log Viewer

Once you have configured a Group object, you can review the activities of the objects inthe group three different ways:

• Log Viewer Member List

• Log Viewer History

• Log Viewer Graph

To bring up any of these group views:1. Select the Group object in Continuum Explorer

2. Right-click and select View then Member List, History or Graph from the popupmenus

Or, select View from the Object menu, then Member List, History or Graph.

Editing a Group from the Log Viewer

Do the following steps to open the Group editor for a Log Viewer:

1. Click the Edit Parent Object icon in the GroupView tool bar.



TAC 560

2. You then can change an existing Group’s default settings or add members to itsmember list. If there is a check in the checkbox next to an object on a Member List,that object will appear in a history.

3. You can drag and drop objects from Continuum Explorer to the Member List tab.




CreatingListViews

What is a ListView?

A ListView is a Continuum object that displays information about a specific object class.ListView information is either live or retrieved from the Continuum database. Theinformation that you see in a ListView depends on the columns of information displayed,how those columns have been configured, and whether or not qualifiers have beenestablished to filter objects by specified criteria. You can view the contents of theListView from the ListView object itself, from an HTML report, or from a printeddocument.

ListViews provide features that allow you to display an HTML report, format and print theListView contents, and even access the ListView editor itself. From the editor, you canadd and configure columns, choose colors for various situations, and set up qualifiers tofilter objects. Additionally, you can open the editor for any object shown in the ListView.

About Creating a New ListViewYou create ListViews by typing information into text fields, making selections fromdropdown menus, and browsing for objects. Once you have used the ListView editor tocreate a ListView, you will run the ListView then return to the editor if necessary.

Using the ListView Editor

The ListView General Tab

Use the General tab to select an object class and specify where Continuum looks forobjects of this class. You can also specify an HTML template for viewing your ListViewdata in an HTML report document.

23



TAC 562

Description Enter a description of up to 32 characters (including spaces) to help

others who need to test, modify or manipulate this ListView.Class Select an object class from the dropdown menu. This list of objects

includes all the object classes that appear in the New object popup listin Continuum Explorer.

Continuum also provides many specialized ListView classes you canuse to track system events, such as AlarmInfo, DistributionBatch,

EventLogControl and ImExportRef.

About Class Default ListViews

Continuum allows only one Class Default ListView per class. Database and Livequalifiers should not be used in a Class Default ListView. You can use sorting andbackground color choices when configuring the ListView columns to make items in the list

stand out.

For example, you can create an InfinityInfinetController Class Default ListView with threecolumns, Name, CommStatus and InfinetId. Make the CommStatus column Sort orderbe Primary and Sort direction be Ascending. Make the CommStatus columnBackground color red. Make the Name column Sort order Secondary.

Selecting any path other than ClassDefault will not produce a Class Default ListView.

Path Type Select from the dropdown menu. This helps Continuum decide where itlooks for objects in the Class, such as Programs on a particularcontroller or BinaryValue points stored in a certain folder.




AllPaths

Searches all possible paths on your system

FolderOnly

Searches the folder in the Path field

FolderandBelow

Searches the folder in the Path field and all its subfolders

DeviceOnlySearches the device in the Path field

DeviceandBelow

Searches the device in the Path field all the objects attached (owned by)the device

Prompt

Displays a dialog that asks users for the ListView path

ClassDefault

Designates this ListView as the default view for the class you selectedfrom the Class dropdown menu.

Path Browse for and select the device or folder to insert in Path.

Options Show Grid Lines: Use this option if you want your ListView to containrow and column markings.

Live Data on Open: Use this option to make the ListView open with livedata rather than data from the Continuum database.

Options Live Data Refresh Rate: If your ListView contains live data, enter therefresh rate in seconds. Continuum refreshes the ListView display usingthe interval you specify here. Five (5) seconds is the fastest a list view ispermitted to refresh.

List Reload Rate: The rate that Continuum reloads the entire list in

seconds. The time is measured from when the list finishes loading. Forexample if you set the reload rate to 20 seconds, the list will reload 20seconds after it finishes loading, not 20 seconds from when it startsloading: load list, wait 20 seconds, reload list, wait 20 seconds, and soon. Zero (0) seconds disables this feature. A valid setting must be 5 ormore seconds.

ReportTemplate

Click the Browse button in the Report Template field to display theOpen dialog:



TAC 564

Browse to find the HTML report template file that you want to use for thisListView.

The HTML file must be local to the workstation or be stored on theserver.

The HTML report templates provided for this course contain the fieldsthat will accept ListView attribute data.

When you view the HTML report, the ListView data that appears in the report fields isstatic. The values are not updated from the ListView. Creating HTML report templates is

covered in the Continuum System Administration Course.

The Columns Tab

Use the Columns tab to add, remove and configure data columns in the ListView. Youcan configure the contents and appearance of each column you add.




Add Column Click the Add Column button once for every column you want in yourListView. For every column you add, a column template like the oneshown below appears:

See Configuring ListView Columns on the next tab for instructions on configuringcolumns after you create them.

Configuring ListView Columns

For each column you add to your ListView you select the attribute information that itdisplays and make several other choices regarding its appearance.

To make these choices, you work with a column template like the one shown below

Each column template begins with default values for every aspect of your data. Tospecify different values, click in the field containing the value you want to change (seediagram above). Depending on the value type, you can:

1. Type over the existing value

2. Choose a new value from a dropdown menu.



TAC 566

3. Display a dialog that helps you select a new value.

4. Select a checkbox to indicate yes, or clear it to indicate no.

The following table tells you how to use each field.

Column Field How to Configure

Attribute Select an attribute such as Name or Status from thedropdown menu.

Type in the first letter of the attribute you want to make the

list scroll to that letter.

Heading By default, the ListView uses the attribute’s name as aheading. To use a different heading, type over the attributename.

Edit Select this checkbox to let users edit the attribute from theListView. Clear the checkbox to disallow editing.

Note: Not all attributes are editable.

Font andHeading Font

For each ListView column you can specify fonts for thecolumn data and the column heading:

Click in the Font or Heading Font field of your column.

Click the button that appears to display the Font dialog.

Select a font, font style and size from the scrollable lists. Asyou do so, the Sample box shows a text sample.

In Effects, specify strikeout marks, underlines and fontcolor.

Click OK to save your font settings.

Justification Select Right, Left, or Center from the dropdown menu.

Source Select Database or Live from the dropdown menu.

With Database, display the attribute’s database value.

With Live, display the current attribute value of the object.Specify the refresh rate in Live Data Refresh Rate on theGeneral tab.

Sort See the section Sorting in ListViews later in this chapter forinstructions on using the option.

Width The number of pixels for the column width, such as 25.

Show To include this column in the ListView, select the Show checkbox. To hide this column in the ListView, clear thecheckbox. Columns that do not show in a ListView canappear in HTML and printed report formats.




Column Field How to Configure

BackgroundColor

Click in the Background Color field of your column.

Click the button that appears to display the Color dialog.

Select a color from the palette or define your own customcolors.

Click OK to save your color settings.

Sorting in ListViews

You can sort the data in your ListView by the values of up to three attributes.

This is useful for ordering the rows of data to make them easier to read. Select theattributes used to sort the rows from the Columns tab.

Because each column represents one attribute of the object class you are viewing, youcan sort by Name, Value, or Status providing you have added and configured columnsfor those attributes.

To Sort by Attribute Value

Click the Sort field of the column of the attribute you wish to sort. This displays the dialog

shown below:

Select an Order number to help establish the sort order when you sort by more than oneattribute. See Understanding Sort Order on the next tab.

Select either Ascending or Descending from the dropdown menu. See the section,Sorting in Ascending or Descending Order on the next tab.

Click OK to save your work, or click Cancel to exit the dialog without saving.

For every attribute on which you base the sort order, specify if it’s the Primary,Secondary, or Tertiary sort order.

The Order number defines what happens when Continuum finds two objects that havethe same attribute value.



TAC 568

For example, if the Primary sort attribute is Name, how does Continuum order twoobjects named RoomTemp1? Which does it list first?

If another attribute has been set up as the Secondary sort attribute, Continuum uses itsvalue to decide which object is listed first.

The Tertiary sort attribute works the same way. If Continuum finds two objects with thesame Primary and Secondary sort attributes, it uses the Tertiary sort attribute to decidehow to list the objects.

Sorting in Ascending or Descending Order

For every attribute on which you base the sort order, specify either Ascending orDescending order:

• Ascending order starts with the lowest value and ends with the highest value.

• For text, ascending order is A to Z.

• For numbers ascending order is 0 to the highest numeric value.

• Descending order starts with the highest value and ends with the lowest value.

• For text, descending value is Z to A.

• For numbers, descending value is from the highest value to 0.

Note: Values such as Active, Inactive, ON, OFF, Online, Offline, Enabled andDisabled are represented to Continuum by 1 and 0 respectively. These values aresorted just like numeric values.

Sorting Example

The following example shows Numeric objects sorted in Ascending order, with Name asthe Primary sort attribute, Value as the Secondary and Device Name as the Tertiary:

The first two objects are sorted by Device Name because they have the same name andvalue. The third object is sorted by Value because, although it has the same name as thefirst two, its value is higher. The last two objects are sorted by Name.

The Qualifiers Tab

Uses the Qualifiers tab to enter Plain English statements to further qualify the objectsdisplayed in the ListView.

While the General tab allows you to qualify objects by class and path, the Qualifiers tablets you qualify and highlight objects depending on their attribute values. It is divided into




three main sections: Database, Live and Highlight. In addition, the Highlight Color fieldis used in conjunction with the Highlight section.

The Qualifiers tab offers two methods of creating qualifying statements for ListViewobjects:

1. Type the statements directly into the appropriate text field.

2. Use the Query Wizard to build the statements.

The method that you use is determined by the state of the "Advanced XXX Qualifiers checkbox.

• If it is checked, the edit control is enabled and text can be entered into the text field.

• If it is not checked, the Query Wizard button is enabled and selecting it will open theQuery Wizard dialog (see below) which allows you to build an appropriate qualifierstatement.

Using the first (advanced) method, you are responsible for creating the qualifierstatement correctly. With the second method, the Query Wizard assists you in building

the statement and once it is built, it is returned to the appropriate text field in the Qualifier tab. If necessary, the statement can then be edited by checking the "Advanced XXXQualifier checkbox

Live versus Database Qualifiers

The Qualifiers tab offers you the choice of constructing statements Live or from the

Database. If you select Live, the Cyberstation retrieves the settings of the qualifierstatement attributes directly from the controller. If you select Database the Cyberstationretrieves the attributes settings from Continuum's database.



TAC 570

The choice between Live and Database depends on certain factors. By using Live, youare assured of getting the latest version of the qualifier attribute settings since they areretrieved directly from the controller. If you know the attribute doesn't change very often,you can retrieve it from the database, which is faster than going to the controller to get alive value.

Using the Qualifiers Tab in the Advanced Mode

To create your qualifier statements directly in the Qualifiers tab, proceed as follows:

1. Click the Advanced Database (or Live) Qualifier checkbox.

2. Type the Plain English qualifier statement/s in the Database (or Live) text field. Forexample: STATE = DISABLED OR OVERRIDE = TRUE

3. Click the Advanced Highlight Qualifier checkbox if you wish to highlight certainparts of the statement created in step 2.

4. Type the parts of the statement you want highlighted in the Highlight text field. Forthe example in Step 2, if you want to highlight only those objects with an Overridevalue of TRUE, you would enter the following statement:

5. OVERRIDE = TRUE

6. Place the cursor in the Highlight Color text field and click the right mouse button:

7. Click Background Color to display the Color dialog:

8. Select the color you want and click the OK button.

9. Repeat steps 6 and 7 for the desired Text Color. Your color selections will bepreviewed in the Highlight Color field.

10. Return to the General tab and follow the "Test and Save" procedure at the end of thischapter to create the ListView.




Highlight Text and Color Example

The following figure shows an example of a ListView where objects with a State attributeof Disabled have been highlighted:

Using the Query Wizard

To build your qualifier statements with the Query Wizard, proceed as follows:

1. Click the Query Wizard button in the Database (or Live) section of the Qualifier tab(the Advanced XXX Qualifier checkbox must unchecked) to display the QueryWizard dialog.

2. Click the down arrow in the Attribute list field and scroll through the list and selectthe attribute you want by clicking on it.

3. Click the down arrow in the Operator list field and select the operator you want byclicking on it. (See "Operator Selections" on the next page.)

4. Click the Value text field and type in the appropriate value for your qualifier statement(see "Value Selections" on the next page).

5. Click the Prompt checkbox if you want to be prompted for an alternate attribute valuewhen the ListView appears. (See "Prompt for an Attribute Value" on the next page.)

Note: The Prompt feature is only available for a Database qualifier. It is not availablefor object link attributes, such as owner ID or device ID.

6. If you have additional qualifying conditions to add to your statement move down tothe next row of boxes on the Wizard.



TAC 572

7. Fill in the Attribute, Operator and Value fields as described in steps 2, 3 and 4.

8. Click the left hand field to enter a joint and/or operator. (See "Compound Qualifiers"on the next page.)

9. Repeat steps 6, 7 and 8 if additional Compound Qualifiers are required.

10. Click the OK button. If the statement validates without any errors, it will re-appear inthe appropriate text field of the Qualifier tab. If errors occur during validation, anerror message will appear and must be corrected to complete the operation. (See"Error Messages" later in this chapter.)

Operator Selections

The operators that are selectable from the Operator dropdown menu include thefollowing:

> Is Is like

>= Is not Is not like

< Is between

<= Is not between

Refer to Chapter 3 of the Plain English Language Reference manual for explanations for

each of these operators. The values to associate with these operators are discussedbelow.

Value Selections

The value that you select must be an appropriate one for the operator. The valuerequirements for certain operators are listed below.

Operators Value

Is

Is not

Number or expression that gives a number or a string. Also works with

object links, for example "Ownerid is \root\MyFolder".

Is like

Is not like

An asterisk (*) for number of characters or a question mark (?) for anysingle character.

Is between

Is not between

An expression that gives two numeric values, the lower one first,separated by an ampersand (&): number & number

>, >=

<, <=

Number or expression that gives a number.




Compound Qualifiers

Notice that an additional selection box appears to the left of the last three rows in theQuery Wizard dialog. These boxes allow you to link multiple statements together with theand/or joining operators. An example might look like this:

Attribute Operator Value

Description Is like A*

and Value is between 1 & 10

and Channel > 1

Prompt for an Attribute Value

Notice that a Prompt checkbox is located at the right hand end of each row on the QueryWizard dialog. This is an optional feature that is only available for a Database qualifier.Activating the checkbox will cause a prompt to appear on the screen when the ListView isopened. The prompt will allow you to change the corresponding attribute value and thuschange the contents of the ListView for that particular object.

Error Messages

The error messages that you may receive if the qualifier statement is invalid are listedbelow.

Note: In the Error Message column, the words in italics represent the type of item that

would be substituted in the actual message.Error Message Possible Cause

"You must pick an operator for theexpression"

You selected an attribute but did not pick anoperator to go with it.

"You must join additional qualifierswith either an and or an oroperator"

You have more than one qualifier statement, butdid not pick an AND/OR operator to join them.

"The value AttritubeValue youentered for the attributeAttributeName is invalid.

The value portion of the expression failedvalidation for some reason. For example "Thevalue is not within the specified range".

"You may only use the is, is not,is like and is not like operators onthe attribute AttributeName .

You have selected an operator that is notsupported for the attribute.

"The object ObjectName that youentered for the attributeAttributeName does not exist in thedatabase. Do you wish to use thisobject anyway?"

You have tried to enter a value for an object linkattribute but the value you entered does notexist in the database. This message box willgive you two choices, yes and no. If you selectyes then the text you entered will be usedanyway, if you select no then validation will failand you can then change the text.



TAC 574

Test and Save

After you fill out the tabs of the ListView editor, return to the General tab.

1. Click the Apply button to create the new ListView.

2. Click the Run ListView button. Your new ListView will appear, covering the ListVieweditor window.

3. Review the elements of your new ListView.

4.

To use the editor to modify the ListView, click its button in the Windows task bar atthe bottom of the screen.

5. Use the ListView buttons in the Windows task bar to switch between the ListView andits editor.

6. Click OK in the editor to save the ListView.

Creating a History or Graph of a ListView

To create a history or graph of your ListView, follow these steps.

Note: This procedure is performed the same (with the same screens) when a history orgraph report for your ListView is required. The final output of your history or graphis different and both outputs are shown.

1. Highlight the ListView from which you want a history or graph.

2. From the ListView Object menu, select History or Graph.




3. You are presented with the following screen. Select the times you require in theRange fields and the Time Between Rows fields. Select the type of log you requireand click OK or Now.

4. Depending on whether you selected History or Graph, you are presented one of thefollowing screens depicting a history or a graph of your ListView.

If you select History, the following appears:

If you select Graph, the following appears:



TAC 576




Creating

EventViews

Overview

An EventView object determines which access-related events will display in an ActiveEvent View. You configure an EventView object using the EventView editor.

Active Event Views are used to monitor access-related activities. These activities includethe use of card readers and/or keypads to gain access through locked doors, or troublesituations such as a door left ajar, keypad tampering, or forced entry. Active Event Viewsalso provide information such as who is using which door, when, and whether the doorre-locks properly. Event views are called “active” because they receive and list accesscontrol events as they occur.

Using the EventView editor, you specify the types of events and the doors you want tomonitor. You can also specify sorting criteria for the events, and configure the font andcolor for each event. Once you have created an EventView object, users on anyCyberStation workstation can monitor events as they occur in an Active Event View.

24



TAC 578

Before Creating an EventView

Prior to creating an EventView object, make sure the appropriate Access Events havebeen selected on the Options tab of your Door editor.




Creating an EventView

From the Continuum Explorer, right-click the Live Views folder, New, and selectEventView.

Type in a name for the new EventView (for example, DoorXXEventView) and pressEnter.

You will be presented with the following tabs. These tabs are discussed in the followingsections.

• General

• Doors

• Fonts and Colors



TAC 580

The General Tab

In the General tab, enter information about the Active Event View’s general appearance.

Description Enter a description that explains which doors and event types willdisplay in the Active Event View. (Adding this information is optional.)

MaximumNumber ofEvents

Enter the maximum number of events you want the Active EventView to display at one time.

When the number of events displayed reaches the maximum number,the bottommost event drops off the list as a new event displays. Theorder in which events display depends on the sort criteria you set up.

Maximum Timein View

Enter the number of seconds events will display in the Active EventView before expiring and dropping off the list.

If this field is left blank, events don’t expire, they drop off the listbased on the maximum number of events and the current sort order.

Sort Criteria In the Sort Criteria area, you may sort events according to threecolumns. The Active Event View displays several columns ofinformation for every event, according to the sort criteria you selecthere. Sorting is useful for grouping events to look for trends in, forexample, the source of events, types of events, and which personnelare accessing which doors most often.

From the Primary, Secondary, and Tertiary dropdown menus, selectup to three columns. The columns you select establish the sort orderthat the Active Event View uses. Check the ascending checkbox tosort in ascending order, or clear it to sort by descending order andclick OK to save your work.




The Doors Tab

In the Doors tab, select the doors and the event types to display in the Active EventView. These doors and event types you select are listed on this tab.

Perform the following steps to add doors and/or event types.

1. Click the Add Door button.

The Browse dialog appears.

2. Search the directories for, and select, a door to add to the list of doors to bedisplayed in the Active Event View.

Note: As an alternative, you may select one or more doors from the desired

directory, click and drag the doors to the Doors tab, and release the mousebutton.

3. Click OK to return to the Doors tab.

4. For each door listed, check the checkbox for every event type that you want to

include in the Active Event View. Use the horizontal scroll bar to see all the availableevent types.

Note: As an alternative, select the event type you want to include in the Active EventView, and click Check Selected.

5. When you do not want to include an event type in the Active Event View, scroll to theevent type you want to remove, and click the checkbox to remove the check.

Note: As an alternative, select the event type you do not want to include, and clickUncheck Selected.

Perform the following steps to remove doors.

1. In the list of doors on the Doors tab, select one or more doors you wish to remove.



TAC 582

2. Click Remove Doors.

The Fonts and Colors Tab

In the Fonts and Colors tab, configure the font, text color, and background color forevery event type. All event types are listed on this tab. For example, you could use agreen background for valid access events, yellow for invalid attempts, and red for doorajar events. Configuring fonts in this way helps the operator quickly differentiate events.

When you select a font and color for an event type, that event type is listed with its newfont and new colors.

Perform the following steps to configure fonts and colors.

1. On the Fonts and Colors tab, right click an event type. A popup menu appears.

2. Select Font to configure the font and font style.

3. Select Background Color or Text Color to configure colors for the background andtext, respectively.

The Security Level Tab

For details in attaching or detaching Security Levels, see Chapter 4, Security .




The Active Event View

The Active Event View lists the events associated with the specified object (in this casethe Lobby Area). Based on how your Administrator configured the active event view, itcan show events for one door, a group of doors, all doors, or doors associated with aparticular area.

The events are shown in chronological order with the most recent event presented first.Each row displays columns of information related to a particular event. Event informationcan be displayed in a variety of colors to depict different categories of events.

Parts of the Active Event View

An Active Event View generally consists of the following types of components:

• Active Event View menus

• Quick pick options

• Columns

Menus

The Active Event View has the following dropdown menus: Object, View, and Help.

Object Menu

Menu Selection Description

Print Prints the current Active Event View.

Print Preview Displays a full screen preview, showing how the current ActiveEvent View will be formatted when printed.

Print Setup Opens the Microsoft Print Options dialog for changing printersand setting print options.

Clear All Events

Exit Closes the Active Event View. Prompts to save data.

View Menu


Toolbar Prints the current Active Event View.



TAC 584

Sort Displays a full screen preview, showing how the current ActiveEvent View will be formatted when printed.

Auto Sort Sorts all access events.

Freeze Opens the Microsoft Print Options dialog for changing printersand setting print options.

Add/RemoveColumns

Closes the Active Event View.

Status Bar Hides or displays the status bar.Always on Top When selected, ensures that the Active Event View will stay on

top of all other applications on your screen.

Event View Object Opens the EventView object editor for this Active Event View.

Door Opens the Door object editor.

Area Opens the Area object editor.

Person Opens the Personnel Manager.

Help Menu


Contents Opens Active Event View help topics.About ActiveAccess Event View

Displays program information, version number, and copyrightinformation.

Quick Picks

As an alternative to the dropdown menus, you may use the these quick pick icons to savetime:

Click this … To …

Print the current Active Event View.

Start or stops the addition of new events.

Open the EventView editor.

Open the Personnel Manager or editor.

Open the Door editor.

Open the Area editor.

Navigate to a video (brings up the VideoLayout editor) for anevent.

Enable the sort function.




Click this … To …

Open the Pending Access Distribution dialog, which allowsimmediate distribution. When you want to distribute a personnelrecord immediately to a controller, in order to resolve a pendingrequest to access an area by that person, highlight the pendingdistribution-event transaction, and click this button. The PendingAccess Distribution dialog appears. To perform an immediatedistribution, click the Distribute Now button.

For related information, please see Chapter 20, ManagingPersonnel Distribution.

Open Active Event View help topics.

Columns

For every event, the Active Event View displays the following columns of information:

Column Description

Date/Time Date and time the event occurred

Type Type of access event.

Door Door at which the event occurred

Person Personnel associated with the card reader or keypad event

Area Area in which the event occurred

Controller Full path to the controller that controls the door

Message Not yet implemented

Zone Code If the system is zone-based rather than area-based, the codenumber of the zone in which the event occurred

DepartmentPoint

Department point number of the person causing the event

Card

Number

Access card number of the person causing the event

Card Type Access card type, Wiegand, or ABA, of the person causing theevent

Site Code Access card site code number of the person causing the event

Working in the Active Event View

As mentioned previously, the Active Event View is a dynamically updating list. By default,the view lists all of the event details in columns. You use the scroll bars to access theinformation not displayed in the window.



TAC 586

Two options are available for changing the way the information is presented in the view:

• Resizing Columns – You can resize column widths by pointing on the verticaldividing line between two columns.

When the cursor changes to a double arrow , then hold down the mouse buttonand drag the column boundary to the left or right.

• Adding/Removing Columns from the View - You can modify the settings for the

view to remove (or add) columns from the display. To accomplish this, choose theoption Add/Remove Columns from the View dropdown menu.

A dialog appears:

Click the box to the left the columns you want removed from the view. The checkmark is removed from the box indicating the column has been deselected. Click theOK button to save the changes and have the view updated to reflect the columnremoval. Conversely, if you want to add columns to the view, click in the box so acheck mark does appear and then click OK to save the changes.

Viewing Event Details

Viewing the event information can be accomplished through the Active Event View or youcan retrieve an Event Details View. The Details View conveniently displays all of theevent information in one window that you may find easier to read the event information.

Double click any event in the Active Event View to see the Details View of that event.The Details View shows you all the Active Event View column information in a singledialog.




Right click any browsable field to open a popup menu of options.

Field Description

Type Indicates what type of event occurred.Date andTime

Indicate when the event occurred.

Message Displays a text string describing the event condition.

Door Indicates at which door the event occurred.

Personnel Shows the person associated with the card reader or keypad event.

Area Shows what area the event occurred (where door is located).

Controller Displays the name of the controller the access control device isattached.

DepartmentPoint

Indicates the department point number of the person causing theevent (if one has been defined for the person).

Zone Code Reflects the code number of the zone in which the event occurred, ifyour system uses zone rather than area based access control.

Card # Shows the access card number of the person causing the event.

Card Type Indicates the type of access control card used by the person causingthe event.

Site Code Displays the site code assigned to the person causing the event (if onehas been defined for the person).



TAC 588

Sorting Events

You can sort events by the values of up to three columns. This is useful for groupingevents to look for trends in, for example, the source of events, types of events, and whichpersonnel are accessing which doors most often.

Note: You may also sort events by columns, and establish sort criteria, via the General tab of the EventView editor.

Perform the following steps to sort events by columns.

1. Select Sort from the View menu to display the Sort Criteria dialog.

2. From the Sort Criteria dialog, select up to three columns from the Primary,Secondary and Tertiary dropdown lists.

The columns you select establish the sort order that the Active Event View uses.

3. Check the ascending checkbox to sort in ascending order, or clear it to sort bydescending order.

4. Click OK.

Rearranging Active Event View Columns

Use the click and drag method to rearrange the columns in the Active Event View:

1. Click once on a column heading to highlight the column.

2. Click again anywhere in the column, and hold down the mouse button.

A small box appears next to your cursor. This indicates you are ready to move thecolumn.

3. Drag the cursor to the new location in the Active Alarm View, and release the mousebutton.




Adding and Hiding Columns

Follow these procedures to add a column, hide two or more columns, and hide onecolumn.

To add a column:

1. Select Add/Hide Columns from the View menu. This opens the Add/Hide Columnsdialog.

2. Select the checkboxes of the columns you want to add.

To hide two or more columns:

1. Select Add/Hide Columns from the View menu. This opens the Add/Hide Columns dialog.

2. Clear the check boxes of the columns you want to hide.

To hide one column:

1. Right click the column you want to hide. This opens the shortcut menu.

2. Click Hide.

Accessing Events for a Specific Door

To monitor the access control activities of a particular door, you open the Door editorwindow for the door through a listview. The steps to do this are as follows:

1. Click the All Doors listview button. The listview opens showing a list of all yourdoors.

2. Double-click the door whose activities you want to monitor. The Door editor windowopens for the door (in this example, Lobby Door is the selected door.)



TAC 590

To monitor the access control activities of a particular door, you open the Door editorwindow for the door through a listview. Follow this procedure:

1. Click the Access Events tab. The window updates to show the events recorded forthis door, in chronological order.




As you can see from the figure, the Access Events list displays:

o The type of event (EventClass column)

o Date and time the event occurred (TimeStamp column)

o Person associated with the event (Person column)

o Area associated with the event (Area column—not shown in this figurebut accessible via the horizontal scroll bar)

2. Click the Refresh button to see the most recent access events.

In addition to monitoring active events, you may need to review past event informationthat has been stored in the CyberStation database. To look at event history, ListViewsare utilized.

Event history is useful in diagnosing recurring problems. For example, your supervisormay ask you to research Door Ajar events for a particular door. Or, gather informationabout the number of personnel moving into or out of a specific area.

An example event listview is shown below.



TAC 592




Configuringand ViewingVideo

Version 1.7 and higher, CyberStation has two video object classes, VideoLayout andVideoServer , and video integration. Specifically, this chapter presents:

•

Overview of Video integration and configuration• Using the VideoServer editor

• Using the VideoLayout editor

Overview of Video Integration and Configuration

Video integration comprises:

• Two object classes: VideoLayout and VideoServer.

A VideoLayout object is essentially CyberStation’s video surveillance monitor,through which you may view live and/or recorded video images. Each layout candisplay images from up to nine cameras.

A VideoServer object identifies video servers for CyberStation, making it possible forCyberStation to communicate with each video server and its cameras.

Note: It is assumed that the video servers (Integral brand) have already beenconfigured, along with cameras and video presets. Therefore, to perform yourconfiguration tasks, you should already know the video server names, usernames, user passwords, and IP addresses for each Integral video server.

• Various attributes for many existing object classes that have video associated withthem — for example, graphics objects, Door objects, and points, such as InfinityInputand BinaryInput.

• Active Alarm View features and Active Event View features that integrate video withindividual alarms and access events, respectively

25



TAC 594

The following procedure provides an overview of configuration tasks that you perform toachieve video solutions suited to your site. While completing these tasks, refer to theother sections in this chapter (Using the VideoServer Editor and Using the VideoLayout Editor ) for more details. Also refer to other parts of this manual, where noted.

1. Create all VideoServer objects — Enter server names, user names, passwords,and IP addresses. Test each server's connection. (See Using the VideoServer Editor ,later in this chapter.)

Note: You must have already gathered this information from each video server,which should have already been configured, along with cameras and presets.(See your Integral video server documentation.)

2. Create all VideoLayout objects — When you create a VideoLayout object, youmust associate cameras with (and assign them to) video control frames, or“windows,” where images are displayed.

There are two ways to do this:

• Manually assign cameras — You may manually assign a camera — that is,“hardwire” it — to each video frame in the VideoLayout object editor. You wouldtypically “hardwire” a camera to view video that is not associated with alarms. Forexample, this method is useful during real-time surveillance and routine guardtours. (See Using the VideoLayout Editor , later in this chapter.)

• Pre-assign cameras — You may pre-assign cameras in objects that associatevideo with alarms and access events. This method uses a new feature calledvideo points . In the long run, video points save time and are easier to usebecause they populate the frames of VideoLayout objects dynamically andautomatically. Up to four “video point” frame assignments are made in objects(such as a Door or InfinityInput) that generate alarms and access events. Whenthe object goes into alarm, the VideoLayout associated with the objectdynamically loads those camera assignments.

Within the VideoLayout object, you must reference one of the four video points. (SeeUsing the VideoLayout Editor , later in this chapter.)

The actual assignment of video points in objects is addressed in Step 4. See Step 4below, as well as the section, Using the Alarms/Advanced Alarms Tab of an ObjectEditor, in Chapter 10, Configuring Alarms.)

3. Make a list of objects to be associated with video — You do this whenever youhave a need to view video images when those objects, such as doors and inputpoints, go into alarm or have an access event.

4. Configure video points in the object editor — For each object in the list, configurevideo points using its object editor, and associate the object with a VideoLayout.

Video points are video-server and camera references that are attached to Continuumobjects. Video points also contain other video information, such as presets, recordflags, and PTZ (pan, tilt, zoom) information. A VideoLayout can be attached toobjects in exactly the same way a graphic can be attached to an object.




Note: If you launch (open) a VideoLayout from Continuum Explorer, from a graphic, froma ListView, and so on, and that layout references video points, then only the frameswhose cameras have been “hardwired” display video.

Open each object from the list in Step 3, select its editor’s Alarms tab or AdvancedAlarms tab, and associate the video layout with the object. (See the section, Using the Alarms/Advanced Alarms Tab of an Object Editor , in Chapter 10, Configuring Alarms .)

Configure video points 1 through 4 from the Video Points dialog. (See Chapter 10.)

Repeat for each object in your list.

1. Configure EventNotifications to display video with alarms — If you areassociating video with alarms, and you want to pop up a video layout when a newalarm comes in, then edit the EventNotifications associated with those alarms, andselect Display Video on the Actions tab of the EventNotification editor. (See thesection, The EventNotifcation Actions Tab , in Chapter 10.)

2. Configure graphics with video — Configure graphic controls to launch “hardwired”video layouts from buttons and other graphic controls.

3. Test the alarms and access events — Trigger an alarm with an associated videolayout. Ensure the video pops up, if configured to do so.

If you choose not to pop up video, you can launch the video layout using the newvideo button on the Active Alarm View. (See Active Alarm View in Chapter 10.)

Repeat this process for access events, if necessary. Launch the video layout usingthe new video button on the Active Event View. (See Active Event View in Chapter21.)



TAC 596

Using the VideoServer Editor

Using the VideoServer editor's General tab, you assign a physical video server to thisVideoServer object. Any camera attached to this VideoServer object may be thereforeassigned to (and its images viewed in) a video layout image frame or “window.” (SeeUsing the VideoLayout Editor , later in this chapter.)

General Tab

In the General tab, you assign a physical video server to this VideoServer object:

Any camera attached to this VideoServer object may therefore assigned to video imagewindows (video controls) in the VideoLayout editor.


Description Enter a text description of this VideoServer object.

IP Address Enter the IP address of the physical video server that you wish toassign to this object.

User NamePasswordVerify Password

Enter the user name, and this user's password, that will be used tolog onto the video server, when this VideoServer object isaccessed. This user must exist on the actual video server to whichyou are connected. If the user does not exist on the server, thisVideoServer object cannot be created for that user.

Tip: To have two or more users log onto the same video server,create two or more VideoServer objects that connect to the sameserver, but with different user names and passwords. This is usefulwhen you need to limit a Continuum user's access to Continuumvideo features. For example, a guard typically should not have thesame access to video servers and layouts as an administrator.




Test Connection Click this button to test the network connection to the server whoseIP address appears.

If the test is successful, this message appears beneath the button:

Connection successful

If it is unsuccessful, this message appears:

Error Connecting to Server

Using the VideoLayout EditorA "video layout" is essentially the video surveillance monitor for CyberStation. You opena VideoLayout object either manually in Continuum Explorer, or automatically byattaching it to a point's alarm or to a graphical control, to view live video images from asingle surveillance camera or from multiple cameras set up in a matrix of video imageframes. (See also Overview of Video Integration and Configuration , earlier in thischapter.)

Note: You may also open a video layout via the Plain English SHOW command, in theContinuum Command Line or via a Plain English program.

Via the VideoLayout editor's General tab, you may also:

• Assign, delete, and reassign cameras in the layout.

• Play back a recorded video clip.

• Capture a video image and save it to a file.

• Freeze, reload/refresh, pan, tilt, zoom, and adjust the image resolution (contrast,brightness, and so on)

Each image window in the layout is called a video control frame . Using a multiple-cameramatrix, the VideoLayout editor allows you to assign (and view the images of) one, two,three, four, six, or nine cameras.

Note: In order to assign a camera to a video control, at least one video server must havebeen configured so that its cameras are available to the VideoLayout. (See thefirst two sections in this chapter.)

In Continuum Explorer, you may create a VideoLayout object from the Root directory or afolder. You may not create a VideoLayout object from a network, controller, workstation,or any other device.



TAC 598

General Tab

In the General tab, you configure a VideoLayout object, view video images, and performbasic video operations:

The General tab displays one or more video controls — frames that display live orrecorded images from one or more video cameras associated with one or more videoservers. Using a multiple-camera matrix, you may assign (and view the images of) one,two, three, four, six, or nine cameras in the same layout.

How to Access the Video Control Popup Menu — The video control popup menuallows you to assign and reassign cameras, view live video, play back recorded videoclips, capture video images, adjust the image resolution, and perform other basic videooperations. To access the video control popup menu:




1. Select (highlight) the video control frame with which you want to work. A red boxappears around the selected frame.

2. Right click the selected frame. The popup menu appears.

Video Control Popup Menu — The following table describes the choices in a videocontrol popup menu, as well as the tasks you may perform via each selection.

MenuSelection

Description

Live Video Select Live Video to display live (real time) images from the cameraassigned to this video control frame.

Note: Be sure to select Live Video again for any image that waspreviously frozen. (See Freeze Video, below.)

RecordedVideo

Select Recorded Video to play back a video clip from the cameraassigned to this video control frame. When Recorded Video is selected,a list of clips appears at the bottom of the video layout. Each clip in thelist displays the camera name, the date the clip was recorded, the starttime, the end time, and the number of frames. For example:

Select the video clip that you want to play back. A black play button andstop button appear on the bottom of the frame. Click the play button tobegin the playback. Click the stop button to stop playback. You may alsouse the slider control within the frame to move forward and backward inthe recording.

To search for available video clips, specify a start date/time and an enddate/time in the Start and End fields, respectively. Then click the Search button. All video clips within that time frame appear in the list.

In the date fields, click the down arrow to display a calendar. Then clicka start or end date on the calendar. The selected date is highlighted in



TAC 600

MenuSelection

Description

blue, while the current date appears in a red circle. As an alternative,you may highlight the month, day, or year field, and manually key-in themonth, day, or year.

In the time fields, use the up- and down-arrow buttons to select a time.As an alternative, you may highlight the hour, minute, second, or AM/PMfield, and manually key-in the hour, minute, and second, and specifymorning or afternoon/evening (AM or PM).

Playback fps – Select the speed (number of frames per second) atwhich you want to play back the video clip. The current number offrames per second is displayed at the left of this field. Use the slider barand right- and left-arrow buttons, as needed.

Note: Video clips are stored on the video server, and not in theContinuum database.

FreezeVideo

Select Freeze Video to freeze the moving image of this video controlframe immediately.

DeleteCamera

Assignment

Select Delete Camera Assignment to remove the camera from thisvideo control frame. When you delete a camera assignment, the cameraimages disappear and the frame goes black.

To reassign a camera, select Change Camera. (See below.)

PTZ Select PTZ when you need to pan, tilt, or zoom in and out of the videoimage in this video control frame.

Note: The camera assigned to this video control frame must have PTZcapabilities in order to use this feature.

At the bottom of the frame, PTZ displays the numbers 1...6, as well asthe following letters:

I O F N O C

I — Click to zoom in.

O — Click to zoom out.

F — Click to focus the camera "far" or further out.

N — Click to focus the camera "near" or further in.

O — Click to open the iris and increase the amount of light streaminginto the camera.

C — Click to close the ir is and decrease the amount of light streaminginto the camera.

The numbers 1...6 are the first six "preset" camera views. Althoughsome cameras support up to 256 camera presets, only the first six are




MenuSelection

Description

supported here.

Panning and tilting — To pan and tilt the camera, place your cursor inside the video control frame, and click once. A light blue thick arrowappears. You may pan/tilt up, down, left, right, and diagonally. The bluearrow changes direction, according to where you place it on the frame:

Up arrow — Pan up. Click cursor at top-center.

Down arrow — Pan down. Click cursor at bottom-center.

Left arrow — Pan left. Click cursor at left-center.

Right arrow — Pan right. Click cursor at right-center.

Right diagonal up arrow — Pan diagonally to the upper right. Clickcursor at top right corner.

Left diagonal up arrow — Pan diagonally to the upper left. Click cursor at top left corner.

Right diagonal down arrow — Pan diagonally to the lower right. Clickcursor at bottom right corner.

Left diagonal down arrow — Pan diagonally to the lower left. Clickcursor at bottom left corner.

CaptureImage

Select Capture Image to capture the image being displayed in this videocontrol frame and to save it to a file.

The Capture Video Image Save dialog appears. Browse for thedirectory in which you want to save the image file, specify the file name,specify the image file type (.BMP, .JPG, and so on), and click Save.

VideoPoints

Select Video Points to preconfigure a video control frame so that, whenthis VideoLayout is attached to an object and associated with an alarm,up to four cameras (known as "video points") can be automaticallyassociated with the VideoLayout.

When the alarm goes off, this VideoLayout is launched, displaying thevideo points associated with the object that went into alarm.

These cameras are pre-assigned via the Video Points button (and theVideo Points dialog) in the Alarms tab or Advanced Alarms tab of theAnalogInput, AnalogValue, BinaryInput, BinaryValue, Door, InfinityInput,InfinityNumeric, InfinitySystemVariable, MultistateInput, orMultistateValue editor.

Note: See Overview of Video Integration and Configuration , earlier inthis chapter, as well as the section, Using the Alarms/Advanced Alarms Tab of an Object Editor , in Chapter 10, Configuring Alarms.)

Using the Video Points dialog (shown below) in these editors, you



TAC 602

MenuSelection

Description

designate between one and four video points, whereby each numbered"video point" represents a frame in this VideoLayout's matrix.

About the Video Points Dialog – Click the Video Points button on theAlarms or Advanced Alarms tab of the editors listed above to bring upthe Video Points dialog. (See also Chapter 10, Configuring Alarms .)

In this Video Points dialog, you may also configure a camera to recorda video clip, for specified number of seconds, when the alarm goes off.

Video Servers: Use the Video Servers dropdown menu to select a

video server on which the camera is located. (A VideoServer object mustbe already configured and the server online. See VideoServer Editor earlier in this chapter.)

Cameras: Use the Cameras dropdown menu to select a camera for thenumbered video point. (The camera must be configured and enabled onthe selected video server.)

Rec: Check the Rec. checkbox to record a video clip from the selectedcamera. Recording begins at the moment the alarm goes off.

Duration: In the Duration field, use the up and down arrows to selectthe number of seconds to record a video clip, once you check the Rec.checkbox.

PTZ: In the PTZ field, select the number of the preset camera view. (Thiscamera must have PTZ (pan, tilt, zoom) capabilities in order to use thisfeature.) See also the General tab of the VideoLayout editor.)

After you preassign the video point cameras to the frames (Chapter 10)you reference a video point number here (in the General tab of theVideoLayout editor) that corresponds with each numbered frame youconfigured in the Video Points dialog. Right click over the frame, selectVideo Points, then select 1, 2, 3, or 4. For example, the camera youspecified as "Video point 1" in the object editor is assigned to the frameyou reference as "1" in this VideoLayout object.

When the VideoLayout is launched, on an alarm associated with the




MenuSelection

Description

object, this preconfigured video control matrix is displayed.

ChangeCamera

Select Change Camera to assign or reassign a camera or "videosource" to this video control frame.

Select the name of a server in the popup menu of server names, next toChange Camera. Then, in the next popup menu, select the name of acamera — for example, it might be called "main lobby" or "loading dock"

— belonging to that server. The camera is assigned to the video control,and the camera's images immediately appear in its frame.

Note: If a server is not available for connection (not online) then its list ofcameras does not appear in the popup menu. The server must beavailable for connection. Likewise, a server's cameras must beenabled. If a camera is disabled (via Integral video serversoftware) it does not appear in the menu.

In order to assign a camera to a video control, at least one video servermust have been configured. (See the VideoServer editor.)

Security considerations: Access to video servers may be restricted byContinuum's security system. Access to cameras on the video servermay be restricted by the server's security system. That is, users see onlythe cameras to which they have been granted access.

Repeat this procedure for every video control frame in the matrix. Youmay select another camera, or even the same camera, for other videocontrol frames. When you select the same camera for two or moreframes, then the same camera images are displayed in those frames.You may also select cameras from more than one video server.

The following table describes other General tab video attributes and buttons, which allowyou to adjust your video control images.


Text Overlay Check this checkbox to display the name of the camera, as well asthe date and time, over each video control frame of the matrix. Clickand remove the check to display no text.

Top — Click this radio button to position the text at the top of eachframe.

Bottom — Click this radio button to position the text at the bottomof each frame.



TAC 604


Text Colors You may change the color of the text in the text overlay by clickingone of the six colors in the color key, located beneath the textoverlay radio buttons. These colors are:

Red

White

Blue

Yellow

Green

Black

Black is the default.

BrightnessContrastSharpness

Use the slider control to increase and decrease brightness,contrast, or sharpness, respectively.

Note: The slider control on the Brightness, Contrast, or Sharpnessblinks at any given time to indicate which setting is currentlyselected.

Reload Layout Click this button to reload and refresh all the video controls.

Freeze All Video Click this button to freeze every video image in every video controlframe.

If you wish to freeze the image for just one video control, right clickthe control frame and select Freeze Video from the popup. (See thetable above.)

Capture Layout Click this button to capture the image being displayed (live orrecorded) in the selected video control frame and save it to a file.

The Capture Video Image Save dialog appears. Browse for thedirectory in which you want to save the image file, specify the filename, specify the image file type (.BMP, .JPG, and so on), andclick Save.

MatrixSelections

To select or change the desired video-control matrix to display one,two, three, four, six, or nine video images in your layout, click one ofthese video control frame matrix buttons. The matrix changesimmediately.

Note: The three-frame and six-frame matrices display one framelarger than the others, as shown in these matrix buttons.

A video-control frame remains black until you assign a camera byright-clicking on its frame and selecting Change Camera from thepopup. (See the table above.)




Graphics

Panels

Introduction

The Pinpoint graphics application is used to produce dynamic virtual control panels righton your CyberStation workstation.

CyberStation control panels are computer-generated representations of physical panels.They consist of a screen display of buttons, switches, animations and text, and other“controls” that control particular points, particular elements of log or array points, pointattributes, system variables, or certain Continuum objects, such as areas and doors.Every control placed on a CyberStation control panel can be easily changed, deleted andre-assigned through software.

Controls can be active or passive:

• Active controls, such as a switch or button, can be manipulated by the user. Forexample, a switch control, when “turned,” might set a point value or setpoint.

• Passive controls convey information, such as gauges and read-only text controls thatdisplay values. A text control might display the current room temperature.

A control panel can have one or more controls, or not controls at all.

Pinpoint supports a simple form of animation that uses multiple images of the samecontrol. Because each image is slightly different, viewing them in a sequential orderproduces the effect of animation.

The following example shows a Pinpoint graphics panel that monitors HVAC equipmenton one floor of a building.

26



TAC 606

Controls

The following list identifies the type of controls available in the Pinpoint application. Alibrary of predefined images for each control is provided with the application. You canalso use bitmap images that you created in another application to represent controls.

Switches

Pinpoint switch controls allow you to control two-state (on-off) points. Inaddition to their control capabilities, they also can display a differentimage for each state. Clicking once activates the control and alsoautomatically displays the control’s image associated with its activation.

You choose the bitmap image set that defines the switch in eachposition.

Buttons

Buttons work in a similar manner to switches. They allow you to controltwo-state (on-off) points, launch applications, etc. Buttons can be anyshape, but they do not change appearance.

Active Animated Buttons

Active or animated buttons can be any shape. They can change colorwhen pressed.




Bar Control

A bar control shows the value of the point by rising or descending to aparticular level as the value of the point changes. Both horizontal andvertical bar controls are available in the image library.

Text Control

A text control displays a textual representation of a point value. If the

point is an input or output, it displays the point value in engineeringunits. For a numeric point, it displays the numeric value. For a stringpoint, it displays the characters in the string. For a datetime point, itdisplays the date and time in the point.

Door Control

The door control provides a graphic display of a CyberStation doorobject. It illustrates the switch states of the door by using configurableanimation. Images illustrate the states of the door, such aslocked/unlocked, trouble, and alarm. When you right click a doorcontrol, a popup menu provides access to additional functions, such aslocking or unlocking the door, and opening the Door editor.

Area ControlThe area control provides a graphic display of an Area object and canindicate whether the area is in Lockdown state or its normal state. Youcan also use an area control to initiate or clear the Lockdown state.Popup menu options allow you to lockdown individual doors to thearea, or to clear the Lockdown state as well as to access other areafunctions. For more information regarding area lockdown, see Chapter18.

Panel with Multiple Controls

The following figure shows a complex graphics panel that monitors both accessinformation and HVAC data. This panel uses several Pinpoint features:

• Background image representing the controller and IOU module

• Lines created with drawing tools

• Text boxes to display and label values

• Images associated with active components to current conditions for CyberStationpoints and other objects

The table following the figure identifies how some of the controls are set up.



TAC 608




TextControls

Controller Time/Date

This is a text control tied to the system clock. It displays the date and time.

Power Fail

This text control indicates whether the power fail condition is true or false.The other text controls are also tied to various points throughout thesystem and include such information as the amount of free systemmemory, which server is being accessed, alarm and error counts, etc.

Bar Control Temperature Gauge

This bar control is linked to a sensor and displays the temperaturegraphically.

Switches Gate Switches

Off On

These switch controls operate security gates. When on, the indicator onthe top of the switch turns red.

Gate 4

This object indicates whether a gate in the building area is open (up) orclosed (down) position.



TAC 610

About Image Files Used in Panels

Where you store your image files affects your system performance. Whether you accessimages from a central location, such as a server, or from the local drive of a workstationmakes a difference. Using a central location may be appropriate if you are working with alarge number of workstations. However, because the data must travel through a network,accessing them will be slower than if the data was retrieved locally. See Setting Up Pinpoint Options .

When you create a graphic to become part of your panel, we suggest that you save the

image in the lowest resolution possible, so that the resulting image file is small andrequires little memory.

The Pinpoint image library contains bitmap (*.bmp), JPEGs, Icon, and enhanced metafile(*.emf) files. We recommend that you use the metafile graphics wherever possible.Metafiles are significantly smaller than the other formats, they scale up or down withoutdistortion, and they support transparency better than the other formats.

In addition, the number of controls on a panel may affect how quickly the panel isupdated when changes occur. Using large numbers of controls on a panel can affect therate at which the controls react to changes.

Creating a Pinpoint Panel

1. Click the hot spot on the CyberStation Main Menu.

2. Click the hot spot.

3. Select the File option on the Pinpoint menu bar, and then select New.

4. In the Create Graphic dialog, enter a name into the Object Name field, and click theCreate button. A new blank Pinpoint panel appears.

Selecting Graphics Locations

Use this procedure to select the default folders to use for the following Pinpoint elements:

• Pinpoint panels (.Pin)

• Bitmap images that represent controls

• Images that represent the background in a panel

1. From the System and Status menu page, open the Pinpoint graphics editor.

2. From the View menu, select Options.




3. Enter (or browse to) the appropriate locations where you want your graphics, image,and background files stored.

Location Description

Graphics Folder Pinpoint panel files that you create or modify.

Image Folder Images that you can use to represent controls.

BackgroundFolder Background image files.

Setting Panel Options

Although Pinpoint has default values for all options, you can change these options byperforming the following steps:

1. From the System and Status menu page, open the Pinpoint graphics editor

2. From the View menu, select Options.

3. In the Options dialog, select the Misc tab.

4. Select options for working in the graphics editor.

Option Description

Warn SaveInto Run Mode

If selected, Pinpoint displays a message asking if you want tosave the panel file before you enter Run Mode ; if not selected,Pinpoint automatically saves the panel file when you enter Run

Mode.

Make BackupCopy PanelFile

If selected, Pinpoint automatically makes a backup copy of apanel (.pin) file when that panel file is saved in the graphicsfolder. Backup files have the extension: *.bck.

Home PanelField

Enter (or browse to) a Pinpoint graphic file to use as the Pinpointapplication home panel. When you click the Home button of thePinpoint Standard Toolbar, the selected home panel opens.



TAC 612

Option Description

No Change Opens the home panel with no change to the current panel state.

Minimize Opens the home panel and minimizes the current panel.

Close (default) Opens the home panel and closes the current panel.

Default PaperOrientationField

Select the radio buttons to choose the default paper orientation(landscape or portrait).

Units ofMeasure

Select the units of measure for the size of your canvas. Thedefault is inches.

5. Click OK.

Drag and Drop

Pinpoint supports drag and drop of points from any CyberStation source, such asContinuum Explorer. With drag and drop, you can create an active control that isautomatically linked to the object it was dragged from.

The drag and drop operation can be performed with either the left or right mouse buttondepending on what type of control you want to create on the Pinpoint canvas.

Left Mouse Button

When you drag and drop an object (other than a door or area) with the left mouse button,an active text control button is created. When you select a door or an area, a door or areacontrol is created.

To drag and drop an object with the left mouse button, proceed as follows:

1. Open the panel where you want to add a control.

2. Open Continuum Explorer and adjust its size so that the Pinpoint panel is visible toone side.

3. Place the cursor over the object in Continuum Explorer that you want to place on thepanel.

4. Hold down the left mouse button while you drag the object onto the Pinpoint panel.

5. Release the mouse button.

An active text control button for this object appears on the Pinpoint panel.

Right Mouse Button

When you drag and drop an object with the right mouse button, you can choose a controlto be created from the object on the Pinpoint panel.

To drag and drop an object with the right mouse button, proceed as follows:

1. Open the panel where you want to add a control.

2. Open Continuum Explore and adjust its size so that the Pinpoint panel is visible toone side.




3. Place the cursor over the object in Continuum Explorer that you want to place on thepanel.

4. Hold down the right mouse button while you drag the object onto the Pinpoint panel.

5. Release the mouse button.

A popup menu appears listing the control types.

6. Select the type of control you want.

The object will appear on the panel represented by the control you selected.

Pinpoint Environment

Pinpoint operates in two modes: Design and Run.

• In Design Mode you create a panel, which allows you to draw, animate, and insertobjects, attach points, etc.

• In Run Mode the panel operates – showing assigned point values, opening/closingdoors, etc.–as you designed it to do.

Below are the basic components of the Pinpoint environment:

Pinpoint WindowFeatures

Description

Menu bar The Menu bar comprises the standard Windows program functionsand Pinpoint-specific functions.Tool bars The tool bars provide editing functions in Pinpoint. When no

applicable elements are open in the main window, the functionsare grayed-out indicating their unavailability.

Canvas The canvas represents the graphics panel. In Design Mode, youarrange controls and other components on the canvas as youwant them to appear on the panel when it operates in Run Mode.

Status bar The status bar along the bottom of the window indicates whetherPinpoint is in Design Mode or Run Mode, and at whatmagnification the panel is displaying. The status bar also providesyou with useful prompts, and visual indication of the status ofvarious keyboard functions.

Drawing Pinpoint Components

Components are objects that you place on the canvas (Pinpoint workspace) andmanipulate. A component can be a simple shape (such as a rectangle or circle) or acomplex collection of shapes or images.

To start drawing a component, you select the toolbar button or menu command thatcorresponds to a particular shape.



TAC 614

To … You can…

Draw a component ofequal proportions or at90 degree angles

Hold the SHIFT key while drawing a component. If youselect a rectangle tool button and then clicked in anempty area on the canvas while holding the SHIFT key,the application draws a square.

Resize a componentfrom the center

Hold the CTRL key while resizing a component.

Draw a lineClick the Line button and then click and hold the

mouse button in an empty area on the canvas until theline is the desired length. Release the mouse button.

Draw a polylineClick the Polyline button and then click in an

empty area on the canvas. Click again to place anendpoint or corner. Double click to finish drawing thecomponent. Click the right mouse button to cancel theaction.

Draw a polygon Click the Polygon button and then click in an

empty area on the canvas. Click to place each endpointor corner. Double click to finish drawing the polygon.Click the right mouse button to cancel the action.

Draw a rectangleClick the Rectangle button and then click and hold

the mouse button in an empty area on the canvas.Drag the pointer until the rectangle is the width andlength you want.

Draw a polycurveClick the Polycurve button and then click in an

empty area on the canvas. Click to place an endpoint,two control points and another endpoint. Double click tofinish drawing the curve.

Draw a closed curveClick the Closed Curve button and then click in an

empty area on the canvas. Click to place an endpoint,

two control points and another endpoint. Double click tofinish drawing or click the right mouse button to cancel.You can assign a fill color to a closed curve.

Draw an ellipse Click the Ellipse button and then click and hold

the mouse button in the canvas. Drag the pointer untilthe ellipse is the size you want.

Add textClick the Text button and then click in an empty

area on the canvas. Right click the text to edit.




To … You can…

Add an imageClick the Image button to open a standard dialog

from which you can select an image to insert on thecanvas in the following formats:

• .bmp

• .ico

• .jpg

• .emf.dib

Configuring a Pinpoint Panel

1. From the File menu, select Configuration to display the Graphics dialog for thepanel you are editing. The General tab page of the Graphics dialog appears.

2. Enter the configuration information in the fields described below:

Description General description of the panel, up to 32 letters.

Graphic Panel File File created when the panel is saved. By default it

takes the same name as the panel object. All files aresaved to a specific location (shared in a multi-userenvironment) usually set at c:\ProgramFiles\Continuum\NewGraphicsFiles. Graphic panelfiles have a “.pin” extension.

Plain EnglishProgram to RunWhen the Panel isOpened

Use this field to select a program or Infinity programwhen the panel is in Run Mode.

Stop When Panel isClosed

If selected and you have selected a Plain Englishprogram to run when the panel opens, the PlainEnglish program stops running when you close the

panel or put it into Design Mode. If not selected, thePlain English program continues to run when thepanel is closed or put in Design Mode.

Window Size Field Select whether the panel should be maximized orretain the position/size of the panel when it was lastsaved.

Scroll Bars Check this checkbox to enable scroll bars in Run orDesign Mode. Without scroll bars you can still viewparts of a panel that do not initially appear onscreen,because the Pinpoint window can be resized bystretching the frame around the panel.



TAC 616

Active Polling RateOnly

Check this checkbox to enable the active polling.

3. Select the Canvas tab, and select preferences for the panel workspace, which iscalled the canvas.

BackgroundColor

Select a background color for the panel from the drop downlist.

BackgroundFile

Enter the location of the background image file displayedwhen the panel is loaded. If the background file changes,

the panel reflects the latest change.

If you choose a background file that is not located in thedefault background folder specified in the Options dialog, acopy of the file is placed in the default folder.

If you choose a background file for your panel, it willoverride the background color. For example, if you have agray background for your panel and then you add a graphicimage to be the background, the image will show and thebackground color will not.

A background file is optional.

Canvas Width/

Height

Enter the dimensions of the canvas.

4. Select the Object List tab to view the CyberStation objects attached to Pinpointcontrols in the current panel.




Object name Name and path of the CyberStation object

Component name Name of the Pinpoint control that represents the object inthis panel

Polling Rate Polling rate in milliseconds, which determines how oftenthe panel can be updated when object informationchanges.

Delete Deletes the selected object.

Go To Selects the active component in the panel and brings it tothe center.

Find Object Finds an object selected by the user.

Replace With Replaces the object found in the Find Object field with anobject selected by the user.

Replace Object Replaces the selected object with the one specified bythe user.

Replace AllObjects

Replaces all selected objects with the one specified bythe user.

6. If you want to attach a single object to this panel, click the Security Level tab andselect a single object.

7. Click OK.



TAC 618

Selecting Default Properties for Components

Before adding components to a panel, you can set their default properties. The propertiesyou select are common to all component types and are used as the initial settings forevery component added to the panel. Your settings apply only to new object and do notapply to existing objects.

1. Right click the canvas, and select Default Properties from the pop up menu.

2. In the Line tab, define the default appearance of lines in a component:

• Select line color, style, and width. Dashed or dotted lines can be used only when 0Point is selected for line width.

• If you do not want to display lines when the panel is in Run Mode, check theTransparent checkbox.

3. Select Fill tab to define component fill properties.

A solid fill, a foreground color without hatching, is the most commonly used fill. Ahatched fill with a background color can also be used. When Transparent Fill is

selected, a component’s fill won’t show when the panel is in Run Mode. SelectingTransparent Fill locks out the use of the other options on this tab.




4. Select the Font tab, and select font properties to define the appearance of text in acomponent.

Because True Type fonts are the only fonts that support rotation, text is limited toTrue Type fonts.

5. Click OK.

Creating an Active Text Component

An active text control can display the text of any object attribute. You can also use a textbox as a label for a value displayed in another text box or other active component.

1. From the Drawing tool bar, select the Text icon.

Text

2. Click a location on the canvas to place the text box. Adjust the size, placement, andappearance of the component as needed.


Resize the component Select any of the points on the border of thetext box and drag the point to increase ordecrease size.



TAC 620


Move the component Hover the curser over the center of the text

box until the cursor changes to , andthen click and drag the box to a differentlocation.

You can also use your keyboard arrow keys orthe nudge buttons to move the text box in

small increments.

Edit the display properties ofthe component

Right click the text box, and select Displayproperties. Edit line, fill, font, and otherproperties, and click OK.

3. To make this text component an active component (tied to a point object ), select the

text component, and click the Text icon from the Active Components toolbar.

The Active Text tab page of the Active Text Object dialog is displayed.

Object Enter or use the browse button to locate the path to the point objectand attribute you want to attach to the component. Browse or typein the path to a Continuum point and attribute.

User Entry Check this checkbox to change the value of the point in RunMode. Ifthe checkbox is not selected, the value will be read only.

High/Low

Limit

Enter the maximum and minimum values accepted for this pointwhen user entry is enabled.

4. If the selected object is attached to alarm(s), select the Alarms tab, and use thecolorwells attached to each alarm to select the color the text changes to in responseto the alarm event.

5. Select the Misc tab.

6. If you want to adjust the polling rate, enter a new value for Rate.

The polling rate determines how often a point is queried per millisecond to see if its

value has changed.7. Check the ToolTips checkbox if you want to display a tooltip when the cursor lovers

over the text box, and then specify the tooltip content:

• Select Attached Object if you want to display the name and path of the objectattached to the text box.

• Select User Defined, and enter the appropriate text if you want to display customtext in the tooltip.

8. Click OK.

9. To save and test the component, click the Run Mode button in the Standard toolbar.

Click the Design Mode button to return to editing the panel.




Inserting Images

To insert an image to use in a component, perform the following steps. You can insertpredefined images from the image library or browse images created another application.

1. From the Insert menu, select Image Library.

2. In the PinPoint images dialog, expand folders to view the list of images, and select animage to display it in the preview area.

3. To insert a custom image, click the Browse button to locate the folder that contains

the image.

4. Double click an image to insert it in the current panel.

Continue inserting images as needed.

5. Click Close.

Creating an Active Switch Control

An active switch control always toggles between two discreet values, i.e., binary or digitalvalues such as on and off.

1. Create two graphics to represent the two state of the switch control:

• You can draw the graphics with the Pinpoint drawing tools.

• You can insert bitmap images in the panel.

2. Place the graphic you created to symbolize the off state on top of the graphic youcreated to symbolize the on state, completely covering the on graphic.

Do not group the graphic together.

3. Select the graphic object for the off state, and select Active Components/Switches, or select the Active Switch button from the Active Components toolbar.

4. In the Object field in the Active Switch tab page, enter the full path or click thebrowse button to locate the point, object, or object attribute that the switch controls.The object or attribute must have only two states (as a digital point does). Forexample, you can have the switch change the State of a program – ENABLED or

DISABLED.5. Select the User Entry checkbox if you want to allow users to toggle the state of the

object or attribute (for example, to allow an operator to turn a light on and off).

6. Click OK.

7. To save and test the component, select the Run Mode, or select the Run Mode

button from the Standard toolbar. This action saves the panel.




TAC 622

Creating an Active Rotation Control

An Active Rotation control can be any shape or combination of grouped shapes, but it ismost useful in a circular style control. For example, you can draw a fan or pump withspokes inside the circular part of it, and define it as an Active Rotation Control. When thefan or pump is on, the spokes continuously rotate.

1. Create the graphic to represent the rotating object:

• You can draw the graphic with the PinPoint drawing tools. Group the shapes that

make the graphic as a single element.• You can insert a bitmap image in the panel.

2. Select the graphic object, and select the Active Rotation button from the Active

Components toolbar.

3. In the Active Rotation dialog, select the point the control represents and the rotationproperties of the control.

Object Enter the full path or browse to the point the controlrepresents.

This is an option; you do not have to link the rotation to anobject. It can be used simply for effect.

Rotate when: Select when rotation occurs:

• Always indicates that the object always rotates. Thereis no need to select a point.

• Value is on indicates that the object rotates wheneverthe value of the point is not zero. You can use Value ison with analog (numeric) or digital (binary) points.




Direction Choose a clockwise or counterclockwise rotation.

Rotation Rate Enter the rotation rate for the control. The valid range forthis field is between 100 and 5000 milliseconds.

Angle Enter the angle in degrees the control will rotate at eachinterval based on the Rotation Rate. The valid range forthis field is between 1 and 180 degrees.

Select PivotPoint

By default, a component chosen to be an Active Rotation object will rotate about its center. To change the center of

rotation, click the Select Pivot Point button. The Center ofRotation dialog appears. Either drag with the mouse oruse the Nudge Pivot buttons to move the rotation selector

to the desired center of rotation. Click OK.

4. Click OK.

5. To save and test the component, select the Run Mode, or select the Run Mode button

from the Standard toolbar. This action saves the panel.


Creating a Personnel Picture Control

You can create personnel picture control to display a photo and information fromPersonnel objects in a graphics panel. For example, you can create a control thatdisplays a photo name and access card number of a person who requests access at aspecific door.

1. Click the Personnel Picture Control from the Active Components toolbar.

2. Specify the properties of the control.



TAC 624

Person: Either type in or browse for the Personnel object of the personwhose photo you want to display, or for an attribute that stores apersonnel object. For example, any of the following doorattributes may be used:

• LastPersonEntered

• LastPersonExited

• LastInvalidEntry

• LastInvalidEntryExit

If you select one of these attributes, you can display the person’sphoto when the person enters/exits through the door.

Fade:Delay Time

Enter the number of seconds you want to display a photo beforeit fades. If the delay is 0, the personnel photo will not fade.

Fade: File Either type in or browse for the path to the personnel photo.

User Entry Select this checkbox to change the control right from the panel inRun Mode.

Beep Whenthe PictureChanges

Select this checkbox to hear a beep when a new photo appears.

3. Click OK.




Creating an Active Bar Control

A bar control is similar to a thermometer. It fills as the value rises and empties as thevalue falls.

You can change the value of the point object that the bar component is tied to. Users canclick the left mouse button while in Run Mode, and an image of a calculator will appear.Users can then use the mouse to click the calculator buttons or use the keyboard to type

in the new value, and click OK on the calculator to set the new value.1. From the Drawing toolbar, select the rectangle icon.

Rectangle

2. Draw a rectangle on the canvas by holding down the left mouse button and movingthe mouse diagonally.




3. If you want to edit visual properties of the rectangle, such as color, right click andselect Display Properties from the popup menu. Edit the properties and click OK.

6. Select the rectangle and select the Active Bar icon from the Active Componentstoolbar.

5. In the Active Bar Object dialog, select the object the bar represents and the propertiesof the bar.

Object Enter or click the browse button for the point andattribute.

User Entry Select the check box to allow users to change thevalue of the point from the panel.

Top of Scale Enter the maximum value to represent a completelyfilled bar.

Bottom of Scale Enter the minimum value to represent an empty bar.

Direction Select the Horizontal or Vertical radio button toindicate which direction you want the bar to grow inproportion to the value.

6. Click OK.




Creating an Active Button Control

You can create a button control to trigger one of the following events or actions:

• Open an object

• Open a panel

• Replace a point

• Run a Plain English program

• Start a Windows program

• Stop a Plain English program

• Toggle the value of a point

A button can be any shape or can be an image. For a button to change color whenpressed, create an active animated button rather than a button. Buttons do not changeappearance.

1. From the Drawing toolbar, select a shape or image button.



TAC 626

2. Select a location in the canvas to place the shape.

3. If you want to edit visual properties of the component, right click and select DisplayProperties from the popup menu. Edit the properties, and click OK.

4. Click the Active Button toolbar icon to display the Active Button Object dialog.

5. Select an action from the Action dropdown list.

After you select an action, the Active Button data entry fields change to reflect theinformation required for that action. The following table describes how to configureeach option.

If you select… Then…

Open Object Enter or click the browse button to specify the full pathname for the object the button opens.

Open Panel Enter or click the browse button to specify the full path forthe graphics panel the button opens. Under CurrentWindow, select what happens to the display of thecurrent panel (the panel containing the button) when thenew panel is opened.

Replace Point Enter or click the browse button to specify the full pathname for the point that will be replaced when a userclicks the button.

Note: When you go into Run Mode, click thereplacement point you have selected to become anactive button. You are prompted for the point youwant to replace.

Run Plain EnglishProgram

Enter or click the browse button to specify the full path ofthe Plain English program that you want to run when auser clicks the button.




Start WindowsProgram (enables youto start any installedWindows applications,such as Notepad orExcel, or to create or editCyberStation Objects)

If you want to open another application, enter or click thebrowse button to specify the executable file (.exe) of theWindows program you want the button to launch. Enterany arguments, such as launching another application oropening a specific file that should be passed to theWindows program in the Command Line Arguments field (optional).

If you want to create a button to create, edit, or open aCyberStation, click the Button Wizard button, and make

selections from the wizard as prompted. Click Finish toclose the wizard. The Windows Program andCommand Line Arguments fields are populated with thevalues needed to create or edit the object you specified.

Stop Plain EnglishProgram

Enter or click the browse button to specify the full path ofthe Plain English program you want to stop when a userclicks the button.

Toggle Value Enter or click the browse button to specify the full path forthe point you want to turn on or off (or enable/disable,etc.) when a user clicks the button.

Current Panel Under Current Window, select the desired state that thecurrent window should be in after the Active Button isclicked.

3. To execute Plain English (PE) commands in addition to the button action you definedin step 5, select the Plain English script tab, and enter the PE script. Click theCheck button to verify that the script has no syntax or other errors.



TAC 628

PE scripts can execute any command-line command. PE scripts cannot have localvariable declarations or labels. PE scripts are executed before the selected ActiveButton performs its action (i.e., open panel, open object, etc.).



The polling rate determines how often a point is queried per millisecond to see if itsvalue has changed.

6. Select the ToolTips checkbox if you want to display a tooltip when the curser hoversover the text box, and then specify the tooltip content:



7. Click OK.

8. To save and test the component, click the Run Mode button in the standard toolbar.


Creating an Active n-Stage Animation Control

An active animation control displays a series of images that correspond to analog ordigital values of a point that you specify. For example, you could use a sequence ofpropeller images to indicate a fan that is turned on.




1. Click the Active Animation toolbar icon to display the Active Animation dialog.

2. Select the animation type.

The selection you make in the Animation Type field determines the appearance ofthe tab page.


Create animation for analog points, allowingimages to be shown on value ranges

Select Analog Animation.

Proceed to step 3.

Create animation for digital (binary) points,allowing images to represent the two states ofthe point (enabled/disabled, on/off, etc.)

Select Digital Animation.

Proceed to step 4.

3. Select the point, images, and valid range for analog animation.

C:\Program Files\Graphics\Graphic File1C:\Program Files\Graphics\Graphic File2C:\Program Files\Graphics\Graphic File3C:\Program Files\Graphics\Graphic File4

Value Enter or click the browse button to specify the full path of to the analogvalue to be used to control which image is viewed for the animation.

Image Ranges Value ranges for each chosen image file. The ranges are createdfrom the low and high limit you enter.



TAC 630

Image Files List of the images used for this animation.

To create and organize the list of images, use the four icons abovethe preview area:

Insert a new image – Click this icon image and type in the filename and path.

Delete an image – Select the image to be deleted and clickthis icon.

Move an image one up the list – Select the image to moveand click this icon.

Move an image one down the list - Select the image to moveand click this icon.

Also, to edit an existing image, double click the image and make theappropriate changes in the open edit box.

Preview Click this button to preview the files in the Image Files field.

High/LowLimit

Enter maximum and minimum values. If you change either of thesevalues, the ranges are automatically calculated when the edit boxes

lose their focus.Change By default, the ranges are split evenly over the range limits entered

in the High Limit and Low Limit fields. Use this button to changethe high limit for a selected range (and as a result the low limit forthe next higher range) in the Image Range field.

Reset Click this button to reset all the ranges to their default ranges ({Highlimit – Low Limit}/ # of files in the image list). This is only applicableif you have made changes to the default range.

HideAnimation ifAbove/BelowRange

Select this checkbox to hide the animation if the value of the point isoutside the limits of the range.

8.

Select the point, images, and animation properties for digital animation.




C:\Program Files\Graphics\Graphic File1C:\Program Files\Graphics\Graphic File2C:\Program Files\Graphics\Graphic File3C:\Program Files\Graphics\Graphic File4

Value Enter or click the browse button to specify the full path of the binaryvalue to be used to control which image is viewed for the animation.

Image Files List of the images to be used for this animation.

To create and organize the list of images, use the four icons above

the preview area:

Insert a new image – Click this icon and type in the file nameand path in the edit box.

Delete an image – Select the image to be deleted and clickthis icon.

Move an image one up the list – Select the image to move andclick this icon.

Move an image one down the list - Select the image to moveand click this icon.

Also, to edit an existing image, double click the image and make theappropriate changes in the open edit box.

Preview Click this button to preview the files in the Image Files field.

Animate WhenOn

Select this checkbox for the animation to continue repeatedly whenthe value is on. Deselect this checkbox for the animation to continuerepeatedly when the value is off.

Animate onlywhen Changeof State

If this checkbox is selected, the system runs through the image listone time for change of state on, and then in reverse order for changeof state off. This cycle repeats for every change of state.



TAC 632

Invisible WhenOff

Select this checkbox to make the image invisible when it is notanimating. (when value = off)

Current FrameWhen Off

When the animation is off and visible, select this checkbox for thecurrent frame to appear. Leave this checkbox unselected for the firstframe in the image list to appear.

Image Rate Rate (in ms) the system cycles through the images selected inImage Files.







8. Click OK.



Creating an Active Animated Button Control

Like the active button, the animated button can be any shape. It also supports the sameactions as an active button, but can change appearance when an event occurs.

1. From the Drawing toolbar, select a shape.

You cannot use text or images as an active animated button.

2. Select a location in the canvas to place the shape.

3. Specify the shape, and click the Animated Button icon on the toolbar.

4. In the Active Animated Button dialog, specify trigger settings.




Trigger Enter or click the browse button to specify the full path to theobject used to trigger the animated effects of the button. The

trigger is the point or attribute that initiates (“fires”) an event.Trigger Options Select the event that triggers button animation:

• On/Off

• Alarm

• Ranges

Disable Action Select this checkbox to disable the trigger action on thebutton.

Action Field Select an action from the Action dropdown list.



TAC 634

Object DropMenu

If needed, enter or browse to the action object.

Current Window Select the checkbox that indicates what will happen to thecurrent window when the panel is launched.

5. Select the Options tab.

The settings in this tab depend on the trigger option you selected in the ActiveAnimation Button tab.

TriggerOptionValue

The values in the Trigger Option Values list are determined by theselection you make in the Trigger Options in the Active Animated button tab. In the above example, the choices are On/Off. Use this tabto determine how the button appears in each state.Note: Both On and Off require separate configuration.

Fill Select this checkbox to select Fill options for the state selected in theTrigger Option Value field. The Fill Properties dialog appears. Selectfill settings for the button, and click OK.

Visible Select this checkbox for the button to be visible in that state.

Blink andBeep

Select these checkboxes for the button to blink and/or beep in thatstate.




DisplayValue


6. To execute Plain English (PE) commands in addition the button action you defined instep 5, select the Plain English script tab, and enter the PE script. Click the Check button to verify that the script has no syntax or other errors.




The polling rate determines how often a point is queried per millisecond to see if itsvalue has changed..




10. Click OK.





TAC 636

Inserting a Scale

A scale active component works with a gauge active component to display the value of apoint object that you specify:

• The scale provides the visual characteristics: upper and low limits, divisions andsteps, and labels. Create the scale before you create the gauge.

• The gauge provides the graphic element that represents the point value on the scale,such as the needed on a circular dial.

To insert a scale, follow these steps:1. From the Insert menu, select Scale.

The Scale dialog appears with the default scale type as linear.

2. Select settings that define the appearance and labeling on the scale.

Type Select linear or circular.

Orientation If you selected Linear, select Horizontal or Vertical.




Start andSweep AngleFields

Enter the number of degrees from vertical in a clockwise directionas the start angle. The default start angle is 90 degrees. Thedirection of the sweep angle is always clockwise. The defaultsweep is 180 degrees.

DirectionRadioButtons

Use these radio buttons to choose the direction that the numberswill appear on the scale.

• Select Clockwise and the numbers appear clockwise fromlow to high.

• Select Counterclockwise and the numbers appearcounterclockwise from low to high.

Scale Color Select a color for the scale using the Scale colorwell dropdown list.

Limits Use these fields to set the high and low limits of the scale. Thelimits can be positive or negative (you can set the number ofdecimal places that appear in the Decimal Places field). The High

limit is the largest number displayed on the scale. The Low Limit isthe smallest number displayed on the scale.

Subdivisions Use these fields to set the number of Subdivisions and Steps thatappear on the scale. Subdivisions are the tiny tick marks betweeneach Step (major tick mark).

Show Units Use these fields to type in and select the color for a short textstring usually used to display the units of scale. Select the coloryou desire from the colorwell, which opens like a drop down list.

ShowNumbers

Select Show Numbers to display numbers on the scale.

Type in or scroll to the number of decimal places you want todisplay in the Decimal Places field.

Select the color you want the numbers to appear in Color field.

Use the Position drop down list to enter where you want thenumbers to appear. The options depend on the type of scaleselected.

3. Click OK.

Inserting a Gauge

To insert a gauge, follow these steps:

1. Use the drawing toolbar to create the graphic representing the gauge reading on thescale you drew in the previous procedure.



TAC 638

2. Position the graphic on the scale, and select the graphic (not the scale component).

3. From the Active Components toolbar, select Gauge. The Gauge dialog appears.

4. Select settings for the gauge.

Object Browse for or enter the Continuum point that the gauge willindicate.

Scale Enter the upper and low limits of values shown.

Direction Select the direction in which the numbers will appear on thescale:

• Selecting Clockwise causes the numbers to appearclockwise from high to low.

• Selecting Counterclockwise causes the numbers toappear from low to high in a counterclockwise direction.

SweepAngle

Enter the angle, in degrees, (thedirection of the sweep angle is alwaysclockwise) for the gauge. For example,a gauge with measurements that form acomplete circle has a Sweep Angle of360 degrees. The default sweep angleis 310 degrees. The example to the

right shows the sweep angle of 180degrees.

Select PivotPoint

Click this button to display the Select the Center of Rotationdialog. Use this graphic device to position the pivot point of thegauge. In the above example, the gauge appears in thedefault pivot position.

5. Click OK.

The gauge is now capable of moving to the corresponding position on the scale whenthe value it represents changes.




Importing a Pinpoint Panel

Use this procedure to import a Pinpoint panel file that was created in anotherCyberStation installation. For example, a TAC dealer could create custom panels for youon the dealer’s CyberStation system.

1. From the File menu, select Import Panel File.

2. In the Import Panel File dialog, select a panel, and click the Import button.

A warning telling you that the imported file will completely replace the contents of the

open panel appears.

3. Click OK.

Creating Windows Controls

Windows controls are graphics that visually represent common components on a controlpanel, such as buttons, sliders, and LED displays. Like active components, Windowscontrols are associated with CyberStation points. Two special Windows controlsrepresent CyberStation area and door objects.

Windows controls do not require you to create a graphic to represent the control. Eachcontrol has a predefined set of images that represent the control in its various states.Many controls include several image sets to choose from.

Creating a Button Control

Follow these steps to create a Windows button control.

1. From the Windows Controls toolbar, select the button control.

The following control is created for you on your Pinpoint working area.

2. Click the button control to display the Active Button Object dialog.

Note: The properties of this Window control are the same as the standard Pinpointactive button control. Refer to the section in this chapter called Creating anActive Button Control for detailed information about these properties.



TAC 640

3. After you select the properties you require, click OK.

Creating an Edit Box Control

Follow these steps to create an edit box control. You can use an edit box control todisplay values or to accept user entry values.

1.

From the Windows Controls toolbar, select the edit box control.The following control is created for you on your Pinpoint working area.

2. Select Edit from the menu bar, and click Object Properties.

3. In the Edit Box Object Properties dialog, select the properties you require.

Object Enter or click the browse button to specify the pathto a Continuum point and attribute.

User Entry If selected, users can enter values into the editcontrol, just as they do for active text controls. If notselected, the content of the edit box is read only.

3D Border If selected, the control has a border.




• Select the ToolTips checkbox if you want to display a tooltip when the curserhovers over the text box, and then specify the tooltip content.





6. Select User Defined, and enter the appropriate text if you want to display customtext in the tooltip.

7. Click OK.



Creating a Switch ControlFollow these steps to create a Windows switch control.

1. From the Windows Controls toolbar, select the Switch Control.


2. Select Edit from the menu bar, and select Object Properties.

3. In the Switch Properties dialog, select the properties you require.

Object Enter or click the browse button to specify the path to aContinuum point and attribute.

Style Under Style, click the down arrow, and then select the switchgraphic you want to use.

User Entry If selected, users can click the switch to toggle the attachedobject value.




6. Select the ToolTips checkbox if you want to display a tooltip when the curser hoversover the text box, and then specify the tooltip content.



TAC 642



7. Click OK.



Creating a Combo Box ControlFollow these steps to create a Windows combo box control.

1. From the Window Controls toolbar, select the Combo Box Control.



3. In the Combobox Object Properties dialog, select the properties you require.

Object Enter or click the browse button to specify the path to a Continuumpoint and attribute.

List Items The List Items are the possible values of the attached object that willbe displayed in the dropdown list of the combo box control.

Use the four icons at the top of the List Items field:

Insert a new list item – Click this icon and type in the list itemin the edit box.

Delete a list item – Select the item to be deleted and clickthis icon.

Move an item one up the list – Select the item to move and

click this icon.

Move an item one down the list - Select the item to move andclick this icon.

Also, to edit an existing list item, double click the item and make theappropriate changes in the edit box.

Autofill Click this button to automatically insert the values of a selected objectin the List Items field.

Note: A message will appear informing you that the current list ofitems will be overwritten with the newly selected values.








• Select Attached Object if you want to display the name and path of the object

attached to the text box.• Select User Defined, and enter the appropriate text if you want to display custom

text in the tooltip.

7. Click OK.



Creating a Slider Control

Follow these steps to create a Windows slider control.

1. From the Window Controls toolbar, select the Slider Control.



3. In the Slider dialog, select the properties you require.



TAC 644


Top of Scale Enter the maximum value to represent a completely filledslider.

Bottom ofScale

Enter the minimum value to represent an empty slider.

Integers Only Check this check box if you want the slider scale to be inwhole numbers







7. Click OK.



Create a Video Control

A video control window is used to display a live or recorded video stream from a sourcevideo object – a surveillance camera or a file containing a recorded video – that youassign to the video control.

Follow these steps to create a video control.

1. From the Window Controls toolbar, select the Video Control.

A new video control window appears.




2. Right click the empty video control window, and select Display Properties from thepopup menu.

3. Enter the name of the video control window.

4. Check the Preserve Original Video Aspect Ratio checkbox if you are going toresize the video control and want to preserve its original aspect ratio in the resize.

That is, it prevents you from accidentally distorting the dimensions of the image. Thisbox is not checked, by default.

Note: This checkbox is for live video only. If you are using a video source file, thissetting does not apply.

5. Click OK.

6. Right click the video control, and select Object Properties.

In the Active Video tab, you must select either a video source file or a video sourcedevice (surveillance camera.)



TAC 646

Note: If you wish to select a source object, it must be an object that has two states –something that can be on or off, enabled or disabled, set or cleared, and so on.

Live or recorded video is displayed only when the object is an on/enabledstate. It does not display when it is in an off/enabled state. If you do not selecta source object, live images are displayed continuously, and recorded file videois played either once (by default) or continuously, via the Loop Forever checkbox (described in the following text).

7. If you select a source data object, click the browse button in the Play when objectvalue is On field, search for, and select an object that has an on/off (orenabled/disabled) state, such as an alarm.

8. Click the Video Source Device radio button if you want to display live images from asurveillance camera.

If you are selecting Video Source File, go to step 11.

9. If you clicked Video Source Device, select a video driver from the dropdown menu,and then go to step 12.

Your system must be configured with video surveillance-camera software in order forvideo driver selections to appear in the dropdown menu.

The following video hardware is recommended for use with the video control window:

• CreativeLabs WebCamGo+ USB camera

• Hauppage WinTVGo Model 190

• Any capture board with VGA/DirectX compatibility

• Integral’s FlashBus cards




10. If you selected Video Source File, click the browse button in the Video Source File field to browse for a AVI, MOV, or MPG file whose video recording you want to playback. Use the four checkboxes to configure the file’s video display.

Select… If you want…

Loop Forever The recorded video in the file will play back continuously(over and over again). Remove the check from this box ifyou want the file’s recorded video to play back only once.

Note: If you have selected a source data object, the video

is played back (once or continuously) only when theobject is on/enabled. If the object is turned off orbecomes disabled during playback, the playbackstops and the image disappears from the videocontrol window.

Show configurationmenu

Access to the video control window’s configuration popupmenu – accessible in either deign mode or un mode. Thismenu allows you to modify the display in a number of ways,including speed and volume.

Remove the check to deny access to the configurationmenu – for example, if you don’t want security guards orcertain other users to change the video display.

Show Play Controls To display a play button, a menu button, and a playbackslider control along the bottom of the video control window,as shown in step 12. Remove the check to hide thesecontrols.

Auto Play whenpanel loads

The video control window to begin playback automatically,as soon as its panel loads on the screen.

11. Click OK.

Live images – If you are viewing live video from a device (surveillance camera) thelive image appears. For example:



TAC 648

Recorded images – If you are viewing a recorded video file, the beginning of therecording appears (in a stopped state) in design mode in your video control window.For example:

Note: Your video control window can play a video stream in either design mode or

run mode .

In the recorded video image above, notice the play controls along the bottom of thecontrol window. Live images (from a video source device) do not display playcontrols.

Play Controls – In run or design mode, the play controls function as follows:

• Play button Click the play button to begin or resume the playback of a video.This button becomes a stop button when the video is playing.

• Menu button Click the menu button (next to the play button) to bring up theconfiguration menu at any time, while the video is playing or stopped.

• Playback slider control The length of the slider control represents the

entire duration of the recorded video. The position of the slider control buttonrepresents the current spot in playback. For example, if the slider button islocated in the middle of the slider, playback is 50 percent completed. Use theslider button to go to a specific spot in the recording. Click and drag the slidercontrol button right to advance the recording forward, as well as all the way to theright to go to the end of the recording. Likewise, slide it left to go back to aprevious spot in the recording, or all the way to the left to restart the entirerecording.

12. Configure the size, sound, and speed of your video stream via the Configurationmenu.




(You must have checked the Show configuration menu checkbox in the VideoProperties dialog.) This menu also allows you to make a “still” copy of the imageinside the video control window, open and close the window, and pause, stop, andresume playback.

To use this menu, right click on the video control window in run or design mode. TheConfiguration popup menu appears.

Select… To…

View Select the size of the image from its popup menu, as shown

above.

• Half Size reduces the image by 50 percent

• Double Size increases the image to twice its current size

• Normal Size restores the image to its original (100percent) size

Volume Adjust the video’s sound (if the video has sound) using thevolume slider control.

Click and drag the slider button down to decrease volume.The integer inside the slider button indicates the percentageof full volume. Likewise, drag the slider up to increasevolume.

Speed Adjust the playback speed using the speed slider control.

Click and drag the slider button down to decrease playbackspeed. The integer inside the slider button indicates thepercentage of speed, where 100 percent is normal speed.

Copy Make a still snapshot of the image currently inside the videocontrol window. This is useful if you want to show a picture ofsomething important happening at a precise moment duringthe course of a video recorded. This image can be pastedinto documentation files, for example.

Note: Copy copies the image only, not the video controlwindow.









TAC 650

16. Click OK.



Creating a Check Box Control

Follow these steps to create a Windows check box control.

1. From the Window Controls toolbar, select the Check Box Control.

The following control is created for you on your Pinpoint workingarea.


3. In the Check Box dialog, select the properties you require.


User Entry When selected, users can click the control to check thecheckbox or to the clear the check.










7. Click OK.



Creating a Web Browser Control

A web browser control allows you to show web pages inside a Pinpoint panel. This page

can be either a URL address or a local HTML file. You control which web pages todisplay in a web browser control window, based on certain trigger conditions. When apoint is on, one page is displayed; when the point is off, another web page is displayed.For example, you can display different web pages, depending on the current state of analarm – that is, when an alarm is active, acknowledged, returned, and so on. This controlcan also host any type of active document, such as Microsoft Word or Excel.

You may want to use the web browser control to display documentation, such asinstructions for handling an active alarm.

Note: Your web browser control window must be in run mode in order for the websource object to display in the window.

To create a new web browser control:

1. Click the web browser (globe) icon in your Window Controls toolbar.

An empty web browser control window appears.

2. Right click the control, and select Object Properties from the popup menu.

The Web Browser Control Object Properties dialog appears. You must assign atrigger for the web browser control. The trigger comprises a string object(representing a URL address or an HTML file) and a trigger, which defines thecondition under which your web page appears.

3. Click the browser button in the String Object field, and select a Continuum stringobject.

4. Select a Trigger Option from the dropdown menu.

String URL By default, you may simply bring up a URL or HTML page in yourweb browser control window, every time the web browser windowopens – that is, whenever the string object that you assigned isturned on. When you choose this String URL, the Options tab istherefore not selectable.



TAC 652

On-Off Select this option when you want to launch two different webpages in your web browser control– one when the string object isturned on, and the other when it is turned off. When you selectOn-Off, the Options tab becomes selectable.

From the On-Off Options tab, in the On field, enter a URLaddress, or click the browse button to specify an HTML file thatyou want to launch in your web browser control window whenyour string object is turned on. Likewise, in the Off field, enter aURL address, or click the browse button to specify an HTML file

that you want to launch in your web browser control window whenyour string object is turned off.

Alarms Select this option when you want to open different web pagesaccording to a particular state of an alarm, when an alarm istriggered on you string object. For example, you can launch oneURL or HTML file when an alarm is active, another when it isacknowledged, another when it is returned, and so on. When youselect Alarms, the Options tab becomes selectable.

In this Options tab, there are five fields; one field for each sate ofan alarm. In each state’s respective field, enter a URL address oruse the browse button to specify an HTML file. When your stringobject triggers an alarm, the web page that you specify will open

according to the state of the alarm.

5. In the General tab, you can specify a home page for your web browser controlwindow. To do, simply enter a URL address in the Home Page field, or click thebrowse button to browse for an HTML file to launch as a home page.

When the web browser control is active, click the home icon at the top of thecontrol to go to the specified home page.

6. From the General tab, you can select user entry mode and theater mode by checkingthe User entry URL and Theater Mode checkboxes, respectively.

User entry URL This feature allows you to navigate in run mode with a manualentry. To do so, enter a URL address in the edit field at the top

of the web browser control window.Theater Mode This feature displays the web browser control window without

the navigational buttons and edit entry field. Using theatermode, you may create buttons that trigger certain conditionswhereby a different web page appears based on whichparticular button you click. Each button would be labeledaccording to the web page that it retrieves.







9. Click OK.



Creating a Progress Bar Control

Follow these steps to create a Windows progress bar control.

1. From the Window Controls toolbar, select the Progress Bar Control.



3. In the Progress Bar Object Properties dialog, select the properties you require.

Object Enter or click the browse button to specify the path toa Continuum point and attribute.

High/Low Limit Enter maximum and minimum values. If you changeeither of these values, the ranges are automaticallyimplemented on the progress bar.

Display Value Select to display the progress bar values.

Units Select to display units with the value.

Vertical Select to change the progress bar from horizontal tovertical.

User Entry If selected, users can click the control to display acalculator that they can use to change the valueassociated with the control.

4. Click the Colors tab to view the Colors dialog. This screen allows you to select colorsfor:

• Text

• Background

• Start

• End







TAC 654



8. Click OK.



Creating a Trend ControlA trend control is used to display points of data, plotted on a trend graph from one ormore sources (data objects) over a period of time. Data from the objects are displayed inuser-customized formats on a graph within the trend control window. These can be line,point, or bar graphs. The trend window consists of four main areas:

• Graph plot area, with optional grid (center of window)

• Pen units scale (left side of window)

• Time scale (bottom of window)

• Pen labels area (beneath the time scale by default). This area lists the pens (a key tothe data object sources) that are plotted on the graph. You may move the pen labels

area to the right side of the trend control windows via the Graph Properties dialog,discussed later in this section.

The trend window with its four main areas is shown below. In this example, the trendcontrol has three pens, each of which is polling data for temperature, in degreesFahrenheit:

You may select the color and plot-point design of each pen, via the pen style properties.




Note: Your trend control window must be in run mode in order for Pinpoint to polllive data from the data source objects and plot it on the graph.

Margin The area surrounding the entire trend control window is called themargin . You may change the margin color (as well as many othercharacteristics of the graph) via the Graph Properties dialog,discussed later in this chapter.

Scrolling Pen scale units begin at 0 at the bottom of the graph, by default. Youmany scroll the pen units scale and the time scale by placing the

cursor over one of the scales, holding down the left mouse button,and dragging the scale up or down (for the pen scaled) or from side toside (for the time scale). You may also scroll up the pen units scale toshow negative unit values. Scrolling the scales is useful when youwant to demarcate a certain area of plots on the graph.

Zooming Your trend control allows you to zoom in and zoom out on the graph.The zoom features are contained in the graph’s run mode menu.

About Pens

All pens belonging to a trend control are displayed in the window’s pen labels areas. Thelist of pens in the pen labels area is scrollable if there are more pens than the area candisplay. In the pen labels area, each pen is listed as a pushbutton. Each label name

appears on its respective button.

You may select a pen as follows:

• Click its pen button in the pen labels area.

• Click its actual pen data plotted on the graph.

When you select a pen, the active pen scale and active time scale change according tohow that pen is configured.

Once the pen labels area is created on the trend control window, you may access thePen Properties dialog by moving the cursor over one of the pens in the pen labels area,right clicking, and selecting Pen Properties from the popup menu.

Creating a New Trend Control Graph

Follow these steps to create a Windows trend control.

1. From the Windows Controls toolbar, select the Trend Control.

A new graph appears.



TAC 656

The graph is empty, and it does not display the pen labels area because you havenot yet created a pen. However, the active pen unit scale and the time scale appear

at the left side and bottom of the graph, respectively.

2. Right click, and select Add New Pen from the popup menu. The Pen Properties dialog appears.




3. Click the browse button in the Pen Data Object field, and search for an object whosedata you wish to poll, track, and plot.

A data source is a real-time source (object attribute). The name of the pen dataobject becomes the pen label (i.e., the name of the pen). Pen labels appear in thepen labels area of the trend control window.

4. In the Scale area, enter maximum and minimum values for the data that is plotted onthe graph.

5. In the Style area, customize the appearance of the trend line and data points. Style

characteristics include pen color, what kind of line connects the data points, as wellas the style of the data points themselves.

Check the Hide this pen checkbox when you don’t want this pen to appear on thegraph. The pen continues to record data from its source data object, but does not plotdata on the graph. A gray screen covers the pen itself in the pen labels area. Forexample, the pen on the left is hidden:

6. Click OK.

7. Right click the trend control, and select Properties from the popup menu.

8. Select the Plot tab and specify properties of the graph.

Margin Select the margin’s background color and size. From theBackground color dropdown menu, select a color from the colorpalette. The default color is blue.

Plot Select the graph’s background color as well as whether to show orhide the grid. From the Background Color dropdown menu, selecta color from the color palette. The default color is gray.

Check the Grid Marks checkbox if you want to show the grid.Remove the check if you want to hide the grid. The Grid Marks boxis checked by default.

Label In the label field, as an option, you may enter a name for the trendcontrol window. This label appears above the graph. Click the Font button to select a typeface and font for the trend control label, aswell as for the text throughout the entire trend control.

Check the Show checkbox when you want to show the trendcontrol label name. Remove the check in the Show checkbox whenyou want to hide the label name.



TAC 658

Time Scale Check the Show Time Scale checkbox when you want to show thetime scale on the trend control. Remove the check when you wantto hide the time scale. The Show Time Scale box is checked bydefault. Check the Vertical Text checkbox when you want todisplay time scale text vertically, at a right angle. This box is notchecked, and text is displayed horizontally, by default. When youcheck this box, text is displayed vertically.

9. Click the Pen Labels tab to show, hide, and position pen labels, as well as pen labelunits, on the trend control.

Show Pen Labels Displays the pen labels on the trend control. Remove thischeck to hide all pen labels.

Show at the Bottom Displays the pen labels along the bottom of the trendcontrol, beneath the time scale. By default, this button isselected, and pen labels are displayed at the bottom.

Show on the Right Displays the pen labels along the right side of the trendcontrol.

Show Pen Units Displays the pen units’ scale.

Vertical Text Displays text in the pen scale vertically.

10. Select the Pens tab to add or delete a pen, as well as access the Pen Properties

dialog, where you may view and/or modify a pen’s properties.






• Select User Defined, and enter the appropriate text if you want to display custom

text in the tooltip.14. Click OK.



Run Mode Menu Features of Trend Graphs

The run mode popup menus for the graph and the pen labels enable you to controlcertain display characteristics of the plotted data.




Right click the graph to display the following options:

Pause Select Pause to stop the plotting of new sample data on thegraph.

Restart Select Restart after a pause, to resume the plotting of data onthe graph.

Auto Scroll Select Auto Scroll when you want the graph to scroll to the leftautomatically whenever more data samples are plotted on thegraph. This allows you to see the latest plotted data.

Fit Time Select Fit Time to show all the plotted data on the graph at once,beginning with the time of the first plot in the leftmost part of thegraph, and ending with the latest plot on the rightmost part of thegraph.

Time Zoom In Select Time Zoom In to zoom into the graph area (time axis) by50 percent of its current size.

Time Zoom Out Select Time Zoom Out to zoom out of the graph area (time axis)by 50 percent of its current size.

Right click a pen to display the following options:

Object Properties Select Object Properties to launch the object editor for the

source data object whose data is being polled and plotted.Hide Select Hide to hide the selected pen.

Fit Time Select Fit Time to show all the plotted data on the graph atonce, beginning with the time of the first plot in the leftmost partof the graph, and ending with the latest plot on the rightmostpart of the graph.

Design Mode Menu Features of Trend Graphs

Right click the graph to display the following options:

Properties Select Properties to launch the Graph Properties dialog for thetrend control.

Add New Pen Select Add New Pen to launch the Pen Properties dialog, whichallows you to add a new pen to the trend control window. See alsoAdding a New Pen .

Auto Scroll Select Auto Scroll when you want the graph to scroll to the leftautomatically whenever more data samples are plotted on thegraph. This allows you to see the latest plotted data.

Fit Time Select Fit Time to show all the plotted data on the graph at once,beginning with the time of the first plot in the leftmost part of thegraph, and ending with the latest plot on the rightmost part of thegraph.



TAC 660

Right click a pen, and select Pen Properties to launch the Pen Properties dialogcontaining all the settings for that particular pen.

Creating an LED Number Control

A light-emitting diode (LED) number control allows you to simulate a digital LED numberdisplay, based on numeric values it receives from a source data object that is assigned tothe number control. The number control can be a multiple-digit integer, up to 10 digits.You may also display the digits in certain colors to indicate various states of an alarm,when your data object has triggers an alarm.

To create a new LED number control:

1. Click the LED number control icon on the Windows Controls toolbar.

A new, empty LED number control appears. By default, it has four digit places.

2. Right click the control, and select Object Properties from the popup menu.

The LED Number Control Object Properties dialog appears.

3. In the General tab, click the browse button in the Object field, search for, and selectan object whose numeric value you want to display.

4. Enter the number of digits to display. You may select a minimum of one digit and amaximum of 10 digits.

5. Check the User Entry checkbox if you want users to be able to manually change theinteger value of the number control’s source object.




Users can click the control to display a calculator where they can specify a newvalue. Clear the checkbox to make the control read only.

6. Select the Alarms tab, and select a color for each state of an alarm.

When your data object triggers an alarm, the integer in the LED number controlappears in the specified color, depending on its current state.







Click OK.



Creating a Door Control

The Windows door control provides you with a graphic display of a Door object. Itillustrates the switch states of the door by using configurable animation. Bitmap imagesillustrate the states of the door:

• Alarm

• Enabled/disabled

• Locked/unlocked

• Scheduled lock/unlock

• Trouble

• Timed unlock• Enabled/disabled keypad/reader access

To make the control operational, you have the option of:

• Using the default animation bitmap set.

• Choosing from several supplied bitmap sets.

• Using your own bitmap set.

Follow these steps to create a door control:

1. From the Window Controls toolbar, select the door control.




TAC 662

2. Right click the door control and select Object Properties to display the DoorControl dialog.

3. In the General tab, select the properties you require.

Object Enter or click the browse button to specify the path to adoor object to attach to this control.

Style Select a style of door graphics that you want to use fromthe drop down menu.

User Entry If selected, users can right click the door control todisplay a popup menu with options for controlling to door.

SwitchAnimation

Check this box if you want the selected set of bitmaps inthe Style combo box to reflect the state of the door switchor to represent the locked/unlocked state of the door. Ifthe attached door is not configured for a switch (switch

channel is zero), the switch animation checkbox isunchecked and disabled and the locked/unlocked state ofthe door is represented.

FlatAppearance

If not checked, the door control will have a raised edge(appearing like a button.)

4. Select the Advanced Alarms Images tab to display a specific image for a forcedentry, door ajar, or custom alarm.

Browsing to or entering an image file (in their respective edit boxes) and thenspecifying the alarm link (1 through 8) from the door editor’s alarm page. If the alarmenrollment associated with the alarm link is in the alarm stage, the specified bitmap isdisplayed. The custom alarm can be attached to any alarm link.

Note: If advanced alarms are not required, make sure the Alarm Links values areset to zero.

5. Select the Custom Images tab if you wish to use your own door style images.

6. Browse to or enter the names of your custom set of bitmaps in the Open, Closed,Alarm, and Trouble edit boxes. Files must be entered for both the Open and Closedimages; the Alarm and Trouble images are optional. If the Alarm and Trouble imagesare blank, the door control checks the door switch state and implements theappropriate Open or Closed image.

Note: If you are not going to use custom images, ensure that the Open, Closed,Alarm, and Trouble edit boxes are blank.




7. Select the Personnel Data tab, to select up to four attributes to be displayed in thedetails dialog.

You can select any personnel attributes listed to be displayed under the personnelpicture of the last person to enter or to exit through the attached door. If the checkbox next to the attribute is checked, it is displayed in the dialog.

8. To execute Plain English (PE) commands in addition the button action you defined instep 5, select the Plain English Script tab, and enter the PE script. Click the Checkbutton to verify that the script has no syntax or other errors.








12. Click OK.





TAC 664

Controlling a Door

You can use a door control to unlock the door assigned to the control, view door detailsand events, and perform other functions to control that door object.

You cannot use a door control to lock down a door or to clear the Lockdown state from adoor. Instead, use the area control for the Area object to which the door is assigned.

Note: The User Entry checkbox must be checked in the Door Control dialog for thespecific door control before you can control the door as described in the followingtable. For more information see, Creating a Door Control , earlier in this chapter.


Prevent access at the card reader orkeypad associated with the door

Right click the door control, and select DisableKeypad/Reader Access from the popup menu.

Unlock the door and allow it to remainunlocked

Right click the door control, and selectPermanent Unlock from the popup menu.

If the door is in the Lockdown state, the messageis ignored and door does not unlock.

Unlock the door for a specified amountof time, and then relock it

Right click the door control, select Timed Unlock ,and then select the number of minutes to allowthe door to remain unlocked.

To enter a specific time, select Custom, enter thenumber of minutes (up to 105), and click OK.

If the door is in the Lockdown state, the messageis ignored and the door does not unlock.

Relock an unlocked door Right click the door control, select Timed Unlock ,and then select Relock .

Obtain information about the cardholder of the access card used (or PINentered) most recently at this door(including the photo of the card holder,if available)

Right click the door control, and select DoorDetails.

View the list of access events thatoccurred at this door

Right click the door control, and select DoorEvents.

View or change values for doorattributes

Right click the door control, and select Edit Door to open the Door editor.

View a video layout, if one is attachedto the door object associated with thecontrol

Right click the door control, and select VideoLayout.

Run the Plain English script that isentered in the Door control dialog forthis control

Right click the door control, and select RunScript.




Creating an Area Control

The area control provides a graphic display of a CyberStation Area object. The controlillustrates whether the area is in the Lockdown state or in the Normal state, using eitherbitmap images or colors. You can create an Area control and attach a CyberStation Areaobject to the control, or you can drag an Area object from Continuum Explorer onto thePinpoint canvas to create an area control for the selected area.

In run mode, you can click the area control to initiate the Lockdown state at thecontrollers that manage doors for the area. You can also right click the area control and

select Options from the popup menu to lock down or clear the Lockdown state for thearea and at individual doors assigned to the area.

Use the following procedure to create an area control and attach the control to an Areaobject.

1. Either click the area icon on the Windows controls toolbar, or select Area from theWindows controls dropdown menu.

A new area control appears on the canvas.

2. Click the new area control.

The Area Control dialog appears.

3. In the General tab, configure the control properties, as follows.

Object Enter or click the browse button to specify a path to anArea object.

User Entry Check this checkbox to interact with the area controlwhen in run mode. While in run mode, you can click thearea control to lock down the area. You can also rightclick the area control to access a context menu withoptions or controlling the area and doors assigned to

the area.

Flat Appearance Do not check this checkbox if you want the area controlto have a raised edge (appearing like a button).

Warn before changingLockdown

Check this checkbox to be prompted with aconfirmation message when you lock down the areausing this area control.

4. In the Images tab, specify how you want to represent the area in its Lockdown andNormal states:

• Select From Library to use the predefined bitmap images.



TAC 666

• Select Custom Images, and use the browse buttons to select the files thatcontain the bitmap images you want to use for the Lockdown and Normal states.

• Select Color, and select the colors you want to represent the Lockdown andNormal states for this area. When you select the Color option, the select colorfills the rectangle that represents the area in the specified state.

5. In the Label tab, select the Show Area Name checkbox if you want to display thearea name on the control. Select the font and color you want to use to use for the textin the Lockdown and Normal states.

6.

In the Plain English (PE) Script tab, you can execute any command-line command.PE Scripts cannot have local variable declarations or labels. Note that PE scripts areexecuted before the selected active button performs its actions (that is, open panel,open object, and so on).

Create or insert your PE script, and click the Check button to check the script forerrors.




9. Select the ToolTips checkbox if you want to display a tooltip when the curser hovers

over the text box, and then specify the tooltip content:



10. Click OK.



Controlling Doors with an Area Control

After you create an area control for an area, you can use the area control to monitor andcontrol individual doors assigned to the area. (You assign doors to an area in the Dooreditor.)

When an area is locked down, only personnel who are assigned executive privilegeaccess and have access rights to the area can enter or exit through doors assigned to it.Requests to exit and lock and unlock messages issued manually, in CyberStation, byschedules, or through Plain English programs are ignored in the Lockdown state.

Note: The User Entry checkbox must be checked in the Area Control dialog for thespecific area control before you can control associated doors as described in thefollowing table.





Lock down an individual door Right click the area control, select Doors, and thenselect the name of the door you want to lock down.Select Lockdown. If prompted to confirm the changein state, click Yes.

Clear the Lockdown statefrom an individual door

Right click the area control, select Doors, and thenselect the name of the door you want to change.

The Clear Lockdown option is disabled if either or

both of the area to which the door provides accessare still in the Lockdown state. You must cleat theLockdown state from the area, which should alsoclear the Lockdown state from the associated doors.

Unlock the door and thenrelock it

Right click the area control, select Doors, and thenselect the name of the door. Select MomentaryUnlock .

The door remains unlocked for the number ofseconds entered for Door Strike in the Channel tabof the Door editor. The door is then relocked.

If the door is in the Lockdown state, the message is

ignored and door does not unlock.Unlock the door and allow itto remain unlocked

Right click the area control, select Doors, and thenselect the name of the door. Select PermanentUnlock .

If the door if in the Lockdown state, the message isignored and door does not unlock.

Obtain information about thecard holder of the accesscard (or PIM) entered, usedmost recently at this door(including the photo of thecard holder, if available)

Right click the area control, select Doors, and thenselect the name of the door. Select Door Details.

View the list of accessevents that occurred at thisdoor

Right click the area control, select Doors, and thenselect the name of the door. Select Door Events.

View or change values fordoor attributes

Right click the area control, select Doors, and thenselect the name of the door. Select Edit Door toopen the Door editor.



TAC 668

Using an Area Control to Lock Down an Area or Door

After you create an area control for an area, you can use the control to monitor andchange the lockdown status of the area and of individual doors assigned to the area.

When an area is locked down, only personnel who are assigned executive privilegeaccess and have access rights to the area can enter or exit through doors assigned to it.Requests to exist and lock and unlock messages issued manually, in CyberStation, byschedules, or through Plain English programs are ignored in the Lockdown state.

You select executive privilege access and assign area access rights in the Personnelobject for each object that you want to have this access.

Note: The User Entry checkbox must be checked in the Area Control dialog for thespecific area control before you can change the Lockdown state as described inthe following table. For more information, see Creating an Area Control , earlier inthis chapter.


Lock down an areathat is currently in theNormal state

Click the area control. If prompted to confirm the change instate, click Yes.

You can also lock down an area by right clicking to areacontrol, and selecting Lockdown from the popup menu.

Clear the Lockdownstate from an area

Right click the area control, and select Clear Lockdown from the dropdown menu.

Lock down anindividual door

Right click the area control, select Doors, and then selectthe name of the door you want to lock down. SelectLockdown.

Clear the Lockdownstate from anindividual door

Right click the area control, select Doors, and then selectthe name of the door you want to change. Select ClearLockdown.

The Clear Lockdown options is disabled if either or both ofthe areas to which the door provides access are still in theLockdown state. You must clear the Lockdown state from

the area, which should also clear the Lockdown state fromthe associated doors.




Appendix AUsing the Personnel Editor



TAC 672

The following appendix describes how to complete the tabs of the Personnel objecteditor. The Personnel editor is a dialog similar to other CyberStation dialogs. ThePersonnel Manager, described in Chapter 19, is a powerful and easy-to-use tool forentering, viewing, and managing personnel data. If you prefer to use the Personneleditor, you can edit the workstation configuration to display this editor.

1. In Continuum Explorer, right click your workstation folder, and click Open.

2. Select the Preferences tab of the Device editor.

3. Scroll down to the preference setting, Use Personnel Manager, and select False.

4. Click OK.In Continuum Explorer, you can double click a Personnel object to edit the object inthe Personnel editor.

General Tab – Personnel Editor

In the General tab, you enter access-card and access-code information so the personcan use an access card and/or access code to gain entrance to the areas on the AreaList tab. You also use the settings in the General tab if an access card is lost.




From the General tab, you also create or modify a photo ID badge for this person. Seethe Make/Edit Badge description in the table below.

Note: The Andover Continuum system supports custom ABA cards. Each custom ABAformat must be defined as a special Infinity String. The custom format of this stringaffects the way you enter card numbers and site does in this tab.

Name Enter from left to right, a person’s first name, middle initial or middle name(if applicable), and last name.

State Select Enabled or Disabled.

ActivationDate

Enter the date and time a person can begin using an access card.

ExpirationDate

Enter an expiration date and time for this person's access card. ExpirationDate automatically disables a personnel object when the specifieddate/time is reached.

Card Type Select this person’s card type from the dropdown menu.

CardNumber

Enter the number that is encoded on this person's card.

Site Code Enter the site code that is encoded on this person's card.

PIN Enter this person’s Personal Identification Number (PIN).Visitor Select if this person is a visitor rather than a permanent employee.

ADA Select if the person requires assistance due to a disability.

Selecting this attribute allows a door to remain open for a length of timespecified in the ADA configuration choices for each door connected to acontroller or IOU module that supports this feature. Use the Door editor toconfigure door settings for ADA access.

Signature Displays this person’s signature in a read-only box.

DefaultClearanceLevel

Enter the clearance level that applies to all areas you assign to thisperson. You can enter a value between 0 and 255, with 1 providing thegreatest access and 255 providing the least access. Enter 0 if you do not

want to assign a default clearance level to this person.

You can override the Default Clearance Level for an individual area byentering a different clearance level for the area when you assign the areato this person. You assign areas to a personnel object and specify theirclearance levels in the Area List tab.

ExecutivePrivilege

Check the Executive Privilege checkbox if you want this person to beable to access any area assigned to him/her when the area, or a door tothe area, is in the Lockdown state.



TAC 674

Mark CardAs Lost

Click this button in the editor if a person has lost an access card.

CyberStation creates another personnel record for this individual with a.LOST file extension. If the card is used after being marked as lost, it willnot open a door and it logs into the Event Viewer as an Invalid Attempt.

IssueTemporaryCard/ Restore

PermanentCard

Click this button to issue a card to temporarily replace a lost card.

The button text changes to Restore Permanent Card. CyberStationsaves the personnel object for the original card. You can later click theRestore Permanent Card button to restore the information if the original

card is found.

Make/Edit

Badge

Click this button to create or modify a photo ID badge for this person.

When you click this button, the Make/Edit Badge dialog appears. Fromthis dialog, you can create/edit a badge layout, select a photo-imagesource, and, if necessary, a signature-image and fingerprint-imagesource. See “Making/Editing a Badge” in Chapter 19 for more information.

To create or modify a badge layout, your site must have purchased theseparately sold application called the EPIDesigner . This option isenabled/licensed via your CyberStation key, if your site has purchasedthis option.

Compatible with old Guard Draw Files: For Version 1.8 and higher,EPIDesigner is used for layout instead of Guard Draw. However, you caneasily open and save you pre-Version 1.8 Guard Draw layouts (.gdr files)as EPIDesigner layouts (.dgn files).

Area List Tab – Personnel Editor

In the Area List tab, you specify the areas to which this person is allowed access. Thelist of areas displays the following information:

• The name of each area

• The name of the schedule that controls each area

• The clearance level, if any, assigned to each area for this person, and whether

validation for access to this area occurs at the access server or at the controllermanaging doors to the area

• The status of the area, either enabled or disabled, indicating whether or not the areais currently accessible



TAC 676

You can complete the following tasks in the Area List tab:

• Assign one or more areas to a person, and attach a schedule to an area.

• Enter a clearance level for a specific area assigned to one person, overriding thevalue for Default Clearance Level entered in the General tab.

• Temporarily disable a person’s access to an area.

• Permanently remove a person’s access to an area.

Assigning an Area to a Personnel Object

Perform the following steps to add one area in CyberStation.

1. Click the Add Area button.

2. Click the browse button in the Area field to search for and select the area that youwish to add for this person.

3. Click the browse button in the Area Schedule field to search for and select theschedule for that area.

4. Select the State from the dropdown menu (Enabled or Disabled.

5. From the Workstation Validation Only dropdown menu, select True to specify thatthis person’s record (and access permission for this area) gets validated only in theworkstations serving as access servers, instead of being validated by the localcontroller’s database.

This saves data storage space in the controller. Use this option when controllermemory is filling up with records that do not utilize these areas very often.

6. Enter a value for Clearance Level if you want to override the person’s defaultclearance level specified in the General tab. Leave the value at 0 if you do not wantto override the default clearance level for this person.

You can override the default clearance level if you want a person to have accessprivileges in a specific area that are more or less restricted than the access providedby the person’s default clearance level.

7. Click OK.

8. In the Area List tab, click the Apply button to save, or click the OK button to saveand exit.

Assigning Multiple Areas to a Personnel ObjectPerform the following steps to add multiple areas in CyberStation.

1. Click the Add Areas button.

The Area dialog appears, listing the names and locations of areas that you canassign to this person.

2. Click and highlight the first area, hold down the Ctrl key, then click and highlight thenext area you want to add. While still holding the Ctrl key, click additional areas you

want to add for this person. (You can hold down the Shift key instead of the Ctrl keyto select the next area and all areas in your first and last selection.)




3. Click OK.

You are then asked: Do you want to attach a schedule to the areas?

4. Click Yes to search for, select, and attach a schedule, via the Browse dialog.

Click No if you do not want to attach a schedule.

5. Click OK.

If you want to change the clearance level of any of the areas you added, you can editthe area properties as described below.

Changing the Clearance Level of an Assigned AreaThe Clearance Level for an area enables you to specify different access privileges todifferent areas assigned to the same person.

Perform the following steps to change the clearance level of an assigned area.

1. Select the area you want to change, right click, and select Area Properties.

2. Enter a new value for Clearance Level.

If you want the clearance level for an area to be the same as the value entered forDefault Clearance Level in the General tab, enter 0 for Clearance Level for thearea.

3. Click OK.

Disabling Access to an Assigned Area

When you disable access to the area, any schedule attached to the area and other areaproperties continue to be stored in the Personnel object and are restored when you laterenable the area. Other personnel with access to the same area are not affected.

Perform the following steps to temporarily disable a person’s access to an area.

1. Select the area you want to change, right click, and select Area Properties.

2. Select Disabled for State, and click OK.

3. Click OK.

Removing Access to an Assigned Area

When you remove an assigned area, the person’s card or key code no longer allowsthem to access the area. Any schedule or clearance level saved with the area is alsoremoved for this person. Other personnel with access to this area are not affected.

You many want to remove an area if an employee has changes jobs within your companyand no longer needs access to the area in their new assignment.

Perform the following steps to remove an area from the areas list.

1. Select one or more areas to remove from a person’s area list.

To select multiple areas, click and highlight the first area, hold down the Ctrl key,then click and highlight the next area you want to add. While still holding the Ctrl key,click additional areas. (You can hold down the Shift key instead of the Ctrl key toselect the next area and all areas in the list between your first and last selections.)



TAC 678

2. Click the Remove Areas button.

3. Click OK.

Privileges Tab – Personnel Editor

In the Privileges tab, you enter and view information that defines a person’s accessprivileges.

Zone Point Browse for a Numeric point.CustomControl

Fields

Used only if Andover Continuum created custom controls as part ofthe installation.

Allow Anti-PassBack

Check this checkbox to allow this person to access an arearegardless of an Anti-Pass violation.

If such a violation occurs, it is recorded in the event log, but theperson is granted access to the area.

DisableCard if notused in

Days

Enter the number of days of inactivity after which the access card isdisabled. The card remains in the database and is restored if youlater enable the card in the General tab.

Employee Info Tab – Personnel Editor

In the Employee Information tab, you enter employment-related information about aperson. Everything on this page is optional and provided for convenient record keeping.

Department Enter the name of the department for which this person works.

Dept Number Enter the number of the department for which this personworks.

This number is limited to the range 0-65535. This number isstored in every door object’s department point every time this

person gains access through a door. In this way, the controlsystem tracks which departments use which doors.

Employee Number Enter this person's employee number.

Supervisor Enter the name of this person's supervisor.

Office Phone Enter this person's office phone number.

Office Location Enter the location of this person's office.

Title Enter this person's job title.

Parking Sticker Enter the number of this person's parking sticker.

Vehicle Info Enter vehicle information, such as year and make, for this




person.

License Enter this person's license number

Social Security # Enter this person's Social Security number.

Start Date Enter the date this person started work.

Info 1 – Info 6 Enter values as needed for these user-defined attributes. YourCyberStation administrator may have customized the attributenames for your company.

Personal Info Tab – Personnel Editor

The Personal Info tab lets you enter optional personal information such as homeaddress, physical characteristics, and an emergency contact. Everything on this tab isoptional.

Address Enter this person's home street address.

City Enter the city in which this person lives.

State Enter the state in which this person lives.

ZIP Enter this person's ZIP code.

Country Enter the country in which this person lives.Emergency Enter the name of this person's emergency contact.

Phone Enter the phone number of this person's emergency contact.

Home Phone Enter this person's home phone number.

Date of Birth Enter this person's date of birth.

Hair Color Enter this person's hair color.

Eye Color Enter this person's eye color.

Height Enter this person's height.

Weight Enter this person's weight.

Sex Enter this person's sex.

Select either Male or Female from the dropdown menu.

Blood Type Enter this person's blood type.



TAC 680

Current Status Tab – Personnel Editor

In the Current Status tab, you view a person’s current status.

Current Area Displays the last area entered by this person. If needed, you canalso override the current area with a different area for thisperson.

CyberStation determines the current area from the last doorentered information, if available. In systems sets up to preventor discourage tailgating, you may occasionally need to overridethe displayed current area if the person accessed a differentarea without using their card or entering their PIN and is nowprevented from leaving an area.

To override the current area, click the browse button. In theBrowse dialog, locate the correct area for the person, and clickthe Select button. CyberStation distributes the new current areafor this person to the appropriate controllers.

Current SecurityZone

Not implemented in this release

Last DoorEntered

Displays the object name of the last door a person went throughusing an access card and/or access code.

Current Status If doors in your facility are set up to detect personnel requestingaccess under duress (that is, when compelled by anunauthorized person or in other emergency circumstances), andif this situation occurs, Duress is displayed in this field for thePersonnel object associated with the access card used (or PINentered). You select duress settings in the Entry Options taband Exit Option tab of the Door Editor.

Time of Entry Displays the time and date a person entered the area displayed

for Current Area.




Access Events Tab – Personnel Editor

In the Access Events tab, you view access activities for this person. This tab displays allthe events in the current access log that pertain to this person. The events are loadedonto this tab the first time you click the Access Events tab. You can then click theRefresh button to see additional events that occurred since you displayed the tab.

Event Class Displays the type of class of access event that has occurred.

Time Stamp Displays the date and time at which the access event occurred.Door Displays the name and path of the Door with which the person

caused the event.

Area Displays the area associated with this event.

Templates Tab – Personnel Editor

The Templates tab displays a list of personnel template objects that appear in thePersonnel Templates folder of Continuum Explorer and indicates whether one of thesetemplates is attached to the current Personnel object. A template is an object withpredefined attributes. You use a template to create new objects with the same attributesettings. CyberStation templates let you quickly, easily, and consistently create new

objects of the same class. Templates are a powerful tool for ongoing maintenance of yoursystem.

Use the Templates tab to associate the Personnel object with a selected template.Typically, you do this to assign areas configured in the template to the personnel record.Any values for attributes whose data source in the template is Inherited from Template will also be added to the Personnel object when you associate the template with theobject. In the Templates tab, you can also clear values linked to a template from aPersonnel object.

Any areas that you added to the Personnel object using the buttons in the Area List tabremain assigned to the object when you select a different template. If you enteredindividual clearance levels for any of these areas, the clearance levels are not overwrittenby the new areas list.

Adding a Personnel Template

1. Click the radio button next to the personnel template that has the areas you want toassign to the current Personnel object.

2. Click OK.

Removing a Personnel Template

1. Right click the list of templates, and select Clear Selection from the popup menu.

2. Click OK.



TAC 682

Custom Attributes Tab – Personnel Editor

The Custom Attributes tab shows any custom attributes that have been configured foryour system. Custom Attributes are created and deleted in the Custom Attributes editor.

Security Tab – Personnel Editor

The access permissions configured in a security level allow you to customize (deny)access to individual CyberStation objects. Security levels are actual CyberStation objects(SecurityLevel objects) configured via the SecurityLevel editor.

A security level can deny access to a CyberStation object editor on a page-by-page basisusing object-level security. Object-level security is a way to deny user groups the abilityto create, delete, or change individual CyberStation objects.

Every object editor in CyberStation has a Security Level tab that displays a list of allexisting security level objects. Selecting a security level object here attaches that securitylevel to the object being edited.

Note: Object-level security that is placed on an individual CyberStation object in theSecurityLevel editor (or from this Security Level tab) cannot grant accesspermission to any user group that has already been denied access in the defaultuser security group settings, established in the main CyberStation Security editor.That is, you can override the default Security editor settings to deny access

(change a default key to a security-level lock) but you cannot override the defaultsettings to grant access (change a default lock to a security-level key).

Attaching a SecurityLevel Object

1. Determine which security level you wish to assign to the object that you areconfiguring in this editor. The names of security levels are listed in the Name column.Security descriptions are listed in the corresponding Descriptions column.

2. In the Name column, click and place a black dot in the radio button next to the nameof the security level that you want to attach.

Detaching a SecurityLevel Object

1. Determine which security level you wish to remove from the object that you areconfiguring in this editor.

2. In the Name column, click and remove the black dot in the radio button next to thename of the security level that you want to remove.

OR

1. In the security level list, click and highlight the security level that you want to removefrom this object.

2. Right click on the highlighted security level. A popup menu appears.

3. Select Clear Selection from the popup menu.




Distributing Personnel Objects to Controllers

There are two methods for distributing Personnel objects to controllers:

• Sending Selected Personnel Objects to All Controllers.

Select and right click the Personnel objects to be sent to the controllers. Click SendTo in the dropdown menu and select Controllers.

• Sending All Personnel Objects to a Specific Controller

Select and right click the controller to which the Personnel objects will be distributed.On the dropdown menu select Distribute Personnel.



TAC 684




Appendix B EpiBui lder I nstal lation



TAC 686

In order to make or modify a badge layout, your site must have already purchased theseparately sold badging software product, EPIBuilder , made and distributed byImageWare Systems. In CyberStation Version 1.8 and higher, EPIBuilder replacesEPISuite software, which was used in previous versions. The EPIBuilder option isenabled and activated via your CyberStation key, if your site has purchased this option.

In CyberStation 1.8 and higher, the EPIDesigner application replaces Guard Draw as thebadge layout tool. (Guard Draw is used in previous versions of CyberStation.) However,your existing Guard Draw files are compatible with and can be used in EPIDesigner.

Installing EPIBuilderEPIBuilder, with it’s EPIDesigner photo badge layout application, is a separate productthat your site has purchased as a special option. EPIBuilder is included on yourCyberStation product key that you insert into your computer. If your site has notpurchased EPIBuilder, TAC activates the option inside the CyberStation key at thefactory. Therefore, not much is required, other than inserting your key.

1. Insert the CyberStation product key into the USB port on your computer, as youwould normally.

Note: If your site has purchased this option, then EPIBuilder is already activatedinside your CyberStation key. Proceed to Step 2.

However, if your site wants to add EPIBuilder on computers with existing

CyberStation installations, then your administrator must contact TAC to obtainan activation code. When contacting TAC, provide the serial number of yourCyberStation key. To assist in obtaining this serial number and activating thekey, run the file, ACCKeyWriter.exe, located in:


Enter the activation code into the Keycode field in the ACCKeyWriter, and click

the Update button. If successful, you receive this message:

Your key has been programmed.

This activation must be performed on every workstation.

2. Continue installing CyberStation as you would normally.

For more information on installing CyberStation, please see the Andover Continuum CyberStation Installation Guide , 30-3001-720.




Appendix C Personnel Import Uti l i ty Tables

and Sample XSLT F ile



TAC 688

This appendix presents the following tables:

• Active Directory attributes

• Continuum Personnel object attributes

• Card type formats and allowed values for site code and card number

This appendix also includes a sample XSLT file and general information about ActiveDirectory and the Lightweight Directory Access Protocol (LDAP).

Active Directory Attributes TableThis table lists supported data-source personnel attributes that reside on the ActiveDirectory domain server. This table lists the attribute name, the user-interface attributename, and the tab on which it appears.

Note: When processing Active Directory "Multi-value" attributes, the Personnel ImportUtility will treat these attributes differently than all of the other, Single-valueattributes. When the Personnel Import Utility retrieves a Multi-value ActiveDirectory attribute, it will create a comma-delimited list of the items before mappingthe values to a CyberStation attribute.

You can manipulate the comma-delimited list in the XSLT file, if desired. This behaviorconcerns the following Active Directory attributes: directReports, memberOf,

otherFacsimileTelephoneNumber, otherHomePhone, otherIpPhone, otherMailbox,otherMobile, otherPager, otherTelephone, ou, and url.

Attribute NameActive DirectoryUser Interface Tab

Active Directory UserInterface Attribute Name

assistant

businessCategory

c Address Country/region

carLicense

cn

co Address Country/region

comment

company Organization Company

countryCode Address Country/region

createTimeStamp

department Organization Department

description General Display Name

directReports Organization Direct Reports






displayName General Display Name

distinguishedName

division

employeeID

employeeNumberemployeeType

extensionAttribute1

extensionAttribute2

extensionAttribute3

extensionAttribute4

extensionAttribute5

extensionAttribute6

extensionAttribute7extensionAttribute8

extensionAttribute9

extensionAttribute10





extensionAttribute15extensionAttribute16

facsimileTelephoneNumber

Telephones Fax

givenName General First Name

homePhone Telephones Home

homePostalAddress

houseIdentifier



TAC 690



info Telephones Notes

initial General Initials

ipPhone Telephones IP phone

l (Lower-case L) Address City

mail General E-mailmanager Organization Manager

memberOf Member Of Member Of

middleName

mobile Telephones Mobile

modifyTimeStamp

name

otherFacsimileTelephoneNumber

Telephones Fax Number (Others)

otherHomePhone Telephones Home Phone (Others)

otherIpPhone Telephones IP Phone Number (Others)

otherMailbox

otherMobile Telephones Mobile Number (Others)

otherPager Telephones Pager Number (Others)

otherTelephone General Phone Number (Others)

ou

pager Telephones Pager

personalTitle

physicalDeliveryOfficeName

General Office

postalAddress

postalCode Address Zip/Postal Code

postOfficeBox Address P.O. Box

preferredLanguage






primaryGroupID Member Of Primary Group

primaryInternationalISDNNumber

primaryTelexNumber

roomNumber

sAMAccountName Account User Logon Name (pre-Windows 2000)

sAMAccountType

sn General Last Name

st Address State/Province

street

streetAddress Address Street

telephoneNumber General Telephone Number

title Organization Title

url General Web Page Address(Others)

userPrincipalName Account User Logon Name

userWorkstations Account Logon On To/LogonWorkstations

whenChanged Object Modified

whenCreated Object Created

wWWHomePage General Web Page

Continuum Personnel Attributes Table

This table lists all CyberStation Personnel object attributes that can be modified in thePersonnel Import Utility. This table lists the user-interface display name, the tab on whichit appears in the Personnel editor, the data type, and any possible value restrictions.These attributes appear in the Details tab of the Personnel Manager (if they are select tobe displayed in the Personnel Manager profiles).



TAC 692

ContinuumPersonnelAttribute Name

Personnel EditorTab and Field

ActiveDirectoryData Type

Rules and Boundariesfor Values

ADA General / ADA String orBoolean

Value of "True" or "False"

Address Personal Info / Address

String String value having alength 1-48

Alias Properties / Alias String String value having alength 1-16, and followsnormal Continuum namingrules

AllowEntEntEgr Privileges / AllowEntry Upon Area Anti-Passback Violation

String orBoolean


AreaLinks AreaList / N/A String String value having alength 1-255 (supportedonly from .xsl file)

Blood Personal Info / BloodType


Card Number Genera / CardNumber

String orInteger

Range of values dependson Card Type -- see tablebelow.

Card Type General / Card Type String String value, namingsupported ContinuumCard Type -- see tablebelow.

City Personal Info / City String String value having alength 1-16

Country Personal Info /

Country

String String value having a

length 1-12DateOfBirth Personal Info / Date

of BirthGeneralizedTime

Time Value

DefaultClearanceLevel

General / DefaultClearance Level

String orInteger

Value 0-255

Department Employee Info / Department


DepartmentCode

Employee Info / Department Number

String orInteger

Value 0-65535








EmergencyContact

Personal Info / Emergency


EmergencyPhone

Personal Info / Phone String String value having alength 1-40

EmpNumber Employee Ingo / Employee Number


ExecutivePrivilege

General / ExecutivePrivilege

String orBoolean


ExpirationDate

General / ExpirationDate

GeneralizedTime

Time Value

EyeColor Personal Info / EyeColor


FirstName General / Name String String value having alength 1-16

HairColor Personal Info / HairColor String String value having alength 1-12

Height Personal Info / Height String String value having alength 1-16

HomePhone Personal Info / HomePhone


Info1 Employee Info / Info 1 String String value having alength 1-40






JobTitle Employee Info / Title String String value having alength 1-40



TAC 694





LastName General / Name String String value having alength 1-32

LicenseNumber

Employee Info / License


Lost Card General / N/A String orBoolean


MiddleName General / Name String String value having alength 1-40

NonABACardNumber

General / CardNumber

String orInteger

Range of values dependson Card Type -- see tablebelow

OfficeLocation Employee Info / Office Location


ParkingSticker

Employee Info / Parking Sticker


PIN General / Pin String orInteger

Value of 1-65535

RefTemplate Templates / N/A String String value having alength 1-255, Continuumdirectory path to PersonnelTemplate

SecurityLevel Security Level / N/A String String value having alength 1-128, Continuumdirectory path to SecurityLevel object

Sex Personal Info / Sex String Value of "Male" or

"Female"

SiteCode General / Site Code String orInteger

Range of values dependson Card Type -- see tablebelow

SocSecNo Employee Info / Social Security No


StartDate Employee Info / StartDate

GeneralizedTime

Time Value








State General / State N/A Value determined by stateof User account in ActiveDirectory

StateOfResidence

Personal Info / State String String value having alength 1-2

Supervisor Employee Info / Supervisor


Vehicleinfo Employee Info / Vehicle Info


Visitor General / Visitor String orBoolean


Weight Personal Info / Weight

String orInteger

Value of 0-999

WorkPhone Employee Info / Office Phone


ZIP Personal Info / ZIP String String value having alength 1-9

Card Type Table

For different card types, this table lists minimum and maximum values allowed for SiteCode and Card Number.

Card Type Site Code Minimum-Maximum

Card Number Minimum-Maximum

ABA2 N/A 1 – 99999999999999999999999

AC4plus432 1 – 2047 1 – 8191

CK34 1 – 4095 1 – 7065535

CustomMagStripe(Custom ABA)

0 – 65535 1 – 99999999999999999999999

CustomWiegand 0 – 6535 1 – 4294967295

G31 (Wiegand31) 1 – 255 1 – 65535

HIDCorp1000_35 1 – 4095 1 – 1048575

Infinity_37 1 – 4095 1 – 524287



TAC 696

Card Type Site Code Minimum-Maximum

Card Number Minimum-Maximum

PINOnly N/A N/A

Wiegand26 1 – 255 1 – 65535

Active Directory

The Personnel Import Utility uses the Microsoft Active Directory service. Active Directory,a service based on the LDAP network protocol, provides a unified view of complexnetworks. It is a tree structure. Each node in the tree has a set of properties.

Active Directory, or Active Directory Services (ADS), resides on a server known as thedomain controller. The domain controller must be Windows Server 2000 or WindowsServer 2003 machine. When ADS is installed, four principle objects are created:

• A user entry that represents the administrator of the network

• A computer entry that represents the domain controller for the Windows 2000/2003Server

• Various default groups for managing security relationships in Windows 2000

• A Domain context container into which the above objects are placed.

Note: You IT or system administrator is responsible for learning about and stabling theMicrosoft Active Directory service on a domain server. You must have thisMicrosoft service in order to use the Personnel Import Utility. For more informationon setting up Active Directory, visit webs sites such as these:

• http://www.serverwatch.com/tutorials/article.php/1474461

• http://www.windowsnetworking.com/articles_tutorials/w2ksvrin.html

• http://activedirectory.com

Three Purposes of Active Directory

Active Directory is usually used for one of the following three purposes:

Note: The Personnel Import Utility only uses the implementation – external directory.

• External Directory: These directories are typically located on servers in theperimeter network or demilitarized zone (DMZ) at the boundary between thecorporate local area network (LAN) and the public Internet. External Directories aretypically used to store information about customers, clients, and business partnerswho access external applications or services. They are also made available tocustomers, clients, and business partners to provide them with selected businessinformation such as catalogs and so on.

• Internal Directory: These directories are used within the corporate network forpublishing information about users and resources within the enterprise. A company’sinternal directory may be accessible to employees when they are outside thecompany network using a secure connection such as a virtual private network (VPN)connections, but it is not accessible to non-employees.




• Application Directory: These directories store “private” directory data that arerelevant only to the application in a local directory, perhaps on the same server asthe application, without requiring any additional configuration to Active Directory. Thepersonalization data, which is only interesting to the portal application and does notneed to be widely replicated, can be stared solely in the directory associated with theapplication. This solution reduces replication traffic on the network between domaincontrollers.

Logical Domain Structure of Active Directory

Unit DescriptionSimple Objects Simple Objects include computers, groups, users, security

policies, and user-defined objects. Objects have attributes,some of which are mandatory and some of which are options.

Organizational Units Organizational Unites (OUs) are a new object type within 2000Server’s Active Directory. They are designed to reduce thenumber of domain in an organization. OUs are often used toreplace domains and sub-domains on systems migrating toActive Directory. Under NT 4.0, different departments in anorganization are often structures as separate domains, but byusing Active Directory, these domains can and should berestructured as OUs, thereby flattening the domain structure.

OUs can be nested, so that a section within a department canhave its own OU within the department OU. Objects withinOUs must be contained within one domain.

Domain By definition, a domain is a logical grouping of users andcomputers. A domain typically resides in a localizedgeographic location, but this is not always the case. In reality,a domain is more than a logical grouping – it is actually asecurity boundary in w Windows 2000 or NT Server.

Tree The hierarchy structure of the domain, organization units, andobjects, is called a tree. The objects within the tree arereferred to as endpoints, while the OUs in the tree structureare nodes. In terms of a physical tree, you can think of the

branches as OUs or containers and leaves as objects – anobject is the natural endpoint of the node within the tree.



TAC 698

Unit Description

Domain Trees A domain tree exists when several domains are linked by trustrelationships and share a common schema, configuration, andglobal catalog.

A domain tree also shares a contiguous name space. Acontiguous name space follows the same naming DNS(domain Name System) hierarchy within the domain tree. Forexample, if the root domain is smithfin.com and domain A anddomain B exist in a domain tree, the contiguous name spacefor the two would be domaina.smithfin.com anddomainb.smithfun.com. If domain A resides insmithfindal.com and domain B resides in smithfin.com, thenthe two would not share a contiguous namespace.

The following is an example of a contiguous namespace.

Forest A forest is one or more trees that do not share a contiguousnamespace, but the trees in the forest do share a commonschema, configuration, and global catalog. All trees in theforest trust each other through Kerberos Transitive Trusts. Inactuality, the forest does not have a distinct name, but thetrees are viewed as a hierarchy of trust relationships. The treeat the top of the hierarchy normally is referred to as the forestroot. For example, corp.com, prod.corp.com, andmgmt.corp.com form a forest with corp.com serving as theforest root.




Unit Description

Site A site is not actually considered a part of the Active Directoryhierarchy, but it is configured in the Active Directory forreplication purposes. A site is defined as a geographicallocation in a network containing Active Directory servers with awell-connected TCP/TP subnet. Well-connected means thatthe network connection is highly reliable and fast to othersubnets in the network. Administrators use the ActiveDirectory to configure replication between sites. User to not

have to be aware of site configuration. As far as the ActiveDirectory is concerned, users only see domains.

Schema The schema is simply a framework of definitions thatestablishes the type of objects available to the ActiveDirectory. These definitions are divided into object classesand the information that described the object is known as itsattributes. There are two types of attributes, those that mustexists and those that may exist. For example, the schemadefines a user object class as having the user’s name as arequired attribute; the user’s physical location or jobdescription is optional. Attributes are used to further helpdistinguish one object from another. They include ObjectName, Object Identifier (OID), Syntax, and Optional

Information.

The schema is stored within the Active Directory database fileNtds.dit. Object definitions are stored as individual objects, sothat Directory can treat schema definitions in the same way ittreat other objects. The default schema is created with thefirst installation on the Active Directory. It contains commonobjects and properties for items such as users, groups,computers, printers, and network devices. It also establishesthe default Active Directory structure that is used internally.

As an extensible component, new object classes may bedynamically added to the current schema and old objectclasses can be modified. It is not possible to modify or

deactivate system classes and attributes.



TAC 700

Active Directory Names

In the Active Directory, every object (such as a user, a group, a computer, a printer, andso forth), has a unique name. There are four kinds of names associated with eachobject, as shown in the following table.

Name Description

Distinguished Name (DN) The DN is unique from all other objects and containsthe full information needed to retrieve the object. The

DN contains the domain where the object resides andthe path to the object. It is made up of these attributes:

DomainComponentName (DC)

OrganizationalUnitName (OU)

CommonName (CN)

By using the DN, the Active directory can begin at thetop of the domain and work its way down to the actualfolder or document.

Relative Distinguished Name(RDN)

The RDN is the part of the DN that defines the actualobject. This part if called an attribute. This is the CN,or common name. Fortunately, all you need to know to

search for objects are common names. You do nothave to know or use the DN, and the DN itself isnormally hidden from the users.

Globally Unique Identifiers(GUID)

The GUID is a 128-bit number unique from all others. Itis assigned to an object when it is created in the ActiveDirectory, and it never changes.

User Principal Name (UPN) Active Directory objects can be identified by the UPN,which is a short, friendly name that looks like an emailaddress, such as [email protected].

The Active Directory provides the DN, RDN, GUID, and UPN for objects to ensureuniqueness, ease of location for LDAP queries, and ease of use. These names are usedto map data source attributes to Continuum personnel record attributes in the PersonnelImport Utility. (For more information, refer to Chapter 19, “Personnel.”)

Global Catalog

The LDAP protocol allows network users to search for a find te objects in the ActiveDirectory they want to use. For this to happen, the Active Directory domain controllersmaintain a global catalog.

The global catalog allows users and applications to find objects in the Active Directory bysearching for one or more particular attributes. The global catalog holds a partial“replica” of the objects and their most common attributes. When you perform a searchoperation to find a user (or other object), the global catalog is checked to find matched for




that request. The global catalog looks for that attribute and returns matches. Data in theglobal catalog are built and maintained through replications among domain controllers.

LDAP Protocol

The Lightweight Directory Access Protocol (LDAP) is a networking protocol forquerying and modifying directory services running over TCP/IP. The Personnel ImportUtility uses the LDAP-compatible Microsoft Active Directory service. An LDAP directoryusually followings the x.500 model: it is a tree of entries, each of which consists of a setof named attributes with values.

Note: If you need to know more about the KDAP beyond the information that is providedin this manual, please consult websites and other literature for this networkprotocol.

Protocol Overview

LDAP is a protocol designed to be a lightweight front-end to a X.500 directory or stand-alone directory serve, such as Active Directory, over the Transmission Control Protocol(TCP) and the User Datagram Protocol (UDP).

LDAP is a client-server protocol that enables you to locate specific information and otherresources, such as files and devices on a network. Protocol elements are carried directlyover TCP or UDP, thereby bypassing much of the session/presentation overhead

requires for other directory serves, such as X.5000. LDAP uses a lightweight basicencoding rule (BER) notation to encode all protocol elements.

LDAP Directory Structure

The protocol accesses LDAP directories, such as Active Directory services, which followthe X.500 model:

• A directory is a tree of director entries.

• An entry consists of a set of attributes.

• An attribute has a name (an attribute type or attribute description ) and one or morevalues.

• The attributes are defined in a schema.

Each entry has an unambiguous name: Distinguished Name (DN). This consists of itsRelative Distinguished Name (RDN) constructed from some attribute(s) in the entry,followed by the parent entry’s DN. Think of the DN as a full filename, or a databaseindex value, and the RDN as a relative filename in a folder. For more information onthese names, refer to “Active Directory” earlier in this appendix.

A server holds a subtree starting from a specific entry (for example,“dc=example,dc=com” and its children). Servers may also hold references to otherservers, so an attempt to access “ou=Some department,dc=example,dc=com” couldreturn a referral or continuum reference to a server that holds the part of the directorytree. The client can then contact the other server. Some servers support chaining , whichmeans the server contacts the other server and returns the results to the client.



TAC 702

LDAP rarely defines any ordering. The server may return the values in an attribute, theattributes in an entry, and the entries found by a search operation, in any order.

The following is a table of acronyms used in LDAP.

ADSI Active Directory Services Interfaces

ADS Active Directory Services

DNS Domain Name System

DN Distinguished Name

OU Organizational Name

CN Common Name

LDIF LDAP Data Interchange Format

RDN Relative Distinguished Name

DC Domain Controller

ADAM Active Directory Application Mode

The following is a table of Active Directory user attributes information and theircorresponding LDAP names.

Attribute

Name

Description CN LDAP Display

Name

Text-Country The country/region in whichthe user is located.

Text-Country

CO

Address The user's address. Address streetAddress

Address-Home

The user's home address. Address-Home

honePostalAddress

Assistant The distinguished name of auser's administrative assistant.

Assistant Assistant

Comment The user's comments. Thisstring can be a null string.

Comment info

Picture An image of the user. A space-efficient format like JPEG orGIF is recommended.

Picture thumbnailPhoto

Country-Name

The country/region in theaddress of the user. Thecountry/region is representedas the 2-character countrycode based on ISO-3166.

Country-Name

C

Facsimile-Telephone-Number

Contains the telephonenumber of the user's businessfax machine.

Facsimile-Telephone-Number

facsimileTelephoneNumber




AttributeName

Description CN LDAP DisplayName

International-ISDN-Number

Specifies an InternationalISDN Number associated withan objet.

International-ISDN-Number

internationalISDNNumber

Locality-Name

Represents the name of alocality, such as a town or city.

Locality-Name

l

Personal-Title The user's title. Personal-

Title

PersonalTitle

Post-Office-Box

The P.O. Box Number for thisobject.

Post-Office-Box

postOfficeBox

Postal-Address

The mailing address for theobject.

Postal-Address

PostalAddress

Postal-Code The postal or zip code for maildelivery.

Postal-Code

PoastalCode

State-Or-Province-Name

The name of a user's state orprovince.

State-Or-Province-Name

st

Steet-Address

The user's street address. Street-Address

street

Telephone-Numer

The user's primary phonenumber.

Telephone-Number

telephoneNumber

Phone-Home-Other

A list of the user's alternatehome phone numbers.

Phone-Home-Other

otherHomePhone

LDIF (LDAP Data Interchange Format)

The LDAP Data Interchange Format (LDIF) is a data interchange format that facilitatesexporting data from and importing data to LDAP domain servers. It conveys directoryinformation or a description of changes made to directory entries. The data are

represented in plain text form, with a LDIF file comprising a number of records (directoryentries or changes to directory entries).

The following is a complete example and explanation of what an entry can look like,when represented in LDAP Data Interchange Format, or LDIF (LDAP itself is a binaryprotocol).

Dn: cn=John Doe,dc=example,dc=comcn: John DoegivenName: Johnsn=DortelephoneNumber: +1 555 6789telephoneNumber: +1 555 1234mail: [email protected]

2. How to manipulate states



3. Adding templates based on department:

TAC 706

Giving single value and appending Department to it:<RefTemplate><xsl:value-of select="concat('Root\Templates\Personnel Templates\',Department)"/></RefTemplate>

Giving single value:<RefTemplate> Root\Templates\Personnel Templates\PT1</ RefTemplate>

4. Manipulating telephone numbers

<WorkPhone><xsl:choose><xsl:when test="contains(WorkPhone,'-')">

<xsl:value-of select="WorkPhone"/></xsl:when>

<xsl:when test="string-length(WorkPhone)=0"><xsl:value-of select="WorkPhone"/>

</xsl:when><xsl:otherwise>

<xsl:value-of select="concat(substring(WorkPhone,1,3),'-,substring(WorkPhone,4,3),'-',substring(WorkPhone,7,4))"/>


</WorkPhone>

5. Adding individual Continuum attributes

<CardType>AC4plus432</ CardType>

<SiteCode>35</ SiteCode>

6. Adding Arealinks









7. Removing carriage return characters (or any characters) when importing ADattribute values

TAC 708

8. Manipulating multi-valued attributes

!--************************************************************** -->

9. Using your own functions in an XSL file



<msxsl:script language="C#"implements-prefix="TAC">



<![CDATA[

public string today() {return "abcdefs";

} ]]>

</ msxsl:script> Use functions only when you need more flexibility/power than XSL supports.



TAC 710




Appendix D Schedul ing Automatic Personnel

Object Updates



TAC 712

This appendix provides a procedure for setting automatic updating of personnel data inCyberStation with data from your personnel application. This information applies only tocustomers who use the Personnel Import Utility to import personnel records intoCyberStation. For more information about the Personnel Import Utility, see Chapter 19.

The Windows Task Scheduler is a Windows system tool you can use to run scripts orprograms according to a schedule. With this tool, you may regularly perform personnelimport operations automatically at specific times.

Note: Before you run Task Scheduler, make sure the computer’s date and time settingsare accurate.

Perform the following steps to set up and run a task automatically:

1. From the Windows Start menu, select Programs, select Accessories, selectSystem Tools, and then select Scheduled Tasks.

Note: This procedure is based on Microsoft Windows XP. Other user interfaces mayvary.

2. In the Schedule Tasks dialog, double click Add Scheduled Task , and click Next.

3. To search for the program you want to run (PersonnelImportUtility), click Browse.

4. Double click the Program Files folder, and then double click the Continuum foler.

5. Navigate to and double click PersonnelImportUtility.exe.

The Schedule Task Wizard automatically displays the application name in theprogram naming field.




6. Select one of the radio buttons to specify how often you want to thus update to run

automatically, and click Next.7. Select the time and day you want this scheduled task to start, enter a Start time and

Start Date in their respective fields, and click Next.



TAC 714

8. Enter the name and password of a user in the Enter the user name field and Enterthe password field respectively, and click Next.

The final screen informs you that the task has been successfully scheduled. It alsoprovides the time and frequency of the task and the day it begins. For example:




If you want to configure more advanced properties for this scheduled task, check theOpen advanced properties for this task when I click Finish checkbox.

9. Click Finish.

10. The PersonnelImportUtility dialog appears.

This dialog contains the advanced properties for this task, as mentions in theprevious step. If you do not check this box in the previous step, the scheduled tasksetup completes, and the PersonnelImportUtility dialog does not appear.

11. In the Tasks tab of the PersonelImportUtility dialog, enter the command in the Run field as follows:

“C:\Program Files\Continumm-C “ConfigurationFileName” –G “No” –E“ErrorFil.txt” “-U “acc”

Note: When entering the command rom here, please make sure you set theparameters outside the quotes surrounding the path name.

If the ObjectName and/or UserName contains a space, then you must also placequotes around those items.



TAC 716

12. Enter the path of the folder in which you are starting the application in the Start field.In this case:

“C:\Program Files\Continuum”

13. In the Schedule tab, click the Advanced button to bring up the Advanced ScheduleOptions dialog. Configure more advanced settings as needed, and click OK.

14. On the PersonnelImportUtility dialog, configure other advanced settings as neededon the Task, Schedule, and Settings tabs.

15. Click OK to completely the setup.

The following is a table of permissions for managing scheduled tasks.

Full Control View, Run, Change, Delete, Change Owner

Modify View, Run, Change, Delete

Read and Execute View, Run

Read View

Write View, Run, Change, Delete




The following is a table of names you must use and a description of those names.

Name Description

-C Configuration File Name

-G UI Mode

-E Error File Name

-U Continuum User Name

PersonnelImportUtility Executable File Name

Working with Scheduled Tasks

After creating a schedule, you are able to modify it and/or check the status of thatschedule. There are many options offered by the Task Scheduler to work with existingschedules.

• Start and Stop Scheduled Tasks:

Rather than having to wait for the next scheduled occurrence, you are able to run anyschedule at any time. To do this, open the Scheduled Tasks window, select the taskyou wish to start or stop, choose File from the menu bar, and select Run. You couldalso just right click on the specific task and select Run.

• Check the Status of Scheduled Tasks:

To check the status of a scheduled task, select the Details view of the Scheduled

Tasks window. To access the log file, open the Schedule Tasks window, selectAdvanced from the menu bar, and select View. It is also possible to open the logmanually from Notepad. Below is a table of status notation and their meanings.

Status Notation Meaning

Could not start The most recent attempt to start the task failed.

Empty The task is not running or the task has run successfully.

Missed One or more attempts to run the task were missed.

Running The task is running.

• Modify Scheduled Tasks:

To change the properties for an already existing task, open the Scheduled Tasks window and select the task you wish to modify. Open the task’s Properties dialogand make the needed changes.

• Delete Scheduled Tasks:

To delete a scheduled task, open the Scheduled Tasks window and select the taskyou wish to delete. Press the Del key, click the Delete icon on the toolbar, or choose

File from the menu bar, and then select Delete. It is also possible to right click thetask and select Delete from the popup menu.



TAC 718

Note: Task Scheduler sends deleted tasks to the Recycle Bin. If you do not want a taskto run, but think you might want to use the task later, Disable the task instead ofdeleting it.

Selecting Global Options

The Task Scheduler Advanced Menu offers many options for controlling the way thescheduled tasks operate. To get to this menu, open the Scheduled Tasks window, andselect Advanced from the menu bar. You are presented with the following options.

Option Description

Stop Using Task Scheduler Select this option to disable all scheduled tasks andprevent Task Scheduler from running automaticallywhen you start Windows.

To get to this menu, open the Scheduled Tasks window and click Advanced in the menu bar.

In order for the Task Scheduler to return to its normaloperation, you must select Start Using TasksScheduler.

Pause Task Scheduler Select this option to temporarily stop running tasks andprevent Task Scheduler from running automatically

when starting Windows. This command is especiallyuseful to stop tasks while you are installing software.

In order to resume Schedules Tasks, you must selectContinue Task Scheduler.

Any tasks that were scheduled to run while PauseTask Scheduler was active will go on to run at the nextscheduled time.

Notify Me of Missed Tasks This option notifies you only of Task Schedulers failure,not of individual missed tasks . Tasks that fail to runbecause of corrupt or missing executables do not setoff a notification.

AT Service Account This option allows you to change the user accountunder which tasks scheduled with the At command willrun (the default account is System). Select this optionopens the AT Service Account dialog.

To change the account, select This Account, enter auser account, and then enter and confirm the passwordfor that account.

View Log Select this option to open the task log in Notepad. Youcan use the log to track the success or failure of yourscheduled tasks.




Appendix E Custom Card Formats



TAC 720

Configuring CyberStation for Custom ABA Card Access

In addition to supporting the ISO 7811 ABA (American Banking Association) standard themagnetic stripe cards, CyberStation now provides support for custom ABA access cards.The CyberStation standard ABA card format only reads one field (the Primary AccountNumber or PAN) consisting of 19 digits from the card, which is used it identify the cardnumber. The custom ABA card format expands that capability (in addition to the cardnumber) to provide support for:

• Site code

• Issue code

• Manufacturer code

CyberStation provides the user with an interface to specify the structure of a custom ABAmagnetic stripe card.

Custom ABA Card Rules

In order for CyberStation to support custom ABA cards the following requirements apply.

• Andover Continuum CX series controllers connected to AC-1 Plus Door Accessmodules must be used.

• A door can be configured for ABA Format2 or Custom ABA, but not both.

•

Only one custom ABA format will be supported at a time.• The default mode for parsing a card is fixed length. Installations not using f ixed length

cards must indicate that they are using variable length structures with a specialidentifier character (V) described later in this section.

Overall Process

The over process of setting up CyberStation to support custom ABA access cards worksas follows:

Define a special InfinityString object in the CX controller editor and name itCustomABAFormat. This allows CyberStation to interrupt important custom informationcontained on a person’s ABA access card – for example, the site or “faculty” code, theissue code, the manufacturer code, and so on.

• Specify the Custom ABA card format in the Door editor.

• Enter the card number and site code of the Personnel object for each holder.

• Once the door is configured for Custom ABA card format, the CX controller sends thevalue of the string to the AC-! Plus modules.

• The AC-1 Plus modules use the information in the string to parse card swipes andthen send the parsed data (CardNumber, SiteCode, etc.) to the CX controller forvalidation.




Procedure

The detailed steps involved in defining and configuring a custom ABA card format aredescribed below.

1. In network view in the Continuum Explorer, right click the CX controller to beconfigured for the custom ABA format.

2. Select New, and then select InfinityString from the dropdown menus.

3. Type in CustomABAFormat in the Object name field of the New dialog.

4. Click the Create button. This InfintyString editor will appear.

5. In the General tab, set the String Size field to 60 or less characters. 132 is thedefault. If you enter more than 60 you will receive an error message (only on CXreload).

6. Ensure that the Setpoint checkbox is checked (the string must be identified as asetpoint) and click Apply.

7. In the Value field, enter the unique alphanumeric characters for theCustomABAFormat string.

8. Click OK.

9. Open the Door editor associated with the CustomABAFormat CX controller selected

in step 1.

10. In the Card Formats tab, select the Card Format ABA radio button.

11. Select the ABA Formats Custom checkbox.

12. In the Entry Reader tab, select the Validate Site checkboxes, along with any otherapplicable checkboxes.

13. Repeat step 12 for the Exit Reader tab.

14. Click OK.

15. Open the Personnel Manager (or Personnel editor) for the person holding aCustomABAFormat access card.

16. From the Card Type dropdown menu, select CustomMagStripe.

17. Enter the correct numbers in the Site Code and Card Number fields.

Site Code is optional. If it is not used, set it to 0.

18. Click OK.

Repeat steps 15-18 for each custom ABA cardholder.



TAC 722

Guidelines for Creating a CustomABAFormat InfinityString

The special name CustomeABAFormat (step 3 above) together with the uniquealphanumeric InfinityString that you enter as its value (step 7 above), s what tellsCyberSTation howt o interpret and validate the information on a peron’s custom ABAcard.

Every CX controller that has AC-1 Plus IOU modules attached will need to have its owninstance of the CustomABAFormat InfinityString object. The string structre must matchthe layout of the data on the card.

Definitions Associated with ABA Card Formats

The following table describes important terms used when dealing with ADA card formats.

Term Description

Bit A binary digit with the value of either 0 or 1. Each trackconsists of a string of bits; but strings make up an alphaor numeric character.

Start Sentinel A defined character (bit pattern) in an encoding format.Cannot be all zeros. The Start Sentinel is encoded onthe magnetic stripe immediately before the first datacharacter and indicates the beginning of data.

Field Separator A designated character, which separated data fields.Cannot be used for data.

End Sentinel A defined character (bit pattern) in an encoding format.Cannot be used for data. The End Sentinel is encodedon the magnetic stripe immediately after the last datacharacter and indicates the beginning of data.

Longitudinal

Redundancy Check Character (LCR)

A bit pattern, which is encoded immediately after theEnd Sentinel. Checks for bit errors in the message,which includes the Start Sentinel, End Sentinel, data,and Field Separators.

Custom ABA Card Structure

ABA cards are digit oriented, not bit oriented. The card structure defines the membershipof each digit to one or more of the card fields with each field having a character identifier.The character identifiers are assembled in a CX controller string object(CustomABAFormat), which contains all the information needed to allow the AC-1 PlusIOU modules to parse the card swipes.

The supported card fields are SiteCode, CardNumber, IssueCode, andManufacturerCode. Other elements of the cardstructure are the StartSentinel,FieldSeparator, EndSentinel, and the LRC Check.

TAC provides the following card data fields that you must use in defining your structure.




Card Field Description AlphanumericIdentifier

Start Sentinel (forfixed length structure)

Indicates the beginning of data. See“Definition,” above.

T (an ASCIIcharacter)

Start Sentinel (forvariable-lengthstructure)

See “Definitions,” above, and “Rulesand Guidelines,” later in this chapter.

V (an ASCIIcharacter)

Site or Faculty code The site code, if used, is a number

that identifies your facility. See “SiteCode Requirements,” later in thischapter.

1 (a hexadecimal

integer)

Card Number Contains the custom ABA cardnumber. See “Card NumberRequirements,” later in this chapter.

2 (a hexadecimalinteger)

Field Separator Separates the digits of one field fromanother. See “Definitions,” above.

S (an ASCIIcharacter)

Card Issue Code If used, the number of times a personhas been issued a card – second,third, fourth, and so on. See “CardIssue Code Requirements,” later inthis chapter.


Manufacturer Code Identifies the card’s manufacturercode. See “Manufacturer CodeRequirements,” later in this chapter.


Shared-field Integers Each of these integers indicates thatthe digit is shared in two or morefields. If you specify shared-fieldintegers, the string structure must befixed-length. See “Shared-field IntegerRequirements,” later in this chapter.

Any otherhexadecimalinteger

Not Used Indicates digits that are not used

within the string structure. See “Rulesand Guidelines,” later in this chapter.

X (an ASCII

character)

End Sentinel Indicates the end of data. See“Definition,” on previous page.

Z (an ASCIIcharacter)

LongitudinalRedundancy Check (LRC)

Checks for bit errors when the card isread. See “Definitions” on previouspage.

L (an ASCIIcharacter)

Raw Data Mode To read the raw data encoded on acard, set the first characters to R. See“Raw ABA Data Mode,” later in thischapter.

R (an ASCIIcharacter)



TAC 724

Example of a CustomABAFormat String

As an example, you might enter the following value as a CustomABAFormat string:

T3311222222222SXXXX8888ZL

Settings the CustomABAFormat string to the value shown above tells CyberStation tointerpret the information read from a custom ABA card as follows:

• The first digit (T) is the start sentinel.

• The second and third digits (33) are the first two digits of the site code as well as the

first two digits of the card number since both fields share them.• Digits 4 – 6 (111) are the remaining digits of the site code.

• Digits 7-15 (222222222) are the remaining digits of the card number.

• Digit 16 (S) is a field separator.

• Digits 17-20 (XXX) are ignored by CyberStation since they have been marked as notused.

• Digits 21-24 (888) make up the manufacturer code.

• Digit 25 (Z) is the end sentinel.

• Digit 26 (L) is the LRC (Longitudinal Redundancy Check).

Now, suppose that a card that has been previously encoded with the following data isswiped at the custom ABA door.

SS1055123456789FS20021040ESL

(For the purpose of this illustration, SS is the start sentinel, FS is the field separator, andES s the end sentinel.)

In accordance with the CustomABAFormat string entered in the example on the previouspage, CyberStation will interpret the card data as follows:

Site Code 10555Card Number 10123456789Not Used 2002Manufacturer Code 1040

Note that the site code and card number share the same first two digits (10) as

determined by the 33 in the string format.Rules and Guidelines

Here are some important rules and guidelines to follow when entering the string structurevalue:

• CyberStation parses and interprets the card data from left to right, based on thestring structure you provide. The leftmost digit becomes the most significant digit.Remember, the a limit of 60 characters.

• There is a limit to the number of digits each field may have.

Field Limit

Card Numer 19 digits




Site Code 5 digits

Card Issue Code 2 digits

Manufacturer Code 16 digits

• In a fixed-length structure, the number of digits in a field of a person’s card mustmatch the number of digits in each field of the structure you define. For example, ifyour facility’s code (site code) is 75 (encoded on the second and third digits on youcards) and your cards use up to 4 digits for the card number (encoded on the fourththrough seven digits) you would configure the CustomABAFormat string as follows:

T112222…

When the cards are encoded, any card with a card number less than four digits mustbe padded to four digits. For example, a card with card number 12 must be encodedwith 0012 in the card number field.

• In a fixed-length structure, you must use a field separator (S) to correspond withevery place it appears in the person’s card. For example, if the card contains fourfield spearators, your structure must have four separators that must appear in thesame location specified by the CustomABAFormat string. If the card has noseparators, your structure should have no separators.

• A variable-length structure can accommodate cards containing fields whose digitsvary in length. If the number of digits in a field on a person’s card is less than thenumber of corresponding digits in your structure, then CyberStation pads hat numberwith zeros. For example, if a person’s site code is 75, the card number is 1234, andyour structure is V11111S222222, then these numbers become:

00075001234

In a variable-length structure, you must use a field separator (S) to separate thefields. The card must be encoded with a field separator to indicate to CyberStationwhere each field ends, as follows:

SS74FS1234FS………….ESLRC

(For the purpose of this illustration, SS is the start sentinel, FS is the field separator,and ES is the end sentinel.

•

In any structure, the not-used character (X) should correspond with digits that are notused on the card (see example on previous page).

• Any ASCII character, other than A, B, C, D, E, F, L, R, S, T, V, X, and Z, is invalid.

Card Number Requirements

The field containing the integer 2 represents the card number that is read from a person’scustom ABA card. The limit is 19 digits. The largest card number supported is99999999999999999999. The structure must be fixed-length when one ore more digitsare shared. See, “Shared Site Code Requirements,” below. The card number must be

entered in the Card Number field on the Personnel editor’s General tab.



TAC 726

Site Code Requirements

The field containing the integer 1 represents a person’s site. The limit is five digits. Thelargest site doe supported is 65535. The site code is optional. If you have a site code, itmust be entered in a Site Codes field on the Personnel editor’s General tab.

Card Issue Code Requirements

The field containing the integer 4 represents digits belonging to the card issue code (thatis, if your site uses issue codes). The limit is 2 digits. CyberStation reads the issue code(one or two digits) from the card, and attaches the code to the beginning of the person’s

card number, whereby is becomes part of the card number. The card number is firstpadded with zeros if necessary until it has the same number of digits as specified in theCustomABAFormat string.

For example, if a peron’s card number is 751, the issue code is12, and if theCustomABAFormat string specifies a 6- digit card number, the resulting card number is:

12000751

CyberStation inserts the issue code in front (to the left) of the card number.

Note: Because the issue code becomes the first digits (or first 2 digits) of a person’s cardnumber, you must enter this modified card in the Card Number field in Personnelobjects, so that CyberStation recognizes the issue code. Using the exampleabove, you would enter 12000751.

Manufacturer Code Requirements

This field contain the integer 8 represents digits belonging to the manufacturer code (thatis, if your site uses a manufacturer code). The limit is 16 digits.

Note: You must append the card’s actual manufacturer code after the LRC (L) wherebythis code becomes the last digits of the structure. For example, if the manufacturercode on your card is 576, then the latter half of the CustomABAFormat stringwould look similar to this:

…S44XXX888ZL576where CyberStation will reject any cards that does not contain the number 576 inthe location specified by the code 888 in the CustomABAFormat string.

Shared-Field Integer Requirements

In two or more fields, you may share any digit that is read from a person’s card. To do so,use one or more of the following hexadecimal integers in your string structure:

3, 5, 6, 7, 9, A, B, C, D, E, or F

Each of these integers tells CyberStation to read the digit and use it in the field specifiedby the integer. For example, the integer 3 means the digit is used in the card number andthe site code. The integer D means the digit is used in the site code, the card issue code,and the manufacturer code (See the table below).

Note: To accommodate shared-field integers, your string structure must be fixed-length.




You must place the overlapping (shared) integer in the structure from left to right becauseCyberStation parses digits from left to right.

For example, suppose you were sharing two numbers in the site code and card number.(The integer 3 specifies a share between these two fields.) Suppose the person’s sitecode is 75, and the card number is 75944. The site code and card number fields in yourstructure would look similar to this:

T332222…

For every combination of shared fields (two, three, or four fields), the following table tells

you which hexadecimal integer to use in your string structure.

Note: Each integer below is the sum of the integers that represent the shared fields (1 forsite code, 2 for card number, 4 for card issue code, and 8 for manufacturer code).For example, a 9 specifies a share between the site code field (1) andmanufacturer code field (8) – in other words, 1 plus 8. A 6 specifies a sharebetween the card number field (2) and the card issue code field (4) – in otherwords, 2 plus 4.

To Share Digits in theseFields…

Use this SharedHexadecimal Integer

Card NumberSite Code

3(represents 2+1)

Site CodeCard Issue Code

5(represents 1+4)

Card NumberCard Issue Code

6(represents 2+4)

Card NumberSite CodeCard Issue Code

7(represents 2+1+4)

Site CodeManufacturer Code

9(represents 1+8)

Card NumberManufacturer Code

A(represents 2+8)

Card NumberSite CodeManufacturer Code

B(represents 2+1+8)

Card Issue CodeManufacturer Code

C(represents 4+8)

Site CodeCard Issue CodeManufacturer Code

D (represents 1+4+8)



TAC 728

To Share Digits in theseFields…

Use this SharedHexadecimal Integer

Card NumberSite CodeManufacturer Code

E

(represents 2+1+8)

Card NumberSite CodeCard Issue Code

Manufacturer Code

F(represents 2+1+4+8)

Remember the string structure must be fixed-length.

Raw ABA Data Mode

Sometimes it is desirable to read the “raw” data encoded on a card. To do this, the firstcharacter that you enter in the CustomABAFormat string must be an R. This charactertakes the place of the StartSentinel.

When the CX controller detects such a string, it sends a Custom Card event to theCyberStation workstation and allows the raw card data to appear in an Active Event Viewwhenever the card is swiped. The raw data that appears will be from the Start Sentineldigit to the LCR digit.

Multiple Custom Card Formats

You can now define more than one AccessFormat array object. This will enable theaccess control engine to handle more than one custom card format per controller.

Note: Multiple Custom Card Formats are supported in the CX99xx and NetController II(96xx) controllers only.

Requirements

• The points must be named AccessFormat, AccessFormat2, AccessFormar3 , andAccessFormat4 .

• Each custom card format must have a unique site code, otherwise the system will notbe bale to uniquely identify people with the same card number but different formats.

• Selecting the Custom card type on a door will allow all custom card types to enterthat door.

Functionality

There is no change in the way custom cards are implemented; this new revision onlyexpands the number of custom cards supported from one to four.

Custom Card Validation in Degrade Mode

Degrade Mode is when the AC-1 cannot communication with the NetController. For theAC-1 to perform site code validation when operating in degrade mode, do the following:




Add the following code at the end of the Plain English program where the AccessFormat array9s) is/are initialized:

Numeric siteCode1, SiteCode2, SiteCode3, SiteCode4

‘Set up AccessFormat below

‘AccessFormat[0] =

‘etc

‘STORE SITE CODES FROM DOOR

SiteCode1 = MyDoor Site1



SiteCode4 – MyDoor Site4

‘CLEAR DOOR’S SITE CODES

MyDoor Site1 = 0

MyDoor Site2 = 0MyDoor Site3 = 0

MyDoor Site4 = 0

‘RESOTRE DOOR’S SITE CODES

MyDoor Site1 = SiteCode1



MyDoor Site4 = SiteCode 4

All site code information is sent to the AC-1s for each card type selected in the followingorder.

1. Infinity37

2. AC4Plus432

3. Weigand26

4. CK34

5. Custom

6. G31



TAC 730

The AC-1 can only store all four site codes for one format and the last one selected fromthe above list wins. Out of the four possible Custom Access Format arrays, only theAccessFormat is sent to the AC-1. Note that if G31 were select, the AC-1 would storethat instead of Custom Access Format.




Appendix F Points – Electr ical Types



TAC 732

Infinity Electrical Types and BACnet Objects

Andover Continuum supports BACnet-compliant devices — for Andover Continuumb4920, bCX1 (b40x0 series), and b3 controllers, as well as third-party devices.

When you create an InfinityInput or InfinityOutput residing on Andover ContinuumBACnet controller, a BACnet Analog, Binary, or Multistate input or output object is alsocreated, depending on the electrical type you assign when the InfinityInput orInfinityOutput point is created via their respective editors.

For example, if you select an analog electrical type, Voltage , a BACnet AnalogInput orAnalogOutput is also created. If you select a binary electrical type, Digital , a BACnetBinaryInput or BinaryOutput is also created. If you select a multistate electrical type,Supervised or Tristate , a MultistateInput or MultistateOutput object is created,respectively.

These BACnet Analog, Binary, and Multistate input and output objects may be viewed inthe BACnet devices portion of the Continuum Explorer’s navigation pane. Their Infinitypoint counterparts may be viewed in the Infinity portion of the navigation pane. Pleasesee Chapter 14 for a description of the Analog, Binary, and Multistate object editors, aswell as BACnet device operations in general.

InfinityInput Types

Type Description

ACC_Airflow Not Available: This electrical type will be available in afuture release.

ACC_Keypad Not Available: This electrical type will be available in afuture release.

ACC_Pressure Not Available: This electrical type will be available in afuture release.

ACCTemp(DegC) Use this electrical type for Andover Continuumthermistor type temperature sensors, and for the EMX170/SP 100 temperature sensor modules. This inputtype performs the conversion from voltage to

temperature in degrees Celsius.

ACCTemp(DegF) Use this electrical type for Andover Continuumthermistor type temperature sensors, and for the EMX170/SP 100 temperature sensor modules. This inputtype performs the conversion from voltage totemperature in degrees Fahrenheit.

Counter Use this electrical type for a pulse counting input. Thecounter triggers on the falling edge of the inputwaveform.




Type Description

Digital Use this electrical type of the input point is an ON orOFF contact closure. After you select Digital as anelectrical type, a checkbox for Polarity will appear. If youwant to invert the meanings of ON and OFF, click thebox to put a check mark in it.

InputCurrent Use this electrical type if the input is a current type.

RTD1000TempC Use this electrical type for RTD 1000 Ohms

temperature (Celsius) sensors.

RTD1000TempC2W Use this electrical value if the sensor is a ResistiveThermal Device Temperature Sensor, 1000 Ohms,Degrees Celsius, 2 wire.

RTD1000TempF Use this electrical type for RTD 1000 Ohms temperature(Fahrenheit) sensors.

RTD1000TempF2W Use this electrical value if the sensor is a ResistiveThermal Device Temperature Sensor, 1000 Ohms,Degrees Fahrenheit, 2 wire.

RTDTemp(DegC) Use this electrical type for Andover Continuum 1K RTDresistive type temperature sensors. These sensors must

be wired to two consecutive input points where the firstchannel number is an odd number. Assign the oddnumber as the channel number. This input typeautomatically performs the conversion from resistanceto temperature in degrees Celsius. RTD Temp is onlyavailable on 9400 and 9500 series controllers.

RTDTemp(DegF) Use this electrical type for Andover Continuum 1K RTDresistive type temperature sensors. These sensors mustbe wired to two consecutive input points where the firstchannel number is an odd number. Assign the oddnumber as the channel number. This input typeautomatically performs the conversion form resistanceto temperature in degrees Fahrenheit. RTD Temp is

only available on 9400 and 9500 series controllers.

RTDTempC2W Use this electrical type if the sensor is a ResistiveThermal Device Temperature Sensor, 100 Ohms,Degrees Celsius, 2 wire.

RTDTempF2W Use this electrical type if the sensor is a ResistiveThermal Device Temperature sensor, 100 Ohms,Degrees Fahrenheit, 2 wire.



TAC 734

Type Description

Supervised Use this multistate electrical type if the input is for anaccess control system on either a 700 or a 800 seriescontroller, an AC1, AC1Plus or AC1A Continuummodule, a b4 or b3 controller, and most Infinity models.

This type creates three states: On, Off, and Trouble.

Supervised inputs are normally part of a Door object, soyou do not have to set them up as input points unless

you want to user them in programs, or associated themwith alarms.

After you select Supervised as an electrical type, acheckbox for the resistor type will display. Click thedown arrow to select one of the following: NoSeries,NoParallel, NoSerPar, NCSeries, NCParallel, orNCSerPar.

If the resistor is for a Supervised input on a EMX 190 orCRM 100 (channel 9, 10, 11, or 12), you must selectNOSeries, NOParallel, NCSeries, or NCParallel.

Note: When this type is selected, a BACnetMultistateInput object, with these three states (On,Off, and Trouble) is created, in addition to theInfinityOutput point. The MultistateInput can beviewed in the BACnet devices portion of theContinuum Explorer’s navigation pane. Pleasesee Chapter 14 for a description of theMultistateInput editor and on BACnet in general.

TankProbe Use this electrical type for a probe on TankNet

ThermoCoupBTempC Not Available: This electrical type will be available in afuture release.

ThermoCoupBTempF Not Available: This electrical type will be available in afuture release.

ThermoCoupETempC Not Available: This electrical type will be available in afuture release.

ThermoCoupETempF Not Available: This electrical type will be available in afuture release.

ThermoCoupJTempC Not Available: This electrical type will be available in afuture release.

ThermoCoupJTempF Not Available: This electrical type will be available in afuture release.

ThermoCoupKTempC Not Available: This electrical type will be available in afuture release.




Type Description

ThermoCoupKTempF Not Available: This electrical type will be available in afuture release.

ThermoCoupRTempC Not Available: This electrical type will be available in afuture release.

ThermoCoupRTempF Not Available: This electrical type will be available in afuture release.

ThermoCoupSTempCNot Available: This electrical type will be available in afuture release.

ThermoCoupSTempF Not Available: This electrical type will be available in afuture release.

ThermoCoupTTempC Not Available: This electrical type will be available in afuture release.

ThermoCoupTTempF Not Available: This electrical type will be available in afuture release.

Voltage Use this electrical type if the input point is a voltage orcurrent sensor. Continuum gives a voltage reading forthis type of sensor, so you will need to enter aconversion formula on the Conversions page.

InfinityOutput Types

Type Description

Current Select this type if the output is a current type.

Digital Use this electrical type of the output point is an ON or OFFcontact closure. After you select Digital as an electrical type, atext box for Polarity will appear. If you want to invert themeanings of ON and OFF, click the box to put a check mark init.

HiResCurrent Select this type for certain EMX input modules.

HiResVoltage Select this type for certain EMX input modules.

PanelMeter Use this unit type when setting up an output point for an LS-8Seven Segment Display Board IOU module. A PanelMeteroutput allows a Plain English program to assign a numericvalue to the display without doing a string conversion. TheAlternative is to use a string output, but the Plain Englishprogram must convert the string using the NumToStrnfunction.



Type Description

Pneumatic Select this type if the output is a pneumatic type. Pneumatic isapplicable only if the controller is an Infinet controller and thepoint is on an EMX 140 or POM 200 expansion module. If youhave an EMX 141 or an EMX 143 with only one output, youmust skip a channel for the missing one.

Tristate Select this multistate type if the output is a tristate type (ON,OFF, and -ON).

Note: When this type is selected, a BACnet MultistateOutputobject, with these three states, is created, in addition to theInfinityOutput point. The MultistateOutput can be viewed in theBACnet devices portion of the Continuum Explorer’snavigation pane. Please see Chapter 14 for a description ofthe MultistateOutput editor and on BACnet in general.

Voltage Use this electrical type if the output point is a voltage output.Continuum gives a voltage setting for this type of output, soyou will need to enter a conversion formula on theConversions page.

andover continuum

Documents