# Process Model

{% hint style="info" %}
TestStand stores its sequences in so called sequence files. A sequence file usually has a so called process model attached. TestStand ships with 3 standard process models: sequential model (default), parallel model and batch model. In TestStand the normal sequence file is also called **client sequence file**, whereas the process model is called process model sequence file. For the LTT we call the client sequence file **testplan**. The testplan represents the project specific collection of sequences.
{% endhint %}

![Process Model Selected](https://1704635928-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FH5etzy4TvPRLxLRNfHlb%2Fuploads%2Fgit-blob-82fd14b5dfeb97098d7bbe3c6a5fb57f1ef27b55%2FTS_ProcModel_Selected.png?alt=media)

{% hint style="info" %}
Each LTT testplan needs to have the LTT process model assigned. It is located at `\50_LTT_SW\LTT TS\model\LTT Model.seq`. **Do not modify the LTT process model** as it gets overwritten by the next update.
{% endhint %}

The **LTT process model** specifies the **frame sequence** for each LTT testplan. It determines the order, in which each of those [standard sequences](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/predefinedsequences) are called and also provides some execution logic, initialization, error handling and so on. The LTT process model is the same for every LTT testplan, hence it is not project specific.

The LTT model is derived from the **standard TestStand parallel model**. It is therefore able to handle multiple DUT's in parallel. The LTT model also contains features of the standard TestStand batch model.

{% hint style="info" %}
When running multiple DUT's in parallel, you need to be aware that parallel execution has some limitations / drawbacks.
{% endhint %}

* You cannot access hardware simultaneously, which exists only once for all DUT's. Therefore you need some kind of [locking](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/synchronization) to make sure that the hardware is accessed serially.
* Since parallel DUT's run independently, some are faster than others. At some point in your testplan you might need to wait for all DUT's before you continue. You will need this kind of [synchronization](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/synchronization) especially if you want to change the voltage level of your power supply, if it supplies more than one DUT.

{% hint style="info" %}
Use the [SYNC sequence](https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/synchronization) to change your DUT's voltage level and/or wait for the other DUT's to continue.
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.irs.systems/ltt/documentation/ltt-gui-manual/teststand/processmodel.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.