You are on page 1of 1

Document ID : OPR-R310.

1-001
Loop Scout Detail Report
OperTune R310.1 Quick-Start
Simple Flow, Pressure, Temperature, Level Loops and 1
Yes Responsive Loops Only:
1. Do not use OperTune for feed forward, split range, 3
pH, fan-out etc. 5
Note: OperTune needs to be used for tuning under 4
supervision of operator/control engineer and never to be
left unattended

Loop Scout Pre-Check: 2


2. Loop Scout Detail Report available and current? 6
3. Performance unacceptable?
4. No sticky valves? Valve Stiction Probability < 80%
6
5. Either a) no common oscillations or b) high confidence this
loop is the source of common oscillations?
6. Loop PV and OP patterns consistent?
7. No filters or delays configured in instrument?
14
Final Setup of OperTune:
8. Appropriate Controller type (PI or PID) is selected OperTune Configuration Windows
9. Operator has provided large enough OP move?
Should be able to see clear PV response.
10. Operator knows when test will start, how long
will it last, and how to stop it if necessary? 12
11. Accurate Closed Loop Settling Time has been entered?
If not known, use 1min for flow and for pressure loops.
12. PV limits are acceptable? It will try to stay within limits. 13
13. X Parameter is set to 4-6 if aggressive tuning desired?
14. For level loops, please select the suitable loop objective,
i.e. surge or regulation. 20
15. Set safe OP limits during tuning. Note that PV, OP safe
limits will be used during tuning and these values will not
OperTune Main Window
be written to DCS 10
Begin Tuning
8
During OperTune Tuning Session:
16. Is PV moving enough? If not increase OP% excitation.
17. Is PV moving too much? If so decrease OP% excitation. 9,16,17
18. If SP is changed during tuning, duration of 11
test will be increased.
19. If actual Closed Loop Settling Time is far from 19
estimate in Step 20, it will be recalculated,
which will restart the test. Note that, when test restarts, OP
jumps to the value at the beginning of the test.
20. Check for Estimated Time to complete tuning
12
15
R310.1 June 2010

You might also like