Sites
Internal Table Name: Sites
Use this table to define the sites, such as suppliers, manufacturers and distribution centers, 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: Sites
Internal Name: SiteName
Type: Short Text (100)
Enter a unique Name to represent the site.
When using Transportation Optimization, do not use a value of "Dummy_611953" as the Name. This value is a reserved keyword.
Type
Technology: NO IO
Table: Sites
Internal Name: SiteType
Type: Short Text (25)
One of Existing Site, Potential Site
Choose the site type:
- Existing Site - Indicates this site presently exists in the supply chain.
- Potential Site - Indicates this site presently does not exist in the supply chain.
Default: Existing Site
Status | Type | Simulation |
---|---|---|
Include | Existing Site | Included |
Potential Site | Included | |
Consider | Existing Site | Included |
Potential Site | Excluded | |
Exclude | Existing Site | Excluded |
Potential Site | Excluded |
Status | Type | Optimization (Max Profit) | Optimization (Min Cost) |
---|---|---|---|
Include | Existing Site | Included | Included |
Potential Site | Included | Included | |
Consider | Existing Site | Closed if Optimal to do so | Closed if Optimal to do so |
Potential Site | Opened if Optimal | Opened if Optimal | |
Exclude | Existing Site | Excluded | Excluded |
Potential Site | Excluded | Excluded |
Address
Technology: All
Table: Sites
Internal Name: SiteAddress
Type: Short Text (100)
Enter the street address of the site. You can also use the built in geocoding to place the site at the correct Latitude and Longitude.
City
Technology: All
Table: Sites
Internal Name: SiteCity
Type: Short Text (100)
Enter the city for the site. You can also use the built in geocoding to place the site at the correct Latitude and Longitude.
State
Technology: All
Table: Sites
Internal Name: SiteState
Type: Short Text (100)
Enter the state or province of the site. You can also use the built in geocoding to place the site at the correct Latitude and Longitude.
Country
Technology: All
Table: Sites
Internal Name: SiteCountry
Type: Short Text (100)
Enter the country of the site. You can also use the built in geocoding to place the site at the correct Latitude and Longitude.
Postal Code
Technology: All
Table: Sites
Internal Name: SiteZipCode
Type: Short Text (50)
Enter the 5-digit United States or Canada postal, or zip code. You can also use the built in geocoding to place the site at the correct Latitude and Longitude.
Latitude
Technology: All
Table: Sites
Internal Name: SiteLatitude
Type: Number (Double)
Enter the Latitude of your site location. You can use the built in geocoding to populate Latitude and Longitude based on the site’s Address, City, State, Country and/or Postal Code.
If you have sites 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 site with a Latitude outside this range, those connections are not displayed on the map.
Longitude
Technology: All
Table: Sites
Internal Name: SiteLongitude
Type: Number (Double)
Enter the Longitude of your site location. You can use the built in geocoding to populate Latitude and Longitude based on the site’s Address, City, State, Country and/or Postal Code.
If you have sites 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 site with a Longitude outside this range, those connections are not displayed on the map.
Time Zone
Technology: TO
Table: Sites
Internal Name: TimeZone
Type: Short Text (50)
This field specifies the time zone for the site. 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: Sites
Internal Name: WeeklySchedule
Type: Short Text (100)
Selecting a weekly work pattern requires the site to ship and receive orders only during its specified work times during a weekly period.
Annual Schedule
Technology: S
Table: Sites
Internal Name: AnnualSchedule
Type: Short Text (100)
This is used to change weekly schedules throughout the simulation. For example, a site 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.
Tax Region
Technology: NO
Table: Sites
Internal Name: TaxRegionName
Type: Short Text (50)
Use this column to assign the site 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.
Risk Profile
Technology: NO
Table: Sites
Internal Name: RiskProfile
Type: Short Text (100)
Select the risk profile that will be applied to the site. You define the profile in the Risk Profiles table.
Organization
Technology: NO IO S
Table: Sites
Internal Name: OrganizationName
Type: Short Text (255)
Select the organization to which the site belongs.
Site Variable Cost
Technology: NO
Table: Sites
Internal Name: SiteVariableCost
Type: Short Text (100)
The cost per unit of measure as defined in the Site Variable Cost Basis. This cost is incurred for each unit of throughput at the site regardless of the product. This column supports individual cost values, not step costs.
Site Variable Cost Basis
Technology: NO
Table: Sites
Internal Name: SiteVariableCostBasis
Type: Short Text (100)
Select the unit of measure for which the Site Variable Cost is incurred. Select a Quantity, Weight or Volume unit of measure.
Fixed Operating Cost
Technology: NO IO S
Table: Sites
Internal Name: SiteFixedOperatingCost
Type: Short Text (255)
Fixed Operating Cost allows you to specify operating costs for a site. These costs can be different for different levels of throughput. In this field, you can enter a value or select the step cost that defines the relationship between operating capacities and operating cost. If you enter a cost value, note that the default throughput basis is Quantity and output will be reflected in terms of Quantity.
You create the step cost using the Step Cost Definition and Step Costs tables. For example, create a Step Cost Definition such as the following:
Name | Step Type | Step Period | Step Basis |
FixedOperating_NA | All Item | Horizon | Quantity |
And create the associated Step Cost records:
Name | Minimum Quantity | Cost |
FixedOperating_NA | 0 | 1000000 |
FixedOperating_NA | 500000 | 2000000 |
FixedOperating_NA | 750000 | 2500000 |
This step cost definition indicates that there is an initial operating cost of $1,000,000 before any product is shipped. When the capacity is more than 500,000, the operating cost increases to $2,000,000. To set a maximum capacity on the Site, enter a value for Maximum Capacity. You can use "INF" when creating the step cost using the Step Cost Definitions and Step Costs tables, or entering the value directly in Fixed Operating Cost (such as <0|85000><50000|INF>. This effectively acts as a maximum capacity and is a hard constraint. Please note that when creating a step cost in Supply Chain Guru X using the Step Cost builder on the Fixed Operating Cost value, a value of "INF" is not valid as the Cost value on the last step.
The units of measure for throughput level are determined by the following inputs in order:
- the Fixed Operating Cost in Sites.
- If a step cost is applied, the Step Basis in the Step Cost Definitions table determines the Throughput Basis.
- If a numeric value is entered for the Fixed Operating Cost, the Throughput Basis defaults to "Quantity". Keep in mind that 0 is a numeric value and will result in a basis of "Quantity". If you want to report utilization in terms of volume, you can define the Fixed Operating Cost in a format such as <0 CMTR, 10000> or enter the name of a Step Cost Definition that uses Volume.
- If there is no Fixed Operating Cost applied:
- the unit of measure applied to the Maximum Capacity column in the Sites table.
- If there is no Maximum Capacity applied:
- the unit of measure applied to the Minimum Capacity column in the Sites table.
If none of these values are defined, the Throughput Basis defaults to "Quantity".
Network Optimization uses the value in Step Period in the Step Cost Definitions table to determine how to calculate the fixed operating cost:
- If Step Period in Step Cost Definitions is set to “Horizon”, then fixed operating cost is calculated based on the total throughput level across horizon.
- If Step Period in Step Cost Definitions is set to “Period Length”, then the fixed operating cost is calculated based on the throughput level at each period .
- If Step Period in Step Cost Definitions is set to “Day”, “Week”, “Month (30 Day)”, “Quarter (91 Day)”, or “Year”, then the fixed operating cost is calculated based on the throughput level at each period while Minimum Quantity is adjusted by the ratio of the “length of each period” over the Step Period duration (Minimum Quantity * (period length/Step Period)). For single period models, the “length of each period” is the model horizon. For multi-period models, it is the length of the individual period.
In Simulation, a fixed operating cost is applied at the end of the Operating period (specified in the Capacity/Fixed Cost Period field). The accumulated throughput for the period is used to look up the cost for that same period. When capacity for the current period is reached, no more shipments will depart until the beginning of the next period. At this time, all pending shipments will be scheduled for immediate departure.
The Fixed Operating Cost is reflected in the Total Fixed Operating Cost in the Network Summary output table.
Fixed Operating Space Expansion Cost
Technology: NO
Table: Sites
Internal Name: FixedOperatingSpaceExpansionCost
Type: Short Text (100)
Enter the additional fixed operating cost that is incurred per unit of floor space if the site space is expanded. For example, assume the Fixed Operating Cost is $1 million and the space is expanded by 100,000 square feet with a Fixed Operating Space Expansion Cost of 10 per unit of floor space. The new fixed operating cost will be $2 million. Note that this cost is only incurred if the Fixed Operating Cost is defined as a single value, such as 100,000. If you define a step cost for the Fixed Operating Space Expansion Cost, it is ignored.
Initial Floor Space
Technology: NO
Table: Sites
Internal Name: Initial Floor Space
Type: Short Text (100)
Enter the starting floor space of the site. It serves as a limiting constraint with regard to the site spaces. If Min Floor Expansion and Max Floor Expansion are provided, the site floor space can be expanded as needed.
Enter a value, then optionally select an area unit of measure. If you do not select a unit of measure, the default Area Unit Of Measure from Model Settings is used.
Min Floor Expansion
Technology: NO
Table: Sites
Internal Name: MinFloorExpansion
Type: Short Text (100)
Enter the minimum expansion floor space at the site if expansion is required. This expanded space is added to the current floor space. For example, if the site space is currently 500,000 square feet and the Min Floor Expansion is 100,000 square feet, the minimum after expansion is 600,000 square feet.
Enter a value, then optionally select an area unit of measure. If you do not select a unit of measure, the default Area Unit Of Measure from Model Settings is used.
Max Floor Expansion
Technology: NO
Table: Sites
Internal Name: MaxFloorExpansion
Type: Short Text (100)
Enter the maximum expansion floor space for the site for the horizon of the model. The maximum total floor space for the site is the Initial Floor Space + Max Floor Expansion. Unless the Min Floor Expansion and Max Floor Expansion are equal, the site can expand gradually over time until it reaches the maximum allowable space. That space is then maintained through the end of the model horizon.
If you do not want floor expansion to occur at a site, enter a value of 0.
Enter a value, then optionally select an area unit of measure. If you do not select a unit of measure, the default Area Unit Of Measure from Model Settings is used.
Fixed Startup Cost
Technology: NO TO
Table: Sites
Internal Name: SiteFixedStartupCost
Type: Short Text (255)
Network Optimization: Fixed Startup Cost allows you to select a Step Cost Definition for a potential site opening at certain levels. In this field, select the step cost that defines the relationship between startup capacities and startup cost. You create the step cost using the Step Cost Definition and Step Costs tables.
For example, create a Step Cost Definition such as the following:
Name | Step Type | Step Period | Step Basis |
FixedStartup_NA | All Item | Horizon | Quantity |
And create the associated Step Cost records:
Name | Minimum Quantity | Cost |
FixedStartup_NA | 0 | 1000000 |
FixedStartup_NA | 500000 | 2000000 |
FixedStartup_NA | 750000 | 2500000 |
This step cost indicates that before any products can be shipped, an initial expenditure of $1,000,000 must be invested. In order to get capacity to more than 500,000 units, an initial expenditure of $2,000,000 is needed. For capacity to be greater than 750,000, an initial expenditure of $2,500,000 is required.
Fixed Startup Cost does not support the use of INF as a cost.
The Fixed Startup Cost is reflected in the Total Fixed Startup Cost in the Network Summary output table.
Transportation Optimization: Fixed Startup Cost is used to track the cost incurred if the site is used as a source for one or more shipments. The cost is reflected in the Total Sourcing Cost column in the Transportation Summary output table and in the Allocated Sourcing Cost column in the Shipment Output table.
Fixed Closing Cost
Technology: NO
Table: Sites
Internal Name: SiteClosingCost
Type: Number Short Text (25)
Enter the monetary cost of shutting down operations at this site. In Network Optimization, closing cost is included if a site with the type Existing Site is closed.
Expansion Only
Technology: NO
Table: Sites
Internal Name: ExpansionOnly
Type: Bit
One of Yes, No. (Actual database values are 1,0.)
If set to Yes, then the current period throughput capacity level can only be sustained or increased to a greater throughput capacity in the later periods. This applied to the Optimized Status, meaning that if the site has an Optimized Status of "Open at Level 2" in Period_001, it cannot have an Optimized Status of "Open at Level 1" in a later period. The throughput can be any value within the step level. This prevents the model from reducing the throughput to a lower capacity level (as defined in the Fixed Operating Cost field's step function) in later periods.
If set to No, the capacity levels can vary up and down period to period.
Default: No
Single Site Sourcing
Technology: NO
Table: Sites
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.
If a Make site has Single Site Sourcing set to “Yes” and that site can source from alternative suppliers, Network Optimization will select only one of them; that is, it makes a sourcing decision. If you define Flow Count Constraints to limit how the Make site is sourced, this simply restricts the flow coming from suppliers to that site. Using Single Site Sourcing is not the same as defining Flow Count Constraints in terms of solver behavior.
Order Queue Basis
Technology: S
Table: Sites
Internal Name: OrderQueueBasis
Type: Short Text (50)
One of None, Item, Quantity, Weight, Cubic, Value
Defines the basis for queue statistics gathered by Simulation. The order queue is the queue that holds orders before they are processed by the Inventory Policy. These queue statistics can be turned on and off in the Simulation Options.
Back Order Queue Basis
Technology: S
Table: Sites
Internal Name: BackOrderQueueBasis
Type: Short Text (50)
One of None, Item, Quantity, Weight, Cubic, Value
Defines the basis for queue statistics gathered by Simulation. The back order queue holds back orders that await processing based on the way the site handles back orders (Allow Back Orders, Cancel If Late, etc). These queue statistics can be turned on and off in the Simulation Options.
Inbound Shipment Queue Basis
Technology: S
Table: Sites
Internal Name: InboundShipmentQueueBasis
Type: Short Text (50)
One of None, Item, Quantity, Weight, Cubic, Value
Defines the basis for queue statistics gathered by Simulation. The inbound shipment queue holds shipments that the site is about to receive. These queue statistics can be turned on and off in Simulation Options.
Outbound Shipment Queue Basis
Technology: S
Table: Sites
Internal Name: OutboundShipmentQueueBasis
Type: Short Text (50)
One of None, Item, Quantity, Weight, Cubic, Value
Defines the basis for queue statistics gathered by Simulation. The outbound shipment queue holds shipments before they are sent to the lane queue. These queue statistics can be turned on and off in the Simulation Options.
Order Review Policy
Technology: S
Table: Sites
Internal Name: OrderQueueReviewPolicy
Type: Short Text (100)
One of FIFO, Queue Only
This is the rule that controls the sequence in which a site reviews the orders it has received. The value can be one of the following:
- FIFO – (First In First Out) The site will review the orders in the sequence they arrive. This is the default rule if the field is left blank.
- Queue Only – Only queues the orders and does not pass them on. If this value is used, the only way to remove orders from this queue would be through a custom script.
- <Script Name> – If you have defined a custom script with a Type of “Order Queue Review Policy”, it will appear in the drop-down menu for this field.
Order Review Period
Technology: NO IO S
Table: Sites
Internal Name: OrderQueueReviewPeriod
Type: Short Text (100)
This is the specified interval that the Order Review Policy executes. If you leave this value blank, the review period defaults to “Continuous” which means Simulation evaluates the order as soon as the site receives it. When entering individual values or schedules, enter a value, then select a time unit of measure. If no unit of measure is selected, the default Time Unit Of Measure from Model Settings is used.
The Order Review Period can be one of the values in the drop down list, set to one value, or assigned a schedule. The table below shows how to enter data in this field:
Value | Examples | Parameter use |
---|---|---|
No Value | The queue is evaluated as soon as any shipment enters the queue. | |
Single Value |
12 HR 1 DAY |
The queue is evaluated every interval value (for example, every 12 hours). |
Repeating Schedule | 1 DAY, 3 DAY, 2 DAY | The queue is reviewed after one day, then reviewed again 3 days after the first review, and again 2 days after the second review. The schedule is repeated upon completion. |
Offset | <16 HR>, 2 DAY | The initial review is 16 hours after the horizon start, then every 2 days after that. |
Day of Week | MON 1000, TUE 1200 |
This is used with the "Simulation" problem type. The queue is reviewed on Monday at 10:00 am and Tuesday at 12:00 pm. |
Order Review Periods themselves are dependent on the start time of Simulation. For example, assume the start time set in the Model Settings is 12:00 AM 1/1/2016, and the Order Review Period is set to 2 DAY. The queue at the lane is reviewed every two days at 12:00 AM. You can enter an offset in front of the Order Review Period to change the time the model will start reviewing. The offset is incurred only once. For example, if you want to review the queue every day at 4 PM, and the Simulation starts at 12 AM, enter an offset of 16 hours to shift the review time to 4 PM. Then, if the Order Review Period is 2 DAY, it checks every 2 days from the time to which it was offset. The format for the offset is: < "time" >
For a 16 hour offset with an Order Review Period of 2 days, you would enter: <16 HR>, 2 DAY.
Asset Search Distance
Technology: TO
Table: Sites
Internal Name: MaxEquipmentDistance
Type: Number (Double)
This field specifies the radius from the site to search for asset. For each site, all assets available within the specified radius is considered. Assets are sorted by distance (closest first), then by priority (highest priority first), and then by maximum capacity (largest first) in terms of maximum quantity, maximum weight, and maximum cubic (maximum quantity is compared first, then maximum weight, and then maximum cubic). If there is NO asset available within the specified radius, and there is a default asset type defined in the Transportation Asset table, the default asset will be used. Default asset always starts from the pool site.
Enter a value, then select a distance unit of measure. If you do not select a unit of measure, the default Distance Unit Of Measure from Model Settings is used.
Asset Search Distance is not actively used with Interleaved Optimization. The solver enumerates the routes using all the assets that it thinks are reasonable.
Fixed Service Time
Technology: TO
Table: Sites
Internal Name: FixedServiceTime
Type: Short Text (50)
This field specifies the fixed amount of service time at the site. 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.
Fixed Service Time Load
Technology: TO
Table: Sites
Internal Name: FixedServiceTimeLoad
Type: Short Text (50)
This field specifies the fixed amount of service time for loading at the site. 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: Sites
Internal Name: FixedServiceTimeUnload
Type: Short Text (50)
This field specifies the fixed amount of service time for unloading at the site. 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: Sites
Internal Name: VariableServiceTimeLoad
Type: Short Text (50)
This field specifies the variable amount of service time for loading at the site. 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: Sites
Internal Name: VariableServiceTimeUnload
Type: Short Text (50)
This field specifies the variable amount of service time for unloading at the site. 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: Sites
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.
Capital Investment Cost
Technology: NO
Table: Sites
Internal Name: CapitalInvestmentCapCost
Type: Short Text (255)
Capital Investment Cost allows you to add a cost of expansion to both potential and existing facilities. This cost is applied at the throughput level and at all previous levels. For example, you can use Capital Investment Cost to figure out if an existing site should spend an investment cost to expand. These costs can be different for different levels of throughput. In this field, select the step cost that defines the relationship between startup capacities and startup cost. You create the step cost using the Step Cost Definition and Step Costs tables.
For example, create a Step Cost Definition such as the following:
Name | Step Type | Step Period | Throughput Basis |
CapInvest_NA | All Item | Horizon | Quantity |
And create the associated Step Cost records:
Name | Minimum Quantity | Cost |
CapInvest_NA | 0 | 0 |
CapInvest_NA | 200000 | 500000 |
CapInvest_NA | 350000 | 400000 |
CapInvest_NA | 500000 | 750000 |
When going over a 200,000 Throughput Level, a Capital Investment of $500,000 is made. When going over a 350,000 Throughput Level, an additional $400,000 Capital Investment is made. At this point, a total of $900,000 has been invested.
When maintaining the same Throughput Level or lower in subsequent periods, no additional investments are made:
Period Name | Throughput Level | Total Capital Investment | Comments |
Period_01 | 150000 | 0 | |
Period_02 | 175000 | 0 | |
Period_03 | 210000 | 500000 | Throughput of 200,000 has been exceeded. No additional investment will be made unless level of 350,000 is reached. |
Period_04 | 180000 | 0 | Even though throughput is now under 200,000, there is no return of investment. |
Period_05 | 240000 | 0 | |
Period_06 | 310000 | 0 | |
Period_07 | 360000 | 400000 | Throughput of 350,000 has been exceeded. No additional investment will be made unless level of 500,000 is reached. |
Period_08 | 400000 | 0 |
You can also use the field builder to input multiple values.
Book Value
Technology: NO
Table: Sites
Internal Name: BookValue
Type: Short Text (100)
Enter the value of the site or work center at the start of each year for which you want to track book value. If you want to enter values for a number of years, you can enter them in the format:
<BookValue1|BookValue2|BookValue3>
For example, if the value is $1,000,000 in year 1, $800,000 in year 2, and $600,000 in year 3, you would enter:
<1000000|800000|600000>
or
<1M|800K|600K>
where M represents Million and K represents Thousand.
Depreciation Schedule
Technology: NO
Table: Sites
Internal Name: DepreciationSchedule
Type: Short Text (100)
Select the depreciation schedule you want to use:
- 5 Year Straight-line
- 10 Year Straight-line
Default: 10 Year Straight-line
Site Variable CO2
Technology: NO
Table: Sites
Internal Name: SiteVariableCO2
Type: Short Text (100)
The CO2 emitted per unit of measure as defined in the Site Variable CO2 Basis. The CO2 is incurred for each unit of throughput at the site regardless of the product.
Site Variable CO2 Basis
Technology: NO
Table: Sites
Internal Name: SiteVariableCO2
Select the unit of measure for which the Site Variable CO2 is incurred. Select a Quantity, Weight or Volume unit of measure.
Fixed CO2
Technology: NO IO S
Table: Sites
Internal Name: FixedCO2
Type: Short Text (255)
The fixed CO2 field allows a user to specify levels of CO2 output based on the sites throughput. You can enter a value and select a weight UOM such as LB or KG, or select a step cost. For example, create a Step Cost Definition called Fixed CO2, then create Step Cost records:
Name | Minimum Quantity | Cost |
Fixed CO2 | 0 EA | 52500 KG |
Fixed CO2 | 100000 EA | 102000 KG |
Using this step cost structure represents 52,500 KG of CO2 output from opening the site. If the site has a throughput of over 100,000 units then the CO2 output would be 102,000 KG.
In a multi-period model, the Fixed CO2 cost is incurred only in the period that the site is opened.
Fixed CO2 Space Expansion Rate
Technology: NO
Table: Sites
Internal Name: FixedCO2SpaceExpansionRate
Type: Short Text (100)
Enter the additional fixed operating CO2 that is incurred per unit of floor space if the site space is expanded. For example, assume the Fixed CO2 is 100,000 and the space is expanded by 100,000 square feet with a Fixed CO2 Space Expansion Rate of 1 per unit of floor space. The new fixed CO2 will be 200,000. Note that this rate is only incurred if the Fixed CO2 is defined as a single value, such as 100,000. If you define a step cost for the Fixed CO2 Space Expansion Rate, it is ignored.
Minimum Capacity
Technology: NO
Table: Sites
Internal Name: MinimumThroughput
Type: Short Text (100)
Enter the minimum capacity that must flow outbound from the site. For sites that are defined with Type = "Existing Site" and Status = "Include", this value acts as a hard constraint. For sites defined with Type = "Potential Site" and Status = "Consider", this is a conditional minimum (if the site is used, the Minimum Capacity is applied.). Enter a value, then optionally select a quantity, weight or volume unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used.
The units of measure for throughput level are determined by the following inputs in order:
- the Fixed Operating Cost in Sites.
- If a step cost is applied, the Step Basis in the Step Cost Definitions table determines the Throughput Basis.
- If a numeric value is entered for the Fixed Operating Cost, the Throughput Basis defaults to "Quantity". Keep in mind that 0 is a numeric value and will result in a basis of "Quantity". If you want to report utilization in terms of volume, you can define the Fixed Operating Cost in a format such as <0 CMTR, 10000> or enter the name of a Step Cost Definition that uses Volume.
- If there is no Fixed Operating Cost applied:
- the unit of measure applied to the Maximum Capacity column in the Sites table.
- If there is no Maximum Capacity applied:
- the unit of measure applied to the Minimum Capacity column in the Sites table.
If none of these values are defined, the Throughput Basis defaults to "Quantity".
Maximum Capacity
Technology: NO TO
Table: Sites
Internal Name: MaximumThroughput
Type: Short Text (100)
Network Optimization: Enter the maximum capacity that flow outbound from the site. Enter a value, then optionally select a quantity, weight or volume unit of measure. If you do not select a unit of measure, the default Quantity Unit Of Measure from Model Settings is used.
The units of measure for throughput level are determined by the following inputs in order:
- the Fixed Operating Cost in Sites.
- If a step cost is applied, the Step Basis in the Step Cost Definitions table determines the Throughput Basis.
- If a numeric value is entered for the Fixed Operating Cost, the Throughput Basis defaults to "Quantity". Keep in mind that 0 is a numeric value and will result in a basis of "Quantity". If you want to report utilization in terms of volume, you can define the Fixed Operating Cost in a format such as <0 CMTR, 10000> or enter the name of a Step Cost Definition that uses Volume.
- If there is no Fixed Operating Cost applied:
- the unit of measure applied to the Maximum Capacity column in the Sites table.
- If there is no Maximum Capacity applied:
- the unit of measure applied to the Minimum Capacity column in the Sites table.
If none of these values are defined, the Throughput Basis defaults to "Quantity".
Transportation Optimization: Maximum Capacity determines the maximum outbound quantity for sites that are sources for shipments. The Maximum Capacity must be expressed as a quantity, and it will use EA (each) as the unit of measure. The Capacity/Fixed Cost Period column does not apply for Transportation Optimization. The capacity period is the model horizon.
Capacity/Fixed Cost Period
Technology: NO IO S
Table: Sites
Internal Name: FixedCostPeriod
Type: Short Text (50)
One of Period Length, Day, Week, Month (30 Day), Quarter (91 Day), Year, Horizon.
Select the period to which the Minimum Capacity, Maximum Capacity and fixed cost fields apply.
Number Of Dock Doors
Technology: TO
Table: Sites
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: Sites
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: Sites
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 Sites 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.
Unit Production Cost
Technology: TO
Table: Sites
Internal Name: UnitProductionCost
Type: Short Text (100)
This is the cost per quantity unit incurred based on the shipments that are sourced from this site. The Unit Production Cost is reflected in the Total Variable Production Cost in the Site Sourcing Summary table. It is also reflected in the Total Sourcing Cost column in the Transportation Summary output table and in the Allocated Sourcing Cost column in the Shipment Output table.
Drone Eligible
Technology: TO
Table: Sites
Internal Name: IsDroneEligible
Type: Bit
One of Yes, No. (Actual database values are 1,0.)
Select "Yes" if the site 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: Sites
Internal Name: SiteStatus
Type: Short Text (10)
One of Include, Exclude, Consider
Choose the site status:
- Include – This site will be included in a simulation or optimization run.
- Exclude – This site 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 site if it is an existing site and exclude it if it is a potential site.
Default: Include
Notes
Technology: All
Table: Sites
Internal Name: SiteNotes
Type: Memo
Enter optional descriptive notes about the site.
Custom 1
Technology: NO IO S
Table: Sites
Internal Name: Custom1
Type: Short Text (255)
Use this field for any additional custom information you want to records about the site.
Custom 2
Technology: NO IO S
Table: Sites
Internal Name: Custom2
Type: Short Text (255)
Use this field for any additional custom information you want to records about the site.
Last modified: Wednesday May 15, 2024