Configuration and migration guidance for replacing or supplementing legacy readers with mobile access.
Product and selection guidance
Touch io can reuse typical reader wiring and supports Inside/Out behavior on applicable configurations. Design must document Wiegand format, cable/power limits, reader location, ingress/egress logic, mobile-device restrictions and existing badge fallback. A reader upgrade alone does not encrypt the Wiegand link to the controller.
- Legacy reader replacement and wiring validation
- Inside/Out detection and range configuration
- Credential issuance, revocation and offline phone use
- Wiegand security limitations and future OSDP strategy
- Door preparation, life safety and accessibility
- Current availability, subscription and lifecycle support
- Administrator, credential and emergency override policy
- Training, documentation and preventive maintenance
Request a site-specific review
Supported from Charlotte headquarters and local client offices serving Massachusetts, New York and New Jersey.
Official manufacturer references
How to compare and specify this product family
For PDK Touch io Integration, Inside/Out and Reader Migration, the right model and architecture depend on the site, existing infrastructure and operating policy. A proposal should clearly document the following access-control system decisions before equipment is ordered:
- Number and type of controlled openings
- Controller, reader, lock and credential compatibility
- Cloud or on-premise administration and ownership
- Offline behavior, backup power and emergency operation
- Directory, HR, video, visitor and elevator integrations
- Licensing, cybersecurity, training and lifecycle support
Installation, testing and handoff
A site survey records each opening, door hardware, cable path, power, network, credential policy and integration requirement. The design then maps readers, controllers, locks, inputs, outputs and administrator roles to the operational workflow. Commissioning includes door-by-door functional tests, failure-mode and backup-power checks, permission and schedule tests, event verification, administrator training and as-built documentation. Product availability, subscriptions and supported integrations are confirmed for the current project before procurement.
Frequently asked questions
Questions that come up when a property replaces or supplements legacy readers with PDK Touch io and mobile credentials.
Do we have to pull new cable to every door to install Touch io?
Not in every case. Touch io can reuse typical reader wiring, so an existing run is a candidate for reuse. The design still validates that run against cable and power limits and records the Wiegand format the controller expects. A run that fails validation gets replaced, and that finding comes from the wiring survey, not from the reader datasheet.
Will Inside/Out work at every door we plan to convert?
Not automatically. Touch io supports Inside/Out behavior on applicable configurations, so each opening is checked against the configuration in place before it is included. Where it applies, detection and range settings are configured for that reader location, and the ingress and egress logic is documented so phone users and badge users are handled the same way at that door.
Does moving to Touch io secure the link between the reader and the controller?
No. A reader upgrade alone does not encrypt the Wiegand link to the controller, so the connection between reader and panel carries the same exposure it had before. If encrypted reader communication is a requirement, treat it as separate scope and plan a future OSDP strategy around the controller platform rather than around the reader swap.
Do employees keep their current badges during the rollout?
Yes, when existing badge fallback is carried through the design, which is one of the items the design has to document. The current card population and its Wiegand format are recorded before any reader is changed out. Credential issuance and revocation rules are written at the same time, so a departing employee’s card and phone are closed out together.
Is this only a reader swap, or does the door need work?
It depends on what the opening already has. The design sets the reader location with cable and power limits in mind, while door preparation, life safety and accessibility are scoped as their own line items for each opening. A swap at an existing backbox is a smaller job than an opening needing new preparation, and the survey separates the two.
What if a user’s phone has no signal when they reach the door?
That depends on how offline phone use is configured for the site, which is recorded together with credential issuance and revocation. Mobile-device restrictions belong in the same record, since a policy that blocks certain devices changes who can open a door at all. The administrator, credential and emergency override policy names the fallback when a phone cannot be used.
ProdataKey owner, administrator and buyer resources
Discuss ProdataKey installation, maintenance or service
Detailed guides are maintained by 360TechnologyGroup.com, the parent-company knowledge center.
Official ProdataKey touch io software, firmware and support
Official manufacturer resources. We link out rather than host firmware.
Before updating: confirm model, hardware revision, current version, entitlement and rollback plan, and schedule monitored or life-safety-adjacent systems with the administrator.