Understand Product Compatibility continuous monitoring

For any product transfers where the source or destination is a batch transfer or pipeline, the product or products present will change. Therefore any transfers involving these source or destination types need to be monitored. Periodically, products at the source and destination are re-obtained, compatibility is re-checked, and the presence of a rules violation is determined. If any rule violation is detected, an alarm is issued.

The system searches for the following sources of incompatibility, asking the following questions:

1. Given a DRA Injector source: Is the product contained at the Pipeline Location (pipe_segment) destination record compatible with the Drag Reducing Agent (DRA)? This check ensures that the products can be safely combined.

2. Given a DRA Injector source: Is the product contained in the Batch Transfer (batchXfer) / Virtual Flow Computer (VFC) destination record compatible with DRA? This check ensures that the products can be safely combined.

3. Are the products contained in the Batch Transfer / VFC source record and the Pipeline Location destination record compatible? This check looks at the following to ensure that the products in the Batch Transfer / VFC source and the Pipeline Location destination are compatible:

   • The product currently flowing at the source Batch Transfer / VFC. In addition, in the case of Batch Transfer, future product information is gathered from a configurable number of pending tickets.

   • The product contained in the source Batch Transfer / VFC information compared with the product flowing at the destination Pipeline Location as well as the products contained in adjacent upstream and downstream zones.

4. Are the the products contained in the Pipeline Location source record and the Batch Transfer / VFC destination record compatible? This check looks at the following to ensure that the products in the Pipeline Location source record and the Batch Transfer / VFC destination record are compatible:

   • The product currently flowing in the Pipeline Location compared with the products that are currently flowing at the destination Batch Transfer / VFC. In addition, in the case of Batch Transfer, future product information is also gathered from a configurable number of pending tickets.

   • The product currently flowing at the source Pipeline Location as well as the products contained in adjacent upstream and downstream zones.

5. Are the products contained in the Batch Transfer / VFC source record and the Tank destination record compatible? This check looks at the following to ensure that the products in the Batch Transfer / VFC source record and the tank destination record are compatible:

   • The product currently flowing at the source Batch Transfer / VFC. In addition, in the case of Batch Transfer, future product information is also gathered from a configurable number of pending tickets.

   • The product is checked to ensure that they will be compatible with the product stored in the tank.

6. Are the products contained in the Tank source record and the product contained in the Batch Transfer / VFC destination record compatible? This check looks at the following to ensure that the products in the Tank source record and product contained in the Batch Transfer / VFC destination record are compatible:

   • The product contained in the tank.

   • The tank's product information compared with the product that is currently flowing at the destination Batch Transfer / VFC. In addition, in the case of Batch Transfer, future product information is also gathered from a configurable number of pending tickets.

     Note: For all product transfers, product combinations are monitored by Rules Validation Engine (RVE) rules and the Product Monitor service. Even if an RVE rule validation is overridden, the Product Monitor service continually monitors for sources of incompatibility. The Product Monitor is responsible for logging alarms and events in the Alarm and Event Summaries.