Frisco’s indoor digital twins show where smart buildings really begin

Frisco, Texas, started indoor mapping for a single, high-stakes use case in 2008: getting first responders the right school floor plan fast. In 2026, that same indoor mapping and “digital twin” backbone is being used for broader building management, according to Facilities Dive’s reporting on the city’s Situational Awareness for Emergency Response (SAFER) program.

That evolution matters beyond one fast-growing suburb. It’s a clean case study of how enterprise building tech actually scales: a practical data foundation first, then integrations and workflows, then automation. The shiny part comes last, if it comes at all.

A digital twin that earns its keep is mostly identifiers and updates

Facilities Dive reported that Frisco’s SAFER program was conceived to give emergency responders and dispatch a common operating picture for schools, built on a geographic information system foundation. The program includes pre-plan documents and up-to-date contact information, and the floor plans carry operationally specific details such as room names and numbers, nurses’ offices, where hazardous chemicals are stored, and roof access, according to Facilities Dive.

This is where many “digital twin” pitches lose operators. The most expensive part is not modeling, it’s maintenance. If room numbering changes during a renovation, if a chemical storage location moves, or if a camera is replaced and not re-mapped, the twin quietly degrades until nobody trusts it.

For facility and IT teams, Frisco’s trajectory suggests a useful procurement inversion. Buy the update process before buying the visualization. That means defining who is responsible for source-of-truth floor plans, who can approve edits, and how changes flow from capital projects and work orders into the maps that operations and security depend on.

Most buildings still don’t have a BMS, so partners become the product

The retrofit picture is stark. In an Aug. 20 opinion piece for Facilities Dive, Susanne Seitz, CEO of Buildings Smart Infrastructure at Siemens, wrote that building management systems are installed in only about 10% to 15% of medium-sized buildings, and in fewer than 5% of smaller buildings.

Those percentages are a helpful benchmark for portfolio owners and service providers trying to sanity-check their own adoption curves. If an organization’s roadmap assumes “BMS everywhere” as a prerequisite for analytics, indoor positioning, or automated fault detection, the timeline is probably backwards for most of the footprint.

Seitz’s core operational point was that automated operations need to be phased in, and that no single organization can modernize the existing building stock alone. She framed partner ecosystems as the next competitive advantage in buildings, according to Facilities Dive.

Frisco’s SAFER story shows what “partner ecosystem” looks like in practice: IT, public safety stakeholders, facility data owners, and the vendors that hang cameras and maintain networks all contributing to a shared picture of the building. The technology is the enabler. The operating model is the deal.

GSOC thinking is moving into facilities: fuse feeds, don’t stack dashboards

As tools and teams merge, security executives are redefining what counts as “operations.” Writing in Security Magazine, John R. Christman said that Global Security Operations Centers (GSOCs) are evolving from basic alarm-monitoring rooms into intelligence-fusion hubs that pull together open-source intelligence, intelligence from social media, intelligence tied to travel risk, intelligence on cyber threats, monitoring of physical security technology, and crisis-management operations.

That fusion model maps neatly onto the facilities side of the house. Indoor maps and digital twins become operational when they fuse: camera locations, access points, room attributes, contacts, and (when available) building system telemetry. If each system keeps its own naming conventions and no one governs the crosswalk, teams end up with multiple screens and no shared truth.

For operators with highly distributed real estate, like school districts, healthcare systems, retail chains, or corporate campuses, the implication is that the “twin” should be evaluated like critical infrastructure. Ask about uptime, data refresh intervals, audit trails, and integration testing, not just features. That’s especially true if the same map is expected to support both facilities work and safety response.

What to put in the next RFP for mapping, twins and building ops platforms

• Define a minimum data set that must be maintained, room and door identifiers, contact lists, hazard locations, roof access, and camera/device geotags, and specify how often each attribute must be verified (monthly, quarterly, per project closeout). Frisco’s SAFER details in Facilities Dive are a good starter list.
• Require a change-control path from projects to maps: make the GC, architect, or low-voltage integrator deliver updated digital floor plans and device as-builts in a specified format as a condition of closeout, then name the team that approves and publishes updates.
• Write integration responsibilities down to the interface: which system is the system of record for rooms, which for devices, and what IDs are shared across GIS/indoor maps, video, and access control. Security Magazine’s GSOC fusion approach only works when feeds can be correlated reliably.
• If a BMS upgrade is out of scope, don’t let it stall the program: specify what the twin must do without BMS telemetry today, and what data hooks must be available later. Siemens’ BMS penetration figures in Facilities Dive suggest many portfolios will be in this phased state for years.