Archilogic + Integrations: Closing the Feedback Loop

Introduction

Archilogic is a system of record for floor plans and spatial building data. We focus on the operational phase of commercial real estate, and our customers are users of space.

As a system of record, Archilogic has three important components:

1. Onboarding and Standardization of floor plans and spatial building data
2. Editing floor plans and spatial building data
3. Connecting floor plans and spatial building data

This article focuses on 3. - how integrations should work in order to generate maximum end-user value.

Challenge

Operationalizing floor plans and spatial building data is a huge challenge for enterprises. We wrote in BIM vs. Archilogic about the inadequacy of BIM models to drive the operational context of buildings. Operationalizing data means you have the data you need in every system. Those needs could be visual - say in digital signage - or data-driven - say in supporting agentic AI to put together a maintenance route for devices that need attention.

Our customers use a plethora of systems that help them better use their real estate - IWMS is a good example. In the context of integrations it is Archilogic’s first job to ensure all of these systems can be fed from a single source of spatial truth - a system of record. And it is Archilogic’s second job to ensure that the key pieces of data these systems provide find their way back into the Archilogic Editor. Together, these jobs done well establish a feedback loop that ensures the building is its best possible version to serve user needs.

Let’s dive into both.

Our First Job - Connect to Proptech SaaS

IWMS are a great example for how difficult it can be to ensure that up to date floor plans and spatial data find their way into those platforms. Many of these systems use their own flavors of “standard” formats to put proprietary content into a spatial context. Getting these floor plan formats into those systems using legacy floor plan tools can be very labor intensive as the source files in AEC software are drawings and not data. As a result, every time a ground truth change happens, a plethora of processes is triggered to ensure all connected systems receive the latest information. On top of that, buildings have become much more dynamic, meaning that the frequency of running these complex manual updates has increased. There has to be a better way.

We mentioned in previous posts and Articles that Archilogic is running on Space Graph, a graph-based data model for floor plans and spatial building data. We produce that graph for every single floor plan that’s onboarded to Archilogic. And as we say in Step 1 above: that data is fully standardized. It’s no longer a drawing (even though it still looks like a floor plan) - it is data. Why is that important? It’s important because we can create translators / exporters that turn Space Graph into any conceivable format the proptech SaaS world already uses. Once an exporter is configured, it will work on any floor plan on Archilogic. If and when edits are made, a new version is published to whomever is integrated. Our customers benefit because it’s easy to make edits and they know that the new version will find its way to the other systems. The integrator benefits because there is no more back and forth via email and phone calls to figure out how to get the latest versions aligned.

Our Second Job - Provide Data in an Editorial Context

I outlined above that our second important function is to make editing data easy. Sounds abstract, so what do we mean? It means that the person responsible for planning changes has all the relevant data at their fingertips - in a spatial context. For example, a sensor company like Butlr is able to provide granular occupancy data for meeting rooms. As a business, you might decide that the 6-month average meeting room occupancy is an important metric in planning your next iteration. Which meeting rooms to merge, which to upgrade, etc. etc. That information should be available in the place where you make edits, not in an Excel file. Archilogic receives that information via Custom Attributes which are user defined and associated with any floor, space, asset or product. Those data points can be populated via API or manually.

What’s more, we believe that eventually it will be possible to automate office design iteration to a great extent as the building telemetry, usage, and spatial constraints are one fabric of interconnected data. Agentic AIs will start making recommendations that leverage all of these data verticals in a unified way.

A Closed Feedback Loop

When these two jobs are combined and done well we achieve a feedback loop between users of space and proptech SaaS solutions. It ensures that the building can achieve its maximum potential - on any metric - based on tangible information, supported by AI. Getting there is only possible with a System of Record that provides a fabric between property users and proptech SaaS. If you’re a SaaS company leveraging floor plans please get in touch - we’d love to work on a connector. If you’re a user of space and wish you had a system of record to connect to your suite of proptech SaaS products please let us know - we’d be happy to discuss how to get it done.

‍

Contact us to learn more!