> For the complete documentation index, see [llms.txt](https://docs.cfl-bim.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cfl-bim.com/cfl-livrables/1.representations-generales/1.1-principes-generaux-de-production-des-plans.md).

# 1.1 Principes généraux de production des plans

Les dernières versions de ces normes sont à utiliser pour les représentations graphiques:

* DIN ISO 128: Technische Zeichnungen
* DIN 406: Maßeintragungen
* DIN 476: Papierendformate
* DIN 823: Papierformate
* DIN 6776: Beschriftung
* DIN 824: Technische Zeichnungen
* DIN 1301-1: Einheiten
* DIN 1356 Teil 1-10: Bauzeichnungen
* DIN EN ISO 3098 Teil 5: Technische Produktdokumentation -Schriften
* DIN EN ISO 4157: Bezeichnungssysteme
* DIN ISO 5455: Technische Zeichnungen
* DIN EN ISO 5457: Technische Produktdokumentation
* DIN ISO 7518: Zeichnungen im Bauwesen
* ISO 2594: Building drawings
* DIN EN 13501: Klassifizierung von Bauprodukten und Bauarten zu ihrem Brandverhalten
* Instruction de service N°207 GI: Lever topographique et leur représentation graphique


---

# 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://docs.cfl-bim.com/cfl-livrables/1.representations-generales/1.1-principes-generaux-de-production-des-plans.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.