> For the complete documentation index, see [llms.txt](https://help.besmart.software/be.smart-site-management/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/be.smart-site-management/en-site-productivity/asset-management/machines/creating-a-new-machine.md).

# Creating a new machine

Create a new machine by clicking **Create New** on right hand side of the page.&#x20;

<figure><img src="/files/4gAtbej8kFXYvUf9W88u" alt=""><figcaption><p>Create New -button highlighted</p></figcaption></figure>

When creating a new machine, there are two separate tabs to be filled; Basic settings and Parameters.&#x20;

## Basic settings

Basic settings tab contains total of eight (8) fields of information, from which five (5) are mandatory.&#x20;

* Name\*
  * Name of the machine
* Serial number\*
  * Can be anything, but usually consists of the machine model and identifier after it
  * If Hiboo is used, please use the same serial number as in Hiboo.
* Type\*
  * Type of machine, predefined list containing following options:
    * Articulated truck
    * Compactor
    * Dozer
    * Dumper
    * Excavator
    * Motor grader
    * Scraper
    * Soil stabilizer
    * Wheel loader
* Make\*
  * Machine manufacturer, predefined list containing following options
    * Caterpillar
    * Hitachi
    * Liebherr
    * Volvo
    * V5
* Model\*
  * More detailed model of the machine&#x20;
* Site
  * Lists all the sites within the tenant
* Tracker
  * Lists all the trackers, which don't have a machine associated to it.&#x20;
* Description
  * Free text field

<figure><img src="/files/znLvwwMipawFv5435X7t" alt=""><figcaption><p>Mandatory basic settings information filled in.</p></figcaption></figure>

After all the mandatory information is filled in, user may continue to fill in other fields in Basic settings tab or continue to Parameters tab. Saving the machine and added information is done by clicking **Submit.**

## Parameters

Parameters tab becomes editable after the **Type** field in Basic settings is filled. The reason is that for each machine there are different parameters depending on the machine type. Here is the breakdown of parameters for each type:

### Articulated truck, dumper and scraper

* Cost per hour
* Theoretical consumption
* Kg of CO2 per liter
* Target dump time
* Tonne
* Volume
* Valid from
* Valid to

### Compactor, dozer, motor grader, soil stabilizer and wheel loader

* Cost per hour
* Theoretical consumption
* Kg of CO2 per litre
* Valid from
* Valid to

### Excavator

* Cost per hour
* Theoretical consumption
* Kg of CO2 per litre
* Tonne
* Volume
* Target time per bucket
* Valid from
* Valid to

<figure><img src="/files/Li0ZFS5haHmLsM60Ymlc" alt=""><figcaption><p>Excavator parameters</p></figcaption></figure>

When all the information is filled and the machine is ready, save the machine and its settings by clicking **Submit.**


---

# 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://help.besmart.software/be.smart-site-management/en-site-productivity/asset-management/machines/creating-a-new-machine.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.
