Execution Pipeline
- Last UpdatedJul 05, 2024
- 1 minute read
The Execution Pipeline framework enables you to customize different aspects of the data acquisition module.
As an example, the legacy analog krunch routine contains multiple sequential steps that you can not modify without a source code change. With Execution Pipeline, the sequential steps are now configurable and overridable.
An Execution Pipeline divides a process algorithm within AVEVA Enterprise SCADA into a series of individual and overridable "steps". Each step is an atomic piece of the overall pipeline algorithm. You can override any or all steps within an Execution Pipeline by configuring a replacement Dynamic link library (DLL). Additionally, you can insert new steps at any point in an Execution Pipeline to modify the behaviour.
For more information on how to configure or override steps within an Execution Pipeline, or for more details on current implementations of Execution Pipelines within AVEVA Enterprise SCADA, please refer to the Execution Pipeline Application Programming Interface (API) Reference documentation.