General usage signature requests

General usage signatures are generated by Phase Logic requests received from Equipment Phases. The equipment phase specifies the Signature Template ID from which the Signature is generated, and the Phase Logic Request is considered complete when the Signature Request is complete.

If a Phase Logic Request for a General Usage Signature specifies an invalid Signature Template ID, then the Phase Logic Request is handled according to standard Phase Logic Request failure protocols. If the request is successful in generating the Signature, then no response is made until the Signature is either complete or cancelled.

When the Signature for a General Usage Signature generated by a Phase Logic Request is complete, then the Phase Logic Request is considered complete. The Phase Logic Request completion is handled via the standard Phase Logic Request communication protocol.

When the Signature for a General Usage Signature generated by a Phase Logic request is cancelled, the Phase Logic request is considered failed. The Phase Logic request failure is handled via the standard Phase Logic request communication protocol.

The Phase Logic Request protocol does not support overlapped Phase Logic requests; hence, overlapped general usage signatures are not an issue. Note that parallel recipe phases can create parallel requests, but no parallelism is possible from within the scope of a single equipment phase.

If the Phase Logic request from which a general usage signature is generated is aborted, then the general usage signature is System Cancelled if it is in the incomplete state.

Signature requests generated in response to a General Usage Signature Phase Logic request are System Cancelled in the event of a FactoryTalk Batch Server warm boot.