Cleveland Clinic Avon — Digital Twin PoC | 30-Day Emergency Department

Day 1: May 25, 2026 · Day 30: Jun 23, 2026

Project Capabilities 30-Day PoC

What this Proof of Concept delivers, and what natural follow-on phases would add. Phase 2 / Future columns reflect SOW §5 (explicitly out of scope for this engagement).

Capability 30-Day PoC Phase 2 candidate Future SOW reference
Simulation core
ED patient flow Discrete Event Simulation
Arrival → security → check-in → triage → treatment → disposition
 ✓§2.1
Walk-in + EMS arrival modeling
Separate ESI distributions per entry mode
 ✓§2.1
ESI-based triage routing & admission probability ✓§2.1
Security screening queue + KPI ✓§2.1
Configurable parameter framework
Durations, arrival rates, capacities — no code changes
 ✓§2.3
3D visualization
Avon first-floor 3D environment
Built from CC Revit/CAD, zone-labeled, expansion footprint indicated
 ✓§2.2
Color-coded patient agents (by ESI) ✓§2.2
Three run modes: Offline / Real-time / Accelerated ✓§2.2
Floors above first floor / other buildings ✓§5
Controls & analytics
Live scenario control panel
Adjust arrivals, ESI mix, durations at runtime
 ✓§2.3
KPI dashboard: wait time, utilization, throughput, LWBS ✓§2.1
Baseline vs. modified scenario comparison ✓§4
Staff hours per task KPI ✓§2.1
Scenario save/load with file selection ✓—
Extensions (out of scope for this PoC)
Back-of-house supply chain / delivery flow ✓§5
Detailed staff scheduling & workforce optimization ✓§5
Downstream clinical treatment processes ✓§5
Behavioral health / infectious-disease pathways ✓§5
AI / ML predictive modeling ✓§5
Live integration with EHR / RTLS ✓§5
Production hosting + multi-user concurrent sessions ✓§5, §7
Interoperability with IoT ✓§5

System Architecture

How the Custom Product delivered under this SOW is structured. The Discrete Event Simulation core is implemented independently of the 3D visualization layer, joined through a Simulation Bridge — this separation lets the sim logic be validated in isolation and avoids the visual-logic coupling that destabilizes simulation builds.

CC INPUTS PDF diagram Avon first floor as-built Operational data ESI mix, durations, capacities * assumed where not provided Staffing models Coverage by shift, role mix * assumed where not provided Triage protocol ESI rules + admission probs * assumed where not provided ULTISIM PLATFORM 3D Visualization Layer Scenario Panel SimConfigUI · sliders KPI Dashboard MetricsDashboard + charts 3D Avon Scene Patients + staff + stations Time Controls · NavMesh pathfinding · TopDown camera Pause / play / Offline / Real-time / Accelerated Simulation Bridge SimulationBridge · VisualSyncSystem · tick driver Discrete-Event Simulation Core Patient + Staff agents PatientData · StaffData · AgentTask Stations + queue logic Triage · CheckIn · TreatmentBed · FastTrack ERConfig (parameters) · ERMetrics (KPI capture) · SeededRng · tick scheduler DELIVERABLES Live demo 2 baseline + 2 what-if KPI metrics • Wait times (avg + p95) • Bed / triage utilization • Throughput, LWBS (left w/o seen) • Staff hours per task Scenario comparison Baseline vs. modified Final report Methodology, findings, next steps DES core is independent of the 3D visualization layer — can be validated in isolation before integration (SOW §4)
CC inputs 3D Visualization Simulation Bridge DES Core Deliverables

SOW Deliverables

D1–D7 per Statement of Work §3. Click a card to open the work item in Azure DevOps.

Week 1 — Foundation Week 2 — Simulation Engine Week 3 — 3D Environment Week 4 — Delivery Done Active
Task
Title Type Owner Sprint State Link