Advanced - 7.6 - February 2020 PDF

Advanced Access Control
Welcome to Lenel Training
1
A CARRIER COMPANY CONFIDENTIAL AND PROPRIETARY
Introductions
Who ? ( You and your employer ?)
Where ? (Are You From ? )
What ? ( Is your Role and Experience with Regard

to Access Control Hardware and OnGuard ?)
What are your expectations for this course?
2
Training Information
Lenel Training Information
– Parking
– Building Access
• Badge access to the building
– Facility layout
• Bathroom location(s)
• Designated smoking area(s)
• Coffee, water, more…
– Breaks and Lunch Schedule
– Wi-Fi access
3
Course Overview
Course Name: Advanced Access Control

Duration: 3 days
4
Course Objectives
By the end of this course, you will be able to:

– Identify advanced features of OnGuard and select
suitable configurations for various different system
topologies
– Configure Access Series (LNL) hardware components
for advanced functionality
– Program software functions in OnGuard to support
advanced functionality
5
Course Objectives
Course objectives (continued)

– Troubleshoot advanced software programming issues
and identify causes and solutions to common
problems
– Describe and demonstrate operation of the advanced
functions in Alarm Monitoring
…as evidenced by successful completion of all
course modules, active participation in class
discussions/examples, and 90% attendance to all
class sessions.
6
Course Exam and Certification
An exam will be issued and a passing grade required

– Visit www.lenel.proexams.com to access the exam
• Enter the same username and password you use to access
Partner Center
– For the initial exam, the passing grade is 70%
– Up to two make-up exams will be issued as needed
• Passing grade is then 80%
– You have 30 days to complete the exam from the date of
issue
– Pause the exam as often as needed
– Questions can be bookmarked
– Email will be sent after 20 days, as a reminder, if the exam
has not been completed
7
After the Advanced Access course has been taken
and the exam has been completed with a passing
score, the Lenel Certified Professional level will be
achieved
Your certificate will be available as a .PDF at
https://partner.lenel.com
8
Course Agenda: Day 1
Single Sign On FormsDesigner Lite

Segmentation Monitoring Options
– Segment(s) creation Device Groups
– Segmentation Options
Action Groups
• Card Formats
• Badge Types Scheduler
• Cardholders Local IO
• Segment Groups
Global IO
• Access Levels
• List Builder
9
First Card Unlock Invalid Badge
Double Card Unlock / Area Interlock
Toggle Anti-Passback
MapDesigner – Local Anti-Passback
Basic Alarm – Global Anti-Passback
Configurations
Advanced Alarm
Configurations
– Global Output Server Service
(GOS)
• Manual and Automatic emails
– Acknowledgement Actions
– Failure to Acknowledge
• Alarm Highlighting
• Alarm Forwarding
10
Mustering Custom End of Line

Area Access Manager Resistance
Destination Assurance Debounce
Selective Cardholder Hold Time
Download Elevator Control
– LNL-1320 Elevator Solution
– LNL-1300 Elevator Solution
– Day Mode
11
Single Sign On
12
Single Sign-On
Allows the user to log on to any OnGuard desktop
application automatically using the current
Windows log in account
– Manually logging in to OnGuard using the OnGuard Internal
Account User name and Password is still available, if desired
– OnGuard users may have an internal account and/or a directory
account link
13
Internal Account
The Internal Account is what you have been using
to log in to OnGuard up to this point
14
Single Sign-On
Internal Account
– A user account where the authentication information
is saved within the OnGuard system database
Directory Accounts
– A user account where the OnGuard user is linked to
the windows log in account
– The authentication information is controlled by the
directory service selected
15
Single Sign-On Directory Configuration
Directory must first be configured
– System Administration > Administration >
Directories
– Directory Services Template Types
• LDAP
– Lightweight Directory Access Protocol
• Microsoft Active Directory
• Windows NT 4.0 domain
– A precursor to Active Directory that handled domain
directory management prior to Windows 2000
• OpenID Connect
– Third party authentication of a user via a URL
• Windows Local Accounts
– Copy existing directory
• Uses previous configuration as a starting template
16
Select domain hostname

– Other default parameters will automatically be
populated
• Name – {Domain Name}
• Port - 389
• Start Node – Node under which all accounts exist
– SSL (Secure Socket Layer)
• Enables data encryption
17
Single Sign-On Authentication
Determines how OnGuard will authenticate to the
Windows user accounts
– Anonymous
• Directories may be set up to allow anonymous access
– Active directory default is to not allow anonymous access
– Current Windows account
– Explicit
• Account logon information
– Domain\User name
– Password
18
Advanced Configuration for LDAP directories (Not

available for Windows NT4 Domains or Windows
workstations)
– Account class (user)
– Account category (person)
– Account attributes
• ID attributes (objectsid)
• User name attributes (samaccountname)
• Display name attributes (displayname)
• E-Mail attributes
19
OnGuard User Accounts
Open Administration > Users to link your windows
log in account to your OnGuard User account
– Use the filter capabilities for refining the results
20
Auto Single Sign-On
Log in to any OnGuard desktop application
– Launch the OnGuard desktop application
– If the application is already open simply use the key icon or the
Application menu option to log off / on
Auto Logon will be started
– To bypass the auto logon, press the Shift Key and log in
manually using an Internal Account user name and password
21
Segmentation
Documentation Reference
System Administration User Guide | Appendix E
22
Segmentation
Segmentation is the process of dividing an access

control database into smaller subsets known as
Segments
– Basic segmentation includes segmenting hardware
and users
• Note: Once segmentation is enabled, it cannot be disabled
– It’s important to backup the database prior to segmentation
• Hardware can only belong to one segment at a time
– Hardware can be moved to another segment
• Users can have access to one or many segments or segment
groups
23
Segmentation
Segmentation Options
– Additional segmentation options that can be
enabled/disabled
• Card Formats
– For organizations who need many different card formats
beyond the 8 per system (16 card formats in 7.4)
– Allows 8 card formats per segment (16 card formats in 7.4)
• Badges Types
– For organizations who wish to control user and cardholder
access to certain badge types
• Cardholders and/or Visitors
– Useful when cardholders reside in their own segment or
additional segments
24
Segmentation
Segmentation Options
– Additional segmentation options that can be
enabled/disabled
• Segment Groups
– Allows management of multiple segments simultaneously
• Access Levels
– Intended for users who need to assign access levels that
belong to another segment
• List Builder
– Allows List Builder entries that are segment specific to be
customized and viewable in a single segment, segment group
or all segments
25
Segmentation
Why Segment?
– Hardware Limitations
• Since Access Panels are limited in memory, segmentation
allows segment related information to reside on that access
panel
• Each segment can determine what features and options to
choose for their panels
• Some examples
– Cardholders
– Access Levels
– Badges
– Hardware limits
– Anti-passback options
26
Segmentation
Why Segment?
– Manage User Access
• Users are assigned to one or more segments
• Users have visibility of objects that only belong in their
segment(s) and objects that are system-wide
– More efficient Cardholder downloads
• For high cardholder populations
• Only badges that have access to a segment are downloaded
to the access panel in that segment
27
Segmentation
Scenarios
– Landlord / tenant scenarios where one building
houses multiple companies and the landlord controls
the security of the building
– A single company with multiple large divisions who
wish to manage users, cardholders and features
within their own segment
• Users and Cardholders can belong to multiple segments or
segment groups
28
Segmentation
Initial objects assigned to each segment

– Users
– Access Panels
– Access Levels
Adds additional levels of permissions to be
assigned to objects
– “<All Segments>”
– “Segment” (Individual)
– “Segment Groups”
29
Segmentation
<All Segments>
• Any user can view an <All Segments> records/objects
• Only <All Segments> users can add, modify, and delete <All
Segments> records/objects
Segment (individual)
• Users can only add, modify, and delete records/objects that
have that same segment assignment as they do.
Segment Groups
• Users can add, modify and delete records/objects that are
assigned at least one of the segments that are contained
within the segment group assigned to the user.
30
Segmentation
Segmentation allows an additional level of

permissions to be assigned to an object
– Full control
– View only access
– No Access
31
User and Object Assignments
When an <All Segments> user logs into <All

Segments>, that user can view, add, modify and delete
any object with any segment assignment*
User User Logged Object
Assigned User 1 In Segment Object 1 Assigned
Segments Segments
<All Segments> User 2 <All Segments> Object 2 <All Segments>
Segment 1 Segment 1 Segment 1
User 3 Object 3
Segment Group Segment Group Segment Group
User 4 Object 4

User 5 Object 5
*Provided that the user has the proper user permissions to do so.
32
When an <All Segments> user logs into a segment, they can

add, modify and delete only those objects in that segment. The
user can also view any object that belongs to <All Segments>
or an additional segment that matches their segment.*
Segments Segments
User 3 Object 3
User 4 Object 4

User 5 Object 5
33
A user assigned to a single segment can add, modify and delete only
those objects in their segment . The user can also view any object that
has an <All Segments> assignment or an additional segment that
matches their segment.*
Segments Segments
User 3 Object 3
User 4 Object 4

User 5 Object 5
34
When a user logs into their segment group, they can add, modify and
delete only those objects that belong to that segment group. The user
can also view any object that belongs to <All Segments> or an
additional segment that matches any segment in their segment group.*

Segments Segments
User 3 Object 3
User 4 Object 4

User 5 Object 5
35
When a user logs into a segment within a segment group, they can
add, modify and delete only those objects that belong to that segment.
The user can also view any object that belongs to <All Segments> or
an additional segment that matches the segment that the user has
logged into.*
Segments Segments
User 3 Object 3
User 4 Object 4

User 5 Object 5
36
Additional <All Segments> Rules
System wide settings can only be configured by

an <All Segments> user
– BadgeDesigner and FormsDesigner
– Archiving Events and Transactions
– System Cardholder Options
– General System Options
– User segment access permissions must be modified,
otherwise, all users will have <All Segments> access
Note: Being an <All Segments> user is not the same as

having access to each individual segment
37
Pre-Segmentation View
Examine the following forms

– Segments
• Only Segment Options tab available
38

– Users
• Segment column and Segment Access sub tab not available
39

– System Options
• Can be modified by any user
• All tabs on this form are controlled system-wide
40

– Access Panels and Access Levels
• No columns designating segment membership
41

– Monitor Zones
• No segment membership designation
42
Enabling Segmentation
Once enabled, Segmentation cannot be disabled
Default segment is created for placement of pre-

existing records and all users belong to <All
Segments>
43
Post-Segmentation View

– Segments
• Segments and Segment Groups tabs added
44

– Users
• Segment column and Segment Access sub tab available
45

– System Options
• Can only be modified by an <All Segments> user
• All tabs from Hardware Settings and onward controlled per
segment and removed from System Options
46

– Access Panels and Access Levels
• Segment columns designating segment membership
47

– Monitor Zones
• Segment membership displayed
48
Adding New Segment
Segments may be added independently or to a

new or existing segment group
– A segment is created by the New Segment Wizard
– Hardware may be moved to new segment
– Existing data may be copied to new segment
• Access levels and groups may be copied or moved
49
Segmentation Wizard
Unique segment name

Segment group assignment*
Move panels from another segment*
– Hierarchy of readers and alarm panels will be maintained
– Perform full panel download after move
– If “Do not copy records or move panels from another
segment” is chosen then all associated access levels will
not be copied and lost.
* - Optional
50
Segmentation Wizard
51
Segmentation Wizard
52
Segmentation Wizard
Copy records from another segment*

– Select records to be copied
Copy empty access levels and groups*
– Allows creating a similar access level/group scheme
in the new segment
Cleaning up source segment*
– Removes access levels and groups that may become
empty after moving hardware
53
Segmentation Wizard
54
Segmentation Wizard
55
Segmentation Wizard
56
Segmentation Wizard
57
Segmentation Wizard
Prefix or append text to the names of records for

unique identification
– Record names are enforced to be unique per
segment
Define segment hardware settings
58
Segmentation Wizard
59
Segmentation Wizard
60
Segmentation Wizard
61
Post-Segment Added View
62
Features Controlled Per Segment
System wide limits are now per segment

– Holidays – 20-255 supported
– Timezones – 127-255 supported
– Access levels – 255-31999 supported
– Badge number length – 7-18 digits supported
– Number of elevator floors – 1-128 floors
63
– Access level assignments per badge

• Maximum of 128 access levels supported
• Total levels
– Level allowing no activation dates
– Level allowing activation dates
– Anti-Passback
– User Commands
– Access Levels / Assets
64
65
Segmenting Hardware
Segmenting Access Panels

– All downstream devices are automatically given the
ISC’s segment assignment and can’t be changed
– Pre-segmentation
• Configured hardware usually receives assignment during the
segmentation process
– Post-segmentation
• Configured hardware is assigned a segment during the add
hardware process
• Hardware segment assignment can be modified
66
Modifying Access Panel Segment
Assignment
67
User Segmentation
Initially, users are assigned to <All Segments>.

– User segments may need to be modified to
accommodate your customers needs
– Specific segment assignments will restrict
permissions to view objects in other segments
68
User Segmentation
69
Advanced Segmentation
Segment Options
– Card Formats
– Badges via Badge Types
– Cardholders or Cardholders and Visitors
– Allow segments to belong to more than one segment
group
– Access level assignment
– Non-system List Builder lists
70
Advanced Segmentation Features
Additional control over objects that belong to

multiple segments
– Primary Segment
• Primary segment assignment can be either an <All
Segment>, an individual segment or a segment group
• Users can add, modify and delete objects and records with
the same segment assignment
– Additional Segment
• Additional segment assignment can be either an individual
segment or a segment group
• Users can only view/use objects and records in the additional
segment
71
Card Formats Pre-Segment
72
Card Format Segmentation
Card Formats become assignable per segment

– Each segment may now have up to 8 unique card
formats
• 16 card formats starting in 7.4
– Useful for organizations that require many different
card formats
Card formats that belong to <All Segments> will
reserve a format for every segment
73
Card Formats Post-Segment
74
Badge Types Pre-Segment
75
Badge Type Segmentation
Option to segment badge types allows an

organization to control
– Which users have access to certain badge types
configurations
– Which users can only assign access levels to
cardholders who have been assigned a certain badge
type, e.g. a user who only has access to visitors or
contractors
76
Badge Types Segmentation
Badges controlled by Badge Type

– Pre-Segmentation
• Users can add, modify, and delete all badge types*
• Users can add, modify, and delete cardholder badges*
• Users can add, modify, and delete access levels from
badges*
– Post-Segmentation
• Badge Types are initially assigned Primary = <All Segments>
– Only <All Segments> users can add, modify, delete badges*
• Badge Types are initially set where Available to All = NO
– Users can only add, modify, and delete access levels from all
badges*
*Provided that the user has the proper permission level to perform this task
77
Badge Types Segmentation
– Available to All (No Segment Restrictions)

• Only <All Segments> Badge Types can be ‘Available to All’
• Only <All Segments> users can edit the Badge Type itself
• Allows users to add, modify, and delete cardholder badges of
that type as well as access levels
– Primary and Additional Segments
• Users with Primary Segment (or <All Segments>) access can
add, modify, and delete badge types or cardholder badges.*
• Users with Additional Segment access can ONLY assign or
remove access levels from their segments to existing badges
*Provided that the user has the proper permission level to perform this task.
78
Badge Types Post-Segment
79
Cardholder Pre-Segment
80
Cardholder Segmentation
Segment Cardholders
– Allows Cardholder permissions to be controlled based
on segment access
– Segment Visitors
• Allows Visitor permissions to be controlled based on segment
access
• Visitor segmentation can only be done if cardholders are
segmented
81
Access to Cardholder/Visitor controlled by

Segmentation
– Pre-Segmentation
• Users can add, modify, and delete all cardholders*
• Users can add, modify, and delete cardholder badges*
• Users can add, modify, and delete access levels from
badges*
82
Cardholder Post-Segment
83
– Post-Segmentation
• Cardholders are initially assigned Primary = <All Segments>
• Only <All Segments> users can add, modify, delete
cardholder records*
• Any user can view <All Segments> cardholder records*
• Any user can assign access levels from their own segment to
existing badges*
– Cardholders can be assigned primary and additional
segments
• A users access to these cardholders is then based on their
segment
84
User’s Segment = Cardholder’s Primary
Segment
When the user logs into a segment that is the

cardholder’s Primary Segment, the user is able to
– Add, modify, and delete cardholders associated with the Primary
Segment
– Add, modify, and delete badges, assets, network accounts
– Capture multimedia
– Print and encode badges
– Assign Access Levels
– Modify Guard Tour group assignments
– Issue ‘One Free Pass’ for anti-passback
– Execute an APB move badge
– Display global APB areas
85
User’s Segment = Cardholder’s Additional
Segment
When the user logs into a segment that is the

cardholder’s Additional Segment, the user is able
to
– View the cardholder but not change the cardholder’s
personal information
– Modify access levels
– Issue ‘One Free Pass’ for anti-passback
– Execute an APB move badge
– Display global APB areas
86
User = <All Segments>
If the user is not an <All Segments> user, then the

user can only view <All Segments> objects and
add cardholders associated with the user’s
segment
87
Segment Groups
A segment group is a collection of one or more

segments
– Using segment groups can reduce management effort
and complexity
• For example, when a new segment is added to the system,
the administrator simply adds it to the appropriate segment
group. Users and cardholders with those groups assigned
are granted access to the new segment.
It is recommended to use segment group
assignments where possible, especially for users
and cardholders
88
Segment Groups
Allow segments to belong to more than one

segment group.
– A segment group may contain one or more segments
– A single segment optionally may be allowed in
multiple segment groups
• Determined in Segment Options tab
89
Segment Groups
90
Access Level Additional Segments
Allow access levels to be configured as

assignable by users in other segments
– Allows segment users to assign access levels from
other segments to their cardholders
– Access levels are assigned to other segments by the
original segment’s user
91
Access Level Additional Segments
92
List Builder Segmentation
List Builder Simple Lists can be filtered based on

segment
93
Only certain lists can have a segment assignment
94
System Lists cannot be segmented

– Badge Status
– Two-man Type
Non-System Lists can be segmented
– Building
– Department
– Division
– Location
– Title
– Reader Groups
– Visit Type
95
If you ADD an item already in use in another

segment, then the following error will be displayed
96
When viewing, adding, modifying or searching in

the Cardholder, Asset, or Visitor forms, the drop
down menu options will be filtered to show only
the available items based on segmentation.
– If the Cardholder’s current selection is something you
can’t view, <Restricted Entry> will be displayed.
97
FormsDesigner Lite
98
Cardholder Additional Features
FormsDesigner Lite
– Allows for cosmetic changes to the cardholder form
• Other forms can be altered too
99
FormsDesigner Application
Functionality controlled through the license
– FormsDesigner Lite
• Standard feature with OnGuard
• Allows cosmetic changes only
– Label changes
– Set Tab Order
– Move Fields and Labels
– FormsDesigner Full
• Requires an additional license (SWG-1210)
• Covered in an advanced Global Education course
Separate OnGuard application located in the
OnGuard program menu
100
Before Launching FormsDesigner
Everyone should be logged out of System

Administration or Alarm Monitoring
– No changes can be made in these programs while
someone is using FormsDesigner
– The programs may be open, but it is not
recommended
FormsDesigner User Guide as a reference
101
Before Launching FormsDesigner
You must backup your database
– You will be prompted to confirm you have done so
– Once saved modifications cannot be undone
– This protects against unforeseen problems such as
• Power Outage
• Network Problems
• Database Issues
102
Using FormsDesigner
When presented with the Open Form screen,
please select the appropriate choice then press
OK
The most common choice with FormsDesigner
Lite would be Cardholder
103
FormsDesigner Navigation
Form Design Layout
Object List
All Viewing Permanent Area
Database
Info Window Custom Area
104
Object List
– Lists all objects currently defined in the system
– Allows for easy selection of objects
Database Information Window
– Lists the database tables and fields
Form Layout View
– Forms look as they will within their respective
applications
105
All Viewing Permanent Area

– This appears at the top and right hand side of all
cardholder pages including the reports tab
Custom Area
– This is where user configurable objects appear only
on the cardholder page
106
FormsDesigner Lite
Typical Cosmetic Changes

– Change field labels object text to match country
requirements, such as zip code, state, etc.
– Relocate fields on a page
– Change the tab order when adding cardholders
107
Label Object
Double click on the label to be updated
Update the label text to the appropriate value
108
Field Location
Fields may be moved within the chosen screen

– Select the field as shown, then drag to the desired
location
– Be careful not to place one field on top of another
– Keep the field and field labels together
– Only fields in the custom area should be moved
109
Finalizing The Layout
Alignment Tools
– Allow objects to be
properly aligned
– Horizontally or Vertically
– Carefully select
appropriate fields for
alignment
– Toolbar located at the
bottom
110
Set Tab Order
Speeds up copy-typing
from lists Step 1
– Sets the order in which

the cursor moves from
field to field when the
user tabs through them
Step 2
on a page
– Click on the fields in the
order required
– When done, select Save
Step 3
and Exit Tab Mode
111
Saving Changes
With FormsDesigner Lite the only option is to save

cosmetic changes
– This does not affect the data in the database
– Log back in to System Administration and review the
results
112
FormsDesigner Lite – Knowledge Check
Knowledge acquired in this section should

include:
– Understanding the capabilities of FormsDesigner Lite
– How to change a field label
– How to move fields / labels around
– How to adjust Set Tab Order
– How many OnGuard users are allowed to log in to
FormsDesigner at the same time (in a typical
environment)?
113
Monitoring Options
114
Monitoring Options
Monitoring Options allows an Alarm Monitoring
operator to double click on an icon to execute a
selected command
– Operators can execute the command from the system
tree or a map
Only one command per Icon Type for all operators
The configuration is set under Monitoring >
Monitoring Options
115
Monitoring Options
Your instructor will select the Reader icon and set
the command to Open door(s)
Log off / on of Alarm Monitoring once this is done
Double click on any reader icon in the system tree or
on a map to observe the outcome
– Under the Options menu, Execute Command on Single Click can
be selected
116
Device Groups
117
Device Groups
Device Groups allow for mass control, in Alarm
Monitoring, of the hardware components
contained within the group
– Useful for reader lock downs, activate/deactivate outputs, or
mask/unmask various inputs
– Use Monitor permissions groups to control usage of device
groups
Unlimited device groups can be created
Unlimited hardware can be added to each group
Group types are:
– Reader Group
– Input Group
– Output Group
118
Reader Device Groups
Go to Access Control > Group
On the second tab, Device Groups, click on Add
Name the group and select Reader Group as the
type
119
Reader Device Groups
Checkmark the appropriate Readers, assign to
the right, and click OK
Readers may be grouped to provide control of
the following
• Online reader mode
• Masking and Unmasking of door forced and door held
alarms
• The testing of door forced open and access granted events
120
Input Device Groups
Click Add, name the
group, and select Input
Group as the type
Checkmark the
appropriate Inputs,
Assign to the right, and
click OK
Inputs may be grouped
to provide control of the
following
• The masking and
unmasking of alarms
• The testing of inputs
121
Output Device Groups
Click Add, name the group, and select Output
Group as the type
Checkmark the appropriate Outputs, Assign to the
right, and click OK
Outputs may be grouped to provide control to
activate, deactivate, or pulse the outputs
122
Device Groups in Alarm Monitoring
Open Device Groups in Alarm Monitoring under
View > Device Groups
Understand it is not possible to control device
groups that contain hardware not included in the
current monitor zone
123
Device Groups in Alarm Monitoring
Test the following by right clicking on the device
group:
– Change reader mode to lock for all readers in the group
– Mask / Unmask inputs in the input group
– Pulse all outputs in the output group
– Test Door Forced Opens / Access Grants
• There is no reporting capabilities for Test Modes
124
Device Group - Test Mode
125
Action Types
and
Action Groups
126
Action Groups Defined
An Action Group contains one or more Action

Types that will be executed simultaneously
An Action Group Library contains one or more
Action Groups
– The Action Group created is listed in the Action Group
Library
System Administration User Guide – Appendix A
lists all the available Action Types
LS Linkage Server is required
127
Action Group Library
Action Groups can be used in other System

Administration features such as
– Scheduler
– Global I/O
– Guard Tour
– Alarm Acknowledgement Actions
– Note: Not all Action Types are available in all

configuration locations
128
Action Group Library
Select Action Group Library under the
Administration program menu
Click on Add
129
Action Types
Click on Add to add the Action Type(s) to the Group
Select the Action Type
130
Action Types
Select the corresponding components or features
for the selected Action Type
Click OK to save
131
Action Types
Checkmark the appropriate Monitor Zone
Click OK
132
Action Group - Monitor Zone Configuration
Monitor Zones may be configured to include Action

Groups in the Alarm Monitoring system tree
The Action Group may be directly executed through
right click menu
133
Scheduler
134
Scheduler
Scheduler is useful to manage one time actions
such as a database download or unlocking a
reader for a once a month meeting in a conference
room
Action Types can be selected
– A description of each Action Type can be found in the System
Administration User Guide under appendix A
LS Linkage Server must be configured and
running
– Schedule does not reside on the Access Panel(s)
– If upstream communication is lost, scheduled item will fail
– Linkage Server is configured under Administration > System
Options
135
Scheduler Configuration
With the correct user permissions, Scheduler may
be launched from:
– System Administration > Administration > Scheduler
– Alarm Monitoring > View > Scheduler
136
Scheduler
Service Status indicates LS Linkage Server status
and Host Name is the computer running the service
Time Zone selection shows current time in a specific
world time zone
– For reference purposes only
137
Scheduler
Click on Add and select the Pulse Open Door
Action Type
Click Next to select your Server Room Reader
138
Scheduler
On the Schedule tab, select Recurring and click on
the Change button
– One time only can be selected and set with an appropriate date
and time
– Schedule can be Disabled using checkbox
139
Scheduler
Schedule the Occurrence
– Daily, weekly, monthly
Schedule the Frequency
– Occurs once or Occurs every
quantity of minutes or hours,
starting at and ending at
specific times
Schedule the Duration
– Start and end date
Schedule your action to
occur every one minute
140
Scheduler and Alarm Monitoring
Scheduler will attempt to
perform configured action
at scheduled time
– Failures will be logged and may
be examined by right clicking on
scheduled item
Right click to View Action
History
Right click to Disable
Action
141
Schedule Reports
Scheduled reports allows for selection of file

format output
142
Local I/O
143
Local I/O
Local I/Os automatically trigger
specified output action(s), called a
Function List, based on the selected
event(s) occurring
Local I/Os are confined to a single
access panel
– They do not span across multiple ISCs
Function Lists are configured per
access panel
– Up to 100 Function Lists are supported
per ISC
– These are stored on the ISC
144
Local I/O
Functions allow control of:
• Activating alarm panel outputs
• Activating reader outputs
• Masking/unmasking of alarm groups
• All Reader Lock/Set Mode
• Opening/closing areas
• Chaining multiple function lists together
• Dialing back to the host computer when upstream
communication for access panels is set to dialup
• Activating Two Man Area Control
• Unlocking readers or setting reader mode
• Testing for active alarms in alarm group
– Used in conjunction with Alarm Group unmasking to provide
intrusion detection panel functionality
145
Local I/O
The following functions were introduced in 2012 and
enhanced in 2013
Timezone Activate/Deactivate
– Temporarily activates a timezone until the next timezone interval occurs
– Temporarily deactivates a timezone until the next timezone interval occurs
Timezone Override
– Permanently activates a timezone until the release override occurs
– Permanently deactivates a timezone until the release override occurs
– Triggered by right clicking on the ‘Timezone Override’ Local I/O function in
the System Status window in Alarm Monitoring
– Ability to release the timezone override (choose Pulse)
• In OnGuard 6.5 the release override capability was not available
146
Local I/O
Timezone activate/deactivate function behavior
Timezone override function behavior
147
Local I/O
All Reader Lock/Set Mode
– All Reader Lock/Set Mode function allows the reader
mode for all readers on a specific controller to be
simultaneously controlled for a specific period of time
• 1 to 48 hour incremental range
148
Local I/O
All Reader Lock/Set Mode behavior
– Set true
• Sets all readers on the controller to Locked for the time
specified in argument 2
– Set false
• Sets all readers on the controller to the mode selected in
argument 1 for the time specified in argument 2
– Set pulse argument 1 mode selected
• Set all readers on the controller back to the online mode
configured in the reader configuration plus any timezone
changes
Note: The reader mode may be manually changed in Alarm Monitoring. This will
remove the locked override mode of the reader and will return the reader to the
selected reader mode
149
Local I/O
All Reader Lock/Set Mode puts the readers in an
‘Override Reader Mode’ which overrides the standard
reader mode
Any Timezones, Schedules, or I/Os that normally change the
reader mode will be ignored when the card reader is in Override
Reader Mode
Any programmed changes to the reader mode are tracked by the
access panel but not applied to the card reader
When the override is aborted or expires the reader mode, as
tracked by the access panel, will be restored
This applies to First Card Unlock and Double Card Unlock/toggle
features as well
150
Local I/O
Once the Function is selected then a
corresponding Argument(s) must be selected
Up to six (6) functions can be selected per List
151
Local I/O
Take note of the Function Behavior box listed at
the bottom
– Set True
– Set False
– Pulse
152
Local I/O
Select Local I/O under the Access Control program
menu
Click on Add
Name the I/O
Select the ISC
153
Local I/O
Select the Function
– Activate Reader Output
Select Argument 1
– Specific Reader
Select Argument 2
– Auxiliary Output
Repeat up to 6 times
Click OK
154
Local I/O
Local I/Os may be executed via:
– Alarm Monitoring by right clicking on the Local I/O
and selecting Execute
– Device Linkage (second tab under Local I/O)
– Scheduler
• Action type: Execute Function List
– Command Programming
– Instant Commands
– Area count
– Alarm mask group count
– Alarm Acknowledgment
155
Local I/O
Device Linkage options include:
– All alarm points
• Inputs
• Door Forced Open
• Door Held Open
– Communications loss to downstream devices
– Host communication loss
• Loss in communication to workstation running the LS
Communication Server
– Access activity
– Cabinet Tampers
– Power Failure
156
Local I/O
Input actions on state change can be configured to
– Do nothing
– Set true
– Set false
– Pulse
Based on the Function Behavior box on the
Function Lists tab
157
Local I/O
Select Access panel from the drop down list on the
second tab under Local I/O
Select a Device on the left side
– LNL-1100
Select a Function List on the right side
Click on the Link button
158
Local I/O
Select the appropriate Logical Event
– Each Logical Event can be linked to only one Function List
Select the appropriate Take Action(s)
– Do Nothing
– Set False
– Set True
– Pulse
Click OK
159
Local I/O
Device and Function are linked
To Modify or Remove the link, click on the link to
access the Modify Link or Remove Link buttons
– Double clicking on the link opens the tree to display specifics
contained within the link
160
Local I/O and Alarm Monitoring
Activate the Device (Input) to trigger the Function
List and view results in Alarm Monitoring
Activate the Function List manually by right
clicking on the function in the System Tree
161
Global I/O
162
Global I/O
Global I/O functionality allows linkage between
Access Panels and downstream hardware system
wide
– Configuration includes
• Global Linkage
• Input Event
• Output Action
– Utilizes the LS Linkage Server for Global I/O execution
• Global I/Os are not resident on the Access Panels
• Global I/Os are server based
163
Global I/O
Select Global I/O under Access Control program menu
Click on Add and enter a Name
164
Global I/O
Global Linkage
– World Time Zone
• Defines world time zone that the LS Linkage Server will use to
execute based on the OnGuard Timezone assignment
– Timezone
• Defines allowable times when Global Linkage will execute
based on world time zone
– Always
– User defined
– Never – Could be used to disable Global I/O linkage
165
Global I/O
Event Timestamp Tolerance
– Sets a user specified timeout period for a linkage
which indicates how long after an input is activated it
will remain valid and can cause an output action
• 3 Minutes is the default time
166
Global I/O
Logic correlation time period
– When creating a linked alarm
event (And Logic), set this to the
maximum number of seconds
between each event occurring
• This is a rolling time limit where the
time period resets after each
correlating event occurs
• Valid range 1-999 seconds
– Defaults to 10 seconds
– If each event transaction occurs
within the logic correlation time,
the output action is triggered
167
Global I/O
Click on Add to add Input Event(s)
– Event is required
• May individually add more inputs to be linked to same output
action(s)
168
Global I/O
Devices may be optionally assigned
– All field hardware
Badges may be optionally assigned
– One badge number per configuration
169
Global I/O: “And / Or” Logic
Requires two or more input (event) transactions in a
pre-configured time (Logic correlation time period)
in order to generate the output event(s)
– Not a state-based AND operation
• All inputs must report active, but do not have to remain active
• Inputs are ‘transaction’ based NOT ‘Alarm State’ based
170
Global I/O: “And / Or” Logic
Multi-layer AND/OR hierarchy may be created
– OR gates feeding an AND gate
– The AND gates feeding an OR gate
– Limited to OR-AND-OR relationship
171
Global I/O: “And” Logic Group
Two or more inputs must be selected, checkmarked,
to initially create an “And” Logic Group
– An OR logic group will also be automatically created
172
Creating Logic Groups
The automatically created ‘OR’ group represents
that the Input Event window was originally an ‘OR’
window
– It also allows you to follow the logic of any inputs
added to the window after the ‘AND’ was created
Logic Diagram
173
Global I/O: Multiple Logic Levels
Up to 3 logic levels may be created
“OR” logic group

allows multiple conditions
to trigger execution
174
Global I/O: Modifying Inputs in Logic Groups
Inputs may be dragged and dropped between logic

groups using a mouse
– As long as moving the input does not violate the logical
operation
• Example: There MUST always be at least 2 inputs in an
‘AND’ group
Logic groups may be deleted
– User will be prompted for keeping the inputs belonging to the
group
175
Global I/O
Click on Add to add
Output Action(s)
– Choices include
• Action Types
• Action Group Library
– Control action
• Action dependent on
selected item
Click OK to save Global I/O
176
Global I/O and Alarm Monitoring
Trigger the Global I/O Input Event
View the results and associated events in Alarm
Monitoring
177
Global I/O – Additional Output Actions
Deactivate Badge
– Deactivates any badge
based on a specified Input
Event(s)
• New Badge Status
automatically assigned
• Use List Builder to add more
Badge Status values
178
Local I/O may be linked to Global I/O when
Execute Function List is selected for the Output
Action
– Execute: True
– Execute: False
– Execute: Pulse
179
Grant / Deny Action Type

Launches pop-up on any access related event
Grant access or Deny access to the output action
reader selected
180
Generate Event
Custom text alarm generated in Alarm Monitoring
as an output action
– Useful for creating a custom alarm text for the
AND/OR linkage
181
Global I/O: Generate Event Text
Configuring event text
– Select configured text using dropdown
• Contents added in Text Library under Administration
– Events can be typed in the given area
• Automatically added to Text Library
182
Global I/O: Generate Event Text
Generate Event Text and Alarm Monitoring
Trigger Global I/O with Generate Event as an
Output Action to view the results
183
I/O - Knowledge Check
Knowledge acquired in this section should
include:
– Knowing the difference in functionality between a Local IO
and a Global IO
– How to add / modify a Function List
– How to link a Function List to a Device
– How to add / modify a Global IO
– How to create a Logic (and/or) Global IO
– Knowing the associated alarms and events in Alarm
Monitoring when using IO’s
– What service(s) is required for Global IO’s to work?
184
First Card Unlock
185
First Card Unlock
Referred to as ‘Snow Day’ functionality

– To keep a door secured in the event of a ‘snow day’
unless the first badge that has access to a reader
places the reader in unlock mode
The reader will change to unlock mode when the
first badge is presented by
– Any badge
– An authorized badge
• Based on access level permission
186
First Card Unlock
Option is enabled first at each ISC

Enabled on a per reader basis
– At the configuration of the reader
• This will be the default reader setting
Manually enabled through Alarm Monitoring
– Right click on the reader and select Reader First Card
Unlock Mode
Enabled during a timezone
– Configured under Timezone/Reader Modes
187
First Card Unlock
188
First Card Unlock
To unlock a reader by any valid badge

– Select First Card Unlock at the access panel
– Enable First Card Unlock
• In Alarm Monitoring, select a reader and enable Reader First
Card Unlock Mode or
• Configure a Timezone/Reader mode and enable First Card
Unlock at either the start or end of a timezone
– The first badge that has access to the reader will be
able to change the reader to unlocked mode
• Present the badge to the reader
• Open / close the door to unlock the reader
189
First Card Unlock
Timezone can be applied to determine when

reader will switch to first card unlock mode.
190
First Card Unlock
To unlock a reader by an authorized badge

– Select First Card Unlock at the access panel
– Enable First Card Unlock
• In Alarm Monitoring, select a reader and enable Reader First
Card Unlock Mode or
• Configure a Timezone/Reader mode and enable First Card
Unlock at either the start or end of a timezone
– Enable First Card Unlock Authority Required
• Reader settings
– Enable First Card Unlock Authority
• User Commands within Access Levels
191
First Card Unlock
To unlock a reader by an authorized badge

continued
– The badge that has an access level with First Card
Unlock Authority enabled will be able to unlock the
reader that is configured for First Card Unlock
Authority Required
• Present the badge to the reader
• Open / close the door to unlock the reader
192
First Card Unlock Authority
193
First Card Unlock
Other features can enable or disable First Card

Unlock by selecting Reader Mode within the Add
Action Wizard
– Global I/O
• Enabled as an output action
– Alarm Acknowledgment Actions
– Scheduler
194
First Card Unlock
195
Double Card Unlock/Toggle
196
Double Card Unlock/Toggle allows the ability to

alternate unlocking/securing an Access Series
reader
– Feature enabled on the Mercury Series 2 and 3
Access Series controllers
– Authority given in access levels
– Feature enabled on a per reader basis
197
Double Card Unlock/Toggle is a reader that is in

‘Override Reader Mode’ which overrides the standard
reader mode
Any Timezones, Schedules, Local I/O or Global I/Os that
normally change the reader mode will be ignored when the
reader is in Override Reader Mode
198
The default time that the reader will remain

unlocked is 1440 minutes (24 hours)
– The default time can be changed in the acs.ini file
• c:\Windows\acs.ini
• Start > run > acs.ini
199
– The described setting must be added to, or updated

in, the [CommunicationServer] section of the ACS.ini
configuration file on the machine running that
controller’s Communication Server
• LenelDoubleCardUnlockTime
– The amount of time that the reader will remain unlocked may
be configured through a ACS.INI setting on the LS
Communication Server workstation before reverting back to the
last secured mode
– LenelDoubleCardUnlockTime=1440 (in minutes)
» Default is 1440 minutes (24 hours)
200
Second time attempt must be performed within 5

seconds at the reader
– Same badge ID presented two times with proper
access and Double Card Unlock/Toggle authority
– The door position switch, DPS, (opening of door) has
no bearing on the feature
201
Reader modes supported when using Double Card

Unlock/Toggle
– Card only
– Card and PIN
– PIN or card (only if a card is used)
• The feature does not support entering a pin twice within five
seconds of each other
Unsupported modes
– Locked
– Unlocked
– Facility Code Mode
– Cipher Mode
– PIN / PIN
202
Access panel option

– Feature enabled on the controller
• System Administration > Administration > Access Control >
Access Panels
203
Reader setting
– Feature enabled on a reader by reader basis
• System Administration > Administration > Access Control >
Readers and Doors
204
Access level
permission
– Enables the feature to be
used by the cardholder
– Enabling the feature will
impact any readers that the
Double Card feature is
enabled
– Any badge that has an
access level with this
feature enabled will have
Double Card Authority
• As it is with all User
Commands
205
To release a reader that is in Override Reader

Mode, the following can be done
– Wait for the default timeout of 24 hours that is
configured in the acs.ini file
– Right click in Alarm Monitoring and change the reader
access mode
– Present the authorized badge twice at the reader to
put the reader back to the original mode
206
MapDesigner
207
MapDesigner
MapDesigner provides a straight forward way to
associate system hardware with a map in Alarm
Monitoring
– Detailed maps can be created which show all the
access control hardware
– Alarms can be configured to automatically display a
map
– Map icons may be used to control the alarm point by
right clicking on the icon
208
Icon Library
Displays all the icons and icon groups currently

available for use within MapDesigner
– New icons and groups may be added
– Icons may assigned to the groups
209
Icon Library
Devices in
MapDesigner can use
either a default icon or
an icon group
– Icon groups allow the
device to change the
way it looks on the map
based on the state the
object is in
210
Creating a Map
Steps to create a map

– Log on to MapDesigner
– Load a graphic file representing the map background
• Supported file formats include AutoCAD DXF
(.dxf), .JPG, .BMP and more
– Click and drag the hardware icons onto the map to
correspond with their physical locations in the facility
– Add a text label for the map
– Save the map to the database
211
MapDesigner Window
List Window
– Shows the current
system maps
– Shows the hardware
in the database
Map Window
– Displays either the
new map being
created, or the map
that is highlighted in
the list window
212
Customizing Maps
Place text on the
map
– Can be a title or
other reference
– Define the font,
style, size, and
color of the font
to be used
213
MapDesigner
Changing the size

of a device label
will have a global
effect on all the
labels for that map
– To have the label
text be hidden,
change the point
size to 1 and the
color to the
background color
214
MapDesigner
Map Icons
– Single icons may be used for all device states
– Icon groups use different icons for each hardware state
215
MapDesigner
Text can be added to appear when you mouse

over the device
– The text is only visible in Alarm Monitoring
216
MapDesigner
Map Hierarchy
– Maps can be linked together to highlight a special area on the
map
– You can double click to navigate through multiple maps
217
Maps and Monitor Zones
Assign a Default Map to a particular Monitor Zone
for easier access in Alarm Monitoring
– In System Administration select Monitoring > Monitor Zones to
configure
– In Alarm Monitoring to display default map, select View >
Default Map
218
Using Maps in Alarm Monitoring
Manually open the Map in Alarm
Monitoring under View > Map
Selection
– Maps can be configured to
automatically display when an alarm
occurs (next topic)
Maps can control hardware through
right clicking on the device just like
the System Status Tree
Maps display active alarms
Icons dynamically change
Mouse Over icon to view text
219
Using Maps in Alarm Monitoring
Right click
functionality
Alarm
notification
and Icon
changes
220
Map Printing
Maps are able to be printed by selecting

– The print icon from the toolbar
– The print choice from the File menu
221
Mouse Over Tool Tips
Alarm Monitoring maps

display a mouse over tool
tip window for map icons
– The tool tip window displays
• The device name
• The device status
• Any optional text to provide
additional information for Alarm
Monitoring operators
222
Alarm Configurations
223
Alarm Configuration
Default alarms, like door forced open, can be
modified to control the behavior of the alarm in
Alarm Monitoring
– Such as the priority level, audio, color, blinking,
acknowledgement actions, displaying a map,
popping up an associated camera, and more
224
Alarm Configuration
There are two main types of alarms
– System Alarms
• These are the default, system-wide alarms that comes with
every OnGuard install
– User Alarms
• These are alarms that are created and customized by an
OnGuard user
• User alarms can be hardware and event specific
225
Alarm Configuration
Any User Type (custom) alarm will override a
System Type alarm
– For example, the System type ‘Door Forced Open’
alarm will be generated and displayed in Alarm
Monitoring if there are no other custom, User type,
Door Forced Open alarms
– If there is a device specific custom alarm, ‘Door
Forced Open at the Entrance Reader’, then that alarm
is a User type alarm and will override the System type
Door Forced Open alarm
226
System Alarm
Let’s start by adjusting a System Alarm

Go to Monitoring > Alarms in System
Administration
Locate the Door Forced Open alarm
– Type in the beginning letters of the alarm name to find it faster
227
System Alarm
Modify the alarm and only enable Display Map

– The last OnGuard User to click OK will set the new
feature(s) for the alarm
228
System Alarm
Go to Alarm Monitoring and either log off / on or
refresh Alarm Monitoring by clicking on Options >
Refresh Alarm Configurations located at the bottom
– Any configuration changes that are made in any of the tabs from
the Alarm Configuration form in System Administration, requires a
Refresh in Alarm Monitoring
229
System Alarm
Cause a Door Forced Open alarm to occur and
observe the results in Alarm Monitoring
– Automatic Map Display can be turned off in Alarm Monitoring,
with the correct user permission, by clicking on Options >
Automatic Map Display
230
Custom Alarm
Now let’s add a custom (User Type) alarm for a Door
Forced Open on your Entrance Reader
We will be programming the following alarm
configuration features for this custom alarm
– Alarm definitions
– Alarm priority
– Text instructions
– Audio instructions and notifications
– Automatic email message when alarms are generated
• Emails can also be customized
– Acknowledgment Actions
– Failure to Acknowledge
• Forward Alarm
• Highlight Alarm
231
Alarm Configuration
Click on the ADD button and name your custom
alarm
232
Alarm Priority
Alarms may be prioritized
– 0 – 255 priority levels
– Higher the number = higher the priority
– Can be sorted by priority column in Alarm Monitoring
Set a unique priority number for your custom
alarm
233
Hardware Devices and Events
An alarm definition may be created for specific and
multiple devices
– Use the “_Default_” device to create an alarm for all devices in
the system (or segment)
Under Devices select your Entrance Reader and
choose Door Forced Open under the Event window
– Note you will have to checkmark the device(s)
234
Hardware Devices and Events
Be sure to assign to the right the device(s)/event
selections
235
Alarm Attributes
Alarms may be configured to have customized
attributes
– Use F1 (help) for feature information
236
Alarm Attributes
When selected under Alarm Definitions and when
the alarm is triggered…
– Display alarm
• Displays the alarm in Alarm Monitoring
– Print alarm
• A one-line entry will be printed to an activity printer at an
alarm monitoring workstation
• The activity printer will need to be configured via the
Workstations form
– Visual notification
• The Main Alarm Monitor window will be displayed in the
foreground on the Alarm Monitoring workstations
• Can be disabled in Alarm Monitoring
237
Alarm Attributes

– Display map
• Displays the monitoring map that contains the alarm’s
location
• Automatic Map Display can be disabled in Alarm Monitoring
– Video verification
• Displays live video and the cardholder photo in Alarm
Monitoring
238
Alarm Attributes

– Show cardholder
• Displays the Cardholder form in Alarm Monitoring
• Can be disabled in Alarm Monitoring
– Active alarm
• When the alarm is generated, it will be highlighted in the
Alarm Monitor window with the assigned priority color
• On a map, the alarm will animate the device icon and
indicate the location of the alarm
239
Alarm Attributes

– Alarm Aggregation
• Combines alarms of the same type and device and displays
as one line in Alarm Monitoring for easier viewing
• The alarm window columns will display the most recent alarm
info
• The number of times that the alarm has been generated will
also be displayed
• Aggregation is only applied to the Main Alarm window
– Users may perform a trace or open the Pending alarm window
to view all alarms as individual rows
240
Alarm Aggregation
Alarm Aggregation Off
Alarm Aggregation On
241
Alarm Attributes

– Must mark in progress
• Prior to acknowledgment, this is an indication that another
alarm monitor operator is handling the alarm
• When enabled, this automatically selects Must acknowledge
– Must acknowledge
• The alarm must be acknowledged prior to being deleted
242
Alarm Attributes

– Require login on acknowledge
• The alarm monitoring operator will be required to log in using
either their OnGuard Internal Account or Windows login (if
Single Sign-on is enabled) prior to placing the alarm in
progress and acknowledging the alarm
• This is used for logging transactions related to the alarm
– Must enter response on acknowledge
• The alarm monitoring operator must enter in notes in the
Notes field of the Alarm Acknowledgment window
243
Alarm Attributes

– Don’t delete on acknowledge
• After the alarm has been acknowledged, the alarm remains
in the Main Alarm Monitor window until it is manually deleted
by the alarm monitoring operator
– Operator can change response
• The main alarm operator is able to add additional notes to
the Alarm Acknowledgment window
244
Alarm Attributes for Custom Alarm
Select the following attributes for your custom
alarm and click OK to save
– Display alarm (enabled by default)
– Active alarm
– Aggregate alarm
– Must acknowledge
245
Priority Tab
Assigns a color to a range of alarm priorities for
visual identification
– A color can be assigned when the alarm is generated
– A color can be assigned to indicate that the alarm has been
acknowledged
– Range is from 0 - 255
246
Priority Tab
Add a color for your custom priority level number
247
Text Tab
Text instructions may be associated with an alarm
giving the operator a detailed description of what
to do
Text acknowledgment notes provide a consistent

set of responses when acknowledging an alarm
248
Text Tab
Hyperlinks may be
configured and used in
Alarm Instructions and
Acknowledgement Notes
– Hyperlinks can be created
at the location of where
the cursor is placed or by
selecting an existing word
– Right click and select
Insert Hyperlink
– The selected word will be
highlighted to indicate a
link
249
Text Tab
Add one Text Instruction and one Acknowledgment

Note
250
Audio Tab
Audio announcements may be used to alert the
alarm monitoring operator
– Notification
• Upon arrival of an alarm
– Instruction
• As part of the alarm acknowledgment process
– May use standard prerecorded .wav files
– Audio may also be recorded real time on this tab
251
Audio Tab
Add one Audio Notification using the .wav files

located in the class files folder
– Click on the Browse button to find an audio file and the play
button to hear the selected audio file
252
Alarm Configuration Tab
The following features can be optionally set on the
alarm configuration page per alarm
– Text instructions
– Audio instruction and notification files
– Password assignment for sensitive alarms
• Passwords can be assigned to either view and/or acknowledge
alarms
253
Alarm Configuration Tab
Assign your custom instructions and audio files to
your custom alarm
– It may be necessary to close the Alarms form and re-open it to
see the custom instructions in the dropdown list
254
Custom Alarm and Alarm Monitoring
Refresh Alarm Monitoring

– Log off/on or select Options > Refresh Alarm Configurations
Activate your custom alarm and observe the
results
– Aggregation
– Audio
– Text Instruction
– Click on Select button to view Acknowledgment notes
255
Alarm Configuration
Global Output Server Service
256
Messages Tab
Email messages can be assigned to a specific

alarm
– The standard email message that is sent includes
• The Alarm Description
• The Priority of the alarm
• The Date and Time in which the alarm is generated
• The Device that generated the alarm
Global Output Server Service (GOS) is a Lenel
service that needs to be configured and started in
order to send email messages
257
GOS
Global Output Server (GOS) routes manual and/or

automatic email requests from the Lenel
application to other 3rd party applications:
– SMTP servers for E-mail requests
• Simple Mail Transport Protocol is an Internet standard used
for sending email transmissions across Internet Protocol (IP)
networks.
Email server and email accounts must be set up
by email administrators prior to proceeding with
GOS configurations
258
Manual E-mail
Alarm * SMTP
Monitoring
GOS Server
Manual Process
(Alarm Monitoring Operator)
*
Comm
Server
OnGuard
* Service
259
Automatic E-mail
Alarm
Monitoring
Comm * Linkage* * SMTP

GOS
Server Server Server
* Service
260
Global Output Devices Setup
SMTP Server Settings configuration includes

– Friendly name given to the OnGuard email server
– Host is the name of the workstation the mail server is
configured on
– Port number (defaults to 25)
– Workstation running GOS service
– Authentication into the mail server
– Sender name and email address
261
E-mail (SMTP) Devices
262
Recipients
Recipients
– Creates a list of intended
recipients who will be
emailed when the event
is generated
Add recipient E-mail
address
– Device
• Created under SMTP
Server Settings
– Description
– Address (recognized by
E-mail server)
263
Sending E-mail
Information sent:
– Subject
• Defaults to include alarm description
– Message
• Alarm description
• Priority
• Date and time of event
• Device/badge generating event
264
Sending a Manual E-mail
Alarm monitoring station

– System wide connection to GOS
Able to be performed from any window displaying
events and alarms
Right mouse click on an alarm
– Select E-mail
– Custom messages can also be appended in the
subject and body of the email
265
Sending a Manual E-mail
A single event may be sent to multiple recipients
266
Sending an Automatic E-mail
Linkage server is used to route E-mail requests from
the Communication Server to GOS
– Typically a custom alarm definition is created for a specific
hardware device/event
– The definition is associated with E-mail messages and
recipients
– When configuring E-mail messages the default information
regarding the specific alarm will be shown in the subject
and body of the email if left blank.
• Otherwise any appended additional messages will erase default
information
– To use custom E-mail layouts use %[item] as shown in the
help files
267
System Administration > Monitoring > Alarms >

Messages tab
268
To access the help files for the parameters used

for custom automatic emails
– System Administration > Monitoring Alarms >
Messages tab
– Add a new email or modify an existing one to bring up
the ‘Add E-Mail Message’ form
– Hit F1 for Help
– In the Help form, place your cursor in the body of the
Message and click on the form
– An additional help file will appear with the custom
email parameters
269
Shown here are the

parameters that can be
entered to customize an
automatic email
For example, The
%alarmDescription has
occurred at %alarmTime
with a Priority of
%alarmPriority at
%deviceName.
When you trigger the
alarm, and the email will
be automatically
generated
270
Alarm Configuration
Acknowledgment Actions
271
Acknowledgment Actions tab
Allows an Action Type or Action Group to be

executed during the alarm acknowledgment
process
– For example, deactivating a siren upon the
acknowledgment of an alarm
Allows a Local I/O function to be executed during
the alarm acknowledgment process
– Execute Function List Action can be chosen from
Action Types
• Execute: True
• Execute: False
• Execute: Pulse
272
Acknowledgment Actions
Acknowledgment time limit may be configured to

prevent execution after a period of time lapses
– Zero sets no limit
273
Alarm Configuration
Failure to Acknowledge
274
Failure to Acknowledge Tab
One of two alarm handling options may be

configured per alarm definition
– Alarm highlighting
• Displays pop-up window after a pre-configured period
indicating that an alarm has not been acknowledged
– Alarm forwarding
• The alarm will be forwarded to another alarm monitoring
station after a pre-configured period
//System Administration/Administration/Monitoring/Alarms/Failure to Acknowledge
275
Failure to Acknowledge Tab
Dependent services
– The LS Communications Server is used to forward
hardware related alarms
– The LS Linkage Server is used for non-hardware
related alarms
• Mustering alarms
• DataConduIT events
//System Administration/Administration/Monitoring/Monitor Zones/Monitor Stations
276
Alarm Highlighting
Select alarm and select Highlight alarm under

Perform action
– System Admin > Monitoring Alarms > Failure to
Acknowledge
277
Alarm Highlighting
A dialog box will to pop-up in Alarm Monitoring

when the alarm has not been acknowledged in the
configured time frame
– Option to silence the reoccurrence of selected
alarm(s) for the snooze interval
• Snooze
• Snooze all
278
Alarm Highlighting
279
Alarm Forwarding
Alarm forwarding may be configured per alarm

definition
– The alarm will be forwarded to another alarm
monitoring station after a pre-configured period
– Uses the time received by the Alarm Monitoring
program
Create a monitor station and select the
workstation in which the alarm will be forwarded
to
– The workstation receiving the alarm will have to be
configured first, then configure the workstation that
will be forwarding the alarm
//System Administration/Administration/Monitoring/Alarms/Failure to Acknowledge
280
Alarm Forwarding
A monitor zone will need to be assigned to both

the workstation forwarding the alarm and the
workstation receiving the alarm
– The workstation receiving the alarm must have a
monitor zone that includes the originating
workstation’s hardware
Event routing may be used to control suppression
of events except when forwarded
– For the workstation receiving the forwarded alarm,
Event routing time zones do not affect forwarded
events
281
Alarm Forwarding
System Admin > Monitoring > Monitor Zones
282
Alarm Forwarding
System Admin > Monitoring > Monitor Zones >

Monitor Stations tab
Monitor Station receiving Monitor Station forwarding alarms

forwarded alarms
283
Alarm Forwarding
Select alarm and select Forward alarm under

Perform action
– System Admin > Monitoring Alarms > Failure to
Acknowledge
284
Alarm Forwarding
Alarm monitoring includes two columns that may

be configured to display
– Workstation
• Workstation that events are forwarded from
– Time received
• Date/time when event was received by the Alarm Monitoring
station the event was forwarded
Alarms forwarded to a monitor station who already
has received the alarm will not display the alarm a
second time
//Alarm Monitoring/Configure/Columns
285
Alarm Forwarding
Alarm Monitoring > Configure > Columns
286
Alarm Forwarding
Alarm icon indicates forwarding status in Alarm

Monitoring
– Routed In
• Workstation receiving alarms that are forwarded to them will
see the green arrow icon
– Routed Out
• Workstation forwarding alarms will see the blue arrow icon
– Failure to Route
• Alarms that fail to forward will see the broken red arrow
• This is typically caused when the workstation the alarms are
forwarded to is not logged into Alarm Monitoring
287
Alarm Forwarding
Set Forwarding Station

action type allows
alarm forwarding to be
scheduled
– Choose source
monitoring station
– Choose monitoring
station that events are
to be forwarded
• Set station to None to
configure the system to
stop forwarding
//System Administration/Administration/Scheduler
288
Alarm Configuration
Invalid Badge Event
289
Invalid Badge Event
Invalid badge events will have the badge status
appended to the event description for inactive
badges
– No status will be appended on an Invalid badge event
in Alarm Monitoring if that badge is:
• Active but has no access level assignment(s)
• Not in the database
290
Invalid Badge Event Configuration
‘Use invalid badge event text’ checkbox must be

enabled under Administration > Cardholder
Options
291
Add one (1) Inactive status under Administration >
List Builder > Badge Status
292
Under Monitoring > Alarms, the Invalid Badge
event can be modified to adjust the alarm
description display format
• Event Text Only
• Alarm Name Only
• Alarm Name – Event Text (default setting)
• Event Text – Alarm Name
293
Log off / on to Alarm Monitoring or refresh Alarm
Configurations under Options
Deactivate your badge by choosing one of the
added badge statuses
Present your badge to a reader to observe the
results in Alarm Monitoring
294
Invalid Badge Event:
Additional Event Configuration Options
Badge statuses requiring special handling will

need an exact entry match in the Text Library
Special alarm handling may be configured
– Alarm definition will need to include text
– Global I/O will need to include text as the trigger for
an action execution
295
Invalid Badge Event: Advanced Configuration
‘Use invalid badge event text’ must be enabled

under Cardholder Options
Inactive badge status’ can be customized in List
Builder
– Entry must match exactly entry in Text Library
Create Text Library entry
– Directly from Text Library or Alarm Definition or Global
I/O
Create custom alarm definition and/or Global I/O
Log off / on to Alarm Monitoring
– Refresh Alarm Configuration if custom alarm created
296
Invalid Badge Event: Text Library
297
Invalid Badge Event: Alarm Definition
298
Invalid Badge Event: Global I/O
299
Invalid Badge Events
Badge not in DB
– Invalid badge
Active badge with no access levels assigned
– Invalid badge
Badge marked inactive (with ‘Use invalid badge
event text’ enabled under Cardholder Options)
– Invalid badge – <inactive badge status>
• E.g. Invalid badge – Stolen
• E.g. Invalid badge - Terminated
300
Area Control
Area Interlock
301
Area Interlock
A multiple door interlock may be created using Local
APB
– For any door in the area if either the door strike is active or the door
is open, no other door may be opened to leave or enter the area
• Typically used with magnetic locks in order to secure the interlock
302
Area Interlock
This option requires

– LNL-2210, LNL-2220, LNL-4420 or LNL-3300 panels
– System configured with local areas
• Reader tab for APB is used for configuration
• If Global APB is enabled this option will be unavailable
When the area interlock is active, any additional
request for access will be denied
– An event will be indicated in Alarm Monitoring
– LED’s on the door reader(s) will show that access has been
disabled
303
Area Interlock
Configure areas
– System Admin > Access Control > Area
– Select ‘Interlock all doors in area’ for each area
configured for the interlock
• The area prior to entering the interlock area
• The interlock area
• The area entered once you leave the interlock area
Associate readers to areas
– Configure ‘Area entering’ and ‘Area leaving’
• Readers and Doors > Anti-Passback tab
304
Area Interlock
Interlock Area Events

– Interlock Area Busy
– Cannot Open Door: Interlock Area Busy
– Exit Request Denied: Interlock Area Busy
– DURESS - Interlock Area Busy
305
Area Interlock
306
Area Control
Anti-Passback
307
Anti-Passback Overview
OnGuard supports either Local or Global Anti-

Passback (APB)
– Local Area Control & APB
• Tracked and controlled by access panel
– Global Area Control & APB
• Tracked in DB and controlled by Communication Server
308
Local Anti-Passback
Access Control
Panel
Area #1
1A 1B Inside 2B 2A
Area #2
Outside
309
Global Anti-Passback
Access Control Access Control
Panel Panel
Area #1
1A 1B Inside 2B 2A
Area #2
Outside
310
Types of Anti-Passback
Three Types of Anti-Passback scenarios

– Soft
• Access is still granted and APB event is generated if system
thinks you are not in “Area Leaving”
– Hard
• Access Denied into “Area Entering” if system thinks you are
not in “Area Leaving”
• APB event is also generated
311
Types of Anti-Passback
– Timed
• Individual Reader
– Access denied to individual reader until configurable countdown
time expires
– Countdown time transfers to reader on every access granted
event
• Area
– Access denied to “Area Entering” until configurable countdown
time expires
– Countdown time transfers to “Area Entering” upon access
granted event at an entering area reader
312
Soft Anti-Passback
Access Control
Area #2 Panel
Outside
Then
Here 3 Area #1
1A 1B 2 2B 2A
Then Inside
Here 4 Then
Again Here
1
#4 Outcome = Swipe
Here
Access Granted
Anti-Passback
Violation
313
Hard Anti-Passback
Access Control
Area #2 Panel
Outside
Then
Here 3 2
Area #1
Then
1A 1B Inside 2B 2A
Here 4 Then
Again Here
1
# 4 Outcome = Swipe
Access Denied Here
Anti-Passback
Violation
314
Timed Anti-Passback
Access Control
Area #2 Panel
Outside
Then
Here 3 2
Area #1
09:40
09:41
09:42
09:43
09:44
09:45
09:46
09:47
09:48
09:49
09:50
09:51
09:52
09:53
09:54
09:55
09:56
09:57
09:58
09:59
10:00 1A 1B Then 2B 2A
Here Inside
Then
Here 4 09:50
09:51
09:52
09:53
09:54
09:55
09:56
09:57
09:58
09:59
10:00
09:50
09:51
09:52
09:53
09:54
09:55
09:56
09:57
09:58
09:59
10:00
Again 1
Swipe
# 4 Outcome =
Here
Access Denied
on 1A reader for
10 min.
315
Area Control
Local Anti-Passback
316
Setting up Local APB
Local APB is setup in several steps

– Enable Store Area Anti-Passback Locations at Access
Panel
– Create/Set up Areas
– Associate readers to anti-passback areas
317
Enabling at the Access Panel
318
Local Areas
All Local Areas are considered a ‘Normal Area’

type
A default local area will be created in a local APB
system/segment when a new access panel is
added
Areas may not span Access Panels
319
Local Areas
320
Local Areas
Default Local Area

– This area is automatically created for each panel
– All badges will be assigned to the default area
• After an ISC database download
• When new badges are first created
– Typically, no area features should be configured for
default area
– Do not delete the default area
321
Creating a Local Area
Select the panel (ISC) for the area

Define area rules
– Anti-passback readers associated with the area will
be listed once readers are configured
– Interlock
– User Counting
• Two man control
• Maximum occupancy
• Close Area
– Occupancy actions
• Function list
322
User Counting
– Maximum occupancy
• Setting count to zero disables feature
– Two man control
• None: Feature disabled
• Standard: Two cardholders must be in the area at all times
• Other options available are Special Area Rules which is
enabled at the access panel
– Close area
• Manually closes area to any card access
323
MultiCard Timeout
The default time between the presentation of two

badges for Two Man Control is 15 seconds
– The default time can be changed in the acs.ini file
• c:\Windows\acs.ini
• Start > run > acs.ini
– The described settings must be added to, or updated in, the
[Service] section of the ACS.ini configuration file on the machine
running that controller’s Communication Server
• MultiCardTimeout
– Time to wait for subsequent cards to be presented when multi-cards
are required
– Valid range is 1-60 seconds, default is 15 seconds
(EpMultiCardTimeout=15)
324
Occupancy Function Actions

– A Local function list may be set to activate based on
occupancy
– Minimum count
• Local function executes when the number of occupants
decreases to the amount specified
– Maximum count
• Local function executes when the number of occupants
increases to the amount specified
325
Timezone/Area Modes
Doors associated to areas can be configured to

open or close based on the start and end timezone
326
Setup Local APB Readers
Area Configuration Rules

– Area entering
• Updates badge being used with new area
• Required configuration
– Area leaving
• Checks for APB violation
– Free pass negates this check one time
– Cardholder must be in this area before access to area entering
• Not required
– System has choice for ‘Don’t care’; equivalent to blank
327
Local APB Readers
Anti-Passback tab in reader configuration

– Area entering
• Move the badge to this new area
– Area Leaving
• Badge must be in this area to use the reader (for Hard APB)
– Use Soft anti-passback (APB not enforced)
– Timed Area anti-passback
• Configured for areas enforcing Timed APB
– Timed anti-passback setting (minutes)
• Actual time limit for the same badge using the reader twice in
a row
328
Timed Anti-Passback Configuration
Timed APB
– Enable Timed APB at the Access Panel
– Set up time limit at the readers
– Areas may be used with Timed Area APB option set
at the reader
• In this case you will also need to create areas
329
Local APB Readers
330
Reset Local Anti-Passback
Reset APB Status

– At the start of a timezone
• Cards will be able to access
APB areas at the start of the
configured timezone
– Reset Now
• Resets APB immediately for
all cards for all panels in a
non-segmented system or for
all cards for all panels in a
particular segment
331
Area Control
332
Global Anti-passback may be enabled system wide

or may be enabled per segment
– Global and Local Areas are not supported
simultaneously in a non-segmented database or in
the same segment in a segmented database
– Global Area Control utilizes the LS Communication
Server to track and enforce APB
333
Global APB
Decision to grant / deny access will be made at the

database when using Hard APB
– If reader is configured for APB
– Decision based on APB location
Decision to grant / deny access will be made by
the access panel when using Soft APB
– Decision based on access level
– Anti-passback event generated after the access event
is received by the database
334
Segmented vs. Non Segmented
 Non-Segmented
system
Segmented
system 
335
Setting up Global APB
Global APB is setup in several steps

– Enable Global anti-passback
– Create/Set up Areas
– Associate readers to anti-passback areas
336
Global Areas
Areas may span Access Panels

– Not associated with an access panel
Some area features disabled
– Two man control
– Function list activation
Global Area types
– Normal (Similar to a local area)
• Used to track cardholders leaving one normal area and entering another
– Hazardous (only used with Mustering)
• Used to track cardholders still in the hazardous area
– Safe (only used with Mustering)
• Used to track cardholders who have left the hazardous area and entered a
safe area
337
Global Areas
338
Global APB Readers
Global APB reader configuration

– Similar to Local APB reader options
– Timed Area APB not available
– Timed APB is available but reader must not be
associated to an area
– Host Decision Offline Mode
• Global areas require access to the database so we need to
set the behavior when the database is offline
339
Host Decision Offline Mode
For Hard APB only, when the panel is offline from

the OnGuard database
– Access panel will attempt to make access decision
through the LS Communication Server for up to15
seconds
• Reader blinks red/green during this time
– After 15 seconds of database inaccessibility, the
offline state is then enforced based on the
configuration of anti-passback at the reader
• Access will be denied for all cardholders (default)
• Set Make Local Decision at Panel which will suspend APB
and access will be based on access level
340
Global APB Readers
341
Alarm Monitoring
Areas
– Occupancy report
• Displays cardholders in area
• May be manually refreshed
– Move badges
• Allows moving cardholder to selected area
342
Global Anti-Passback Features
Allows current cardholder displayed

– One Free Pass
• APB not enforced for first access attempt
– APB Move Badge
• Allows badges to be moved from the current area to a new
area
• Notes may also be logged
– Display Global APB Areas
• Displays the Global APB areas for all badges of the currently
displayed cardholder
343
Anti-Passback Features
344
Global APB Reset
Reset Now
– Resets APB immediately for all badges
Listed as an Action in scheduler
– Global APB System/Segment Reset
345
Area Control
Global Anti-Passback: Mustering
346
Mustering
Global APB is the foundation for Mustering

Mustering requires at least two global areas
– Hazardous Location
– Safe Location
347
Mustering Area Types
Hazardous Location
– A danger area
– When Mustering is initiated, an occupancy report will
be generated showing cardholders in the Hazardous
Location
– More than one Hazardous Location may exist for a
Safe Location(s)
Safe Location
– A safe area used to account for and assemble
cardholders leaving a Hazardous Location(s)
– More than one Safe Location may exist for a
Hazardous Location(s)
348
Hazard Location
Hazardous Location
• Tracked by the Database/Communication Server
– Normal areas may be associated and located within a
Hazardous Location
– Active area features
• Maximum occupancy
• Close area
349
Safe Location
Safe Location
• Tracked by the DB/Communication Server
– No area features enabled
– Cardholder must access the Safe Area reader
• Any event on the safe reader with the badge number will move
the badge to the safe area
• Area will update regardless of cardholder’s access levels during
Mustering
• Access Grant or usage of the door is not required
– Recommended Safe Area configuration
• Set area leaving as ‘Don’t care’
• ‘Soft APB’ is default
350
Safe Location
351
Associated Safe Locations
Associated Safe Location

– Associates one or more safe locations with each
Hazardous Location
– A mandatory configuration when the following
functionality is required
• Muster Reset Area
– Removes all badges from safe area to a specified area when
Muster mode is reset
• Muster Start Area
– Area where badges are located when Muster mode is initiated
352
Associated Safe Locations
353
Associated Inside Areas

– Associates normal areas with the Hazardous Location
– Muster report will list all badges within the Hazardous
Location and all associated areas
354
355
Mustering Reporting
Muster Reporting
– Muster report shows badges within the Muster area
and associated areas
– Alarm monitoring Muster Report activation
• Immediate
• Time delay in minutes
• Minimum occupancy is reached
356
Mustering Reporting
357
Safe Reader Configuration
Anti-passback tab in reader configuration

– Similar to all other APB reader configurations
– Specify Safe Area entering
Readers configured for Safe Area
– Specify Safe Area entering
– Automatically “Use soft APB”
– Automatically set Area Leaving to <Don’t Care>
358
Alarm Monitoring
Hazardous Location
– Muster report
• Real time display of cardholders in Hazardous Location and
optionally inside areas within the Hazardous Location
• Optionally removes all cardholders from Safe Area
Automatically refreshed every two minutes
• Shows last attempted location
– Start muster mode
• Starts muster mode for Hazardous Location
– Reset muster mode
• Stops muster mode for Hazardous Location and places
cardholders in the Muster Reset Area
359
Alarm Monitoring
360
Anti-Passback Exemption
A cardholder can be exempt from Anti-Passback
rules by enabling the exemption on the
cardholders’ badge
361
Area Access Manager
362
Area Access Manager
Area Access Manager is an application allowing
administration of existing access levels to existing
cardholders
An Area Access Manager user has control over
specific access levels that are assigned to the
User under Administration > Users
Area Access Manager is access level oriented
This is a license feature
363
Area Access Manager
Browser-based Application-based
Access Manager Area Access Manager
364
User Permissions
Access levels must be created prior to assigning
Area Access Manager Levels
Access levels are assigned to the OnGuard user
account
– Only access levels assigned will be accessible in the Area
Access Manager application
Under Administration > Users, assign / checkmark
several access levels to your user account
365
Area Access Manager
Open Area Access Manager and do the following:

– Assign a cardholder(s) to an access level(s)
– Remove a cardholder(s) from an access level
– View personal information concerning highlighted
cardholder
Limited reports are initially available in Area
Access Manager for the user to run
366
Assign Cardholder
Select an access level from the dropdown box
Click on the ‘Assign Access’ button to launch a
cardholder search wizard
Select cardholder(s) to be assigned to the access
level
367
Assign Cardholder
Select additional access levels, if needed
– Temporary access can optionally be given by clicking on the
‘Set Activation Dates’ button
368
Remove Cardholder
Select an access level from the dropdown list
Select cardholder(s) to be removed from the
selected access level
Remove cardholder(s) from the access level by
selecting the ‘Remove Access’ button
369
Display Personal Information
The ‘Personal Information’ button allows viewing
of cardholder, badge and access level information
of selected cardholder
– No information may be modified
Notice there are no

Add, Modify, or
Delete buttons
370
Area Access Manager Reports
Area Access Manager reports
– Two default reports
• Access Level Assignments to Cardholders
• Access Level Assignments to Cardholders by Segment
– Additional reports can be added from System
Administration under Administration > Reports
• Modify the report and select type as Area Access Manager
371
Access Manager
Open Access Manager via Console and do the
following:
– Give access to a cardholder(s)
– Remove access from a cardholder(s)
372
Access Manager
Give Access
– Select an access level
• Search for specific cardholder, as needed
– Use the slide button, per cardholder, to give access
• Additionally, temporary dates can be assigned
373
Access Manager
Remove Access
– Select an access level
– Click on the ‘Have Access’ tab
• Search for specific cardholder, as needed
– Use the slide button, per cardholder, to remove
access
374
Destination Assurance
375
To be used in areas where the cardholder is

limited in the amount of time they have between an
entry reader and exit reader
– Chemical laboratories
– Break rooms
LS Linkage Server Service must be configured and
started
376
Global functionality allows timing the use of a

initiating reader to one of several destination
readers
– ‘Minutes before alarm’ specifies how much time after
a cardholder enters an area by an entrance reader
before they must badge out at an associated exit
reader
– Maximum time 9999 minutes (approximately 7 days)
Must proceed to exit readers option enforces use
of the exit reader prior to any other reader
– Other readers may be accessed prior to the exit
reader within the timeout, with the option turned off
377
378
Without “Must Proceed To Exit Readers”
Entrance reader access

Entrance
Alarm configuration
Reader
– 20 minutes before alarm
Exit reader must be 20 minutes
accessed prior to
timeout expiration Exit
Reader
– Alarm generated if not
accessed within 20 * Option off
minute timeout
– Other readers may be
used during the 20
minute timeout*
379
With “Must Proceed To Exit Readers”
Entrance reader access

Alarm configuration Entrance
Reader
– 20 minutes before alarm
Exit reader must be
accessed prior to Non-exit
timeout expiration 20 minutes
Reader
– Alarm generated due to
non-exit reader being
accessed* Exit
– Alarm also generated Reader * Option on
after the 20 minute
timeout
380
Enabling Badge Exemption
Allows each badge to be set exempt for this

feature
– Default is non-exempt
All users with view or edit permissions will see the
Destination Exemption option control
381
Destination Exempt
382
Selective Cardholder Download
383
Allows for selective badge downloads to the ISC

– Limits the number of badges residing on the ISC
• Useful if you have Series 1 Access Panels with limited memory
– LNL-500, LNL-1000, LNL-2000
• Useful if you have a large cardholder database and want to efficiently
manage them
– Reduces full panel download time
– Downloaded badges that are not assigned a selected Access
Level will be purged as other newer badges are downloaded
384
System Admin > Access Control > Selective

Cardholder Download…
385
There are three configuration options

– By default, all active badges are downloaded to the
access panel if ‘Download only those badges with the
selected access levels’ is not selected
• Limitation of the number of badges downloaded set at the
Access Panel options
• Segmentation affects what access levels will get downloaded
– Select ‘Download only those badges with the selected
access levels’ with no access levels selected
• No badges are downloaded to the access panel
386
Select ‘Download only those badges with the

selected access levels’ and select access levels
– Whatever cardholders have that access level assigned will be
downloaded to the panel
• Limitation of the number of badges downloaded set at the Access Panel
options
– When the access panel cardholder capacity is reached, any
additional cardholders that don’t have the selected access level
assigned will be purged from the panel
387
388
Selective Download Enhancements
There are feature enhancements to manage

controller memory more efficiently when the
access panel reaches its cardholder capacity
– Number of cardholders to delete at capacity
• This will speed up the badge download process
• Allowable values are 1-99,999
– Remove expired badges daily
• Removes badges that have exceeded badge expiration date
• Processed nightly at 3:00AM
389
390
Display of access levels for a controller

– The access levels available for a Selective Cardholder Download
are by default limited to only those that had readers attached to
the panel
• All access levels also available
391
Show all access levels is automatically enabled

when more than one panel is selected
– Access Panels must belong to the same segment if
database is segmented
392
Selective Download Panel Indicator
The Alarm Monitoring icon will change on panels

that are configured for selective download
– The Access Panel properties will display the Selective Download
configuration
393
EOL Resistor Table
394
EOL Resistor Table
Allows configuration of EOL resistor values for all

Lenel alarm inputs
– 4 Default values
• Default normally open
– Non supervised
– Supervised
• Default normally closed
– Non supervised
– Supervised
395
EOL Resistor Table
– 4 Custom values
• Detectable resistance range
– Basic = 51Ω (minimum) to 12,499Ω (maximum)
» 10K (9,999 ohms) is the recommended maximum resistance value
for Normal high range however values up to 12.5K are allowed but
will affect detection accuracy
– Advanced = 50Ω (minimum) to 25000Ω (maximum)
396
EOL Resistor Table
Common
Values
397
EOL Resistor Table
Custom configuration
– Basic
• Allows configuration of low and high range
• Allows selecting N/O or N/C contact
– Advanced
• Input status and resistance ranges may be defined
• Allows configuration of priority (low, med, high) for each
monitored state
• During add or modify switching between basic and advanced
will keep low and high values.
– Default button
• Sets configurations to standard values
398
Basic Configuration
Basic default values

– Normal low range
• 750 to 1250 Ω
– Normal high range
• 1550 to 2500 Ω
Defined values
Foreign 1K Ω Foreign 2K Ω Foreign
Short Open
399
Advanced Configuration
Advanced default
values – Active (alarm) input
– Shorted loop • 1550 to 2500 Ω
• 0 (short) to 50 Ω – Foreign
– Foreign • 2500 to 10000 Ω
• 50 to 750 Ω – Open loop
– Inactive (secure) input • 10000 Ω to ∞ (open)
• 750 to 1250 Ω – Grounded input line
– Foreign • Input A or B grounded
• 1250 to 1550 Ω Defined values
0Ω Foreign 1K Ω Foreign 2K Ω Foreign ∞Ω

Short Open
400
Status options:
– Inactive
– Active
– Fault – Ground fault
– Fault – Shorted
– Fault – Open
– Fault – Foreign voltage (abnormal resistance)
– Fault – Non-settling (debounce time expires)
401
Resistance range
– Positive number representing a resistance value in
ohms
– Drop-down selection
• Infinite resistance
• Shorted
• Ground A
• Ground B
402
Debounce Time
403
Debounce Time
Debounce time
– The amount of time (mS) required for the contact to
remain stable and accurately report a change of state
of the input
– Configuration is relative time based on type of input
• General purpose alarm input (alarm panel, reader interface
alarm input)
• REX
• Door position switch
404
Debounce Time
Debounce values
– Default – used mainly for upgrading, and for hardware
not supporting configurable values
• Previous value used when upgrading
– 1 ~ 33 mS (default for REX)
– 2 ~ 67 mS
– 3 ~ 100 mS (default for general purpose inputs and
DPS)
– 4 ~ 150 mS
– 5 ~ 200 mS
– 6 ~ 250 mS
405
Debounce Time
Debounce time
Contact Open 150 mS
Contact Bounce
Contact Closed
Time
Reported Alarm = Alarm Restored

406
Debounce Time
Debounce
Contact Open time
33 mS
Contact Bounce
Contact Closed
Time
Reported Alarm = Fault – Non settling

407
Hold Time
408
Hold Time
Hold time
– The hold time is intended to reduce multiple
transaction events from sensors that are likely to have
many transitions per incident
• Intended for general purpose inputs
– Extends the detection of the restored alarm
• Configured in seconds
409
Hold Time
Incident Secure
1
A single restored
event will be
generated at the
end of each hold
time
Single Alarm 2 second hold time
410
Debounce & Hold Time Configuration
Configuration of Reader Controls, AUX inputs and

Alarm Inputs
– Assigning the EOL supervision configuration
– Debounce Time
• 1 lowest (33ms)
• 6 highest (250ms)
– Hold Time
• In seconds (1-15)
411
Elevator Control
412
Elevator Control Topics
LNL-1320 Button Interrupt

– 1-6 floors
– LNL-1320 Relays interrupt elevator floor selection button
LNL-1300 or LNL-1300e Button Interrupt
– 1-128 floors
– Uses LNL-1300 or LNL-1300e and LNL-1200 hardware
LNL-1300 or LNL-1300e Floor Tracking
– 1-128 floors
– Uses LNL-1300 or LNL-1300e, LNL-1100 and LNL-1200 hardware
Day Mode
Online Facility Code Mode
Offline Access
413
LNL-1320 Button Interrupt Example
N/C
ISC To
C
N/O
Elevator
Control
Room
LNL-1320 Elevator
Floor Button
1 2
Reader
1 2 3 4
3 4 5 6
5 6
This example shows a button interrupt setup that will allow the
cardholder to select floors 1, 2, 4 & 5 but only chooses floor 1.
414
LNL-1300 or LNL-1300e Button Interrupt Example
To
ISC Elevator
Control
Room
Elevator
Floor Button
1 2 3
4 5 6
1 2 3 4 5 7 8 9
6 7 8 9 10
10 11 12
Reader
11 12 13 14
LNL- 13 14 15
1300
15 16
16
~8 LNL-1200
This example shows a button interrupt setup that will allow the cardholder to select
floors 1, 2, 4, 5, 10, 12, 14 and 15 but only chooses floor 1.
415
LNL-1300 or LNL-1300e Floor Tracking Example
To
ISC Elevator
Control
Room
Reader
LNL-
1300
Elevator
Floor 1 2 3 4 5
Buttons 6 7 8 9 10
1 2 11 12 13 14
3 4 15 16
5 6
~8 LNL-1100 ~8 LNL-1200
416
Elevator Control Access Panels
Elevator Control must be enabled at the ISC for all

types of elevator controls
– Reserves memory in the ISC
– Allows readers to be configured for elevator control
LNL-2220 and LNL-2210 supports elevator controls
for downstream readers only (readers from LNL-
1320 or LNL-1300 or LNL-1300e)
– On-board readers from the LNL-2220 and LNL-2210
cannot be configured as elevator readers
417
Elevator Control Access Panels
418
Reader Setup
LNL-1320 Elevator Control

– Button Interrupt
LNL-1300 or LNL-1300e Elevator Control
– Button Interrupt
– Floor Tracking
419
Lenel LNL-1320 Button Interrupt

– Track floors not available
– Reader two disabled
– Additional elevator hardware not used
– On-board relays control outputs associated with
elevator floors
• Up to 6 floors supported
– Auxiliary inputs 1 and 2 are available and can be
configured under Readers and Doors
420
421
Elevator Control Levels and Access Levels
Comparing Access Levels and Elevator Control

Levels
– Elevator Control Levels
• Combination of Timezones, Relay Outputs and Floors
• 256 Elevator Control Levels Supported
• Elevator Control Levels used to configure:
– Elevator Access Level assigned to badge
– Day mode for free access to floors
– Access Levels
• Combination of Readers and Elevator Control Levels
• Elevator control level treated as a multi-floor timezone
• Standard readers and elevator readers may be combined into
the same access level
422
Elevator Control Levels
423
Elevator Control Levels
424
Using Elevator Control
Access Granted Events

– Pulses 1320 relays based on assigned Elevator
Controls
– Pulse duration is set by adjusting each reader’s strike
time
425
Using Elevator Control
426
LNL-1300 / LNL-1300e – Without Floor Tracking
Lenel LNL-1300 / LNL-1300e Button Interrupt

– Enable ‘Elevator Support’
• System Admin > Access Control > Access Panel > Options
– Select LNL-1300 / LNL-1300e Reader and select
‘Elevator’
• System Admin > Access Control > Readers and Doors >
General tab
• Both Reader 1 and 2 from the LNL-1300e support elevator
– Additional elevator hardware must be used
• Need the LNL-1200 Output Control Module
• Must be configured through the Reader Elevator Hardware
tab
427
428
Activation of LNL-1200 relays control which floor a

cardholder will travel to
– Up to 8 LNL-1200 Output Control Modules for use in
elevator control to allow up to 128 floors
– Without Floor tracking selected, LNL-1200 is the only
hardware available
429
LNL-1300 / LNL-1300e – Adding Elevator Hardware
430
LNL-1300 / LNL-1300e – Renaming Floors
Outputs may be renamed to match floor names

• System Administration > Access Control > Alarm Panels >
Alarm Outputs
431
Create Elevator Control Levels

– Assignment of Elevator Outputs to Floor to Timezone
Assign Elevator Control Levels to Access Levels
Assign Access Levels to Cardholders
432
LNL-1300 / LNL-1300e – Floor Tracking
Lenel LNL-1300 / LNL-1300e Floor Tracking

– Enable ‘Elevator Support’
• System Admin > Access Control > Access Panel > Options
– Select LNL-1300 / LNL-1300e Reader
• Select ‘Elevator’ & ‘Track Floors’
– One or both readers from the LNL-1300e can be selected
• System Admin > Access Control > Readers and Doors >
General tab
433
434
Additional elevator hardware must be used

– Must be configured through the Reader Elevator
Hardware tab
– LNL-1100 and LNL-1200 required
– Up to 8 LNL-1100s and LNL-1200s can be configured
per elevator to support up to 128 floors
Elevator buttons wired to LNL-1100 inputs are
linked to the elevator control unit
– Used only for Floor Tracking
– Used to detect which floor has been requested
435
LNL-1300 / LNL-1300e – Adding Elevator Hardware
436
Rename outputs to reflect elevator floors

Create Elevator Control Levels
– Assignment of Elevator Outputs to Floor to Timezone
Assign Elevator Control Levels to Access Levels
Assign Access Levels to Cardholders
437
Custom Day Mode
Pre-defined floors have free access during active

day mode timezone
• Each floor may use a different time zone
• LNL-1320 will have output(s) energized
• LNL-1300 / LNL-1300e requires button selection
Day Mode Elevator Control assigned per reader
• Access Control > Reader > Control Tab > Elevator Control
Settings
438
Custom Day Mode
439
Online Facility Code
Online Facility Code – No Floor Tracking

– All outputs defined in the Elevator Control Level
(ECL) selected from the drop down box will energize
when granted facility code is issued at the reader
• Works for LNL-1300 and LNL-1320 elevator solutions
• The reader must be on-line and in facility code mode
Online Facility Code – With Floor Tracking enabled
for LNL-1300 / LNL-1300e
– Outputs defined in the Elevator Control Level (ECL)
selected from the drop down box will be available
• Selection of the floor via elevator button is necessary
• The reader must be on-line and in facility code mode
440
Online Facility Code
441
Offline Access
LNL-1320 offline from ISC

– Output 1 will energize when a badge (with valid facility
code) is presented to the elevator reader
LNL-1300 / LNL-1300e offline from ISC

– No Floor Tracking – all outputs defined in the Elevator
Control Level (ECL) selected in the drop down box for
Online Facility Code will energize
– With Floor Tracking enabled – the outputs defined in the
Elevator Control Level (ECL) selected in the drop down
box for Online Facility Code will be available
– Selection of the floor via elevator button is necessary
442
Summary of Advanced Access Course
Single Sign On Alarms Configurations
Segmentation Invalid Badge
FormsDesigner Lite Area Interlock
Monitoring Options Anti-Passback
Device Groups Mustering
Action Groups Area Access Manager
Scheduler Destination Assurance
Local IO Selective Cardholder
Global IO Download
First Card Unlock Custom EOL Resistance
Double Card Unlock / Hold Time
Toggle Debounce
Map Designer Elevator Control
443
Upon Completion of Class
Congratulations, you have completed the

Advanced Access Control course
You must pass the online exam within 30 days
– 70% is passing with two additional options for make-
up
• A score of 80% is required to pass for make-up exams
Please clean up your personal area
– Take all personal items with you
Please return all classroom badges to the
instructor
Thank you for your participation!
444
Student Transcripts
Thank you for attending this course!

– Student transcripts (including records of CEUs
issued) are available online through the Lenel
Training Portal at all times and can be viewed or
downloaded at any time.
• https://partner.lenel.com/training/transcript
– Official Transcripts can also be sent via e-mail
through the Lenel Training Portal.
445

Advanced - 7.6 - February 2020 PDF

Uploaded by

Copyright:

Available Formats

You might also like

Advanced - 7.6 - February 2020 PDF

Uploaded by

Document Information

Original Description:

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

Advanced - 7.6 - February 2020 PDF

Uploaded by

Copyright:

Available Formats

Advanced Access Control

Welcome to Lenel Training

Who ? ( You and your employer ?)

Where ? (Are You From ? )

What ? ( Is your Role and Experience with Regard

What are your expectations for this course?

Course Name: Advanced Access Control

By the end of this course, you will be able to:

Course objectives (continued)

An exam will be issued and a passing grade required

Single Sign On FormsDesigner Lite

Mustering Custom End of Line

Select domain hostname

Advanced Configuration for LDAP directories (Not

Segmentation is the process of dividing an access

Initial objects assigned to each segment

Segmentation allows an additional level of

When an <All Segments> user logs into <All

Segment 1 Segment 1 Segment 1

Segment 3 Segment 3 Segment 3

When an <All Segments> user logs into a segment, they can

Segment 1 Segment 1 Segment 1

Segment 3 Segment 3 Segment 3

Segment 1 Segment 1 Segment 1

Segment 3 Segment 3 Segment 3

User User Logged Object

Segment 1 Segment 1 Segment 1

Segment 3 Segment 3 Segment 3

Segment 1 Segment 1 Segment 1

Segment 3 Segment 3 Segment 3

System wide settings can only be configured by

Note: Being an <All Segments> user is not the same as

Examine the following forms

Examine the following forms

Examine the following forms

Examine the following forms

Examine the following forms

Once enabled, Segmentation cannot be disabled

Default segment is created for placement of pre-

Examine the following forms

Examine the following forms

Examine the following forms

Examine the following forms

Examine the following forms

Segments may be added independently or to a

Unique segment name

Copy records from another segment*

Prefix or append text to the names of records for

System wide limits are now per segment

– Access level assignments per badge

Segmenting Access Panels

Initially, users are assigned to <All Segments>.

Additional control over objects that belong to

Card Formats become assignable per segment

Option to segment badge types allows an

Badges controlled by Badge Type

– Available to All (No Segment Restrictions)