Listed below are common questions about Backhaul Optimization.

General

• If I need help configuring Backhaul Optimization, what should I do?
• Where can I find a network dataset to use for closest facility analysis?

Troubleshooting

• During the Backhaul Assets script, I receive warnings like:
  • Location "Remote X" in "Incidents" is unlocated
  • Location "Fixed X" in "Facilities" is unlocated
  What do these warnings mean and how do I fix the data so that these assets are included in closest facility solves?
• During the Backhaul Assets script, I receive warnings like:
  • Location "Remote X" in "Incidents" is on a non-traversable network element position.
  • 0 location(s) in "Incidents" are valid. Need at least 1 valid location(s).
  Why are my locations invalid?

If I need help configuring Backhaul Optimization, what should I do?

If you need support configuring Backhaul Optimization at your organization, please contact Esri Support Services. If you would like to get help from other telecommunications community members, post your question on the Utilities and Telecommunications space on GeoNet.

Where can I find a network dataset to use for closest facility analysis?

The sample data provided with this solution was created with StreetMap Premium for ArcGIS. You can use this dataset for routing or your own custom network dataset.

What do these warnings mean and how do I fix the data so that these assets are included in closest facility solves?

The unlocated warnings mean that the assets are outside of the network dataset search tolerance (the default is 5,000m) and therefore their network locations could not be calculated. If you want to include these assets in future closest facility solves:

1. Open the Calculate Locations tool in the Network Analyst toolbox.
2. Specify the feature class in the Assets.gdb created by the Locate Assets script.
3. Increase the search tolerance and run.
4. Repeat as needed until all desired assets have a network location.

Why are my locations invalid?

Invalid locations can be caused by multiple factors such as barriers, closest facility restrictions, or network dataset updates.

1. Remove all point, line, and polygon barriers from the closest facility layer.
2. Disable closest facility layer restrictions.
3. If the network dataset has been edited or rebuilt recently, re-run the Locate Assets script.