Authorized · Certified · Carolinas
Authorized ProdataKey dealer, certified installer and integrator
360 Mobile Vision sells, installs, programs and services ProdataKey for businesses across North and South Carolina — Cloud Nodes, Red controllers, Touch io readers and pdk.io cloud administration. Being the authorized dealer as well as the installer is what gets you genuine equipment, a valid warranty and a manufacturer support path when something needs escalating.
- DealerWe quote and supply genuine ProdataKey equipment, licensing and subscriptions.
- InstallerOur own technicians run the cable, mount the hardware, set the software up and test it — not a subcontractor you have never met.
- IntegratorWe make it work with the cameras, doors, network and identity systems already in the building, rather than leaving you with two systems that do not talk.
- Still here afterwardsService, repair, expansion and takeover of systems somebody else installed. Emergency cover round the clock.
Access control product-family guide
A defensible PDK Touch design connects controllers, readers, credentials, locks, software and integrations to the actual openings and user workflow. This page organizes the principal product families and the field decisions that should be settled before equipment is purchased.
Start with the system architecture
PDK Touch product names describe parts of a solution, not the complete installed result. A responsible design also covers power, pathways, network, software or subscriptions, compatible accessories, integrations, environmental conditions, user administration, testing and long-term support. Those dependencies should be visible in the proposal instead of left for the field team to discover.
The product-family sections below summarize the principal choices represented on this site. Availability, model numbers, software packaging and regional support can change. Final selection is verified against current manufacturer documentation and the actual site before procurement.
New systems
Develop the architecture from measured conditions, operating requirements and a written acceptance plan.
Existing-system expansion
Inventory installed models, versions, licenses, capacity and support status before promising compatibility.
Phased migration
Separate reusable infrastructure from weak credentials, obsolete controllers, unsupported software and unreliable field devices.
Multi-site standards
Create repeatable naming, configuration, testing and handoff rules while preserving a survey for each location.
PDK Touch io Integration, Inside/Out and Reader Migration
This product-family guide addresses Product and selection guidance, Legacy reader replacement and wiring validation, Inside/Out detection and range configuration.
- Product and selection guidance
- 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
- PDK Touch io documentation
- PDK reader documentation
- Number and type of controlled openings
Open the detailed PDK Touch io Integration, Inside/Out and Reader Migration guide
PDK Touch io Reader and Mobile Credentials
This product-family guide addresses Product and selection guidance, BLE mobile credential and ProdataKey App workflow, 125 kHz legacy card/fob coexistence and migration.
- Product and selection guidance
- BLE mobile credential and ProdataKey App workflow
- 125 kHz legacy card/fob coexistence and migration
- Cloud Node, pdk.io controller and subscription requirement
- Adjustable read range, IP65 mounting and Wiegand wiring
- Door preparation, life safety and accessibility
- Current availability, subscription and lifecycle support
- Administrator, credential and emergency override policy
- Training, documentation and preventive maintenance
- PDK Touch io overview
- Touch io datasheet
- Number and type of controlled openings
Open the detailed PDK Touch io Reader and Mobile Credentials guide
Decisions to document before ordering PDK Touch
Use these questions to turn a feature discussion into an installable scope. Any item that remains unresolved should appear as an assumption, allowance or exclusion rather than becoming an undocumented field decision.
- Inventory every controlled opening, frame, lock, reader, request-to-exit device, contact, power supply and reusable cable.
- Choose cloud, on-premises or hybrid administration and assign ownership for identities, schedules, visitors, backups and renewals.
- Confirm controller capacity, reader protocol, credential technology, lock compatibility, offline behavior and standby power.
- Map video, intrusion, intercom, elevator, fire-alarm, HR, directory and property-management integrations before ordering.
- Document free egress, accessibility, door hardware, emergency release, mechanical override and other trade responsibilities.
- Define acceptance tests for valid, invalid, emergency, outage, mobile and administrator scenarios.
Reuse, migration and lifecycle review
An existing system may contain a mix of serviceable field hardware and components that are no longer secure, supported or economical. Record model and serial information, firmware and application versions, active licenses, administrator access, backups, warranties, spare capacity and known faults. Test reused devices instead of assuming they work because they are present.
Compare continued support, partial modernization and replacement using lifecycle cost and operational risk. A lower initial price can be misleading if the client inherits unsupported software, weak credentials, subscription surprises, proprietary dependencies or an undocumented integration. The handoff should identify official support resources and state who owns updates, renewals, backups and recovery.
Project delivery and acceptance
1. Discovery
Define the operating problem, users, sites, critical areas, policies, existing assets and success criteria.
2. Field verification
Measure conditions, inspect infrastructure, photograph constraints and resolve responsibilities shared with other trades.
3. Design and deployment
Approve models, capacity, licensing, pathways, settings, integration ownership, test cases and the installation sequence.
4. Closeout
Resolve exceptions and provide labels, test records, versions, diagrams, backups, training and official support routes.
North and South Carolina projects are coordinated from Charlotte. Coverage and scheduling depend on the site count, scope, required trades, field conditions and support expectations.
PDK Touch planning questions
Can existing equipment be reused?
Possibly. Reuse depends on exact models, condition, protocol, firmware, software support, capacity and the target security or performance level. A survey and supported compatibility check are required before reuse becomes part of the proposal.
How are product models selected?
Models are selected from the required function, site conditions, capacity, environment, integrations, lifecycle and current availability. A catalog feature alone is not a substitute for those design inputs.
Who manages software, subscriptions and updates?
The project scope should name the client and service responsibilities for accounts, licenses, renewals, backups, release review, maintenance windows and recovery. Software and firmware come only from official manufacturer resources.
What should be tested at handoff?
Acceptance should prove normal operation, invalid or exception behavior, loss of power or communications, alerts, integrations, user permissions, reporting and the owner’s ability to perform routine administration.
Can 360 Mobile Vision service an existing PDK Touch system?
We can inventory the installed environment, identify deficiencies and evaluate repair, expansion, migration or replacement. Manufacturer entitlement, administrator access and current support status are confirmed during discovery.
Official product and lifecycle resources
Use current manufacturer-controlled documentation for model availability, software, firmware, compatibility and release notes. 360 Mobile Vision links to official resources and does not redistribute firmware files.
Build a site-specific PDK Touch scope
Share the locations, quantities, existing models, required integrations, network or power constraints, desired schedule and support expectations. That information allows a focused survey and product-family comparison.
Related services, products and planning guides
PDK IO®
Use the PDK IO® guide to compare compatible equipment, integrations, deployment choices and lifecycle responsibilities related to this project.
Property Management
Use the Property Management guide to compare compatible equipment, integrations, deployment choices and lifecycle responsibilities related to this project.
Retail
Use the Retail guide to compare compatible equipment, integrations, deployment choices and lifecycle responsibilities related to this project.
School
Use the School guide to compare compatible equipment, integrations, deployment choices and lifecycle responsibilities related to this project.
Security Company home text
Use the Security Company home text guide to compare compatible equipment, integrations, deployment choices and lifecycle responsibilities related to this project.
ProdataKey owner, administrator and buyer resources
Carolina clients can use the parent-company technical guides to prepare new installation, expansion, software, maintenance and repair requirements before field work.
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
Use the manufacturer links below for current software, firmware, release notes, manuals and technical resources. 360 Mobile Vision links directly to official manufacturer portals and does not copy or host firmware files.
Before installing an update: verify the exact model, region, hardware revision, current version, required intermediate releases, licensing or support entitlement, backup and rollback plan, integrations and maintenance window. An incorrect firmware package or upgrade sequence can interrupt service, invalidate compatibility or prevent a downgrade. Coordinate updates for monitored, life-safety-adjacent or business-critical systems with the system administrator and an authorized specialist.
Some resources require a customer, dealer, certified-technician or active-support login. Cloud-managed products may update automatically and may not provide a public firmware file.