> For the complete documentation index, see [llms.txt](https://docs.gospace.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gospace.com/overview/trial-subscription-guides/data-requirements/best-case-data-requirements.md).

# Best case data requirements

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

## Overview

With a simulation there are 3 data sources we require: Directory, Occupancy (both historic, and weekly or daily), and floorplans. Historic, and floorplan requirements are no different to the minimum we require, however with better directory and current occupancy integrations we can do the below.

Our ideal state simulation puts you in the best standing to:

* Quickly scale to a live site
* Amalgamate all your occupancy data into one single platform
* Utilise improved forecasting, both of directory changes, and of daily occupancy trends

So how do we achieve this ideal state?

### Directory

For your directory, we want an integration that is automated (when your teams change, headcounts change, users change email and so forth) this is all automatically updated in gospace. The issue with our ideal minimum data requirements is it relies on directory data being uploaded to SFTP daily.

Therefore, for best case we'd recommend integrating one of the following:

* [Microsoft AD](/integrations/connecting-an-integration/microsoft-ad.md)
* [Snowflake](/integrations/connecting-an-integration/snowflake.md)

In the links it shows how to connect the integration, and what permissions we'd need.

### Occupancy

With your occupancy in the minimum data requirements this relies on you providing daily or weekly occupancy dumps via SFTP. This we can use in addition to other occupancy integrations, however can be very manual. To automate your occupancy we recommend integrating CISCO Meraki, alongside your badge data we previously integrated via SFTP.

Therefore, for best case we'd recommend integrating the following:

* [CISCO Meraki](/integrations/connecting-an-integration/cisco-meraki.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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/data-requirements/best-case-data-requirements.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.