> For the complete documentation index, see [llms.txt](https://docs.voltmasters.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.voltmasters.io/getting-started/adding-a-new-project.md).

# Adding a new project

Follow these steps to create a new project and link a controller to the Voltmasters EMS platform.

{% stepper %}
{% step %}

### Start a new project

On the home screen, click **Add new project**.
{% endstep %}

{% step %}

### Enter project information

Fill in the basic details of the installation site:

* **Project name**: enter a clear and unique name for the project, for example *Company HQ - Battery System*.
* **Street**: street name of the installation address.
* **City**: city where the system is installed.
* **Postal code**: postal or ZIP code of the location.
* **Country**: select the country from the dropdown list.
  {% endstep %}

{% step %}

### Configure grid capacity limits

These values define the technical limits of the grid connection and are critical for EMS operation.

* **Grid import capacity limit (kW)**: enter the maximum power that may be imported from the grid. This value is used for load limiting and peak shaving.
* **Grid export capacity limit (kW)**: enter the maximum power that may be exported to the grid. This is important for export limitation and PV curtailment.

{% hint style="info" %}
These limits should match the contractual or physical grid connection limits. Be sure to verify this in advance.
{% endhint %}
{% endstep %}

{% step %}

### Link the controller

* **Controller ID**: enter the unique Controller ID of the EMS controller installed on-site.
  * Make sure the controller is powered on and connected to the internet.
  * The Controller ID can be found on the device label.
    {% endstep %}
    {% endstepper %}

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

## Having the project validated

A new project is first **commissioned**: devices are added, the grid settings are entered and the control strategy is chosen. When that work is finished, you can have the configuration checked by the Voltmasters **project engineers** before the installation goes into service. Mark the project as **ready for validation**.

* The **EMS dashboard** shows a status bar with the validation state of the project, so everyone involved can see whether the project is still being commissioned, is waiting for validation, or has been validated.
* Voltmasters reviews the configuration: the meters and their roles, the grid limits, the strategy and the energy contract, and the communication with each device. Anything that needs correcting is reported back to you.
* After you correct the findings, request the validation again.

Before you request a validation, check that:

* every device has been added and is delivering **live data**;
* the correct **main meter** is selected and the grid connection type matches the installation;
* the **import and export limits** and their safety margins match the grid connection contract;
* the **strategy** and the **energy contract** match each other.

See [Adding and verifying devices](/getting-started/adding-and-verifying-devices.md) and [Project settings](/voltmasters-platform/10.-project-settings/10.5-project-settings.md) for the settings involved.


---

# 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.voltmasters.io/getting-started/adding-a-new-project.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.