Breaking Spatial Silos

What Employee Kiosks and Cleaning Workflows have in common

This article describes how spatial silos can be broken by introducing a Spatial System of Record (SoR) as the foundation for unifying all workflows and processes tied to buildings. It draws on recent Archilogic posts and releases that describe various aspects of the platform: Floor Plan SDK, Extensions SDK, GraphQL API, MCP Server, the Editor, use of Custom Attributes, and more.

Building Spatial Apps and Experiences

As a Spatial SoR we need to make it easy for third parties - customers and Integration Partners - to build applications based on floor plans and spatial building data. Here’s an example of an employee kiosk app that leverages the Floor Plan SDK, the new Wayfinding method (beta), as well as Custom Attributes (Room Status, Desk Occupancy, etc.):

A sample Kiosk App using the Floor Plan SDK and Wayfinding method

‍

Please note the following:

• Archilogic is not in the business of building these experiences - we give our Integration Partners (for example Kadence) and Customers the tools to build what they want. They are much better at it than us - we are focused on providing the Spatial SoR.
• 3rd party data, for example desk occupancy, can be pushed into Archilogic in order to unlock spatial workflows. For example, the Wayfinding method would like to "know" whether a meeting room is currently booked. Archilogic is agnostic as to where that data comes from.

In this example, desk and meeting room occupancy is data that’s collected anywhere. That data can be used to power derivative workflows. For example, you’d want the cleaning teams to know where to go and how to most efficiently get the job done.

Custom Attributes and Editor Extensions

Usage data is pushed into Archilogic as a Custom Attribute via API (manual edit in the example below). Custom Attributes are fully customizable by our customers - this is important as decision-making processes vary. Importantly, Custom Attributes are part of the spatial graph. That means any spatial logic can take those values into account. In the example, the “Cleaning Map” Extension in the Archilogic Editor checks for occupancy and then computes the shortest path that covers all the right spots.

Sample Cleaning Extension in the Archilogic Editor

‍

Please note the following:

• Extensions are custom pieces of spatial logic that run on any floor plan (because data is standardized on Archilogic). They can be public or private - i.e. our customers and partners can create their own. For example, someone selling sensors or furniture could create an extension that automatically places the right types and numbers of devices in any plan based on their rulesets. They could keep the extension private or make it public as part of their sales funnel.
• Extensions can run in the Archilogic Editor or headlessly
• Extensions are the way to truly scale spatial intelligence across the entire asset class

Archilogic MCP + Claude

Let's say we want to leverage usage data to drive cleaning processes. The Archilogic MCP Server allows AI assistants and agents to access Archilogic resources through a set of standard tools like listing floors or creating a PDF plan. Any Worker Extension is also exposed as a tool the agent can use.

In this example the Cleaning Map extension is called from Claude to compute the most efficient cleaning path and use that info to create a PDF based on the latest data. Of course, that can be part of a more complex agentic workflow of which Archilogic’s contribution is but one part.

Archilogic MCP in Claude

‍

Breaking Silos

Given that real estate is the world’s largest asset class and an integral part of any enterprise’s resources, the spatial data that describes it needs to be part of the enterprise data fabric. If it is not, AI cannot start optimizing the physical environment. Archilogic’s Spatial SoR breaks the siloed approach to floor plans and makes buildings queryable and scriptable. It’s the foundation for agentically supported optimization of an entire asset class.

‍