Access control and building security upgrade

With Pentillion Construction, I helped coordinate an access-control and security-system upgrade for a commercial building. The work included access-controlled doors, elevator access, cameras, wiring routes, and the operational requirements needed by both the landlord and tenants.

The project was not just a matter of selecting hardware. The scope had to balance security, usability, cost, code requirements, tenant disruption, and long-term building operations. I helped define which access points needed to be controlled, what the system needed to do, and how the work could be coordinated across the security contractor, electricians, elevator company, automated door contractor, tenants, and landlord.

One of the key constraints was elevator access. The building needed more controlled access to certain areas, but a full elevator-control upgrade would have added cost and complexity beyond the practical scope of the project. I worked through the requirements with the contractor and helped shape a solution that controlled access where it was needed without overbuilding the system.

The project also required code interpretation around the building’s crossover floor. Because the crossover floor formed part of the life-safety and exiting strategy, the access-control approach had to preserve the required function of that floor rather than treating every door as a simple security device. That added an important check on the design: the system still had to support safe movement and code-required access while improving security.

I also coordinated wiring routes with the contractor and helped manage the system after installation. That included programming useful operational automations, such as event-based actions that supported day-to-day security and reduced manual steps for building management.

The result was a more practical access-control system that served landlord and tenant needs without turning the project into a larger elevator-modernization or building-wide security rebuild. It shows the value of defining the real operating requirements before selecting a technical solution, then coordinating the trades and code constraints needed to make the system work.

Enterphone data recovery and audio repair

A building’s Mircom TX3 enterphone failed, and the first risk was not just getting the hardware working again. The resident directory and system configuration also needed to be protected. Replacing the controller board without recovering the data could have turned a hardware failure into a larger setup and handoff problem.

I traced the failure through the power supply, transformer, door strike circuit, phone line, and controller board. The likely failure was in the board’s low-voltage power section, where a small surface-mount capacitor had burned.

Instead of immediately replacing the board and losing the configuration, I powered the damaged board with a current-limited DC bench supply. That let me bring the board up carefully, confirm that the internal 5V and 3.3V logic rails were stable enough to communicate, connect to the TX3 software, and recover the resident names and configuration before replacing the board.

After the new board was installed, I updated the configuration and verified the building functions tied to the panel. That included the postal lock input, door strike operation, grounding, phone-line settings, and relay behaviour. The goal was to leave the system in a known working state, not just swap the failed component.

There was also a call-audio issue where the caller’s voice became quiet after the call connected. I tested microphone gain, speaker level, DTMF sensitivity, and echo-reduction profiles. The issue appeared to be aggravated by sound reflecting inside the panel and around the speaker/microphone assembly, which could cause the echo reduction to clamp down unnecessarily.

I repaired and sealed the broken speaker enclosure and started working on a simple acoustic treatment around the microphone to reduce reflected traffic noise. It was a small repair, but it reflected the same troubleshooting approach as the board recovery: trace the system, protect the important data, verify the handoff, and keep looking when the first fix does not fully solve the user experience.