> For the complete documentation index, see [llms.txt](https://doc.simax.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.simax.fr/documentation-simax-anglais/functional/production/machine-revision-and-maintenance/planning.md).
# Planning
It is necessary to define **a planning margin duration** **in advance** of maintenance so that they can be planned and integrated into **planning** schedules.
To do this, enter the duration in Plan ahead by, accessible via:
**Settings > Plug-ins and options, \[\[Production]]**.
In our case, maintenance must be scheduled **200 days in advance**, for example.
When using this feature for the first time, you can **manually start the planning process** from the menu:
**Production > Machines/CMMS > Machine maintenance planning.**
This action will generate **maintenance operations** in the **planning** for all maintenance tasks whose next maintenance date is **earlier than the date entered in the Until** setting.
Once processing is complete, you will be able to view the time **slots blocked by maintenance operations** in **Production > Production Planning.**
In **Production > Manufacturing Orders**, **maintenance manufacturing orders** associated with manufacturing operations are displayed **in green**.
{% hint style="info" %}
Planning is also done **on a daily basis**. **Nighttime automation** allows maintenance tasks to be automatically scheduled.
{% endhint %}
---
# 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://doc.simax.fr/documentation-simax-anglais/functional/production/machine-revision-and-maintenance/planning.md?ask=&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.
