Common Area Locks Supported by ProdataKey (PDK)

The AccessIQ PDK integration allows for PDK common area/perimeter access solutions to be managed within the AccessIQ Command Center web portal and mobile apps. This provides property owners and managers with a centralized access management system throughout their entire property.

Technical characteristics of the PDK Integration:

● PDK “locks” can take on a variety of forms (e.g. readers with strike locks, magnetic locks, etc.) and AccessIQ has been extended to provide for unlocking those common areas that are secured with PDK hardware.
● Initial installation and set up of the PDK hardware (controllers, readers, locks, etc.) is expected to be done by PDK partners (resellers and/or integrators). Once the PDK installation has been completed, the installer will “hand off” the installation to the AccessIQ Property Manager (PM) through the Integrations page of pdk.io.

Setting up the PDK Integration:

Installer:
● Installer sets up an account for the site in PDK’s system.
● Installer installs PDK hardware (e.g. Cloud Nodes, readers, locks) and configures those using the pdk.io web portal.
● Installer “hands off” the PDK installation to the PM using the Integrations page in pdk.io:
   ○ AccessIQ integration is selected.
   ○ Integration is Enabled - this adds the AccessIQ integration to the account.
   ○ AccessIQ Integration is Configured - the Installer provides the PM’s email address and an invitation to     integrate is sent to the PM

Property Manager:
● PM opens the Your AccessIQ PDK Integration is Ready! email and clicks on the COMPLETE INTEGRATION button.
● If the PM manages more than one site, they must select the proper Site to Integrate from the list.
● PM clicks on the Complete Integration button to finish the process.
● At this point, the AccessIQ site and PDK account are “linked” together. The AccessIQ back-end server communicates with the PDK system to populate the account with Users, Groups (policies) and user access information (Site-wide Access Code, Access Card, Bluetooth credential). It also fetches the information for the PDK locks that the installer set up.
● If the PM has not already done so, Common Area Policies and Secured Areas must be set up before proceeding.
   ○ Each Secured Area might have more than one lock supporting it.
   ○ Each Secured Area could have different schedules and access rules for PMs, Employees, Residents and Resident Guests.
   ○ PDK locks support Remote Access where a mobile app user can tap on the lock control to unlock the door via the internet.

● Open the Locks screen and Add the PDK locks to their corresponding Secured Area.
● Assign optional PDK Access Cards to users. PDK Access Cards are a different type of card as compared to AccessIQ Access Cards. If the site issues access cards to residents, they will need a PDK Access Card for use at common area locks and an AccessIQ Access Card for use at their unit’s AIQ lock.

Common Area at Door Experiences:
Several at-door experiences are available to users for PDK locks at common areas:
● Present-To-Open (PTO):
      ○ PTO is a similar mobile device experience as presenting to an AccessIQ lock and unlocking it via Apple Wallet or Android Smart Tap. At this time, PDK locks do not support Apple/Google Wallet but they do support Bluetooth based PTO.
      ○ When presenting the phone to a PDK reader, the reader LED will react when a phone is in range of the reader.
      ○ The app needs to be running in the background on the mobile device for PTO to unlock the door.
      ○ If a user without access permission to the secured area presents their mobile device to the PDK reader, nothing will happen, i.e. the LED will not change.

● PDK Access Card
   ○ For those users who are issued a PDK Access Card, presenting the card to the PDK reader will unlock the door if the user has permission to the secured area and they are within the scheduled timeframe.

● Site-wide Access Code (SAC)
   ○ For PDK readers with a keypad, all users’ SAC (auto-generated and emailed to all new users) can be used to unlock the door if the user has permission to the secured area and they are within the scheduled timeframe.

● Remote Access
   ○ PDK locks can be unlocked remotely (via the internet) using the mobile app.
   ○ PMs define which Common Areas are able to be unlocked per role when they set up the policy. By default, residents are not Allowed Remote Access for unlocking common area doors. The setting in the web portal is the same as for AIQ locks, but instead of gateways controlling PDK locks, that is accomplished by an unlock command sent via the internet to the PDK cloud node that controls the lock.
   ○ Using the mobile app, the user need only tap on the lock control for the common area to unlock the door. The app will display the unlocked icon and it will be gray to indicate that the user cannot lock the door using the app. Instead, the lock will auto-lock after the dwell time that is configured in pdk.io 

PDK Lock States:

The mobile app will display different icons for different states of the PDK lock.

Activity Log Changes:

The Access Log for PDK locks include events for:
● Integration Added
● Integration Removed
● Lock Added to Site
● Lock Removed from Site
● Remote Unlock
● Unlock (PTO)
● Site-wide Access Code Unlock

Dynamic Updates: 

The PDK integration with AccessIQ is dynamic and any changes made through the web portal that affect the site’s PDK locks are transmitted to the PDK system in real-time. Changes include:
● Adding and removing users (move-in, move-out)
● Adding a PDK Access Card to a user’s account
● Changing the schedule for a common area
● Removing a PDK lock from the site

Dynamic updates for PDK access from the mobile app include:

• When a user signs into the mobile app the first time, the user's mobile device gets registered with the PDK system.  The PDK system generates the Bluetooth credentials for all PDK locks for which the user has access.  It can take a few minutes for the process to complete and for the Bluetooth credential to be available for unlocking doors.
   
• If a user deletes the mobile app, their Bluetooth credential and all other user's data gets deleted on their mobile device.  Their Bluetooth credential in PDK's cloud is retained, however, and will be sent back to the user if/when they sign into their account again on a mobile device.

Troubleshooting

● If PTO at a PDK lock for a user does not work, it can be for a variety of reasons:
   ○ The user does not have permission to access the secured area.
   ○ Outside scheduled access - visible in the mobile app.
   ○ Bluetooth related issue on the mobile device:
      ■ Something might be wrong with the user’s Bluetooth credential. Using the mobile app, sign out and sign in again to see if that resolves the issue.
      ■ Since PTO relies upon Bluetooth services, permission to use Bluetooth and the current setting for Bluetooth on a mobile device, Consult the Bluetooth troubleshooting article.
      ■ The user might have force closed or force stopped the AccessIQ app. In this state, the AccessIQ app is unable to respond to Bluetooth connection requests from the PDK lock.

Disabling the PDK Integration

In the unlikely event where a property decides to remove PDK locks from their site, the PDK integration needs to be removed so that all lock permissions, Access Codes and Cards are removed from the associated PDK account. The PM needs to follow these steps to remove the PDK integration:
● From the web portal, open the Site Overview / Site Details screen.
● Click on the pencil icon to edit the PDK Integration.
● In the field provided, enter the PDK System Name and click on Remove System Integration.

● NOTE: It can take several minutes for the PDK system to complete the process of removing all People (including Bluetooth credentials, Access Codes and Cards) and Groups (Access Policies) from the account.