With ten hospital sites, divergent records, and major rebuilding on the horizon, Manchester University NHS Foundation Trust needed a reliable way to pin every decision to an exact place, time, and fact rather than to scattered files and siloed systems that slowed critical work and obscured accountability across the portfolio. The trust’s answer is a spatial digital twin designed to unify data about buildings, rooms, and assets and then layer risk, condition, and operations on top. By anchoring everything in geography—rooms, corridors, roofs, plant, points of entry—the program seeks to give planners, engineers, security, and project teams a single frame of reference. That choice matters. Space does not argue. Drawings may, spreadsheets often do, but a verified model of physical reality serves as a durable point of truth. The aim is pragmatic: simplify complex estates work, cut guesswork, and prepare for new construction under the New Hospital Program without fragmenting oversight.
Strategy and Architecture
Rationale and Scope
MFT framed the twin as an estate-wide platform rather than a project tool, reflecting the fact that the North Manchester General Hospital redevelopment would ultimately represent only about a fifth of total floor area. Building for the whole meant the new site could be absorbed seamlessly, avoiding a two-tier environment in which “smart” buildings operate apart from legacy stock. Space became the organizing principle, because risks, assets, and tasks all resolve to location. RAAC planks span bays. Asbestos sits in discrete rooms. Doors, detectors, risers, and clinical equipment live at precise coordinates that matter for compliance and access. This spatial spine reduces interpretation overhead for every discipline. It also scales. Whether a team is surveying a façade or planning an internal move, they navigate the same backbone and trust that data are current, versioned, and findable.
MFT’s scope decision also addressed a historic challenge: a merged estate carrying three different ways of drawing, naming, and maintaining records. A piecemeal twin would have reinforced boundaries between systems and teams; an estate twin forces harmonization. By agreeing that every task begins with “where,” the trust could make “what” and “how” consistent. That consistency, in turn, supports governance that travels from project sites to board-level reporting. A single change to a room’s status or a wall’s material updates risk registers, maintenance routes, and project assumptions in one place. For executives, this provides a defensible audit trail. For field staff, it saves time otherwise spent reconciling artifacts. The upshot is not only coherence today but a runway for sensors, analytics, and user-facing services that all speak the same spatial language.
Technology Stack
ArcGIS was selected as the twin’s integration hub and visual layer, giving the trust a mature geospatial core that could ingest and display both engineering-grade models and operational datasets. Revit and CAD deliver building geometry and room definitions; CAFM exports bring daily maintenance updates; condition and project datasets round out the picture. ArcGIS converts these inputs into interactive 2D and 3D experiences that work from the campus level down to individual rooms, with role-based views switching on relevant layers. A surveyor auditing RAAC sees plank extents, identifiers, and condition fields at the click level. A security officer sees entrances, camera coverage, and restricted areas. Behind the scenes, conventions for naming, versioning, and symbology keep models and maps consistent.
The platform’s flexibility also supports controlled evolution. As pilots expand, ArcGIS can incorporate submetered energy streams, microclimate and weather feeds, and transportation data that affect patient and staff movement. Crucially, the system is built with interoperability in mind: exports and APIs allow data to flow in and out without locking teams to any single authoring tool. This matters in capital projects, where contractors arrive with different BIM standards and deliverables. ArcGIS normalizes what it consumes, aligns it to the spatial backbone, and exposes the results through web maps, dashboards, or mobile forms tailored to the task. The result is not just a map or a model, but a role-aware environment that respects source-of-truth systems while presenting actionable, location-accurate information.
Data and Governance
Spatial-First Data Model
Early staff workshops surfaced predictable but costly pain points: lost drawings stored on personal drives, time wasted verifying which floor plan was current, and space records that did not reflect built reality. In response, MFT established a unified standard for capturing and maintaining space data that superseded practices inherited from the three legacy trusts. Every room, corridor, stair, and plant area now follows consistent identifiers, geometry rules, and attribution, so assets and risks can be related to a reliable base. By institutionalizing “space before everything,” the trust gave itself a reference model that resists entropy. When a wall moves, affected rooms and linked datasets move with it.
Governance followed the model. Change control enforces how updates are proposed, reviewed, and published, with responsibilities assigned to roles and not to ad hoc project teams. Version histories preserve lineage. Validation checks flag common errors—misaligned levels, duplicate rooms, or geometry gaps—before they propagate into safety or compliance records. Crucially, governance is framed as an enabler rather than a gate. Templates, naming guides, and spatial QA tools reduce friction for contributors, while dashboards show data fitness by site and by discipline. Over time, this approach turns the twin into a living reference that improves with use. Each inspection, move, or project leaves the estate smarter than it was the day before.
Integration and Interoperability
With the space model in place, MFT could bring heterogeneous data into a coherent whole. BIM files describe geometry and classification; CAFM records tell the story of maintenance cycles; condition surveys add defects, ratings, and photos; project controls contribute phasing and access constraints. ArcGIS aligns these threads by location. A compliance officer can open a room and see asbestos records, recent works, and any upcoming fit-out that may disturb materials. A planner can switch to a floor view that overlays evacuation routes, fire compartments, and live service requests to sequence works safely.
The roadmap extends outside the buildings. Submetered energy will pair with space use and building fabric condition to reveal where consumption deviates from expected patterns. Weather and microclimate will contextualize heating and cooling loads. Transport feeds and demographics will help anticipate arrival peaks and identify access challenges for patients with mobility needs. If approved and governed appropriately, selected EPR-derived movement patterns could surface as anonymized signals that inform wayfinding or clinic adjacencies without exposing personal data. The throughline is clear: integrate only what adds value, relate it to place, and present it through views that drive accountable action rather than dashboard fatigue.
Practical Use Cases
Risk and Operations
The trust’s RAAC response shows the twin’s utility under pressure. A dedicated tool inside ArcGIS lets survey teams click individual planks, capture condition, and attach photos in the exact location. Rather than uploading static spreadsheets after site visits, surveyors complete structured forms in situ, building an auditable, visual record that supports triage and remediation. Decision-makers can filter by severity, age, or location to prioritize works and minimize disruption to clinical services. Because planks live in the same spatial context as rooms, routes, and access control, planned interventions consider patient flows and adjacent risks from the outset.
Asbestos management follows a similar pattern. Locations are mapped down to rooms and zones, with documentation and imagery tied to features. Before a contractor steps onto a floor, the project team can verify materials, confirm isolation needs, and plan sequencing without a paper chase. Daily CAFM synchronization closes the loop. Service tickets, planned preventive maintenance, and asset histories appear in the same view, so a technician can find an air handling unit, understand its surroundings, and see asbestos notes before raising a ladder. Fewer cross-system lookups mean fewer site delays, clearer handovers, and better compliance evidence. The payoff is measured in time reclaimed and risks avoided rather than in abstract digital rhetoric.
Patient Experience and Performance
The same spatial foundation lends itself to user-facing services. MFT intends to deploy wayfinding that blends campus maps, entrances, clinics, and transit links so patients can plan journeys with confidence. Missed appointments often trace to navigation failures across complex sites. By aligning clinic locations with public transport timetables and on-site routing, the twin can help patients select the right entrance, anticipate walking times, and avoid wrong turns. For staff, updated routes around live construction zones or temporary closures improve safety and reduce lateness across shifts.
On the performance side, energy and condition data will feed capital planning with sharper signals. As submeter coverage grows, unusual consumption can be tied to space use, equipment schedules, or known fabric issues such as poor insulation or failing seals. ArcGIS can then highlight candidate packages for retrofit, balancing carbon, cost, and patient impact. Works can be phased geographically to reduce decanting and maintain clinical capacity. In parallel, M&E telemetry can surface early warnings—fans drawing too much current, valves cycling unusually—that inform maintenance before breakdowns occur. The common thread is specificity: problems appear where they are, with enough context to act quickly.
Adoption and Impact
Change Management and Upskilling
Technology alone does not move the needle, so MFT treated adoption as a program in its own right. A central digital team seeded the platform, set data pipelines, and authored initial role-based apps, but the long-term model shifts capability to the edges. Engineers, surveyors, planners, and security staff are being trained to self-serve—querying rooms, updating inspections, and generating reports without specialist mediation. Short, task-focused training sessions beat marathon workshops. Pilot groups prove value in one workflow, then expand to adjacent tasks. This cadence builds confidence and keeps momentum visible.
Governance supports culture change rather than stalling it. Clear “how-tos” and embedded validation reduce the fear of “breaking the model.” Leaders sponsor usage by asking for twin-based views in reviews and reports, normalizing the platform as the default rather than an optional extra. Feedback loops matter. When users suggest a layer tweak or a new filter and see it arrive in the next sprint, the system earns trust. Over time, the center shifts from “doers” to “enablers,” curating standards and quality while disciplines own day-to-day data. The result is a living twin that keeps pace with operations because it is used where the work happens.
Early Gains and National Alignment
The platform went live in October last year, and the first returns were concrete. Security and asbestos teams reported time savings equivalent to about two full-time roles, thanks to faster lookups, clearer routing, and fewer site surprises. Reporting cycles tightened as location-specific data replaced stitched-together narratives. With adoption broadening, cumulative savings of up to five FTEs were projected, not as headcount cuts but as capacity redeployed to higher-value work. The approach also aligned with the New Hospital Program’s intelligent hospital agenda, positioning MFT to exchange playbooks on AI-assisted analytics, smart-building controls, and gap analyses that benchmark readiness across trusts.
Actionable takeaways were clear and practical. Standardize space data first; this had anchored every other integration. Build role-based apps that answer specific questions; this had boosted usage more than generic dashboards. Schedule quarterly data-quality sprints; these had kept drift in check. Tie pilots to urgent problems—RAAC, asbestos, access—so benefits were defensible. Finally, plan governance for patient-facing extensions from day one; this had de-risked future wayfinding and any EPR-adjacent signals. In short, success depended on treating the twin as an operating system for the estate, not a one-off project, and measurable impact followed when spatial truth met everyday work.
