EBI R500.1 EBIOverview PDF

Enterprise Buildings Integrator
Overview
EBI-ZZDOC500-02
May 2016
Release 500
Document Release Issue Date
EBI-ZZDOC500-02 500 2 May 2016
Disclaimer
This document contains Honeywell proprietary information. Information contained
herein is to be used solely for the purpose submitted, and no part of this document or its
contents shall be reproduced, published, or disclosed to a third party without the express
permission of Honeywell International Sàrl.
While this information is presented in good faith and believed to be accurate, Honeywell
disclaims the implied warranties of merchantability and fitness for a purpose and makes
no express warranties except as may be stated in its written agreement with and for its
customer.
In no event is Honeywell liable to anyone for any direct, special, or consequential
damages. The information and specifications in this document are subject to change
without notice.
Copyright 2016 - Honeywell International Sàrl
2 www.honeywell.com
Contents
About this guide ........................................................................................................................... 7

The EBI documentation ............................................................................................................................ 8
Document availability .................................................................................................................. 10
Introduction to EBI ..................................................................................................................... 13
The versatility of EBI ............................................................................................................................... 14
Honeywell Security Manager ....................................................................................................... 15
Honeywell Building Manager ...................................................................................................... 15
Honeywell Life Safety Manager .................................................................................................. 16
EBI and Pharmaceutical Compliance ........................................................................................... 16
Architectural flexibility ............................................................................................................................ 17
EBI Cloud Connector ................................................................................................................... 17
Server redundancy ........................................................................................................................ 17
Distributed System Architecture .................................................................................................. 18
Point servers ................................................................................................................................. 19
Controller interfaces ..................................................................................................................... 20
Controller-to-server connections .................................................................................................. 20
Operator interfaces ................................................................................................................................... 24
Displays ........................................................................................................................................ 24
Station on mobile tablets .............................................................................................................. 26
HMIWeb browser ......................................................................................................................... 26
Honeywell EasyMobile ................................................................................................................ 26
Operator security ...................................................................................................................................... 28
Facility Model, Organization Model, and scope of responsibility ............................................... 28
Station security ............................................................................................................................. 28
Point control restrictions .............................................................................................................. 29
Electronic Signatures ................................................................................................................... 30
Exchanging data with other applications ................................................................................................. 31
Microsoft Excel Data Exchange ................................................................................................... 31
ODBC Data Exchange ................................................................................................................. 31
ODBC Driver ............................................................................................................................... 32
OPC .............................................................................................................................................. 32
Advanced customization capabilities ....................................................................................................... 34
Companion products ................................................................................................................................ 37
Honeywell Digital Video Manager .............................................................................................. 37
3
CONTENTS
Honeywell Energy Manager ........................................................................................................ 37

Understanding supervisory control .......................................................................................................... 38
About points ............................................................................................................................................. 39
Using EBI ..................................................................................................................................... 41
Responding to alarms and events ............................................................................................................. 42
Alarm shelving ............................................................................................................................. 43
Alarm groups ................................................................................................................................ 44
Managing operator response to alarms ........................................................................................ 44
Analyzing system data ............................................................................................................................. 45
Reports ......................................................................................................................................... 45
Trends ........................................................................................................................................... 45
Storing point history ..................................................................................................................... 46
Archiving point history and events .......................................................................................................... 47
Troubleshooting EBI ................................................................................................................................ 48
Using EBI for Security Management ......................................................................................... 49
Cardholder management .......................................................................................................................... 50
Cardholder information in the server database ............................................................................ 50
Integrated PhotoID ....................................................................................................................... 50
Reception Management ................................................................................................................ 51
Controlling building access ...................................................................................................................... 52
Server control of access ............................................................................................................... 52
Downloading access information to the field device ................................................................... 52
Managing alarms .......................................................................................................................... 52
Access control concepts ........................................................................................................................... 54
Card readers ................................................................................................................................. 54
Access points ................................................................................................................................ 54
Floor points .................................................................................................................................. 55
Zones ............................................................................................................................................ 55
Time periods ................................................................................................................................. 57
Access rights ................................................................................................................................ 57
Perimeter Global Anti-Passback .................................................................................................. 57
Occupancy reporting .................................................................................................................... 57
Cardholder reporting .................................................................................................................... 58
Using EBI for Building Management ......................................................................................... 59
Monitoring and controlling HVAC information ...................................................................................... 60
Scheduling ................................................................................................................................................ 61
Alarm paging ............................................................................................................................................ 63
Life Safety Management .......................................................................................................................... 64
Notices ......................................................................................................................................... 65
How to report a security vulnerability ..................................................................................................... 66
4 www.honeywell.com
CONTENTS
Support and other contacts ....................................................................................................................... 67

Training classes ........................................................................................................................................ 68
5
CONTENTS
6 www.honeywell.com
About this guide
This guide provides an overview of Enterprise Buildings Integrator (EBI). It describes

the concepts behind EBI, and describes the ways in which EBI can be configured to
meet your specific requirements.
7
ABOUT THIS GUIDE
The EBI documentation

The EBI documentation library includes the following documents in addition to this
guide.
Installation Guide
The Installation Guide describes how to set up server and client computers and install
the EBI components.
Access Control Configuration Guide

The Access Control Configuration Guides, one each for AXSS-II, FS90, IdentIPoint,
PCSC, Security Electronics, and Temaline, are primarily designed for engineers and
system administrators responsible for configuring and supporting an EBI security
system. It also includes operational information relating to Cardholder Management for
photo identification.
Import Export Guide

The Import Export Guide describes how to import and export cardholder data to and
from EBI.
Building Management Guide

The Building Management Guide is primarily designed for engineers and system
administrators responsible for configuring and supporting an EBI building management
system.
Configuration and Administration Guide

The Configuration and Administration Guide describes basic configuration tasks and
administration procedures. It is designed to be read in conjunction with the Advanced
Configuration Guide, the Access Control and Configuration Guide for your controller
type, and Building Management guides.
Advanced Configuration Guide

The Advanced Configuration Guide describes configuration tasks for the more advanced
features of EBI. Use this guide in conjunction with the Configuration and
Administration Guide.
8 www.honeywell.com
ABOUT THIS GUIDE
HMIWeb Display Building Guide

The HMIWeb Display Building Guide describes how to use HMIWeb Display Builder,
the tool used to create custom HMIWeb displays. (HMIWeb displays are based on Web
standards.)
Quick Builder Reference/Help

The Quick Builder Reference/Help describes how to use Quick Builder, the tool used to
configure controllers, Stations and other system items.
Remote Access Deployment Guide

The Remote Access Deployment Guide describes how to implement remote access to
your EBI system.
Operator's Guide
The Operator's Guide describes how to use Station to monitor and control your EBI
system.
Reception Management Module Guide

The Reception Management Module Guide describes how to configure Reception
Management and how to use Reception Management.
Reception Management replaces Visitor Management.
Reception Web Module Guide

The Reception Web Module Guide describes how to use the Web interface of the
Reception Management Module.
The Backup and Restore Guide

The Backup and Restore Guide documents the recommended procedure for backing up
and restoring an EBI system using Acronis True Image.
Application Development Guide

The Application Development Guide provides an overview of the customization
capabilities of EBI, as well as important information about developing a custom
application that integrates with EBI.
Server Scripting Reference

The Server Scripting Reference describes how to extend the functionality of your EBI
system by writing scripts for the server, points and other items. (A script is a mini-
program that performs a specific task.)
9
ABOUT THIS GUIDE
Hardware and Point Build Reference

The Hardware and Point Build Reference is a reference for engineers who want to
understand the syntax and structure of the hardware and point definition files created by
Quick Builder.
Diagnostic Guide
The Diagnostic Guide is a troubleshooting reference. It describes common problems,
diagnostic checks and solutions.
Interface and Controller References

There is a separate reference for each type of interface and controller supported by EBI.
Each reference describes how to set up and integrate the controller with EBI.
Document availability
The documents are supplied in one or more of the following formats:
• Documentation Set—a help file that contains all EBI documents.
You can access the Documentation Set from Station, or from the Start menu by
selecting Programs > Enterprise Buildings Integrator > EBI Documentation.
• Print—included in the EBI delivery package.
• PDF—supplied on EBI DVD. (If necessary, you can load them on any computer.)
• Context-sensitive help—supplied with client applications such as Quick Builder and
Display Builder.
The following table shows the formats in which each document is supplied.
Title Documentation Set Print PDF Context-sensitive help

Overview Yes Yes Yes
Installation Guide Yes Yes Yes
Configuration and Yes Yes Yes
Administration Guide
Advanced Configuration Yes Yes
Guide
10 www.honeywell.com
ABOUT THIS GUIDE
Title Documentation Set Print PDF Context-sensitive help

Access Control Configuration Yes Yes Yes (If configured in
Guides for: Quick Builder)
• AXSS-II
• FS90
• IdentIPoint
• PCSC
• Security Electronics
• Temaline
Import Export Guide Yes Yes
Building Management Guide Yes Yes
HMIWeb Display Building Yes Yes
Guide
Quick Builder Reference Yes Yes
Remote Access Deployment Yes Yes
Guide
Operator's Guide Yes Yes Yes Yes
Reception Management Yes Yes
Module Guide
Reception Web Module Guide Yes Yes
Backup and Restore Guide Yes Yes
Diagnostic Guide Yes
Server Scripting Reference Yes Yes
Application Development Yes
Guide available in CHM
format in the Documentation
folder on the EBI DVD.
Hardware and Point Build Yes Yes
Reference
Interface and Controller Yes Yes Yes (If configured in
References Quick Builder.)
11
ABOUT THIS GUIDE
Introduction to EBI
This section provides an overview of EBI. You should read this section carefully to gain
an understanding of EBI features and capabilities.
Related topics
“The versatility of EBI” on page 14
“Architectural flexibility” on page 17
“Operator interfaces” on page 24
“Operator security” on page 28
“Exchanging data with other applications” on page 31
“Advanced customization capabilities” on page 34
“Companion products” on page 37
“Understanding supervisory control” on page 38
“About points” on page 39
13
INTRODUCTION TO EBI
The versatility of EBI

An EBI system takes care of a building's security management, building management,
and fire monitoring. It is a one-window, web-enabled system that allows you to control
everything from HVAC, lighting, and energy, to life-safety and security subsystems, to
financial and personnel records, environmental controls, and supply chain databases.
EBI is used in a wide range of applications including:
• Large commercial buildings
• Telecommunications
• Industrial sites
• Casinos
• Education
• Healthcare
• Government
• Prisons
• Airports
Of course, EBI can also be tailored to suit other specialized applications, and it is
compatible with controllers from all the major providers. The philosophy behind EBI is
to provide an open standard for integration and to embrace open technology.
It is fully integrated with Microsoft Windows with industry networking standards and
works seamlessly with BACnet and Echelon LONmark devices. Standard TCP/IP
network topologies include LAN, WAN, serial, and dial-up access.
EBI is based around a client-server architecture. A high-performance real-time database
is maintained by the server (which can be redundant). This provides real-time
information to local or network-based (LAN or WAN) clients such as Stations, or other
applications such as spreadsheets or relational databases. And because it is modular in
design, EBI is an extremely cost-effective and scalable solution. Configurations can
range from small single-node systems to multi-server integrated systems, as shown in
the following figures.
INTRODUCTION TO EBI
Stations (Clients)
Remote Access Internet Access

Enterprise Systems & Databases
Dial In
F-Box BNA
Other Integration
Server
HVAC Controllers
Security & Access Controllers
XLS System
Figure 1: Redundant-Server System with Security, Building and Fire Management
Honeywell Security Manager

The Honeywell Security Manager option provides an affordable way of ensuring the
security of people, locations, and intellectual property. Its comprehensive approach to
access control and security accommodates all of your security requirements including:
• Efficient management of cardholder details
• Access card design and creation, including PhotoID
• Comprehensive control and monitoring of all cardholders at your site, including shift
management, guard tour, and visitor management
• Prompt, intelligent alarms, including operator response instructions and deadman
timer
Honeywell Building Manager

The Honeywell Building Manager option provides tools and data to better manage the
environment, resulting in energy efficiency and significant cost savings. Maintenance
staff have, at their fingertips, the functionality and information they need to minimize
maintenance costs, including:
• Scheduling
• Detailed HVAC information
15
INTRODUCTION TO EBI
• Alarm Pager
• HVAC reports
Honeywell Life Safety Manager

The Honeywell Life Safety option allows a Station (EBI's operator interface) to monitor
and test the building's fire panels. The operator is provided with continuous information
about the building's fire protection systems and can actuate a fire alarm or building
evacuation from Station.
EBI and Pharmaceutical Compliance

EBI's Pharmaceutical Compliance option addresses the specific needs of the
pharmaceutical, bio-technology or medical device industries. In particular, it addresses
21CFR Part 11 guidelines most critical for FDA-regulated industries, namely electronic
records and electronic signatures.
INTRODUCTION TO EBI
Architectural flexibility
The philosophy behind EBI is to provide an open standard for integration and to
embrace open technology. EBI supports TCP/IP networking standards, and industry-
specific standards such as BACnet and Echelon LONmark. EBI also supports standard
LAN and WAN network topologies, cloud connectivity, as well as serial and dial-up
connections.
EBI is based around a server-client architecture. The server maintains a high-
performance, real-time database. Clients include Stations (EBI's operator interface) and
other applications such as spreadsheets or relational databases.
The modular design of EBI makes it an extremely cost-effective and scalable solution.
The following examples show typical configurations that range from small single-node
systems to multi-server integrated systems.
EBI Cloud Connector

The EBI Cloud Connector provides a way to securely and reliably connect to EBI
systems from the cloud. Cloud connectivity enables a suite of applications that range
from automated detection of equipment faults, energy optimization, to mobile
applications for common operation and maintenance tasks.
By providing a single path from site to cloud it ensures all applications use the same
audited and monitored method to access systems and removes the need for other
connections, such as Remote Desktop.
Using cloud services enables:
• Standard history records to be pushed to the cloud every minute.
• The flow of real-time alarms to the cloud.
• The support of point read from the cloud.
For details about the EBI Cloud Connector, refer to the EBI Configuration and
Administration Guide and the Network Security and Planning Guide.
Server redundancy
You can improve system availability with server redundancy. In a redundant server
system, EBI is installed on two identically configured servers.
EBI uses software arbitration to determine which server acts as primary. (With software
arbitration, each server polls the other over the network to determine whether the other
server has failed.)
17
INTRODUCTION TO EBI
Primary Server Backup Server
Ethernet
Controllers
Stations
Figure 2: Typical Redundant Server System
Distributed System Architecture

Distributed System Architecture (DSA) allows you to integrate up to 10 servers into a
single system. DSA is appropriate for:
• Logically separate EBI systems located in different parts of a facility
• Geographically-dispersed systems, as shown in the following figure, in which the
servers are connected through a WAN
INTRODUCTION TO EBI
Master Control Center
WAN
Site A Site C
Site B
Figure 3: Typical Geographically-dispersed System
Point servers
A point server is a high-level interface that allows EBI to exchange data with other
applications or sub-systems, such as LON and BACnet, without the need for
individually configuring points in EBI.
Point servers read data directly from the field when requested by EBI. The structure of
each data set (called a flexible point) is determined by the application or sub-system,
rather than by EBI.
The LonWorks point server option, for example, gives EBI access to Honeywell
EXCEL 10 devices without the need for complex point-building configuration tasks. It
also includes pre-built point detail displays for EXCEL 10 devices so that operators can
monitor their HVAC system.
The following figure shows a system that uses three LonWorks point servers to integrate
three LonWorks networks.
19
INTRODUCTION TO EBI
Honeywell Server
Ethernet
LonWorks
Point Servers
LON Bus LON Bus LON Bus Honeywell or

Third-party
LON Devices
Figure 4: An EBI System with LonWorks Point Servers
Controller interfaces
Controller interfaces enable EBI to exchange data with controllers by individually
mapping memory locations in the controllers to standard points in EBI. (EBI provides
interfaces for most types of controllers used in security and building management.)
Controller-to-server connections
The way in which you connect a controller to the server depends on several factors, such
as the physical layout of your site and the controller's communication ports.
Network connections
If a controller has a network port, you can connect it directly to the network, as shown in
the following figure.
INTRODUCTION TO EBI
Honeywell Server
Ethernet
Controllers
Figure 5: Controllers Connected Directly to the Network
Indirect serial (terminal server) connections

You can connect controllers to the network through a terminal server. (A terminal server
allows you to connect several controllers to the network even though they only have
serial or parallel ports.) Most terminal servers also provide a range of serial connection
options, such as RS-232, RS-422 and RS-485.
Terminal servers are particularly useful if you have a:
• Site-wide network, and you want to connect controllers to the LAN—as shown in the
following figure
• Geographically-dispersed controllers on a WAN
21
INTRODUCTION TO EBI
Server
Network
Terminal Server Terminal Server
Controllers
Building A Building B
Figure 6: Typical System with Terminal Servers
Direct serial connections

If you have a small system, you can connect controllers to the server's serial ports.
Note that you can add more serial ports to the server with a serial adapter. An advantage
of serial adapters is that they provide a choice of interfaces, such as RS-422 and RS-485,
which are suitable for medium-distance links.
Terminal servers and server redundancy

If you have redundant servers, you must use terminal servers to connect controllers that
only have serial ports. (Unlike the controllers, terminal servers can automatically switch
communications to whichever server is running as primary.)
INTRODUCTION TO EBI
Primary Server Backup Server
LAN
Terminal Server
Controllers
Figure 7: A Terminal Server in a Redundant Server System
Modems
You can use modems to connect controllers located at remote sites.
If you only require infrequent scanning, you could use a dial-up modem. If you require
more frequent scanning, you could use a modem in conjunction with a leased line.
23
INTRODUCTION TO EBI
Operator interfaces
Station is EBI's user interface that presents information in a graphical, user-friendly
manner. (There are other operator interfaces such as HMIWeb browser and Honeywell
EasyMobile.)
In general, Station runs on standard computers that are connected to the server through
the network. However, Station supports most Windows-compliant peripherals such as
touch-screens with dedicated function keys. (If you have an entry-level system, you can
even use Station on the server computer.)
You can have up to four instances of Station running simultaneously on the one
computer. From a licensing point of view, all instances of Station on the same computer
are treated as one Station connection. For example, if you have a license for two static
Stations and two client computers, you can run up to eight instances of Station (four on
each computer).
You can configure the way in which the instances of Station interact. For example, when
operators call up trends and groups from STN01 (the master Station), you can direct
trends to STN02 and groups to STN03. If you have several monitors, you can also direct
each instance of Station to a specific monitor.
Displays
Station uses displays to present information. Each display is, in effect, a control panel
that shows information about a particular part of the system, and contains appropriate
controls such as buttons and scroll bars.
System displays
EBI is supplied with a comprehensive set of system displays that present information in a
standardized manner.
INTRODUCTION TO EBI
Figure 8: A Typical System Display
Custom displays
You can make it much easier for operators to supervise your facility if you create
suitable custom displays, such as the one shown in the following figure.
Figure 9: A Typical Custom Display
You use HMIWeb Display Builder, a specialized drawing tool supplied with EBI, to
create custom displays. HMIWeb Display builder is supplied with clip art libraries that
25
INTRODUCTION TO EBI
cover both security and building management. You can also insert your own graphics,
such as photographs and floor layouts.
Station on mobile tablets

You can gain access to your EBI server using a mobile tablet (such as an iPad or similar
tablet device) by implementing remote access.
When using tablet devices, users have full Station capabilities—they provide the same
level of control as Station does when used on a desktop computer.
Mobile tablets can connect to the EBI server using simple or enhanced remote access:
• In simple remote access, the tablet device connects directly to the EBI server through
the corporate firewall.
• In enhanced remote access, the tablet device connects to a remote access server
(RAS) located in the DMZ behind a firewall. In turn, the RAS connects to the EBI
server, located in the building control network (BCN) behind a firewall. (The RAS is
loaded with Station and Remote Desktop Gateway to ensure secure, encrypted
communication with the tablet device.)
Simple remote access supports a single remote user connection. Enhanced remote access
supports multiple, simultaneous remote user connections. Each Station connection
running in a remote desktop on a mobile device requires a licensed Station connection.
HMIWeb browser
The EBI inbuilt Web server enables users to access EBI using HMIWeb browser
components and Internet Explorer. HMIWeb browser is especially useful to casual users
remotely accessing Honeywell Building Manager.
The section “Configuring the EBI Web Server” in the Configuration and Administration
Guide provides detailed information about setting up the web server and configuring
HMIWeb browser. It also describes the operational differences between Station and
HMIWeb browser. (For example, it is not suitable for accessing the cardholder
management system or Honeywell DVM systems.)
Each HMIWeb browser session is treated as a rotary Station connection. Consequently,
you need to ensure that your license includes enough rotary Stations to cater for
HMIWeb browser users.
Honeywell EasyMobile
If you use EBI for Building Management, Honeywell EasyMobile is a solution allowing
the basic operations of EBI from most mobile browser interfaces such as smartphones.
INTRODUCTION TO EBI
Honeywell EasyMobile can assist with maintenance tasks. For example, a field
technician can make adjustments to HVAC equipment and use Honeywell EasyMobile
to connect to EBI to see the affect on the HVAC system.
Honeywell EasyMobile is designed as a complementary tool to Station and therefore the
full Station functionality is not available on Honeywell EasyMobile.
27
INTRODUCTION TO EBI
Operator security
You can configure operator security using:
• Facility Model, Organization Model, and scope of responsibility
• Station security
• Point control restrictions
Related topics
“Facility Model, Organization Model, and scope of responsibility” on page 28
“Station security” on page 28
“Point control restrictions” on page 29
“Electronic Signatures” on page 30
Facility Model, Organization Model, and scope of responsibility

You can control access to your EBI system by creating a Facility Model (previously
called areas) and an Organization Model (if you use the Cardholder management
system). These models provide a method of organizing your points and cardholders in a
way that reflects the building and tenants you are managing.
By creating locations in the Facility model and organizations in the Organization Model,
you can then assign access to these locations and organizations to operators or Stations;
this is known as scope of responsibility. Scope of responsibility allows you to provide or
restrict access to the parts of the EBI system as appropriate for each operator or Station.
These models are particularly useful in buildings that have several tenants and in large
facilities where different operators have responsibility for different parts of a facility.
Locations and organizations allow you to restrict operator/Station access to:
• Alarms
• Points
• Custom and cardholder detail displays
• Access rights
• Zones
Station security
You can restrict access to Station using either operator-based or Station-based security.
INTRODUCTION TO EBI
Operator-based security
With operator-based security each operator has an operator ID and a security level, and
logs on to Station using the operator ID and password.
Operator-based security provides six security levels, each with different privileges: View
Only, Ack Only (Acknowledge only), Oper, Supv, Engr, and Mngr (shown in order of
increasing security level).
You can use operator-based security to restrict:
• Control of points
• Access to specific locations
• Access based on day and time
• Access to specific Stations
You can also specify an 'inactivity time', which, if exceeded, automatically logs off the
operator.
Station-based security
Station-based security does not require an operator ID or password to log on to Station
with Oper security level. However, passwords are required to change to higher security
levels in order to perform configuration and administration tasks.
Security is managed on a Station-by-Station basis, enabling a particular Station to access
designated parts of the database.
Duress login
As an added security precaution, an operator, under hostile circumstances, can log on
using a duress login and set off a silent alarm in order to alert other operators.
Point control restrictions

By defining each operator's point control rights you can prevent certain operators from
intervening or overriding automatic point control, or even prevent them from viewing
the detail displays for points.
You can use the following techniques to restrict an operator's point control rights:
• Control Level. Only operators with a control level equal to or higher than the point's
control level are able to control the point. (The point is assigned a particular control
level when it is configured.)
• Locations. Only operators who are assigned to the same location as the point are
able to view the point. (The point is assigned to a particular location when it is
configured.)
29
INTRODUCTION TO EBI
Electronic Signatures
EBI's Electronic Signature option enables you to implement electronic signatures for
specified operator actions, such as controlling particular points.
An electronic signature requires a user with appropriate privileges to enter their operator
ID and password, as well as the reason for performing the action.
For critical actions, you can configure them to require two signatures.
Details about each action, including the operator name(s), date and time are stored in the
events database.
INTRODUCTION TO EBI
Exchanging data with other applications

EBI includes a number of options for exchanging data with other applications, such as:
• Microsoft Excel Data Exchange
• ODBC Data Exchange
• ODBC Driver
• OPC
Related topics
“Microsoft Excel Data Exchange” on page 31
“ODBC Data Exchange” on page 31
“ODBC Driver” on page 32
“OPC” on page 32
Microsoft Excel Data Exchange

Microsoft Excel Data Exchange allows you to capture real-time point parameter and
history data, and display it in a Microsoft Excel spreadsheet. The captured data can be
static or dynamically updating.
You can capture the data using either the Microsoft Excel Data Exchange Wizard, or
through cell formulas. After capturing the data, you can create charts to display and
analyze data with Microsoft Excel's toolset. You can also link the values into other OLE-
enabled applications.
Microsoft Excel Data Exchange provides:
• Read/write access to point parameter values
• Read access to history data
• Read/write access to server database files (user files)
ODBC Data Exchange

ODBC Data Exchange enables two-way exchange of data between the EBI database and
an ODBC-compliant database (either local or remote). It is typically used to periodically
transfer data for billing customers. ODBC-compliant databases include Microsoft SQL
Server, Oracle 7, Microsoft Access, and Sybase 10.
31
INTRODUCTION TO EBI
ODBC Driver
The ODBC Driver is primarily intended for reporting, and enables an ODBC-compliant
application to access data in the EBI database, such as history, event, access, and point
parameter values. ODBC-compliant applications include Microsoft Access and
Microsoft Excel.
OPC
EBI provides the following OPC options, each of which has been optimized for a
particular purpose.
EBI OPC Client Interface

The EBI OPC Client Interface is primarily designed for integrating low-complexity
subsystems, such as controllers. Configuration involves individually mapping OPC
items to standard points. If you require alarming for an item, you must configure the
associated point's alarm properties.
EBI OPC Data Access Server

The EBI OPC Data Access Server gives an OPC client read/write access to EBI point
parameters. It is compliant with the OPC 2.0 Data Access specification, and can accept
connections from either OPC 1.0 or 2.0 clients.
EBI OPC Historical Data Access Server

The EBI Historical Data Access Server gives an OPC client access to EBI point
parameter history. It supports the OPC Historical Data Access Specification.
EBI OPC Alarm and Event Server

The EBI OPC Alarm and Event Server allows an OPC alarm and event client to receive
alarm and event information from EBI. It is compliant with the OPC Version 1.02
Foundation Alarm and Event Specification.
EBI OPC Data Transfer

EBI OPC Data Transfer is designed to allow bi-directional data transfer between two or
more OPC Data Access Servers. The following scenarios illustrate typical uses of the
EBI OPC Data Transfer:
• You require fast and efficient transfer of data within an EBI system. You can use EBI
OPC Data Transfer, instead of the value transportation algorithm, to transfer data
between point servers as well as controllers.
INTRODUCTION TO EBI
• You have a system that provides an OPC server, but not an OPC client. However, the
system needs to retrieve data from EBI.
• EBI data needs to be transferred to a third-party OPC server whenever it changes,
irrespective of the reason for the change (including when the data is changed by an
operator).
OPC Data Transfer supports redundant EBI servers, and is therefore itself redundant.
33
INTRODUCTION TO EBI
Advanced customization capabilities

There are several options available to customize your EBI system, ranging from
HMIWeb Display Builder for creating custom displays, to Application services for
creating custom applications:
• Enterprise Web Services
A family of web services that can be used to search and query entities such as points
and alarms, read and write point parameter values, enable and disable entities such as
channels, point servers, controllers, raise alarms and events, and acknowledge alarms
Application services replaces the Server API and the Network API.
• Enterprise Web Services REST API
Used to create HTML pages that contain data sourced from the EBI server. The
REST interface supersedes the Web toolkit.
• Real-time Data Services
A programming interface designed for integrating with third-party devices.
Real-time Data Services replaces the point server development toolkit.
• Cardholder Services
A family of web services that can read, write, add and delete entities such as
cardholders, cards, organizations. They also provide advanced features such as
downloading and uploading cardholder images, advanced searches, and reading and
writing to custom user tables.
• CMS Customization toolkit
A collection of configuration tools that allow changing the structure of the
cardholder database (by adding, changing or deleting user fields), changing the look
and feel of the cardholder displays or even changing how certain operations work.
• HMIWeb Display Builder
A specialized drawing application used for creating custom displays. It includes a
display object model for to create scripts to extend the functionality of the custom
displays.
• Automation rules
A user-configurable set of rules to automate routine, repetitive tasks such as display
callup, cardholder comparison, video recording. The rules are designed to be easy to
configure and reduce the need for creating server scripts and algorithms.
• Server Scripting
Includes a server object model to extend the functionality of the EBI server.
INTRODUCTION TO EBI
The following tables describe the options available in the context of the type of
application you might require. The types of applications have been broadly categorized
as:
• Integrating with business processes
• Integrating with third-party hardware
Integrating with business processes

To determine the appropriate customization option if the application you are developing
integrates with the customers business process, ask the following questions:
Question/answer Recommendation
Q. What level of operator interaction is required and what type of content is the operator
interacting with?
A. Support for operator workflow for typical Use the HMIWeb Display Builder to create
operators using Station and/or HMIWeb custom displays.
browser and interacting with notifications
For detailed information about building custom
(alarms, events) and point parameter data
displays and the scripting that is available, see the
HMIWeb Display Building Guide.
A. Support for operator workflow for typical Use the CMS Customization Toolkit.
operators using Station and/or HMIWeb
browser and the operator interacts with
cardholder data
A. Support for ad-hoc users with limited Use Enterprise Web Services REST interface to
access to EBI using a browser and the ad-hoc create a web interface that connects to the EBI
users require point: parameter data server.
A. A combination of operator interaction and A combination of solutions may be required, such
system automation is required as building custom displays using HMIWeb
Display builder, the CMS Customization Toolkit,
and custom applications using Enterprise Web
Services and Cardholder Services.
A. No interaction is required, the solution Ask the follow-on question, What is the scope of
needs to provide an automated workflow the data/workflow?
Q. What is the scope of the data/workflow?
A. data/workflow remains completing within Use Automation Rules or Server Scripting to
the EBI system extend existing EBI functionality
A. Data/workflow spans both EBI and non- Use Enterprise Web Services to create a custom
Honeywell enterprise systems application.
Integrating with third-party hardware

To determine the appropriate option if you need to integrate with third-party hardware,
ask the following questions:
35
INTRODUCTION TO EBI
Question/answer Recommendation
Q. Does the device support a standard?
A. The device supports on the following Investigate whether the EBI interfaces for these
industry standards: industry standards can be used.
• BACnet
• LonWorks
• OPC
A. The device does not support one of Create a Comms Driver using Real-time Data
the standards, or the EBI interface for Services.
the standards is not suitable.
For information about understanding the scope of
work required to develop a Comms driver, see the
topic, “Assessing the requirements for integrating with
third-party devices” in the Application Development
Guide.
INTRODUCTION TO EBI
Companion products
The following Honeywell products are tightly integrated with EBI and provide
specialized functionality:
• Honeywell Digital Video Manager
• Honeywell Energy Manager
For more information about any of these products, contact your Honeywell
representative.
Related topics
“Honeywell Digital Video Manager” on page 37
“Honeywell Energy Manager” on page 37
Honeywell Digital Video Manager

Honeywell Digital Video Manager (Honeywell DVM) is a Closed Circuit Television
(CCTV) application that combines the advantages of digital video with the latest Web
and networking technologies.
You can configure Honeywell DVM so that it initiates recordings in response to
specified EBI alarms and events.
Also, because Honeywell DVM uses Station as its user interface, operators can switch
between EBI and Honeywell DVM displays in a seamless manner.
Honeywell Energy Manager

Honeywell Energy Manager is designed to minimize the engineering effort required to
set up and maintain your energy information and control system.
Honeywell Energy Manager provides a set of tools to help you:
• Model your energy system
• Collect and store energy-related data
• Transform raw energy data into user-friendly indicators to help you make effective
cost-reduction decisions
37
INTRODUCTION TO EBI
Understanding supervisory control

Supervisory control means control that originates from EBI (whether by an operator or
programmatically, for example, global schedules or automation rules).
Supervisory control works by changing the values in controllers that are associated with
field devices. Usually control is performed by the internal logic of controllers. An
example of this is the remote locking of a door.
Supervisory control works as follows:
1. A new value is entered by an operator (manual mode) or an EBI program (automatic
mode).
2. The server relays the new value to the controller.
3. The controller outputs the control value to the field device.
INTRODUCTION TO EBI
About points
A point is a collection of information about a particular part of your system. For
example, a point representing a motor would include the following items of information:
• An ID, also known as a tag name, which uniquely identifies the motor.
• A description, such as "Fan cool unit 1".
• A full name. The full name indicates a point's location within the Facility Model; for
example, /Facility/Honeywell/Grnd Floor/TempGuage1 indicates that the point
named TempGuage1 is assigned to the location named Grnd Floor which is itself
assigned to the location name Honeywell.
• The current state (Off or On).
• The desired state. This is applicable if you are allowed to control the point. For
example, if current state of the motor is On you can change the real state of the motor
to Off using the display.
Points are used to exchange data between controllers and the server database.
EBI records each significant change in the values for a point as an event, which
operators can see on the Event Summary display. Point events can also be treated as
alarms.
39
INTRODUCTION TO EBI
Using EBI
This section describes the basics of using EBI, such as responding to alarms and events,
analyzing system data, and working with events and historical data.
Related topics
“Responding to alarms and events” on page 42
“Analyzing system data” on page 45
“Archiving point history and events” on page 47
“Troubleshooting EBI” on page 48
41
USING EBI
Responding to alarms and events

EBI generates alarms and events when it detects specified changes in the field.
Alarms indicate unusual conditions, such as an unexpected change in temperature or
movement in a secure location, that require operator action. The alarm remains until the
condition that triggered the alarm returns to normal and someone acknowledges the
alarm.
All changes in the system, for example, alarm changes, operator changes, and security
level changes, are logged as events.
The following figure shows how EBI responds to a typical event (in this case, a card
being presented to a card reader).
1. Someone presents card 2. Server determines whether 3. Alarms and events are displayed
to card reader it should raise an in Station. (They can also be printed
alarm or event as they occur and included in reports)
Server Station
Alarm!
Card status
"stolen"
Card Reader
Access Panel
Printer
Figure 10: Alarm/Event Generation
All alarm conditions are recorded in the event log, including when an alarm is generated,
when it returns to normal, and when it is acknowledged.
Alarms are generally assigned different priorities to help you view critical alarms first.
The priorities are: Urgent, High, Low, and Journal. Journal alarms are not shown on the
Alarm Summary but are recorded as events.
Operators can:
• View events and alarms on Stations. The Status Zone, beneath the display, always
shows the most recent (or oldest) and highest priority alarm that has not been
acknowledged.
• Print a summary of alarms and events to an alarm/event printer. All alarms and
events are recorded in an alarm/event journal.
USING EBI
Figure 11: A Typical Alarm Summary Display
Alarm shelving
Alarm shelving is a form of manual suppression that enables operators to remove
individual alarms from the main alarm summary display for a limited time.
Shelving is typically used by operators to hide “nuisance” alarms that are distracting
them from other more important alarms. Although multiple alarms can be shelved at the
same time, you can only shelve one alarm at a time.
Alarm shelving is most suitable for the following situations and scenarios:
• Dealing with stale or standing alarms such as those arising from instrument
malfunction or faulty equipment awaiting repair.
• Background or nuisance alarms such as those arising from unusual weather
conditions.
• Dealing with alarms that require action that may take time. For example, an operator
may need to change a temperature set point for a process that takes two hours to
effect the change. In a case like this, operators can shelve the alarm for two hours,
knowing that if the alarm is re-annunciated after that time, there is still a problem
that needs to be addressed.
43
USING EBI
How alarm shelving works

• When an alarm is shelved, EBI automatically:
– Acknowledges the alarm
– Silences the alarm
• While alarms are shelved they can be viewed by using the (shelved alarms) view on
the Alarm Summary or by choosing one of the filters on the Alarm Icon column that
show shelved or hidden alarms.
• Depending on how shelving has been configured at a given site, shelved alarms
generally do not reappear in the Alarm Summary until their shelving period expires
or they are manually unshelved.
• If an alarm returns to normal while it is shelved, it remains shelved until its shelving
period elapses or it is unshelved by the operator. When such an alarm is unshelved it
automatically disappears from the alarm summary.
• If an alarm recurs while it is shelved, the alarm remains shelved and also remains
acknowledged and silenced.
For more information about alarm shelving, see the “Configuring alarm shelving” topic
in the “Configuring alarms and messages” section of the Configuration and
Administration Guide.
Alarm groups
By using alarm groups, you can create an arbitrary group of points for the purposes of
monitoring alarms on those points. For example, you might want to group together all
points that represent the fire doors in your building. As a result of doing this, you can
easily monitor any alarms on any of these doors.
Managing operator response to alarms

The Advanced Alarm Management option is used to provide operators with a series of
steps to follow for a particular alarm. When an operator acknowledges an alarm, an
alarm instruction display appears. In order to close the alarm, the operator must
complete an alarm response display.
USING EBI
Analyzing system data

You can use reports and trends to analyze system data.
Related topics
“Reports” on page 45
“Trends” on page 45
“Storing point history” on page 46
Reports
EBI includes a comprehensive set of standard reports that are useful for analyzing and
monitoring alarms, events, points, cards, and so on. If necessary, you can create your
own custom reports using tools such as Microsoft Access.
You can request reports when you need them, or produce them automatically at pre-
defined times. You can also specify a report's destination: either a printer or display.
Trends
You can use trends (specialized displays) to analyze changes in point values over time.
You can include an Event Summary in your trend to investigate any correlation between
changes in points to specific events.
Trends can present information in several forms (such as lines or bars) and can show
values for up to 32 points.
45
USING EBI
Figure 12: A Typical Trend Display
Storing point history

EBI can store the values of points over time to create a history of the operations of your
site. There are three types of history:
• Fast. Stores snapshots of a point parameter at the fast history interval (configurable
between 1 and 30 seconds, the default being 5 seconds).
• Standard. Stores the following snapshots and averages:
– 1-minute snapshots
– 6-minute averages of the 1-minute snapshots
– 1-hour averages of the 1-minute snapshots
• Extended. Stores the following history snapshots:
– 1-hour snapshots
USING EBI
Archiving point history and events
Point history archiving

EBI stores point history data in the server for a limited time, which is determined by the
default retention periods for the history interval being used.
If you want to keep point history data for longer periods, you must archive the data to
off-line media, such as tape or removable disk.
Event archiving
EBI stores every event, such as point status changes or operator actions, in an event
database for a specified time.
Event archiving enables you to archive these events to disk or tape, where they can be
stored for future retrieval. For example, you can restore event archives so that they can
be included in standard reports.
Event archiving can be scheduled automatically, or an alarm can be generated to alert the
operator to archive the events.
47
USING EBI
Troubleshooting EBI
EBI includes the Diagnostic Framework, a stand-alone application that provides a
unified interface for running tests, collecting diagnostic information and viewing logs.
The Diagnostic Framework contains a set of pre-defined tests that are applicable to your
system and the current environment—that is, the tests vary depending on whether the
Diagnostic Framework is installed on a server as opposed to a client computer.
If you have a problem that you can reproduce—for example, you cannot start the server
—you can record relevant system activity as you reproduce the problem.
You also use the Diagnostic Framework to create diagnostic packages for TAC, which
include log, recordings (captured when reproducing a problem) and other files that may
help diagnose the problem.
Using EBI for Security Management
This section describes how EBI is used for security management. It includes the
following topics:
• Cardholder management
• Controlling building access
• Access control concepts
Related topics
“Cardholder management” on page 50
“Controlling building access” on page 52
“Access control concepts” on page 54
49
USING EBI FOR SECURITY MANAGEMENT
Cardholder management
Access to a site or installation is usually controlled using access cards. Anyone who
requires access has a card that is imprinted with identification details. When they use the
card (at a door, for example), the access controller that has been downloaded with the
EBI cardholder database checks their access permissions, and grants or denies access.
Cardholders can only access a location if they have the required permissions (and are
seeking access during the appropriate shifts).
In EBI, access rights are easy to allocate and easy to maintain, and you can define your
own fields for cardholder information. You can even design and print your own access
cards (with photos, signatures, logos, and so on).
Cardholder information in the server database

There are two kinds of information required for a cardholder: personal and access.
Personal information includes the cardholder name, card identification number, and
other optional information such as employee number, department, phone number,
photographic images, and so on.
Access information for a cardholder includes the access levels or access rights assigned
which indicates the sections of the facility that can be accessed by that individual. The
current state of the card (active, lost, stolen, or inactive) is also entered. The types of
access controllers used at your site will determine what other attributes associated with
access can be entered for the cardholder.
Integrated PhotoID
You use the Integrated PhotoID option to create your site's access cards. You can design
the layout of the card (including the cardholder's photograph, signature, and other
personal details) and then encode information onto the card using magnetic stripes or
barcodes.
Integrated PhotoID supports chromakey and ghosting, which make it more difficult to
forge or tamper with cards. (Chromakey removes the background from a cardholder's
photograph, and ghosting makes the cardholder's photograph semi-transparent.)
The details of all access cards created using Integrated PhotoID are saved as part of the
cardholder database. In addition to the convenience of only having to enter information
once, you have a central location from which you can create reports on cardholder
information. This is particularly useful if you are using Integrated PhotoID from a
remote Station.
Integrated PhotoID can be used with a wide range of cameras, both digital and video. (A
video capture card is required if you use a video camera.)
Reception Management
The Reception Management feature enables you to track and report on visitors to your
facility.
The activities you can perform using Reception Management are:
• Checking in visitors on arrival
• Checking out visitors on departure
• Preregistering visitors
• Collecting and performing historical analysis of visits and visitor data
• Assigning and returning temporary cards
In addition, the Reception Web Module allows you to manage reception tasks using a
browser rather than Station.
51
Controlling building access

This section describes how operators use EBI to control and monitor building or
installation access.
Related topics
“Server control of access” on page 52
“Downloading access information to the field device” on page 52
“Managing alarms” on page 52
Server control of access

You can configure the server so that it automatically controls the commencement and
expiry of access card validity. Using the current system date, the server checks to see if
there are existing cardholders whose cards have reached either their commencement date
or their expiry date. When found, the server changes the status to one of 'active' or
'inactive' and the modified card data is downloaded to the controllers.
Downloading access information to the field device

Access information is configured on displays and then downloaded to the access
controllers providing the controllers with up-to-date information. In general, information
is downloaded to the controller as it is saved in Station. However, there may be times
when you need to download all information. Downloading all information may take
some time and, as access to various locations in the site may be denied during the
download, should only be performed during off-peak times and when necessary.
Managing alarms
If there is an attempt at security violation, EBI's alarm management ensures that
operators know about it instantly and know precisely how to react. If a number of alarms
occur simultaneously, EBI prioritizes them so that the important ones can be
acknowledged first.
If an operator does not respond to an alarm within a given time period, the deadman
timer triggers an alarm. This means that you can be sure that operators are at their posts
and that all alarms are acknowledged promptly. Additionally, all actions are logged to an
event file and are available for future reporting and analysis.
EBI gives you the flexibility to choose precisely what constitutes an alarm. You can
choose its priority, and associate it with any or all point states. You can display an alarm
on a standard display, or you can create your own custom displays. You can even trigger
an audible tone or '.wav' file when an alarm occurs.
53
Access control concepts

This section describes access control concepts.
Related topics
“Card readers” on page 54
“Access points” on page 54
“Floor points” on page 55
“Zones” on page 55
“Time periods” on page 57
“Access rights” on page 57
“Perimeter Global Anti-Passback” on page 57
“Occupancy reporting” on page 57
“Cardholder reporting” on page 58
Card readers
A card reader is a hardware device that decodes the encrypted information stored on an
access card. A card reader connects to an Access Controller.
Normally card readers control doors, but they can also control turnstiles, lifts, gates, or
any other physical devices designed to control access. EBI includes interfaces to a wide
range of makes and models of card reader and access controller.
The decision to enable or deny access to a given card is made locally by the access
controller itself, using the configuration data EBI downloads to it. Each device must be
configured according to its hardware requirements. One issue to resolve during planning
is the limitation on how much configuration information your particular type of
controller can hold. You will need to plan your system very carefully to ensure that it
does not try to download more information to a given controller than can be stored.
Access points
An access point represents a card reader which defines an entry or exit point to a
physical space. Access points are used to monitor card traffic at the card reader by
recording the card number and cardholder name, and whether or not access was granted.
If two card readers were associated with one physical door—one to control entry and
one to control exit—two access points would be used to represent these two card
readers.
Access points are configured using Quick Builder and downloaded to the server
database. Operators view information about the access point and make limited changes
to the configuration on the point detail display for the access point. Access point
information can also be printed from any of various reports.
Figure 13: Access Point Detail Display
Floor points
A floor point represents a particular floor in a building served by elevators. Floor points
restrict access to certain floors of a building through control of the elevators.
A floor point is a specialized status point. A floor is either in the 'access' state, allowing
anyone to stop at the floor, or in the 'secure' state, where only cardholders with the
required privileges can access the floor.
Zones
A zone represents a physical space which is totally enclosed by card readers. That is, in
order to enter a physical space, one must use an access card at a card reader which
allows entry to that space. It should not be possible to enter this physical space without
using a card reader.
55
A zone consists of a list of access points which represent the card readers which allow
entry to the physical space. An access point can only be included in one zone, because a
card reader can define the entry into only one physical space.
For AXSS-II, FS90, PCSC, and SE controllers, you can assign up to 128 access points to
a single zone. The points can be those associated with physical doors or with elevator
floors. Zones are paired with time periods to create access level definitions for site entry
and exit control.
Access points are assigned to the same zones if they define entry into the same physical
space. In the following figure, for example, doors C, D, and F define entry into the
Payroll zone.
Outside
Reader A
Pay Office
Counter Area
G C
J I F E D
Cash Room Payroll
Figure 14: Zones and Zone Doors
Time periods
A time period represents a period during which a person may have access to a physical
space.
For example, the time period Working Hours might be made up of days Monday to
Friday and times 9:00am to 5:00pm, excluding holidays.
Time periods are configured and modified on Time Period Configuration displays. The
time period details depend on the type of access controller you use: all controllers of the
same type store the same time period definitions.
Access rights
Access rights is a term that encompasses both access levels and Temaline behavior
models. Both access levels and behavior models represent a particular set of access
control criteria. If you have FS90, PCSC, SE, or AXSS-II access controllers, you use
access levels. If you have Temaline access controllers, you use behavior models.
An access level is a combination of zones and time periods where the zone defines the
physical space and the time period defines the times at which that physical space may be
accessed.
Behavior models consist of a time-based component (time periods and day types) and a
typological component (the TemaKey terminals for accessing gateways). You can assign
up to four behavior models per cardholder per Temaline site.
Perimeter Global Anti-Passback

Perimeter Global Anti-Passback (PGAP) prevents people from entering a facility, then
passing their card back to another person to enable them to enter as well.
You must establish a perimeter zone around the facility to which access is strictly
controlled; all entry and exit points of the perimeter must be controlled by card readers.
A cardholder can only enter if they are registered as being outside the perimeter, and
they can only exit if they are registered as being inside.
EBI also supports nested anti-passback, which enforces readers be used in a designated
sequence to enter or leave a secured area.
Occupancy reporting
Once your facility is divided into zones, you can report on which people are currently in
a particular zone.
57
This works best if both entry and exit points to the zone are controlled by card readers.
This enables EBI to determine when people have entered a zone and when they have
exited it, either by entering another zone or by exiting the whole facility. Without dual
readers, you can tell only which zone a person last entered; until they present their card
to enter another zone, you cannot tell if they have left.
Cardholder reporting
Using EBI's pre-configured reports, you can produce a number of cardholder reports,
including:
• Card Usage
• Cardholder Details
• Cardholder List
• Cardholder Zone Summary
Using EBI for Building Management
This section describes how EBI is used for building management.
Related topics
“Monitoring and controlling HVAC information” on page 60
“Scheduling” on page 61
“Alarm paging” on page 63
“Life Safety Management” on page 64
59
USING EBI FOR BUILDING MANAGEMENT
Monitoring and controlling HVAC information

The point detail displays provide easy and fast access to point values and point control.
You can incorporate live point data into custom displays, such as floor plans and
schematics for optimal representation of the building's HVAC performance. You can also
trend and archive all point parameters.
EBI includes point server interfaces for LonWorks and BACnet, popular HVAC
networking standards. LonWorks is, for example, used by Honeywell's EXCEL 5000
system. (Point servers speed up configuration tasks because they provide direct access to
field values.)
If you have EXCEL 5000 or R7044 controllers, you can view and modify the
configuration parameters that control your HVAC system.
If you use the EXCEL 5000 Dial-up Interface, you can also monitor, control, and acquire
data from remote sites containing EXCEL 5000 series controllers, as if each site was
locally connected.
You can also use Easy Mobile to access HVAC information on a mobile device.
Scheduling
EBI's scheduling capabilities enable you to control points on both a one-off and periodic
basis.
Global Schedules
Global Schedules enable controls to be carried out on predetermined days and at
predetermined times. EBI Global Schedules provide an integrated means of configuring
and viewing schedule information.
With Global Schedules you can define schedules, calendars and holidays once and then
propagate them to all supported controllers. The current release of EBI Global Schedules
supports schedules for:
• Honeywell Server points
• BNPS-R7044 controllers
• Excel 5000 controllers
• BACnet controllers
Key concepts related to Global Schedules are:
• Resources
• Control items
• Calendars
A resource is a way in which you can represent the real control entities of your site by
grouping point parameters or control items. After creating a resource you can start to
define new schedules for that resource, or you can assign an existing schedule that was
created for another resource. As you define the schedules for a selected resource,
summary schedule information is added to the Microsoft Outlook-style Global
Schedules display.
Control items are the actual control parameters that will perform the control that you
need to schedule. So, after you have decided on how you want to structure your
resources, you then need to define which control parameters on which controllers will
perform the required controls for each resource.
Calendars are generally a way of creating exceptions to normal daily (recurring) control
schedules. For example, if an office building is open every day of the working week
(except for public holidays), you would set up a system calendar that includes all public
holidays to ensure that the standard recurrent schedule is not in operation on those days
when the building is not open for general access.
Point Control Schedules

A Point Control Schedule allows you to control a point at a specified time on either a
periodic or one-off basis. In the case of a building, for example, you could have one
61
schedule switch the lights on at 7 am each day and another schedule to switch them off
at 9 pm.
Alarm paging
The Alarm Pager option pages specified alarms to a number of pagers.
You can use two techniques to specify which alarms are paged:
• Individually define each point and the minimum alarm priority that results in a paged
alarm
• Specify the operators whose alarms are paged—that is, alarms assigned to locations
for which operators are responsible are paged (Only applicable if you use operator-
based security.)
If the paging service provider allows, the Alarm Paging system sends multiple message
blocks at the same time, thus reducing the amount of times it has to ring up the provider.
The Alarm Paging system supports the following protocols:
• Paging Entry Terminal (PET) protocol
• Telocator Alphanumeric Protocol (TAP)
• Universal Computer Protocol (UCP)
The Alarm Paging system also supports sending messages as:
• Email
• SNMP messages
63
Life Safety Management

The Life Safety option enables EBI to monitor fire panels. The Life Safety displays
provide operators with detailed information about the status of the fire and emergency
monitoring systems, including:
• Panel Alarms
• Panel Supervisory Alarms
• Panel Troubles (indicates panel trouble)
• Panel Monitoring (indicates if any XLS Panel on the channel goes into monitor
mode)
• Comms Status (indicates Fire panel communications)
Operators can also issue panel commands, such as Initiate Fire Drill and Reset Panel.
Figure 15: XLS Panel Status Display
Notices
Trademarks
IdentIPoint® and SafeBrowse® are U.S registered trademarks of Honeywell
International Inc.
Other trademarks
Microsoft and SQL Server are either registered trademarks or trademarks of Microsoft
Corporation in the United States and/or other countries.
Trademarks that appear in this document are used only to the benefit of the trademark
owner, with no intention of trademark infringement.
65
NOTICES
How to report a security vulnerability

For the purpose of submission, a security vulnerability is defined as a software defect or
weakness that can be exploited to reduce the operational or security capabilities of the
software.
Honeywell investigates all reports of security vulnerabilities affecting Honeywell
products and services.
To report a potential security vulnerability against any Honeywell product, please follow
the instructions at:
https://honeywell.com/pages/vulnerabilityreporting.aspx
Submit the requested information to Honeywell using one of the following methods:
• Send an email to security@honeywell.com.
or
• Contact your local Honeywell Technical Assistance Center (TAC) listed in the
“Support and other contacts” section of this document.
NOTICES
Support and other contacts

For technical assistance, contact your nearest Honeywell office.
67
NOTICES
Training classes
Honeywell holds technical training classes on Enterprise Buildings Integrator. These
classes are taught by experts in the field of building control systems. For more
information about these classes, contact your Honeywell representative.
Index
A Life Safety 64
overview 59
Access and Control Security Guide 8 scheduling 61
access cards 50 Building Management Guide 8
access control
alarms 52
areas 28 C
concepts 54 card readers
downloading card details 52 described 54
levels 57 downloading card details 52
overview 52 cardholders
points 54 database information 50
zones 55 management of 50
access points 54 reporting 58
Advanced Alarm Management 44 cards
Advanced Configuration Guide 8 access levels 57
Alarm Paging 63 downloading access details to readers 52
alarms photos 50
access-related, managing 52 charts 45
Advanced Alarm Management 44 Cloud Connector 17
described 42 companion products 37
responding to 42 Configuration and Administration Guide 8
shelving 43 control
analyzing history card access 52
overview 46 controllers
trend displays 45 connecting 20
archiving interfaces to EBI 20
event 47 modem-connected 20
history 47 custom displays 24
areas 28 custom reports 45
B D
Backup and Restore Guide 8 database, controlling access to 28
building access, controlling 52 Diagnostic Framework, described 48
building management Diagnostic Guide 8
accessing HVAC information 60 direct serial connections to controllers 20
alarm paging 63 displays
69
INDEX
custom 24 indirect serial connections to controllers 20

described 24 Installation Guide 8
system 24 Integrated Microsoft Excel Reports 45
Distributed System Architecture (DSA) 18 Integrated PhotoID 50
documentation set 8 Interface and Controller references 8
downloading card details to readers 52 Internet Explorer 26
duress login 28
E L
levels, access 57
EBI Web Server 26
Life Safety Management 64
electronic signatures 30
lifts (elevators), control of 55
elevators, control of 55
login, duress 28
Energy Manager 37
event archiving 47
EXCEL 5000 60, 61 M
exchanging data with other applications 31
extended history 46 Microsoft Excel
Data Exchange
described 31
F modems, using 20
fast history 46
Fire Management 64
fire panels 64 O
overview 16 occupancy reporting 57
flexible points 19 ODBC Data Exchange
floor points 55 described 31
ODBC driver
G described 32
OPC
Global Schedules 61 Alarm and Event Server 32
graphs 45 client interface 32
Data Access Server 32
H Integrator 32
Hardware and Point Build Reference 8 operator-based security 28
history
archiving 47
overview 46
P
types of 46 paging, alarm 63
HMIWeb browser 26 Perimeter Global Anti-Passback 57
Honeywell Digital Video Manager 37 periods, time 57
HVAC PGAP 57
information, accessing 60 Pharmaceutical Compliance option 16
overview 59 Photo ID, Integrated 50
photographs on access cards 50
point servers 19
I points
Import and Export Guide 8
INDEX
access 54 signatures, electronic 30

controlling access 29 standard history 46
flexible 19 standard points
floor 55 described 39
products, companion 37 standard reports 45
Station-based security 28
R Stations
controlling access to 28
R7044 60, 61 described 24
Reception Management Guide 8 duress login 28
redundancy electronic signatures 30
server 17 modem-connected 20
terminal servers 20 supervisory control 38
Remote Access Deployment Guide 8 system data, analyzing 45
reports
cardholder 58
described 45 T
occupancy 57 terminal servers
responding to alarms 42 connecting controllers 20
described 20
S server redundancy 20
scheduling 61 time periods, access control 57
security trends 45
electronic signatures 30 troubleshooting 48
operator 28
Station
operator-based 28
V
Station-based 28 visitor management 51
Security Management, overview 49
Server Scripting Reference 8
servers
X
Distributed System Architecture (DSA) 18 XLS1000 64
point servers 19
redundancy 17
shelving Z
alarms 43 zones 55
signatures, cardholder 50
71
INDEX

EBI R500.1 EBIOverview PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

EBI R500.1 EBIOverview PDF

Uploaded by

Copyright:

Available Formats

Enterprise Buildings Integrator

About this guide ........................................................................................................................... 7

Honeywell Energy Manager ........................................................................................................ 37

Support and other contacts ....................................................................................................................... 67

This guide provides an overview of Enterprise Buildings Integrator (EBI). It describes

The EBI documentation

Access Control Configuration Guide

Import Export Guide

Building Management Guide

Configuration and Administration Guide

Advanced Configuration Guide

HMIWeb Display Building Guide

Quick Builder Reference/Help

Remote Access Deployment Guide

Reception Management Module Guide

Reception Web Module Guide

The Backup and Restore Guide

Application Development Guide

Server Scripting Reference

Hardware and Point Build Reference

Interface and Controller References

Title Documentation Set Print PDF Context-sensitive help

Title Documentation Set Print PDF Context-sensitive help

The versatility of EBI

Remote Access Internet Access

Figure 1: Redundant-Server System with Security, Building and Fire Management

Honeywell Security Manager

Honeywell Building Manager

Honeywell Life Safety Manager

EBI and Pharmaceutical Compliance

EBI Cloud Connector

Primary Server Backup Server

Figure 2: Typical Redundant Server System

Distributed System Architecture

Master Control Center

Figure 3: Typical Geographically-dispersed System

LON Bus LON Bus LON Bus Honeywell or

Figure 4: An EBI System with LonWorks Point Servers

Figure 5: Controllers Connected Directly to the Network

Indirect serial (terminal server) connections

Terminal Server Terminal Server

Figure 6: Typical System with Terminal Servers

Direct serial connections

Terminal servers and server redundancy

Primary Server Backup Server

Figure 7: A Terminal Server in a Redundant Server System

Figure 8: A Typical System Display

Figure 9: A Typical Custom Display

Station on mobile tablets

Facility Model, Organization Model, and scope of responsibility

Point control restrictions

Exchanging data with other applications

Microsoft Excel Data Exchange

ODBC Data Exchange

EBI OPC Client Interface

EBI OPC Data Access Server

EBI OPC Historical Data Access Server

EBI OPC Alarm and Event Server

EBI OPC Data Transfer

Advanced customization capabilities

Integrating with business processes

Integrating with third-party hardware

Honeywell Digital Video Manager