Understand completed ticket data flow

There are two ways to handle completed tickets.

Typically, the batch transfer creates completed tickets in the manner demonstrated in the diagram below:

The second method, referred to as Completed Ticket Upload, is the process in which the AVEVA Enterprise SCADA (Host) will send a request to the Flow Computer for the ticket.

This process relies on the assumption that the protocol has been developed to both send the command and receive the completed ticket(s) from the Flow Computer. The protocol will then need to be capable of sending the completed ticket information, unaltered, into a table in Microsoft SQL Server known as LMS.rdm_readingRaw. From there, an application known as the Data Payload Processor (DPP) will take the information from the Flow Computer and translate it into our Completed Ticket Storage table, LMS.ticketTotal. The LMS.flowcomputerTicketDevice table also stores additional Historical information.

The configuration of the DPP will need to be customized for each Flow Computer.