> For the complete documentation index, see [llms.txt](https://water-strategy.gitbook.io/waterstrategy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://water-strategy.gitbook.io/waterstrategy/francais/tutoriels/creating-a-reservoir-system/control-curves-and-demand-savings.md).

# Courbes de contrôle et économies de demande

Le didacticiel sur la modélisation des systèmes de réservoirs de captage explique comment mettre en œuvre des réductions de la demande en fonction des niveaux de stockage des réservoirs à l'aide de courbes de contrôle. En réduisant progressivement la demande lorsque certains seuils sont atteints, elle permet de gérer les ressources en eau en cas de pénurie. Il couvre des étapes telles que la définition de courbes de contrôle, l'association de facteurs de demande, le calcul de la demande et l'exécution de simulations pour visualiser les effets sur le stockage des réservoirs et la demande dans diverses conditions.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://water-strategy.gitbook.io/waterstrategy/francais/tutoriels/creating-a-reservoir-system/control-curves-and-demand-savings.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.