> 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/selmo-as-a-process/selmo-digital-twin-process/introduction-from-ptf-to-the-digital-twin.md).

# Introduction: From PTF to the Digital Twin

The **Digital Twin (DT)** is the **virtual counterpart** of a real machine or plant.\
It is used to **behavior, control, communication and interaction** between system components to test and optimize even before physical implementation.

In the **Selmo context** the Digital Twin is the **logical continuation of the PTF process**:

* The **PTF** provides all structured and verified information about **process**, **technology** and **Function**.
* The **Digital Twin** uses this information to **simulate, emulate or verify the** – **even before real commissioning**.

This turns the DT into a tool for:

* **Soft-FAT** (Factory Acceptance Test in simulation),
* **early integration with MES / ERP / IT systems**, and
* **training, diagnosis and optimization** throughout the lifecycle.


---

# 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/selmo-as-a-process/selmo-digital-twin-process/introduction-from-ptf-to-the-digital-twin.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.