A command centre is the one room that must work when everything else does not. Designing it for the normal day is the standard mistake.
Charles Trinh designs command and operations centres from Las Vegas, Nevada: video wall and source routing, operator positions, redundant paths for power and network, and a degraded mode that is tested rather than assumed.

The room exists for the incident. That means redundant sources, a control path that survives the loss of the control system, and a documented degraded mode an operator can enter without a technician.
If the wall can only be reconfigured from one laptop in one drawer, the room has a single point of failure that nobody wrote down.
Eight hours in front of a wall is a physical task. Viewing distance, screen height, ambient light, console depth and the position of the phone all affect how long an operator stays effective.
The design is measured, not chosen from a catalogue. It also accounts for the second and third shift, when fatigue is highest.
A wall is a routing problem: many sources, a few windows, a layout that changes per incident. The design names the source inventory, the window count and the preset logic.
Presets are the operational interface. An operator should be able to reach the incident layout in one action, not five.
The acceptance test is a drill: lose a source, lose a switch, lose power on one feed, and confirm the room still shows what the operator needs.
That drill produces the run book, and the run book is what makes the room usable by people who were not in the design meetings.
A command centre is only as good as the people in it at three in the morning. That makes the staffing model part of the design: how many positions, what each one watches, what the handover note contains, and how a new operator is trained.
The training material is usually the last thing written and the first thing used. A short guide with the ten most common incidents, the preset that corresponds to each and the escalation contact turns a new hire into a useful operator in a week instead of a quarter.
The room also needs a rhythm outside incidents: a daily check of sources and recordings, a monthly test of the degraded mode, and a quarterly review of whether the wall still shows what the organisation actually needs to see.
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.
Las Vegas command centres span resort security, utility operations, healthcare transfer centres and public agencies, each with a different incident rhythm.
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.
Teams searching for command centre design near Las Vegas usually need a room that behaves in an incident, not a wall that looks impressive in a photograph.
The routing, layout and ergonomics; the physical wall is specified to that design.
Redundant sources, redundant control path, and a degraded mode that is drilled.
Yes, usually in phases with a temporary operating position.
Yes, from the acceptance drill.
Four to six weeks for a single room.
trinh.io · Services · Las Vegas, Nevada · charles@trinh.io · 702-559-3489