> For the complete documentation index, see [llms.txt](https://infosys.selmotech.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://infosys.selmotech.com/selmo-solution/selmo-solution-en/engineering-through-the-ages.md).

# Engineering through the Ages

For centuries, humans have sought ways to describe technology **clearly and understandably** to describe.\
Because only with a **language** can ideas, designs and functions be shared worldwide.

* In mechanics it is the **technical drawing**, that makes dimensions, shapes and tolerances unambiguous.
* In electrical engineering it is the **circuit diagram**, that describes electrical connections and functions.
* In manufacturing it is the **G-code**, that standardizes the control of movements and machining.

But in the **logic of machines** there has been a gap since 1968: with the invention of the PLC the clarity of circuit-diagram logic was lost.

This document traces the **history of technical languages** shows the transitions and clarifies how **Selmo** closes this gap again.


---

# 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://infosys.selmotech.com/selmo-solution/selmo-solution-en/engineering-through-the-ages.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.