<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>Trinh — notes</title><link>https://trinh.io/notes/</link>
<description>Interoperability, identity and regulation — notes by Charles Trinh.</description>
<language>en-us</language>
<item>
<title>Why &quot;fail small&quot; should be the test for health data</title>
<link>https://trinh.io/notes/fail-small-health-data/</link>
<pubDate>Tue, 17 Nov 2026 00:00:00 -0800</pubDate>
<description>A breach should cost one patient, not a population. Per-patient encryption, sharded storage and provable consent change the blast radius — and that is the test health systems should be buying against.</description>
<guid isPermaLink="true">https://trinh.io/notes/fail-small-health-data/#article</guid>
</item>
<item>
<title>Writing an AV RFP a real integrator can price</title>
<link>https://trinh.io/notes/av-procurement-rfp/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Scope by outcome and room type, demand the engineered documents, and separate equipment, labour and service so bids can be compared at all.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-procurement-rfp/#article</guid>
</item>
<item>
<title>Why AV projects fail inside IT governance</title>
<link>https://trinh.io/notes/why-av-projects-fail-in-it-governance/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>AV arrives as a capital project and leaves as an operations burden. If it never enters the asset, patch and support model, it fails quietly for years.</description>
<guid isPermaLink="true">https://trinh.io/notes/why-av-projects-fail-in-it-governance/#article</guid>
</item>
<item>
<title>Venue AV: the scoreboard is the smallest system</title>
<link>https://trinh.io/notes/venue-av-scoreboard-smallest-system/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Stadium and speedway AV is a control room, a signal transport layer, a public-address system, a display network and a game-day operations team.</description>
<guid isPermaLink="true">https://trinh.io/notes/venue-av-scoreboard-smallest-system/#article</guid>
</item>
<item>
<title>Teams Rooms and Zoom Rooms turned the conference room into a managed endpoint</title>
<link>https://trinh.io/notes/teams-rooms-zoom-rooms-managed-endpoint/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>The platform chooses the hardware compatibility list, the update cadence and the management console. Procurement should follow the platform decision, not.</description>
<guid isPermaLink="true">https://trinh.io/notes/teams-rooms-zoom-rooms-managed-endpoint/#article</guid>
</item>
<item>
<title>Put AV on its own VLAN, then test what still works</title>
<link>https://trinh.io/notes/network-av-segmentation/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>AV over IP shares the wire with everything else. Segmentation is a design choice that protects both the clinic network and the room.</description>
<guid isPermaLink="true">https://trinh.io/notes/network-av-segmentation/#article</guid>
</item>
<item>
<title>One conference-room standard, or twenty rooms nobody can use</title>
<link>https://trinh.io/notes/conference-room-standard/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Every room built to its own spec becomes its own support ticket. A standard room kit is an operational decision disguised as a design one.</description>
<guid isPermaLink="true">https://trinh.io/notes/conference-room-standard/#article</guid>
</item>
<item>
<title>Digital signage fails at scale, not at install</title>
<link>https://trinh.io/notes/digital-signage-at-scale/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>One screen is a purchase. Fifty screens is a content pipeline, a player fleet, a network policy and a support model. Most signage programs fund only the first.</description>
<guid isPermaLink="true">https://trinh.io/notes/digital-signage-at-scale/#article</guid>
</item>
<item>
<title>Design-build is a procurement model, not a promise</title>
<link>https://trinh.io/notes/av-integration-design-build/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>What an enterprise buyer actually pays for when the integrator owns drawings, engineering, installation and commissioning — and where responsibility stops.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-integration-design-build/#article</guid>
</item>
<item>
<title>Converged cabling: one plant, two owners</title>
<link>https://trinh.io/notes/structured-cabling-network-convergence/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>When AV, security and IT share the same cable plant, the responsibility matrix decides who fixes it at 2 a.m. Most projects never write that page.</description>
<guid isPermaLink="true">https://trinh.io/notes/structured-cabling-network-convergence/#article</guid>
</item>
<item>
<title>Control system lock-in is a lifecycle decision</title>
<link>https://trinh.io/notes/control-system-lock-in/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>The control platform outlives the room. Choosing it decides who can service the room, what a future change costs, and how portable the design is.</description>
<guid isPermaLink="true">https://trinh.io/notes/control-system-lock-in/#article</guid>
</item>
<item>
<title>Casino and hospitality AV: rooms that cannot go dark</title>
<link>https://trinh.io/notes/casino-hospitality-av-no-dark-rooms/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>In a casino, a dark display is lost revenue and a broken experience at the same moment. Redundancy, spares and maintenance windows are revenue protection.</description>
<guid isPermaLink="true">https://trinh.io/notes/casino-hospitality-av-no-dark-rooms/#article</guid>
</item>
<item>
<title>Buying AV as a service changes who owns the failure</title>
<link>https://trinh.io/notes/av-as-a-service-lifecycle/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>AVaaS moves capital to operating cost and moves the upgrade decision to the contract. Read the exit terms before the first room opens.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-as-a-service-lifecycle/#article</guid>
</item>
<item>
<title>AV-as-a-Service is a financing structure, not a service</title>
<link>https://trinh.io/notes/av-as-a-service-is-financing/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>The label bundles equipment, installation and support into a subscription. What changes is the balance sheet and the exit — not the engineering.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-as-a-service-is-financing/#article</guid>
</item>
<item>
<title>AV over IP put the AV system on the network team&#x27;s budget</title>
<link>https://trinh.io/notes/av-over-ip-dante-network/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Once audio, video and control ride the LAN, the AV integrator and the network engineer are designing one system. The handoff is where projects fail.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-over-ip-dante-network/#article</guid>
</item>
<item>
<title>AV managed services: what day 2 actually costs</title>
<link>https://trinh.io/notes/av-managed-services-day-2/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Monitoring, dispatch, spares and firmware are the recurring bill. A support contract priced without a device inventory is a guess on both sides.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-managed-services-day-2/#article</guid>
</item>
<item>
<title>AV in a hospital is clinical infrastructure</title>
<link>https://trinh.io/notes/hospital-av-is-clinical-infrastructure/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Patient-room televisions, education systems, nurse-call integration and clinical communications share a network and a maintenance window. Treating them as.</description>
<guid isPermaLink="true">https://trinh.io/notes/hospital-av-is-clinical-infrastructure/#article</guid>
</item>
<item>
<title>AV design in a healthcare building is a clinical decision</title>
<link>https://trinh.io/notes/av-design-for-healthcare-facilities/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>A conference room is easy; a procedure room, a nurse station and a command centre are not. The difference is who is in the room when the system fails.</description>
<guid isPermaLink="true">https://trinh.io/notes/av-design-for-healthcare-facilities/#article</guid>
</item>
<item>
<title>A command centre is an AV system with a consequence</title>
<link>https://trinh.io/notes/command-centre-av/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>Video walls, consoles and control-room ergonomics are one system. When it fails, the failure is operational, not cosmetic.</description>
<guid isPermaLink="true">https://trinh.io/notes/command-centre-av/#article</guid>
</item>
<item>
<title>A command center is an operations design, not a video wall</title>
<link>https://trinh.io/notes/command-and-control-centers/</link>
<pubDate>Tue, 10 Nov 2026 00:00:00 -0800</pubDate>
<description>The wall is the least interesting part. Sightlines, console ergonomics, source switching, redundancy and the operator&#x27;s decision loop decide whether.</description>
<guid isPermaLink="true">https://trinh.io/notes/command-and-control-centers/#article</guid>
</item>
</channel></rss>
