Summary of Product Compatibility messages and events
- Last UpdatedApr 24, 2025
- 9 minute read
The following messages and events are the result of Rules Validation Engine (RVE) configuration. These appear first as a pop-up window; but if there is also Product Monitor component designed to look for violations, the same alarm and event messages are recorded in the Alarm and Event Summary.
The following table details the messages and events associated with RVE rule configuration.
|
Message |
Description |
|---|---|
|
RVEbltcaller: Rule 1 - Product [Source] (Tank: Source) is incompatible with the product [Destination] (Tank: Destination). |
This error message indicates that the source product is not compatible with the destination product. The rule number indicates which RVE Rule is being violated. Compatibility is assessed for the following before the valves are opened:
This error message is the result of the ProductTransferValveOpenVerify command. |
|
RVEbltcaller: Rule 1 - Product [Source] in tank [Tank Name] is incompatible with the products of the tank group:[Destination Product List Separated by Commas]. |
This error message indicates that the source product is not compatible with the destination product. The rule number indicates which RVE Rule is being violated. Compatibility is assessed for the following before the valves are opened:
This error message is the result of the ProductTransferValveOpenVerify command. |
|
Product incompatibility detected at pump [Pump Name] and pipe segment [Destination Name]. The following product(s) in the pipe are not compatible with the product ([Source Product]) in the pump:[Destination Product List Separated by Commas]. |
This error message indicates that the source product is not compatible with the destination product. The rule number indicates which RVE Rule is being violated. Compatibility is assessed for the following before the pump is started:
This error message is the result of the productTransferPumpStartVerify command. |
|
DRA pump start restricted at virtualflowcomputer [Name] by the following incompatible product(s):[Destination Product List Separated by Commas]. |
This error message indicates that the source product is not compatible with DRA and the injection will not take place. The rule number indicates which RVE Rule is being violated.
This error message is the result of the ProductTransferDRAVerify command. |
|
DRA pump start restricted at milepost [Mile Post] on pipe segment [Pipeline Location Name] by the following incompatible product(s) in the [Volume] upstream to [Volume] downstream zone: [Destination Product List Separated by Commas]. |
This error message indicates that the source product is not compatible with Drag Reducing Agent (DRA) and the injection will not take place. The rule number indicates which RVE Rule is being violated.
This error message is the result of the DRAVerify command. |
|
DRA pump start restricted at tank [Tank Name] by the following incompatible products(s): |
This error message indicates that the source product is not compatible with DRA and the injection will take place. The rule number indicates which RVE rule is being violated.
This error message is the result of the DRAVerify command. |
|
RVEbltcaller: Rule 1 - violation for flowxfer '[flowXfer Name]': - Violation product '[Product at Batch Transfer]' found at Batch Transfer '[Batch Transfer Name]'. |
This error message indicates that the source product is not compatible with DRA and the injection will not take place. The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The following products in virtualflowcomputer [VFC Name] are not compatible with the product [Product in Tank] in Tank [Tank Name]:- [Product in VFC]. |
This error message indicates that the product at source (VFC) is not compatible with the product at Destination (Tank). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The following products in tank [Tank Name] are not compatible with the product [product in VFC] in virtualflowcomputer [VFC Name]:[product in Tank]. |
This error message indicates that the product at source (Tank) is not compatible with the product at Destination (VFC). The rule number indicates which RVE Rule is being violated.
This error message is the result of the productTransferValveOpenVerify command. |
|
RVEbltcaller: Rule 1 - The Product [Product at VFC] at virtualflowcomputer [VFC Name] is not compatible with the product [Product at Pipeline Location] at pipe_segment [Pipeline Location Name]. |
This error message indicates that the product at source (VFC) is not compatible with the product at Destination (Pipeline Location). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The Product [Product at Pipeline Location] at pipe_segment [Pipeline Location Name] is not compatible with the product [product in VFC] at VFC [Product in VFC]. |
This error message indicates that the product at source (Pipeline Location) is not compatible with the product at Destination (VFC). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The following products in Batch Transfer [Batch Transfer Name] are not compatible with the product [product in Tank] in tank [Tank Name]: [Product in Batch Transfer]. |
This error message indicates that the product at source (Batch Transfer) is not compatible with the product at Destination (Tank). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The following products in tank [Tank Name] are not compatible with the product [Product in Batch Transfer] in batch transfer [Batch Transfer Name]: [Product in Tank]. |
This error message indicates that the product at source (Tank) is not compatible with the product at Destination (Batch Transfer). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The Product [Product in Batch Transfer] at Batch Transfer [Batch Transfer Name] is not compatible with the product [Product in pipe_segment] at pipe_segment [Pipeline Location Name]. |
This error message indicates that the product at source (Batch Transfer) is not compatible with the product at Destination (Pipeline Location). The rule number indicates which RVE Rule is being violated.
|
|
RVEbltcaller: Rule 1 - The Product [Product in pipe_segment] at pipe_segment [Pipeline Location name] is not compatible with the product [product in Batch Transfer] at batch transfer [Batch Transfer Name]. |
This error message indicates that the product at source (pipe segment) is not compatible with the product at Destination (Batch Transfer). The rule number indicates which RVE Rule is being violated.
|
The following table details the messages and alarms associated with the Product Monitor process.
The Product Monitor process is used to silently monitor for un-commanded changes to values and objects.
|
Message |
Description |
|---|---|
|
Product compatibility violation between [Source Type] [Source Name] and [Destination Type] [Destination Name] (Products [Product in Source] and [Product in Destination]). |
This error message indicates that there is a Product Compatibility violation between the source and destination product. It is applicable to the following configurations:
These alarms and events can be generated even if you or another Controller has previously overridden an RVE rule-generated error message. For more information, see Understand and respond to a Command Violation. |
The following table details the messages and alarms associated with Product Injection Verification and Control.
The Product Injection Verification feature allows the system to automatically send an ON or OFF command to a configurable status or multistate point.
|
Message |
Description |
|---|---|
|
Product Transfer Checking Record <Flow Transfer Name>: Node <Node Name> entered the injection zone of the compatible batch. Sending an ON command to <Table Name (Status/Multistate)> <Point Name> point. |
This alarm is generated when the downstream no injection zone ends and an ON command is sent to the permissive. |
|
Product Transfer Checking Record <Flow Transfer Name>: Node <Node Name> exited the injection zone of the compatible batch. Sending an OFF command to <Table Name (Status/Multistate)> <Point Name> point. |
This alarm is generated when the upstream no injection zone begins and an OFF command is sent to the permissive. |
|
Automatic Product Injection and Verification Control has been disabled for pipeline <Pipeline Name> by <User> at <Location> due to deactivating the pipeline | system startup. |
This event is generated to indicate that the product injection auto enable control is disabled for the pipeline. |
|
Automatic Product Injection and Verification Control has been re-enabled for pipeline <Pipeline Name> by <User> at <Location>. |
This event is generated to indicate that the product injection auto enable control is re-enabled for the pipeline. |
|
Product Transfer Checking Record <Flow Transfer Name> : Node <Node Name> will reach the end of the downstream no injection zone of the compatible batch (configured at <Downstream Zone Configuration>) and issue an ON command in approximately <DOWNSTREAM REMAINING WARNING ZONE VOLUME (Calculated)>. |
This event is generated to indicate that the downstream no injection zone is about to end. This version of the event will be generated if the Product Transfer Checking record is configured to be volume based.
|
|
Product Transfer Checking Record <Flow Transfer Name>: Node <Node Name> will reach the upstream no injection zone of the compatible batch (configured at <Upstream Zone Configuration>) and issue an OFF command in approximately <UPSTREAM REMAINING WARNING ZONE VOLUME (Calculated)>. |
This event is generated to indicate that the upstream no injection zone is about to begin. This version of the event will be generated if the Product Transfer Checking record is configured to be volume based. |
|
Product Transfer Checking Record <Flow Transfer Name>: Node <Node Name> will reach the end of the downstream no injection zone of the compatible batch (configured at <Downstream Zone Configuration>) and issue an ON command in approximately <DOWNSTREAM REMAINING WARNING ZONE TIME (Calculated)> - at an effective flow rate of <Segment Flow Rate>. |
This event is generated to indicate that the downstream no injection zone is about to end. This version of the event will be generated if the Product Transfer Checking record is configured to be time based. |
|
Product Transfer Checking Record <Flow Transfer Name>: Node <Node Name> will reach the upstream no injection zone of the compatible batch (configured at <Upstream Zone Configuration>) and issue an OFF command in approximately <UPSTREAM REMAINING WARNING ZONE TIME (Calculated)> - at an effective flow rate of <Segment Flow Rate>. |
This event is generated to indicate that the upstream no injection zone is about to begin. This version of the event will be generated if the Product Transfer Checking record is configured to be time based. |
|
One or more errors occurred in Product Injection BLT on FlowTransfer <Flow Transfer Name>. Please check the log file for more details. |
This alarm indicates that there is one or more unexpected issues with the flow transfer record. Contact your administrator and consult the log for more details. |
|
The Flow Transfer Record <Flow Transfer Name> has configuration errors, due to an incorrect reference. See error logs for more details and contact your system administrator. |
This alarm indicates that there is one or more configuration issues with the flow transfer record that will need to be resolved before further processing will occur. Contact your administrator and consult the log for more details. |
|
The Flow Transfer Record <Flow Transfer Name> configuration error has been resolved. |
This alarm indicates that the configuration issues have been resolved and the flow transfer record will continue processing. No action is required. |
|
Product Transfer Checking Record <FLOW TRANSFER NAME>: Node <NODE NAME> entered the injection zone of the compatible batch. An ON command will not be sent to <TABLE NAME (STATUS/MULTISTATE)> due to a Control Delay (configured at <CONTROL DELAY CONFIGURTION> minutes). The next command can be sent after <REMAINING CONTROL DELAY TIME> minutes. |
This event indicates that the batch has entered the injection zone. However, due to Control Delay, the ON command will not be sent. |
|
Product Transfer Checking Record <FLOW TRANSFER NAME>: Node <NODE NAME> exited the injection zone of the compatible batch. An OFF command will not be sent to <TABLE NAME (STATUS/MULTISTATE)> due to a Control Delay (configured at <CONTROL DELAY CONFIGURTION> minutes). The next command can be sent after <REMAINING CONTROL DELAY TIME> minutes. |
This event indicates that the batch has exited the injection zone. However, due to Control Delay, the OFF command will not be sent. |
|
Product Transfer Checking Record <FLOW TRANSFER NAME>: Node <NODE NAME> is out of the downstream warning zone. |
This event indicates that the batch is fluctuating around the Downstream Warning Zone. This could happen in scenarios that cause the batch to move in a reverse direction and enter the no-injection zone again (for example, after resizing a batch in Batch Tracking). |
|
Product Transfer Checking Record <FLOW TRANSFER NAME>: Node <NODE NAME> is out of the upstream warning zone. |
This event indicates that the batch is fluctuating around the Upstream Warning Zone. This could happen in scenarios that cause the batch to move in a reverse direction and enter the injection zone again (for example, after resizing a batch in Batch Tracking). |