SC Navigator Demo Webinar – Frequently Asked Questions
During our first SC Navigator demo webinar, participants were able to submit questions via the chat.
This FAQ compiles those questions along with our responses. We’ve also included several reference links related to the topics demonstrated by Emily (links are provided at the end of this document).
Topics covered
- End-to-end (E2E) lead time constraints
- Transport load consolidation
- Lead time offset
- Transport cost data
How does using end-to-end (E2E) lead time constraints impact model performance?
Are there any general rules of thumb?
The performance impact of E2E lead time constraints is highly dependent on the size and structure of your model, so it is difficult to give a general rule of thumb upfront.
That said, the example below may help set expectations regarding scale and performance:
- Dataset characteristics
- 110k demand points with a maximum E2E lead time constraint
- 1k transportation lanes with transportation lead times
- No supplier, warehouse, or production lead times
- Observed solve times
- E2E constraint disabled: ~3 minutes
- E2E constraint enabled: ~6 minutes, after which the model concluded infeasibility (not all demand could meet the maximum E2E lead time)
- Infeasibility analysis and relaxation of E2E lead times: 7 iterations, approximately 60 minutes in total
After this process, the E2E lead time is calculated for each demand point.
How does opening inventory work when E2E lead time constraints are enabled?
When E2E lead time constraints are present, opening inventory must be set to zero.
If any value other than zero is entered in the Opening Inventory tab, the data validation step will fail and the E2E lead time optimization will not run. This ensures consistent and correct calculation of E2E lead times.
Are throughput constraints supported for cross-dock (x-dock) locations?
In the simplified model shown during the demo, no throughput constraints were applied to the x-dock location.
However, SC Navigator does support:
- Throughput constraints based on volume and weight
- Constraints on the number of destinations served by an x-dock
Can lead time offset be defined in days instead of months?
Lead time offset is defined in number of periods, and therefore depends on the period length used in your model:
- Monthly periods → lead time offset in months
- Weekly periods → lead time offset in weeks
If a lead time is shorter than a single planning period, production or flow can take place within that period and the lead time offset functionality is not required.
How often are transport cost rates updated?
SC Navigator is currently in a 6-month trial period for transport cost data.
- After the first 3 months of the trial, the transport cost data will be updated (May 2026).
- At the end of the 6-month trial, we will determine next steps based on usage and feedback