System Events is where rules that are not person dependent are created and modified. Keep tabs on who’s coming and going with real-time live monitoring of system activity. For example, security personnel can compare the system's photo image of the authorized cardholder versus the actual person scanning the card.
Permission roles of Integrator and Admin have access to the System Events features.
System Events Overview
Create System Events
Click the System Events icon in the Cloud Node Appliances home screen to create a new System Event or to edit/view existing events. Any current system events that have been created are listed here in alpha order.
To create a System Event, click the + icon at the lower right of the System Events screen.
Name
Assign a unique descriptive name for the event.
Partition
To assign a previously created partition to the System Event, click inside this field or on the down arrow. Any partitions that have been created previously appear in the list. If no partitions have been created, the Partition field will not appear on this screen.
(See Partitions for additional information.)
Understanding Partitions
Schedule
-
Specify a Start Time and Stop Time in a 24-hour format for the rule to be active. Click the down arrow in these fields and use the up and down arrows to set hours and minutes. Click SAVE.
-
Recurring - Select the day(s) of the week for a recurring event.
-
Single Date - If selected, a rule can be defined for a specific date, such as a holiday closure. Use the Date menu to select the month and day. Click inside the Date field to enter a date using the MM/DD/YYYY format (Month, Day, Year) or click on the down arrow to use a calendar.
-
Use the < and > to change to a previous or future month.
-
Click on the month to select a month's name from the drop-down list.
-
Click on the year to change the year.
NOTE: Single dates are useful for temporary access, holidays, etc. Once the date and time have passed, the rule will be inactive. These rules can be used again by simply changing the date.
Action
Select a Trigger event and a subsequent Action event when that Trigger occurs.
Trigger
A Trigger event is a selectable option that, when it occurs, “triggers” a specifically selected Action. Click inside the Trigger field or on the down arrow to select an event that will trigger or “set off” an Action.
- On Open - The door position sensor (DPS) is open
- On Close - The door position sensor (DPS) is closed
- On Propped - The door is held or propped open longer than the prop Trigger period
- On Forced - The door is opened without a valid credential read or Request to Exit (Rex) input.
- On Prop Cleared - Door position of closed after the prop Trigger was activated
- All Prop Cleared - All door propped alarms have been cleared.
- On Rex Open - Request to Exit (Rex) input is activated (unlocked). For example, connecting NO on the Rex to the PDK Rex input (B).
- On Rex Close - Request to Exit (Rex) input closed is deactivated (locked). For example, connecting NC on the Rex to the PDK Rex input (B).
- On Credentials Input - Trigger the event on ANY credential input, either valid or invalid.
- On Credentials Not Found - Credential input at the reader that is not recognized or not programmed in the system
- On Comm Loss - Device communication that is lost
- On Comm Loss Cleared - Communication to the connection has been re-established
- On Any Duress - When a duress PIN is entered
- On Input Power Loss - When input power is lost/off.
- On Input Power Recovery - When input power is restored.
- On Overcurrent Detected - When excess or larger than intended current occurs
- On Overcurrent Cleared - When standard or intended current occurs
- On Low Power Mode On - When low power mode is detected
- On Low Power Mode Off - When low power mode is not detected
- On Battery Connect - When expected battery power is detected
- On Battery Disconnect - When battery power is lost
- On Circuit Breaker On - A 'Circuit Breaker' event occurred. This is a flood of event logging (40 events in 30 seconds) occurring on either input A or B (DPS or REX), this disables the input for 30 minutes.
- On Circuit Breaker Off - A 'Circuit Breaker' event ended.
- On Partial Connectivity Detected - The controller is not responding but contact with the WiMac radio is established.
- On Partial Connectivity Cleared - Communication between the WiMac radio and controller is restored.
WARNING: Using # (pound or hashtag key) or any input that includes the # key as a Trigger unlocks the device for ANY credential that is used. This means that pressing any number plus # or just the # key unlocks a door. Use this # Trigger option with caution.
System Events - Door Forced Rules Overview
System Events - Prop Rules Overview
System Events - REX Rules Overview
Duress PIN
The PIN field is accessed in the Person screen from the People option in the Cloud Node Appliances home screen. A Duress PIN is automatically generated when a PIN number is entered in the PIN field. A leading 9 is added to the personal identification number (PIN) that has been created. For example, if the user-created PIN is 1234, a Duress PIN of 91234 is automatically created for that user.
NOTE: Using a leading zero at the start of a PIN will drop that 0 digit when it is used in PDK. A PIN with a leading zero shouldn't be used. As an example, if a PIN of 0123 is created and entered into the reader, the system will see it as 123. Zero is a non-significant digit and is dropped at the start of a number. The system will not recognize a PIN number with a leading zero as a valid PIN and will not allow it.
NOTE: The system generated duress PIN does not appear in the Duress PIN field until after the SAVE button in the Person screen is clicked.
As is the case with most of these screens in this application, the SAVE button does not appear unless and until additions/changes have been made to the information on that screen.
The Duress PIN is used to trigger system event rules that use the Trigger option "On Any Duress", Groups rules using the trigger "On Duress", Reports events using “Duress PIN Entered” and “Any Duress PIN Entered”, and Live Events using “Duress PIN Entered”.
As an example, in a threat situation in which a user is being forced to use their PIN to enter a building or office against their will by an unauthorized person, the Duress PIN can be used to trigger and activate an emergency lockdown or some other action to help resolve and alert others to the situation. A Duress PIN rule, for example, can be created that sends out an email or text message to alert others to the situation.
Action
System Event - Email / Text Alerts Overview
An Action event is a specific response that occurs when the action is “triggered” by a Trigger event. Click inside the Action field or on the down arrow to select a specific action or response from the list that will occur when triggered by a Trigger event.
- Send Email - With a valid Trigger, an email (or even an SMS text message) is sent to the specified email address(es) (or phone numbers) using the pre-configured email template. When Send Email is selected, the Email Template heading and its associated fields are displayed.
Under the Email Template heading, click the + icon next to Recipients to assign who will receive the email (or SMS using the PHONE NUMBER tab) notification. Check the email address(es).
To add an email not listed, use the Another Email field and enter the email address. Click ADD. Repeat for any additional email addresses to be added.
- Do Not Disturb - Toggles the “Do Not Disturb” status of the door/relay. On DND status, the door is locked and unresponsive to regular access attempts until the DND status is removed. For example, a DND can be set while on a conference call or in a meeting to prevent entry to an office by others during the call/meeting.
- Force Toggle - Toggles the current state of the door/relay to opened/closed. If door is closed (locked), toggles to open (unlock). If the door is open (unlocked), toggles to closed (locked).
- Force Open - Holds the door/relay (that the event is created on) in the Open (unlock) position and will not close (lock) unless Force Close status is set.
- Force Close - Clears the Force Open status and locks the door/relay.
- Open - Opens (unlocks) the door/relay
- Close - Closes (locks) the door/relay
- Lockdown On - Lockdown (doors locked) of selected devices is set to On. All doors are locked.
- Lockdown Off - Lockdown (doors locked) of selected devices is set to Off. All doors are unlocked.
- Delay Open - A time delay can be set for opening (unlocking) the door/relay
- Delay Close - A time delay can be set for closing (locking) the door/relay
- Open/Close - Opens (unlocks) the door/relay and sends a close (lock) after a delayed time period
Email Template - Recipients
When Send Email is selected in the Action field, the Email Template screen is displayed.
Click the + icon next to Recipients to assign who receives the email or text message notification. The Add Recipients screen is displayed.
EMAIL Tab - Add Recipients
Check the email address(es) of the person(s) to be notified as a result of the Trigger event. An email is sent (as an Action) to the selected recipient(s) when the specified Trigger event occurs.
Another Email - To add an email address that is not listed, click in the Another Email field and enter the email address. Click ADD.
Repeat this for any additional unlisted email addresses that need to be added.
PHONE NUMBER Tab - Add Recipients
A text message is sent to the recipient(s) when the specified Trigger event occurs.
Mobile Provider - Click in the Mobile Provider field or on the down arrow to select the provider name that corresponds to the phone number.
NOTE: It will be necessary to request this provider information from the person whose phone number is being used. For Verizon customers receiving the SMS text message, there is a 75-character limit for email-to-text messages. To eliminate potential problems with this issue, it is necessary to delete the entire last portion of the Mail message that begins, “This event has been logged…” otherwise the full content of the text message may be truncated.
Phone Number - In the Phone Number field, enter the number for the recipient in the form: 1234567890 (numbers only, no special characters such as a dash, period, comma, or parentheses). Click ADD.
Repeat for any additional phone numbers that need to be added.
Subject - Recipients
Determine what information appears in the Subject line of the email/text message. Click inside the Subject field to edit its contents. (By default <%loginfo%> <%time%> appears in this Subject field. These can be changed to any of a number of parameter options or enter plain text content of your own choosing.)
Clicking anywhere in the Subject field displays a floating + icon. All text within this Subject field can be edited to display whatever content is desired for the Subject of the email.
Click on the floating + icon to display a list of the Subject field parameter options.
- <%time%> - Displays the date and time
- <%logdoor%> - Displays the accessed door
- <%logevent%> - Displays the logged event
- <%logresult%> - Displays the logged result
- <%loginfo%> - Displays the logged information
- <%logcardno%> - Displays the card number
- <%logname%> - Displays the name of the person
- <%logiolink%> - Displays the logged link
Mail - Recipients
In this portion of the Email Template field, you will define the contents for the body of the email.
By default, ALERT INFORMATION appears at the beginning of this Mail field information. This text can be edited by clicking on the text to change its content to whatever message is desired for the recipient. Click inside the Mail field to edit its contents. Click on the floating + icon to select from the specific list of parameter options, or text of your own choosing can be entered.
-
Clicking anywhere in this field causes the floating + icon to appear. Existing text or text of your own choosing may be edited/entered in this Mail field and will comprise the body of the email.
-
Click on the floating + icon to display a list of the Mail field parameter options.
- <%time%> - Displays the date and time
- <%logdoor%> - Displays the accessed door
- <%logevent%> - Displays the logged event
- <%logresult%> - Displays the logged result
- <%loginfo%> - Displays the logged information
- <%logcardno%> - Displays the card number
- <%logname%> - Displays the name of the person
- <%logiolink%> - Displays the logged link
The following field text is also displayed by default. These options can also be fully edited by clicking anywhere inside of these texts and/or clicking on the floating + icon.
- TIME/DATE: <%time%>
- LOG INFO: <%loginfo%>
- CARD NUMBER: <%logcardno%>
- NAME: <%logname%>
This event has been logged by your ProdataKey Access Control System. Note the information above for details. For assistance, contact your Local Dealer or ProdataKey at 801.317.8802 or visit www.prodatakey.com.
NOTE: As is the case with most of these screens in this application, the SAVE button does not appear unless and until additions/changes have been made to the information in that screen.
Source Doors - System Event
A Source Door is the location where a Trigger event, such as a card scan, occurs. Typically, the Source door (when triggered) and the Target door (where the action occurs) are the same, such as performing a card scan at a door (the Source door), after which that same door (the Target door) is unlocked.
Click the + icon next to Source Doors to add access-controlled doors to the System Event and check the door(s) to be associated with the Trigger and Action. When doors are selected from Source Doors, the Target Doors option is also available (unless Send Email is selected as an Action). Click SELECT.
Once Trigger and Action options have been set, check the Source Doors to be used or use the Filter field to search for a door from a long list. When triggered, the specified action occurs at the designated door(s). Click SELECT.
With Trigger and Action option(s) defined, select from the list of Source Doors to be affected by the Trigger. When the Trigger event occurs, the defined Action occurs at the selected Source door(s). Source Doors is where the Trigger event is set to occur. It is not affected by the Action unless the selected Source door(s) are included with the Target doors.
Target Doors - System Event
Target Doors are the door access devices that perform the Action specified in the rule. To select specific door(s), click the + icon next to Target Doors (when Another Doors is selected) and check the door(s) to be associated with the Source Doors or use the Filter field to search for a door from a long list. Click SELECT.
Same as Source Doors - Target Doors
-
If the Target Doors is to be the same as the Source Doors, select the Same as Source Doors option.
-
Click SAVE at the upper right.
NOTE: As is the case with most of these screens in this application, the SAVE button does not appear unless and until additions/changes have been made to the information in that screen.
Another Doors - Target Doors
-
To use Target door(s) other than those specified in Source door(s), select the Another Doors option and click the + icon next to Target Doors.
-
Check the desired doors, or search for a specific door(s) by name from a long list using the Filter field. Click SELECT.
Delete System Events
In the System Events list, hover the cursor over the System Event to be deleted and click the trash icon.
Comments
0 comments
Please sign in to leave a comment.