Platinum CCTV

Configuring PDK Integration in AVM

A. Connecting to your PDK Site

To establish a connection between your PDK access control system and your AVM NVR, you will first need to add your PDK.io System ID in the CMS4 software on your AVM NVR. Follow these steps to initiate a connection.

• Find your PDK System ID

  

  1. Log in to your PDK.io account
  2. Browse to System Settings
  3. Copy your System ID
• Enter your System ID into AVM NVR
  1. Log in to your AVM NCR through CMS4 using Admin Account 

     1. Click on the Configuration Tab

        

     2. Select PDK Access Control at the top left

         

     3. Enter your System ID 

        

     4. Click Refresh configuration to initiate the first connection and pull doors 
     5. Click Select Doors and select door(s) to communicate with your AVM NVR

     6. Click Save 

        

B. Controlling and Viewing Door States from Layouts 

Our AVM NVRs let you control and view door states in real time while monitoring your cameras. The AVM NVR receives signals from your CloudNode and updates door status, allowing you to control and force door states, provide momentary access, and set doors to DND (lockdown) state. This integration will enable you to fully control your access control system without ever leaving your AVM CMS4 client software.

• Adding PDK Door Control Icon to camera layout(s)

  1. Select any camera layout where door control is desired 

  2. Enter Administrator Mode in CMS4 through the top menu

     

  3. Right-click on the camera and open Configuration Tools

     

  4. Select PDK Access Control controls

  5. Drag the selected door icon onto the screen where the button is desired. Repeat for any layout where you need control

     

  6. Exit Administrator Mode

  7. The door icon will show the door state 

     

     • White - Door Locked

     • Green - Door Unlocked

     • Red Flashing - Door Propped Open

  8. Hover over the icon for more details 

  9. Click on the icon to open the Door Control Menu

     

     • Locked - Lock Door

     • DND - Put the door in DND mode to prevent access

     • Allow - Momentarily allow access (timeframe based on PDK Open/Close Dwell setting in PDK.io)

     • Unlocked - Unlocks the door, putting it in Force Open mode

NOTE: Door icons can be added to as many camera layouts as desired with one or multiple cameras. Repeat as desired.

C. Adding Person Data for Access Control

Once your PDK Access Control system is connected to your AVM NVR, it will automatically download user data and add it as a Person in your AVM Persons list, so you can combine the access control data with your LPR plate numbers, person images, etc., to improve access control. Persons will download at the interval specified in the PDK Access Control system's configuration page of your CMS4 client software.

• Adding Person Data
  1. Enter your Persons tab

     1. Add a tab to the top of the screen in administrator mode if you haven't yet.

        

         

  2. Double-click the Person you wish to view or edit
     1. Add Photo from your PC (new users created in PDK will download images automatically)
     2. The credential number should be listed if it was in PDK.io already 
     3. Add License Plate info (to use with LPR/ANPR cameras if desired)

     4. Add Company and Car status if desired 

        

D. Viewing Access Control Data

In Access Control Mode, you can monitor the status of all of your doors for a facility at a time, see the door states, control each door, view the latest door state and sensor changes, as well as see the names, card numbers, and/or pictures of the latest individuals who have requested, been granted, or denied access.

• Door State and Controls (left pane)

  • In the left tab, each door for the selected facility (selected at the top of the screen) is listed, and right-clicking a door allows control of the door state (same as the icons in section B). DPS states are also shown, as are door alarms.

    

• Historic Door State and Sensor Changes (bottom pane)

  • The lower panel will show a real-time journal of door state changes, mode changes, and access requests, and will pop up individuals as they request access, along with their card/image.

    

• Latest Person Cards showing granted or denied access (right pane)

  • The right panel shows a real-time journal of selected doors (or all doors), showing access requests that have been either permitted or denied. For individuals that have images loaded in their persons list, you will also see their image for both Bluetooth and credential access, the user’s name and photo are displayed as well as the time and date of access.

    

E. Searching for Video from Access Control Events

Once the data from the PDK access control system is imported into the AVM system, it is stored in the AVM database, allowing you to search for access control events and pull up specific incidents based on who was accessing the facility at that time. This is done through the Access Control archive tab.

• Add Access Control archive tab to CMS top bar
  • Enter Administrator Mode

  • Click the + Icon in the top bar

    

  • Check boxes for Access Control and Access Control archive

    

  • Click the checkmark to apply 
• Click the Access Control archive tab

  • This will open the pane for searching access control events. Controls at the top left will allow you to search for specific events

    

• Searching for Access Control Events

  • Saved Searches - Once you have defined searches, they will appear in the list to provide you with a quick way to search for common access control events

    

  • Click the down arrow to expand the search criteria 

    

  • Search Event Type for search 

    

  • Select the State of the above-selected event

    

  • Enter the card number to filter by card #

  • Select User to filter events by a specific user (Bluetooth or card)

    

  • Select the Door or Doors for the search 

  • Time range will default to the time range represented by the time bar at the bottom (You can also enter time start and end manually)

    

  • Optionally save the search and give it a name to quickly access in the future

    

  • Click Search to run the search you have defined 

    • Results will appear in the list at the bottom left of the screen
    • Double-click a result to jump to the selected video 

    

Advanced PDK Integration Configuration

Configuring Schedules 

The real power of the AVM software lies in the collaboration between your alarm, access control, and camera systems, providing an extremely powerful engine that lets you control all your systems from within your real-time AVM software. This powerful scheduling engine allows your access control system to interact with AI from your security cameras, OCR from your LPR/ANPR camera, and inputs and outputs from your alarm system or cameras, to truly schedule and automate your building, alerts, and security all in one place. 

The powerful AVM scheduling engine runs at several levels, one on the NVR server-side, which provides you with email, push alerts, and the ability to trigger video backup, control of gates using your LPR/ANPR cameras, forced video recording, multi-door control, and setting bookmarks in your video archive, among other items. The other level is on the client side, providing instantaneous, audible, and visual alerts while watching cameras, displaying specific layouts, and alerting when access control events occur. There is no way for us to show every potential schedule, as each system and each owner is entirely different, but we will try to provide the most popular and useful schedule settings.

A. Configuring Server-Side Schedules

For the following schedule events, the configuration will be done in the NVR configuration selection on the Configuration tab.

1. Find Server-Side Scheduler
   1. Click on the Configuration Tab at the top of the screen
   2. Select your AVM NVR from the list (top left)

   3. Click Task Scheduler

      

   4. Click Add new task

      

2. Create Trigger Events 

   Events will trigger the task to begin. Events can be stacked. 

   NOTE: Any one event will cause the task to run.

   • Click Events tab
   • Drag one or more triggers from the right into the empty pane

   • Configure each Trigger as the pop-up opens

     

• Access Control Event Triggers 

  Each access control event is pulled directly from live events as they occur in the PDK system via the CloudNode. Below are the most popular Access Control event triggers

  Access Control Type:

  (1 door or any, Any Person or specific) 

A. Access Granted 

B. Access Denied

Door Alarms:

(Single or any door)

C. Door open too long

D. Door Forced Open 

Door Modes:

E. Door Unlocked

F. Door Locked

G. Door State Open 

H. Door State Closed

• Virtual Output Switch - (on-screen & in-app switch)

  The virtual switch can trigger the action (if limiting conditions are met). This can allow you to trigger door actions while watching cameras in the AVM CMS4 software. Virtual output switches can also be triggered through our AVM Client on your mobile phone, allowing you to open a door or gate without even leaving your camera app.

1. Create a Virtual Output (increment number in settings)

• Click General Settings and Virtual outputs
• Increase the number

• Scroll down and click on the new Virtual output under the Output heading

  

2. Configure the new Virtual Output 

• For a momentary switch used to allow access to a door from the AVM CMS software, we recommend giving it a name for easy reference, then setting it to auto-switch off after 1 second. This is the most common configuration if you are going to use the switch to allow access to a door

  

3. Add and Configure Virtual Output 

• Drag Output state changed into Events as a trigger
• Drag the switch onto a layout to control doors while watching 

• Select State from List

  

3. Select Conditions 

Conditions will limit the Events that trigger the task. 

ALL conditions must be met in order for the actions to run. 

• Virtual Outputs (can be used as timers) - especially popular when push alerts are used to prevent over-sending

• Date Range

  

• Time Range

  

• Alarm Input State - ie Only trigger events when the alarm system is armed or disarmed, or an auxiliary system or sensor is activated

  

4. Select Actions 

Actions can be stacked and occur when a single event triggers and all conditions are met. All Actions will run when the task is triggered. Below are just a few examples of Server-Side Actions. 

• Archive Bookmarks - Set a pin in the video archive to easily see 

  

• Push Alerts - Send an instant push alert to your phone 

  

• Access Control - (for one or multiple doors)
  • Lock Down Door(s) - PDK DND Mode

  • Unlock Door(s) Permanently or temporarily 

    

• Camera Recording - Trigger specific camera recordings based on the Event Triggers

  

• Audio Backchannel - Send prerecorded audio through a camera's speakers. This can be any .wav audio file, and is commonly used for positive or negative alert messages to acknowledge permitted or denied access

  

• Send Email Alerts - Send an email alert with images from a camera 

  

• Upload image to FTP - Send images from cameras to off-site FTP server

  

• Control Camera Lights - Control System outputs or lighting systems 

  

Stack as many Actions for each Task as needed. 

All Tasks will run when...

Any Triggering Event is activated, and All Conditions are met 

B. Example Server Side Alerts:

The following are examples of popular client-side alerts to help you better understand the possibilities and begin creating your own custom tasks.

1. Momentary Access to a Door (and Push Alert) through CMS

   This task is the most popular server-side task, allowing you to control momentary access through a door or gate with just a push of a button in the CMS4 software or AVM Client mobile application. See Server Side Event setup for details on configuring the toggle switch.

   a. Events - Output State Change Event Config 

   

   b. Conditions - (none)

   c. Actions -

   

Action Specific configurations (common)

CMS4 Client (PC/Mac) with Toggle 

AVM Mobile Client 

Once completed, you can allow temporary access to one of your PDK doors witha single toggle press from your phone or PC/Mac

2. Sample Server-Side Task:

Push alert on Access Denied

Receive a push alert whenever a failed access attempt occurs on one or more doors. 

Event

Action

3. Sample Server-Side Task:

Push alert on Access Granted or Denied (any person)

Event

Action 

4. Sample Task: Push alert on a specific person, Access Granted 

Event 

Action

5. Sample Task: Push alert on Door Propped, Forced open, or Unlocked/Locked 

Event 

Action

6. Sample Task: Send an auto through the Camera when access is denied

This event is for systems that support built-in 2-way audio, such as our AI-Series IP cameras. These cameras have a built-in speaker and can be used to programmatically play a prerecorded audio message to let someone know whether they have been authorized or denied access.

Event

Action

This is just a few examples of popular PDK Access Control schedules on the Server-Side Scheduler in our AVM software. 

As you use your system, you will learn to customize the schedule to suit your specific needs, as every building and every user is unique.

C. Configuring Client-Side Schedules 

For the following schedule events, the configuration will occur inside the CMS Client configuration selection of the ‘Configuration’ tab. The client-side schedules focus on audible alerts, showing cameras, showing person information as access or denial occurs, playing sounds through your PC speakers, and more.

1. Find Client-Side Scheduler 
   • Click on the Configuration Tab at the top of the screen
   • Select CMS Client from the list (top left)

   • Click Task Scheduler

     

   • Click Add new task

     

2. Select Triggering Event and drag it into the Events tab

Events can be stacked. Any one event will cause the task to run.

• Access Control Events 

  Same as the Server-Side Event triggers. 

  Events are dragged into the new tasks in the same way as with Server-side events. Review server-side event triggers in Section B for further details. 

  

3. Select Conditions

Conditions will limit the Events that trigger the task.

NOTE: ALL conditions must be met in order for the actions to run.

• Date Range - Limit Task execution to specific dates. This is great for having tasks that run during holidays or certain timeframes.

  

• Time Range - Limit Task execution to specific days and hours of the day. This is very useful for changing alerts based on whether the facility is in normal business hours or outside them, allowing you to have 'quiet' alerts during normal hours and louder alerts that will grab attention when the facility is closed. 

  

• Alarm Input State - i.e., only trigger events when the alarm system is armed or disarmed, or an auxiliary system or sensor is activated. This is especially useful when you have an alarm system integrated with your AVM NVR, so you can send separate alerts based on whether the alarm system is armed or disarmed at your facility, or to operate doors differently during that period. 

  

4. Select Actions 

Client-side actions are the main difference from server-side tasks. The client-side actions are primarily user interface items, such as maximizing the display window, displaying a specific layout, playing a sound through your speakers, and showing the Access Control tab. 

Most often, these actions are stacked to automate your experience when doors are activated.

Popular Actions for Client-Side Tasks:

• Window State - The window state will allow you to change the appearance of the CMS4 client on your PC or Mac - 
  • Full Screen - This will bring the CMS4 to full screen on the selected monitor 
  • Maximized - This option will maximize the CMS4 application in the current dock
  • Minimized - This will reduce/hide the CMS4 window 

  • Activated - This will not change the window's size, but will bring it to the foreground if it is below other windows.

    

• Show Layout - This action lets you call a specific camera layout (must be created before adding it to a task) in the CMS4 software to display specific cameras.

  

• Play Sound - This action will play a selected audio .wav file through your PC speakers to draw attention to the fact that the task has been run. On Windows PCs, C:\Windows\Media\ has a lot of great options for noises/sounds/ringtones to play.

  

• Set Current Tab - This option programmatically selects a tab in the CMS4 software and helps switch to “Live” or “Access Control” view. You can also stack the Show Tab in the same Task with the delay option to have it return to a different tab afterwards.

  

• Export Video Remotely - This action is less frequently used, but can be helpful if the CMS client is remote from the NVR, and can be used to export video clips of the action that triggered the task. For example, if you use this action with a trigger of an Access Control → Denied event, the system can export a video clip of the attempted access onto your CMS4 PC remotely. Video export will occur after 5 minutes of the video trigger event.
  • Select Camera for export
  • Path on the CMS PC to save the file
  • File Name - It is recommended that you use %Date% and %Time% in the file name so that each file gets a unique name and does not overwrite a prior file.
  • Start and End times (before and after the action trigger) for the video clip
  • Include audio track - if audio is associated with this camera 
  • Draw tets - This will overlay time and date stamp onto the video

  • Change Resolution - If you want the NVR to reduce the file size

    

D. Example Client-Side Alerts

Client-side tasks are ideal when you want to pop up a camera, play a sound through your PC, and/or show access control events and triggers. The Event Triggers that can be used to create these tasks are the same as for Server-Side events, only the output (actions) varies. 

The following are examples of popular client-side alerts to help you better understand the possibilities and begin creating your own custom tasks.

1. Display camera, Play sound, and Show Access Events when Successful or Denied Credential Scanned

In this task, a single event will trigger multiple actions, displaying a pre-created layout of cameras, to show the user a specific camera or cameras, Playing a sound through the GUI (computer speakers) to draw attention, Setting TAB immediately to Access Control to show the person that has been authorized in this case, then Setting Tab after 30 seconds back to LIVE to remove the Access Control info. Finally, it Activates Monitor 1, which brings the CMS4 software to the forefront if a window is open over it.

Event

Actions

2. Display camera, etc when Door Open Too Long 

This task will play a noise and display a layout (camera full screen) to alert when a door has been propped open for too long. It plays a more urgent sound to get attention. This alerts staff to a problem at a specific door.

Event

Actions

These are just a few examples of popular PDK Access Control schedules in the Client-Side Scheduler of our AVM software. 

As you use your system, you will learn to customize the schedule to suit your specific needs, as every building and every user is unique.

More information regarding the Platinum CCTV Integration with ProdataKey can be found here on their website.