These four working models are operational digital twins of a hospital: how patients flow, how rooms get cleaned and turned over, how supplies reach the point of care, and how meals get made and delivered. Each runs on the same shell and reports in the same KPIs the client already manages to.
In production they run on AnyLogic Private Cloud against the project's own Revit geometry — turning a design into an operational forecast while it can still be changed.
Four operational twins
Arrivals are triaged by acuity, wait for a treatment bay, see a physician, and are discharged or admitted — the classic flow bottleneck.
Open demo →Discharge bed-turnovers and scheduled daily room cleans compete for one technician pool — and daily work is what slips under pressure.
Open demo →Bins in PAR rooms draw down with care; a room signals at half-par and a runner refills it — a point-of-care stockout if the second bin empties first.
Open demo →Patients order, the kitchen prepares, robots deliver to rooms, and cart staff collect finished trays — three meal rushes cascading through a full day.
Open demo →What ties them together
Every twin carries a travel-time control. It stands in for the design itself — adjacencies, floor distances, kitchen and dock placement, elevator access. Stretch it and KPIs degrade in all four; in Food Service one distance slows both delivery and pickup at once. This is how a design decision becomes a measurable, daily operational cost.
All four share the same controls, the same KPI dashboard, and the same scenario-compare panel. The engine underneath changes; the experience does not. Adding a fifth twin — pharmacy, sterile processing, imaging — is a configuration exercise, not a new application.