存在几点在动态动作规划及设定值实现方法行为中起重要作用的影响因素。本主题较为详尽地介绍了这些影响因素。其中的某些因素是基于DCS或设备水平解决层面上的，另一些则是算法选项。
涵盖的主题主要包括以下内容：
•内部动作总和（INTSUM）
•动作容忍（MVTOL）
•动作分辨率（MOVRES/ MOVACC）
•动态动作规划选项（DYNOPT）
内部动作总和（INTSUM）
内部动作总和（INTSUM）旨在解决DCS无法执行MV中小的动作（比MVTOL小的）之类的问题。为补偿这一问题，控制器将设定值保持在内部值。
通常情况下控制器计算出MV变化量，并将其加到MV的当前值。控制器从底层读入的值为VIND，向底层写的值为VINDSP。则计算公式为VINDSP=VIND+CMOV。其中CMOV是动态动作规划计算出的增量值。
保存内部设定值后，因为其会积累，我们可以确保小的动作也能写入DCS中。此时VINDSP计算公式为VINDSP=VINDSP_internal+ CMOV,控制器将克服分辨率问题并驱动过程向预定方向。
当控制器为OFF时，内部设定值跟踪VIND值。在许多情况下内部设定值也会被复位，如OFF至ON转换、建议动作正负号变化以及接近操作限时。
该功能默认为OFF。在使用时应用于所有MV。
动作容忍（MVTOL）
动作容忍（MVTOL）是MV在工程极限意义上的分辨率。建议该值从过程控制系统文档中获取确认。
在过程控制系统的模拟转换器中，通过将提供的值（工程单位）除以变量范围得到的2~比特数范围可能是可以接受的。
MVTOL作为容忍限使用范围是高于MV高限和低于MV低限的（ULINDM和LLINDM）。
假设MV的上限是5.00，并且控制器已将设定点(VINDSP)移到该限制处。如果进行数值舍入，由于工艺控制系统的数值分辨率，回读值（VIND）是一个比送出值微大的值，假设是5.01，这一值将会导致控制器关闭该MV并将其作为一个前馈。
为避免这个问题，MVTOL被加入到上限使得VIND值与ULINDM和MVTOL的和进行比较。即使VIND读入值为5.01，计算出的VINDSP也将不超过5.00（ULINDM）。
它也可以用于输入变换或其它输入计算，以避免与过程值或极限比较时产生的数值冲突。
动作分辨率（MOVRES/ MOVACC）
MV最小动作分辨率可在每个MV中设定使用。该功能不适用于DCS解决问题;它是对物理过程的限制。
如果控制器决定该变量执行动作，MOVRES定义了工程单位上一个周期内控制器对MV设定值动作的最小变化值。
该功能对以下两种情况是有用的：一是在过程受影响前需要足够动作的工作阀，二是离散变量如散热片风扇等。
计算出的动作若比MOVRES小将不会执行，但会被累积在MOVACC中。该功能与将LRCRIT设为1（最小动作）是不同的，当确定了稳态解决方案后是在任意方向上惩罚移动MV的。无论动作计划是否调整，当前动作都将被存储到CMOV并用来计算控制器输出的设定值。
其目标是当值在小于当前值MOVRES范围内时，稳态求解器将不会产生解决方案。如果目标计算出一非零变化，则动作必将大于MOVRES。
附原文：
There are several features that impact the behavior of the dynamic move plan or the method that setpoints are implemented. This topic explains more about these features. Some features address resolution issues at the DCS or equipment level, and some address algorithms options.
Topics covered include the following:
• Internal move summation (INTSUM)
• Move tolerance (MVTOL)
• Move resolution (MOVRES / MOVACC)
• Dynamic move plan options (DYNOPT)
Internalmove summation (INTSUM)
Internal move summation (INTSUM) is intended to solve problems associated with the inability of the DCS to implement small moves(less than MVTOL) in the manipulated variables. To compensate for this problem, the controller keeps an internal value of the setpoint.
Ordinarily the controller calculates a delta move in the manipulated variable and adds it to the current value of the manipulated variable. Therefore, it reads in VIND and writes out VINDSP, which is calculated as VIND+ CMOV, where CMOV is the delta move calculated by the dynamic move plan.
By maintaining an internal setpoint, we can ensure that small moves will get written out to the DCS as they accumulate. The VINDSP then becomes VINDSP_internal + CMOV, and the controller will overcome resolution problems and drive the process in the intended direction.
When the controller is OFF, the internal setpoint tracks VIND. The internal setpointis also reset in many situations, such as OFF-to-ON transitions, changes in thesign of the proposed moves, and when near operating limits.
Thefeature is defaulted to OFF. When used, it applies to all manipulated variables.
Movetolerance (MVTOL)
Move tolerance (MVTOL) is the resolution, in engineering limits, of a manipulated variable. It is suggested that this valuebe determined from the process control system documentation.
It might be acceptable to supply the value derived by dividing the range of the variable in engineering units by 2 raised to the power of the number of bits in the analog-to-digital converter of the process control system.
MVTOL is used as a tolerance beyond the high and low MV limits (ULINDM and LLINDM).
Suppose that the MV high limit is 5.00, and the controller has moved the setpoint(VINDSP) to that limit. If round-off occurs, due to process control system numerical resolution, and the value read back (VIND) is a slightly larger value than what was sent, say 5.01, this value will cause the controller to turn off that MV and treat it as a feedforward.
To avoid this problem, MVTOL is added to the high limit so that the VIND value iscompared to the sum of ULINDM and MVTOL. Even if VIND is read in as 5.01, theVINDSP that is calculated will not exceed 5.00 (ULINDM).
It can also be used in an input transform, or other input calculations, to avoid numerical conflicts when comparing process values and limits.
Move resolution (MOVRES / MOVACC)
Manipulated variable minimum move resolution is available on each individual manipulated variable. This feature is not for DCS resolution problems; rather, it is for physical process limitations.
MOVRES defines the smallest change,in engineering units, the controller is to make in the manipulated variable setpoint in one cycle if the controller decides to move this variable.
This feature is useful for working with valves that require sufficient movement before the process is affected and for discrete variables such as fin fans.
Calculated moves smaller than MOVRES are not implemented, but are accumulated in MOVACC instead. This feature is
different than setting LPCRIT to 1 (minimum movement), which penalizes moving the manipulated variable in either direction when determining the steady state solution. Whether the move plan is adjusted or not, the current move is stored in CMOV and then used to calculate the setpoint that is output by the controller.
The goal is that the steady state solver will not produce a solution that is less than MOVRES away from the current value. If a nonzero change in target IS calculated, then moves will be larger than MOVRES.
2015.9.23