> 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/onboarding/getting-started.md).

# Getting Started

## What is the process to get setup 

Our aim is to get you setup as efficiently as possible. Below is a guide to take you through the onboarding process for Busroot. 

**Discovery**

[Here is a link](https://docs.google.com/spreadsheets/d/1wfQ3NxDRbffC_IMJkT-pnzBC0__nH_bHE3SmhnPAuvI/edit?usp=sharing) to a document that needs to be completed by the person that will be installing the hardware.

The information required at this stage is: 

* Internet status (please see additional notes at bottom of this email)
* For each machine (serial no, machine name and power supply)
* Signal source(s) for each machine 
* Will our hardware require Whitelisting (IT team)? 

Once this information has been sent to us in the work order form format,  we will confirm compatibility and prepare the hardware for installation. Please confirm the address and who we should address the package to. 

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). 

Do understand how to check the WiFi signal near your machines please check [this link](https://output-industries.gitbook.io/busroot/integration/onboarding/implementation) for more information.<br>

**Installation**

If your in-house maintenance/engineering team will complete the installation please let us know the installation date. Alternatively we will liaise with you for a suitable date for one of our partners to visit.&#x20;

The remaining fields of the work order form should be completed during the installation and shared with your Busroot contact when completed.&#x20;

**Account setup and calibration**&#x20;

Once the installation is complete. We will setup your Busroot platform and schedule a call to calibrate the data with you (usually in 3-5days). This is to verify the data we receive from the machines is what is actually happening on your factory shop-floor.&#x20;

We will setup weekly calls for the first 4 weeks to monitor the data. As well as show you how to navigate the Busroot platform. &#x20;

**Additional information**

\- Please double check the WiFi password as autocorrect (or similar) can alter characters (capitalisation for example).&#x20;

\- The Firewall information should be completed by the IT team&#x20;

\- In the case of device white-listing, we can supply the MAC addresses if required for you IT team&#x20;

\- If you have requested or required to add the WiFi information yourselves we can share the instruction with you to do this.  [See here](https://output-industries.gitbook.io/busroot/integration/hardware/arduino-opta/configuration)

**How long will the installation take?**&#x20;

\- 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.

<br>


---

# 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/onboarding/getting-started.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.