Parameter deviation signature requests

When an attempt is made to change a recipe parameter value, the

FactoryTalk Batch

Server validates the new value against the correct limits and then executes the correct verification policy. There are two ways a recipe parameter can be changed, SETPARM and ACK executes.

After checking for deviations, the server carries out the parameter’s configured verification policy. A verification policy of "None" has no action, meaning that no electronic signatures or failures are generated even if a deviation exists. When the verification policy is "Signature Template", the server initiates an action as defined by the signature template. When the verification policy is "Not Allowed", the server fails the parameter change. The SETPARM or ACK execute response will be: "FAIL: Value is outside the permitted limits."

If a parameter value is changed on a recipe parameter, the limit values must remain within the high and low range defined in the area model. The server will not allow a batch to be created containing a recipe parameter that violates the limit values defined area model.

When a phase is run in Manual Phase Control, the server reads the recipe and report parameter limits from the area model phase class configuration. If a phase is executing within a recipe, then the server reads the recipe and report parameter limits from the recipe step configuration.

An ActionID is returned by the execute used to locate the generated signature(s).

The server does not change the parameter value sent in the ACK or SETPARM execute until all required signatures are complete. Completion of a signature generated for Parameter Deviation acknowledgment results in execution of a queued SetParm or ParamValueAck execute action if the signature was the last remaining incomplete signature associated with the action.

Cancellation of a signature generated for acknowledgment of a Parameter Deviation results in termination of its associated SetParm or ParamValueAck execute action and termination of any incomplete signature requests associated with the same action.

If a SetParm execute is received targeting a parameter that has incomplete signature requests for a prior SetParm execute action, then the new SetParm execute fails. A failed execute’s response item contains an appropriate error message.

If an Ack execute response to a recipe phase bind prompt is received while there are existing incomplete signature requests generated by a prior Ack to the same prompt, or the batch has a Remove action pending, then the new execute fails. The failed execute’s response item is populated with an appropriate error message string.

Parameter deviation signature requests are system cancelled if any other incomplete signatures associated with the same Action ID are cancelled. The server does not change the parameter value sent in the ACK or SETPARM if any of the required signatures are cancelled.

A

FactoryTalk Batch

Server warm boot restores parameter deviation signature requests generated by a SetParm execute action, but not those generated by an Ack execute action.