Skip to Content
Jan 22, 2019 at 10:11 PM

RBATP Calculation profile - Allowed delays not working as expected


Hello All,

We're working on turning on the RBATP Location Substitution logic and I've created multiple Rules for our checks. The first Rule is to check a 3 day window, in the calculation profile Allowed Delay setup. And the second Rule checks the full horizon.

The idea is to check the multiple plants for the 3 day window, if confirmations are found, accept them. If no confirmation are found, check the full window for the multiple plants and find the next "best" confirmation.

From what I've read, the Calculation profile should be based on the MAD date (some had asked this question back in 2013 - However, I'm finding that in my setup, the confirmed MAD is available tomorrow, well within my 3 day Allowed delay window, but the Rule check is not acknowledging it. However, my confirmed Delivery Date is 9 days later. When I change the route so that my TPT is only 2 days, my Confirmed Delivery Date pulls, the confirmed MAD is still tomorrow and my first Rule picks up the support in the 3 day window. It seems as though the delivery date is playing a part in the check.

Has anyone seen this or had similar issues?


-Current date 1/22/2019

-RDD is 1/23/2019

-CMAD is 1/23/2019

-CDD is 1/31/2019

*Rule 1 window is 1/22/2019 to 1/25/2019 (CMAD falls within this window).

*Rule 2 window is current date + APT +RLT (i.e. open).

I do not have the Use calculation profile option selected on the Check Instructions because I don't want to use that capability. The logic worked in our development environment fine, but that was when the TPT was 0 days.

Thank you for any insight you can provide.

Jodi Martin