Within the development environment OTX sequences are generated and processed. Within the execution environment they are running. For the execution of sequences code is generated and translated on-the-fly. If you exclude the time for on-screen input and output the run-time requirements of the runtime environment is negligible. The running time is largely determined by other layers, such as the diagnostic runtime system.

The figure below shows the basic structure of the OTX runtime environment.

Structure of the OTX-execution environment

There are two types of data provision for the OTX-processes:

1. Im OTX-For­mat
2. In the binary format

When deploying the OTX sequence data in this format are translated directly to the store just in time. If the data in binary format, provided they can be used directly without translation. The development environment can be created and encoded binary data to subsequent disassembly. With the binary format there is a secure, slim and fast transfer format, such as for rolling out the procedures in the workshop area.

Codegenerierung

For the execution of sequences code is generated and translated (package = namespace, Document = Class, Procedure = method). Currently generated code is C#. In the future it is possible to generate other code such as Java or Python.

Gene­rated C#-Code

For each OTX document a C# file is generated. The clear and streamlined code corresponds to the code of an expert in diagnostic procedures. It is generated on-the-Fly, translated and executed.

Advantages:

• Maximal performance
  Also suitable for control and regulation tasks

• Minimal ressources usage
  Precompiled sequences can be distributed in an extremly compact way

• Arbitrary target systems possible
  Pocket-PC Browser, etc. Tablett PC.