RemoteLock and EdgeState: Sequencing a Georgia Deployment
RemoteLock projects go sideways for a predictable reason. The lock is the only part of the system that cannot be moved to a better spot later, and it is usually the first thing ordered. Reversing that order is most of what makes these deployments go smoothly.
First: survey the wireless at the door, not in the hallway
OpenEdge locks are Wi-Fi devices. Every opening you intend to control has to be somewhere an access point signal is genuinely usable, measured at lock height, with the door closed, in its metal frame, in a furnished building. A reading taken from the corridor on a phone does not count. Steel frames, elevator shafts, masonry corridors and the back-of-house spaces common in older Atlanta and Macon buildings each take a bite out of the signal.
Where coverage falls short, the answer is a new access point or a wired opening. Both cost far more after the drywall is up.
Second: match the lock to the opening
The OpenEdge series splits by application. The CG is aimed at larger commercial and enterprise properties, the BG at medium commercial and office use, and the RG at residential, small office and short-term rental doors. Backset, door thickness, handing and existing prep have to be confirmed opening by opening. A schedule built from a floor plan without walking the doors will be wrong somewhere, and a wrong lock is a return, not a field adjustment.
Third: settle the network before anything is enrolled
Decide which SSID the locks join, whether that network is the same one guests or residents use, how its credentials get rotated, and what happens when the property replaces its wireless gear. Locks commissioned against an SSID nobody documented are the single most common reason a portfolio quietly drifts offline over a couple of years.
Fourth: build the access model, then enroll doors into it
EdgeState is the platform that pulls connected locks into one dashboard, with schedules, user groups and remote control across locations. Property and hospitality operators generally want it tied to software they already run, so guest and resident access is created by the reservation or the lease rather than by hand. Define the groups, schedules and integrations first, then enroll hardware into a structure that already exists.
Student housing around Athens makes this argument better than anything else in the state. Turn week is a few days in which hundreds of doors change hands. If access is driven from the housing system, the work is a data import. If it is not, it is one person with a laptop and a very long night.
Fifth: plan for Georgia weather and for batteries
These are battery-powered locks on a wireless network, and both facts matter here. Summer storms drop power often enough that the access points, not the locks, are the fragile part. A lock keeps working locally while the network is down, but remote changes queue until it comes back. Put the switches and access points serving door hardware on the same UPS protecting the rest of the network, and size the runtime for a real outage rather than a flicker.
Humidity and exposure are the other half. A covered entry is a different environment from a breezeway door taking wind-driven rain in a coastal storm. Confirm the rating for the specific model at the specific opening rather than assuming that a commercial lock is a weatherproof lock.
Sixth: hand it over properly
- Account ownership in the property’s name, with at least two administrators
- A door schedule listing model, location, network and battery type per opening
- A written mechanical override procedure and a record of where those keys live
- Integration credentials documented on paper, not sitting in an installer’s inbox
- A named person responsible for low-battery reporting and spares
KSEDCO handles RemoteLock installation, expansion and service throughout Georgia. Call (888) 360-0035.