Access Control Controller Installation in Cypress, TX, Planned for the Next Phase

Boards, buses and licenses: the three limits on growth

When a spec sheet says a system “supports 64 doors,” that figure usually hides three separate ceilings. Knowing each one is how you avoid a platform that tops out one building too early.

1. Hardware ports

Every controller board has a fixed count of reader ports, relay outputs and monitored inputs. Some platforms expand by hanging interface boards off a downstream RS-485 bus, each adding a door or two beneath one main controller that keeps the database. Others expand by adding another networked controller per door or per cluster of doors. Both approaches work; what matters is whether spare ports, room in the enclosure and power supply headroom were left for them.

2. The reader bus

With OSDP, several readers can share a single RS-485 run in a daisy chain, each on its own address, across distances well beyond what Wiegand tolerates. In a long building that changes how cable gets pulled: one trunk down the corridor instead of a separate home run to each door. Wiegand needs its own cable per reader and is generally limited to a few hundred feet.

3. Software and licensing

Management software is often licensed per door, per reader or per site, and cloud platforms bill per door on subscription. The hardware may accept a door that the license does not cover. We lay out the licensing model in the quote so that expansion costs do not surprise a board two budget cycles later.

Cardholder and event capacity count as well. A community with thousands of residents, each carrying two or three fobs, plus years of stored history, needs a controller whose local memory can hold them, because each decision at the door is made without asking a server.

Worked layout: one association, five amenity sites

The table below is a composite of a situation we see often in Cypress master-planned communities such as Towne Lake, Bridgeland and Fairfield: an association whose facilities are spread over several miles and were opened in phases. It is illustrative, not a specific client.

The point of the exercise is that the controller hardware can differ from site to site while the management platform stays the same. What should never differ is the credential format and the software, because a resident carries one fob to all five places and the manager should be able to cancel a lost fob once.

What happens when the link between buildings drops

A controller that makes its own decisions will go on opening doors for valid fobs with no network at all. That is the behavior to insist on. The consequences of an outage show up in other places:

• Changes stop propagating. A fob deleted in the software remains valid at any site that has not received the update. For a lost fob at a pool gate, that window matters.
• Events queue up. Better controllers buffer entries in local memory and upload them once the link returns; cheaper devices may simply lose them.
• Clocks drift. Schedules depend on the controller’s internal clock, so we point each controller at a network time source to keep pool hours and daylight saving changes correct.

For the physical connection, buried fiber between buildings is the most dependable choice, and because glass carries no current it also removes a path for lightning surges between structures. Point-to-point wireless is faster to deploy across a parking lot or a street when there is clear line of sight. Cellular suits remote amenity buildings where nothing else reaches, and cloud-managed controllers are built around that kind of link.

Churches, private schools and daycares: schedules and lockdown

Cypress has a large number of church campuses, private schools and early-childhood centers, and for these clients the controller’s schedule engine is the real product. One week can include weekday school hours, a Wednesday evening program, weekend services, and events booked by outside groups, each needing a different set of doors open or restricted for different people.

• Timed unlock with first-person-in. Scheduled unlocking waits until the first staff credential is presented, which means a day the campus closes for weather, or an event that gets called off, never leaves the front doors sitting unlocked.
• Lockdown input. A hardwired button, or a command in the software, tells the controller to secure every exterior door at once and suspend scheduled unlocks. Exiting from inside must still work; lockdown restricts who can enter, never who can leave.
• Classroom and nursery wings. Interior doors can be limited to staff groups while programs run and left free the rest of the week.
• Visitors. A video intercom at the entrance, released by the front office through the controller, lets staff see who is outside before anyone is admitted. Our intercom installation page covers that side.

We build these schedules with the people who actually run the building and write them down in plain language before they are programmed. A schedule nobody understands ends up overridden by a door propped open with a chair.

Signs your current controller cannot follow you to the next phase

• The software runs on one office PC and nobody else can reach it.
• Adding a door means buying a different brand, because the board has no spare ports and expansion modules are no longer sold.
• Each building has its own separate system with its own fobs.
• Readers are wired Wiegand and the new building is too far from the panel for a home run.
• The controller cannot hold the number of cardholders your community or congregation now has.
• Firmware updates ended years ago.

Any one of those is reason to plan the next controller around the whole property rather than one more door. Several together usually point to a platform change, phased so buildings convert one at a time. If the real problem is a single board that is failing, our Cypress panel replacement page addresses that case, and ZIP-level detail for 77429 and 77433 is on their own pages.

How a Cypress controller project runs with EVOTECH

1. A walk through every building in the current phase, plus a look at the plans for the next one.
2. A topology decision: which doors home-run to which controller, which sites get their own, and how each one connects back.
3. A single credential format for the whole property, with readers able to read the old cards during a changeover when needed.
4. Cable and conduit, including underground runs, with pull strings left in place for the next phase.
5. Controller, power supplies and batteries mounted, terminated and labeled.
6. Schedules programmed together with the staff who operate the building, then every door tested.
7. A written site standard covering controller model, cable types, credential format and door naming, so the next building is built the same way even if a different contractor handles the construction.

What sets the price on a Cypress controller project

The number of separate sites and the way they connect drive the price more than raw door count. After that come underground or wireless links between buildings, the lock hardware at each opening, the software’s licensing model, how many cardholders need enrolling, and whether the work has to be phased to keep amenities open. Each quote is itemized by site, so an association or church board can approve one phase at a time.

Request a controller quote for your Cypress property

Related services

Frequently asked questions