Door Schedule & Access Profile Setup in Houston, TX 77095

Before anything is changed: reading the schedules already running

On an inherited system the first hour is spent reading, not typing. We export the schedule list, the access level list and the door table exactly as they stand, and that export is your rollback — the only version of the truth that survives if a change goes sideways at four on a Friday.

What that pass turns up in a Copperfield-era building is consistent enough to predict:

• Schedules named TEST, NEW or tmp2 that are still live and still attached to a door.
• Two schedules with identical hours, because two different technicians each built one rather than reuse the other’s.
• Access levels pointing at a schedule deleted years ago, which behaves differently on every platform and never predictably.
• An exterior opening in permanent unlock, with a mechanical cylinder doing the only real work after dark.
• A credential list longer than the number of people who have ever worked there.

We hand that back as a written before-picture. Plenty of 77095 owners decide the picture alone was worth the visit — you cannot govern hours you cannot see.

The four door modes, and which one each opening deserves

Every opening is in one of a small set of states at any minute. Naming them out loud is usually the fastest way to settle an argument about hours:

The mode that causes the trouble is the second one. An unlocked door produces no record of who came in, so when something goes missing on a Tuesday afternoon the access system has nothing to say. That is not a reason to lock a building the public is meant to enter — it is a reason to be deliberate about which openings are in that mode and for exactly how long.

One more state deserves a question at the panel: some controllers fall back to a degraded mode when they lose the host, accepting anything with a matching facility code. Ask what yours does, and prove it by pulling the network cable.

Fail-safe, fail-secure, and what your doors do when the schedule is gone

A schedule lives in the controller. The lock does not care about it. The moment power or the panel goes away, behaviour is decided entirely by how the opening was built, and in older 77095 suites that is frequently a mix nobody documented:

• Fail-secure electric strike. No power, still locked from the outside. The common choice on a front entry, and the reason a power cut does not open a building.
• Fail-safe strike or magnetic lock. No power, released. Required where a lock must never impede egress, and it means an outage leaves that opening standing open.

We routinely find a fail-secure strike on the front of a Highway 6 suite and a magnetic lock on the rear with no documented release path — no one on site can say what drops it. A magnetic lock’s release is wired, through listed release devices and the fire alarm interface, and it must drop regardless of what any schedule says. That is not a setting; it is a circuit, and it gets tested physically with your fire alarm contractor present.

Multi-tenant buildings: who owns which schedule

The strip and office properties along Highway 6 and West Little York are mostly multi-tenant, and access control there has an ownership question long before it has a technical one. The suite reader usually sits on the landlord’s panel, which means the tenant cannot change their own hours without calling a property manager who may have started last month.

Written boundaries settle it faster than any configuration:

• The landlord owns the common entries, the shared rear service corridor and the holiday table, because those affect every tenant at once.
• The tenant owns the suite door, its own profiles and its own staff list — the part that changes every time somebody is hired.
• Both get read access to the events for their own doors. An audit trail nobody may read is a log file, not a control.

Two habits from these buildings are worth copying. Align the access calendar with the after-hours HVAC timeclock — a lobby unlocked while the air is off generates complaints that land on the access company by mistake. And handle the propped rear corridor with a door-held-open timer and a local sounder, not a scheduled unlock that hands the service hallway to the whole centre for three hours.

Panel time, daylight saving, and the drift nobody reports

Schedules are only as accurate as the clock enforcing them, and a controller keeps its own. On a panel that has been running without a network time source, drift accumulates quietly until someone notices the front door releasing a few minutes late and cannot say when it started.

• Check the clock at the panel, against a phone, standing in front of it. The workstation’s time is not evidence; the workstation is not the thing unlocking the door.
• Confirm the daylight saving rule in firmware. The United States moves on the second Sunday in March and the first Sunday in November. Older or wrongly regioned firmware can be an hour out for a week each spring, or permanently.
• Check the clock battery. A panel that loses time at every power blip has a finished onboard battery, and after a Gulf Coast outage the schedules come back wrong.
• Test intervals that cross midnight. Platforms disagree on whether 22:00 to 02:00 is one interval or two. Build it, then stand at the door at midnight once and watch.

Server time zone is worth a glance too: a head-end restored from backup or moved to a hosted machine can come back in the wrong zone and shift every schedule by an hour without touching a single interval.

Rebuilding access profiles without re-badging the building

Owners assume that cleaning up permissions means collecting and reissuing every badge. It does not. Credentials stay exactly where they are; what changes is the profile attached to them. The rebuild runs alongside the live system rather than replacing it:

1. Build the new role-based profiles next to the old ones, named for the job and the hours — Suite-Staff-Business, Janitorial-Evening, Vendor-Escort — so a log line reads in English.
2. Move one department or one tenant at a time, leaving the old level in place.
3. Watch the events for a week. Denials at the wrong door surface immediately and cost nothing to fix at this stage.
4. Only then remove the old level — and never delete a schedule an access level still references, which is precisely how the orphaned pointers in the audit section were created.

Two rules survive every building we have done this in: nobody gets round-the-clock rights because it is easier than asking, and no profile is built for one person unless that job is genuinely unique. When the profile count starts climbing toward the headcount, the design has failed.

Proving it works: the walk test we do not skip

Configuration that has only been seen on a screen has not been tested. Every boundary gets walked, at the door, with a credential in hand:

• Just before an interval opens, just after it opens, and just after it closes — three reads at each opening that changes mode.
• One simulated holiday, so the closure is proven before the closure matters.
• Lockdown triggered, then cleared. A lockdown nobody can clear is its own emergency, so the clearing procedure is written down and handed to two people.
• The network cable pulled, to see what the controller does on its own, and the event log read afterward — because the point of all of it is that next month’s question has an answer.

When a boundary can only be proven at the hour it happens — a six a.m. release, a nine p.m. relock — we come at that hour rather than shifting a test schedule and hoping somebody remembers to shift it back. Abandoned test schedules are among the most common things we find on an inherited system.

What a schedule rebuild in 77095 depends on

No dollar figures over the phone — on an inherited system nobody can price what they have not read. The variables:

• How much documentation exists. A building with a current door schedule and a known admin login is a fraction of the work of one where the password left with a manager three years ago.
• Head-end age. Whether the installed version still supports holiday groups, per-reader PIN modes and first-credential unlock decides whether this is configuration or a platform conversation.
• Hardware corrections. Missing contacts, dead request-to-exit sensors and undocumented magnetic lock releases turn a programming visit into an installation.
• Tenant coordination and night testing — every hour change agreed before it is built, and boundaries that only exist at night proven at night.

The on-site estimate is free and itemised: audit, configuration and hardware on separate lines.

Related services

Frequently asked questions