A resort is a building where the network is part of the product. When it fails, the guest notices before the help desk does.
Charles Trinh designs resort and casino technology from Las Vegas, Nevada: property and guest networks, surveillance, access control, point of sale and the change control that keeps a live floor running during a renovation.

Guest wireless, point of sale, surveillance, building systems and back office run in one building and must not reach each other. Segmentation is the design that keeps a compromised television from touching a cash register.
The hard part is the change: a new outlet opens, a vendor needs a port, a camera is replaced. Without a written rule set the segmentation erodes in a year.
Property work happens while guests are present. The design has to sequence cutovers so that each one is reversible in minutes, with a rollback tested before the night it is needed.
Maintenance windows are negotiated with operations, not assumed. The plan names who can approve a cutover and what the abort condition is.
Camera and door systems are the two that carry legal weight. Retention periods, time synchronisation and chain of custody matter more than resolution when a recording is requested.
Access control is the quieter risk: a badge system that is never audited is an inventory of who could enter a room last year.
Resort systems are maintained by a mix of internal staff and specialty vendors, each responsible for a slice. The failure is usually in the seams.
A written responsibility matrix, with escalation contacts and response times, is worth more than another monitoring screen.
A renovation turns a stable property into a series of small changes, each individually safe and collectively disruptive. The control that works is a single change calendar that every trade reads, with the cutover time, the abort condition and the name of the person who can stop it.
Two rules earn their keep. No cutover on a night with a scheduled show or a high occupancy forecast. And every cutover has a tested rollback, not a hoped-for one, because the moment of failure is the worst moment to improvise.
The third rule is duller and more important: the as-built drawings are updated the same night, not at the end of the project. A property that loses its drawings during a renovation spends the next five years paying for it.
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.
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.
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.
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.
The valley has more hotel rooms than any other market in the country outside Orlando, and most of the properties run on a vendor stack chosen decades ago and extended ever since.
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.
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.
Serving customers in Columbus, Ohio, United States and worldwide.
Properties searching for resort technology help near Las Vegas usually need someone who can walk a back-of-house corridor and read the as-built drawings.
Yes, with the compliance boundaries respected and documented.
Cutovers are usually scheduled when they least affect the floor, which is often overnight.
No. The design sets the standard the integrator builds to.
It is treated as a product requirement, not an IT convenience.
A fixed assessment, then a phased plan priced per phase.
trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489