Charles Trinh · Las Vegas, Nevada · Access control

Charles Trinh - access control design in Las Vegas, Nevada

An access control system is an inventory of who can enter every room, and most organisations never audit it after the first year.

Charles Trinh designs access control from Las Vegas, Nevada: door and hardware schedule, credential and reader choice, controller placement on a segmented network, and the quarterly review that keeps the access list truthful.

Charles Trinh - T markCharles Trinh · Las Vegas, Nevada · trinh.io
Access control and credential design, Las Vegas Nevada

Hardware before software

The door decides more than the platform: fail-safe or fail-secure, request-to-exit, door position switch, and whether the frame can carry the hardware chosen.

A platform is easy to replace. A door cut wrongly is a construction change order.

Credentials and readers

Cards, fobs, mobile credentials and biometrics each carry a different cost and a different failure mode. The design names what happens when a credential is lost, and who can revoke it.

Readers belong on a segmented network with the controllers, not on the general office VLAN, because a compromised reader should not be a route into the building systems.

The audit

Badge lists grow. Terminated staff keep access, contractors keep credentials, and shared cards defeat the log entirely.

A quarterly review with the HR and facilities lists, producing a signed exception list, is the control that makes the system meaningful.

Integration with HR and surveillance

Access control is the physical half of a joiners and leavers process. When HR adds a person, the badge should exist; when HR closes a record, the badge should stop working the same day. Most organisations do that by email and memory.

A scheduled reconciliation against the HR list, with exceptions signed off, is the control that closes the gap. It is unglamorous and it is the difference between a system and an inventory of who might still get in.

Surveillance integration adds a second requirement: time. Cameras and controllers drift, and a recording that is ninety seconds out of step with the door event is a recording that will be argued about. Time synchronisation is part of the design, not an afterthought.

The last piece is the exception list. Every site has doors that stay propped, cards that are shared and a service entrance with a key under a mat. Writing those exceptions down, with the risk accepted by a named person, is what separates a managed system from a hopeful one.

Badge photography and identity proofing belong in the same register as the credential itself, because an access decision that cannot be traced to a verified person is difficult to defend after an incident.

Where a site has already been audited, the finding that repeats is rarely the hardware: it is the missing review, the stale list and the door that everyone agreed to leave propped.

How an engagement runs

It starts with a scoping call of thirty to forty-five minutes. The point is not to sell; it is to establish what decision has to be made, what constrains it, and whether this is the right kind of work for one architect rather than a team. If it is not, the call ends with a referral.

If it is, the next artefact is a written plan: scope, sequence, price and the evidence each step will produce. Nothing starts before that plan is agreed in writing, and nothing in it is a surprise later. Plans change, and when they do the change is written down with its effect on price and date.

Delivery runs in weekly checkpoints. Each one ends with something that exists: a document, a design, a working system, a test result. That is deliberate, because a programme that reports progress without artefacts is a programme that cannot be audited, handed over or defended.

Pricing and terms

Two shapes. A fixed price for a defined deliverable - an assessment, a design, a due-diligence report - where the scope is clear enough to price honestly. Or a monthly seat for continuing advisory work, with a set number of days and a standing slot for decisions.

Invoices are monthly, net fifteen, and the terms are the same for every client. There is no percentage of savings, no success fee and no commission from a vendor, because an advisor paid by the seller is not an advisor.

What to prepare before the first call

Nothing formal. What helps is a one-page description of the problem in your own words, the names of the systems involved, the deadline that is driving the timing, and who else has to agree before anything changes.

If a vendor proposal is already on the table, send it. Reading someone else proposal is often the fastest way to find the question nobody asked, and it costs nothing to look.

Why the written record matters

Every engagement leaves a record: the map, the decisions, the trade-offs that were rejected and why. That record is what makes a change of staff survivable, what an auditor reads, and what a buyer inspects. It is also the part most consultancies keep for themselves.

The record settles arguments. When a decision is questioned a year later, the note that states what was known, what was chosen and what it would cost to change is usually the only thing that ends the discussion.

Working in Las Vegas, Nevada

Las Vegas properties mix long-term staff, seasonal hires and contractors, which makes credential lifecycle management the highest-value part of the design.

Scope and terms

Scope is a fixed number of hours per month or a defined project, agreed in writing before work starts. Every engagement carries a written plan, a weekly checkpoint, and a closing pack that states what was built, what was verified and what is left.

What the engagement produces

Services and expertise in Las Vegas, Nevada

Charles Trinh is a Las Vegas-based technology architect and fractional CTO/CIO serving health systems, payers, enterprises and government programmes in Nevada and nationally. Every discipline below is offered in ten engagement forms - consultant, architect, advisor, contractor, specialist, expert, services, support, solutions and consulting - so an engagement can be a review, a build, a retainer or an interim role.

The full catalogue, every discipline in all ten engagement forms, sits on the Las Vegas, Nevada services index. Delivery is remote-first from Las Vegas with on-site coverage across Clark County, and the same ten disciplines carry to engagements anywhere in the United States and in 264 countries.

TRINH - Charles Trinh, technology architect
Charles Trinh

Charles Trinh

Fractional CTO/CIO and Technology Architect - Las Vegas, NV

Las Vegas, Nevada - US citizen - Fractional and project engagements

(702) 559-3489 Email Charles Trinh

TRINH

Services near me — Las Vegas, Nevada, the United States and worldwide

Serving customers in Columbus, Ohio, United States and worldwide.

Facilities teams searching for access control design near Las Vegas usually need the door schedule and the audit process more than another platform demo.

Questions about access control

Do you install the system?

The design and the standard; installation runs through an integrator.

Can you audit our existing badge list?

Yes, that is usually the first engagement.

Do you support mobile credentials?

Yes, with the failure mode documented.

What about integrations?

Surveillance, alarm and HR data flows are designed explicitly.

How long does a design take?

Three to five weeks depending on door count.

trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489