Control Loops
Find the loops that do not control well, know why in plain words, and get a tuning in your controller’s own units.
The problem it solves
A loop in manual is a loop nobody trusts.
A plant has many loops. Some oscillate, sit in manual or fight a sticking valve, and nobody has time to check them one by one.
Retuning by trial and error takes time, and it never cures a sticking valve or data that is too slow.
1 · Ranked Every loop of the plant, the worst first, with what is wrong.
2 · Checked Six checks per loop: mode, control, valve, oscillation and more.
3 · Explained What each check found, in plain words, with what to do.
4 · Tuned A tuning in the controller’s units, with the reason for each change.
What it does
-
A health index per loop
Six checks of the last hours: the time in the normal mode, the control within its band, the valve, the oscillation, the performance index and the data. The worst loops first.
-
Problems found for you
Loops in manual, oscillating or saturated, sticking valves found from the shape of the oscillation, and data too slow or too compressed for the loop.
-
Explanations in plain words
What each check found, the worst first, with what to do. The AI can sum it up and draft a work order to paste in your maintenance system.
-
Tuning suggestions
P, I and D in your controller’s own form and units, for three speeds, with the reason for each change and the process model found in the data.
-
A tuning log
The changes applied in the control system, with the loop’s health before and since.
-
Your PI points, unchanged
Each loop’s PV, setpoint and output are read through your AVEVA CONNECT, found by their PI names or by the AI. OneStop never changes your points or your controllers.
Who uses it
- Control and process engineers who own the loops.
- Instrumentation and maintenance teams who fix valves and transmitters.
- Operations supervisors who want fewer loops in manual.
See it on your own data.
Ask for a demo on our simulated mines, or tell us how you want to use it on yours.