Configure the Upstream Zone tab of the DRAInjector record

On the Upstream Zone tab, products that are upstream from the Drag Reducing Agent (DRA) Injector are defined so that the DRA incompatible products coming down the line are caught before they actually reach the DRA Injector. Product incompatibilities are detected using the Product Compatibility table (separately configured), which has entries denoting which products are compatible with DRA.

It is possible to define up to four upstream volume measurement devices for which their upstream batch line-ups are monitored proportionally based on their flow rate.

Optionally, you can assign an Advanced Logic Processor Configuration (ALPConfig) record to each configured upstream batch transfer. The evaluated result of the ALPConfig record determines if the batch transfer’s products are included in the upstream violation check. If the result of an ALPConfig record evaluates to false, the system ignores the batch transfer in the violation check. The tables below illustrate how the system calculates upstream volume zone with different ALP configurations.

Note: The flow rate is assumed to be equal among these scenarios.

It is assumed that the DRA injector and the volume sources are physically located in close proximity such that the volume between the injector and the volume sources is negligible.

To configure the Upstream Zone tab of the DRAInjector record

1. Open the DRAInjector record. For more information on opening a DRAInjector record, see Opening the Drag Reducing Agent Injector (DRAInjector) Record.

   The DRAInjector Row Edit dialog appears.

   

2. Select the Upstream Zone tab.

   The Upstream Zone tab appears.

   

3. To enable upstream zone checking, select the Enable checkbox. In order for the upstream zone to be observed, a minimum of one Batch Transfer must be configured to work.

4. In the Batch Transfer column, click (...) for a given row to select the Batch Transfer that should be checked for product incompatibilities. If more than one is configured, special logic is employed to determine what to check from each.

   Further logic is applied after this in regards to the Upstream and Exclusion Zone.

5. Optional: In the Advanced Logic Process column, click (...) for a given row to select the ALPConfig record whose evaluation result determines whether or not the system includes the Batch Transfer's products in the upstream violation check.

6. In the Upstream Zone field, enter the amount of volume to check upstream for product violations. This starts at the active ticket of a connected Batch Transfer and extends into its pending batches, if the zone is larger than the remaining volume of the current ticket. If multiple Batch Transfers are configured, additional logic is applied.

   For each connected Batch Transfer (the rules of connection are covered in step 2), the upstream zone is split between them based on their flow rate. So if there are two Batch Transfers, and one has a flow rate 2x that of the other, and we have an upstream zone of 3000 configured, a zone of 2000 will be applied to the quicker-flowing one, and 1000 will be applied to the slower one. If either of these volumes extend past the remaining volume of the active batch for a Batch Transfer, they will continue their checking in the first pending batch (and if they exceed that they will continue checking the next pending ticket and so on). If any incompatibilities are found, a violation is generated.

   Note: There are maximum and minimum values that can be entered into the Upstream Zone field. The minimum is 0 and the maximum is 99999.

7. In the Exclusion Zone field, enter an amount of the Upstream Zone volume to exclude from violation checking. If configured, this would result in the portion of volume at the front (downstream end) of the Upstream Zone being ignored. The Exclusion Zone is also observed proportionally based on flow rate if multiple volume sources are configured.

   The rules that outline how Batch Transfers should behave in the event that there are multiple Batch Transfer connections associated with the DRA Injector apply to the Exclusion Zone as well.

   Note: The minimum value that can be entered is 0 for the Exclusion Zone. If it is greater than 0, then it must be less than the Upstream Zone. The Exclusive Zone cannot be greater than or equal to the Upstream Zone.

   For example, if there is more than one Batch Transfer configured, the Upstream Zone is split proportionally according to flow rate into individual upstream zones for each Batch Transfer. The Exclusion Zone is also split proportionally in a similar manner.

   Consider having two Batch Transfers connected with the first having a flow rate 2x that of the other, and an Upstream Zone of 9000 and an Exclusion Zone of 1000. The individual upstream zone for the faster Batch Transfer will be 6000 and the individual Upstream Zone for the slower batch transfer will be 3000. Similarly, the Exclusion Zone for the faster Batch Transfer will be 666.67 and the Exclusion Zone for the slower Batch Transfer will be 333.33. Therefore, product violation checking for the faster batch transfer will begin at 666.67 and continue for the remainder of its Upstream Zone of 6000. Similarly, the product violation checking for the slower Batch Transfer will begin at 333.33 and continue for the remainder of its 3000 Upstream Zone.

   Therefore, the total amount of volume checked for the faster Batch Transfer will be 6000 – 666.66 = 5333.33. In the case of the slower Batch Transfer, the total amount of volume checked will be 3000 – 333.33 = 2666.67.