Understand how tickets are checked for errors

Ticketing validation, informally known as error checking, allows you to define standard criteria that must be fulfilled for a pending ticket to be considered valid.

The user input is compared to a series of rules. If the information entered into the system adheres to those rules, the information is considered valid. If it fails, the Controller will be provided with an error message.

The ticket must pass all validity tests before it can be started. If the ticket fails a validity test, the Controller will not be allowed to either start the ticket, or use the Switch on Volume function on the batchXferControls dialog for a batch transfer in the easy eXtended Operator Station (ezXOS).

When the validation applied to tickets fails, a Controller can be provided with a message outlining why the error occurred or why the pending ticket is not currently considered valid.

Your organization has the capacity to define the content of these error messages.

This messaging is displayed when a Controller attempts to either start a pending ticket, or enables Switch on Volume on the batchXferControls dialog. If the ticket is started automatically, the error messaging appears in the Alarm and Event Summaries. An error will also be logged within the AVEVA Enterprise SCADA Error Log for both automatic and manual ticket starts.

You can configure and enable the following automatic checks.

Minimum Time/Flow

Once a ticket has started, it must remain active for a minimum configurable time period, and a minimum configurable amount of a commodity must flow before it can be stopped or a new ticket started.

Actual vs. Scheduled Ticket Size

AVEVA Enterprise SCADA can generate a warning if the actual size of a ticket differs from the scheduled ticket size by more than a configurable amount.

Action Sequence Required

The name of an action sequence record must be entered on the pending ticket before it can be started.