ops centre · display wall · incident room
Charles Trinh — Command Centre Design, Las Vegas NV

Designing an operations or command centre: sight lines and ergonomics, display wall technology, the data that actually belongs on the wall, and the procedures that make the room useful.
Design the room around the decision
A command centre exists to support decisions under time pressure; every screen should answer a question someone is accountable for answering.
Start from the incident procedure and work backwards to the displays, not from the display wall outwards.
If a panel never changes a decision, remove it; a wall of ambient dashboards trains people to stop looking.
Sight lines and ergonomics
Seated eye height, viewing distance and monitor height determine whether the room is usable for eight hours or for twenty minutes.
Test with real operators at real shift length before committing to furniture and screen counts.
Provide desk-level control, because a room where one person controls all layout produces conflict and nobody uses it.
Display technology
Direct-view LED for large, bright, seamless walls; LCD video wall where cost matters; projection only where ambient light is controlled.
Seams and brightness uniformity matter more than resolution at distance, and they are what people complain about after installation.
Include a smaller, always-on operations display outside the room, because the big wall is rarely viewed except during an incident.
Data and sources
Agree the source systems, the refresh cadence and who owns each panel before the integrator arrives.
Normalise into a single data layer, because six browsers tiled across a wall is not a display system.
Record the refresh interval on the panel itself; a dashboard showing yesterday's numbers without a timestamp is actively misleading.
Audio, comms and recording
Separate the room audio from the incident bridge, and make it trivial to record a decision without recording patient identifiers.
Test the bridge with the actual conferencing platform the organisation uses, not a generic room system.
Provide a documented way to bring remote participants in without exposing the whole room.
Procedures that make it work
A room without a procedure is a meeting space with expensive screens; write the escalation, the roles and the log.
Assign a named duty operator per shift and rehearse one scenario per quarter with a written output.
Review after each activation: which panel was used, which was ignored, and what should be removed.
How I do it
One trace of a real case with timestamps at every hop, before any document is written.
A findings list naming the defect, the system, the owner and the date, reviewed monthly.
No attestation I did not test, and no template sold as an assessment.
The room is a procedure with furniture
A command centre that has no activation procedure becomes a room people book for meetings, and the displays become a backdrop for slide decks. Write the activation criteria, the roles, the communication plan and the log before specifying a single screen, because those documents determine how many people need to sit in the room, what they need to see and what has to be visible at a glance. The displays follow from the procedure, and a centre designed the other way around ends up with capacity nobody uses and data nobody reads.
The activation criteria should be specific enough that two different duty managers would make the same call: a defined severity, a defined number of affected users, a defined external event. Vague criteria produce inconsistency, and inconsistency produces a room that is activated for some incidents and not others, which erodes the procedure faster than any technical failure. Review the criteria after each activation, because the first three events always reveal a category nobody anticipated.
Data ownership and the panel contract
Every panel on the wall needs a named owner, a defined refresh interval and an agreed definition of the number it shows, and that contract should be written down before the integrator builds anything. The recurring failure is a panel that shows a plausible number computed differently from the operational report, which produces an argument during an incident about which figure is right. A single data layer that normalises sources and publishes a dated contract removes the argument and makes the panel trustworthy enough to act on.
Where a source cannot be integrated reliably, show its age prominently rather than hiding the problem behind a green tile. A panel that says the last update was forty minutes ago is doing its job; a panel that shows a stale number as if it were current is actively harmful, because it converts an outage into a decision. Building that honesty into the display contract is cheaper than discovering it during the incident the wall exists for.
The quiet period problem
A centre that is only used during incidents is a centre that decays: the furniture, the practice and the people all drift, and the first real activation is also the first rehearsal. Give it a secondary, low-intensity use that keeps it occupied without creating noise, such as a daily operational huddle with a fixed agenda and a log. The huddle is what maintains familiarity with the panels and surfaces the ones that are wrong while the stakes are low.
Record the huddle in one line per day and review the log weekly for the questions people had to ask. Those questions describe what the wall is missing, which is more useful than any requirements workshop. The same log becomes the evidence that the room operates rather than merely exists, which matters when the centre is reviewed for budget or reorganised by whoever comes next.
The centre after the incident
The value of a command centre is highest in the twelve months after an incident, when interest is high and the procedures are fresh, and lowest three years later when the room has become a meeting space and the panels show data nobody has queried. Deliberate maintenance is what prevents the drift: a quarterly activation exercise using a scenario that has not been used before, a review of every panel against the last quarter's decisions, and a named owner for the room as an operating asset rather than as a facilities installation. Without that ownership, the centre is a capital project with a closing date rather than a capability.
Record the exercises and the panel reviews in the same log, so the history shows what the room was used for and what changed as a result. When the room is reviewed for budget, that log is the argument, and it is far more persuasive than a demonstration of the wall during a visit. The organisations that keep the log are the ones whose centres survive reorganisation; the ones that do not usually lose the room to a renovation and rediscover the need during the next incident, by which point the cost is a new project rather than a maintenance item.
When the centre is not the answer
Not every organisation needs a command centre, and the honest assessment sometimes concludes that a routine operations huddle with three dashboards on a wall in a meeting room covers the actual need. The distinguishing question is whether decisions during an incident require several disciplines in one room at the same time, or whether they can be made by phone with a shared view. Answering that question honestly before a capital request saves the organisation from a room that is impressive on the day it opens and empty six months later.
Proof
- ONC (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — public suite URL
- 67 public hostnames, 51 serving, one AWS account
- 104 clearinghouse enrolments across 53 jurisdictions
- USCDI v7 proposal — Patient Digital Identity Credential — listed at isp.healthit.gov
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564
- AWS Business Associate Addendum active since 18 August 2026
Where this work is delivered
Engagements run from Las Vegas and reach across the valley: clients in Las Vegas, NV; Las Vegas, Nevada; Henderson; Clark County, Nevada; and North Las Vegas, Nevada — plus remote delivery nationwide.
How an engagement runs
1. Trace one real case
Follow a single patient or claim end to end with a timestamp at every hop, before any document is written.
2. Written findings
A findings list naming the defect, the system, the owner and the date.
3. Monthly review
Review the list monthly and check whether the dates held.
Frequently asked
What is this service?
This page describes charles trinh — command centre design, las vegas nv — the scope, the failure modes it prevents and how the work is measured. It sits in the AV and IT Infrastructure category at trinh.io.
Where is the work delivered?
Engagements run from Las Vegas, Nevada across the valley — Las Vegas, Henderson, North Las Vegas, Spring Valley, Paradise, Winchester, Sunrise Manor, Enterprise, Summerlin, Clark County — and remotely anywhere in the United States. On-site work in the Las Vegas valley, remote delivery elsewhere.
What does it cost?
Standard rate $195 per hour, committed $165 per hour at twenty hours or more per week for three months or more; $1,600 standard day, $1,350 committed day. Scoped in writing before work starts, fixed fee where the deliverable is defined.
Who is Charles Trinh?
A technology architect in Las Vegas, Nevada, working in healthcare identity, consent and interoperability. Not a physician, not a medical practice, and not affiliated with any other Charles Trinh.
How does an engagement start?
With one trace of a real case and a written findings list naming the defect, the system, the owner and the date. The first call is twenty minutes and free: 702-559-3489.
Engagement
Scoped in writing before work starts; fixed fee where the deliverable is defined. First call is 20 minutes and free. 702-559-3489 · charles@trinh.io
Talk to Charles
- Phone: 702-559-3489
- Email: charles@trinh.io
- Based in Las Vegas, Nevada · working remotely across the United States
Record
Profile
Healthcare technology architect working where federal regulation becomes production infrastructure. Built and operates a FHIR R4 clinical platform — SMART App Launch authorization server, patient and provider portals, SQLite — on a hardened single-host AWS estate of 67 public hostnames. The platform returned a self-test PASS on the ONC (g)(10) Standardized API test suite in April 2026, 317 of 317 subtests, publicly verifiable. Designed a consent architecture in which a permissioned ledger records patient grant, refusal and revocation as immutable events while all clinical data stays off-chain and encrypted per patient — no PHI on the ledger by design. Filed a proposed USCDI v7 data element with ONC on verifiable patient identity. Translates the Federal Register, HHS/CMS guidance and HITRUST requirements into architecture, controls and audit evidence.
Selected engineering scale
- Self-managed estate of 67 public hostnames, 51 serving, on one AWS account.
- FHIR R4 API with a SMART App Launch authorization server; patient and provider portals; an AI service layer; Hyperledger Fabric peer, orderer and CA; IPFS; a 337-table SQLite clinical store.
- Two permissioned distributed ledgers in production, one operating a consent registry that records grant, refusal and revocation with no PHI on chain.
- X12 005010 pipelines across eight transaction sets.
- Designed, built, deployed and operated end to end by one person.
Credentials and standards work
- Inferno (g)(10) self-test PASS, 317 of 317 subtests, April 2026 — the ONC Standardized API test suite. Standards validated: US Core 6.1.0, USCDI v3, SMART App Launch 2.0.0, Bulk Data 2.0.0. Public suite URL.
- USCDI v7 public comment submission, April 2026 — proposed Patient Digital Identity Credential under the Provenance data class, listed publicly on the ONC Interoperability Standards Platform.
- SAM.gov UEI MVKQW9DKKGB8 · CAGE 20KM5 · NPI 1194645564. AWS Business Associate Addendum active 18 August 2026.
Technical environment
AWS us-east-1 (compute, storage, messaging, SMS, email, voice) · Linux and systemd hardening · nginx · Fabric and EVM ledgers · FHIR R4 · X12 005010 · HL7 · SQLite · self-hosted mail, drive, search and monitoring · Git-based change control and CI release gates.