Preparing Data for Network Design
This article summarize the minimum data requirements for running a Network Design Study
Overview
Before running a Network Design study, the system requires operational data describing past freight activity. This data allows the optimization engine to analyze shipment patterns and identify consistent lanes, market flows, and tour opportunities.
At minimum, the system must have imported or synchronized records for loads, customers, and locations.
When to Use It
This preparation step should be completed before creating a Network Design study. It ensures the optimization engine has enough historical information to produce meaningful network recommendations.
Required Data
The Network Design module requires the following data to be synchronized:
Loads: Loads represent the shipment history used to identify lane volume and routing patterns.
Customers: Customer information helps identify demand patterns across markets.
Locations: Locations define the geographic coordinates used to determine markets and routing paths.
Together, these datasets allow the system to reconstruct how freight has historically moved across the network.
Recommended Data History
For the most accurate network analysis, it is recommended to include:
-
3 to 12 months of load history
-
Seasonal freight patterns when available
-
Accurate pickup and delivery locations
Shorter datasets may not fully capture recurring network behavior.
Step-by-Step Instructions
- Confirm that location records include valid addresses or coordinates.
-
Verify that customer records are available (minimum data - Customer Name and Reference Code).
-
Confirm that load records are imported into the system.
- Review sample loads to confirm that pickup and delivery locations appear correctly.
Once these datasets are available, you can proceed to creating a Network Design study.
- Determine timeline of market study to align loads and bids
- Gather Market Data (minimum data - Market Code, Latitude, Longitude)
- Gather Bid data (minimum data - Bid Reference Code, Origin City, origin State, Destination City, Destination State)
Tips or Notes
-
Incomplete location data may cause markets to form incorrectly.
-
Duplicate or inconsistent location records can affect lane analysis.
-
Historical loads should include both origin and destination details.