> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/archive/customer-guide-to-busroot/requirements-before-and-during-installation/installation.md).

# Installation

* If you have an in-house maintenance or engineering team we can share information to support the installation.
* If you do not have an in-house to complete the installation we can put you in-touch with one of our installation partners to carry-out the installation.
* We find 5 machines can be installed in one day with minimal impact to production. Machine downtime depends on entering the cabinets we need to install. Some can be entered without needing to power down the machine. If the machine does need to be powered down then a rough estimate is between 5-15 minutes.

We have prepared a guide to help you complete the machine information requested [in this link](https://output-industries.gitbook.io/busroot/customer-onboarding).

Should you require further specifications regarding the hardware, they can be found [in this link](https://output-industries.gitbook.io/busroot/hardware).


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.output.industries/archive/customer-guide-to-busroot/requirements-before-and-during-installation/installation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
