Continuum Intelligence

Truly intelligent facility management

Challenge

A consistent theme emerged from customer interviews, no matter the product or topic we were discussing: data scattered across disconnected systems made it nearly impossible to bring everything together and make confident decisions.

The natural solution would be a dashboard that surfaces the most important data in one place. But a dashboard can often fail to tell a coherent story. Just because you can see the most important data points doesn't mean that you can clearly understand how to act on them.

Approach

As I considered this problem, a connection point across our facility management products came into view: everything had a relationship with time. Events, work orders, planned maintenance, capital planning, and expenses could all be plotted on a timeline. After refining the concept and creating a prompt with Siemens GPT, I moved into Figma Make to build out the prototype.

The result was Continuum Intelligence that maps data from across products into swim lanes, draws connections between them, and surfaces opportunities to optimize, investigate cause and effect, and prevent conflicts before they happen.

What We Built

—

Light and Dark Mode
Optimization, Investigation, and Conflict pinpoints connecting across timelines
Timeline or Kanban view
Side panel with AI chat interface
Hover states with drilled-down details.

—

Swim lanes surfacing:

Events
Work orders: planned and preventative maintenance
Energy consumption
Capital planning
Costs and expenses

—

AI agents scan your data to identify optimization opportunities, issue to investigate and conflicts to resolve. Additionally, you can 'interrogate' the agents with follow-up questions.

The Power of AI

We pulled anonymized data from real clients across four products, ran it through our AI agents, and let them find the connections. The examples below show what they surfaced: usage conflicts, opportunities to coordinate work and eliminate redundancies, and possibilities to save time and money.

One of my favorite findings was just how proactive the agents were. Rather than flagging a direct scheduling conflict, one agent identified that two separate events, while not overlapping, were likely to pull the same stakeholders in different directions at a critical moment:

"The Capital Programs Community Meeting is scheduled to coincide with the start date of the BAS Controls Upgrade project at the District Office, creating a potential scheduling conflict that could divide stakeholder attention and resources at a critical project initiation phase."

That's not a calendar conflict. That's organizational awareness.