Understand Product Injection Verification and Control
- Last UpdatedApr 24, 2025
- 3 minute read
The Product Transfer Checking (PTC) application provides the ability to configure records for Product Injection Verification and Control. This feature allows the system to automatically send an ON or OFF command to a configurable status or multistate point that serves as a permissive for injection. The decision to send an ON or OFF command is based on compatibility between a configurable source (Batch Transfer [batchXfer] or Virtual Flow Computer [virtualflowcomputer]) and a configurable destination (node). Compatibility is defined as an exact product match between the products.
This feature also allows the configuration of an upstream no-injection zone and a downstream no-injection zone. These zones serve as buffers so that the injection only occurs into the heart of the product and away from the batch interfaces, as shown in the diagram below. The Administrator can also specify upstream and downstream warning zones in order to receive audit events in advance of sending an ON command (which occurs after the downstream no-injection zone ends), or, in advance of sending an OFF command (which occurs after the upstream no-injection zone begins).
The following table lists the sequence of events expected to occur as the batch lineup passes through the injection location.
|
Location of Batch Transfer or VFC |
Product Compatibility |
System Behaviour |
|---|---|---|
|
|
Compatible |
The system logs an event indicating that an ON command will be sent after the configured downstream warning volume/time passes. |
|
|
Compatible |
The system sends an ON command, raises an alarm, and logs an event. |
|
|
Compatible |
The system logs an event indicating that an OFF command will be sent after the configured upstream warning volume/time passes. |
|
|
Compatible |
The system sends an OFF command, raises an alarm, and logs an event. |
|
|
Incompatible |
The system will do nothing since it had already sent an OFF command. |
A configurable Control Delay is also available to allow for a wait period in between sending commands to the status or multistate point. That is, after sending an ON or OFF command, the system will not send another command until the Control Delay has passed, even if the system observes a reason to do so. Ensure that you accurately specify the Control Delay based on typical batch sizes and flow rates for a given pipeline. Otherwise, a situation may arise where the system may not react to a change in product due to a long Control Delay.
Note: The Product Injection Verification and Control feature should only be configured when the pipeline has product flowing in a forward direction. Reversed flow is not supported.
For detailed information on how to use the Product Transfer Checking (flowXfer) dialog to define Product Injection Verification and Control information, see Understand the Product Transfer Checking Record Destination tab.