Specifications

LENEL
®
- A UTC FIRE & SECURITY COMPANY FACILITY COMMANDER™ v2.2.3 GUIDE SPECIFICATIONS
[PROJECT NUMBER]
[DATE]
[PROJECT NAME]
[PROJECT LOCATION]
[AUTHOR]
[FILE NAME]
INTEGRATED AUTOMATION INSTRUMENTATION & TERMINAL
DEVICES FOR ELECTRONIC SAFETY & SECURITY SYSTEMS
25 38 00 - 8
LENEL CONFIDENTIAL INFORMATION – For use by Lenel-authorized VARs, prospective or existing Facility Commander users
and their respective authorized consultants. All other third-party use is prohibited without Lenel’s written permission.
2) Graphical user interface shall be English and [Spanish] [French]
[Portuguese] [Dutch] [Italian] [German] [Russian] [Arabic] [Korean]
[Japanese] [Chinese Simplified] [Chinese Traditional]
2. Web Browser Client
a. System Configuration
1) Define and configure devices
2) Define event to action mappings
3) Identify device events in any subsystem to trigger single/multiple actions in
all other subsystems
4) The integration platform shall extract data from subsystem databases
whenever possible, eliminating repeat data entry
b. Reports for system configuration and transaction history data shall be accessed
through the browser interface
c. Administration Features
1) Create facilities
(a) Define each device to be a member of one or more facilities
2) Assign operator facilities
(a) Assign one or more assigned facilities
(b) Operators shall be able to work simultaneously in all of their assigned
facilities
3) Define operator permissions
(a) Operator action limited by the permission profile for the operator in a
particular facility
(b) Ability to add, modify or delete devices and other records (such as
servers, workstations, and operators) based on permissions
4) The system shall have a documented System Backup and Recovery
procedure
3. Command and Control Client
a. General
1) Log-in sessions shall carry the facilities and permissions associated with the
operator.
2) Valid log-in shall activate client launcher, from which the individual
applications can be run.
3) Allow multiple instances of each application to be launched.
4) Provide a facility filter mechanism allowing operators to filter the facilities "in
play."
(a) Allow facility filtering per instance.
5) Allow user-named filtered window applications.
(a) Re-launch user-named filtered window applications on request.
6) Provide window size and position memory for each instance of each
application window.
b. Symbol Editor
1) Provide a tool to associate symbols to devices for use with graphical maps.
(a) System shall provide a series of default graphic images.
(b) System shall support the use of customized graphic images that are in
JPG, GIF, or animated GIF formats.
(c) Variable sizes shall be supported: 16x16, 24x24, or 32x32 pixels.
2) Link different graphic images (icons) with devices types, such as:
(a) Access points.
(b) Camera types.
(c) Digital inputs.
(d) Logical inputs.
(e) Digital outputs.
(f) Intercom stations.