Customers

Internal Table Name: Customers

Use this table to define the customers in your network. Site names and Customer names should be unique - you should not have Sites with the same names as Customers. If there are names duplicated between the Sites and Customers tables, this will be reported in the ErrorLog.txt file when the model is run.

Name

Technology: All

Table: Customers

Internal Name: CustomerName

Type: Short Text (100)

Enter a unique Name to represent the customer.

Do not use the same value for customer names and site names.
When using Transportation Optimization, do not use a value of "Dummy_611953" as the Name. This value is a reserved keyword.

Address

Technology: All

Table: Customers

Internal Name: CustomerAddress

Type: Short Text (100)

Enter the street address of the customer. You can also use the built in geocoder to place the customer at the correct Latitude and Longitude.

City

Technology: All

Table: Customers

Internal Name: CustomerCity

Type: Short Text (100)

Enter the city for the customer. You can also use the built in geocoder to place the customer at the correct Latitude and Longitude.

State

Technology: All

Table: Customers

Internal Name: CustomerState

Type: Short Text (100)

Enter the state or province of the customer. You can also use the built in geocoder to place the customer at the correct Latitude and Longitude.

Country

Technology: All

Table: Customers

Internal Name: CustomerCountry

Type: Short Text (100)

Enter the country of the customer. You can also use the built in geocoder to place the customer at the correct Latitude and Longitude.

Postal Code

Technology: All

Table: Customers

Internal Name: CustomerZipCode

Type: Short Text (50)

Enter the postal code for the customer. You can also use the built in geocoder to place the customer at the correct Latitude and Longitude.

Latitude

Technology: All

Table: Customers

Internal Name: CustomerLatitude

Type: Number (Double)

Enter the Latitude of your customer location. You can use the built in geocoding to populate Latitude and Longitude based on the customer’s Address, City, State, Country and/or Postal Code.

Based on the extents of the map, the Latitude limits for displaying locations is: >= -85 and <= 85
If you have customers defined with a Latitude outside this range (for example, -86.5), they are not displayed on the map. If you have connections, such as Customer Flows that use a customer with a Latitude outside this range, those connections are not displayed on the map.

Longitude

Technology: All

Table: Customers

Internal Name: CustomerLongitude

Type: Number (Double)

Enter the Longitude of your customer location. You can use the built in geocoding to populate Latitude and Longitude based on the customer’s Address, City, State, Country and/or Postal Code.

The Longitude limits for displaying locations is: >= -180 and <= 180
If you have customers defined with a Longitude outside this range (for example, -186.5), they are not displayed on the map. If you have connections, such as Customer Flows that use a customer with a Longitude outside this range, those connections are not displayed on the map.

Time Zone

Technology: TO

Table: Customers

Internal Name: TimeZone

Type: Short Text (50)

This field specifies the time zone for the customer. It is used to determine the local time for route scheduling.

Transportation Optimization uses a default of Eastern Standard Time if no Time Zone is provided.

Default: Eastern Standard Time

Weekly Schedule

Technology: S

Table: Customers

Internal Name: WeeklySchedule

Type: Short Text (100)

Selecting a weekly work pattern requires the customer to ship and receive orders only during its specified work times during a weekly period.

Annual Schedule

Technology: S

Table: Customers

Internal Name: AnnualSchedule

Type: Short Text (100)

Use this field to change weekly schedules throughout the simulation. For example, a customer might only operate for three days during the a holiday week. In order to select an annual schedule, you must first populate it in the Annual Schedules table.

Organization

Technology: NO IO S

Table: Customers

Internal Name: OrganizationName

Type: Short Text (255)

Select the organization to which the customer belongs.

Tax Region

Technology: NO

Table: Customers

Internal Name: TaxRegionName

Type: Short Text (50)

Use this column to assign the customer to a tax region for use in calculating taxes and duties. When defining a tax region you can specify a region, sites or customers for the Source and Destination fields. The selection of a region for either of these fields affects how product values are calculated.

  • If the location is a site (not a customer), use the Product Taxable Value from the Inventory Policies table.
  • If the location is a region, then the value is calculated based on the Taxable Value Overrides table. If there are no associated records in the Taxable Value Overrides table, a straight average across locations is used (default).
    • If the region includes a mix of customers and sites, the Product Price is used for the customers and the taxable value (as described above) is used for the sites.
    • If the region includes only sites, the taxable value (as described above) is used.
    • If the region includes only customers, use Price values from Products.

Transportation Region

Technology: All

Table: Customers

Internal Name: TransportationRegion

Type: Short Text (255)

Enter the region to which the customer belongs for use in multi-stop estimated route calculation. Customers assigned to the region are used to determine more accurate transportation costs.

Single Site Sourcing

Technology: NO IO S

Table: Customers

Internal Name: SingleSiteSourcing

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

When this field is set to Yes, the site will be required to source all products from only a single site for the model horizon. Even if a new site becomes available as a source in a future period, Network Optimization will not use this site to source products. You can override the horizon-based sourcing restriction to force the constraint at a period level using settings on the Constraints tab in Optimization Options.

Fixed Service Time

Technology: TO

Table: Customers

Internal Name: FixedServiceTime

Type: Short Text (50)

This field specifies the fixed amount of service time at the customer. It is applicable to pool site, pickup and delivery locations. Enter a value, then select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Fixed Service Time Load

Technology: TO

Table: Customers

Internal Name: FixedServiceTimeLoad

Type: Short Text (50)

This field specifies the fixed amount of service time for loading at the customer. The total service time at a pickup stop =

Fixed Service Time + Fixed Service Time Load + (Variable Service Time Load x total Quantity/Weight/Volume value),

Enter a value, then select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Fixed Service Time Unload

Technology: TO

Table: Customers

Internal Name: FixedServiceTimeUnload

Type: Short Text (50)

This field specifies the fixed amount of service time for unloading at the customer. The total service time at a delivery stop =

Fixed Service Time + Fixed Service Time Unload + (Variable Service Time Unload x total Quantity/Weight/Volume value),

Enter a value, then select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Load

Technology: TO

Table: Customers

Internal Name: VariableServiceTimeLoad

Type: Short Text (50)

This field specifies the variable amount of service time for loading at the customer. The total service time at a pickup stop =

Fixed Service Time + Fixed Service Time Load + (Variable Service Time Load x total Quantity/Weight/Volume value),

Use of a Quantity/Weight/Volume unit of measure is defined by Variable Service Time Basis.

Enter a value, then select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Unload

Technology: TO

Table: Customers

Internal Name: VariableServiceTimeUnload

Type: Short Text (50)

This field specifies the variable amount of service time for unloading at the customer. The total service time at a delivery stop =

Fixed Service Time + Fixed Service Time Unload + (Variable Service Time Unload x total Quantity/Weight/Volume value),

Use of a Quantity/Weight/Volume unit of measure is defined by Variable Service Time Basis.

Enter a value, then select a time unit of measure. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Variable Service Time Basis

Technology: TO

Table: Customers

Internal Name: VariableServiceTimeBasis

Type: Short Text (50)

Select the Unit of Measure by which variable service time is assessed. Select one of Quantity, Weight or Volume, then select the specific unit of measure. If you do not select a unit of measure, the default Quantity unit of measure is used.

Number Of Dock Doors

Technology: TO

Table: Customers

Internal Name: NumberOfDockDoors

Type: Integer

Specify the number of dock doors available at the Site. If dock doors are not defined, there is no constraint on dock doors and multiple vehicles can be routed to the same location at the same time.

Dock Door Reset Time

Technology: TO

Table: Customers

Internal Name: DockDoorResetTime

Type: Short Text (100)

Specify the time required to dispatch one vehicle from the dock door and bring the next vehicle to the dock door. This is the time between one vehicle leaving the door and the next one arriving at the same door. This time is in addition to the fixed and variable unloading and loading time at the stop. If you do not select a unit of measure, the default Time Unit Of Measure from Model Settings is used.

Mandatory Routing Sequence

Technology: TO

Table: Customers

Internal Name: RoutingSequence

Type: Short Text (10)

In many cases, specific Sites and Customers are required to be either the first or the last stop on a route. You can specify this requirement using the Mandatory Routing Sequence column. By default, this value is null, meaning that there is no constraint on the Customer in its routing sequence. You can select one of the available values to control the sequence for the location:

  • First Pickup - This location will always be the first pickup stop on a route to which it is assigned.
  • Last Pickup - This location will always be the last pickup stop on a route to which it is assigned.
  • First Delivery - This location will always be the first delivery stop on a route to which it is assigned.
  • Last Delivery - This location will always be the last delivery stop on a route to which it is assigned.

Drone Eligible

Technology: TO

Table: Customers

Internal Name: IsDroneEligible

Type: Bit

One of Yes, No. (Actual database values are 1,0.)

Select "Yes" if the customer can be a stop for drone sorties. Locations where the Drone Eligible column is set to "Yes" can be served by drones or by trucks. Locations where Drone Eligible is set to "No" must be served by trucks only. The Drone Eligible value does not have an effect with source locations or the sites to which trucks are assigned (depots).

Status

Technology: All

Table: Customers

Internal Name: CustomerStatus

Type: Short Text (10)

One of Include, Exclude, Consider

Choose the customer status:

  • Include – This customer will be included in a simulation or optimization run.
  • Exclude – This customer will be excluded from a simulation or optimization run.
  • Consider – In optimization, the design engine will determine if this customer should be opened or closed.

Simulation will include this customer if the Type is Existing Site and exclude it if the Type is Potential Site.

Default: Include

Notes

Technology: All

Table: Customers

Internal Name: CustomerNotes

Type: Memo

Enter optional descriptive notes about the customer.

Custom 1

Technology: All

Table: Customers

Internal Name: Custom1

Type: Short Text (255)

Use this field for any additional custom information you want to records about the customer.

Custom 2

Technology: All

Table: Customers

Internal Name: Custom2

Type: Short Text (255)

Use this field for any additional custom information you want to records about the customer.

Last modified: Wednesday May 15, 2024

Is this useful?