# Understanding the outputs

This guide is focused strictly on what a simulation is, the value, and how to begin with gospace.

## Why simulate a digital twin of your building?

Running a simulation can allow you to assess the following:

* How can I improve my static neighborhood assignments to better utilise space
* Assess whether a fully autonomous AI can replace the tedious parts of your occupancy managers workload, freeing them up to make more strategic decisions
* Assess the Co2 or operational savings of my business when Aidra is automatically consolidating empty space 
* Review the co-attendance of my teams within my organisation
* Test different scenarios and see how the allocated neighborhoods would have changed for that day

### So how does it work?

<figure><img src="/files/Pjb9nbIuh336yFqwAkv8" alt=""><figcaption></figcaption></figure>

Once you have registered at [www.console.gospace.app](http://www.console.gospace.app)  you first need to create a location and upload your floorplans. From here we need to setup 2 things, your directory and occupancy integrations.

* For directory please see:

{% content-ref url="/pages/lG9Yu9yv5tiXxXBWOAy1" %}
[Map your directory](/integrations/mapping-your-data/map-your-directory.md)
{% endcontent-ref %}

* For occupancy please see:

{% content-ref url="/pages/hl8psPtH5SNrvtNIA2Nb" %}
[How to map your occupancy data](/integrations/mapping-your-data/how-to-map-your-occupancy-data.md)
{% endcontent-ref %}

Once both these integrations are setup Aidra will begin to learn from your buildings attendance and begin to intelligently allocate! 🥳 We recommended waiting 2-3 weeks before reviewing your digital twin, this gives Aidra opportunity to learn attendance patterns and forecast more accurately.

## Once my digital twin is setup in gospace, how do I assess the performance vs my live building?

At present we have the following metrics to monitor the performance of your simulated building, however in Q1 2025 we will be releasing further metrics detailed below.

There is no industry standard for defining success in an office building, however these are the high-level metrics we'd recommend monitoring for best analysis:

* <mark style="color:blue;">Density (liveliness)</mark> - this is a decimal value to show the density of the building day to day - the assumption is that with Aidra forecasting people coming into the office users with people they collaborate with that they will then be more inclined to go into the office, and consequently will begin to come in more - driving density higher.&#x20;
* <mark style="color:blue;">Co2 savings</mark> *<mark style="color:orange;">**(coming soon)**</mark>* - gospace can optimise the space in your building dramatically by automatically consolidating empty space, consequently meaning part or full floors can be shut down and therefore incurring a Co2 saving
* <mark style="color:blue;">Co-attendance</mark> - Co attendance is simply a way of monitoring that colloborators are coming into the office on the same days of the week so they can collaborate in person together. Utilising your occupancy integration gospace can continuously analyse co-attendance between individuals in a team and recommend how they should amend what days they go in to attend on the same days as other people from their team.
* <mark style="color:blue;">Connectivity score</mark> *<mark style="color:orange;">**(coming soon)**</mark>* - Connections are what make gospace truly unique, Aidra utilises connections to ensure entities are allocated near or far from eachother. Ie you could connect Product to Engineering, then these teams will be allocated space as close to eachother as possible. Connectivity score gives you an aggregated percentage of how many of those connections were achieved for a day or not.&#x20;

#### 1. Review the allocations themselves

<figure><img src="/files/viUqYl6hGohBLamwbFgJ" alt=""><figcaption></figcaption></figure>

Most occupancy managed apply static team neighborhoods based on sharing ratios, which often mean teams don't have enough space, or far too much due to ever changing requirements like new starters, meeting days or more. gospace solves this by allocating a dynamic team zone based on how many people are forecasted to be in that day or booked in, meaning the team always has the pefect amount of space.&#x20;

One success metric is to review how Aidra is dynamically allocating space to teams vs how your organisation is currently allocating team space.

> <mark style="color:red;">Main output: Assess Aidra's dynamic team nighborhood allocations against your current assignments</mark>

#### 2. Review Aidra allocation metrics

<figure><img src="/files/vz3FeC867aAsyrr5pxN7" alt=""><figcaption></figcaption></figure>

Inside Allocations you'll see a tab named metrics, here you can review how Aidra performed in the allocations for the day.

You have three levels to these metrics, the team allocation performance, the floor performance, and the overall building performance for the day.

In the screenshot above you can see that the "Accounting" team have a headcount of 17, they were allocated 9 desks, their attendance for the day was 9 and therefore the difference is 0 as Aidra correctly allocated the amount of people that actually attended that day. They also have movement as "adjusted", this means that the team was moved from their previous days allocation, but they remain on the same floor. If this shows as "Moved", then they were moved floor, and if this shows as "No change" they kept the same space as the previous day they were allocated.

> <mark style="color:red;">Main output: See how your buildings allocations performed day by day from how gospace predicted how much space was used against how much was actually used per team. Similarly see if the density has increased day by day, or whether Aidra has moved teams.</mark>

#### 3. Review Allocation dashboard

<figure><img src="/files/xodyOFh6nu80Gw3mrOK5" alt=""><figcaption></figcaption></figure>

This dashboard lets you quickly analyse what space Aidra forecasted for different days of the week, and what the actual attendance was for the whole building on that day.&#x20;

> <mark style="color:red;">Main output: Quickly see overall forecasted attendance for a building against the actual attendance for that day, and visually see attendance patterns week by week</mark>

#### 4. Review co-attendance dashboard

<figure><img src="/files/xGyulOFRulykeyAAYcoN" alt=""><figcaption></figcaption></figure>

The co attendance dashboard will show you whether using are attending on the same day as other people from their team, and recommend what days to change their in-person schedule for better optimising coming into the office the same day as their team.

* Current schedule shows on a week the user does come in, what days are they in
* Recommended schedule shows the days Aidra recommends to optimise the teams co attendance
* Overlap shows the percentage that a person comes in with their team on a week they do go into the office
* Engagement shows the percentage that a person comes in with their team over a whole month period regardless of frequency
* Frequenct shows over a month period the average frequency per week they attend the office

> <mark style="color:red;">Main output: Analyse how your teams can optimise their schedule to come in on days where other people from their team are in</mark>

## <mark style="color:green;">Coming soon!</mark> 🔜

* Dedicated simulation dashboard, see your month by month improvement for:
  * Co2 savings
  * Operational savings
  * Density
  * Co-location score
  * Co-attendance score
* Dedicated simulation UI to quickly setup & run simulations&#x20;

<div align="left"><figure><img src="/files/WyTnC2UQ0KGKsabJWst2" alt="" width="563"><figcaption></figcaption></figure></div>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.gospace.com/overview/trial-subscription-guides/understanding-the-outputs.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.