Version 3 System Description - Jan14 - 03 PDF

- 1 -
ORCA Native BACnet

System Description

- HVAC
- LIGHTING
- ACCESS

- 2 -
Table of Contents
TABLE OF CONTENTS............................................................................................................................................. 2
DELTA CONTROLS................................................................................................................................................... 5
ORCA SYSTEM DESCRIPTION............................................................................................................................. 5
HVAC HARDWARE................................................................................................................................................... 6
Native BACnet......................................................................................................................................................... 6
Peer-to-Peer............................................................................................................................................................ 6
HVAC, Lighting and Access Integration............................................................................................................... 6
LINKnet................................................................................................................................................................... 6
HARDWARE PRODUCT DESCRIPTION.......................................................................................................................... 7
Delta System Managers.......................................................................................................................................... 7
Delta System Controllers........................................................................................................................................ 8
Delta Application Controllers................................................................................................................................ 9
Delta Field Modules............................................................................................................................................. 11
Delta Network Thermostats.................................................................................................................................. 12
Delta Network Sensors......................................................................................................................................... 14
I/O APPLICATION GUIDE........................................................................................................................................... 14
Input Types............................................................................................................................................................ 14
Outputs Types ....................................................................................................................................................... 14
LIGHTING HARDWARE........................................................................................................................................ 15
ACCESS HARDWARE............................................................................................................................................. 15
CONTROLLER FIRMWARE................................................................................................................................. 16
STANDARD FEATURES............................................................................................................................................... 16
Native BACnet....................................................................................................................................................... 16
HVAC, Lighting and Access Integration............................................................................................................. 16
SYSTEM CONTROLLERS AND APPLICATION CONTROLLERS.................................................................................... 16
Flash-Loadable..................................................................................................................................................... 16
Real-Time Programming...................................................................................................................................... 16
FIELD MODULES........................................................................................................................................................ 17
DOOR MODULES........................................................................................................................................................ 17
HARDWARE ARCHITECTURE........................................................................................................................... 18
ARCHITECTURE DESIGN............................................................................................................................................ 18
DERIVED NETWORK ADDRESSING (DNA)............................................................................................................... 19
TYPICAL ARCHITECTURES ........................................................................................................................................ 21
LINKnet................................................................................................................................................................. 21
BACnet MS/TP...................................................................................................................................................... 22
Ethernet BACnet MS/TP................................................................................................................................... 23
BACnet/IP............................................................................................................................................................. 24
Operator Workstation Connections..................................................................................................................... 25

- 3 -
ACCESS CONTROL SYSTEM............................................................................................................................... 26
INTRODUCTION.......................................................................................................................................................... 26
ACCESS CONTROL DATABASE OBJECTS................................................................................................................... 28
ACCESS CONTROL SYSTEM FEATURES..................................................................................................................... 28
Seamless Integration with ORCAview................................................................................................................. 28
Card Holders ........................................................................................................................................................ 29
Wiegand Device Support...................................................................................................................................... 29
Card Formats........................................................................................................................................................ 29
Combo Keypad ..................................................................................................................................................... 29
User Database ...................................................................................................................................................... 29
Event Reporting .................................................................................................................................................... 29
Historian ............................................................................................................................................................... 30
Reporting............................................................................................................................................................... 30
Alarms ................................................................................................................................................................... 30
Anti-Passback ....................................................................................................................................................... 30
Flexible Door Control .......................................................................................................................................... 30
Elevator Control ................................................................................................................................................... 31
Degraded Mode.................................................................................................................................................... 31
Hardware Standards ............................................................................................................................................ 31
Object Replication................................................................................................................................................ 31
Easy Integration.................................................................................................................................................... 31
SYSTEM ARCHITECTURE........................................................................................................................................... 32
Hardware.............................................................................................................................................................. 32
Example Uses of Single Door Module................................................................................................................. 33
Firmware............................................................................................................................................................... 34
System Assembly................................................................................................................................................... 34
SYSTEM ARCHITECTURE TOPOLOGIES ..................................................................................................................... 37
SYSTEM ARCHITECTURE TOPOLOGIES ..................................................................................................................... 37
24 Door Access Control System........................................................................................................................... 37
Small Size Integrated Access Control System..................................................................................................... 38
Medium Size Integrated Access Control System................................................................................................. 39
Large Size Integrated Access Control System..................................................................................................... 40
ORCAVIEW OPERATOR WORKSTATION................................................................................................. 41
COMPONENTS ............................................................................................................................................................ 41
Navigator Viewer.................................................................................................................................................. 41
Toolbar.................................................................................................................................................................. 42
Illustrator .............................................................................................................................................................. 43
FEATURES .................................................................................................................................................................. 44
Automatic Device Discovery of Delta and third-Party BACnet Devices........................................................... 44
Context Sensitive Help.......................................................................................................................................... 44
Filterable Real-Time Data View.......................................................................................................................... 44
GCL+.................................................................................................................................................................... 44
Custom View Folders ........................................................................................................................................... 45
Device Object Renaming...................................................................................................................................... 46
Dynamic System Graphics ................................................................................................................................... 46
Multi Trend Viewer............................................................................................................................................... 46
Drag and Drop Technology................................................................................................................................. 46
Bitmap Graphics................................................................................................................................................... 46

- 4 -
WAV Files ............................................................................................................................................................. 46
Multiple Languages.............................................................................................................................................. 47
ORCAWEB.................................................................................................................................................................. 48
COMPONENTS ............................................................................................................................................................ 48
Navigator .............................................................................................................................................................. 48
Tenant Portal ........................................................................................................................................................ 50
Virtual Stat ............................................................................................................................................................ 51
Topology Diagram................................................................................................................................................ 52
Network Architecture............................................................................................................................................ 53
FEATURES .................................................................................................................................................................. 54
Real-Time Navigation........................................................................................................................................... 54
Auto Listing of BACnet Devices........................................................................................................................... 54
USER/GROUP Security Access........................................................................................................................... 54
Object Editing....................................................................................................................................................... 55
Event (Alarm) Handling....................................................................................................................................... 56
Event (Alarm) Notifications Email....................................................................................................................... 57
Graphics Folder.................................................................................................................................................... 58
BMA (BACNET MANUFACTURERS ASSOCIATION) .................................................................................. 58
BMA.......................................................................................................................................................................... 58
BTL (BACNET TESTING LABORATORIES) ............................................................................................................... 59

- 5 -
Delta Controls
With thousands of successful projects throughout the world, Delta Controls Inc. is an
established leader in Building Management and Control. For over two decades, Delta
Controls has been raising the standard for building comfort while reducing operating
expenses in commercial, retail & government buildings; manufacturing, transportation,
sports and other entertainment facilities; and schools, universities and hotels.
Deltas BACnet building automation systems include HVAC, Card Access and Lighting
and feature full interoperability.
With research, development, production and customer solutions under one roof at its
corporate headquarters, Delta ensures the highest level of innovative design, product
quality and customer service in the industry.
Delta is ISO 9001 registered. Deltas quality management system includes all facets of the
design and manufacture of its products and systems.

Our vision Integrated Facilities Management Solutions. Simplified!

ORCA System Description
The Purpose of this document is to provide a general overview and description of the
Delta Controls ORCA (Open Real-time Control Architecture) Native BACnet Product Line.
The intended audience includes, but is not restricted to Consulting Engineers, Building
Owners, and Prospective Dealers.
This document begins with a detailed overview, followed by a layout and analysis of the
possible network architectures. Descriptions are provided for Deltas front-end Operator
Workstation Software (ORCAview), and PC Based WEB Server (ORCAweb). A brief
introduction to the BACnet Manufacturers Association (BMA) and the BACnet Testing
Laboratories (BTL) is also provided.
This document serves to deliver a general system description and is designed to be used
in concert with detailed Delta technical catalogue sheets and Deltas business
development professionals and channel partners.

- 6 -
HVAC Hardware
Native BACnet
Delta Controls ORCA Hardware is native BACnet. Native BACnet means that the
database objects in the controller can be seen by other BACnet systems, and data can be
exchanged between other BACnet devices without the need for a GATEWAY (separate
piece of hardware that maps data between Communication Protocols). Deltas hardware
is easily added into other vendors BACnet architectures because we have implemented
many of the BACnet standards optional properties and have rendered them writeable.
Please refer to the individual hardware PICS (Protocol Implementation Conformance
Statements) to determine the level of interoperability available.
Peer-to-Peer
Delta System Managers (DSM), System Controllers (DSC), and Application Controllers
(DAC), support peer-to-peer data communication and are able to initiate requests. For
example, an Application Controller on a BACnet MS/TP network segment can ask another
Application Controller on a different BACnet MS/TP network segment for data.
HVAC, Lighting and Access Integration
All of Delta Controls products and systems are designed with our Vision Statement in
mind,

Integrated Facilities Management Solutions. Simplified!

In keeping with this Vision, Delta has designed its native BACnet HVAC, Lighting, and
Card Access control systems to work together in a simple, seamless fashion. Single-
sourcing these products from Delta provides the end-user with an operator friendly
integrated system, which improves efficiency, productivity, and cost effectiveness.
Integrating these systems with Deltas ORCAview OWS (Operator Workstation) delivers a
full-featured facility management system.
LINKnet
Delta has developed LINKnet, a proprietary protocol for use with our Native BACnet
controllers. LINKnet uses a BACnet MS/TP backbone with proprietary network services
added by Delta and is used for mapping remote I/O information into a DSC/DAC controller
as virtual I/O. The DSC/DAC controller can then use these virtual I/O objects to execute
control strategies through GCL.
The purpose of LINKnet is to provide incremental point count expansion to our ORCA
Controllers, as well as providing specific specialized I/O in small quantity to a standard

- 7 -
controller (i.e. line voltage relays, lighting relays). It is also used to create specialized I/O
cards for unique markets.

There is a limit to the number of LINKnet Devices that can be connected to the controllers.
The maximum depends on whether the controller is a DSC model or a DAC model. DSC
models can support a maximum of twelve LINKnet devices. Two of the twelve devices
can be LINKnet I/O boards such as the DFM-220, the remainder would be BACstats
(DNS models). DAC models can support a maximum of four LINKnet devices, and two of
the four devices can be LINKnet I/O boards such as the DFM-220. The only exception to
this rule is the DSC-T305 and the DSM-T0. These models have the same support
capacity as the DAC models (four LINKnet devices max, two of which may be LINKnet I/O
boards).

Hardware Product Description
Delta System Managers
These devices are used to route network traffic. Delta System Managers do not have I/O
on board, but can have the same database as other System Controllers. Features include
a Real-Time Clock (RTC), battery back-up, and an EIA-232 serial port. System Managers
are fully programmable.
DSM-050
The DSM-050 is a DCU-050 that is built-up without any I/O capability. You can not
connect a baseboard to it. The DSM-050 comes with a DXC-052-3 Ethernet Network
Card. It is used for routing Ethernet traffic to BACnet IP.
DSM-T0
The DSM-T0 is a Room Controller that is built-up without any I/O capability. You can
have a subnet of DAC controllers or LINKnet controllers beneath it. It is used when
you require a LCD interface without any I/O.
ASM-24
The ASM-24 is hardware that has been specifically designed for use with Delta
access controls products. The ASM-24 has expandable memory for the large
databases required. This product supports 12 individual Door Modules (ADM-
2W704). Access Controls will be described later in this document.
Options:
ASM-24 base model
ASM-24E 10Base-T Ethernet port

- 8 -
Delta System Controllers
Delta System Controllers (DSC) are capable of operating in a stand-alone manner. They
have I/O on-board, a Real-Time Clock (RTC), battery back up, an EIA-232 serial port, and
can support a BACnet MS/TP subnet. System Controllers are fully programmable. All of
these products are shipped with housings (excluding the DSC-1616EX, which is available
with an optional housing).
DSC-1616EX
The DSC-1616EX is a combination of the DCU-050, the DBB-060, and the DXC-052-
2. The DSC-1616EX was the first of the ORCA Controllers. It is designed to have the
I/O on the controller added, as the project requires it. It can be purchased with just the
16 Universal Inputs, 16 Universal Outputs with Module baseboard (DEB-060), or you
can add various I/O expansion modules to it.
Options:
DPM065-xx Pug-In Modules
DEB-100-1 I/O Expansion Board (8 Input & 8 Output)
DEB-100-2 I/O Expansion Board (8 Input and 16 Triac Output)
DEB-101 I/O Expansion Board (32 Universal Input)
DEB-102 I/O Expansion Board (8 Input, 8 Output & 8 Plug-In Module)
DEN768 I/O Expansion Board (Product Enclosures)

DSC-1616
The DSC-1616 has 16 Universal Inputs and 16 Analog Outputs. This controller comes
with optional monitored HOA switches and can be ordered with a built in 10Base-T
Ethernet port. Unlike the DSC-1616EX, this controllers I/O cannot be expanded
through plug-in Expansion I/O cards.
Options:
DSC-1616: base model
DSC-1616H: built in HOA with position feedback.
DSC-1616E: 10Base-T Ethernet port as well as built in HOA with position
feedback.

DSC-1212
Ethernet port.
Options:
feedback.

- 9 -
DSC-1280/H/E
Ethernet port.
Options:
feedback.

DSC-T305
The DSC-T305 is a Room Controller that comes with an Internal 10K Thermistor, 3
Universal Inputs, and 5 Binary Outputs (0.5 Amp FET). It can be ordered with a
variety of keypad configurations. It also has a programmable three line, 36-segment
LCD display.
Options:
Can be ordered with various keypad configurations

Delta Application Controllers
These devices are not designed to operate stand-alone in a building; they are designed to
be used in concert with the Delta System Controllers or System Managers. The
Application Controllers do not have a Real Time Clock (RTC), battery back up, or an EIA-
232 serial port. They are fully programmable and may support a BACnet MS/TP subnet.
All of these products come with a housing.
DAC-606
The DAC-606 has 6 Universal Inputs and 6 Binary Outputs (0.5 Amp Triac).
DAC-633
The DAC-633 has 6 Universal Inputs, 3 Analog Outputs (0-10 Volts DC), and 3 Binary
Outputs (0.5 Amp Triac).
DAC-T305
The DSC-T305 is a Room Controller that comes with an Internal 10K Thermistor, 3
Universal Inputs, and 5 Binary Outputs (0.5 Amp FET). It can be ordered with a
variety of keypad configurations. It also has a programmable 3 line, 36-segment LCD
display.
Options:
Can be ordered with various keypad configurations

- 10 -

DAC-V304
The DAC-V304 is a Binary VAV Controller. It has an Internal True Differential
Pressure Sensor, 3 Universal Inputs, and 4 Binary Outputs (0.5 Amp Triac). This
controller comes with an Integrated housing for the optional actuator. You can also
order this packaged with actuator feedback if required.
Options:
DAC-V304: base model with no actuator
DAC-V304A: includes actuator
DAC-V304AF: includes actuator with feedback
DAC-V322
The DAC-V322 is an Analog VAV Controller. It has an Internal True Differential
Pressure Sensor, 3 Universal Inputs, 2 Analog Outputs (0-10 Volts DC) and 2 Binary
Outputs (0.5 Amp Triac). This controller comes with an Integrated housing for the
optional actuator. You can also order this packaged with actuator feedback if
required.
Options:
DAC-V322: base model with no actuator
DAC-V322A: includes actuator
DAC-V322AF: includes actuator with feedback

DAC-304
The DAC-304 is a Binary VVT Controller. It has 3 Universal Inputs, and 4 Binary
Outputs (0.5 Amp Triac). This controller comes with an Integrated housing for the
optional actuator. You can also order this packaged with actuator feedback if
required. This controller is well suited for VVT or other pressure dependent
applications.
Options:
DAC-304: base model with no actuator
DAC-304A: includes actuator
DAC-304AF: includes actuator with feedback

DAC-322
The DAC-322 is an Analog VVT Controller. It has 3 Universal Inputs, 2 Analog
Outputs (0-10 Volts DC) and 2 Binary Outputs (0.5 Amp Triac). This controller comes
with an Integrated housing for the optional actuator. You can also order this

- 11 -
packaged with actuator feedback if required. This controller is well suited for VVT or
other pressure dependent applications.
Options:
DAC-322: base model with no actuator
DAC-322A: includes actuator
DAC-322AF: includes actuator with feedback
Delta Field Modules
The DFM series of products are designed to reside on Deltas LINKnet network and
provide remote I/O for the SYSTEM or SUBNET Level controllers. They can be
connected to a DSC/DAC subnet. The DFMs are not programmable, and do not have
algorithms in them.
Some Field Modules can be directly connected to a BACnet MS/TP network segment
(such as the DFM-200/400). When installed on BACnet MS/TP they have their own
device object and their objects may be read or written to using BACnet services. DFM
models with inputs only, will be permitted to reside on the BACnet MS/TP network.
When connected to a LINKnet network, Input and Output objects are created in the
DSC/DAC controller that is connected to the LINKnet network, and their value is an actual
representation of the DFM I/O status. The DSC/DAC controllers then program the virtual
I/O in GCL to control simple applications. Each DSC/DAC has a limited number of
LINKnet devices that it can support on the LINKnet network, depending on the specific
model of DSC/DAC.
DFM-200
The DFM-200 has 2 Universal Inputs and can reside on a LINKnet or BACnet MS/TP
network.
DFM-202
The DFM-202 has 2 Universal Inputs and 2 Binary Outputs (0.5 Amp Triac) and can
reside on a LINKnet network.
DFM-220
The DFM-220 has 2 Universal Inputs and 2 Analog Outputs (0-10 Volt DC) and can
DFM-400
The DFM-400 has 4 Universal Inputs and can reside on a LINKnet or BACnet MS/TP
network.
DFM-404

- 12 -
The DFM-404 has 4 Universal Inputs and 4 Binary Outputs (0.5 Amp Triac) and can
DFM-440
The DFM-440 has 4 Universal Inputs and 4 Analog Outputs (0-10 Volt DC) and can
Delta Network Thermostats
A Delta Network Thermostat is any networkable temperature sensor with I/O built onto it.
These products communicate on a BACnet MS/TP network at 76.8 Kbaud. They do not
support a BACnet MS/TP or LINKnet subnet.
DNT-T305 (Digital Room Controller)
The DNT-T305 is a fully programmable Room Controller. You can create customized
object databases and programs. It comes with an internal 10K Thermistor, 3 Universal
Inputs and 5 Binary FET outputs. The outputs can either source 24 VAC directly from
the controller or they can switch an external 24 VAC source.
DNT-T103 (Digital BACstat II)
The DNT-T103 is a field-selectable, fixed algorithm controller. It comes with a fixed
object database and you can field-select 6 different control strategy algorithms. The
available algorithms for this controller are VAV, VVT, Fan Coil, Heat Pump, Unit
Heater, and Reheat/Radiation. Setting the algorithm to NONE allows the I/O to be
controlled from another device.
This controller comes with an internal 10K Thermistor for measuring space
temperature, 1 Universal Input, and 3 Binary Outputs (0.5 Amp Triac). The binary
outputs can be configured for Pulse Width Modulation, Time Proportioned signal for
analog operation of various actuators, or floating point.
The BACstat IIs have a password protected Configuration Menu used to configure
the stats network properties and algorithm. It also has a Service Tool mode with
advanced Air Balancing functions for use with the VAV algorithm. All of these
properties can be accessed through the LCD interface, or set through variables in the
controller database.
DNT-T221 (Analog BACstat II)
The DNT-T221 is a field-selectable, configurable, fixed algorithm controller. It comes
with a fixed object database and you can field select one of 5 different control strategy
algorithms: VAV, VVT, Fan Coil, Unit Heater, and Reheat/Radiation.
This controller comes with an internal 10K Thermistor for measuring space
temperature, 2 Universal Inputs, and 2 Analog Outputs and 1 Binary Triac Output.

- 13 -
The binary output can be configured for Pulse Width Modulation or a Time
Proportioned signal for analog operation of various actuators.

- 14 -
Delta Network Sensors
These products are networked temperature sensors without I/O built into them. All of
these products can reside on either the LINKnet or SUBNET level of our network
architecture. These products can communicate on a BACnet MS/TP network at 76.8K
baud.
DNS-14 (BACstat I)
The DNS-14 has a 3 digit LCD display, and has 4 programmable buttons typically
used for occupancy and setpoint adjust. This product is powered with 24 VAC Class
II.
DNS-24 (BACstat II)
The DNS-24 has a 96 segment LCD display with backlight option, and has 4
programmable buttons typically used for occupancy and setpoint adjust. This product
is powered with 24 VAC Class II.
I/O Application Guide
Input Types
Universal Inputs
Universal Inputs can be jumper selected for use with 10K ohm Thermistors, 4-20 mA,
0-5 VDC, or 0-10VDC.
You can use these inputs for monitoring temperatures, humidity, dry-contacts, voltage
signals from current sensors etc. All of the measured signals can be converted to
appropriate engineering values through scale ranges in the controller.
Supervised Inputs
The Access Door Module (ADM-2W704) has Supervised Inputs. Supervised Inputs
are inputs that always have monitoring current passing through them, even if they are
monitoring a dry contact. This is a security measure, used to ensure that the wire is
not tampered with in any way. There are several different types of supervised inputs
depending on how the contact is wired. For more detail please read the ADM-2W704
documentation.
Output Types
Analog Outputs

- 15 -
Analog Outputs are all 0 to 10 Volts DC and can source up to a maximum of 20 mA.
These outputs can be used to drive actuators, solid-state relays and to provide control
signals to miscellaneous equipment.

Binary Triac Outputs
Binary Triac Outputs can switch 24 Volts AC only, up to a maximum of 0.5 Amps.
They cannot switch DC voltages. These output types are typically used to switch
external 24 VAC control relays. Due to leakage current inherent in Triacs these
outputs should not be used to switch any solid-state controls circuitry. For example
you should not use Binary Triac Outputs to provide drive enable indication to Variable
Frequency AC drives. The leakage current may provide ON indication when you
may have the output OFF.
Binary FET Outputs
Binary FET Outputs can switch 24 VAC or 24 VDC. They can switch a maximum of
up to 0.5 amps. These Outputs can be used with external 24 VAC control relays or
solid state controls circuitry.
Relay Outputs
The Access Door Module (ADM-2W704) has 4 Relay Outputs, and is designed to
switch 24 VAC.
Lighting Hardware
DLC-G1212 (GE Relay Lighting Controller)
The Delta Lighting Controller (DLC-G1212), is a fully programmable native BACnet
lighting controller designed to be used with General Electric RR style relays.
Schedules can be created and modified directly in the controller and sequences can
be customized using GCL+ programming. The DLC-G1212 supports monitored,
hardwired switches. These local switches do not require any programming to turn on
the relay it is wired to. The hardware can sense when the local switch has been
depressed and this information can be used during flick warning sequences. The
controller has a hardwired, relay on/off sequencer. This sequencer can be relayed to
multiple boards by simply wiring the Sequencer Out of one board to the Sequencer
In of the next board.
Access Hardware
ADM-2W704

- 16 -
The Access Door Module (ADM-2W704), is a LINKnet device that is specifically
designed as an Access Controller. It can not be connected directly onto a native
BACnet MS/TP network, it resides on the LINKnet network underneath an Access
System Manager (ASM-24). The board comes with two Wiegand Interface ports,
seven Supervised Inputs (Type 0,1,2,3,4), and four Binary Relay Outputs (5 Amps @
24V AC/DC). The Door Module can support a battery back up using a 7A-H battery
connected directly to the controller itself.
Controller Firmware
Standard Features
Native BACnet
Delta Controls ORCA Hardware is native BACnet and supports peer-to-peer data
communications between BACnet/IP, Ethernet, BACnet MS/TP and BACnet PTP
networks.
HVAC, Lighting and Access Integration
All of these products can reside on the same network segments. Several proprietary
objects were created for the Access Controllers that all of the HVAC System Controllers
could utilize in their customizable programs.
System Controllers and Application Controllers
Flash-Loadable
When connected together using the BACnet MS/TP protocol over EIA-485, Delta System
and Application Controllers can have their firmware upgraded without disconnecting them
from an active network. This provides the customer with timesavings when upgrading an
existing Delta ORCA network to gain features added in the future.
Real-Time Programming
All Delta System Controllers and Application Controllers support dynamic real-time
programming using GCL+. These programs reside in the specific controllers and when
viewing the program dynamic data is available simply by hovering over the object name.
When changes are made to the program, it is instantly modified and updated in the
controller as soon as OK or APPLY are pressed in the GCL editor. These features
make programming and troubleshooting very efficient.

- 17 -
Field Modules
Field Module firmware comes in two varieties; native BACnet MS/TP and LINKnet. The
DFM-200 and DFM-400 are able to reside on any BACnet MS/TP network at up to 76.8
Kbaud or they can reside on the LINKnet network. They are used for remote monitoring
and to reduce negative impact on network performance, the controllers support Change-
of-Value (COV) data exchange. When connected to the BACnet MS/TP network each
DFM-200/400 is presented with its own Device object and database. When connected to
the LINKnet network the controller objects will reside in the System/Application Controller
that they are sub-networked to.
The DFM-202/220 and DFM-404/440 can only be connected to the LINKnet network.
Their inputs and ouptuts are created as virtual objects in the System/Application controller
that they are sub-networked to.
Door Modules
The ADM-2W704 is a LINKnet device. It must be connect to the ASM-24 (Access System
Manager). The Door Modules I/O is created as virtual objects in the System
Manager/Controller that they are sub-networked to.

- 18 -
Hardware Architecture
The ORCA Hardware architecture is based on a hierarchical design. This allows for
simple and efficient communications in large Wide Area Networks and small stand-alone
systems. The ORCA architecture is extremely flexible and can be built up in a variety of
configurations.
Architecture Design
There are four levels to the ORCA hardware architecture: AREA level, SYSTEM level,
SUBNET level, and LINKnet level. AREA Level controllers are primarily used to break-up
large segments of a WAN. There is one controller that can be used as AREA Level
controller;
DSM-050
SYSTEM Level controllers are used to logically distribute networks into manageable
building segments. SYSTEM Level Controllers are I/O controllers for major equipment
systems such as AHUs. SYSTEM Level controllers have Real-Time Clocks, EIA-232
serial ports, and battery back up. This will allow the individual segments to function
normally if network cabling is damaged and communications between SYSTEM Level
controllers is not possible or interrupted. Only DSC and DSM model controllers can be
placed at the SYSTEM Level. Any DSC model can have a subnet of controllers beneath
it. DAC model controllers cannot be installed in the SYSTEM Level.

- 19 -
AREA Level
SYSTEM Level
SUBNET Level
LINKnet Level

Derived Network Addressing (DNA)
Derived Network Addressing, or DNA, is a product addressing method that Delta Controls
has developed in order to make addressing controllers as simple as possible. When
dealing with large networks there are many technical addressing properties, such as MAC
(Medium Access Control) Address and Network Numbers, that have been automated, in
order to make installing a network as efficient as possible.
Controllers connected to the subnet of a controller higher up in the architecture will inherit
the higher controllers address as part of its own. At the same time, individual network
numbers will be assigned to it from the higher controller. The MAC address is
automatically inherited from the physical address of the controller.
The format of any controllers address will be AAASSDD. AAA is the address component
inherited from the AREA Level controller directly above it in the architecture (if an AREA
Level controller does not exist then it will be 000 by default). SS is the address
component inherited from the SYSTEM Level controller directly above it in the
architecture. DD is the address component of the individual device in the SUBNET Level
of the architecture.

- 20 -
AREA Level
SYSTEM Level
SUBNET Level
Physical Address: 1
DNA Address 10000
Physical : 1
DNA: 10101
Physical Address: 1
DNA Address 10100
Physical Address: 2
DNA Address 10200
Physical Address: 3
DNA Address 10300
Physical : 2
DNA: 10102
Physical : 3
DNA: 10103
Physical : 4
DNA: 10104

The individual address components are determined from the physical address of the
controller. Most controllers set their physical address from the DIPswitch on the controller.
If the controller has an LCD/LED screen then the address is set via the keypad. When
using the DNA scheme the controllers have a physical address range of 1 to 99.
DNA can be disabled in each controller. Software addressing can assign any address
within the allowable range specified by BACnet (0 to 4,194,302). This feature allows
integration with other vendors products easily, when required.

- 21 -
Typical Architectures
Deltas ORCA systems are designed to support a variety of architectures all with Deltas
vision (Integrated Facility Management Solutions. Simplified!) as a guiding focus.
LINKnet
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
ic
a
t
in
g

@

7
6
.
8

K
b
a
u
d

B
A
C
n
e
t

M
S
T
P
N
e
t
w
o
r
k

(
N
E
T
2
)
DSC-1212
Device 100
DAC-606
Device 101
DNS-24
Object created virtually in
Device 101
System Level
Subnet Level
LINKnet Level
DFM-202
Device 101

This diagram shows a typical network architecture. In this case, two LINKnet devices are
connected to a DAC-606. The I/O objects on the LINKnet devices are created in the DAC
controller. The DAC has GCL programs that read the Inputs and control the Outputs
depending on the GCL strategy. LINKnet provides simple, expansion I/O for the DAC
controller.
LINKnet devices are always connected to the NET2 port of the DAC controller. The
LINKnet objects in the DAC are addressed based on the physical address of the LINKnet
board and the object instance that you are referring to. For example to create a reference
to Analog Input 1 on LINKnet device 2, in the DAC controller you would create Analog
Input 201. To create a reference to Analog Output 3 on LINKnet device 4, in the DAC
controller you would create Analog Output 403. The first digit of the LINKnet object
represents the physical LINKnet device number and the two digits following represent the
specific object instance number on that LINKnet device.

- 22 -
BACnet MS/TP

S
e
c
o
n
d
a
r
y

B
A
C
n
e
t

M
S
T
P
N
e
t
w
o
r
k

(
N
E
T
2
)
S
e
c
o
n
d
a
r
y

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k

(
N
E
T
2
)
S
e
c
o
n
d
a
r
y

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k

(
N
E
T
2
)
S
e
c
o
n
d
a
r
y

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k

(
N
E
T
2
)
Primary BACnet MS/TP Network (NET1)
DSC-1212
Device 100
DSC-T305
Device 200
DAC-606
Device 101
DLC-G1212
Device 102
DNT-T103
Device 103
DNT-T103
Device 203
DNT-T103
Device 303
DAC-T305
Device 201
DAC-T305
Device 202
DLC-G1212
Device 302
DAC-606
Device 301
DSC-633
Device 300
DAC-633
Device 401
DSC-1280
Device 400
System Level
Subnet Level

This network architecture shows that the primary network between system controllers can
be BACnet MS/TP @ 76.8 Kbps. The primary MS/TP network must be connected to
NET1 of the System Level controllers. SUBNET Level controllers are connected to the
NET2 port of the System Level Controllers. LINKnet devices are connected to the NET2
port of the SUBNET level devices. The only DSC models that cannot currently support this
architecture is the DSC-1616EX, and the DSM-050.

- 23 -

Ethernet BACnet MS/TP

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
BACnet MSTP Network
Ethernet
System Level
Subnet Level
LINKnet Level
DSC-1616E or
DSC-1212E or
DSC-1280E or
DSC-1616EX
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
i
c
a
t
i
n
g

@

7
6
.
8

K
b
a
u
d
DNS-24
DFM-202
DSC
DACs
DAC
DAC
DSC DSC

This architecture illustrates the flexibility of the Delta ORCA Native BACnet control system.
Here, two SYSTEM level controllers have the Ethernet option. This allows them to route
from Ethernet to BACnet MS/TP at both the SYSTEM Level (NET1 MS/TP port) and the
SUBNET Level (NET2 MS/TP port).

- 24 -

BACnet/IP

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
i
c
a
t
i
n
g

@

7
6
.
8
K
b
a
u
d
Ethernet Network Segment Ethernet Network Segment
Router
B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
i
c
a
t
i
n
g

@

7
6
.
8

K
b
a
u
d
Area Level
Subnet Level
LINKnet Level
System Level
DSM-050 DSM-050

This architecture shows how the DSM-050 can be used to route information across Internet
routers. The DSM-050 has BACnet/IP protocols and can send data across a WAN, Intranet, or
Internet network to another DSM-050. The DSM-050 is required to have a unique IP address on
the network and when the two DSMs know each others IP addresses, the two network segments
can communicate with each other.

- 25 -

Operator Workstation Connections
B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
Ethernet
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
i
c
a
t
i
n
g

@

7
6
.
8

K
b
a
u
d
DNS-24
Device 101
DFM-202
Device 101
Workstation
Laptop computer
IBM Compatible
Modem
BACnet MSTP connection
through the Service Port
using Delta's CON-768
(EIA-232 / EIA-485 Converter)
Laptop computer
Laptop computer
INTERNET
Workstation
This diagram shows the possible workstation connections. A distinctive connection point
is the BACstat Service Port. Using Deltas 232/485 converter (CON-768) you can connect
any laptop running ORCAview software to the BACstat Service Port and see the entire
Delta Controls Network. This simplifies commissioning and troubleshooting, allowing the
Engineer to connect his workstation through a BACstat near the problem area.
There are also several standard connection points such as EIA-232 ports using BACnet
PTP, directly or through a modem.
ORCAview connects directly to the Ethernet network through a Standard Ethernet
Network Interface Card connected to the ORCAview PC.

- 26 -
There is a service port on most Delta ORCA hardware. This service port supplies power
to the EIA-232/485 converter so that the operator does not have to provide a separate
power supply for powering the converter.
It is also possible to use ORCAview to connect to the network across the Internet using
BACnet/IP protocols
ACCESS Control System
Introduction
The Delta Controls Access Control system is an Access Management system that
integrates seamlessly with existing Delta Controls installations Inc. HVAC and Lighting
Controllers. Like all of Delta Controls products, the Access Control Management system is
native BACnet, giving the building owner the flexibility of interoperability with other BACnet
products in his facility. Delta Controls offers a cost-effective access control solution since it
can be easily added to existing HVAC installations, without the need for additional
software, hardware, or networking infrastructure.

The Delta Controls Access Control system is designed for installations of up to 24 card
readers and 2200 individual card users per Access System Manager (ASM). Targeted
installations will be institutional and small to medium-sized commercial facilities.

Delta bundles all the basic functions of access control into an easy to learn system. In its
simplest form, the access control management system grants or denies entry to an
individual user for a specific door. The control decision is based upon identifying the user
and determining that specific users access privileges. We identify the user based on one
or more of the following:
1. A card number read by a card reader (proximity or mag stripe).
2. A PIN entered at a keypad.
3. Biometric information (fingerprint, hand geometry, retina scan etc.).
Once a user has been identified, his access profile is checked to determine whether
access can be granted. Access is granted based on one or more of the following access
criteria:
1. The specific door the user is attempting to get access to.
2. Time of day and day of week.
3. The access groups the user belongs to.
4. The current status of the door (operator controlled, unlock inhibit, etc).
Once the user has been identified, and the access conditions have been met, the door
that the user is requesting access to will be unlocked.
In most installations, there are common doors that will remain unlocked during regular
business hours. In this situation, the door can be unlocked from a time schedule.

- 27 -
Alternatively, a schedule can be attached to a door to prevent it from being unlocked
during specified hours. Doors may also be manually locked or unlocked by the operator,
this manual override is given a higher priority than either individual access (i.e., card
swipe) or scheduled control.

- 28 -
Access Control Database Objects
Several Access Control specific objects have been created by Delta Controls as
proprietary BACnet objects for use with the ORCA Native BACnet Control system. The
objects and their descriptions are as follows:

Card User The Card User object is used to identify an individual user. This object holds
the access privileges for the user as well as employee and personal information that may
be of interest.

Access Group Each card user belongs to one or more access groups. An access
group defines the rights and access privileges of a common group of users.

Door Controller This object defines a specific door in the system. It specifies the related
components of the door that are used for control, such as door contact input, door strike/
mag lock output, Request to Exit input, card reader, etc.

Door Group A door group lets you group a number of related doors together.

Card Reader This object defines the physical attributes of the card reader.

Access Setup The Access Setup object details various setup parameters specific to
access control applications.

Elevator Controller This object defines a specific elevator in the system. It specifies the
related components of the elevator that are used for control, such as card reader, keypad,
door contact, call button, emergency button, etc.

Access Event Log The Access Event Log is used to log all of the events related to
access control. This includes events that aren't defined by the Door or Elevator
Controllers, such as Time Change and Reset Events.

Access Control System Features
Several features have been implemented in Deltas Access Control system.
Seamless Integration with ORCAview
The Access Control system integrates with Deltas front-end operator workstation software
ORCAview. This allows the operator to create system graphics that interface directly with
HVAC, Lighting, and Access Control objects making for a simple, easy-to-use interface.
All of the database objects are created with a similar look and feel as the other ORCA
systems objects, giving the user an easy-to-learn, intuitive interface.

- 29 -
Card Holders
The Access Control system is expandable from 500 individual card users. With the
Access System Manager, ASM-24, 2200 individual card users can be created. Each
card user can have one or multiple cards. Data specific to each card user can be
stored in an ODBC database. This data can include things such as phone number,
address and picture.

Wiegand Device Support
Each Door Module, ADM-2W704, can support two individual Wiegand output devices.
These devices can be card readers, keypads, biometric devices or any other Wiegand
output device. If twelve Access Door Modules are connected, the system will support
twenty-four Wiegand devices. These Wiegand devices can support card only, pin only or
card & pin operation. The Delta Card Reader object has adjustable Wiegand formats that
can be configured to support any Wiegand format up to 64 bits.
Card Formats
The system allows multiple card formats to be used. It supports 26 bit and one custom
format on a single card reader. The card formats are selected from within the Card Reader
object.
Combo Keypad
The Delta Access Control system now supports the AWID Combo Keypad on a single
Wiegand Port. Keypads can be used in combination with a card reader, or on their own.
When used in combination with a card reader, a valid card swipe must be accompanied
by a valid PIN entry. When used standalone, the keypad essentially takes place of the
card reader, and the user need only enter a valid PIN code to gain access. These options
are selected from within the Door Controller object.
User Database
There is no hard restriction on the number of User Access Groups that can be created in
the Delta Access Control system. Each card user can be assigned to as many as four
access groups, and every access group can have an unlimited number of doors or door
groups assigned to it.
Event Reporting
Access control events are generated when any access control activity takes place. An
access control event includes valid access attempts, where the cardholder gains access to
the door, as well as invalid access attempts, where the cardholder is denied access. For
each event we record the cardholder name (if known), access time and access door.
Events are configurable door by door. Events are stored in a local Access Event Log

- 30 -
(AEL1), which is automatically created. The number of events stored in the event log
defaults to 100. The maximum number of events that can be stored in the AEL is 2000.
Events may be directed to a larger event log on the PC.
Historian
Historian is used to
Reporting
There is a new Reporting aspect of the OWS, which will allow you to view live reports
looking for card number, etc.
Alarms
Alarms are generated when a potential breech of security has occurred. This may require
action by an operator or security personal. These include circumstances such as someone
trying to use a card reported lost or stolen, an anti-passback violation, forced entry of a
locked door, etc. Unlike events, an alarm will pop up a window in the operator console,
which forces the operator to acknowledge the alarm. Alarms are stored in a local event log
(EVL1), which is automatically created and can be redirected to a larger event log on the
PC. Operators can specify on a per door basis which types of alarms will be generated.

Anti-Passback
Using the Door Group objects anti-passback support can be set up. There are three types
of anti-passback supported in the Delta Access system, hard, timed and soft. Hard anti-
passback is a mechanism that prevents an employee/user from entering a zone and
passing his card back so that another person may use it to gain entrance to the same
zone. In order to open a door to that area again, the user would first have to swipe their
card at an exit door to that zone. Timed anti-passback prevents the user from re-entering
the zone without first exiting for the time period set using the software. After that period
has elapsed, the user can reenter the zone. Soft anti-passback does not prevent the
cardholder from re-entering the space; it alerts the software interface that the event has
occurred.
Flexible Door Control
Doors can be scheduled to be open or locked based on pre-defined schedules. The
system operator can also manually override schedules. The system also includes a
feature where a door could be scheduled for unlocked operation but will not unlock until
the first person at the door swipes their card.
Doors may also be controlled in Lock/Relock mode. In this mode, a valid card swipe
causes the door lock to change state (i.e., locked door becomes unlocked, unlocked door
becomes locked). This mode of operation allows a cardholder to completely control the

- 31 -
locked state of the door. This is useful for private offices; conference rooms or any other
space in which the time the door remains unlocked does not follow a fixed schedule.
It is also possible to define a card user with disabled access, which will allow the door
contact to be open for a longer period.
Visitor and Temporary Card users can be assigned in the system by setting an activation
and/or expiry time and date for the card.
Elevator Control
Elevator Control is used to control the movement of people via an elevator to various
floors and sections of a building. Elevators can be controlled in much the same way as a
door, which is explained above. It does however have a new Elevator Control object,
through which to define the specifics of that elevator. The elevator also has the same
options for input devices as the door. Anti-passback is one function, which will not be used
in Elevator Control.
Degraded Mode
If the ADM-2W704 looses communication with the Access Controller, it can operate in
Degraded Mode. When in degraded mode, only the site code of the card is used to
validate the cardholder. If the site code of a swiped card matches one in the site code list
of the Access Setup object then the card is valid. Degraded mode can be turned on or off
on a door-by-door basis.
Hardware Standards
The Door Module is being approved for UL294 and FCC (pending).
Object Replication
Phase 1 of Access Control was limited to 24 doors, as there was only one ASM (brain) on
the network. This was because there was no facility to keep users, access groups, etc. up
to date across more than one controller. Object Replication allows you to replicate
selected or all objects across chosen controllers. Any changes in an object on one
controller will be updated on all associated controllers. This includes information within
objects such as the Card User object, the Access Group object, the Schedule object, etc.
Easy Integration
The Delta Controls Access Control system integrates seamlessly with existing Delta
Controls Inc. HVAC and Lighting Controllers. Like all of Delta Controls products, the
Access Control Management system is native BACnet, giving the building owner the
flexibility of interoperability with other BACnet products in his facility. Delta Controls offers
a cost-effective Access Control solution as it can easily be added to existing HVAC

- 32 -
installations, without the need for additional software, hardware, or networking
infrastructure.

System Architecture
Hardware
The Access Control System is assembled using a minimum combination of two
controllers, one of each type below. The system can be expanded to accommodate more
doors by adding more Door Modules.
Access System Manager (the central controller of the Access Control
System).
Door Module (the I/O of the Access Control System).
The Access System Manager is the master device to the Door Module. It contains all the
representations of I/O from the Door Module, and is where the Access System is set up
and programmed. It has no I/O, but contains the I/O software objects, networking,
programming, setup, processing, and memory for the Access Control system. The base
memory of the controller is 512 kilobytes. The Access Controller can be purchased with
an optional Ethernet port to allow the access system to reside on an Ethernet backbone.
The Access System Manager address can be configured using Delta Controls Derived
Network Addressing (DNA) similar to our other HVAC/Lighting Controllers to create a
logical view of the network.
The Door Module is the I/O for the Access Control System. It has the hardware I/O to
control and monitor 2 doors. There are two Wiegand ports on the Door Module for
connecting Card Readers/Keypads. This means that each door can have one input
device if you want to control two doors off a Door Module. If you want to use an entry and
exit card reader/keypad then you need to use a Door Module for each door you would like
to control.

- 33 -

Exa
mpl
e
Use
s of
Sin
gle
Doo
r
Mod
ule

1 - Door Module
1 - Door Prox Card and
Keypand
1 - Door Module
1 - Door Entry Prox Card
and Exit Prox Card
1 - Door Module
2 - Door Prox Card &
Keypad (AWID)
1 - Door Module
2 - Door Prox Card only
Enter Exit

- 34 -

Each Door Module has built in power management that provides monitoring of AC Power
and Battery Power if used. A Battery charging circuit for a 7 aH battery is also included.
The Battery backup is intended to be backup power for both the controller and the door
controls (electric strike, mag lock, card reader, etc.). The Door Module is designed to
make wiring of a door easy and neat. All the power and interlocks are hardwired on the
board for ease of installation.
The inputs on the Door Module can be supervised if desired. Supervision of the inputs is
selectable from any of the industry standard types (Type 0,1,2,or 3).
Firmware
Both the Access System Manager and the Door Module have on board firmware for
operation. The Access System Manager firmware can be upgraded by using the Flash
Loader. This allows easy upgrading of the Access System Manager to new versions in
order to take advantage of improvements/enhancements to the Access Control System.
The Door Module firmware cannot be upgraded using the Flash Loader and therefore
cannot be field upgraded. Since the Door Module is the I/O portion of the Access Control
system, the firmware will not need to be upgraded.
The core of the Access Control system is built on top of the BACnet specifications and
proven Delta Controls HVAC controller firmware using the BACnet Standard. Proprietary
objects have been implemented for the Access Control System objects using the BACnet
standards for objects. Some of the objects used in the Access Control System are the
same BACnet objects in our HVAC firmware (SCH, CAL, BO, etc).
The front-end software required to program, commission, and monitor the Access Control
System is the same existing HVAC software ORCAview. The software can be used with
little or no modification depending on the application you wish to install on the Access
Control System. ORCAview is the same BACnet software for the HVAC and Lighting
making Integration and operation for end users very easy.
System Assembly
The Door Module cannot be used on a stand-alone basis unless operating in degraded
mode. It must be under the control of the Access System Manager as it is the I/O portion
of the Access Control System. The Door Module is connected to the Access System
Manager that it is under, via Delta Controls proprietary RS-485 communication standard
LINKnet. Each Access System Manager can support up to 12 Door Modules being
connected on the LINKnet port to control a maximum of 24 doors off a single controller.
You can substitute either the DAC+ or the DSC for the Access System Manager. Using
either of these replacements, you will be restricted to 2 Door Modules controlling a
maximum of 4 doors. ORCAview 3.30 will allow the networking of the Access System
Managers to control more doors. Any number of HVAC/Lighting controllers can be
connected to the Access Control System to control the integrated Access Control, HVAC
and Lighting system from the ORCAview front end software.

- 35 -
Object Replication, as mentioned on page 29, ensures that all Card User objects, Access
Group objects, etc are updated across the entire Access Control network.

- 36 -
Each of the various controllers has certain restrictions and is only good for certain types of
Access Systems. The restrictions are listed below:

Controller # Of Card Users Supported # Of Door Modules Supported
ASM 2200 12
DSC 500 2
DAC + 500 2

- 37 -
System Architecture Topologies
24 Door Access Control System

ORCAview
RS232/RS485
or
Ethernet
Note: When using RS485 you
need RS485 Converter for the PC.
Access System
Manager
Access Door
Module 1
Access Door
Module 11
Access Door
Module 12
......
The ASM-24 supports up to 12
Door Modules off its LINKnet
port.
.......

- 38 -
Small Size Integrated Access Control System

ORCAview
Ethernet
Access Door
Module 1
System Controller -
DSC1212
......
The System
Controller supports
up to 99
Controllers, each
which can control
two Door Modules.
.......
LINKnet
MS/TP
VAV Controller
VAV Controller
Access Door
Module 2
Access Door
Module
Access Door
Module
Access Door
Module
Access Door
Module
Entrance Doors Controls
Indoor Office Controls
LINKnet
LINKnet
LINKnet
DAC Plus
Historian
(optional)

- 39 -
Medium Size Integrated Access Control System
OrcaView
MS/TP
MS/TP
MS/TP MS/TP
Note: When using MS/TP
connection you need a RS485
Converter for the PC.
System
Controller
Room
Controller
Lighting
Controller
BacStat II
LINKnet
LINKnet
BacStat II
System
Controller
LINKnet I/O
......
The ASM-24 supports
up to 12 Door Modules
off its LINKnet port.
.......
LINKnet
LINKnet
Access System
Manager
Access Door
Module 1
Access Door
Module 12
......
The ASM-24 supports
up to 12 Door Modules
off its LINKnet port.
.......
LINKnet
LINKnet
Access System
Manager
Access Door
Module 1
Access Door
Module 12

- 40 -
Large Size Integrated Access Control System
ORCAview
Ethernet
LINKnet
LINKnet
Access System
Manager
Access Door
Module
Access Door
Module
......
The ASM-24 supports up
to 12 Door Modules off its
LINKnet port.
.......
BacStat II
MS/TP
ORCAview
MS/TP
System Controller
Application Controller
Application Controller
LINKnet
LINKnet
Access System
Manager
Access Door
Module
Access Door
Module
......
The ASM-24 supports up
to 12 Door Modules off its
LINKnet port.
.......
MS/TP
MS/TP
VAV Controller
VAV Controller
Historian
(optional)

- 41 -
ORCAview Operator Workstation
ORCAview is Delta Controls Operator Workstation. It combines both simple to use
graphical front-end graphics with powerful, real-time system tools for advanced users.
ORCAview operates on Windows Platforms (Windows 95/98/ME/2000/NT) and
incorporates many of the ease-of-use characteristics of Windows, such as Right-Click
context sensitive menus, and F1 Help Menus.

ORCAview has a built-in object-oriented system navigation and operation tool, called
Navigator. Navigator has built-in real-time program editing capabilities for the controllers
programs, and can be used with Drag-and-Link technology with Deltas Graphic Editor,
ILLUSTRATOR.

ORCAview communicates using both standard BACnet network services and Deltas
INTELLI-sys protocols. This facilitates interfacing with third-party BACnet products as well
as Deltas legacy products. Using its built-in BACnet IP capability, ORCAview can
communicate on WIDE AREA NETWORKS, (WANs), which are connected over
INTRANETS or the INTERNET. ORCAview can also communicate on Ethernet LANs
(LOCAL AREA NETWORKS). Using BACnet PTP protocol, ORCAview can connect to
any DSC model controller over an EIA-232 connection, either directly or through a modem
for remote access.
Components
Navigator Viewer

- 42 -
Navigator is used to view the control system architecture in a simple and intuitive manner.
When you open Navigator, you are presented with a double pane view window. The left
pane is used to display the hardware controllers currently in the system, and the right pane
is used to view the individual objects that are resident in each of the pieces of hardware.
When viewing Delta controllers the architecture is shown in a DNA mode. That means
that the collapsible tree is shown with the Delta hierarchical architecture view. If any
AREA devices are on the network they are shown leftmost, then SYSTEM controllers are
shown beneath them in a collapsible tree, and finally SUBNET devices are shown
beneath each connected SYSTEM controller. This makes for easy viewing of large
networks.
The Navigator dynamically updates the network tree. When a new controller is added to
the network, the controllers device ICON appears in the tree in the appropriate location.
Every ICON is unique to the device or model of controller. If the controller has a unique
look then its ICON will match it; for example, the room controller (DSC-T305) icon looks
similar to the room controller hardware.
You can also define custom views that can be created based on descriptors or point types.
This is useful when you wish to see all of the objects associated with AHU1 on a single
screen.
The right pane is used to view objects located in a specific piece of hardware. For
example, when you click on Device 100 in the left pane the right pane will immediately
display Device 100s objects located in the right pane. The right pane has several different
views: Small ICON, Large ICON, List, and Detail. Detail view can also display live Real-
Time Data. When displaying real-time data the data refresh can be updated at various
intervals. The right pane can be filtered by simply clicking on the appropriate table header.
When you do the data will be filtered alpha-numerically in either ascending or descending
order.
Toolbar

The Toolbar is used to provide context-sensitive menus when using the ORCAview OWS.
For example when using the Illustrator, the toolbar is modified to include graphic editing
features and graphical palletes.

- 43 -

Illustrator

Illustrator is used to create, and edit graphics that provide a real-time interface to the
controllers connected to the ORCAview OWS. Illustrator comes with a graphic object
palette that can be easily added to. In order to create graphics you simply drag the
desired palette object to the graphic being edited, and then using our Drag-and-Link
technology, drag the controller object that you wish to be linked with, from Navigator, and
drop it onto the palette object on the graphic. As soon as you drop the Navigator object
onto the graphics palette object the link is created, no extra work is required.

- 44 -
When the graphics are in online mode, the data displayed is real and you can open any
object directly from the graphic. You can also put any object into manual mode and
change its value from the graphic.

Features
ORCAview OWS has an extensive feature list. These features create a simple, but
powerful tool for use as the front-end to your BACnet hardware.
Automatic Device Discovery of Delta and third-Party BACnet Devices
When devices are added to the network ORCAview will automatically update the network
tree without any operator action. The controllers objects from Delta controllers are loaded
as soon as the new device is detected. When third party devices are detected, their
objects are loaded as soon as their new device icon is clicked-on. This prevents third-
party BACnet hardware that has low network capabilities from negatively affecting system
performance when connected to the network.
Context Sensitive Help
When using the Delta ORCAview OWS you can open the context-sensitive help from
anywhere in the system, by simply clicking on the F1 function key on your keyboard.
Filterable Real-Time Data View
Objects in your Navigator right pane can display Real-Time Data at selectable automatic
refresh rates. This ensures that the operator has the most recent data possible when
looking at the network.
GCL+
GCL+ is Deltas proprietary programming language. It is English based line programming
and has several built-in features that make it one of the most powerful automation
programming languages available.
Live Data
When viewing a program in one of the controllers, live data is displayed in a tooltip
when you hover over the desired object descriptor. This feature is a great benefit
when troubleshooting program code. The operator can step through each line of
code using his mouse and he knows exactly what the value is and thereby knows
what should be happening in the program.

- 45 -
Live Program Modification
If the operator wishes to make a change to the program code, he simply opens the
program by double-clicking on the specific program object in the navigator right pane,
making the program change and then hitting the APPLY or OK button. As soon as
this is done, the program has been changed in the controller. There is no need to
stop the panels operation during this process.

Color Coded Syntax
The program text is color coded to assist the operator when viewing or editing the
program. Object descriptors are different colors than GCL functions, which are
different from numeric value or operators. These colors can be customized to the
operators preference.
Program Trace Elements
Each program has small green dots located on the left of the program code, which
indicate which lines have executed in the program. You can clear these traces and
get a fresh trace pattern by simply clicking apply.
Syntax-specific Help
There is context-sensitive help in GCL+ that the operator can access at any time by
simply placing the cursor at the problem area and then hitting the F1 key. This will
open a Help screen on the topic area. For example if the operator had the cursor on
an IF statement and pressed the F1 key, the HELP screen would open up to the
IFTHEN statement and provide instructions on its use.
Commandability from GCL+
When editing a GCL program the operator can command any object value by simply
right-clicking on the object and then selecting command and entering the appropriate
value. This is a valuable tool when troubleshooting and diagnosing system problems.
Custom View Folders
It is possible to create Custom View Folders in the Navigator. This allows the operator to
create his own system views. So instead of viewing an architecture-based view, the
operator could create System based views. Custom Folders could be created for each
system by entering specific descriptor wildcards such as AHU1* or AHU2*. Then when
the folder is opened all of the objects with AHU1 in their object name would be present in
the specific folder. These folders can be organized in the manner desired by the operator.

- 46 -
Device Object Renaming
ORCAview allows the operator to easily rename a single object or a group of objects.
When renaming a group of objects in a device the operator can replace a common piece
of the object name with something new (such as replacing AHU1 with AHU2 in all of the
selected objects). You can also prepend or append something to all of the selected
objects (for example you can select a group of objects and add AHU1 to the front or back
of all their object names). This feature simplifies the engineers life when creating
duplicate databases for multiple controllers. He simply creates one database and then
renames the entire object database with a few mouse-clicks.

Dynamic System Graphics
All of the graphics in the ORCAview OWS provide the operator with live real-time data that
is automatically refreshed at a selectable rate based on who the logged-in operator is.

Multi Trend Viewer
The Multi-Trend is Deltas custom BACnet trendlog viewer. It can view up to eight
individual Trend Logs and provides a host of features that make it a powerful way to view
data.
Drag and Drop Technology
Drag-and-Drop technology is a simple and easy-to-use method of both linking device
objects to graphic palette objects, as well as dragging reference objects into other object
properties (for example when creating an alarm point, you can drag the referenced object
into the appropriate field instead of typing the object name in).
Drag-and-Drop is also used for the Multi-trend viewer. You can easily drag one of the
eight possible BACnet trends onto the Multi-trend object and the link is automatically
configured.
Bitmap Graphics
ORCAview OWS incorporates the importing of bitmap, jpeg, and gif files into your
graphics. These images can be over-layed with dynamic data links.

WAV Files

- 47 -
ORCAview is able to play and link WAV Sound clips directly from the graphics. These
clips can be embedded into various graphic objects and can be used to add another
dimension to the front-end system.

Multiple Languages
ORCAview supports multiple languages. These languages can be selected from a drop-
down menu. Multiple Navigator windows, with multiple languages can be viewed at the
same time. Currently ORCAview supports 18 different languages plus 1 custom language
for site translation by the end user. Note that each time a custom language is created it
can be added to future software releases by Delta Controls.

- 48 -
ORCAweb
ORCAweb is a web-based front-end for use by both facility staff and tenants. It is a PC-
Based WEB Server that connects to both the building automation network and the facility
LAN. ORCAweb is based on a client-server architecture and the software has no software
limits on the number of simultaneous users. Based upon your access level you may view
graphics, device architecture, object properties, or tenant portal pages.
ORCAweb has several tenant functions that make it ideally suited for use in a large facility
with many tenants that are connected to the facility LAN. The tenant portal pages allow
each tenant to view a customizable web page that displays the status of the mechanical
and lighting systems that serve their office area. The Virtual Stat is a simple application
that resides on the Windows Tray. It allows the tenant to display their current space
temperature. When they double click the Virtual Stat icon a larger, more detailed user
interface is displayed. ORCAweb has a Navigator view that displays the current system
architecture and will allow the operator to manipulate properties on individual objects.
Components
Navigator

The ORCAweb Navigator is similar to the ORCAview Navigator in that it presents the
network of controllers in the left pane and the controller specific objects in the right pane.

- 49 -
The Navigator dynamically updates the network tree. When a new controller is added to
the network, the controllers device icon appears in the tree in the appropriate location as
soon as the browser is refreshed. Every ICON is unique to the device or model of
controller. If the controller has a unique look then its ICON will match it; for example, the
room controller (DSC-T305) icon looks similar to the room controller hardware.
The left pane contains additional features. There is an Alarms Folder, which contains all
of the active alarm information. There is also a link to the Delta Controls Corporate WEB
page and an email form which can be sent directly to Delta. The graphics folder is located
in the left pane. Clicking on the graphics folder will open a graphics navigation tree that
can be used to view various dynamic WEB graphics. There is a specific Third Party folder
that contains all of the controllers connected to the network. A Tenant Portal link is also
available. Clicking on this folder will open the login screen for the Tenant Portals.
The right pane is used to view objects located in a specific piece of hardware. For
example, when you click on Device 100 in the left pane the right pane will immediately
display Device 100s objects located in the right pane. The right pane is also used to view
dynamic WEB graphics

- 50 -

Tenant Portal

The Tenant Portal was created as a way to provide many end-users with their specific
objects of interest in a format that is both informative and easy to understand. Each user
can customize the presentation of information, including what AREA data they would like
displayed in their portal.
Every User has an Area assigned to him/her. An Area is defined as an association of
objects including Temperature, Temperature Setpoint, Outside Temperature, Lighting
Control, Equipment Calendar, Equipment Schedule, and a Trend Log. An Area can also

- 51 -
have additional equipment added to it. This allows for Areas that have more than one
piece of mechanical equipment serving it. When additional equipment is added to an
AREA, the new equipment will also have an associated Value, Temperature Setpoint,
Calendar, Schedule and Trend Log. A User can have more than one AREA assigned to
him. This could be used by office managers who wish to view many different Office
AREAS on a single screen.
Virtual Stat

The Virtual Stat is an application that resides on the Windows Tray. It will display a single
USER selected temperature; either Current Temperature, Temperature Setpoint, or
Outside Temperature. When the user double clicks on the Tray Icon Temperature a larger
interface is opened. This larger interface allows the operator to adjust the current
Temperature Setpoint. The user can pick between two different interfaces for their Virtual
Stat as seen below.

- 52 -
Topology Diagram
INTELLIview
PC Based WEB-Server
Remote Internet/Intranet Client
Native BACnet Hardware
Internet or Intranet
Network

It is possible for there to be many concurrent users when using Delta ORCAweb.
Concurrent Users are when more than one client is connected to the server at the same
time. The ORCAweb must be connected to the Controller Hardware by using an Ethernet
connection. The Server then in turn connects to the Client PCs using TCP/IP across the
INTERNET or an in-house INTRANET. When communicating across the INTERNET we
recommend that the architecture be set up using Firewalls. This will help prevent hacking
by unauthorized sources.
Delta ORCAweb uses a CLIENT / SERVER architecture. This means that no additional
software is required on the CLIENT PC other than the INTERNET browser (Internet
Explorer 5+, Netscape 6+ or Mozilla). The SERVER sends all of the web pages and data
to the CLIENT PC.

- 53 -

Network Architecture

B
A
C
n
e
t

M
S
T
P

N
e
t
w
o
r
k
L
I
N
K
n
e
t

N
e
w
t
o
r
k
c
o
m
m
u
n
i
c
a
t
i
n
g

@

7
6
.
8

K
b
a
u
d
Ethernet Network Segment Ethernet Network Segment
Router
PC Based WEB-Server

This drawing shows a typical WEB-server network architecture. ORCAweb connects to
the controls network through an Ethernet connection, and when a Client Workstation
connects to it, ORCAweb will send the data and graphics to the Client.
It is also possible to separate the client workstation network from the Delta Controls DDC
Network by placing two Ethernet NICs (Network Interface Cards) in the WEB Server PC.
One NIC would be for the external Client Workstations and the other NIC would be
connected to the Delta network.

- 54 -

Features
Real-Time Navigation
When using the ORCAweb Navigator the values in the object listing in the right pane are
loaded with live data when the device icon in the left pane is clicked or when the Refresh
Button is pressed.
Auto Listing of BACnet Devices
Whenever a new device is connected to the controller network, its device icon is
automatically placed into the left pane device tree. The operator does not have to update
any information in the system for this to occur. Both Delta and Third-Party Native BACnet
product are handled in this way making for seamless integration to Third-Party devices.
USER/GROUP Security Access
Delta ORCAweb utilizes a USER/GROUP user access scheme. A GROUP defines an
access level that would be used by a group of users or a single special case user. A
USER is then created and the proper GROUP is assigned to that USER. The USER can
have exceptions to the GROUP security access levels. For example, the USER may be
assigned to the Custodian GROUP, which does not have access to output objects. The
USER in this case may be required to turn off a single master light object (Binary Output
#27) in the system. In order to accomplish this, the USER can be given EDIT individual
access to Binary Output #27.

- 55 -

It is possible to restrict individual users from viewing the Delta ORCAweb Navigator. This
will force them into the Tenant Portal.
Object Editing
ORCAweb has been developed for use in systems that have already been engineered
and commissioned. As such the available access to object properties has been limited to
only those properties that would normally be modified under normal operating conditions.
The ability to place objects into Auto/Manual, enter Manual values, modify the Description
property, Calibrate values, and set the Commissioned property is allowed. If more
advanced modification of objects is required then you would use the ORCAview OWS.

- 56 -

Event (Alarm) Handling
Delta ORCAweb is able to receive BACnet events/alarms. When the alarms are received
by the system they are placed into the Alarms Folder in the Navigator Left pane. The
operator can open the alarms folder and acknowledge each individual alarm. When the
alarm is acknowledged and the alarm has returned to its Normal State, it is removed from
the Active Alarm List.

- 57 -

Event (Alarm) Notifications Email
If the User has an email assigned in his User information then he/she will also receive an
email notification when any of his/her subscribe alarms are received. The email
notification includes a URL link to the WEB server that when opened will link the operator

- 58 -
directly to the alarm folder. The operator can then acknowledge the alarm after logging
into Delta ORCAweb.
Graphics Folder
ORCAweb has been designed to make WEB graphic navigation as easy to set up as
possible. In order to create your graphic navigation tree in the left-hand pane you simply
copy your graphics into a specific folder location on the WEB server PC. When you create
the folders on the PC, folders are automatically created in the Left Hand Pane. This
makes it easy for operators to modify their graphics tree in seconds with no requirement
for HTML knowledge.

BMA (BACnet Manufacturers Association)

The following information is provided directly from the BACnet Manufacturers Association
(BMA) official web site http://www.bacnetassociation.org/ It is included to provide you with
accurate information regarding the purpose and function of the BMA as well as the
BACnet Testing Laboratories (BTL).
BMA
The BACnet Manufacturers Association (BMA) is an organization that will encourage the
successful use of BACnet in building automation and control systems through
interoperability testing, educational programs, and promotional activities. The BACnet
Manufacturers Association will complement the work of other BACnet-related groups
whose charters limit their commercial activities. BACnet Manufacturers Association
members will include companies involved in the design, manufacturing, installation,
commissioning, and maintenance of control equipment that uses BACnet for
communication, as well as other interested persons.
BMAs objectives are to:
Develop a BACnet conformance certification and listing program that will award
an interoperability mark to BMA compliant products and strongly enforce BMAs
trademarks. Testing procedures will be based on ASHRAE standards.
Establish a test lab to support compliance testing and interoperability testing
activities.
Promote interoperability and compliance with the BACnet Standard by developing
conformance testing software and organizing multi-vendor interoperability testing
activities.

- 59 -
Provide the latest information about BACnet technology and products through
educational events and a web site that displays listed products.
Market and promote the use of BACnet to consulting engineers, end users of
building automation equipment, and the building automation community at large.
This will include education and publicizing successful implementations.
Work with existing organizations to promote and improve BACnet, including:
ASHRAE BACnet Committee (SSPC 135), CEN/TC247, IEIEJ, BACnet
Interoperability Testing Consortium, BIG-AA, BIG-EU, BIG-NA, NEMA, NFPA,
and ISO/TC205.

BTL (BACnet Testing Laboratories)
The BACnet Testing Laboratories (BTL), which is part of the BACnet Manufacturers
Association (BMA), offers a product testing and listing program for products that have
BACnet capability. The BTL's authorized test laboratories will test the BACnet functionality
of a product to a set of requirements developed by the BTL that are based on ASHRAE
Standard 135.1P. Products that meet the BTL's requirements are eligible to receive a BTL
listing.
Products are submitted to the BTL by manufacturers, developers, or their recognized
representatives or licensees. The name under which a product is submitted, is the same
name that will appear on the product and in the official BTL listing in print and on the
BMA's web site.

Version 3 System Description - Jan14 - 03 PDF

Transféré par

Informations du document

Description originale:

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Version 3 System Description - Jan14 - 03 PDF

Transféré par

Droits d'auteur :

Formats disponibles

- 1 -

ORCA Native BACnet

Vous aimerez peut-être aussi