Remove Batch Signature request
Overview
If a Remove/Reset Command Verification policy is configured in the area model and it
is associated with a Signature Template, then a
Remove Batch
Signature
Request is generated when a user attempts to remove a
batch from the Batch List or reset a phase run under Manual Phase Control.Modifications made to support FactoryTalk Batch electronic signatures
The following is an explanation of the modifications made to support
FactoryTalk® Batch
electronic signatures:Remove Execute | |
|---|---|
Batch Server | When the FactoryTalk Batch Server receives a legal
Remove execute, the area model configuration is checked to
decide if a confirmation Signature is required for the batch
removal request. If one is required, then a Signature Request is
generated using the specified Signature Template and the batch
removal action is queued pending completion of the Signature
Request.Manual Phase Control - When the server receives a legal Phase
Reset Execute, it checks the area model configuration to decide
if a confirmation signature is required. If so, then a Signature
Request is generated using the specified Signature Template and
the phase reset action is queued pending the Signature Request
completion. |
Response | An ActionID is returned by the Execute used to locate the
generated signature. |
Completion | When all Signature Signoffs associated with a Remove Execute are
completed, then the batch specified in the Remove execute is
removed from the batch list if the Remove instruction is still
legal. When all Signatures associated with a Phase Reset are complete,
then the Manual Phase Control batch specified in the Phase Reset
Execute is removed from the Batch List if the Phase Reset
instruction is still legal. |
Overlap | If a Remove Execute is received targeting a batch for which a
queued Remove Execution Action already exists pending Signature
completion(s), then the new Remove Execute fails. The failed
execute’s response item is populated with an appropriate
response string. If a Phase Reset Execute is received targeting a batch for which
a queued Phase Reset Execution Action already exists pending
Signature completion(s), then the new Phase Reset Execute
fails. For purposes of determining the legality of overlapping of
executes, Remove Executes are treated as Phase Reset Executes.
This means that if a Remove Execute action is pending Signature
completion on a Manual Phase Control batch, then a Phase Reset
issued via a Phase Execute to the same batch fails because of
the Remove Execute overlap. |
Cancellation | When an incomplete Signature associated with a Remove Execute
Action is cancelled, then the queued Remove Execute Action is
terminated and its associated incomplete Signature Requests are
System Cancelled. When an incomplete Signature associated with a Phase Reset
Execute Action is cancelled, then the queued Phase Reset Execute
Action is terminated and its associated incomplete Signature
Requests are System Cancelled. |
Automatic Cancellation | A Remove Execute Action that is queued pending Signature
Completion(s) is terminated if the target batch changes to an
illegal state for Batch Removal, resulting in System
Cancellation of its incomplete Signature Request(s). A Phase Reset Execute Action that is queued pending Signature
Completion(s) is terminated if the target batch changes to an
illegal state for Batch Removal, resulting in System
Cancellation of its incomplete Signature Request(s). |
Warm Restart, Warm All Restart, or Hot Restart | Signature Requests generated in response to a Phase Reset or a
Remove Execute Action are System Cancelled in the event of a FactoryTalk Batch Server Warm Restart, Warm All Restart, or Hot Restart. |
Provide Feedback