> 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/pre-installation-requirements/completing-the-work-order-form.md).

# Completing the Work order form

This forms part of our discovery prior to installation and is our reference when connecting the signals and data to your Busroot account. There are some areas marked for completion due to the installation, these can be ignored at this stage. 

You do not need to complete every cell in the section named Signal Source. Please fill in the signals that you know you would like to collect data from for each machine. For example, Machine 1 signal source for running indication is an Andon light. There is more examples of types below:

### Discovery <a href="#discovery" id="discovery"></a>

Objectives of the discovery phase:

#### Identify the machines and processes to be monitored <a href="#identify-the-machines-and-processes-to-be-monitored" id="identify-the-machines-and-processes-to-be-monitored"></a>

* Photograph the machine in location
* Photograph controls including inside cabinets
  * Is there available space for a new device?
  * Is there a 24v DC supply available?
    * If not, what power options are available?
* Find and photograph any available schematics
* Identify signals, where possible, for:
  * Running indication
    * Andon Lights (Green)
    * Idle position light (negative indication)
  * Production Cycle Counts
    * Actuators or relays related to cycle
    * Optical sensors
  * Line Speed
    * Available via PLC as OPC-UA data.
    * Analogue Signal
      * e.g. 0-10v signal from motor inverter
  * Error indicators
    * Error lights
    * Andon Lights (red)
* Document information regarding electrical supply
  * Number of phases
  * Power rating
  * Photograph relevant connection and supplier
* Energy Monitoring
  * For each machine let us know how many phases the machine uses (single phase or 3 phase).
  * And what the maximum current draw is?

### Confirm available networking <a href="#confirm-available-networking" id="confirm-available-networking"></a>

* WiFi
  * Confirm which WiFi network is to be used.
  * Use mobile app to confirm networks signal strength at each machine
    * Android: <https://play.google.com/store/apps/details?id=abdelrahman.wifianalyzerpro&hl=en&gl=US&pli=1>
    * Window: Use WiFi connections manager.
* Ethernet
  * Which machines is wired Ethernet available at. (Less important if WiFi is available)


---

# 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/pre-installation-requirements/completing-the-work-order-form.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.