Supply Chain Guru

Data Dictionary
Version 8.2
Supply Chain Guru 8.2 Data Dictionary
January 2015
Copyright © 2015 LLamasoft, Inc. All Rights Reserved.

PC*MILER and ALK are registered trademarks of ALK Technologies, Inc.

Contents

Supply Chain Guru Tables ..................................................... 1

Accessing Supply Chain Guru Tables........................................................ 1

1 Standard Tables................................................................... 3
Products ................................................................................................... 4
Name ............................................................................................. 4
Value ............................................................................................. 4
Price .............................................................................................. 4
Weight ........................................................................................... 4
Cubic ............................................................................................. 5
Type .............................................................................................. 5
Status ............................................................................................ 5
Class.............................................................................................. 5
Shelf Life ........................................................................................ 6
Lead Time Cost/Day/Unit .................................................................. 6
Max-Lead Time x Flow ...................................................................... 6
Description ..................................................................................... 6
Height ............................................................................................ 6
Length ........................................................................................... 6
Width ............................................................................................. 7
Sites ........................................................................................................ 7
Name ............................................................................................. 7
Address, City, State, Country ............................................................ 7
Postal Code..................................................................................... 7
Status ............................................................................................ 7
Type .............................................................................................. 8
Capacity Period ............................................................................... 9
Capacity Basis ................................................................................. 9
Fixed Startup <Cap,Cost> ............................................................... 9
Fixed Operating <Cap,Cost> ............................................................. 9
Closing Cost ..................................................................................10
Apply Fixed <Cap,Cost> to Horizon ..................................................10
Expansion Only ..............................................................................10
Capital Investment Basis .................................................................11
Capital Investment <Cap,Cost>........................................................11
Book Value ....................................................................................11
Depreciation Schedule .....................................................................11
Fixed CO2 <Cap,CO2> ....................................................................12
Single Site Sourcing .......................................................................12
Graphic, Graphic Color, Graphic Size .................................................12
Latitude, Longitude .........................................................................12
Weekly Schedule ...........................................................................12
 Annual Schedule ............................................................................12
Order Queue Basis .........................................................................12
Back Order Queue Basis .................................................................13
Inbound Shipment Queue Basis .......................................................13
Outbound Shipment Queue Basis .....................................................13
Order Review Policy ........................................................................13
Order Review Period........................................................................13
Time Zone .....................................................................................13
Asset Search Distance ....................................................................14
Fixed Service Time..........................................................................14
Variable Service Time ......................................................................14
Demand ..................................................................................................14
Product Name ................................................................................14
Site Name......................................................................................14
Quantity ........................................................................................14
Order Time ....................................................................................15
Order Time Formula ........................................................................15
Due Date .......................................................................................15
Due Date Formula...........................................................................16
Occurrences ...................................................................................17
Time Between Orders ......................................................................17
Pattern .........................................................................................18
Mode.............................................................................................19
Order Number ...............................................................................19
Priority .........................................................................................19
Unit Price.......................................................................................20
Unit Weight ...................................................................................20
Unit Cubic .....................................................................................20
Cancel If Late ................................................................................21
Earliest Pickup Date ........................................................................21
Earliest Pickup Date Formula ............................................................21
Latest Pickup Date ..........................................................................21
Latest Pickup Date Formula ..............................................................21
Status ...........................................................................................21
Sourcing Policies.......................................................................................21
Network Optimization Sourcing Policies ...................................................22
Safety Stock Optimization Sourcing Policies.............................................22
Simulation Sourcing Policies ..................................................................22
Sourcing Policy Fields ...........................................................................22
Site Name......................................................................................22
Product Name ................................................................................23
Sourcing Policy ...............................................................................23
Policy Parameter.............................................................................23
Source Name .................................................................................23
BOM Name.....................................................................................23
Process .........................................................................................24
 Avg Unit Cost ................................................................................24
Apply Cost To Horizon ....................................................................25
Sourcing Unit Cost .........................................................................25
Sourcing Order Cost .......................................................................25
Source Lead Time ...........................................................................25
Order Processing Time.....................................................................26
Order Processing Time Per Unit ........................................................26
Production Time..............................................................................26
Production Time Per Unit .................................................................26
Max Sourcing Distance ...................................................................26
Status ...........................................................................................26
Type .............................................................................................27
Order Lot Size ...............................................................................27
Allow Back Orders...........................................................................27
Probability of Balking.......................................................................27
Days Between Productions ...............................................................27
Guaranteed Service Time .................................................................27
Minimum Order Qty.........................................................................27
CO2 ..............................................................................................28
Graphic, Graphic Size, Graphic Color .................................................28
Network Flow Graphic, Network Flow Graphic Size, Network Flow Graphic Color28
Inventory Policies .....................................................................................28
Site Name......................................................................................28
Product Name ................................................................................29
Inventory Policy .............................................................................29
Reorder Point ................................................................................31
Reorder/Order Up To Qty ................................................................31
Review Period ................................................................................32
Status ...........................................................................................33
Initial Inventory..............................................................................33
Inbound Shipment Unit Cost.............................................................33
Inbound Shipment Cost ...................................................................33
Outbound Shipment Unit Cost...........................................................34
Outbound Shipment Cost .................................................................34
Apply Inbound Cost to Horizon .........................................................34
Apply Outbound Cost to Horizon .......................................................34
Inbound Capacity ...........................................................................34
Outbound Capacity .........................................................................34
Capacity Period ..............................................................................35
Capacity Basis ...............................................................................35
Inv Turns ......................................................................................35
Inv Carrying Cost % .......................................................................36
Min Dwell Time ...............................................................................36
Max Dwell Time ..............................................................................36
Max Inv Qty ..................................................................................36
Min Inv Qty ...................................................................................36
 Safety Stock .................................................................................37
Disposal Cost .................................................................................37
Product Value .................................................................................37
Inv Cost Other................................................................................38
Stocking Site..................................................................................38
Safety Stock Basis ..........................................................................38
Service Requirement ......................................................................38
Min and Max Safety Stock ...............................................................39
Min and Max Service Time ...............................................................39
Allow Partial Fill .............................................................................39
Forecast Name ..............................................................................39
DOS Window .................................................................................39
Consignment Cost...........................................................................39
Consignment Unit Cost ....................................................................39
Unit Delay Factor ............................................................................40
DOS Planning Lead Time .................................................................40
Delay Factor ..................................................................................40
Transportation Policies ..............................................................................40
Source Site ....................................................................................40
Destination Site ..............................................................................40
Product Name ................................................................................40
Mode.............................................................................................40
Mode Rule......................................................................................41
Parameter......................................................................................42
Transportation Policy .......................................................................43
Status ...........................................................................................45
Average Cost .................................................................................46
Cost .............................................................................................46
Cost Basis......................................................................................46
Apply Cost To Horizon ....................................................................48
Fuel Surcharge ...............................................................................48
Shipment Size ................................................................................48
Shipment Size Basis ........................................................................49
Product Class .................................................................................49
Distance ........................................................................................49
Transport Time ...............................................................................49
Asset Name ...................................................................................49
Days Between Replenishments ........................................................50
Duty .............................................................................................50
Discount Rate.................................................................................50
Min Charge ....................................................................................50
Review Period ................................................................................50
Shipment Period ............................................................................51
CO2 ..............................................................................................52
CO2 Basis ......................................................................................52
Animation Graphic .........................................................................53
 Graphic, Graphic Size, Graphic Color .................................................53
Network Flow Graphic, Network Flow Graphic Size, Network Flow Graphic Color53
Load Cost ......................................................................................53
Unit Load Cost ...............................................................................53
Unload Cost ...................................................................................53
Unit Unload Cost ............................................................................54
Load Time......................................................................................54
Unload Time...................................................................................54
Load Unit Time ...............................................................................54
Unload Unit Time ............................................................................54
Ship To ........................................................................................54
Load Resource................................................................................54
Unload Resource.............................................................................54
Auto-Release Load Resource ............................................................55
Auto-Release Unload Resource .........................................................55
Require Return Trip ........................................................................55
Return Trip Time.............................................................................55
Return Trip Cost .............................................................................55
Flow Reqt .....................................................................................55
Flow Reqt Type ..............................................................................55
Flow Reqt Basis .............................................................................55
Flow Reqt Period ............................................................................56
Lane Name ....................................................................................56
Path Name ....................................................................................56
Lane Consignment Queue Basis .......................................................56
Mode Consignment Queue Basis .......................................................56
Chance for Ambush ........................................................................56
Ambush Delay ...............................................................................56
Ambush Damage ...........................................................................56
Reorder When Destroyed ................................................................57
Unit Delay Factor ............................................................................57
Delay Factor ..................................................................................57
Minimum Shipment Quantity ............................................................57
Minimum Service Time ....................................................................57
Maximum Service Time....................................................................57
Guaranteed Service Time .................................................................57
Transportation Assets................................................................................58
Name ............................................................................................58
Units .............................................................................................58
Type .............................................................................................58
Unit Fixed Cost ...............................................................................58
Hourly Cost Cap..............................................................................58
Capacity Period ..............................................................................59
Expansion Only ..............................................................................59
Apply Fixed Cost to Horizon .............................................................59
Weight Fill Level .............................................................................59
 Weight Capacity .............................................................................59
Cubic Fill Level ...............................................................................60
Cubic Capacity................................................................................60
Quantity Fill Level ...........................................................................60
Quantity Capacity ...........................................................................61
Comp2 Quantity Capacity.................................................................61
Comp2 Weight Capacity...................................................................61
Comp2 Cubic Capacity .....................................................................61
Speed (Dist per Hour) .....................................................................61
Asset Weight ..................................................................................61
Asset Cubic ....................................................................................61
Units is Integer ..............................................................................62
Shipping Route ..............................................................................62
Unit Selection Rule .........................................................................62
Shift Pattern .................................................................................62
Asset Home Base ...........................................................................62
On Idle Behavior ............................................................................62
On Idle Location ............................................................................62
Waiting Consumer Queue Basis ........................................................63
On Available Event Handler ..............................................................63
Vulnerability Factor ........................................................................63
Max Stops Per Route .......................................................................63
Max Distance Between Stops ............................................................63
Min Distance Between Stops.............................................................63
Max Total Distance Per Route ...........................................................64
Max Time Per Route ........................................................................64
Max Waiting Time At Location...........................................................64
Is Default ......................................................................................64
Is Round Trip .................................................................................64
Max Duty Time Per Shift ..................................................................65
Max Drive Time Per Shift .................................................................65
Min Break Time Between Shifts.........................................................65
Max Drive Time Within Shift .............................................................65
Min Break Time Within Shift .............................................................65
Fixed Service Time at Stop...............................................................65
Variable Service Time at Stop ...........................................................66
Max Distance from Warehouse..........................................................66
Min Time Between Stops..................................................................66
Min Time Between Routes ................................................................66
Max Time Per Asset.........................................................................66
Max Out Of Route Percent ................................................................66
Empty Weight ................................................................................67
CO2 ..............................................................................................67
CO2 Basis ......................................................................................67
Groups ....................................................................................................67
Name ............................................................................................67
 Type .............................................................................................67
Members .......................................................................................68
Function ........................................................................................68
Graphic, Graphic Color, and Graphic Size ...........................................68
Bill of Materials.........................................................................................68
Name ............................................................................................68
Product Name ................................................................................68
Quantity ........................................................................................69
Type .............................................................................................69
Bill of Materials Example ..................................................................69
Processes ................................................................................................70
Process Name ................................................................................70
Process Step ..................................................................................70
Next Process Step ...........................................................................70
Work Center...................................................................................70
Routing Rule .................................................................................70
Routing Rule Parameter ..................................................................71
Status ...........................................................................................71
Work Time per Unit .........................................................................72
Cost Per Unit ..................................................................................72
Average Changeover Time ..............................................................72
Setup Cost.....................................................................................72
Work Time Per Order ......................................................................73
Move Time ....................................................................................73
Lot Size .........................................................................................73
Yield .............................................................................................73
Resource .......................................................................................74
Minimum Lot Size ...........................................................................74
Resource Usage Hours ....................................................................74
Graphic, Graphic Color, Graphic Size .................................................74
Work Centers ...........................................................................................74
Name ............................................................................................74
Site...............................................................................................74
Status ...........................................................................................74
Type .............................................................................................75
Capacity Basis ...............................................................................75
Capacity Period ..............................................................................75
Fixed Startup <Cap,Cost> ...............................................................75
Fixed Operating <Cap,Cost> ............................................................76
Closing Cost ...................................................................................76
Apply Fixed <Cap,Cost> To Horizon ..................................................76
Expansion Only...............................................................................76
Capital Investment Basis .................................................................77
Capital Investment <Cap,Cost>........................................................77
Book Value ....................................................................................77
Depreciation Schedule .....................................................................77
 Queue Capacity ..............................................................................78
Queue Selection Rule ......................................................................78
Planning Capacity ...........................................................................78
Changeover Table ...........................................................................78
Shift Pattern ..................................................................................78
Work Resources........................................................................................78
Name ............................................................................................78
Site Name......................................................................................78
Units .............................................................................................79
Expansion Only ..............................................................................79
Unit Fixed Cost ...............................................................................79
Hourly Cost Cap..............................................................................79
Capacity Period ..............................................................................79
Waiting Consumer Queue Basis ........................................................79
Work Center Changeovers..........................................................................79
Name ............................................................................................79
Changeover Table ...........................................................................79
Current Product ..............................................................................80
Previous Product.............................................................................80
Changeover Time............................................................................80
Production ...............................................................................................80
Production Site ...............................................................................80
Product Name ................................................................................80
Quantity ........................................................................................80
Order Time ....................................................................................80
Order Time Formula ........................................................................81
Due Date .......................................................................................81
Due Date Formula...........................................................................81
Occurrences ...................................................................................82
Time Between Orders ......................................................................82
Process Name ................................................................................82
Pattern .........................................................................................83
Order Number ...............................................................................84
Priority .........................................................................................84
Unit Weight ...................................................................................84
Unit Cubic .....................................................................................84
User Defined Customer Demand Profile........................................................84
Customer Name..............................................................................84
Product Name ................................................................................84
Period Name ..................................................................................84
Non-zero Demand Mean ..................................................................84
Non-zero Demand Std Dev...............................................................84
Inter-Demand Interval Mean ............................................................85
Demand Mean ................................................................................85
Demand Std Dev ............................................................................85
Demand Class Details......................................................................85
 Forecast Mean ................................................................................85
Forecast Std Dev ............................................................................85
Status ...........................................................................................85
User Defined Facility Demand Profile ...........................................................86
Facility Name .................................................................................86
Product Name ................................................................................86
Period Name ..................................................................................86
Non-zero Demand Mean ..................................................................86
Non-zero Demand Std Dev...............................................................86
Inter-Demand Interval Mean ............................................................86
Demand Mean ................................................................................86
Demand Std Dev ............................................................................86
Demand Class Details......................................................................87
Status ...........................................................................................87
Shipments ...............................................................................................87
Product Name ................................................................................87
Source Site ....................................................................................87
Destination Site ..............................................................................87
Quantity ........................................................................................87
Name ............................................................................................87
Order Time ....................................................................................88
Order Time Formula ........................................................................88
Due Date .......................................................................................88
Due Date Formula...........................................................................88
Occurrences ...................................................................................89
Time Between Orders ......................................................................89
Mode.............................................................................................90
Route ID........................................................................................90
Delivery Sequence ..........................................................................90
Pickup Sequence.............................................................................90
Order Number ...............................................................................90
Priority .........................................................................................90
Unit Price.......................................................................................90
Weight .........................................................................................91
Cubic ...........................................................................................91
Comp2 Quantity .............................................................................91
Comp2 Weight................................................................................91
Comp2 Cubic..................................................................................91
Cancel if Late ................................................................................91
Inter Location ID 1..........................................................................92
Inter Location ID 2..........................................................................92
LTL Time .......................................................................................92
Direct Shipping Cost........................................................................92
Desired Pickup Date ........................................................................92
Desired Delivery Date......................................................................92
Freight Class ..................................................................................93
 Max Cost .......................................................................................93
Fixed Service Time..........................................................................93
Earliest Pickup Date ........................................................................93
Earliest Pickup Date Formula ............................................................93
Latest Pickup Date ..........................................................................93
Latest Pickup Date Formula ..............................................................93
Status ...........................................................................................93
Forecasts.................................................................................................94
Name ............................................................................................94
Basis.............................................................................................94
Type .............................................................................................94
Quantities ......................................................................................94
Annual Schedules .....................................................................................95
Name ............................................................................................95
Date .............................................................................................95
State.............................................................................................95
Weekly Schedule ............................................................................95
Shipping Routes .......................................................................................95
Name ............................................................................................96
Waypoint Name ..............................................................................96
Waypoint Number ...........................................................................96
Distance ........................................................................................96
Time .............................................................................................96
Global Variables .......................................................................................96
Name ............................................................................................96
Type .............................................................................................96
Value ............................................................................................96
Dimensions ....................................................................................97
Greenhouse Gases ....................................................................................97
Max Carbon Footprint ......................................................................97
Enforce Max Carbon Footprint...........................................................97
Carbon Cost ...................................................................................97
Carbon Offset Price .........................................................................97
Optimize Carbon Offset....................................................................98
Carbon Offset Initial ........................................................................98
Carbon Offset Minimum ...................................................................98
Carbon Offset Maximum ..................................................................98
Service Requirements................................................................................98
Customer Name..............................................................................98
Product Name ................................................................................98
Source Site ....................................................................................98
Lead Time Reqt ..............................................................................99
Distance Reqt.................................................................................99
Asset & Inventory Constraints ....................................................................99
Site Name......................................................................................99
Constraint Type ..............................................................................99
 Constraint Scope ............................................................................99
Constraint Basis............................................................................ 100
Maximum .................................................................................... 100
Period ......................................................................................... 100
Transportation Paths ............................................................................... 100
Path Name................................................................................... 100
Leg Number ................................................................................. 100
Leg Latitude ................................................................................. 100
Leg Longitude .............................................................................. 100
Leg Distance ................................................................................ 100
Leg Speed ................................................................................... 100
Leg Constraint Scope .................................................................... 101
Leg Constraint Basis...................................................................... 101
Leg Constraint Maximum ............................................................... 101
Leg Constraint Period .................................................................... 101
Asset Availability .................................................................................... 101
Site Name.................................................................................... 101
Asset Name ................................................................................. 101
Available Quantity......................................................................... 101
Priority ........................................................................................ 102
Equipment ID ............................................................................... 102
Mode........................................................................................... 102
Home Site Name........................................................................... 102
Start Date/Time............................................................................ 102
Start Date/Time Formula ............................................................... 102
Carrier ID .................................................................................... 102
Dedicated Origin ID....................................................................... 103
Dedicated Destination ID ............................................................... 103
Status ......................................................................................... 103
End Date/Time ............................................................................. 103
End Date/Time Formula ................................................................. 103
Rate ..................................................................................................... 103
Rate ID ....................................................................................... 104
Asset Name ................................................................................. 104
Origin Location Group.................................................................... 104
Destination Location Group ............................................................ 104
Unit of Measurement ..................................................................... 104
Freight Class ................................................................................ 104
Carrier ........................................................................................ 104
Charge Type ................................................................................ 105
Surcharge Per Distance ................................................................. 105
Surcharge Percentage ................................................................... 105
Discount Rate............................................................................... 105
Fixed Cost ................................................................................... 105
Per Unit Cost................................................................................ 106
Unit Cost Basis ............................................................................. 106
 Minimum Cost .............................................................................. 106
Per Distance Cost.......................................................................... 106
Per Reposition Distance Cost .......................................................... 106
Per Stop Cost ............................................................................... 107
Fixed Overnight Cost ..................................................................... 107
Drive Time Cost............................................................................ 107
Service Time Cost ......................................................................... 107
Wait Time Cost ............................................................................. 108
Variable Overnight Cost ................................................................. 108
Break Time Cost ........................................................................... 108
Duty Time Cost............................................................................. 108
Status ......................................................................................... 109
Business Hours....................................................................................... 109
Site............................................................................................. 109
Sunday Open ............................................................................... 109
Sunday Closed ............................................................................. 109
Monday Open ............................................................................... 109
Monday Closed ............................................................................. 109
Tuesday Open .............................................................................. 110
Tuesday Closed ............................................................................ 110
Wednesday Open .......................................................................... 110
Wednesday Closed ........................................................................ 110
Thursday Open ............................................................................. 110
Thursday Closed ........................................................................... 110
Friday Open ................................................................................. 110
Friday Closed ............................................................................... 110
Saturday Open ............................................................................. 111
Saturday Closed ........................................................................... 111
Status ......................................................................................... 111
Transit Override ..................................................................................... 111
Origin.......................................................................................... 111
Destination .................................................................................. 111
Travel Time.................................................................................. 111
Travel Time Factor ........................................................................ 111
Distance ...................................................................................... 112
Cost............................................................................................ 112
Asset Name ................................................................................. 112
Is Symmetric ............................................................................... 112
Status ......................................................................................... 112
Relationship Constraint............................................................................ 112
Relationship ................................................................................. 113
Type A ........................................................................................ 113
ID Field A .................................................................................... 114
Type B ........................................................................................ 114
ID Field B .................................................................................... 114
Status ......................................................................................... 114
 Notes .......................................................................................... 114
Relationship Constraint Example: .................................................... 114
Periodic VRP Schedule ............................................................................. 115
Site Name.................................................................................... 115
Frequency.................................................................................... 115
Minimum Days Between................................................................. 115
Maximum Days Between ................................................................ 115
Forced Include Day(s) ................................................................... 115
Status ......................................................................................... 116

2 Multi-Time Period Tables ................................................. 117

Multi-Time Period Costs and Constraints .................................................... 117
Costs ............................................................................................... 117
Constraints ....................................................................................... 118
Periods.................................................................................................. 118
Period Name ............................................................................... 118
Period Start Date .......................................................................... 118
Products Multi-Period .............................................................................. 118
Period Name ................................................................................ 118
Name .......................................................................................... 118
Value .......................................................................................... 118
Price ........................................................................................... 119
Lead Time Cost/Day/Unit ............................................................... 119
Max-Lead Time x Flow ................................................................... 119
Sites Multi-Period.................................................................................... 119
Period Name ................................................................................ 119
Name .......................................................................................... 119
Fixed Operating <Cap,Cost> .......................................................... 119
Closing Cost ................................................................................. 120
Sourcing Policies Multi-Period ................................................................... 120
Period Name ................................................................................ 120
Site............................................................................................. 120
Product Name .............................................................................. 120
Source Name ............................................................................... 120
Avg Unit Cost ............................................................................... 120
Days Between Productions ............................................................. 121
Minimum Order Quantity................................................................ 121
Inventory Policies Multi-Period .................................................................. 121
Period Name ................................................................................ 121
Site............................................................................................. 121
Product Name .............................................................................. 122
Inbound Cost ............................................................................... 122
Outbound Cost ............................................................................. 122
Inbound Capacity.......................................................................... 122
Outbound Capacity........................................................................ 122
Inv Carrying Cost %...................................................................... 122
 Inv Turns..................................................................................... 122
Max Inv Qty ................................................................................. 123
Min Inv Qty.................................................................................. 123
Scheduled Receipt ........................................................................ 123
Safety Stock ................................................................................ 123
Disposal Cost ............................................................................... 123
Product Value ............................................................................... 124
Inv Cost Other.............................................................................. 124
Min and Max Safety Stock Qty ........................................................ 124
Min and Max Service Time.............................................................. 124
Reorder Point ............................................................................... 124
Reorder Qty ................................................................................. 125
Service Requirement .................................................................... 125
Transportation Policies Multi-Period ........................................................... 125
Period Name ................................................................................ 125
Source Site .................................................................................. 125
Destination Site ............................................................................ 125
Product Name .............................................................................. 125
Mode........................................................................................... 126
Avg Cost...................................................................................... 126
Flow Reqt .................................................................................... 126
Flow Reqt Type............................................................................. 126
Load Cost .................................................................................... 126
Unload Cost ................................................................................. 126
Return Trip Cost ........................................................................... 126
Duty Rate .................................................................................... 126
Days Between Replenishments ....................................................... 127
Minimum Shipment Quantity .......................................................... 127
Minimum Service Time .................................................................. 127
Maximum Service Time.................................................................. 127
Transportation Assets Multi-Period ............................................................ 127
Period Name ................................................................................ 127
Name .......................................................................................... 127
Units ........................................................................................... 127
Unit Fixed Cost ............................................................................. 127
Hourly Cost Cap............................................................................ 128
Processes Multi-Period ............................................................................. 128
Period Name ................................................................................ 128
Process Name .............................................................................. 128
Process Step ................................................................................ 128
Next Process Step ......................................................................... 128
Work Time Per Unit ....................................................................... 128
Average Changeover Time ............................................................. 128
Resource Usage Hours ................................................................... 129
Lot Size ....................................................................................... 129
Unit Cost ..................................................................................... 129
 Setup Cost................................................................................... 129
Yield ........................................................................................... 129
Work Centers Multi-Period........................................................................ 129
Period Name ................................................................................ 129
Name .......................................................................................... 130
Site............................................................................................. 130
Fixed Startup <Cap,Cost> ............................................................ 130
Fixed Operating <Cap,Cost> .......................................................... 130
Closing Cost ................................................................................. 130
Work Resources Multi-Period .................................................................... 131
Period Name ................................................................................ 131
Site............................................................................................. 131
Name .......................................................................................... 131
Units ........................................................................................... 131
Unit Fixed Cost ............................................................................. 131
Hourly Cost Cap............................................................................ 131

3 Constraints Tables ........................................................... 133

Flow Constraints ..................................................................................... 133
Expression Name .......................................................................... 133
Period Name ................................................................................ 134
Source Site .................................................................................. 134
Destination Site ............................................................................ 134
Product Name .............................................................................. 134
Mode........................................................................................... 134
Flow Reqt .................................................................................... 134
Flow Reqt Type............................................................................. 134
Flow Reqt Basis ............................................................................ 135
Flow Reqt Period........................................................................... 135
Status ......................................................................................... 135
Flow Count Constraints ............................................................................ 135
Period Name ................................................................................ 135
Source Site .................................................................................. 135
Destination Site ............................................................................ 135
Product Name .............................................................................. 135
Mode........................................................................................... 136
Count Value ................................................................................. 136
Count Type .................................................................................. 136
Source Aggregated ....................................................................... 136
Destination Aggregated ................................................................. 136
Product Aggregated....................................................................... 136
Mode Aggregated.......................................................................... 136
Period Aggregated ........................................................................ 136
Status ......................................................................................... 137
Inventory Constraints.............................................................................. 137
Expression Name .......................................................................... 137
 Period Name ................................................................................ 137
Site Name.................................................................................... 137
Product Name .............................................................................. 137
Inventory Reqt ............................................................................. 137
Inventory Reqt Type ..................................................................... 137
Inventory Reqt Basis ..................................................................... 138
Pre-Build Inventory ....................................................................... 138
Safety Stock ................................................................................ 138
Cycle Stock .................................................................................. 138
Turn-Estimated Inventory .............................................................. 139
Status ......................................................................................... 139
Inventory Count Constraints..................................................................... 139
Period Name ................................................................................ 139
Site Name.................................................................................... 139
Product Name .............................................................................. 139
Count Value ................................................................................. 140
Count Type .................................................................................. 140
Site Aggregated............................................................................ 140
Product Aggregated....................................................................... 140
Period Aggregated ........................................................................ 140
Status ......................................................................................... 140
Production Constraints............................................................................. 140
Expression Name .......................................................................... 140
Period Name ................................................................................ 141
Site Name.................................................................................... 141
Product Name .............................................................................. 141
Process Name .............................................................................. 141
Production Reqt ............................................................................ 141
Production Reqt Type .................................................................... 141
Production Reqt Basis .................................................................... 141
Production Reqt Period .................................................................. 142
Status ......................................................................................... 142
Production Count Constraints ................................................................... 142
Period Name ................................................................................ 142
Site Name.................................................................................... 142
Product Name .............................................................................. 142
Count Value ................................................................................. 142
Count Type .................................................................................. 142
Site Aggregated............................................................................ 142
Product Aggregated....................................................................... 143
Period Aggregated ........................................................................ 143
Status ......................................................................................... 143
Site Constraints ...................................................................................... 143
Period Name ................................................................................ 143
Site Name.................................................................................... 143
Open Sites Value .......................................................................... 143
 Open Sites Type ........................................................................... 143
Status ......................................................................................... 144
Work Center Constraints.......................................................................... 144
Period Name ................................................................................ 144
Work Center Name........................................................................ 144
Site Name.................................................................................... 144
Open Work Centers Value .............................................................. 144
Open Work Centers Type ............................................................... 144
Status ......................................................................................... 145
Greenfield Service Constraints .................................................................. 145
Constraint Name........................................................................... 145
Distance ...................................................................................... 145
Percentage Demand/Customers Served ........................................... 145
Status ......................................................................................... 145
Expression Constraints ............................................................................ 145
Expression Name .......................................................................... 145
Coefficient 1................................................................................. 145
Expression 1 ................................................................................ 146
Coefficient 2................................................................................. 146
Expression 2 ................................................................................ 146
Expression Type ........................................................................... 146
Constraint Requirement ................................................................. 146
Status ......................................................................................... 146
Expression Based Costs ........................................................................... 147
Cost Name ................................................................................... 147
Expression Name .......................................................................... 147
Fixed Cost Component................................................................... 147
Variable Cost Component............................................................... 147
Variable Cost Type ........................................................................ 147
Status ......................................................................................... 147
Open/Close Relations .............................................................................. 148
Period Name ................................................................................ 148
If Type ........................................................................................ 148
If Value ....................................................................................... 148
If Site Name ................................................................................ 148
If Work Center Name .................................................................... 148
If Condition.................................................................................. 148
Then Type ................................................................................... 148
Then Value .................................................................................. 149
Then Site Name............................................................................ 149
Then Work Center Name ................................................................ 149
Then Condition ............................................................................. 149
If And Only If ............................................................................... 149
Status ......................................................................................... 149
Sequential Objectives .............................................................................. 149
Objective ..................................................................................... 149
 Priority ........................................................................................ 149
Tolerance .................................................................................... 149
Weight ........................................................................................ 150
Site............................................................................................. 150
Source ........................................................................................ 150
Destination .................................................................................. 150
Product ....................................................................................... 150
Mode........................................................................................... 150
Period ......................................................................................... 150
Asset .......................................................................................... 150
Process ....................................................................................... 150
Expression ................................................................................... 151
Type ........................................................................................... 151
Other .......................................................................................... 151
Status ......................................................................................... 151
Decomposition Sets ................................................................................ 151
Set Name .................................................................................... 151
Status ......................................................................................... 151

4 Optimization Output Tables ............................................. 153

Network Summary ................................................................................. 154
Scenario ...................................................................................... 154
Model Run Time............................................................................ 154
Model Optimization Type................................................................ 154
Model Period In Days..................................................................... 154
Total Profit................................................................................... 155
Total Cost .................................................................................... 155
Total Revenue .............................................................................. 155
Total Fixed Startup Cost ................................................................ 155
Total Fixed Operating Cost ............................................................. 155
Safety Stock Cost ......................................................................... 155
Model Name ................................................................................. 155
Total Ending Book Value ................................................................ 155
Total Closing Cost ......................................................................... 155
Total Capital Investment ................................................................ 155
Accumulated Depreciation .............................................................. 156
Total Production Cost .................................................................... 156
Total Inbound Warehousing Cost..................................................... 156
Total Outbound Warehousing Cost................................................... 156
Total Transportation Cost............................................................... 156
Total Duty Cost ............................................................................ 156
Total Warehousing Cost ................................................................. 156
Total Sourcing Cost ....................................................................... 156
Total Transportation Asset Cost ...................................................... 156
Total Work Resource Cost .............................................................. 156
Total Expression Based Cost ........................................................... 156
 Total Unserved Demand Qty........................................................... 156
Gap Percent ................................................................................. 156
Solution Notes.............................................................................. 156
Total CO2 .................................................................................... 157
Total Carbon Cost ......................................................................... 157
Initial Carbon Offsets..................................................................... 157
Optimized Carbon Offsets .............................................................. 157
Optimized Carbon Offset Cost ......................................................... 157
Carbon Offset Price ....................................................................... 157
Total Cycle Stock .......................................................................... 157
Total Min Inventory ....................................................................... 157
Total Pre Build Inventory ............................................................... 157
Total Inv Holding Cost ................................................................... 157
Scenario ID.................................................................................. 157
Sub-Scenario ID ........................................................................... 157
Financial Summary ................................................................................. 158
Scenario ...................................................................................... 158
Period Name ................................................................................ 158
Total Profit................................................................................... 158
Present Value ............................................................................... 158
Total Cost .................................................................................... 158
Total Revenue .............................................................................. 158
Capital Investment........................................................................ 158
Depreciation................................................................................. 159
Closing Cost ................................................................................. 159
Fixed Startup Cost ........................................................................ 159
Fixed Operating Cost ..................................................................... 159
Transportation Cost....................................................................... 159
Transportation Asset Cost .............................................................. 159
Production Cost ............................................................................ 159
Sourcing Cost............................................................................... 159
Warehousing Cost ......................................................................... 159
Duty Cost .................................................................................... 159
Inventory Holding Cost .................................................................. 159
Work Resource Cost ...................................................................... 159
Carbon Cost ................................................................................. 159
Period No..................................................................................... 160
Scenario ID.................................................................................. 160
Sub-Scenario ID ........................................................................... 160
Customer Flows ...................................................................................... 160
Scenario ...................................................................................... 160
Source Name ............................................................................... 160
Customer Name............................................................................ 160
Product Name .............................................................................. 160
Mode........................................................................................... 160
Period Name ................................................................................ 160
 Demand ...................................................................................... 160
Flow Units.................................................................................... 160
Flow Weight ................................................................................. 161
Flow Cubic ................................................................................... 161
Flow Revenue............................................................................... 161
Flow Outbound Warehousing Cost ................................................... 161
Flow Transportation Cost ............................................................... 161
Flow Sourcing Cost ....................................................................... 161
Flow Duty Cost ............................................................................. 161
In Transit Inventory Holding Cost.................................................... 161
Service Hours............................................................................... 162
Service Distance ........................................................................... 162
CO2 ............................................................................................ 162
Output Flow Graphic / Output Graphic Size / Output Flow Graphic Color162
In Transit Inventory ...................................................................... 162
CO2 Cost ..................................................................................... 162
Total Cost .................................................................................... 162
Flow Lead Time Cost ..................................................................... 162
Period No..................................................................................... 162
Scenario ID.................................................................................. 163
Sub-Scenario ID ........................................................................... 163
Interfacility Flows .................................................................................. 163
Scenario ...................................................................................... 163
Source Name ............................................................................... 163
Destination Name ......................................................................... 163
Product Name .............................................................................. 163
Mode........................................................................................... 163
Period Name ................................................................................ 163
Flow Units.................................................................................... 163
Flow Weight ................................................................................. 163
Flow Cubic ................................................................................... 163
Flow Inbound Warehousing Cost ..................................................... 163
Flow Outbound Warehousing Cost ................................................... 164
Flow Transportation Cost ............................................................... 164
Flow Sourcing Cost ....................................................................... 164
Flow Duty Cost ............................................................................. 164
In Transit Inventory Holding Cost.................................................... 164
Service Hours............................................................................... 164
Service Distance ........................................................................... 164
CO2 ............................................................................................ 165
Cycle Stock .................................................................................. 165
Replenishment Frequency .............................................................. 165
In Transit Inventory ...................................................................... 165
CO2 Cost ..................................................................................... 165
Total Cost .................................................................................... 165
Flow Lead Time Cost ..................................................................... 165
 Output Flow Graphic / Output Graphic Size / Output Flow Graphic Color165
Period No..................................................................................... 165
Scenario ID.................................................................................. 166
Sub-Scenario ID ........................................................................... 166
Facility Summary.................................................................................... 166
Scenario ...................................................................................... 166
Site Name.................................................................................... 166
Site Type ..................................................................................... 166
Initial Status ................................................................................ 166
Period Name ................................................................................ 166
Optimized Status .......................................................................... 166
Throughput Level.......................................................................... 166
Throughput Basis.......................................................................... 166
Total Cost .................................................................................... 166
Total Fixed Startup Cost ................................................................ 167
Total Fixed Operating Cost ............................................................. 167
Total Closing Cost ......................................................................... 167
Total Capital Investment ................................................................ 167
Depreciation................................................................................. 167
Current Book Value ....................................................................... 167
Total Production Cost .................................................................... 167
Total Sourcing Cost ....................................................................... 167
Total Inbound Transportation Cost .................................................. 167
Total Outbound Transportation Cost ................................................ 167
Total Warehousing Cost ................................................................. 168
Total Inbound Warehousing Cost..................................................... 168
Total Outbound Warehousing Cost................................................... 168
Total Duty Cost ............................................................................ 168
Total Inventory Holding Cost .......................................................... 168
Total CO2 Cost ............................................................................. 168
Total CO2 .................................................................................... 168
Safety Stock Cost ......................................................................... 168
Throughput Quantity ..................................................................... 168
Throughput Weight ....................................................................... 169
Throughput Cubic ......................................................................... 169
Step Capacity............................................................................... 169
Step Remaining Capacity ............................................................... 169
Step Capacity Utilization ................................................................ 169
Total Capacity .............................................................................. 169
Total Remaining Capacity............................................................... 169
Total Capacity Utilization................................................................ 169
Period No..................................................................................... 170
Scenario ID.................................................................................. 170
Sub-Scenario ID ........................................................................... 170
Customer Summary ................................................................................ 170
Scenario ...................................................................................... 170
 Customer Name............................................................................ 170
Initial Status ................................................................................ 170
Period Name ................................................................................ 170
Optimized Status .......................................................................... 170
Total Revenue .............................................................................. 170
Total Flow Units ............................................................................ 170
Total Flow Weight ......................................................................... 170
Total Flow Cubic ........................................................................... 170
Period No..................................................................................... 171
Total Demand............................................................................... 171
Unserved Demand ........................................................................ 171
Scenario ID.................................................................................. 171
Sub-Scenario ID ........................................................................... 171
Productions............................................................................................ 171
Scenario ...................................................................................... 171
Site Name.................................................................................... 171
Product Name .............................................................................. 171
Period Name ................................................................................ 171
Gross Production Quantity.............................................................. 171
Net Production Quantity................................................................. 171
Byproduct Production Quantity ....................................................... 172
Total Production Quantity............................................................... 172
Production Weight......................................................................... 172
Production Cubic........................................................................... 172
Production Cost ............................................................................ 172
CO2 ............................................................................................ 172
CO2 Cost ..................................................................................... 172
Total Cost .................................................................................... 172
Period No..................................................................................... 172
Scenario ID.................................................................................. 172
Sub-Scenario ID ........................................................................... 172
Inventory ............................................................................................. 173
Scenario ...................................................................................... 173
Site Name.................................................................................... 173
Product Name .............................................................................. 173
Period Name ................................................................................ 173
Pre Build Inventory ....................................................................... 173
Period No..................................................................................... 173
Transportation Safety Stock ........................................................... 173
Transportation Safety Stock Cost .................................................... 173
Safety Inventory........................................................................... 173
Cycle Stock .................................................................................. 174
Turn Estimated Inventory .............................................................. 174
Total Inventory............................................................................. 174
Total Inv Holding Cost ................................................................... 174
Total Ending Inventory .................................................................. 174
 Total Ending Inv Holding Cost......................................................... 174
In Transit Inventory ...................................................................... 174
Scenario ID.................................................................................. 174
Sub-Scenario ID ........................................................................... 175
Aggregated Customer Demand ................................................................. 175
Scenario ...................................................................................... 175
Customer Name............................................................................ 175
Product Name .............................................................................. 175
Date ........................................................................................... 175
Aggregated Demand ..................................................................... 175
Outlier......................................................................................... 175
Adjusted Demand ......................................................................... 175
Potential Revenue ......................................................................... 175
Scenario ID.................................................................................. 175
Sub-Scenario ID ........................................................................... 176
Aggregated Customer Facing Facility Demand............................................. 176
Scenario ...................................................................................... 176
Site Name.................................................................................... 176
Product Name .............................................................................. 176
Date ........................................................................................... 176
Aggregated Demand ..................................................................... 176
Outlier......................................................................................... 176
Adjusted Demand ......................................................................... 176
Potential Revenue ......................................................................... 176
Scenario ID.................................................................................. 176
Sub-Scenario ID ........................................................................... 177
Customer Demand Profile ........................................................................ 177
Scenario ...................................................................................... 177
Customer Name............................................................................ 177
Product Name .............................................................................. 177
Period Name ................................................................................ 177
Intermittency ............................................................................... 177
Variability .................................................................................... 177
Demand Class .............................................................................. 177
Clumpiness .................................................................................. 178
Demand Class Details.................................................................... 178
Total Demand Qty......................................................................... 178
Non-zero Demand Mean ................................................................ 178
Non-zero Demand Std Dev............................................................. 178
Demand Mean .............................................................................. 178
Demand Std Dev .......................................................................... 178
Inter-Demand Interval Mean .......................................................... 178
Non-zero Demand CV2 .................................................................. 178
Min Non-zero Demand ................................................................... 178
Max Non-zero Demand .................................................................. 178
Aggregation Period Count .............................................................. 179
 Demand Count ............................................................................. 179
Outliers Count .............................................................................. 179
Potential Revenue ......................................................................... 179
Total Cost .................................................................................... 179
Total Weight ................................................................................ 179
Total Cubic................................................................................... 179
Scenario ID.................................................................................. 179
Sub-Scenario ID ........................................................................... 179
Facility Demand Profile ............................................................................ 179
Scenario ...................................................................................... 179
Site Name.................................................................................... 179
Product Name .............................................................................. 180
Period Name ................................................................................ 180
Intermittency ............................................................................... 180
Variability .................................................................................... 180
Demand Class .............................................................................. 180
Clumpiness .................................................................................. 180
Demand Class Details.................................................................... 180
Total Demand Qty......................................................................... 180
Non-zero Demand Mean ................................................................ 181
Non-zero Demand Std Dev............................................................. 181
Demand Mean .............................................................................. 181
Demand Std Dev .......................................................................... 181
Inter-Demand Interval Mean .......................................................... 181
Non-zero Demand CV2 .................................................................. 181
Aggregation Period Count .............................................................. 181
Potential Revenue ......................................................................... 181
Total Cost .................................................................................... 181
Total Weight ................................................................................ 181
Total Cubic................................................................................... 181
Scenario ID.................................................................................. 181
Sub-Scenario ID ........................................................................... 182
Inventory Policy Summary ....................................................................... 182
Scenario ...................................................................................... 182
Site Name.................................................................................... 182
Product Name .............................................................................. 182
Period Name ................................................................................ 182
Target Service Level...................................................................... 182
Service Type ................................................................................ 182
Safety Stock ................................................................................ 183
Excess Safety Stock ...................................................................... 183
Total Safety Stock......................................................................... 183
Safety Stock DOS ......................................................................... 183
Safety Stock Cost ......................................................................... 183
Safety Stock Value........................................................................ 184
Coverage ..................................................................................... 184
 Daily Demand Mean ...................................................................... 184
Daily Demand Std Dev .................................................................. 184
Demand Class Details.................................................................... 184
Recommended Policy..................................................................... 184
Policy Parameter 1 ........................................................................ 184
Policy Parameter 2 ........................................................................ 184
Expected Type 1 Service ................................................................ 185
Expected Type 2 Service ................................................................ 185
Expected Type 3 Service ................................................................ 185
Lead-Time Demand Dist ................................................................ 185
Lead-Time Demand Mean............................................................... 186
Lead-Time Demand Std Dev ........................................................... 186
Avg Backorders ............................................................................ 186
Avg Inventory .............................................................................. 186
Avg Replenishment Qty ................................................................. 186
Sourcing Type .............................................................................. 186
Scenario ID.................................................................................. 186
Sub-Scenario ID ........................................................................... 186
Inventory Policy Details ........................................................................... 187
Scenario ...................................................................................... 187
Source Name ............................................................................... 187
Destination Name ......................................................................... 187
Product Name .............................................................................. 187
Period Name ................................................................................ 187
BOM Name................................................................................... 187
Mode........................................................................................... 187
Min Replenishment Qty .................................................................. 187
Service Time ................................................................................ 187
Immediate Lead Time.................................................................... 188
Max Lead Time ............................................................................. 188
Recommended Policy..................................................................... 188
Policy Parameter 1 ........................................................................ 188
Policy Parameter 2 ........................................................................ 188
Expected Type 1 Service ................................................................ 188
Expected Type 2 Service ................................................................ 189
Expected Type 3 Service ................................................................ 189
Coverage ..................................................................................... 189
Safety Stock ................................................................................ 189
Excess Safety Stock ...................................................................... 190
Total Safety Stock......................................................................... 190
Scenario ID.................................................................................. 190
Sub-Scenario ID ........................................................................... 190
Aggregated Demand ............................................................................... 190
Scenario ...................................................................................... 190
Site Name.................................................................................... 190
Period No..................................................................................... 190
 Product Name .............................................................................. 190
Period Name ................................................................................ 190
Mode........................................................................................... 190
Total Qty ..................................................................................... 190
Total Revenue .............................................................................. 191
Demand Lead Time ....................................................................... 191
Scenario ID.................................................................................. 191
Sub-Scenario ID ........................................................................... 191
Product Summary ................................................................................... 191
Scenario ...................................................................................... 191
Product Name .............................................................................. 191
Period Name ................................................................................ 191
Total Profit................................................................................... 191
Total Cost .................................................................................... 191
Total Revenue .............................................................................. 191
Production Cost ............................................................................ 191
Transportation Cost....................................................................... 191
Warehousing Cost ......................................................................... 192
Duty Cost .................................................................................... 192
Sourcing Cost............................................................................... 192
Facility Inv Holding Cost ................................................................ 192
In Transit Inv Holding Cost............................................................. 192
Product Max Lead Time x Flow ........................................................ 192
Product Lead Time x Flow .............................................................. 192
Product Remaining Lead Time x Flow ............................................... 192
Safety Stock Cost ......................................................................... 192
Period No..................................................................................... 192
Scenario ID.................................................................................. 192
Sub-Scenario ID ........................................................................... 192
Production Process Flows ......................................................................... 193
Scenario ...................................................................................... 193
Site Name.................................................................................... 193
Product Name .............................................................................. 193
Process Name .............................................................................. 193
Work Center Name........................................................................ 193
Process Step Name ....................................................................... 193
Next Process Step Name ................................................................ 193
Period Name ................................................................................ 193
Flow Units.................................................................................... 193
Flow Weight ................................................................................. 193
Flow Cubic ................................................................................... 193
Flow Production Cost ..................................................................... 193
Flow Setup Cost............................................................................ 193
Period No..................................................................................... 194
Scenario ID.................................................................................. 194
Sub-Scenario ID ........................................................................... 194
Work Center Summary ............................................................................ 194
Scenario ...................................................................................... 194
Work Center Name........................................................................ 194
Work Center Type ......................................................................... 194
Site Name.................................................................................... 194
Initial Status ................................................................................ 194
Period Name ................................................................................ 194
Optimized Status .......................................................................... 194
Throughput Level.......................................................................... 194
Throughput Basis.......................................................................... 195
Total Cost .................................................................................... 195
Total Fixed Startup Cost ................................................................ 195
Total Fixed Operating Cost ............................................................. 195
Total Closing Cost ......................................................................... 195
Total Capital Investment ................................................................ 195
Depreciation................................................................................. 195
Current Book Value ....................................................................... 195
Total Production Cost .................................................................... 195
Throughput Quantity ..................................................................... 195
Throughput Weight ....................................................................... 195
Throughput Cubic ......................................................................... 195
Throughput Time .......................................................................... 196
Step Capacity............................................................................... 196
Step Remaining Capacity ............................................................... 196
Step Capacity Utilization ................................................................ 196
Total Capacity .............................................................................. 196
Total Remaining Capacity............................................................... 196
Total Capacity Utilization................................................................ 196
Period No..................................................................................... 196
Scenario ID.................................................................................. 197
Sub-Scenario ID ........................................................................... 197
Work Resource Summary......................................................................... 197
Scenario ...................................................................................... 197
Name .......................................................................................... 197
Max Units .................................................................................... 197
Site Name.................................................................................... 197
Period Name ................................................................................ 197
Optimized Units ............................................................................ 197
Utilization .................................................................................... 197
Fixed Cost ................................................................................... 197
Variable Cost................................................................................ 197
Remaining Units ........................................................................... 198
Period No..................................................................................... 198
Scenario ID.................................................................................. 198
Sub-Scenario ID ........................................................................... 198
Bill Of Materials Summary........................................................................ 198
 Scenario ...................................................................................... 198
Site Name.................................................................................... 198
BOM Name................................................................................... 198
Product Name .............................................................................. 198
Type ........................................................................................... 198
Period Name ................................................................................ 198
Period No..................................................................................... 199
Quantity ...................................................................................... 199
Weight ........................................................................................ 199
Cubic .......................................................................................... 199
Scenario ID.................................................................................. 199
Sub-Scenario ID ........................................................................... 199
Transportation Asset Summary................................................................. 199
Scenario ...................................................................................... 199
Name .......................................................................................... 199
Max Units .................................................................................... 199
Period Name ................................................................................ 199
Optimized Units ............................................................................ 199
Utilization .................................................................................... 199
Fixed Cost ................................................................................... 200
Variable Cost................................................................................ 200
Num Trips.................................................................................... 200
Remaining Units ........................................................................... 200
Period No..................................................................................... 200
Scenario ID.................................................................................. 200
Sub-Scenario ID ........................................................................... 200
Network Paths........................................................................................ 200
Scenario ...................................................................................... 200
Source Name ............................................................................... 201
Destination Name ......................................................................... 201
Product Name .............................................................................. 201
Mode........................................................................................... 201
Flow Units.................................................................................... 201
Flow Weight ................................................................................. 201
Flow Cubic ................................................................................... 201
Flow Inbound Warehousing Cost ..................................................... 201
Flow Outbound Warehousing Cost ................................................... 201
Flow Transportation Cost ............................................................... 201
Flow Production Cost ..................................................................... 201
Flow Duty Cost ............................................................................. 201
Intransit Inventory Holding Cost ..................................................... 201
Service Hours............................................................................... 201
Service Distance ........................................................................... 202
Customer Name............................................................................ 202
Revenue ...................................................................................... 202
Scenario ID.................................................................................. 202
 Sub-Scenario ID ........................................................................... 202
Network Paths Summary ......................................................................... 202
Scenario ...................................................................................... 202
Product Name .............................................................................. 202
Customer Name............................................................................ 202
Demand Qty ................................................................................ 202
Customer Flow Qty ....................................................................... 202
Facility1 (, Facility2, etc.)............................................................... 203
Mode1 (, Mode2, etc.) ................................................................... 203
Transportation Cost....................................................................... 203
Warehousing Cost ......................................................................... 203
Production Cost ............................................................................ 203
Sourcing Cost............................................................................... 203
Duty Cost .................................................................................... 203
Intransit Inventory Holding Cost ..................................................... 203
Service Distance ........................................................................... 203
Service Hours............................................................................... 203
Weight Qty .................................................................................. 203
Cubic Qty .................................................................................... 203
Total Cost .................................................................................... 203
Revenue ...................................................................................... 204
Scenario ID.................................................................................. 204
Sub-Scenario ID ........................................................................... 204
Facility Status Decision History ................................................................. 204
Scenario ...................................................................................... 204
Integer Solution ........................................................................... 204
Site Name.................................................................................... 204
Period Name ................................................................................ 204
Period No..................................................................................... 204
Objective Value ............................................................................ 204
Gap (%) ...................................................................................... 204
Solution Time ............................................................................... 204
Scenario ID.................................................................................. 205
Sub-Scenario ID ........................................................................... 205
Greenfield Summary ............................................................................... 205
Scenario ...................................................................................... 205
Total Customers ........................................................................... 205
Total Greenfield Facilities ............................................................... 205
Total Existing Facilities .................................................................. 205
Total Cost .................................................................................... 205
Scenario ID.................................................................................. 205
Sub-Scenario ID ........................................................................... 205
Greenfield Service................................................................................... 205
Scenario ...................................................................................... 206
Service Level................................................................................ 206
Input Service Distance................................................................... 206
 Input Service Percentage ............................................................... 206
Total Customers Served................................................................. 206
Total Demand Served .................................................................... 206
Percentage Customers Served ........................................................ 206
Percentage Demand Served ........................................................... 206
Constraint Basis............................................................................ 206
Scenario ID.................................................................................. 206
Sub-Scenario ID ........................................................................... 206
Greenfield Facilities ................................................................................. 207
Scenario ...................................................................................... 207
Greenfield Facility ......................................................................... 207
Greenfield Latitude........................................................................ 207
Greenfield Longitude ..................................................................... 207
Closest City Latitude ..................................................................... 207
Closest City Longitude ................................................................... 207
Distance ...................................................................................... 207
City ............................................................................................ 207
State........................................................................................... 207
Country ....................................................................................... 207
Output Type................................................................................. 208
Greenfield Status .......................................................................... 208
Throughput Level.......................................................................... 208
Scenario ID.................................................................................. 208
Sub-Scenario ID ........................................................................... 208
Greenfield Flows ..................................................................................... 208
Scenario ...................................................................................... 208
Source Name ............................................................................... 208
Customer Name............................................................................ 208
Flow Units.................................................................................... 209
Distance ...................................................................................... 209
Flow Times Distance...................................................................... 209
Scenario ID.................................................................................. 209
Sub-Scenario ID ........................................................................... 209
Vehicle Route Optimization Summary ........................................................ 209
Scenario ...................................................................................... 209
Model Run Time............................................................................ 209
Total Transportation System Cost ................................................... 209
Total Route Cost ........................................................................... 209
Total Direct Shipping Cost .............................................................. 209
Total Fixed Asset Cost ................................................................... 209
Total Routes................................................................................. 210
Total Assets ................................................................................. 210
Total Stops .................................................................................. 210
Total In Transit Stops .................................................................... 210
Total Distance .............................................................................. 210
Total Reposition Distance ............................................................... 210
 Total Time ................................................................................... 210
Total Input Quantity ...................................................................... 210
Total Output Quantity.................................................................... 210
Total Input Weight ........................................................................ 210
Total Output Weight ...................................................................... 210
Total Input Cubic .......................................................................... 210
Total Output Cubic ........................................................................ 211
Total Segments ............................................................................ 211
Total Deliveries............................................................................. 211
Total Unrouted Shipments.............................................................. 211
Total Invalid Shipments ................................................................. 211
Model Name ................................................................................. 211
Optimization Type......................................................................... 211
Scenario ID.................................................................................. 211
Sub-Scenario ID ........................................................................... 211
Assets ................................................................................................... 212
Scenario ...................................................................................... 212
Asset ID ...................................................................................... 212
Asset Name ................................................................................. 212
Equipment ID ............................................................................... 212
Equipment Availability ID ............................................................... 212
Location ...................................................................................... 212
Start Date Time ............................................................................ 212
End Date Time.............................................................................. 212
Total Asset Route Cost................................................................... 212
Horizon Fixed Asset Cost................................................................ 212
Total Route Cost ........................................................................... 212
Total Distance .............................................................................. 212
Reposition Distance....................................................................... 212
Total Stops .................................................................................. 213
In Transit Stops............................................................................ 213
Total Weight ................................................................................ 213
Total Cubic................................................................................... 213
Total Qty ..................................................................................... 213
Total Time ................................................................................... 213
Duty Time.................................................................................... 213
Drive Time ................................................................................... 213
Reposition Time ............................................................................ 213
Service Time ................................................................................ 213
Wait Time .................................................................................... 213
Break Time .................................................................................. 214
Overnight Time............................................................................. 214
Total Gap Time Between Routes...................................................... 214
Max Out Of Route Percent .............................................................. 214
Avg Out Of Route Percent .............................................................. 214
Start Date Time Local .................................................................... 214
 End Date Time Local...................................................................... 214
Asset Utilization............................................................................ 214
Number of Routes ......................................................................... 215
Scenario ID.................................................................................. 215
Sub-Scenario ID ........................................................................... 215
Routes .................................................................................................. 215
Scenario ...................................................................................... 215
Route ID...................................................................................... 215
Asset Name ................................................................................. 215
Pool Site ...................................................................................... 215
Total Cost .................................................................................... 215
Direct Shipping Cost...................................................................... 215
Fixed Cost ................................................................................... 215
Unit Cost ..................................................................................... 216
Total Stops .................................................................................. 216
In Transit Stops............................................................................ 216
Total Distance .............................................................................. 216
Reposition Distance....................................................................... 216
Multi-Stop Savings ........................................................................ 216
Selected Mode Cost....................................................................... 216
Selected Mode .............................................................................. 216
Total Weight ................................................................................ 216
Total Cubic................................................................................... 216
Total Qty ..................................................................................... 216
Start Date Time ............................................................................ 216
End Date Time.............................................................................. 217
VRP Number ................................................................................ 217
Break Time .................................................................................. 217
Trans Mode ID.............................................................................. 217
Total Time ................................................................................... 217
Duty Time.................................................................................... 217
Drive Time ................................................................................... 217
Reposition Time ............................................................................ 217
Wait Time .................................................................................... 217
Service Time ................................................................................ 217
Overnight Time............................................................................. 217
Equipment ID ............................................................................... 218
Carrier ID .................................................................................... 218
Start Date Time Local .................................................................... 218
End Date Time Local...................................................................... 218
Lock Type .................................................................................... 218
Out Of Route Percent .................................................................... 218
Max Qty ...................................................................................... 218
Max Cubic.................................................................................... 218
Max Weight.................................................................................. 218
Comp2 Quantity ........................................................................... 219
 Comp2 Weight.............................................................................. 219
Comp2 Cubic................................................................................ 219
Duty Cost .................................................................................... 219
Drive Time Cost............................................................................ 219
Service Time Cost ......................................................................... 219
Break Cost ................................................................................... 219
Overnight Cost ............................................................................. 219
Wait Cost..................................................................................... 219
Total Stop Cost............................................................................. 220
Total Distance Cost ....................................................................... 220
Total Per Reposition Distance Cost .................................................. 220
Total Surcharge ............................................................................ 220
CO2 Emission ............................................................................... 220
Delivered Stops ............................................................................ 220
Delivered Qty ............................................................................... 220
Delivered Weight .......................................................................... 220
Delivered Cubic ............................................................................ 220
Pickup Stops ................................................................................ 220
Pickup Qty ................................................................................... 220
Pickup Weight .............................................................................. 220
Pickup Cubic ................................................................................ 221
Asset ID ...................................................................................... 221
Asset Sequence ID ........................................................................ 221
Route Utilization ........................................................................... 221
Scenario ID.................................................................................. 221
Sub-Scenario ID ........................................................................... 221
Stops .................................................................................................... 221
Scenario ...................................................................................... 221
Stop ID ....................................................................................... 221
Route ID...................................................................................... 221
Sequence ID ................................................................................ 221
Stop Type .................................................................................... 222
Site Name.................................................................................... 222
Arrive Date Time .......................................................................... 222
Delivery Date Time ....................................................................... 222
Leave Date Time........................................................................... 222
Qty ............................................................................................. 222
Weight ........................................................................................ 222
Cubic .......................................................................................... 222
Pickup Cubic ................................................................................ 222
Pickup Weight .............................................................................. 222
Pickup Qty ................................................................................... 222
Delivered Cubic ............................................................................ 222
Delivered Weight .......................................................................... 222
Delivered Qty ............................................................................... 222
Remaining Cubic ........................................................................... 223
 Remaining Weight......................................................................... 223
Remaining Qty ............................................................................. 223
Longitude .................................................................................... 223
Latitude....................................................................................... 223
VRP Number ................................................................................ 223
Arrive Date Time Local .................................................................. 223
Delivery Date Time Local ............................................................... 223
Leave Date Time Local................................................................... 223
Shipment ID ................................................................................ 223
Scenario ID.................................................................................. 223
Sub-Scenario ID ........................................................................... 223
Segments .............................................................................................. 224
Scenario ...................................................................................... 224
VRP Number ................................................................................ 224
Route ID...................................................................................... 224
Start Date Time ............................................................................ 224
End Date Time.............................................................................. 224
Distance ...................................................................................... 224
Drive Time ................................................................................... 224
Carry Shipments........................................................................... 224
Start Date Time Local .................................................................... 224
End Date Time Local...................................................................... 224
Segment ID ................................................................................. 224
Sequence ID ................................................................................ 224
Start Stop ID ............................................................................... 224
Start Site..................................................................................... 225
End Stop ID ................................................................................. 225
End Site ...................................................................................... 225
CO2 Emission ............................................................................... 225
Scenario ID.................................................................................. 225
Sub-Scenario ID ........................................................................... 225
Route Breaks ......................................................................................... 225
Scenario ...................................................................................... 225
Route Break ID............................................................................. 225
Break Start Date Time ................................................................... 225
Break End Date Time..................................................................... 225
Break Start Date Time Local ........................................................... 225
Break End Date Time Local............................................................. 226
Route Event Type ......................................................................... 226
Route ID...................................................................................... 226
Stop ID ....................................................................................... 226
Overnight Cost ............................................................................. 226
Break Cost ................................................................................... 226
Segment ID ................................................................................. 226
Scenario ID.................................................................................. 226
Sub-Scenario ID ........................................................................... 226
Input Shipments..................................................................................... 227
Scenario ...................................................................................... 227
Shipment ID ................................................................................ 227
Customer ID ................................................................................ 227
Source Site .................................................................................. 227
Destination Site ............................................................................ 227
Product Name .............................................................................. 227
Priority ........................................................................................ 227
Qty ............................................................................................. 227
Weight ........................................................................................ 227
Cubic .......................................................................................... 227
Earliest Delivery Date .................................................................... 227
Latest Delivery Date...................................................................... 227
Comp2 Quantity ........................................................................... 228
Comp2 Weight.............................................................................. 228
Comp2 Cubic................................................................................ 228
Earliest Pickup Date ...................................................................... 228
Latest Pickup Date ........................................................................ 228
Order ID ...................................................................................... 228
Pool Site ...................................................................................... 228
Trans Mode ID.............................................................................. 228
Route ID...................................................................................... 228
Sequence ID ................................................................................ 228
Scenario ID.................................................................................. 228
Sub-Scenario ID ........................................................................... 228
Unrouted Shipments ............................................................................... 229
Scenario ...................................................................................... 229
Name .......................................................................................... 229
Product Name .............................................................................. 229
Source Site .................................................................................. 229
Destination Site ............................................................................ 229
Weight ........................................................................................ 229
Cubic .......................................................................................... 229
Qty ............................................................................................. 229
Direct Shipping Cost...................................................................... 229
VRP Number ................................................................................ 229
Comp2 Quantity ........................................................................... 229
Comp2 Weight.............................................................................. 229
Comp2 Cubic................................................................................ 230
Scenario ID.................................................................................. 230
Sub-Scenario ID ........................................................................... 230
Invalid Shipments................................................................................... 230
Scenario ...................................................................................... 230
Shipment Name............................................................................ 230
Product Name .............................................................................. 230
Qty ............................................................................................. 230
 Weight ........................................................................................ 230
Cubic .......................................................................................... 230
Reason ........................................................................................ 230
VRP Number ................................................................................ 230
Source Site .................................................................................. 230
Destination Site ............................................................................ 231
Scenario ID.................................................................................. 231
Sub-Scenario ID ........................................................................... 231
Delivered Shipments ............................................................................... 231
Scenario ...................................................................................... 231
Shipment ID ................................................................................ 231
Route ID...................................................................................... 231
Source Site .................................................................................. 231
Destination Site ............................................................................ 231
Pickup Date Time .......................................................................... 231
Delivery Date Time ....................................................................... 231
Product Name .............................................................................. 231
Weight ........................................................................................ 231
Cubic .......................................................................................... 232
Qty ............................................................................................. 232
Pickup Stop ID ............................................................................. 232
Delivery Stop ID ........................................................................... 232
VRP Number ................................................................................ 232
Pickup Date Time Local.................................................................. 232
Delivery Date Time Local ............................................................... 232
Visit Sequence ID ......................................................................... 232
Comp2 Quantity ........................................................................... 232
Comp2 Weight.............................................................................. 232
Comp2 Cubic................................................................................ 232
Cost To Route .............................................................................. 232
Allocated Cost .............................................................................. 233
Direct Shipping Cost...................................................................... 233
Mode Suggestion .......................................................................... 233
Direct Shipping Confidence %......................................................... 233
Scenario ID.................................................................................. 233
Sub-Scenario ID ........................................................................... 233
PVRP Delivered Shipments ....................................................................... 233
Scenario ...................................................................................... 234
Shipment ID ................................................................................ 234
PVRP Shipment ID ........................................................................ 234
Route ID...................................................................................... 234
Source Site .................................................................................. 234
Destination Site ............................................................................ 234
Pickup Date Time .......................................................................... 234
Delivery Date Time ....................................................................... 234
Product Name .............................................................................. 234
 Weight ........................................................................................ 234
Cubic .......................................................................................... 234
Qty ............................................................................................. 234
Pickup Stop ID ............................................................................. 234
Delivery Stop ID ........................................................................... 235
VRP Number ................................................................................ 235
Pickup Date Time Local.................................................................. 235
Delivery Date Time Local ............................................................... 235
Visit Sequence ID ......................................................................... 235
Comp2 Qty .................................................................................. 235
Comp2 Weight.............................................................................. 235
Comp2 Cubic................................................................................ 235
Cost To Route .............................................................................. 235
Allocated Cost .............................................................................. 235
Direct Shipping Cost...................................................................... 235
Direct Shipping Confidence %......................................................... 236
Mode Suggestion .......................................................................... 236
ScenarioID................................................................................... 236
Sub-Scenario ID ........................................................................... 236
Asset Summary ...................................................................................... 236
Scenario ...................................................................................... 236
Asset Availability ID ...................................................................... 236
Site Name.................................................................................... 236
Asset Name ................................................................................. 237
Assets Available............................................................................ 237
Assets Used ................................................................................. 237
ScenarioID................................................................................... 237
Sub-ScenarioID ............................................................................ 237
Multi-Objective Details ............................................................................ 237
Scenario ...................................................................................... 237
Run Time..................................................................................... 237
Origin Scenario............................................................................. 237
Objective1 ................................................................................... 237
Objective2 ................................................................................... 237
Objective1 Value........................................................................... 238
Objective2 Value........................................................................... 238
Total Cost .................................................................................... 238
Total Profit................................................................................... 238
CO2 ............................................................................................ 238
Solution Time ............................................................................... 238
Scenario ID.................................................................................. 238
Expression Summary .............................................................................. 238
Scenario ...................................................................................... 238
Expression Name .......................................................................... 238
Expression Basis ........................................................................... 238
Expression Value .......................................................................... 239
 Scenario ID.................................................................................. 239
Sub-Scenario ID ........................................................................... 239
Expression Based Cost Summary .............................................................. 239
Scenario ...................................................................................... 239
Cost Name ................................................................................... 239
Cost Value ................................................................................... 239
Expression Name .......................................................................... 239
Expression Value .......................................................................... 239
Fixed Component.......................................................................... 240
Variable Component ...................................................................... 240
Scenario ID.................................................................................. 240
Sub-Scenario ID ........................................................................... 240
Constraint Summary ............................................................................... 240
Scenario ...................................................................................... 240
Constraint.................................................................................... 240
Expression ................................................................................... 240
Site............................................................................................. 240
Source ........................................................................................ 241
Destination .................................................................................. 241
Product ....................................................................................... 241
Mode........................................................................................... 241
Period ......................................................................................... 241
Period Number ............................................................................. 241
Asset .......................................................................................... 241
Process ....................................................................................... 241
Other .......................................................................................... 241
Range ......................................................................................... 241
Constraint Type ............................................................................ 241
Constraint Activity ........................................................................ 241
Constraint Slack ........................................................................... 242
Constraint Requirement ................................................................. 242
Diagnostic Excess ......................................................................... 242
Diagnostic Deficit .......................................................................... 242
Scenario ID.................................................................................. 242
Sub-Scenario ID ........................................................................... 242

5 Simulation Output Tables ................................................ 243

Network Summary .................................................................................. 244
Scenario ...................................................................................... 244
Model Name ................................................................................. 244
Num Reps.................................................................................... 244
Period Length Days ....................................................................... 244
Total Profit................................................................................... 244
Total Cost .................................................................................... 244
Total Revenue .............................................................................. 244
Total Fixed Operating Cost ............................................................. 244
 Total Fixed Startup Cost ................................................................ 244
Total Inbound Warehousing Cost..................................................... 244
Total Outbound Warehousing Cost................................................... 245
Total Production Cost .................................................................... 245
Total Transportation Cost............................................................... 245
Total Inventory Carrying Cost ......................................................... 245
Avg Fill Rate................................................................................. 245
Avg Fill Qty Rate........................................................................... 245
Total CO2 .................................................................................... 245
Total Carbon Offsets...................................................................... 245
Total Carbon Offset Cost ................................................................ 245
Carbon Offset Price ....................................................................... 245
Avg Ready Rate ............................................................................ 245
Period ......................................................................................... 246
Total Demand............................................................................... 246
Lost Demand................................................................................ 246
Lost Revenue ............................................................................... 246
Total Duty Cost ............................................................................ 246
Transportation CO2 ....................................................................... 246
Production CO2 ............................................................................ 246
Fixed CO2.................................................................................... 246
Avg On Time Rate ......................................................................... 246
Avg On Time Qty Rate ................................................................... 246
Rep............................................................................................. 246
Scenario ID.................................................................................. 246
Sub-Scenario ID ........................................................................... 247
Site Summary ........................................................................................ 247
Scenario ...................................................................................... 247
Site Name.................................................................................... 247
Total Cost .................................................................................... 247
Throughput Level.......................................................................... 247
Throughput Basis.......................................................................... 247
Inventory Carrying Cost................................................................. 247
Average Inventory Value................................................................ 247
Maximum Inventory Value ............................................................. 247
Average Inventory Cubic................................................................ 247
Maximum Inventory Cubic.............................................................. 248
Inventory Turns............................................................................ 248
Total Fixed Operating Cost ............................................................. 248
Total Outbound Transportation Cost ................................................ 248
Total Production Cost .................................................................... 248
Avg On Time Rate ......................................................................... 248
Avg On Time Qty Rate ................................................................... 248
Avg Fill Rate................................................................................. 248
Avg Fill Qty Rate........................................................................... 248
Total Inbound Warehousing Cost..................................................... 248
 Total Outbound Warehousing Cost................................................... 248
Outbound Flow ............................................................................. 249
Inbound Flow ............................................................................... 249
Period ......................................................................................... 249
Avg Ready Rate ............................................................................ 249
Outbound Weight.......................................................................... 249
Inbound Weight ............................................................................ 249
Outbound Cubic ............................................................................ 249
Inbound Cubic .............................................................................. 249
COGS (Cost of Goods Sold) ............................................................ 249
Total CO2 .................................................................................... 249
Scenario ID.................................................................................. 249
Sub-Scenario ID ........................................................................... 249
Rep............................................................................................. 249
Asset Summary ...................................................................................... 250
Scenario ...................................................................................... 250
Name .......................................................................................... 250
Available Time.............................................................................. 250
Utilized Time ................................................................................ 250
Setup Time .................................................................................. 250
Scheduled Down Time ................................................................... 250
Unscheduled Down Time ................................................................ 250
Average Units Utilized ................................................................... 250
Maximum Units Utilized ................................................................. 250
Total Utilization ............................................................................ 250
Period ......................................................................................... 251
Scenario ID.................................................................................. 251
Sub-Scenario ID ........................................................................... 251
Rep............................................................................................. 251
Work Center Summary ............................................................................ 251
Scenario ...................................................................................... 251
Site Name.................................................................................... 251
Name .......................................................................................... 251
Available Time.............................................................................. 251
Utilized Time ................................................................................ 251
Setup Time .................................................................................. 251
Scheduled Down Time ................................................................... 252
Unscheduled Down Time ................................................................ 252
Average Queue Depth ................................................................... 252
Maximum Queue Depth ................................................................. 252
Total Utilization ............................................................................ 252
Throughput Level.......................................................................... 252
Throughput Basis.......................................................................... 252
Total Fixed Operating Cost ............................................................. 252
Outbound Flow ............................................................................. 252
Outbound Weight.......................................................................... 252
 Outbound Cubic ............................................................................ 252
Period ......................................................................................... 252
Scenario ID.................................................................................. 252
Sub-Scenario ID ........................................................................... 253
Rep............................................................................................. 253
Work Resource Summary......................................................................... 253
Scenario ...................................................................................... 253
Site Name.................................................................................... 253
Name .......................................................................................... 253
Available Time.............................................................................. 253
Utilized Time ................................................................................ 253
Average Units Utilized ................................................................... 253
Maximum Units Utilized ................................................................. 253
Total Utilization ............................................................................ 253
Period ......................................................................................... 253
Destroyed Time ............................................................................ 254
Scenario ID.................................................................................. 254
Sub-Scenario ID ........................................................................... 254
Rep............................................................................................. 254
Site Details ............................................................................................ 254
Scenario ...................................................................................... 254
Product Name .............................................................................. 254
Site Name.................................................................................... 254
Initial Inventory Units.................................................................... 254
Average Inventory Units ................................................................ 254
Ending Inventory Units .................................................................. 254
Minimum Inventory Units ............................................................... 254
Maximum Inventory Units .............................................................. 255
Average Back Order Units .............................................................. 255
Maximum Back Order Units ............................................................ 255
Average In Transit Units ................................................................ 255
Maximum In Transit Units .............................................................. 255
Average Replenishment Quantity .................................................... 255
Period ......................................................................................... 255
Average Order Cycle Time.............................................................. 255
Maximum Order Cycle Time............................................................ 255
On Time Rate ............................................................................... 255
On Time Qty Rate ......................................................................... 255
Cycle Service Level ....................................................................... 256
Fill Rate ....................................................................................... 256
Fill Qty Rate ................................................................................. 256
Ready Rate .................................................................................. 256
Ending Orders .............................................................................. 256
Ending Order Qty .......................................................................... 256
Total Order Qty ............................................................................ 256
Total Shipped Qty ......................................................................... 256
 Total Shipped Value ...................................................................... 256
Total Shipped Weight .................................................................... 256
Total Shipped Cubic ...................................................................... 256
Ending Back Orders....................................................................... 256
Ending Back Order Qty .................................................................. 257
Total Back Order Qty ..................................................................... 257
Total Downstream Demand ............................................................ 257
Lost Downstream Demand ............................................................. 257
Lost Downstream Demand Revenue ................................................ 257
Scenario ID.................................................................................. 257
Sub-Scenario ID ........................................................................... 257
Rep............................................................................................. 257
Customer Details .................................................................................... 257
Scenario ...................................................................................... 257
Customer Name............................................................................ 257
Product Name .............................................................................. 258
Average Order Cycle Time.............................................................. 258
Maximum Order Cycle Time............................................................ 258
On Time Rate ............................................................................... 258
On Time Qty Rate ......................................................................... 258
Ending Orders .............................................................................. 258
Ending Order Qty .......................................................................... 258
Total Orders................................................................................. 258
Total Order Qty ............................................................................ 258
Period ......................................................................................... 258
Total Demand............................................................................... 259
Total Revenue .............................................................................. 259
Lost Demand................................................................................ 259
Lost Revenue ............................................................................... 259
Scenario ID.................................................................................. 259
Sub-Scenario ID ........................................................................... 259
Rep............................................................................................. 259
Network Flows........................................................................................ 259
Scenario ...................................................................................... 259
Source Name ............................................................................... 259
Destination Name ......................................................................... 259
Product Name .............................................................................. 259
Mode........................................................................................... 259
Flow Units.................................................................................... 260
Flow Weight ................................................................................. 260
Flow Cubic ................................................................................... 260
Flow Transportation Cost ............................................................... 260
Flow Count................................................................................... 260
CO2 ............................................................................................ 260
Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic Color260
Period ......................................................................................... 260
 Flow Revenue............................................................................... 260
Flow Outbound Warehousing Cost ................................................... 260
Flow Duty Cost ............................................................................. 260
Flow Total Cost............................................................................. 260
Rep............................................................................................. 261
Scenario ID.................................................................................. 261
Sub-Scenario ID ........................................................................... 261
Interfacility Shipment Flows ..................................................................... 261
Scenario ...................................................................................... 261
Source Name ............................................................................... 261
Destination Name ......................................................................... 261
Product Name .............................................................................. 261
Mode........................................................................................... 261
Flow Units.................................................................................... 261
Flow Weight ................................................................................. 261
Flow Cubic ................................................................................... 261
Flow Revenue............................................................................... 261
Flow Inbound Warehousing Cost ..................................................... 262
Flow Outbound Warehousing Cost ................................................... 262
Flow Transportation Cost ............................................................... 262
Flow Duty Cost ............................................................................. 262
Flow Intransit Inventory Holding Cost .............................................. 262
Flow Total Cost............................................................................. 262
CO2 ............................................................................................ 262
Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic Color262
Period ......................................................................................... 262
Rep............................................................................................. 262
Scenario ID.................................................................................. 262
Sub-Scenario ID ........................................................................... 263
Customer Shipment Flows........................................................................ 263
Scenario ...................................................................................... 263
Source Name ............................................................................... 263
Customer Name............................................................................ 263
Product Name .............................................................................. 263
Mode........................................................................................... 263
Flow Units.................................................................................... 263
Flow Weight ................................................................................. 263
Flow Cubic ................................................................................... 263
Flow Revenue............................................................................... 263
Flow Outbound Warehousing Cost ................................................... 263
Flow Transportation Cost ............................................................... 264
Flow Duty Cost ............................................................................. 264
Flow Total Cost............................................................................. 264
CO2 ............................................................................................ 264
Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic Color264
Period ......................................................................................... 264
 Rep............................................................................................. 264
Scenario ID.................................................................................. 264
Sub-Scenario ID ........................................................................... 264
Interfacility Order Flows .......................................................................... 264
Scenario ...................................................................................... 264
Order Source................................................................................ 265
Order Destination ......................................................................... 265
Product Name .............................................................................. 265
Orders......................................................................................... 265
Order Qty .................................................................................... 265
Period ......................................................................................... 265
Flow Sourcing Cost ....................................................................... 265
Flow Consignment Cost ................................................................. 265
Rep............................................................................................. 265
Scenario ID.................................................................................. 265
Sub-Scenario ID ........................................................................... 265
Customer Order Flows ............................................................................. 265
Scenario ...................................................................................... 266
Order Source................................................................................ 266
Order Destination ......................................................................... 266
Product Name .............................................................................. 266
Orders......................................................................................... 266
Order Qty .................................................................................... 266
Period ......................................................................................... 266
Flow Sourcing Cost ....................................................................... 266
Flow Consignment Cost ................................................................. 266
Rep............................................................................................. 266
Scenario ID.................................................................................. 266
Sub-Scenario ID ........................................................................... 266
Bill of Materials Summary ........................................................................ 267
Scenario ...................................................................................... 267
Site Name.................................................................................... 267
BOM Name................................................................................... 267
Product Name .............................................................................. 267
Type ........................................................................................... 267
Quantity ...................................................................................... 267
Weight ........................................................................................ 267
Cubic .......................................................................................... 267
Period ......................................................................................... 267
Rep............................................................................................. 267
Scenario ID.................................................................................. 267
Sub-Scenario ID ........................................................................... 267
Customer Summary ................................................................................ 268
Scenario ...................................................................................... 268
Customer Name............................................................................ 268
Avg On Time Rate ......................................................................... 268
 Avg On Time Qty Rate ................................................................... 268
Inbound Flow Units ....................................................................... 268
Inbound Flow Weight..................................................................... 268
Inbound Flow Cubic....................................................................... 268
Total Revenue .............................................................................. 268
Lost Revenue ............................................................................... 268
Total Demand............................................................................... 268
Lost Demand................................................................................ 268
Period ......................................................................................... 269
Rep............................................................................................. 269
Scenario ID.................................................................................. 269
Sub-Scenario ID ........................................................................... 269
Production Summary............................................................................... 269
Scenario ...................................................................................... 269
Site Name.................................................................................... 269
Product Name .............................................................................. 269
Production Lots............................................................................. 269
Production Qty ............................................................................. 269
Production Weight......................................................................... 269
Production Cubic........................................................................... 269
Production Value........................................................................... 269
Production Cost ............................................................................ 270
Period ......................................................................................... 270
Rep............................................................................................. 270
Scenario ID.................................................................................. 270
Sub-Scenario ID ........................................................................... 270
Product Summary ................................................................................... 270
Scenario ...................................................................................... 270
Product Name .............................................................................. 270
Total Profit................................................................................... 270
Total Cost .................................................................................... 270
Total Revenue .............................................................................. 270
Production Cost ............................................................................ 271
Transportation Cost....................................................................... 271
Warehousing Cost ......................................................................... 271
Total CO2 .................................................................................... 271
Total Demand............................................................................... 271
Lost Demand................................................................................ 271
Lost Revenue ............................................................................... 271
Period ......................................................................................... 271
Rep............................................................................................. 271
Scenario ID.................................................................................. 271
Sub-Scenario ID ........................................................................... 271
Process Summary ................................................................................... 271
Scenario ...................................................................................... 272
Site Name.................................................................................... 272
 Product Name .............................................................................. 272
Process Name .............................................................................. 272
Process Step Name ....................................................................... 272
Input Weight ................................................................................ 272
Input Cubic .................................................................................. 272
Input Quantity.............................................................................. 272
Yield Quantity............................................................................... 272
Production Cost ............................................................................ 272
Period ......................................................................................... 272
Rep............................................................................................. 272
Scenario ID.................................................................................. 272
Sub-Scenario ID ........................................................................... 273
Network Paths........................................................................................ 273
Scenario ...................................................................................... 273
Customer Name............................................................................ 273
Product Name .............................................................................. 273
Demand Qty ................................................................................ 273
Flow Unit Qty ............................................................................... 273
Weight Qty .................................................................................. 273
Cubic Qty .................................................................................... 273
Facility1 ...................................................................................... 273
Mode1 ......................................................................................... 273
Transportation Cost1 ..................................................................... 274
Facility Fixed Cost1 ....................................................................... 274
Transportation Cost....................................................................... 274
Scenario ID.................................................................................. 274
Sub-Scenario ID ........................................................................... 274
Production Transactions........................................................................... 274
Scenario ...................................................................................... 274
Site Name.................................................................................... 274
Product Name .............................................................................. 274
Quantity ...................................................................................... 274
Time ........................................................................................... 274
Work Center Name........................................................................ 274
Production Cost ............................................................................ 275
Production Time............................................................................ 275
Internal Order Number .................................................................. 275
User Defined Order Number ........................................................... 275
Scenario ID.................................................................................. 275
Sub-Scenario ID ........................................................................... 275
Rep............................................................................................. 275
Demand Transactions .............................................................................. 275
Scenario ...................................................................................... 275
Site Name.................................................................................... 275
Product Name .............................................................................. 275
Quantity ...................................................................................... 275
 Time ........................................................................................... 276
Scenario ID.................................................................................. 276
Sub-Scenario ID ........................................................................... 276
Rep............................................................................................. 276
Shipment Transactions ............................................................................ 276
Scenario ...................................................................................... 276
Source Name ............................................................................... 276
Destination Name ......................................................................... 276
Product Name .............................................................................. 276
Quantity ...................................................................................... 276
Time ........................................................................................... 276
CO2 ............................................................................................ 276
Weight ........................................................................................ 277
Cubic .......................................................................................... 277
Mode........................................................................................... 277
Shipment Number......................................................................... 277
Transportation Cost....................................................................... 277
Duty ........................................................................................... 277
Due Date ..................................................................................... 277
Transportation Policy ..................................................................... 277
Asset Name ................................................................................. 277
Asset Unit .................................................................................... 277
Internal Order Number .................................................................. 277
User Defined Order Number ........................................................... 277
Scenario ID.................................................................................. 277
Sub-Scenario ID ........................................................................... 278
Rep............................................................................................. 278
Shipment Mileage Log ............................................................................. 278
Scenario ...................................................................................... 278
Source Site .................................................................................. 278
Destination Site ............................................................................ 278
Shipment ID ................................................................................ 278
Departure Date ............................................................................ 278
Arrival Date ................................................................................. 278
Distance ...................................................................................... 278
Asset Name ................................................................................. 279
Asset Unit Number ........................................................................ 279
Container ID ................................................................................ 279
AVERAGE..................................................................................... 279
SIMPLEAVERAGE .......................................................................... 279
STDDEV ...................................................................................... 279
MIN ............................................................................................ 279
MAX ............................................................................................ 279
CURRENT..................................................................................... 279
TOTAL ......................................................................................... 279
Period ......................................................................................... 279
 Scenario ID.................................................................................. 279
Sub-Scenario ID ........................................................................... 279
Rep............................................................................................. 280
Shipment Handling Log............................................................................ 280
Scenario ...................................................................................... 280
Site............................................................................................. 280
Shipment ID ................................................................................ 280
Start Date.................................................................................... 280
Handling Time .............................................................................. 280
Operation .................................................................................... 280
Asset Name ................................................................................. 280
Asset Unit Number ........................................................................ 280
Consignment Name ....................................................................... 280
Quantity ...................................................................................... 280
Work Resource Name .................................................................... 280
Internal Order Number .................................................................. 280
User Defined Order Number ........................................................... 281
AVERAGE..................................................................................... 281
SIMPLEAVERAGE .......................................................................... 281
STDDEV ...................................................................................... 281
MIN ............................................................................................ 281
MAX ............................................................................................ 281
CURRENT..................................................................................... 281
TOTAL ......................................................................................... 281
Period ......................................................................................... 281
Scenario ID.................................................................................. 281
Sub-Scenario ID ........................................................................... 281
Rep............................................................................................. 281
Order Report.......................................................................................... 281
Scenario ...................................................................................... 282
Replication Number ....................................................................... 282
Order Processed Date .................................................................... 282
Source Site .................................................................................. 282
Destination Site ............................................................................ 282
Product Name .............................................................................. 282
Internal Order Number .................................................................. 282
User Defined Order Number ........................................................... 282
Original Order Quantity.................................................................. 282
Quantity Previously Filled ............................................................... 282
Quantity Filled .............................................................................. 282
Quantity Backordered.................................................................... 282
Order Created Date ....................................................................... 282
Order Due Date ............................................................................ 283
Scenario ID.................................................................................. 283
Sub-Scenario ID ........................................................................... 283
Error Log ............................................................................................... 283
 Scenario ...................................................................................... 283
Error ........................................................................................... 283
Scenario ID.................................................................................. 283
Sub-Scenario ID ........................................................................... 283
Rep............................................................................................. 283

Index................................................................................ 285
 Supply Chain Guru Tables

Supply Chain Guru uses a number of input and output tables to hold your
model data:
 Standard Tables – These are standard input tables for single time
period data.
 Multi-Time Period Tables – These are input tables for multi-time period
data.
 Constraints Tables – These are input tables that support constraints on
various types of data, such as Flow, Inventory, Production and
Greenfield Service.
 Optimization Output Tables – These are output tables that contain the
data generated by Network Optimization, Greenfield Analysis, and
Vehicle Route Optimization.
 Simulation Output Tables – These are output tables that contain the
data generated by Simulation.

Accessing Supply Chain Guru Tables

These groups of tables can be selected from the Project Navigator:

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 1

 Supply Chain Guru Tables

2 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Chapter 1

Standard Tables

The following are Supply Chain Guru Standard Tables:

 Products
 Sites
 Demand
 Sourcing Policies
 Inventory Policies
 Transportation Policies
 Transportation Assets
 Groups
 Bill of Materials
 Processes
 Work Centers
 Work Resources
 Work Center Changeovers
 Production
 User Defined Customer Demand Profile
 User Defined Facility Demand Profile
 Shipments
 Forecasts
 Annual Schedules
Network Optimization:
 Greenhouse Gases
 Service Requirements
Simulation:
 Shipping Routes
 Global Variables
 Asset & Inventory Constraints
 Transportation Paths

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 3

Chapter 1 Standard Tables

Vehicle Route Optimization:

 Asset Availability
 Rate
 Business Hours
 Transit Override
 Relationship Constraint
 Periodic VRP Schedule

Products
Name
(Name)
Type: Text
Enter a unique Name to represent product or a Stock Keeping Unit (SKU) number.

Value
Type: Number
Enter a monetary value for each unit. The Value field is used to calculate the inventory
investment and inventory holding costs. It is incorporated in the following formula:
Inv holding cost = Avg Inv * Product value * Inv Carrying Cost % * Length of Time in
Inventory
In Network Optimization, the Product Value in the Inventory Policies table overrides the
Product Value in the Products table.
In Simulation, the Product Value in the Products table is always used. The Inv Carrying
Cost % in the Inventory Policies is used if populated; otherwise, the Inv Carrying Cost %
in Model Options is used.
The Value is reflected in the Total Inv Holding Cost in the Network Summary output table.

Price
Type: Number
Enter the revenue generated from the sale of a single unit of this product. The product
price is used to calculate revenue statistics.
Each time a customer order for this product is filled, it is registered as a sale. Revenue is
determined by the number of units sold multiplied by the price of the product. In case a
Unit Price is specified on the Demand table, in that case the Price in the Products table is
over-ridden. When no Unit Price is specified on the Demand table, the Price field on the
Product table is the default for Revenue calculations.

Weight
Type: Number
Enter the weight for a single unit of your product. Weight is used to calculate truck fill
levels and weight-based transportation costs. You can use the English or metric system,
just be consistent throughout your model. Do not specify a unit of measure in this field
(e.g., 10 ton), just the numeric value.

4 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Products

Cubic
Type: Number
Enter the cubic volume for each unit of product. Cubic is used to calculate truck fill levels
and cubic-based transportation costs. It is also used to calculate site space utilization
statistics. You can use the English or metric system, just be consistent throughout your
model. Do not enter a unit of measure, just the numeric value.

Type
Type: Special
The type field enables you to define the allowable quantity values for this product. Many
products must use specific quantity values. For example, if you are modeling a product
such as "airplane", it would not make sense to have ½ of an airplane. The Type can be
one of:
 Discrete – This value is typically used for products that are produced in integer
quantities. However, if you use the product in a Bill of Materials record, the Quantity
specified in the Bill Of Materials record is the smallest discrete value that can be used.
For example, if the Quantity of a Discrete component is .5, the quantity used cannot
be other than a multiple of .5. Network Optimization uses fractional values to satisfy
demand, even for products defined as Discrete.
 Continuous – Use this value for products that can have fractional values, such as
liquid chemicals.
The Expected Type <x> Service values in the Safety Stock Optimization output tables are
affected by the Product Type. The expected service values will be the same as the Target
Service Level for Continuous products, and greater than or equal to the Target Service
Level for Discrete products. The Type is used when Supply Chain Guru creates the final
results, by rounding up the Safety Stock value to an integer if the Type is Discrete.
If the field is left empty, then it is assumed to be Continuous.

Status
Type: Special
The status field allows you to specify whether a product is included or excluded from a
model simulation or optimization.
If the field is left blank, the product is assumed to be included.
If the product status is set to "Exclude", none of the policies that use this product will be
built, including inventory, sourcing, product-specific transportation policies, and
processes.

Class
Type: Number
Select the shipping class. Only use this field if your shipping policy is Less Than Truckload
(LTL). The National Motor Freight Classification Blue Book designates the shipping
category classification numbers.
The shipping class determines shipping costs for any product shipped as LTL.
The default is 77.5.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 5

Chapter 1 Standard Tables

Shelf Life
Type: Number
As a product moves through the supply chain, its relative age is tracked and compared to
the Shelf Life. The Shelf Life field in the Products table determines the maximum number
of periods in which a product is able to satisfy demand. A common use is to limit how
early products can be pre-built. The value must be a non-negative integer. The Shelf Life
is an index into the period in which the product will expire. For example, if your model
uses monthly periods and the shelf life for a product is about 60 days (2 months), you
define the Shelf Life as 2. A value of 1 indicates the product expires within the current
period. If you enter 0, you are effectively saying that the product never expires (the
same as if Shelf Life is null).
Initial inventory is treated like it came into the system in the period before the model
starts (that is, period 0). If the Shelf Life value in the Products table is set to 1, the initial
inventory is already expired and never used. If the Shelf Life is set to 2, initial inventory
can be used to fulfill demand in period 1, but not 2, 3, and so on.

Note: The Hard Constraints tab of Optimization Options includes a Shelf Life constraint
that you can use to force Shelf Life to be a hard constraint during optimization.

If Shelf Life is defined for a product in the Products table, you cannot define Dwell
Time in the Inventory Policies table for the same product at any site.

Lead Time Cost/Day/Unit

Type: Number
Use this field to specify the cost of 1 day of lead time per unit of product. It is used in lead
time optimization. This field accepts positive values.

Max-Lead Time x Flow

Type: Number
Use this field to specify the maximum limit of the flow times the lead time. It is used in
lead time optimization.

Description
Type: Text
Use this field to provide an optional description of the product.

Height
Type: Number
Use this field to provide an optional product height.

Note: This field is hidden by default. You can display the field using Column Options.

Length
Type: Number
Use this field to provide an optional product length.

6 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sites

Note: This field is hidden by default. You can display the field using Column Options.

Width
Type: Number
Use this field to provide an optional product width.

Note: This field is hidden by default. You can display the field using Column Options.

Sites
Name
Type: Text
Enter a unique Name to represent the site.

Address, City, State, Country

Type: Text
Enter the location of the site. You will notice the Field Guru in-cell button after the City,
State and Country fields. This is an feature that will use the built in geocoder to correctly
place the site at the correct Latitude and Longitude.
The Geocoding of sites uses a "GeoDatabase" set in Model Options (F3, or in the Model
Data tab). The default database contains most of the main cities throughout the world as
well as all of the Airport codes.

Note: For sites outside the United States, leave the state field blank.

Postal Code
Type: Text
Enter the 5-digit United States or Canada postal, or zip code. To change the postal code,
click in this field and type the desired postal code. This value can also be geocoded
without any additional information.
Input of a Canadian Postal Code will not generate an accurate geocoding result unless the
default geocoding database is selected. For more information about geocoding, see
Geocoding.

Status
Type: Text
Choose the site status:
 Include - This site is to be included in a simulation or optimization run.
 Exclude - This site is to be excluded in a simulation or optimization run.
 Consider - In optimization, the software will recommend this site be opened or closed.
Simulation will include this site if it is an existing facility and exclude it if it is a potential
facility.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 7

Chapter 1 Standard Tables

Note: Sites can only open once and close once in a model. This is regardless of whether
Expansion Only is set to Yes or No. A “Closed” site is a site that does not allow
product to flow in or out. If a site that is currently holding inventory is closed, the
inventory is held for the remaining periods in the model and will incur any
associated holding costs.

Type
Type: Text
Choose the site state:
 Existing Facility - Indicates this site presently exists in the supply chain.
 Potential Facility - Indicates this site presently does not exist in the supply chain.
 Customer - Indicates a site where demand is initiated. Customer sites introduce
demand into the supply chain and generate revenue. They do not carry inventory,
ship to other sites, or produce any products. If you would like to do of those things
then your site type can not be a customer.

Status Type Simulation

Include Existing Facility Included

Potential Facility Included

Customer Included

Consider Existing Facility Included

Potential Facility Excluded

Customer Included

Exclude Existing Facility Excluded

Potential Facility Excluded

Customer Excluded

Optimization (Max Optimization (Min

Status Type
Profit) Cost)

Include Existing Facility Included Included

Potential Facility Included Included

Customer Included Included

Consider Existing Facility Closed if Optimal to do so Closed if Optimal to do

so

Potential Facility Opened if Optimal Opened if Optimal

Customer Only served if profitable Not served

8 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sites

Exclude Existing Facility Excluded Excluded

Potential Facility Excluded Excluded

Customer Excluded Excluded

Capacity Period
Type: Text
Choose the period (Day, Week, Month (30 day), Quarter (91 day), or Year) over which the
cost numbers in the Fixed Operating <Cap,Cost> field is applied. If no Capacity Period is
specified, the default is the model period length.
The Fixed Startup <Cap,Cost> is applied over the model horizon.
In a simulation the Capacity Period property defines the interval/frequency with which
costs are calculated and reported.

Capacity Basis
Type: Text
Choose the unit measure you will use to determine the dimension of shipment capacity in
the Startup <Cap,Cost> and Operating <Cap,Cost> fields. Valid choices are:
 Quantity
 Weight
 Cubic
In Simulation, the Capacity Basis property specifies the manner which throughput is
accumulated and reported, which can be any of unit quantity, weight, or cubic volume.
Whatever the basis for throughput the accumulated value is used to look up the fixed
operating cost for the period.

Fixed Startup <Cap,Cost>

Type: Pairs
Fixed Startup allows you to specify a step cost for a potential facility opening at certain
levels. In this field, enter a function that defines the relationship between startup
capacities and startup cost. The function is specified by a series of coordinates. The first
number in the coordinate indicates shipment capacity. The second number indicates the
startup cost.
For example, an entry of <0,1000000> <500000,2000000> <750000, 2500000>
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.
The Fixed Startup Cost is reflected in the Total Fixed Startup Cost in the Network
Summary output table.

Fixed Operating <Cap,Cost>

Type: Pairs
Fixed Operating allows you to specify operating costs for a facility. These costs can be
different for different levels of throughput. In this field, enter a function that defines the
relationship between operating capacity and operating costs. The function is specified by

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 9

Chapter 1 Standard Tables

a series of coordinate pairs. The first number in the pair indicates throughput capacity.
The second number indicates operating cost.
For example, an entry of <0, 1000000> <500000, 2000000> <15000000, INF>
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. The maximum capacity is 15,000,000 as indicated with a cost of infinite
(INF). If the cost is INF for a certain capacity level, that capacity is considered as a hard
constraint.

Note: When you specify INF on fixed operating cost field, you are limiting the throughput
(sum of outflows from that site). This is not a constraint on the production
capacity at the site.

If you create capacity values that do not start with 0, the result is a conditional minimum
constraint for throughput at the site. For example, if you enter
<100,175000><250000,INF> for the Fixed Operating value on a site, if the site is used,
it must have throughput of at least 100 units.
In Simulation, a fixed operating cost is applied at the end of the Operating period
(specified in the Capacity 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.

Closing Cost
Type: Number
Enter the monetary cost of shutting down operations at this site. In an optimization,
closing cost will be included if a site with the type Existing Facility is closed.

Apply Fixed <Cap,Cost> to Horizon

Type: Yes/No
In this field, select Yes or No from the drop down menu. When it is set to Yes, the
specified Cost and Capacity structure for the Fixed Operating Costs is applied over the
total length of the optimization. When periods are specified in the Multi-Time Periods
Table, and this field is set to No, the Cost and Capacity structure will be applied to each
individual period.

Expansion Only
Type: Yes/No
If set to Yes, then the site cannot close after it has already opened. This prevents the
model from opening a new site for excess capacity in one period, then closing it for the
next.

Note: Sites can only open once and close once in a model. This is regardless of whether
Expansion Only is set to Yes or No. A “Closed” site is a site that does not allow
product to flow in or out. If a site that is currently holding inventory is closed, the

10 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sites

inventory is held for the remaining periods in the model and will incur any
associated holding costs.

Capital Investment Basis

Type: Special
Select the basis to be used for the Capital Investment <Cap,Cost> value(s). Select one
of:
 Quantity
 Weight
 Cubic

Capital Investment <Cap,Cost>

Type: Pairs
Capital Investment 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 to figure out if an existing facility should spend
an investment cost to expand. Enter one or more sets of capacity and capital investment
pairs in the format:
<capacity1,cost1><capacity2,cost2><capacity3,cost3>
For example, if the capital investment for throughput over 1000 is 500, and 250 for
throughput over 5000, you would enter:
<1000,500><5000,250>
You can also use the field guru to input multiple values.

Note: INF is not allowed as a value for Cost. Use the Fixed Operating <Cap,Cost> field if
you want to constrain the capacity.

Book Value
Type: Special
Enter the value of the facility 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
Type: Special
Select the depreciation schedule you want to use:

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 11

Chapter 1 Standard Tables

 5 Year Straight-line
 10 Year Straight-line

Fixed CO2 <Cap,CO2>

Type: Pairs
The fixed CO2 field allows a user to specify levels of CO2 output based on the sites
throughput. This can be entered as a step function similar to site fixed operating costs.
Therefore, entering <0, 5000000><100000, 10000000> would represent 5000000 kg of
CO2 output from opening the site. If the site has a throughput of over 100,000 then the
CO2 output would be 10,000,000 kg.

Single Site Sourcing

Type: Yes/No
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, Supply Chain Guru 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 the Optimization Options window.

Graphic, Graphic Color, Graphic Size

In these fields, choose how you want your site to appear on the Layout map. Graphic Size
is measured in points.

Note: It will be helpful to be consistent when choosing how your sites appear on the
Layout map. For example, you could choose to represent all existing facilities with
a red triangle 10 points in size and all potential facilities with blue squares 8 points
in size.

Latitude, Longitude
Type: Number
In these number fields, enter the latitude and longitude of your site location. The
software will fill in the latitude and longitude if you use the Field Guru in-cell button
located in the City, State, Country, or Postal Code field.

Weekly Schedule
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
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.

Order Queue Basis

Type: Special

12 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sites

Defines the basis for queue statistics gathered by the Simulation Server. The order queue
is the queue that holds orders before they are processed by the Inventory Policy. These
queue statistics can be toggled on and off in the Simulation Options panel.

Back Order Queue Basis

Type: Special
Defines the basis for queue statistics gathered by the Simulation Server. 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 toggled on
and off in the Simulation Options panel.

Inbound Shipment Queue Basis

Type: Special
Defines the basis for queue statistics gathered by the Simulation Server. The inbound
shipment queue holds shipments that the site is about to receive. These queue statistics
can be toggled on and off in the Simulation Options panel.

Outbound Shipment Queue Basis

Type: Special
Defines the basis for queue statistics gathered by the Simulation Server. The outbound
shipment queue holds shipments before they are sent to the lane queue. These queue
statistics can be toggled on and off in the Simulation Options panel.

Order Review Policy

Type: Special
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

Type: Special
This is the specified interval that the Order Review Policy executes. If you leave this
value blank, Supply Chain Guru defaults to “Continuous” which means Supply Chain Guru
evaluates the order as soon as the site receives it.

Time Zone
Type: Text
This field specifies the time zone for the site. It is used to determine the local time for
route scheduling.
Vehicle Route Optimization uses a default of EST if no Time Zone is provided.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 13

Chapter 1 Standard Tables

Asset Search Distance

Type: Number
This field specifies the range from a warehouse to search for equipment. For each
warehouse, all equipment available within the specified radius is considered. Equipment is
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 equipment available within the specified radius, and there
is a default equipment type defined in the Transportation Asset table, the default
equipment will be used. Default equipment always starts from the warehouse.

Fixed Service Time

Type: Number
This field specifies the fixed amount of service time at the site. It is applicable to warehouse, pickup
and delivery locations. The default unit for time fields is DAY.

Variable Service Time

Type: Number
This field specifies the variable amount of service time at the site. The total amount of
service time at the site = fixedServiceTime + (varServiceTime x total Quantity/or Weight/
or Cubic). The unit applied to the variable time is determined by the KeyUOM setting in
the Vehicle Route Optimization parameters. The default for this unit is Quantity. The
default unit for time fields is DAY.

Demand
Product Name
Type: Text
Enter the product that is being demanded.

Site Name
Type: Text
Enter the customer site that is requesting the product.
A Tip: You can select your Products and Sites from the drop-down list fields or enter the
first few letters of the product or site and Supply Chain Guru will find the first match from
the drop-down list.

Quantity
Type: Number or Distribution
If a probability distribution is specified, the quantity will be randomly selected each time
the demand requirement occurs in simulation. For optimization, the mean of the
distribution will be used as the demand amount. Use the field Guru for help inputting the
correct distribution.

14 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Demand

Order Time
Type: Date
The order time is the date the order is placed if only one Occurrence is scheduled (see
Occurrences below). In Simulation, if more than one occurrence is scheduled, then the
Order Time field becomes the time of the first Order, and the Time Between Orders field
dictates the next time an order occurs.
Optimization currently only supports orders with one Occurrence.

Note: If you populate both Order Time and Order Time Formula, Supply Chain Guru uses
Order Time Formula when running Optimization or Simulation.

Safety Stock Optimization uses Order Time or Order Time Formula (not Due Date or Due
Date Formula) to do Demand Analysis.
For Vehicle Route Optimization, if you are using Demand to define your shipments, this
field specifies the start of the delivery time window for the shipment. The end of the
delivery time window is defined using Due Date.
If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Order Time Formula

Type: Text
Specify a number or distribution that defines when the order is placed. In Simulation, if
more than one occurrence is scheduled, then the Order Time Formula field becomes the
time of the first Order, and the Time Between Orders field dictates the next time an order
occurs.
Optimization currently only supports orders with one Occurrence.

Note: If you populate both Order Time and Order Time Formula, Supply Chain Guru uses
Order Time Formula when running Optimization or Simulation.

Safety Stock Optimization uses Order Time or Order Time Formula (not Due Date or Due
Date Formula) to do Demand Analysis.
If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Due Date
Type: Date
Used to specify the date by which an order must be filled.
In Simulation, the order cycle time is the period of time between the occurrence of the
order (Order Time or Order Time Formula) and the time the order was satisfied (arrives
at the customer and fulfills demand). When the order arrives at the customer, the current
time is checked and compared to the Due Date or Due Date Formula. This is how the
software determines if a shipment is on time or late.
In Optimization, the Due Date or Due Date Formula field can be used as a constraint. If
you populate the Due Date or Due Date Formula field for records in an optimization, and
then check "Classify Demand By Due Date" in the Optimization Options Constraints tab, it
will act as a constraint for flow on the customer flow (the last echelon of the model). The

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 15

Chapter 1 Standard Tables

demand with due date constraints will not be able to use any mode or lane that is longer
than the specified Due Date or Due Date Formula. For this feature, you must specify
dates in both the Order Time and Due Date fields and not populate the Order Time
Formula or Due Date Formula fields. If the Order Time Formula is set to a number, such
as 0 or 2, this feature will not work.

Note: If you populate both Due Date and Due Date Formula, Supply Chain Guru uses
Due Date Formula when running Optimization or Simulation.

For Vehicle Route Optimization, if you are using Demand to define your shipments, this
field specifies the end of the delivery time window for the shipment. The start of the
delivery time window is defined using Order Time.
If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Due Date Formula

Type: Number or Distribution
Used to specify when an order must be filled.
In Simulation, the order cycle time is the period of time between the occurrence of the
order (Order Time or Order Time Formula) and the time the order was satisfied (arrives
at the customer and fulfills demand). When the order arrives at the customer, the current
time is checked and compared to the Due Date or Due Date Formula. This is how the
software determines if a shipment is on time or late.
In Optimization, the Due Date or Due Date Formula field can be used as a constraint. If
you populate the Due Date or Due Date Formula field for records in an optimization, and
then check "Classify Demand By Due Date" in the Optimization Options Constraints tab, it
will act as a constraint for flow on the customer flow (the last echelon of the model). The
demand with due date constraints will not be able to use any mode or lane that is longer
than the specified Due Date or Due Date Formula. For this feature, you must specify
dates in both the Order Time and Due Date fields and not populate the Order Time
Formula or Due Date Formula fields. If the Order Time Formula is set to a number, such
as 0 or 2, this feature will not work.

Note: The default Due Date Formula unit is DAY. If you do not enter a time unit, the
software assumes the Due Date Formula is measured in days.

If Due Date Formula is left Blank, the software assumes the order is due
immediately when demand occurs.

For example:

If you want the Due Date to occur: Enter

As soon as an order is placed 0 or leave blank

1 day after the order is placed 1Day

Set the actual day it is due Use the Due Date field

For Vehicle Route Optimization, if you are using Demand to define your shipments, this
field specifies the number of days to add to the start of the delivery time window to
calculate the end of the delivery time window. The start of the delivery time window is

16 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Demand

defined using Order Time. If you enter a distribution, this is applied as a Mean, similar to
how distributions are applied in Network Optimization.
If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Occurrences
Type: Number or Text
Enter how many times this demand requirement will occur. A demand must occur at least
once. When you enter a number greater than one, demand will occur multiple times.
For example:

If you want the Occurrences to take place: Enter

1 time 1 or leave blank

10 times 10

As long as the simulation runs INF

Note: If you are defining demand by using a pattern, you do not need to enter the
Occurrences or Time Between Orders. The pattern specifies this for you. The
software will ignore data entered in these fields.

Time Between Orders

Type: Time
For Simulation, the Time Between Orders field is used to specify the time between
multiple orders. In this number/time/distribution, enter how much time must pass
between each recurring demand. For example, Time Between Orders can be 24 HR,
meaning that orders recur every 24 hours for as many occurrences specified.
For Optimization, the Time Between Orders is ignored. The total demand based on
Quantity and Occurrences is put into the period for which the demand is specified based
on the Order Time or Order Time Formula field.

Note: You must enter data in this field if the Occurrences are greater than 1. If you do
not enter Time Between Orders and demand recurs, the software will assume that
this demand happens once a day.

Time Between Orders examples are in the following table.

If you want: Enter

Recurring daily demand Time Between Orders: 1 DAY or

leave blank

Occurrences: INF

Randomly occurring demand according to a Time Between Orders: T(1,3,4)

triangular distribution DAY

Occurrences: INF

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 17

Chapter 1 Standard Tables

Note: If you are defining demand by using a pattern, you do not need to enter a data in
the Occurrences or Time Between Orders fields. The pattern specifies this for you.

Pattern
Type: Text
Allows patterns of demand to be distributed over periods of time. Pattern represents a
predefined set of occurrences, instead of a single occurrence.

Note: If you are defining demand by using the Occurrences and Time Between Orders,
you do not need to enter data in the Pattern field.

Pattern is directly related to Quantity. The pattern you select will take the total aggregate
quantity stated in the Quantity field and spread it out, as evenly as possible, over the
desired time frame. If the product type is set as Discrete, the actual order quantity is the
rounded value of (Quantity/the number of occurrences in the Pattern). If the product type
is set as Continuous, the actual order quantity is (Quantity/the number of occurrences in
the Pattern).

Note: If you specify a pattern, the Quantity field must be a number. Distribution
functions are not allowed in conjunction with patterns.

Pattern examples are in the following table.

If the And
And Product
Quantity Pattern Then:
Type is:
Is: Is:

30 Month to Discrete 1 unit is ordered every day for 30 days.

Day

30 Month to Continuous 1 unit is ordered every day for 30 days.

Day

40 Month to Discrete 1 unit is ordered every day for 30 days.

Day

40 Month to Continuous 1.33333 units are ordered every day for 30 days.
Day

50 Month to Discrete 2 units are ordered every day for 30 days.

Day

50 Month to Continuous 1.66667 units are ordered every day for 30 days.
Day

Note: In Guru Simulation:

1 year = 12 months = 52 weeks = 365 days
1 month = 4 weeks = 30 days = 720 hours
1 week = 7 days = 168 hours
1 day = 24 hours

18 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Demand

The following patterns are available:

Results in part of Quantity being Over the

This pattern
ordered course of

Year to Month Once A Month A Year

Year to Week Once A Week A Year

Year to Day Once A Day A Year

Month to Week Once A Week A Month

Month to Day Once A Day A Month

Month to Hour Once Every Hour A Month

Week to Day Once A Day A Week

Week to Hour Once Every Hour A Week

Day to Hour Once Every Hour A Day

Note: Pattern supports data transfer from other types of systems, such as ERP or
Forecasting. By choosing the right pattern, you can directly use the results of a
forecasting run or a database query.

Mode
Type: Special
Enter the mode for the demand to use. This will assign the Mode of transportation for this
order in both optimization and simulation.
For Vehicle Route Optimization, Demand with the same Mode value will be pooled
together and routed on equipment with the same Mode as specified in the Asset
Availability table.

Order Number
Type: Number
Enter an order number. If an order number is populated, the order number will be traced
through the simulation as long as the facilities the order sources through have inventory
policies of "Demand Flow" for the product. This is property is accessible when using
scripting in simulation as well.

Priority
Type: Number
Enter an order number indicating priority.
Simulation: This is property is accessible when using scripting in simulation. Aside from
use in simulation scripting, it does not have any direct functionality.
Vehicle Route Optimization: Use this value to set the priority for routing the shipment
(lower numbers have a higher priority). The priority is assessed per pool site.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 19

Chapter 1 Standard Tables

Unit Price
Type: Number
A customer specific price can be defined for one unit of the product being demanded in
this number field. This number will then be used to calculate revenue generated by this
site by demanding this specific product instead of the value listed in the Price field of this
product on the Products Table.
If you set Unit Price for one or more entries in the Demand table, be aware of the
following Optimization behavior:
 When the Unit Price field is left blank for all Demand records, the Price field of the
Products table will be used to calculate revenue.
 If you have multiple entries in the Demand table for the same Period for the same
Site-Product-Mode combination, and one of them uses the Unit Price field, then this
price is used to override the price of the Products table for this Site-Product-Mode
combination for the whole demand amount in that period. This is because
optimization works on aggregates and not individual orders.
 If you have multiple entries in the Demand table for the same Period for the same
Site-Product-Mode combination, and a number of these use the Unit Price field,
Supply Chain Guru uses the straight average of these Unit Price numbers for the
entire demand amount in that Period for this Site-Product-Mode combination.
 The Price is a weighted average of the Demand records per Customer-Product-Mode
created over each period. The weighting of this value takes into consideration demand
quantity and occurrences.

Note: The Flow Revenue on Customer Flows records is Mode-specific.

Unit Weight
Type: Number
Simulation: A customer specific weight can be defined for one unit of the product being
demanded in this number field. This number will then be used to calculate shipment
weight at this site by demanding this specific product weight instead of the weight listed
in the Weight field for this product in the Products Table.
When the Unit Weight field is left blank, the Weight field in the Products Table will be used
to calculate Shipment Weight. Currently this Unit Value will only apply to the first echelon
above the customer.
Vehicle Route Optimization: The Unit Weight is the weight of the shipment.

Unit Cubic
Type: Number
Simulation: A customer specific cubic volume can be defined for one unit of the product
being demanded in this number field. This number will then be used to calculate
shipment cubic volume at this site by demanding this specific product cubic volume
instead of the value listed in the Cubic field of this product on the Products Table.
When the Unit Cubic field is left blank, the Cubic field in the Products Table will be used to
calculate shipment cubic volume. Currently this Unit Value will only apply to the first
echelon above the customer.
Vehicle Route Optimization: The Unit Cubic is the cubic volume of the shipment.

20 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sourcing Policies

Cancel If Late
Type: Yes/No
If set to Yes, the customer order will be canceled if it cannot be delivered on time (i.e.
before the DUE DATE); this is determined at the site that ships to the customer. If the site
can not ship the item in time to the customer, the order will be dropped.

Earliest Pickup Date

Type: Date
This field determines the earliest pickup date and time for the shipment. If no value is
specified, Vehicle Route Optimization uses the Begin Time Horizon parameter (defaults to
Model Horizon Start Date).

Earliest Pickup Date Formula

Type: Number or Distribution
Not Currently Used: This field determines the earliest pickup date and time for the
shipment. If no value is specified, Vehicle Route Optimization uses the Begin Time
Horizon parameter (defaults to Model Horizon Start Date).

Latest Pickup Date

Type: Date
This field determines the latest pickup date and time for the shipment. If no value is
specified, Vehicle Route Optimization uses the End Time Horizon parameter (defaults to
Model Horizon End Date).

Latest Pickup Date Formula

Type: Number or Distribution
This field determines the latest pickup date and time for the shipment. Enter the number
of days to add to the start of the pickup time window. If no value is specified, Vehicle
Route Optimization uses the End Time Horizon parameter (defaults to Model Horizon End
Date). If you enter a distribution, this is applied as a Mean.

Status
Type: Include or Exclude
Use this field to exclude Demand records from the Vehicle Route Optimization. This field
does not currently apply when using other algorithms, such as Network Optimization,
Greenfield Analysis, or Safety Stock Optimization. In those cases, all Demand will be
included regardless of the Status value.

Sourcing Policies
The Sourcing Policies table has a different role for Network Optimization, Safety Stock
Optimization, and Simulation. The fields used by the different design engines are

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 21

Chapter 1 Standard Tables

Production Time, Production Time per Unit, Order Processing Time, Order Processing
Time Per Unit, and Source Lead Time:

Network Optimization Sourcing Policies

Network Optimization uses only one of the five fields – Production Time. Its primary use
is to specify how much time is actually available for production of products over a time
period. If a Process is specified, the process time (Work Time Per Unit) defined in the
Processes table is used instead of Production Time.

Safety Stock Optimization Sourcing Policies

Safety Stock Optimization uses the Source Lead Time, which is additional to the
Production Time for Make policies. Source Lead Time plus Production Time is the time
taken from the receipt of the production order to the produced product.
In addition, Safety Stock Optimization uses the Transport Time on the Transportation
Policies when determining the overall lead time for the product.

Simulation Sourcing Policies

Simulation uses the Production Time, the Production Time Per Unit, the Order Processing
Time, and the Order Processing Time Per Unit. These elements are used in the discrete
event planning system on which the Supply Chain Guru Simulation engine is based.

Sourcing Policy Fields

Site Name
Type: Text
Enter the site for which the sourcing policy is being applied to.

22 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sourcing Policies

Product Name
Type: Text
Enter the product for which the sourcing policy is being applied to.

Sourcing Policy
Type: Text
Choose a sourcing policy.

Policy Parameter
Type: Number
Used in conjunction with the "Multiple Sources" sourcing policies.
 Multiple Sources (Order of Preference) – The site selects the source based on the
order defined in the Policy Parameter field.
 Multiple Sources (Probability) – For Simulation, the source for the site’s order is
selected randomly based on the probabilities specified in the Policy Parameter field.
For Optimization, the order is divided based on the percentages specified in the Policy
Parameter field, and then sourced out to the respective sources. As an example, enter
50 to represent 50%. The Policy Parameter values should add up to 100, which
represents 100%.
 Multiple Sources (Split By Ratio) – For Simulation, the order is split according to the
value you set in the Policy Parameter field. For Optimization, the order is divided
according to the percentages specified in the Policy Parameter field, and then sourced
out to the respective sources. As an example, enter 50 to represent 50%. The Policy
Parameter values should add up to 100, which represents 100%.

Source Name
Type: List
Choose a site that can fill this replenishment order, or a work center that has a process
record for this product.

Note: If using the Make souring policy, this field can be left blank.

BOM Name
Type: Text
Choose the BOM Name for the end product you are making.
This may be used when defining a ’Make’ sourcing policy. If the end product defined in
this ’Make’ sourcing policy is made up of component products from further upstream in
the model, a Bill of Materials data table can be defined along with this ’Make’ sourcing
policy.
The Make policy tells the software that this end product is being made at that particular
site, while the BOM Name tells the software to look at the relevant BOM for the amount of
component product(s) that is required to make that particular end product.
You can optionally define a byproduct as part of the Bill of Materials.
Any subsequent order for the end product with a BOM will trigger an inventory check for
its component products. The corresponding inventory policy for the component

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 23

Chapter 1 Standard Tables

product(s) at that site will then decide if a replenishment order should be placed for the
component product(s).

Note: If using the make policy, you should have listed all components of your product in
the Bill of Materials data table.

Process
Type: Text
In this field, select the process name that the product has to go through while at this
particular site. This process can be chosen from the drop-down list in this field. Processes
have to be specified on the Processes Table, and may have an associated Workcenter(s).
If you define multiple Make Sourcing Policies for a Site-Product combination, if any of
these sourcing policy records includes a Process, the Process will be used during the
solve. This is the case, even if use of the policy with the Process results in a higher cost
solution.

Note: If you exclude a process, either in the Processes table or through a Scenario,
sourcing policies using this process are not excluded. The sourcing policy is still
available, but it will not use the process. In most cases, this has the effect of
making the model less costly and less constrained.

If you delete a process, you are prompted if you want to delete rows from dependent
tables (in this case, the Sourcing Policies table). However, rows are not actually deleted
from the Sourcing Policies table when you confirm the deletion. Instead, as when you
exclude the process, the process is no longer used by sourcing policies. The sourcing
policies are still available, but they will not be using a process.

Avg Unit Cost

Type: Number
This field specifies the average cost per unit for sourcing to be used in the network
optimization run.
When a Sourcing Policy is set to 'Make', Avg Unit Cost specifies the average cost of
producing a single unit of the Sourcing Policy's product. You can specify a different cost to
produce products at different facilities.
If the Sourcing Policy has a Process defined, the Cost Per Unit value from the Processes
table overrides the Avg Unit Cost.
When a Sourcing Policy is set to a policy other than 'Make', Avg Unit Cost specifies the
average cost of sourcing a single unit of the sourcing policy's product between the source
site and destination site. Sourcing costs are generally any cost associated with using the
lane such as tariffs, fees, or other overhead costs, but not the cost of physically
transporting the product.
Alternatively, instead of having a simple constant cost, you can set up a cost schedule,
using quantity break points and different costs with the Guru bracketed format, such as
<0,1.50> <5000, 1.25> <10000, 1.00>. In this example, if you are using incremental
discounts, the sourcing cost per unit is 1.50 for units 0 through to 5,000, 1.25 for units
5,000 through to 10,000, and 1.00 for units 10,000 and up. For an order consisting of
20,000 units, the total cost will be: (5,000-0)*1.50 + (10,000-5,000)*1.25 + (20,000-
10,000)*1.00 = 23,750.

24 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sourcing Policies

Note: The example shows incremental discounts. You can use all-item discounts rather
than incremental discounts.

Simulation and optimization handle costs differently. Simulation costs are calculated on a
per order basis for each individual order (using the Sourcing Cost value). Optimization
costs are calculated using the aggregate flow quantity for the time period (using the Avg
Unit Cost value). Thus, when using quantity-cost break points, you will use different
break points for simulation and optimization.

Apply Cost To Horizon

Type: Yes/No
When set to Yes, the specified Avg Unit Cost will be calculated over the total length of the
optimization. When periods are specified in the Periods Table, and this field is set to No,
the Avg Unit Cost will be applied to each individual period.
This setting matters for the total costs only if the Avg Unit Cost specified is a stepwise
function. If the Avg Unit Cost is a numeric value, the total Production/Sourcing costs will
be the same whether the model is a single-time or multi-time period model.

Sourcing Unit Cost

Type: Number or Distribution
Enter the unit cost of production if it is made at this site.
Alternatively, instead of having a simple constant cost, you can set up a cost schedule,
using quantity break points and different costs, with the Guru bracketed format, such as
<0, 1.50> <50, 1.25> <100, 1.00>. In this example, the sourcing cost per unit is 1.50
if the order quantity is between 0 and 50, 1.25 for quantities between 50 and 100, and
1.00 for quantities greater than 100.

Note: You should always make the first cost in a cost lookup function start with a
quantity of zero, such as <0, 1.50>.

Sourcing Order Cost

Type: Number or Distribution
Enter the cost of production of an order if it is made at this site.
Alternatively, instead of having a simple constant cost, you can set up a cost schedule,
using quantity break points and different costs, with the Guru bracketed format, such as
<0, 1.50> <50, 1.25> <100, 1.00>. In this example, the sourcing cost per order is 1.50
if the number of orders is between 0 and 50, 1.25 if the number of orders is between 50
and 100, and 1.00 for numbers of orders greater than 100.

Source Lead Time

Type: Number or Distribution
Simulation and Safety Stock Optimization: If using a Make sourcing policy, enter the
preparation time per order. This is independent of the number of items in an order. For
example, it may take 5 hours to prepare a machine before items are produced.
If receiving a product from outside, enter the time it takes to issue an order. For example,
it may take 2 hours to do the paperwork for an order.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 25

Chapter 1 Standard Tables

Note: To determine Lead Time for Safety Stock Optimization:

For Make policies for Site-Product pairs, Lead Time = Source Lead Time +
Production Time + Review Period (from Inventory Policies table).
For lanes, Lead Time = Source Lead Time + Transport Time + Review Period.
Total Lead Time in HR will be rounded up to DAY.

Network Optimization: Source Lead Time is not used.

Order Processing Time

Type: Number or Distribution
Defines the amount of time taken before an order is evaluated after it is received at the
source. This time is elapsed and considered only in Simulation.

Order Processing Time Per Unit

Type: Number or Distribution
Defines the amount of time taken per unit before an order is evaluated after it is received
at the source. This time is elapsed and considered only in Simulation.

Production Time
Type: Number or Distribution
Simulation: Defines the amount of time taken at a production node in simulation to
produce the finished product, if specific production processes are not implemented. This
is the time between the evaluation of the order and the finished goods' completion. The
default unit for this value is DAYS.
Network Optimization: Defines how much time is actually available for production of
products over a time period. If a Process is specified, the process time (Work Time Per
Unit) defined in the Processes table is used instead of Production Time.

Note: For Network Optimization, the Production Time must be an integer.

Production Time Per Unit

Type: Number or Distribution
Defines the amount of time taken at a production node in simulation to produce each unit
of finished product, if specific production processes are not implemented. This is the time
elapsed from the order receipt or previous production to the finished good's completion.

Max Sourcing Distance

In this number field, enter the maximum distance allowed between source and
destination sites for the product. In an optimization, the software will limit the sourcing
alternatives to those within the maximum distance radius.

Note: Entering 0 or leaving Max Sourcing Distance blank does not impose any
constraint.

Status
Type: Include or Exclude

26 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sourcing Policies

In this field, choose whether you want to include or exclude this Sourcing Policy for
simulation and optimization.

Type
Type: Existing or Potential
In this field, choose whether this Sourcing Policy exists or should be considered during
optimization.

Order Lot Size

Type: Number
Denote the size of the lot for this source.

Allow Back Orders

Type: Yes/No
Choose whether to allow back orders for orders coming from customer sites. If a site
does not have enough inventory to fill the order:
 Yes – holds the unfilled orders until they can be filled; this is a back order.
 No – deletes orders that cannot be filled. This will result in lost revenues.

Probability of Balking
Type: Number
Represents the probability that an order that cannot be filled will be rejected (rather than
backordered; assuming this is allowed) resulting in lost demand.

Days Between Productions

Type: Number
Represents the number of days between production occurring at manufacturing sites that
have make policies. This field is used to calculate the amount of cycle stock that should
be held at the manufacturing sites, equivalent to the number of units produced divided by
the number of production turns that occur during the time period.
Safety Stock Optimization: Days Between Productions is used for demand propagation
and safety stock optimization. For safety stock calculation, when the Service Definition is
Type 2 or Type 3, this value is used to derive the Min Replenishment Qty. For additional
information, refer to Inventory Policy Details.

Guaranteed Service Time

Type: Text
The Guaranteed Service Time is used to determine if the Source site can provide the
Product to the Destination within this time frame. If this is not possible, the order is
considered to have been missed and the Fill Rate may decrease. The Guaranteed Service
Time is in terms of days. It is calculated on a Source-Destination-Product basis.

Minimum Order Qty

Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 27

Chapter 1 Standard Tables

This is the order quantity used when calculating Cycle Stock and for use in Demand
Analysis and Safety Stock Optimization.
When calculating Cycle Stock, provide a Minimum Order Qty or populate the Days
Between Replenishments field in the Transportation Policies table, or both. Supply Chain
Guru takes the Days Between Replenishment and multiplies it by the average daily flow
to the site. Cycle stock is then calculated by taking the maximum of this product and the
Minimum Order Quantity, if specified, and dividing by two.

Note: Minimum Order Qty does not apply to lanes that serve Customers. Cycle Stock is
not calculated at the Customer sites.

In Demand Analysis, if you do not specify a Minimum Order Qty in the Sourcing Policies
table, Supply Chain Guru uses a default of 1 for demand propagation. If Minimum Order
Qty or Days Between Replenishment or both are not specified, Supply Chain Guru uses
Type 1 service to set the safety stock since the batch size is not known. In Safety Stock
Optimization, Type 2 and Type 3 service require either the Minimum Order Qty (Sourcing
Policies) or one of Days between Replenishments (Transportation Policies) or Days
Between Productions (Sourcing Policies) to recommend a batch size.

CO2
Type: Number
Denote the CO2 emissions for this source.

Graphic, Graphic Size, Graphic Color

In these text fields, choose how you want your sourcing policies between a site and its
source site to appear on the Layout map.

Note: For a better visual understanding of your supply chain, be consistent when
choosing how your sourcing policy connections appear on the Layout map. For
example, you could choose to represent all Single Source policies with a solid red
line, 1 point in size and all multiple Source (Most Inventory) policies with a dotted
blue line, 1 point in size.

Network Flow Graphic, Network Flow Graphic Size, Network Flow

Graphic Color
Type: Special
In this text field, choose a graphic to represent the shipment from source site to
destination site within a network flow. The graphic will be used in the animation of the
simulation of the supply chain. Also select the Color and Size of the graphic.

Inventory Policies
Site Name
Type: Text
Select the site for which an inventory policy is being made.

28 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Product Name
Type: Text
Select the product for which an inventory policy is being made.

Inventory Policy
Type: Text
Select an Inventory policy.

Inventory Policy Description

R,Q R,Q is a fixed replenishment point/fixed replenishment

quantity inventory policy. When the inventory level on-hand
falls below a certain replenishment point, R, the site will
generate a replenishment order for a certain quantity, Q, of
this product. When using this policy, the Reorder Point field is
set as the trigger level. The Reorder/Order Up To Qty field will
be the exact number of units reordered.

s,S s,S is a minimum/maximum inventory policy. When the

inventory level on-hand falls below a minimum, s, the site will
generate a request for a replenishment order that will restore
the on-hand inventory to a target, or maximum, number, S.
When using this policy, the Reorder Point field is the minimum,
or trigger level. The Reorder/Order Up To Qty field is the
maximum, or the number to which the inventory level is
restored.
The main difference between s,S and R,Q is that the s,S takes
into account exactly how far below the reorder level the
inventory is when the request for replenishment is generated.
The R,Q will always generate a reorder for exactly the value of
Reorder/Order Up To Qty.
The behavior of the system depends on how often inventory is
checked. So, it is important to select the appropriate Review
Period.

Demand Flow In Demand Flow policy, there is no strict inventory control.

Instead, every order that arrives at this site for this product
will generate a request for a replenishment order for the exact
same quantity. All requests are driven by the actual demand
quantities received at this site for this product. Therefore, the
Reorder Point and Reorder/Order Up To Qty fields are not used
in this policy.
However, you should still establish an initial inventory level. By
establishing an initial inventory level, the site will always
replenish exactly what was consumed by actual demand,
whether it was filled immediately, or left unfilled as a back
order.
Though it seems straightforward, Demand Flow can exhibit
complex behavior, especially when combined with Review
Period. Defining a Review Period can produce batching.
Batching occurs when the replenishment orders accumulate
during the Review Period ends and are then filled.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 29

Chapter 1 Standard Tables

Inventory Policy Description

DOS - Demand Days of Supply (DOS) - Demand Based is similar to an s,S

Based inventory policy except that the parameters for minimum and
maximum levels are specified in number of days rather than
product quantities. This policy computes the daily average of
product by looking back at the actual demand. How far back to
look is given by the DOS Window field.

DOS - Forecast DOS - Forecast Based is similar to an s,S inventory policy

Based except that the parameters for minimum and maximum levels
are specified in number of days rather than product quantities.
This policy computes the daily average of product by looking
forward and using forecasted demand. How far forward to look
is given by the DOS Window field. Forecast quantities must be
entered into the Forecasts table.
In short, DOS-Demand establishes inventory based on what
has happened; DOS-Forecast establishes inventory based on
what you expect to happen.

R,Q - Targets The R,Q - Targets inventory policy allows the user to change
the Reorder Point (R) and Reorder Quantity (Q) based on a
period of time designated by the user (year, quarter, month,
day, etc.)
When using the R,Q - Targets inventory policy, the quantities
and period are specified in the Forecasts input table.

s,S - Targets The regular s,S policy is a minimum/maximum inventory policy

that says that when the inventory on-hand falls below a certain
minimum s, the site will request for a replenishment order that
will restore the on-hand inventory to a maximum number, S.
s,S - Targets inventory policy is just like the regular s,S policy
except that you can specify Reorder Point (s) and Order up to
Quantity (S) for certain periods. You can define the period as
days, weeks, months, years, quarters etc.
When using the s,S - Targets inventory policy, the quantities
and period are specified in the Forecasts input table.

30 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Inventory Policy Description

T,S The periodic review order up to level (T, S) policy is relatively

simple and reflects real world practices to a great extent. This
policy is preferred in an intermittent demand context since it
facilitates the consolidation of shipments from suppliers and it
is associated with the optimization of one single parameter
(the order up to level). Transportation Guru uses this policy to
handle the Lumpy demand class, the most difficult of the
classes. The periodic policy provides the convenience of
regular ordering days for the stock list and for the supplier who
can plan efficient routing of the delivery vehicles.

BaseStock Basestock policy is useful when economies of scale in the

supply system are negligible relative to other factors. For
example, when each individual unit is very valuable, holding
and backorder costs dominate any fixed order costs. A
basestock policy is also recommended for a slow-moving
product where the economics of the situation rule out large
batch sizes. In some cases, there is a natural quantity unit for
both demand supply (for example, a truckload), and in terms
of that unit it makes sense to set Q=1. Basestock policy is
associated with the optimization of a single parameter. This
policy is recommended with a Continuous Review Period in
order to improve the reaction time.
Basestock is a continuous review (R,Q) policy with a Min
Replenishment Qty (Q) equal to 1.

Reorder Point
Type: Number
Enter a value according to the following table:

If Inventory Policy Is: Reorder Point Specifies

R,Q or s,S Quantity at which a replenishment order will

be triggered.

DOS-Demand Based or DOS-Forecast Number of days of supply at which a

Based replenishment order will be triggered.

Reorder/Order Up To Qty
Type: Number
Enter a value according to the following table:

If Inventory Policy
Reorder/ Order Up To Qty Specifies:
is:

R,Q Fixed order size

s,S Target quantity which inventory levels must be brought up

to when a replenishment is made.

DOS-Demand Based or Number of days of supply which inventory levels must be

DOS-Forecast Based brought up to when replenishment order is made.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 31

Chapter 1 Standard Tables

Review Period
Type: Text
Enter how often inventory level is checked to see if a replenishment order is necessary.
Options for review period are Hourly, Daily, Weekly, Monthly, and Continuous. Continuous
means that every order that arrives will cause the inventory level at that site to be
checked to see if a replenishment order is necessary.
For many supply chains, automated inventory tracking means that they continuously
check the inventory level, replenishing almost the instant that the level falls below the
Reorder Point. However, there are also cases where the actual behavior of the system is
really better represented by a periodic review system.
For example, your Lemonade Stand always knows how much inventory is on-hand, but
only wants to replenish once a day. In this case, a Review Period of Daily would result in
product being reordered once a day, but only if needed. How much is ordered depends on
the policy you have defined.
The review period can be set to a pre-defined interval, set to one value, or assigned a
schedule as well. See the table below for how to enter data:

Value Examples Parameter use

Interval Continuous, Daily, The inventory level is evaluated at each pre-defined

Weekly interval.

Single 12 HR The inventory level is evaluated every interval value (for

Value 1 DAY example, every 12 hours).

Repeating 1 DAY, 3 DAY, 2 DAY The inventory level is reviewed after one day, then
Schedule reviewed again 3 days after the first review, and again 2
days after the second review. The schedule is repeated
upon completion.

If the review period has a value entered in it (i.e. 12 Hour or 1 Day etc), the inventory
level is checked as specified by the interval in the review period. (If the review period is
12 Hour, the inventory level will be evaluated every 12 hours).
The review period also supports a repeating schedule. The format is the same as a single
value in the review period, except a comma is placed between the single values. An
example follows:
1 Day, 3 Day, 2 Day
In the above example, a Review of the queue will occur after one day. Then the next
review will occur 3 Days after the first review. Then the third review will occur 2 Days
after the second. When the schedule completes, it repeats itself.
Review periods themselves are dependent on the start time of simulation. For example,
assume the start time set in the Model Options is 12:00 AM 1/1/2010, and the review
period is set to 24 HR. The inventory level will be reviewed every day at 12:00 AM. An
offset can be entered in front of the review period to change the time the model will start
reviewing. The offset will only be incurred once.
For example, if we would like to Review the inventory level every day at 4 PM, and our
simulation starts at 12 AM, an offset of 16 hours can be entered to shift the review time
to 4 PM. Then, if we have 24 hour review period, it will check every 24 hours from the
time to which it was offset. The format for the offset is as follows: < "Time" >
For the a 16 hour offset, with a daily review you would enter: <16 HR>, 24 HR.

32 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Status
Type: Text
Choose the inventory policy status:
 Include - This inventory policy is to be included in a simulation or optimization run.
 Exclude - This inventory policy is to be excluded in a simulation or optimization run.

Initial Inventory
Type: Number
Enter how many units of this product is on-hand at this site when the simulation begins
running.

Note: If no data are entered, Supply Chain Guru assumes there are zero units on-hand
when the simulation or network optimization begins.

In supply chain simulation, you are starting from scratch each time. Although your model
will quickly conform to a real world situation, at time zero, there will likely be differences
between the model and the real world. You can counteract some of these differences by
setting initial inventory levels in your model.

Note: In simulation, inventory holding costs can be incurred at a site that has a Status of
"Closed" if the site had initial inventory and if the Inventory Carrying Cost % > 0
or the Product Value > 0.

Safety Stock Optimization does not consider Initial Inventory.

Inbound Shipment Unit Cost

Type: Number or pairs
Enter the activity cost of handling and moving one unit of this product from the receiving
dock into inventory. This figure contributes to inbound warehousing cost statistics in your
simulation report. Inbound and outbound costs include such costs as paper tracking
procedures, handling equipment, and personnel.

Note: Inbound Shipment Unit Cost does not include Transportation costs.

Inbound Shipment Unit Cost is reflected on the following tables:

 Network Summary Optimization Output Table in the Total Inbound Warehousing Cost
field.
 Interfacility Flows Optimization Output Table in the Flow Inbound Warehousing Cost
field. The costs are reported on a source-destination basis. You can use a filter to get
an aggregated view based on Product and Destination.

Inbound Shipment Cost

Type: Number
Enter the activity cost of handling and moving a shipment of this product from the
receiving dock into inventory. This figure contributes to inbound warehousing cost
statistics in your simulation report. Inbound and outbound costs include such costs as
paper tracking procedures, handling equipment, and personnel.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 33

Chapter 1 Standard Tables

Outbound Shipment Unit Cost

Type: Number or pairs
Enter the activity cost of removing one unit of this product from inventory to the shipping
dock. This figure contributes to outbound warehousing cost statistics in your simulation
report. Inbound and outbound costs include such costs as paper tracking procedures,
handling equipment, and personnel.

Note: Outbound Shipment Unit Cost does not include Transportation costs.

Outbound Shipment Unit Cost is reflected on the following tables:

 Network Summary Optimization Output Table in the Total Outbound Warehousing Cost
field.
 Interfacility Flows Optimization Output Table in the Flow Outbound Warehousing Cost
field. The costs are reported on a source-destination basis. You can use a filter to get
an aggregated view based on Product and Source.
 Customer Flows Optimization Output Table in the Flow Outbound Warehousing Cost
field. These are the outbound warehousing costs facing customers. The costs are
reported on a source-destination basis. You can use a filter to get an aggregated view
based on Product and Source.

Outbound Shipment Cost

Type: Number
Enter the activity cost of removing a shipment of this product from inventory to the
shipping dock. This figure contributes to outbound warehousing cost statistics in your
simulation report. Inbound and outbound costs include such costs as paper tracking
procedures, handling equipment, and personnel.

Apply Inbound Cost to Horizon

Type: Yes/No
During a multi-time period optimization, when Apply Inbound Cost to Horizon is set to
Yes, if the inbound cost is defined as a piecewise function, it will be used over the total
throughput throughout the duration of the optimization time period.

Apply Outbound Cost to Horizon

Type: Yes/No
During a multi-time period optimization, when Apply Outbound Cost to Horizon is set to
Yes, if the outbound cost is defined as a piecewise function, it will be used over the total
throughput throughout the duration of the optimization time period.

Inbound Capacity
Type: Number
Enter the maximum quantity of product this site is capable of accepting. You can also
leave it blank or enter INF (infinity) to define a capacity with no maximum.

Outbound Capacity
Type: Number

34 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Enter the maximum quantity of product this site is capable of shipping. You can also leave
it blank or enter INF (infinity) to define a capacity with no maximum.

Capacity Period
Type: Text
Enter the period of time (Day, Week, Month (30 day), Quarter (91 day), Year) over which
Capacity is measured. If no Capacity Period is specified, the default is the model period
length.

Capacity Basis
Type: Text
Enter the unit in which capacity is measured. Capacity can be measured in:
 Quantity - how many units
 Weight - how much the product weighs
 Cubic - the cubic volume of product.
For example, a Capacity of 500, a Capacity Period of Month, and a Capacity Basis of
Quantity means that the maximum capacity this site can ship is 500 units of product per
month.

Inv Turns
Type: Pairs or Number
This field allows you to specify a (piecewise) linear function from which the average
inventory can be calculated during optimization.
We define the following relationship between Average Inventory and Throughput:
Average Inventory = m times Throughput
Where m is the inverse of the inventory turns value.
We allow Average Inventory to be defined over multiple ranges of Throughput. The
format for the relationship is a series of pairs <lower range value, turns value>.
Consider the sample graph below. Up to 1000, the Average Inventory is (1/5) *
Throughput. Between 1000 and 3000, the Average Inventory is (1/8) * Throughput + 75.
After 3000, the Average Inventory is (1/15) * Throughput + 250. This relationship is to
be entered as <0,5><1000,8><3000,15>. In the case the relationship between Average
Inventory and Throughput is simply linear, it is sufficient to input the turns value (inverse
slope) of this line; for example, 5.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 35

Chapter 1 Standard Tables

Note: In a multi-period model, setting Inv Turns in the Inventory Policies table affects
only the first period. If you want to set inventory turns in other periods, use the
Inventory Policies Multi-Period table to control the Inv Turns per period.

Inv Carrying Cost %

Type: Number
Specifies the cost percentage for holding inventory of specified product at this site during
the optimization run. This percentage and the Product Value are used to calculate
inventory holding costs. If the inventory carrying cost percentage is 10%, enter "10" in
this field. If this value is not specified, the Inv Carrying Cost % defined in Model Options
is used.
Inv Carrying Cost % is reflected in the Total Inv Holding Cost in the Network Summary
output table.

Min Dwell Time

This field determines the minimum number of periods in which a product must stay at the
site. The value must be a non-negative integer. For example, if the Min Dwell Time is set
to 2, and the product is produced in Period_001, it must remain in inventory at the site
for Period_002 and Period_003 before being used to fulfill demand.

Note: If Shelf Life is defined for a product in the Products table, you cannot define Dwell
Time for the same product at any site.

Max Dwell Time

This field determines the maximum number of periods in which a product can stay at the
site. The intent of this value is to push a product out of the site after the number of
periods specified by Max Dwell Time. A common use is to limit how early products can be
prebuilt. The value must be a non-negative integer. A value of 0 means the product
cannot be pre-built at all; it can only be produced in the same period in which it is
demanded. Initial inventory is treated like it came into the system in the period before
the model starts (that is, period 0). If the Max Dwell Time value in Inventory Policies is
set to 1, this initial inventory can be used to fulfill demand in period 1, but not period 2,
or subsequent periods. If the Max Dwell Time is set to 2, initial inventory can be used to
fulfill demand in periods 1 and 2, but not 3, 4, and so on.

Note: If Shelf Life is defined for a product in the Products table, you cannot define Dwell
Time for the same product at any site.

Max Inv Qty

Type: Number
Specifies the maximum number of units of specified product that this site can stock.

Min Inv Qty

Type: Number
Specifies the minimum number of units of specified product that this site is required to
stock.

36 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Safety Stock
Type: Number
Specifies the quantity or Days of Supply (depending on the Safety Stock Basis) that will
be held in inventory. This value can be changed by period in the Multi-Period Inventory
Policies table. This field is an input for Network Optimization. To calculate this value, use
Safety Stock Optimization.

Disposal Cost
Type: Number
Enter the disposal cost that is incurred when the shelf life expires for this by-product at
this site. You can control the disposal cost per period by setting a Disposal Cost in the
Inventory Policies Multi-Period table.
Supply Chain Guru supports disposal cost both for products that expire based on their
shelf life and those by-products that are trash (not expired)
 Expired Products – If the by-product reaches its shelf life before the model ends, it is
an expired product. You can define a disposal cost that is incurred when the shelf life
of a by-product expires within the model horizon. Supply Chain Guru will determine
whether it is cheaper to incur the disposal cost and get rid of the product, or hold it in
inventory based on inventory and production costs.
The Disposal Cost field in the Inventory Policies and Inventory Policies Multi-Period
tables enable you to set a disposal cost per product per site for each time period. You
must define Inventory Policies for products that can expire, even if you are not
applying a Disposal Cost.
For expired products, the cost is reported in the Flow Transportation Cost field on the
Customer Flows Optimization Output table, for a flow with a Customer named "Trash".
The Mode is “EXPIRED PRODUCT”.

Note: The Disposal Cost fields for product expiration are available as target fields when
creating Input Pipes.

 Trashed Products – A by-product is considered trash if it has not reached its expiration
date (end of shelf life) by the end of the model and if there are no Inventory Policies
defined for the product. If there are Inventory Policies defined, it is assumed that the
by-product should be held in inventory, rather than trashed. In this case, an inventory
holding cost may be incurred.
If a by-product is to be trashed (that is, no Inventory Policies have been defined), you
can define a disposal cost to be incurred for an unexpired by-product, in other words
the cost to dispose of by-products created as part of your Bills of Material. This is
referred to as a “trashing cost” and applies to unused, unexpired by-product. You
specify this using the “Disposal cost per unit of by-product” on the Modeling Options
tab of Optimization Options.
The disposal cost for trashed products is reported in the Flow Transportation Cost field
on the Customer Flows Optimization Output table, for a flow with a Customer named
"Trash". The Mode is “UNUSED PRODUCT”.

Product Value
Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 37

Chapter 1 Standard Tables

Data: Enter a monetary value for each unit. The Product Value field is used to calculate
the inventory investment and inventory holding costs. This enables you to vary the
product value at a specific site by time period. It is incorporated in the following formula:
Inventory holding cost = Inventory Quantity * Product value * Holding Cost Percentage *
Length of Time in Inventory
The Product Value in the Inventory Policies table overrides the Product Value in the
Products table for Network Optimization. In Simulation, the Product Value in the Products
table is always used.

Inv Cost Other

Type: Number
Specifies any additional inventory costs associated with carrying cost not covered by
other categories. Enter the cost per unit of inventory per period.

Stocking Site
Type: Boolean
Use this field to determine if a site can hold safety or prebuilt stock. The default value is
Yes. This setting is used in Network Optimization and Safety Stock Optimization. In
Network Optimization, if this value is set to No, a site can incur inbound and outbound
warehousing costs only.
Safety Stock Optimization: If Stocking Site is set to “No”, this site is still considered
during demand propagation although no safety stock is held at the site.

Safety Stock Basis

Type: Special
This field determines the basis used to calculate Safety Stock. Qty means that the
optimization will use the value to represent the actual quantity, and DOS means that the
value is in terms of days of supply.

Note: DOS is not equivalent to Coverage. DOS is another measurement of safety stock
quantity in time.

For Network Optimization, this field specifies how the number in Safety Stock number
field will be interpreted.
For Safety Stock Optimization, it specifies how the Min Safety Stock and Max Safety
Stock constraints will be applied.

Service Requirement
Type: Number
Specifies the required service level of the product for customer-facing sites. The number
must be input as a fraction - that is, 95% would be input as .95, not 95 in the table. A
Service Requirement value of .50 ensures that no safety stock is held (that is, if the
service definition is Type 1). If no service requirements are specified at any site, the
service requirement will default to 95%for the customer facing facilities. If Service
Requirements are not specified upstream from a site where a Service Requirement is
specified, service level propagation is applied.

38 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies

Min and Max Safety Stock

Type: Number
Specifies constraints on the safety stock for the product-location combination. Max Safety
Stock is a constraint that will be respected if it does not lead to infeasibility. In the case of
an infeasibility, the constraint is relaxed (treated as a soft constraint) so that it does not
cause the infeasibility. Min Safety Stock and Max Safety Stock are determined based on
the Safety Stock Basis (Qty or DOS).

Min and Max Service Time

Type: Number
Specifies hard constraints for the service time the site quotes to its downstream sites.
This time is in units of DAY. For these fields, enter the number of days (do not specify a
time unit). Min Service Time and Max Service Time can lead to infeasibility.

Allow Partial Fill

Type: Yes/No
Choose whether orders can be partially filled. The default for this field is Yes.

Forecast Name
Type: Text
In this field choose the Forecast you want to use for a DOS - Forecast Based inventory
policy or the targets for an R,Q-Targets or s,S-Targets inventory policy. These forecasts
can be specified on the Forecast Table.

DOS Window
Type: Number
For Simulation, this is used for the DOS Demand-Based and DOS Forecast-Based
inventory policies. If using the DOS Demand Based inventory policy, enter the number of
days to look back on to calculate average daily demand. If using the DOS Forecast Based
inventory policy, enter the number of days to look ahead to calculate average daily
demand.
When using a DOS-Demand based policy, if the number of days the simulation has run is
less than the DOS Window, the window will be automatically adjusted to the number of
days passed during the simulation run. For DOS-Forecast based policies, if the remaining
time is less than the DOS Window, the new DOS window will be automatically adjusted to
the remaining days left in the simulation.

Consignment Cost
Type: Number
Enter the outbound handling cost of a shipment of this product.

Consignment Unit Cost

Type: Number
Enter the outbound handling cost of one unit of this product.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 39

Chapter 1 Standard Tables

Unit Delay Factor

Type: Number or Distribution
The field specifies the unit delay factor used when the Sourcing Policy is Multiple Sources
(Fastest Path) or Multiple Sources (Close to Due Date).

DOS Planning Lead Time

Type: Number
This is used for the DOS Demand-Based and DOS Forecast-Based inventory policies. It
allows you to offset the DOS window by a number of days either before the current day
(DOS demand based) or ahead of the current day (DOS Forecast based). Acceptable
input in this field is any integer great than 0 and is representative of the number of days
offset.

Delay Factor
Type: Number or Distribution
The field specifies the order delay factor used when the Sourcing Policy is Multiple
Sources (Fastest Path) or Multiple Sources (Close to Due Date).

Transportation Policies
Transportation Policies are considered unique based on the combination of Source Site,
Destination Site, Product Name and Mode.

Source Site
Type: Text
Choose the source site from which the product is to be transported.

Destination Site
Type: Text
Select the destination site that will receive the product.

Product Name
Type: Text
Choose the product to be transported. Transportation Policies can be product-specific,
apply only to a set of products (using a set in the Groups Data Table), or apply to all
products on that lane if the Product Name is left blank. Specifying a product will create a
product-specific transportation policy that only affects transporting this product from Site
A to Site B. No other product will use this policy.
If you are using the aggregate or disaggregate transportation policy, you will designate a
transportation asset type as "container" in the Transportation Assets Data Table. This
container will be visible in the drop down box of the Product Name Field.

Mode
Type: Text

40 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

The mode is a descriptive term used to describe the transportation mode, such as
Customer_Delivery or TruckingCompany1.

Mode Rule
Type: Special
Choose the Mode Rule to be used for transportation policies that have multiple modes
(these have the same Source-Destination combination). The options are explained in the
table below.

Note: Most of the options apply to Simulation only.

For Transportation Policies that have the same Source-Destination combination

and different Modes, use the same Mode Rule for all these records. If multiple
Mode Rules are applied to policies with the same Source-Destination pair,
Simulation will use the Mode with the name that is first alphabetically.

Mode Rule Example

First In Simulation, the mode with the lowest Mode number will be used.
In Optimization, this acts as an unconstrained option and any mode can be
selected.

First Simulation only: The mode for which an asset becomes available first will be used.
Available
Asset

By In Simulation, the mode is chosen based on probability. The Parameter value

Probability determines the probability.
In Optimization, the flows are split based on the percentages set in the policy
Parameter fields.

Split By In Simulation, individual orders are split based on the order size, using the ratios
Ratio as defined in the Parameter value.
In Optimization, the flows are split based on the percentages set in the policy
Parameter fields.

On Due Simulation only: The modes are sorted in descending order from longest to
Date shortest. The first mode that can fulfill the order on time (before or on the Due
Date) will be used.

On Qty Simulation only: The mode will be picked based on the size of the order (in units).
You must specify one mode with a Mode value of 0, and other modes where the
Mode is used as the unit break points. If there are 2 modes, one with Mode 0 and
one with Mode 200, orders that have a size between 0 and 200 units will take
Mode 0, and orders =>200 units will take Mode 200.

On Weight Simulation only: The mode will be picked based on the size of the order (in
weight). Similar to On Qty.

On Cubic Simulation only: The mode will be picked based on the size of the order (in cubic).
Similar to On Qty.

Queue Simulation only: Shipments will only be placed in a queue, but never dispatched.
Only Queue Only assumes a customer written script takes care of scheduling
shipments.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 41

Chapter 1 Standard Tables

Fastest Simulation only: The delivery time for each path is calculated and the policy with
Path the fastest path is selected.

Close To Simulation only: The delivery time for each path is calculated and the policy that
Due Date delivers the shipment as close to the due date as possible without going over is
selected. If no path can deliver by the due date, it selects the policy that gets it
there the fastest.

Parameter
Type: Special
The parameter is used differently depending on the Mode Rule specified.

Mode Rule Parameter use

First In Simulation, modes will be used in alphabetical order by Mode name.

By Probability For Simulation, enter the probability that the mode will be used. For
example, if you enter 30, chances are 30% that this mode will be used.
The probabilities for the lane need to add up to 100.
For Optimization, enter the percentage that should flow on this mode.

Split By Ratio For Simulation, the shipping items will be split by this percentage to use
the mode. For example, if you enter 30, 30% of the shipping items should
use the mode. The probabilities for the lane need to add up to 100.
For Optimization, enter the percentage that should flow on this mode.

On Qty Simulation only: The mode will be picked based on the size of the order (in
units). Each mode should have a range in which to send it (i.e. 0-200 =
Mode_1, 200-500 = Mode 2, 500 - And above = Mode 3). Take the first
number in the range for that mode, and place that in the mode Parameter.

On Weight Simulation only: Each mode should have a range in which to send it (i.e.
0-200 = Mode_1, 200-500 = Mode 2, 500 - And above = Mode 3). Take
the first number in the range for that mode, and place that in the mode
Parameter.

On Cubic Simulation only: Each mode should have a range in which to send it (i.e.
0-200 = Mode_1, 200-500 = Mode 2, 500 - And above = Mode 3). Take
the first number in the range for that mode, and place that in the mode
Parameter.

Queue Only Simulation only: Shipments will only be placed in a queue, but never
dispatched. Queue Only assumes a customer written script takes care of
scheduling shipments.

42 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

Transportation Policy
Type: Text

Transportation
Description
Policy

Parcel The Parcel policy ships product bundles immediately. Product

bundles are shipped to their destinations, regardless of their
quantity, as soon as the product is ready to be shipped.

LTL (Less than The Less than Truckload policy ships product bundles
Truckload) immediately. It does not consider if other bundles are going to
the same destination, and therefore does not aggregate
product bundles. Optionally, a Transportation Asset can be
assigned to the lane, therefore requiring that an asset be
available for the shipment to proceed.

Full TL (Full A Full Truckload policy aggregates product bundles together for
Truckload) shipment. When the product bundle’s total weight (or cubic
volume) first reaches the asset’s weigh fill level (or cubic fill
level), the aggregated set of product bundles are shipped as
soon as an asset becomes available.
The policy must have a Transportation Asset specified. Each
asset unit’s weight and cubic volume capacity is also defined in
the Transportation Assets table. If the aggregated bundles’
total weight or volume exceeds this amount, the bundle is then
split. The excess quantity is set aside while an asset conducts
one shipment at capacity.

Air When a Transportation Asset is specified, this policy behaves

like a Full TL policy. If no asset is specified, it behaves like a
Parcel policy.

Rail When a Transportation Asset is specified, this policy behaves

like a Full TL policy. If no asset is specified, it behaves like a
Parcel policy.

Ship When a Transportation Asset is specified, this policy behaves

like a Full TL policy. If no asset is specified, it behaves like a
Parcel policy. This policy can also be used in conjunction with
containerization in the software.

Daily Shipment Every 24 hours, the project bundles is shipped from source to
destination. The shipment is subject to asset availability in the
event that a Transportation Asset is specified.

Weekly Every 7 days, the project bundles are shipped from source to
Shipment destination. The shipment is subject to asset availability in the
event that a Transportation Asset is specified.

Periodic This policy allows shipments to be scheduled as per your

Shipment definition. The shipment is subject to asset availability in the
event that a Transportation Asset is specified. They can be
simple repeated schedules, such as every 50 hours, or more
intricate setups such as on specific days of the week.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 43

Chapter 1 Standard Tables

Transportation
Description
Policy

Pooled Inbound Simulation: In a Pooled Inbound policy, a single asset acts to

deliver the various product bundles to a specific site. Supply
Chain Guru consolidates all bundles that are inbound into the
same site on a single asset.
By default, the asset travels to sites in increasing order of
distance from the destination site, starting with the closest
source site. You can also specify a route for the asset to follow.
The shipment is subject to asset availability in the event that a
Transportation Asset is specified.
Vehicle Route Optimization: When using Vehicle Route
Optimization, only Transportation Policies that are Pooled
Inbound or Pooled Outbound are considered. If the policy is
Pooled Inbound, the destination sites are considered to be
pooling sites. If the policy is Pooled Outbound, the origin sites
are considered to be pooling sites.

Pooled Periodic A Pooled Periodic Inbound policy is a combination of the Pooled

Inbound Inbound and Periodic policies. In a Pooled Periodic Inbound
policy, a single asset acts to deliver the various product
bundles to a specific site. The software consolidates all bundles
that are inbound into the same site on a single asset.
Additionally, the shipments follow the user defined schedule
much like the Periodic Shipments policy.
By default, the asset travels to sites in increasing order of
distance from the original outbound site, starting with the
closest source site. You can also specify a route for the asset to
follow. The shipment is subject to asset availability in the event
that a Transportation Asset is specified.

Pooled Simulation: In a Pooled Outbound policy, a single asset acts to

Outbound deliver the product bundles to various destinations. The
software consolidates all bundles that are outbound from a
single site on a single asset.
By default, the asset travels to sites in increasing order of
distance from the original outbound site, starting with the
closest destination site. You can also specify a route for the
asset to follow. The shipment is subject to asset availability in
the event that a Transportation Asset is specified.
Vehicle Route Optimization: When using Vehicle Route
Optimization, only Transportation Policies with a Transportation
Policy of Pooled Inbound or Pooled Outbound are considered. If
the policy is Pooled Inbound, the destination sites are
considered to be pooling sites. If the policy is Pooled
Outbound, the origin sites are considered to be pooling sites.

44 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

Transportation
Description
Policy

Pooled Periodic A Pooled Periodic Outbound policy is a combination of the

Outbound Pooled Outbound and Periodic policies. In a Pooled Periodic
Outbound policy, a single asset acts to deliver the product
bundles to various destinations. The software consolidates all
bundles that are outbound from a single site on a single asset.
Additionally, the shipments follow the user defined schedule
much like the Periodic Shipments policy.
By default, the asset travels to sites in increasing order of the
distance from the original outbound site, starting with the
closest destination site. You can also specify a route for the
asset to follow. The shipment is however subject to asset
availability in the event that a Transportation Asset is specified.

Interleaved Vehicle Route Optimization: The route can have interspersed

deliveries and pickups. The vehicle starts from its home base,
visits a sequence of pickups and deliveries, and then goes back
to the home base if a round trip is required.

Flow The Flow Transportation Policy allows you to customize the

complete chain of shipments that a bundle can go through.
Once a bundle uses a transportation lane with a specific Mode,
it thereafter tries to use lanes which have the same Mode. This
policy is used only in Optimization.
NOTE: If you are using the Flow Transportation Policy, you
cannot have multiple modes going into the source site.

Link to Lane This policy creates a virtual lane. It then relies on flow patterns
defined in the Ship to field to ship the product bundle from the
original source to the final destination.

Aggregate Product bundles can be assembled into containers for simpler

Container shipping. In this policy, product bundles are aggregated into a
container asset, which subsequently can be shipped to a
destination.

Disaggregate Container bundles are disassembled back into product bundles.

Container This must be done before a specific product bundle can be
retrieved from the container asset.

Join Convoy Vehicles are assembled into convoys. The convoy can depart
the origin site when the fill level (number of required vehicles)
is reached.

Depart Convoy Convoys are disassembled back into vehicles. This is done
once the convoy reaches the destination site.

Note: Choose a transportation policy. Vehicle Route Optimization considers only records
with a Transportation Policy of Pooled Outbound or Pooled Inbound.

Status
Type: Text
Choose the transportation policy status:

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 45

Chapter 1 Standard Tables

 Include - This transportation policy is to be included in a simulation or optimization

run.
 Exclude - This transportation policy is to be excluded in a simulation or optimization
run.

Average Cost
Type: Number
The Average Cost field is related to the Cost Basis field. The value entered in the Average
Cost field is the transportation cost per Cost Basis unit. For example, if Cost Basis is Qty,
Average Cost should be the cost to ship 1 unit. If Cost Basis is Distance, the Average Cost
should be the cost of shipping 1 unit of distance. The Average Cost rate is only used by
optimization and has an Average Cost Field Guru associated with it. Simulation uses the
Cost rate to calculate transportation costs.

Note: You can use stepwise costs for Average Cost if the Cost Basis is Qty, Weight or
Cubic. You cannot use a value of INF for the Cost when defining a stepwise cost.

Average Cost is reflected in the Total Transportation Cost in the Network Summary output
table.

Cost
Type: Multiple
This is the cost of transportation in the simulation. The Cost rate field is used in
conjunction with the Cost Basis field. There are four ways in which to input costs for this
field:
 Enter in a single number. The single value will be interpreted differently based on the
Cost Basis.
 Enter in a step function. A step function can be entered with assistance from the Cost
field guru.
 Use a Dynamic Rate table (via the Input Pipes table).
 Write a custom script to calculate costs (using Scripts).
Cost is reflected in the Total Transportation Cost in the Network Summary output table.

Cost Basis
Type: Text
Choose the formula for calculating the total transportation cost for a shipment from
Source site to Destination site. The default Cost Basis is Qty. Actual shipment Cost is
calculated as follows:

Shipment
Cost Basis Unit Cost Shipment Cost
Size Basis

Weight Average Cost * Product Weight Unit Cost * Flow Units

Qty Average Cost Unit Cost * Flow Units

Cubic Average Cost * Product Cubic Unit Cost * Flow Units

46 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

Distance Weight (Average Cost * Distance) / (Shipment Size / Product Unit Cost * Flow Units
Weight)

Cubic (Average Cost * Distance) / (Shipment Size / Product Unit Cost * Flow Units
Cubic)

Quantity (Average Cost * Distance) / (Shipment Size ) Unit Cost * Flow Units

Fixed Weight Average Cost / (Shipment Size / Product Weight) Unit Cost * Flow Units

Cubic Average Cost / (Shipment Size / Product Cubic) Unit Cost * Flow Units

Quantity Average Cost / (Shipment Size ) Unit Cost * Flow Units

Weight- Average Cost * Product Weight * Distance Unit Cost * Flow Units
Distance

Qty-Distance Average Cost * Distance Unit Cost * Flow Units

Cubic- Average Cost * Product Cubic * Distance Unit Cost * Flow Units
Distance

For example, assume you have the following Product and Demand data:

Product Weight Cubic Demand.Quantity

A 2 5 100

B 3 10 200

and the following Transportation Policy data:

Average Shipment Shipment

Source Destination Product Distance
Cost Size Size Basis

DC CZ A 1 1000 Weight 750

DC CZ B 1 5000 Weight 750

 For each of the Cost Basis settings and with all demand served on the flow, the
shipment costs for Product A are as follows:

Cost Basis Unit Cost Shipment Cost

Weight 1*2=2 2 * 100 = 200

Qty 1=1 1 * 100 = 100

Cubic 1*5=5 5 * 100 = 500

Distance (1 * 750) / (1000 / 2) = 1.5 1.5 * 100 = 150

Fixed 1 / (1000 / 2) = 0.002 0.002 * 100 = 0.2

Weight-Distance 1 * 2 * 750 = 1500 1500 * 100 = 150000

Qty-Distance 1 * 750 = 750 750 * 100 = 75000

Cubic-Distance 1 * 5 * 750 = 3750 3750 * 100 = 375000

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 47

Chapter 1 Standard Tables

Apply Cost To Horizon

Type: Yes/No
When set to Yes, the specified Average Cost will be calculated over the total length of the
optimization. When periods are specified in the Multi-Time Period Periods Table, and this
field is set to No, the Average Cost will be applied to each individual period.
This setting applies to the total costs only if the Average Cost specified is a stepwise
function. If the Average Cost is a numeric value, the total transportation costs will be the
same whether the model is a single-time or multi-time period model.

Fuel Surcharge
Type: Number
Use this field to represent a fuel surcharge that is incurred in addition to the normal
transportation cost in Network Optimization. The Fuel Surcharge is always calculated as a
Distance-based cost, regardless of the Cost Basis value on the Transportation Policy
record:
Flow Units * (Distance * Fuel Surcharge)/(Shipment Size/Product Weight)
For example, assume the following values:

Average Fuel Cost Shipment Shipment Size Product Flow

Distance
Cost Surcharge Basis Size Basis Weight Units

150 .05 Fixed 800 2 Weight 5 1000

In this case, the cost based on the Transportation Cost is calculated as:
Flow Units * (Average Cost/(Shipment Size/Product Weight)) or
1000 * 150/(2/5) = 375000
The Fuel Surcharge is calculated using a cost basis of Distance:
Flow Units * (Distance * Fuel Surcharge)/(Shipment Size/Product Weight) or
1000 * (800 * .05)/(2/5) = 100000
The Flow Transportation Cost is the cost based on Average Cost plus the cost based on
the Fuel Surcharge:
375000 + 100000 = 475000

Note: Vehicle Route Optimization costs, including surcharges, are defined on the Rate
table.

Shipment Size
Type: Number
In this field, enter the average size of your shipments. This field is only used for
optimization models when the Cost Basis is set to Distance or Fixed. It is used to
determine how many trips are needed to satisfy the flow of product for the respective
mode.
For example, if the average shipment weight for a mode is 50 and 100 units of weight
flow on the mode, there are 2 required trips. If the Cost Basis is Fixed and the Average
Cost is 200, then the transportation cost for this mode is 400. Similarly, if the Cost Basis
is Distance, the transportation cost for this mode would be the Average Cost (200 from

48 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

the previous example) times the distance in miles (found in the Distance field) times the
number of trips (2).

Shipment Size Basis

Type: Text
Select the unit that is represented by the Shipment Size. This value can be one of:
 Quantity
 Weight
 Cubic
The default value is Weight.

Product Class
Type: Text
Product Class supports non product-specific Transportation Policies for use with RateWare
XL in the Cost and Average Cost fields.
If you enter a value for this field, it is used for RateWare XL lookups in the Average Cost
and Cost fields in combination with the Shipment Weight field. This class is used instead
of the Class value on the Products table (based on the Product specified in the Product
Name field on the Transportation Policies table).
If you do not provide a value for this field and the Transportation Policy is product-
specific, the Product Name field is used to look up the Class on the Products table. If
neither Class nor Product Name is specified for the Transportation Policy, a message is
displayed: "Rate request data missing".

Distance
Type: Number
Enter the distance between the source and destination. The software will estimate the
distance for your sites (using latitude and longitude in the Sites table), if you click the in-
cell button.

Transport Time
Type: Number or Distribution
Enter the length of time that a shipment takes to travel from the Source site to
Destination site. This field can accept a properly formatted probability distribution or
simple time units. The default time unit is Day. If a probability distribution is used, the
distribution is sampled and a different transport time is determined for each shipment.
Transport Time is not a required field for any transportation policy. If no time is entered,
a default will be calculated from Source site to Destination site based on the latitude and
longitude of each site, taking the speed of the transportation asset into account (Distance
/ Speed). When no asset is used in the transportation policy, the Default Transport Speed
specified on the Model Options will be used.

Asset Name
Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 49

Chapter 1 Standard Tables

Choose the asset that will transport your product. This field is necessary when using the
Full TL and Pooled policies and optional for others. You can get more information on
Assets in the Transportation Asset Table.
For Vehicle Route Optimization, you assign assets using the Asset Availability.

Days Between Replenishments

Type: Number
Specifies the number of days between receipt of additional product at the destination
site. This field is primarily used for demand propagation, and in cycle stock optimization
and safety stock optimization. For safety stock calculation, when the Service Definition is
Type 2 or Type 3, this value is used to derive the Min Replenishment Qty.

Duty
Type: Number
In this field enter a duty rate to represent the taxes and tariffs that will be levied for each
shipment on this lane. The actual duty cost is calculated by multiplying the duty rate by
the shipment’s total value (Value from the Product table multiplied by shipment quantity.)

Discount Rate
Type: Number
Enter the discount factor negotiated with the transportation company. This rate is
multiplied by the cost to determine the actual cost. The default value is 1.0 (no discount).
For example, if the negotiated discount is 30%, the discount rate is 1.0 - .30 or .70, so
you enter a discount rate of 0.70. If the cost is $100, Supply Chain Guru will multiply
0.70 by 100 to get an actual rate of $70.
Discount Rate is reflected in the Total Transportation Cost in the Network Summary
output table.

Min Charge
Type: Number
In this field enter any minimum rate negotiated with the transportation company.
Minimum rates override costs if the cost is less than the minimum charge.
Min Charge is reflected in the Total Transportation Cost in the Network Summary output
table.

Review Period
Type: Text
Enter how often the queue at the transportation lane is checked. If left blank, the queue
is evaluated every time a shipping item enters. If a review period is specified items are
queued, and then evaluated together. By default, all of the provided mode rules make
decisions of the aggregate contents of the queue. So for example, if the Mode Rule was
"On Weight", and you had a review period of 1 Day; then every day the simulation would
sum the weight of all the items in queue, and apply the mode rule to it.

50 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

The review period can be left blank, set to one value, or assigned a schedule as well. See
the table below for how to enter data:

Value Examples Parameter use

No Value As soon as an item enters the queue, it will be evaluated

by the Mode Rule.

Single 12 HR The queue is evaluated every interval value (for

Value 1 DAY example, every 12 hours).

Repeating 1 DAY, 3 DAY, 2 DAY The queue is reviewed after one day, then reviewed
Schedule again 3 days after the first review, and again 2 days
after the second review. The schedule is repeated upon
completion.

If the review period is left blank, as soon as an item enters the queue, it will be evaluated
by the Mode Rule.
If the review period has a value entered in it (i.e. 12 Hour or 1 Day etc), the mode logic
will repeat fire specified by the interval in the review period. (If the review period is 12
Hour, the queue at the transportation lane will be evaluated every 12 hours).
The review period also supports a repeating schedule. The format is the same as a single
value in the review period, except a comma is placed between the single values. An
example follows:
1 Day, 3 Day, 2 Day
In the above example, a Review of the queue will occur after one day. Then the next
review will occur 3 Days after the first review. Then the third review will occur 2 Days
after the second. When the schedule completes, it repeats itself.
Review periods themselves are dependent on the start time of simulation. For example,
assume the start time set in the Model Options is 12:00 AM 1/1/2010, and the review
period is set to 24 HR. The queue at the lane will be reviewed every day at 12:00 AM. An
offset can be entered in front of the review period to change the time the model will start
reviewing. The offset will only be incurred once.
For example, if we would like to Review the queue every day at 4 PM, and our simulation
starts at 12 AM, an offset of 16 hours can be entered to shift the review time to 4 PM.
Then, if we have 24 hour review period, it will check every 24 hours from the time to
which it was offset. The format for the offset is as follows: < "Time" >
For the a 16 hour offset, with a daily review you would enter: <16 HR>, 24 HR.
For Network Optimization, Review Period is used as part of a Days Between
Replenishments (DBR) replacement scheme when calculating cycle stock. If DBR is not
defined, Supply Chain Guru uses the maximum of Review Period or Shipment Period in
calculating cycle stock.

Note: For Transportation Policies with the same Origin – Destination combination, the
same Review Period should be used.

Shipment Period
Type: Text
Enter the schedule for a Periodic (i.e. scheduled shipment).

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 51

Chapter 1 Standard Tables

The Shipment period supports a repeating schedule. The format is the same as a single
value in the review period, except a comma is placed between the single values. An
example follows:
1 Day, 3 Day, 2 Day
In the above example, a Shipment will occur after one day. Then the next Shipment will
occur 3 Days after the first Shipment. Then the third Shipment will occur 2 Days after the
second. When the schedule completes, it repeats itself.
Shipment schedules themselves are dependent on the start time of simulation. So if the
start time set in the Model Options is 12:00 AM 1/1/2010, and the Shipment period is set
to 24 HR. The Shipments will depart every day at 12:00 AM. An offset can be entered in
front of the Shipment schedule to change the time the shipments depart. The offset will
only be incurred once.
For example, if we would like to ship every day at 4 PM, and our simulation starts at 12
AM; an offset of 16 hours can be entered to shift the review time to 4 PM. Then, if we
have 24 hour shipment schedule, it will check every 24 hours from the time to which it
was offset. The format for the offset is as follows: < "Time" >
For the a 16 hour offset, with a daily shipment you would enter: <16 HR>, 24 HR.
For Network Optimization, Shipment Period is used as part of a Days Between
Replenishments (DBR) replacement scheme when calculating cycle stock. If DBR is not
defined, Supply Chain Guru uses the maximum of Review Period or Shipment Period in
calculating cycle stock.

CO2
Type: Number
In this field, set the CO2 emissions for this transportation mode based on the CO2 Basis.
There is a field guru associated with the CO2 emissions field. You can enter a numeric
value, or select the Transportation Method using the field guru to retrieve the CO2
emission quantity for a specific vehicle type. By default, the CO2 Basis is weight-distance,
therefore the CO2 emission quantity is set at kg per weight unit, per unit of distance.
For example, if .04 is entered, then this is .04 kg of CO2 per one unit of weight of product
moved over one mile by this transportation mode.

CO2 Basis
Type: Special
Use this field to select the basis for determining CO2 emissions. Typically, this is weight-
distance, but you can select one of the other values as shown:

CO2 Basis CO2

Weight CO2 * Product Weight

Qty CO2

Cubic CO2 * Product Cubic

Distance (CO2 * Distance) / (Shipment Weight/Product Weight)

Fixed CO2 / (Shipment Weight/Product Weight)

Weight-Distance CO2 * Product Weight * Distance

52 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

Qty-Distance CO2 * Distance

Cubic-Distance CO2 * Product Cubic * Distance

Animation Graphic
Type: Special
Defines the graphic used if animation is enabled on the Geo Map during simulation. As
the shipment makes a journey from source to destination, this graphic will travel along
the path of travel.

Graphic, Graphic Size, Graphic Color

Type: Special
In this text field, choose a graphic to represent the shipment from source site to
destination site. The graphic will be used in the animation of the simulation of the supply
chain. Also select the Color and Size of the graphic.

Network Flow Graphic, Network Flow Graphic Size, Network Flow

Graphic Color
Type: Special
In this text field, choose a graphic to represent the shipment from source site to
destination site within a network flow. The graphic will be used in the animation of the
simulation of the supply chain. Also select the Color and Size of the graphic.

Load Cost
Type: Number
Cost to load a complete order onto the transportation asset. This cost is only triggered
when assets are defined on a Transportation Policy.
Optimization: Takes the number of trips traveled by an asset type and applies the load
cost to each individual trip. This cost is reported in the Variable Cost field of
Transportation Assets Summary Optimization Output.
Simulation: Applies the load cost to each individual order.
Load Cost is reflected in the Total Transportation Cost in the Network Summary output
table.

Unit Load Cost

Type: Number
Cost to load one unit of product.

Unload Cost
Type: Number
Cost to unload a complete order from the transportation asset. This cost is only triggered
when assets are defined on a Transportation Policy.
Optimization: Takes the number of trips traveled by an asset type and applies the unload
cost to each individual trip. This cost is reported in the Variable Cost field of
Transportation Assets Summary Optimization Output.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 53

Chapter 1 Standard Tables

Simulation: Applies the unload cost to each individual order.

Unload Cost is reflected in the Total Transportation Cost in the Network Summary output
table.

Unit Unload Cost

Type: Number
Cost to unload one unit of product.

Load Time
Type: Time
Time taken for the product to be prepared for dispatch.

Unload Time
Type: Time
Time taken for the product to be unloaded.

Load Unit Time

Type: Time
The amount of time to load each individual unit of product.

Unload Unit Time

Type: Time
The amount of time to unload each individual unit of product.

Ship To
Type: Text
If the Ship To field is used in a transportation policy it means that the Source-Destination
lane becomes a virtual lane. The Source does not ship directly to the Destination, but it
ships to the site specified in the Ship To field (the end destination of the route is still the
site specified in the Destination Site field). Transportation policies for the Source - Ship To
and Ship To - Destination site combinations need to exist in the transportation policies
table.

Load Resource
Type: Special
Select the work resource used to load the shipment. The work resource must be listed in
the Work Resource Table.

Unload Resource
Type: Special
Select the work resource used to unload the shipment. The work resource must be listed
in the Work Resource Table.

54 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

Auto-Release Load Resource

Type: Yes/No
Select Yes if the work resource used for loading is to be automatically released and
becomes immediately available for loading.

Auto-Release Unload Resource

Type: Yes/No
Select Yes if the work resource used for unloading is to be automatically released and
becomes immediately available for unloading.

Require Return Trip

Type: Yes/No
If an asset is used in the transportation policy, this field specifies if the asset must require
a return trip.

Return Trip Time

Type: Number
If an asset requires a return trip, this is the time it takes for asset to travel from final
destination to initial start point.

Return Trip Cost

Type: Number
If an asset is used in the transportation policy, this field specifies the cost for the asset to
return to the Source Site. This cost is reported in the Variable Cost field of Transportation
Assets Summary Optimization Output.

Flow Reqt
Type: Number
Enter the amount of this product required for shipment over the transportation lane. Its
use is determined by three other flow requirement fields listed below; Flow Requirement
Type, Flow Requirement Basis and Flow Requirement Period.
Flow refers to the amount of product moved by this transportation policy in a given time
period. Flow Requirement fields are only used in an optimization; a simulation run will
ignore these four fields. An optimization will use flow requirements as constraints.

Flow Reqt Type

Type: Text
Choose the flow requirement type - conditional minimum, minimum, maximum, or fixed.
This defines how the Flow Requirement is used in an optimization. The conditional
minimum flow establishes that, in order to use this transportation lane for any shipments,
a minimum flow is necessary. Essentially this constraint is similar to saying the flow can
be 0 or higher than the minimum.

Flow Reqt Basis

Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 55

Chapter 1 Standard Tables

Choose the flow requirement basis - Quantity, Weight or Cubic. This defines the units of
measurement for the flow requirement.

Flow Reqt Period

Type: Text
Choose the period over which the Flow Requirement is to be established - Day, Week,
Month, Quarter, or Year. When left blank the horizon of the optimization will be used as
the Flow Reqt Period.

Note: When setting Flow Requirements for non-product specific transportation policies,
the requirement applies to each individual product. Aggregate flow requirements
can be specified on the Aggregate Flow Constraints data table.

Lane Name
Type: Text
Specify a name for this transportation lane that can be used in user-defined Mode
Selection Rule scripts.

Path Name
Type: Text
Enter the name of the transportation path. You define the detailed path in the
Transportation Paths table.

Lane Consignment Queue Basis

Type: Special
Specifies the basis by which the lane consignments are reported. Select from item,
quantity, weight, cubic, or value.

Mode Consignment Queue Basis

Type: Special
Specifies the basis by which the mode consignments are reported. Select from item,
quantity, weight, cubic, or value.

Chance for Ambush

Type: Number or Distribution
This field specifies the percent of time that an ambush will occur. It is interpreted as a
percentage. It can be defined as a number or as a distribution.

Ambush Delay
Type: Text
When an ambush occurs, this specifies how long the shipment will be delayed.

Ambush Damage
Type: Number or Distribution

56 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies

This field specifies the percent of vehicles destroyed when an ambush occurs. It is
interpreted as a percentage. It can be defined as a number or as a distribution.

Reorder When Destroyed

Type: Yes/No
This field gives you a choice to place an immediate "replacement" order to make up for a
destroyed shipment. When this field is "Yes", Supply Chain Guru places an order that has
the same characteristics (due date, qty, product type, etc.) of the destroyed shipment.
When this field is "No", nothing is done.

Unit Delay Factor

Type: Number or Distribution
Specify the unit delay factor for surviving members of an ambushed convoy. This factor is
multiplied by the number of destroyed vehicles in the event of an ambush. You can
provide a constant, such as 2 hours, or a distribution.

Delay Factor
Type: Number or Distribution
Specify the order delay factor for surviving members of an ambushed convoy.

Minimum Shipment Quantity

Type: Number
In Safety Stock Optimization, the Minimum Replenishment Quantity is the maximum of
the Sourcing Policies Min Order Qty and the Transportation Policies Minimum Shipment
Quantity.

Minimum Service Time

Type: Number
Specifies the constraint for the minimum service time on the lane. This time is in units of
DAY. Enter the number of days (do not specify a time unit).

Maximum Service Time

Type: Number
Specifies the constraint for the maximum service time on the lane. This time is in units of
DAY. Enter the number of days (do not specify a time unit).

Guaranteed Service Time

Type: Text
The Guaranteed Service Time is used to determine if the Source site can ship the Product
to the Destination on the defined Mode within this time frame. If this is not possible, the
order is considered to have been missed and the Fill Rate may decrease. The Guaranteed
Service Time is in terms of days. It is calculated on a Source-Destination-Product-Mode
basis.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 57

Chapter 1 Standard Tables

Transportation Assets
Name
Type: Text
Enter a unique name for each asset in your model.

Units
Type: Number
Enter the number of units of this asset that are available for use in the network. Units
must be a whole number (i.e., you cannot have half a truck). When optimizing, the
number of units entered in this field will act as a max number of asset units. The software
will automatically determine the optimal number of transportation assets. The results will
be in the Asset Summary Optimization Output table.

Note: Be sure to specify the Asset being used in the Asset field of the Transportation
Policies data table.

When specifying the number of assets for use with Vehicle Route Optimization,
use the Available Quantity field on the Asset Availability table.

Type
Type: Special
Select either Vehicle or Container. An asset is considered a vehicle if it is able to move
from one node to another, such as a Truck, Boat, Plane or Train. An asset is a container if
it can be loaded with product, but cannot move between sites on its own, such as a pallet
or railcar.

Unit Fixed Cost

Type: Number
Enter the total cost of owning or using each unit of this asset. Unit Fixed Cost is the fixed
cost of using this asset. For example, this could be the cost of maintaining a vehicle in the
fleet, or yearly administrative costs for operating it.

Note: If you do not specify either a Unit Fixed Cost or Hourly Cost Cap on Transportation
Assets, the optimized number of units will always equal the number of Units set on
the Transportation Assets input table. The Transportation Asset Utilization in the
Transportation Asset Summary optimization output table will therefore be
reported as 1 (fully utilized).

Unit Fixed Cost is reflected in the Total Transportation Asset Cost in the Network
Summary output table.
Vehicle Route Optimization: Enter the fixed cost incurred for the asset for the model
horizon. For example, if your model horizon is a week and the annual fixed cost for an
asset is 80,000, the Unit Fixed Cost should be 1,538.

Hourly Cost Cap

Type: Pairs

58 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Assets

The hourly cost is the cost of using this asset. This can be used, for example, for driver
wages that are based on how many hours a vehicle is in use. Specify the <Cap,Cost>
structure per hour for this asset.

Note: If you do not specify either a Unit Fixed Cost or Hourly <Cap,Cost> on
Transportation Assets, the optimized number of units will always equal the number
of Units set on the Transportation Assets input table. The Transportation Asset
Utilization in the Transportation Asset Summary optimization output table will
therefore be reported as 1 (fully utilized).

Hourly Cost is reflected in the Total Transportation Asset Cost in the Network Summary
output table.

Capacity Period
Type: Text
Choose the period (Day, Week, Month (30 day), Quarter (91 day), or Year) over which the
Hourly <Cap,Cost> structure applies to for this asset. If no Capacity Period is specified,
the default is the model period length.

Expansion Only
Type: Yes/No
If set to Yes, then the available number of assets cannot be less than in any previous
period.

Apply Fixed Cost to Horizon

Type: Yes/No
During a multi-time period optimization, if Apply Fixed Cost to Horizon is set to Yes, then
the unit fixed cost will be used throughout the duration of the optimization time period.

Weight Fill Level

Type: Number
Simulation: Enter the weight at which your asset is considered full enough to be
dispatched. The Weight Fill Level acts as a trigger for certain Transportation Policies.
Network Optimization: The fill levels are used as the average asset load size (rather than
the capacities) in determining the number of trips the asset makes. If you have specified
more than one Fill Level for an asset (such as Weight Fill Level and Quantity Fill Level),
the more constraining level is used.
Vehicle Route Optimization: The fill level is the minimum shipment weight that must be
on the asset.

Weight Capacity
Type: Number
Enter the maximum weight your asset is capable of holding. Not used for Network
Optimization.

Note: Weight Capacity must be greater than or equal to the Weight Fill Level. These
fields work hand-in-hand when you create your Transportation Policies. If Weight

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 59

Chapter 1 Standard Tables

Capacity and Weight Fill Level are the same number, your asset will only be
dispatched when it is 100% full. On the other hand, if your Weight Fill Level is 100
pounds and your Weight Capacity is 200 pounds, then your asset will be
dispatched when it is 50% full.

Simulation: Weight Capacity is only used in Simulation for tracking individual assets.
Vehicle Route Optimization: This is the maximum weight that can be loaded on the asset.

Cubic Fill Level

Type: Number
Simulation: Enter the cubic volume at which your asset is considered full enough to be
dispatched. The Cubic Fill Level acts as a trigger for certain Transportation policies.
Network Optimization: The fill levels are used as the average asset load size (rather than
the capacities) in determining the number of trips the asset makes. If you have specified
more than one Fill Level for an asset (such as Weight Fill Level and Quantity Fill Level),
the more constraining level is used.
Vehicle Route Optimization: The fill level is the minimum shipment cubic volume that
must be on the asset.

Cubic Capacity
Type: Number
Enter the maximum cubic volume your asset is capable of holding. Not used in Network
Optimization.

Note: Cubic Capacity must be greater than or equal to the Cubic Fill Level. These fields
work hand-in-hand when you create your Transportation policies. If Cubic Capacity
and Cubic Fill Level are the same number, your asset will only be dispatched when
it is 100% full. On the other hand, if your Cubic Fill Level is 100 ft cubed and your
Cubic Capacity is 200 ft cubed, then your asset will be dispatched when it is 50%
full.

Simulation: Cubic Capacity is only used in Simulation for tracking individual assets.
Vehicle Route Optimization: This is the maximum cubic volume that can be loaded on the
asset.

Quantity Fill Level

Type: Number
Simulation: Enter the number of products that this asset must transport in order to be
dispatched for shipment.
Network Optimization: The fill levels are used as the average asset load size (rather than
the capacities) in determining the number of trips the asset makes. If you have specified
more than one Fill Level for an asset (such as Weight Fill Level and Quantity Fill Level),
the more constraining level is used.
Vehicle Route Optimization: The fill level is the minimum shipment quantity volume that
must be on the asset.

60 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Assets

Quantity Capacity
Type: Number
Enter the maximum number of products that this asset can transport. Not used in
Network Optimization.

Note: Quantity Capacity must be greater than or equal to the Quantity Fill Level. These
fields work hand-in-hand when you create your Transportation policies. If Quantity
Capacity and Quantity Fill Level are the same number, your asset will only be
dispatched when it is 100% full. On the other hand, if your Quantity Fill Level is
100 ft cubed and your Quantity Capacity is 200 ft cubed, then your asset will be
dispatched when it is 50% full.

Simulation: Quantity Capacity is only used in Simulation for tracking individual assets.
Vehicle Route Optimization: This is the maximum quantity that can be loaded on the
asset.

Comp2 Quantity Capacity

Type: Number
Enter the maximum quantity that can be held in the second compartment of the asset.
Shipments that have Comp2 Quantity values populated can be loaded into the second
compartment of the asset during Vehicle Route Optimization.

Comp2 Weight Capacity

Type: Number
Enter the maximum weight that can be held in the second compartment of the asset.
Shipments that have Comp2 Weight values populated can be loaded into the second
compartment of the asset during Vehicle Route Optimization.

Comp2 Cubic Capacity

Type: Number
Enter the maximum cubic volume that can be held in the second compartment of the
asset. Shipments that have Comp2 Cubic values populated can be loaded into the second
compartment of the asset during Vehicle Route Optimization.

Speed (Dist per Hour)

Type: Number
Enter the speed at which your asset can travel in miles or kilometers per hour. If a speed
is not entered, the default speed set in the Model Options will be used for calculations.

Asset Weight
Type: Number
Enter the weight of the transportation asset. This is the weight of the actual asset. When
using containerization the weight of the shipment and the asset are taken into account.

Asset Cubic
Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 61

Chapter 1 Standard Tables

Enter the volume of the transportation asset. This is the volume of the actual asset,
which is distinctly different from the volume capacity of the asset.

Units is Integer
Type: Yes/No
Enter Yes if the asset can only be an integer.

Shipping Route
Type: Special
If there is a specific route this asset should take, select it in this field. The drop-down list
is automatically populated from the Shipping Routes table.

Unit Selection Rule

Type: Special
This drop down menu allows you to select a rule for determining which single asset in this
asset group to use – First Available, Minimize Assets, Local Only, Closest Available, or
create a Custom Rule in the Scripts Table.

Shift Pattern
Type: Special
This causes the site to ship and receive orders only during its specified work times, just
like work centers. Likewise, Transportation Assets are only available for transport when
they are working.

Asset Home Base

Type: Special
Select the home location for this asset. This is the site which "owns" the asset. The site
must be listed in the Sites Table.

On Idle Behavior
Type: Special
Select the policy to designate what the transportation asset should do once it has
completed the delivery of a shipment or completed its shipping route. From the drop
down menu, select one of the following policies:
 Go to Home – Return to the location listed in the Asset Home Base Field
 Return to Start – Return to the starting location for that shipment
 Stay Put – Remain at the site that it became idle
 Go to Location – Travel to the site listed in the On Idle Location Field
 Destroy Unit – Asset is no longer a part of the model. It is removed from further
tracking and data collection

On Idle Location
Type: Special

62 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Assets

Select the site for this asset to travel to once it has completed its shipment or shipping
route. This site must be listed in the Sites Table.

Waiting Consumer Queue Basis

Type: Special
Defines the basis from which asset loading queues are defined in the simulation output.
Unit type, quantity, cubic, weight, or value can be used for reporting.

On Available Event Handler

Type: Special
This is the logic to tell an asset what to do once it becomes available. You define the logic
in a custom script with a Type of “Asset OnAvailable Event”. Scripts of this type will be
available in the dropdown list for this field. On Available behavior is different from the On
Idle behavior because an asset only becomes Idle after a shipment. For example, if the
On Idle behavior is to GO HOME, at the end of a shipment the asset would do that. The
On Available event would fire upon arrival.

Vulnerability Factor
Type: Number
This allows you to weight the vulnerability of different assets. It only applies if an asset is
part of a convoy with multiple asset types when an ambush occurs. For example, there
are 5 assets in a convoy: 3 of type A and 2 of type B. Asset A has a Vulnerability Factor of
100 and Asset B has a Vulnerability Factor of 50. Asset A is therefore twice as likely to be
destroyed if an ambush occurs.

Max Stops Per Route

Type: Number
This field specifies the maximum number of customer locations on a route. Vehicle
domiciles and warehouses are not included in this number. See Modeling Transportation
Assets.

Max Distance Between Stops

Type: Number
This field specifies the maximum distance between any consecutive pair of pickup or
delivery stops on the route for this transportation asset. It is not applied to the distance
between the warehouse and other locations. For example, Max Distance Between Stops is
not applied in the following situations:
 From the equipment home location to the warehouse.
 From the warehouse to the first delivery.
 From the last pickup back to the warehouse in a backhaul. If there is no pickup on the
route, it is not applied to the last delivery back to the warehouse.
Any segment that has a warehouse as an end node ignores this constraint in Standard
VRP and Backhaul.

Min Distance Between Stops

Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 63

Chapter 1 Standard Tables

This field specifies the minimum distance between any consecutive pair of non-warehouse
stops on the route for this transportation asset. If the actual distance is lower than this
value, the distance is set to this value. It is not applied to the distance in the following
situations:
 From the equipment home location to the warehouse (DC).
 From the warehouse (DC) to the first delivery.
 From the last pickup back to the warehouse (DC) in a backhaul. If there is no pickup
on the route, it is not applied to the last delivery back to the DC.
That is, any segment that has a DC as an end node ignores this constraint in Standard
VRP and Backhaul.

Max Total Distance Per Route

Type: Number
This field specifies the maximum total distance of a complete route. This is from the
equipment location to the warehouse, all in-transit legs, and the return to the equipment
home location if the route is round trip.

Max Time Per Route

Type: Text
This field specifies the maximum travel time for a complete route. This is from the
equipment home location to the warehouse, all in-transit legs, and the return to the
equipment home location if the route is round trip. The default unit for time fields is DAY.

Max Waiting Time At Location

Type: Text
This field specifies the maximum extra waiting time allowed at each delivery location, due
to combining multiple shipments which may have different delivery times. It is used to
check if shipments with same destinations could be combined in the same truckload. Not
applicable if there is only one shipment delivered at each location.
The duration from the Arrival Time to the first Delivery Time cannot exceed this value.
Also, the duration from the first delivery to the last delivery cannot exceed this value. The
default time unit is DAY.

Is Default
Type: Yes/No
Set this field to Yes if this is the default equipment type. When there is no equipment
found within the radius value of Max Equipment Distance for a warehouse site, the default
equipment type is used. There must be NO MORE THAN ONE record defined as the
default. There is NO LIMIT in the available quantity of default equipment. Default
equipment type starts routes from the first pickup location.
Default = No

Is Round Trip
Type: Yes/No
Set this field to Yes when the equipment must return to the equipment location at the end
of a trip.

64 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Assets

Default = No

Max Duty Time Per Shift

Type: Text
Specifies the maximum amount of time a driver can be on duty without a break per shift
(A shift is usually a day or a 24 hour period). Duty time includes drive time, non-drive
working time, and wait time. This is the maximum number of hours for regular duty time
and maximum number of hours of overtime per shift. The default unit for time fields is
DAY.

Note: If you specify Max Duty Time Per Shift, an overnight break of at least Min Break
Time Between Shifts will be taken at the end of the shift. If you do not enter a
value for Min Break Time Between Shifts, the “overnight” break will have no
duration.

Max Drive Time Per Shift

Type: Text
Specifies the maximum amount of time a driver can drive per shift without a long break.
A long break is one that is long enough to sleep. The default unit for time fields is DAY.
When specifying driver hours of service constraints, do not set any of the “Maximum”
field values, such as Max Drive Time Within Shift, to 0. This can cause unexpected routing
results, including violation of other driver hours of service constraints.

Min Break Time Between Shifts

Type: Text
Specifies the minimum amount of time a driver must be off duty before being on duty
again. This break must be long enough to sleep. The default unit for time fields is DAY.

Max Drive Time Within Shift

Type: Text
Specifies the maximum amount of time a driver can drive continuously without a short
break. Short breaks are calculated if this field and Min Break Time Within Shift are both
populated. The default unit for time fields is DAY.
When specifying driver hours of service constraints, do not set any of the “Maximum”
field values, such as Max Drive Time Within Shift, to 0. This can cause unexpected routing
results, including violation of other driver hours of service constraints.

Min Break Time Within Shift

Type: Text
Specifies the minimum amount of time a driver needs to break before he can continue to
drive within a shift. This break is incurred after the amount of drive time defined by Max
Drive Time Within Shift is incurred. Short breaks are calculated if this field and Max Drive Time
Within Shift are both populated. The default unit for time fields is DAY.

Fixed Service Time at Stop

Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 65

Chapter 1 Standard Tables

Specifies the fixed amount of service time when the equipment stops at a delivery
location; not applicable at a warehouse. The default unit for time fields is DAY. See
Modeling Transportation Assets.

Variable Service Time at Stop

Type: Text
Specifies the variable amount of service time when the equipment stops at a delivery
location; not applicable at a warehouse. The total service time at a delivery stop = Fixed
Service Time at Stop + Variable Service Time at Stop x total quantity/ weight/cubic
value, which is defined by the Key Unit of Measure in Vehicle Route Optimization Options
dialog (default is quantity). The default unit for time fields is DAY.

Max Distance from Warehouse

Type: Number
Specifies the maximum distance from the warehouse that the equipment can be in service.

Min Time Between Stops

Type: Text
Specifies the minimum travel time between two consecutive stops on a route, excluding
segments that have a warehouse as an end node. If the actual time is lower than this
value, the travel time is set to this value. The default unit for time fields is DAY.
It is not applied to the travel time in the following situations:
 From the equipment home location to the warehouse.
 From the warehouse to the first delivery.
 From the last pickup back to the warehouse in a backhaul. If there is no pickup on the
route, it is not applied to the last delivery back to the warehouse.

Min Time Between Routes

Type: Text
Use this field to define the minimum time that must occur between the routes assigned to
an asset. This is the time from the end of one route (the End Date Time of one route to
the Start Date Time of the next route on the asset). The default unit for time fields is DAY.

Max Time Per Asset

Type: Text
Use this field to define the maximum time for routes assigned to an asset when using
Asset Optimization. This time is from the Arrive Date Time at the first stop on the first
route to the Leave Date Time at the last stop on the last route assigned to the asset. If
Max Time Per Asset is null, the length of the vehicle route optimization horizon is used as
the maximum time per asset. The default unit for time fields is DAY.

Max Out Of Route Percent

Type: Number
This field defines a percentage to constrain how far apart stops within a route can be. The
out of route percent value is calculated as:
(Traveled Distance - Direct Distance)/Direct Distance

66 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Groups

where
 Traveled Distance is the sum of the distances between all stops on the route.
 Direct Distance is the distance from the pool site to the furthest customer, and
multiplied by 2 if it is a round trip.
For example, if you want to limit the out of route percentage to no more than 10%, enter
0.1. See Modeling Transportation Assets.

Empty Weight
Type: Number
This is the weight of an empty vehicle, also known as the “tare” weight. This weight
enables Supply Chain Guru to determine the CO2 emissions on segments of a route
where the vehicle empty.
Default value: 35000

CO2
Type: Number
In this field, set the CO2 emissions for this transportation asset based on the CO2 Basis.
This is the emission amount per weight unit assumed in your model.
There is a field guru associated with the CO2 emissions field. You can:
 Enter a numeric value, or
 Select the Transportation Method using the field guru to retrieve the CO2 emission
quantity for a specific vehicle type.
If you have selected a Transportation Method and the weight unit assumed in your model
is pounds, change the Weight Units to Pound. The CO2 value returned by the
Transportation Method is automatically recalculated.
For example, if .04 is entered, then this is .04 kg of CO2 per one unit of weight (Pound,
by default) of product moved over one mile by this transportation asset.

CO2 Basis
Type: Special
Use this field to select the basis for determining CO2 emissions. Vehicle Route
Optimization uses Weight-Distance. The total weight of the vehicle and shipments on
board per route segment are calculated for the Weight.

Groups
Name
Type: Text
Enter a unique Name to represent the group.

Type
Type: Text
Choose from the drop-down list if you want to create a group for products, sites,
customers, modes or periods.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 67

Chapter 1 Standard Tables

The “ProductSubstitution (Set Only)” value for Type in the Groups table allows you to
model product substitution.

Members
Type: Special
Click on the Field Guru button to open the Group Member Selection window up. In here
you can select from the Possible Group Members list (generated from the appropriate
data table) which products/sites/customers you want to add to the group.

Function
Type: Special
Treat as Individuals: Use this groups as a modeling short cut. Before the model is
optimized or simulated the "Treat as Individuals" groups will be expanded. For example,
assume you have 10,000 products in a model, but they all have the same sourcing
policies. Define a group with the 10,000 products in it and build the policies for the group.
The software will automatically expand the group at run time. If you have Product specific
costs, you can use Input Pipes to define them and still build the model at the group level.
Aggregate into Group: Every member of this group in the model will be "aggregated" or
rolled up into one name (the name of the group).
Set: Set is used to create a group to put a constraint on in the Aggregate constraint
tables.
It is also used in simulation to define a single lane for a "set" of products. For example,
you may have 100 "Frozen" products that need to go on a "Frozen" mode of
transportation. You can define the 100 products as a set and use that set name in the
Product name field of the Transportation Policies table. This will allow all 100 products to
be routed together.

Graphic, Graphic Color, and Graphic Size

Type: Special
In these fields, choose how you want your site to appear in the visual modeler and layout
map.

Bill of Materials
Name
Type: Text
Enter the BOM name. We suggest adding the suffix BOM to the end product name, for
example, Lemonade_BOM.

Product Name
Type: Text
Enter the name of:
 the components needed to produce the end product.
 any byproduct that is produced.

68 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Bill of Materials

 the end product. You do not need to specify the end product if one unit is produced by
the BOM, and the BOM is specified on the Make sourcing policy for the product.

Quantity
Type: Text
Enter the quantity of this component needed to produce the end product.

Note: It is also possible to create byproducts. Byproducts are materials created in

addition to the main through the production process. Byproducts must also be
listed on the Product Data Table.

By-products are listed on the network flows output tables.

In the optimization module it is possible to have demand occurring for the byproduct.
Only the byproduct units that are left over after demand is fulfilled will be discarded in
this case.

Type
Use this field to determine how the product is used in the BOM. The value will be one of:
 Component
 Byproduct
 End Product
The default is Component.

Note: End Product as a Type in the Bill of Materials table are not used in Simulation.

Bill of Materials Example

The Type "End Product" allows you to specify the amount of this End Product that results
from this BOM, so that amounts other than 1 unit can be specified. You must specify the
Make sourcing policy for this product.
When the Sourcing Policy is Make (BOM - Probability) in the Sourcing Policies table,
Supply Chain Guru will use the Policy Parameter as the percentage that the specified BOM
is used. For example, if the Sourcing Policies table is as shown below, each of three BOMs
will be used with respective probabilities of 15, 25 and 60:

Product Policy
Site Name Sourcing Policy BOM Name
Name Parameter

MFG1 Product 1 Make (BOM - Probability) 15 BOM1_Prod1

MFG1 Product 1 Make (BOM - Probability) 25 BOM2_Prod1

MFG1 Product 1 Make (BOM - Probability) 60 BOM3_Prod1

Note: Policy Parameters for Make (Process - Probability) for the same Site - Product
combination and for Make (BOM - Probability) for the same Site - Product
combination should each add up to 100, as in the example above.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 69

Chapter 1 Standard Tables

Processes
Process Name
Type: Text
Enter a descriptive name for the process you are specifying.

Process Step
Type: Text
Enter a descriptive name for this particular step of the process that you are specifying.

Next Process Step

Type: Text
Choose the next step of the process. When the process is complete, choose None or leave
the Next Process Step field blank.

Work Center
Type: Text
Choose the work center used for this step in the process.

Note: If you exclude a work center, either in the Work Centers table or through a
Scenario, processes using this work center are not excluded. The process is still
available, but it will not use the work center. In most cases, this has the effect of
making the model less costly and less constrained.

If you delete a work center, you are prompted if you want to delete rows from
dependent tables (in this case, the Processes table). However, rows are not
actually deleted from the Processes table when you confirm the deletion. Instead,
as when you exclude the work center, the work center is no longer used by
processes. The processes are still available, but they will not be using a work
center.

Routing Rule
Type: Special
Specify if there is one possible route (Single Route option) for this process or if there are
more routes possible.
Simulation: Options include Single Route, Multiple Routes (First Available), Multiple
Routes (Most Capacity) and Multiple Routes (Probability).
Optimization: The only available option is Single Route.

Routing Rule Description

Single Route Use this routing rule if there is only one possible route for
the process to use.

70 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Processes

Multiple Routes (First Simulation: When you use this rule, Supply Chain Guru
Available) selects the work center with the lowest step number. If this
work center is busy, it moves on to the next step. If the next
step is busy, it moves on to the next and so on until it
reaches the last step. If all of the steps/work centers are
occupied, then the step with the lowest step number would
be picked regardless of its queue length.

Multiple Routes Simulation: When you use this rule, Supply Chain Guru
(Most Capacity) selects the work center with the most available capacity.

Multiple Routes Simulation: Use this rule if you want to set a probability for
(Probability) each of the routes that can be used by the process. Specify
the probability value in the Routing Route Parameter field.

Using Multiple Routes

When using Multiple Routes (First Available) for a large number of shipments within a
short time frame, you may see idle work centers. This can occur if shipments are initially
assigned to one or more work centers. Once those work centers are busy with orders,
additional shipments will be queued up at the first work center (WC1). Even if another
work center (WC2) finishes, shipments are not sent to WC2 because they have already
been queued up at WC1. If another demand is scheduled after WC2 is finished producing
the first order, WC2 will then be selected.
Work center steps process orders sequentially and the order is not released until it is
complete. Each order queued up for a step must wait until the previous order is complete
or select an alternate route if available.

Routing Rule Parameter

Type: Number
This is only applicable if the Routing Rule is set to Multiple Routes (Probability). Enter the
percentage of probability that this process will use the specified Next Process Step (can
also be None). If the chance is 25% that the specified Next Process Step will be used,
enter "25".
If the Routing Rule Parameters add up to more than 100, Supply Chain Guru adjusts the
smallest percentage down to equal 100. For example, if two Processes records have
Routing Rule Parameter values of 70 and 50, the value of 70 will be used, then the 50 will
be adjusted to 30.
If the Routing Rule Parameters add up to less than 100, Supply Chain Guru adjusts them
based on their percentage of the total. For example, if two Processes records have
Routing Rule Parameter values of 60 and 15, the total is 75. The value of 60 is 80% of the
total, while 15 is 20%, so the values will be adjusted to their percentage of the total.

Status
Type: Text
Choose the process status:
 Include - This process is to be included in a simulation or optimization run.
 Exclude - This process is to be excluded in a simulation or optimization run.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 71

Chapter 1 Standard Tables

Work Time per Unit

Type: Time
Enter the process time required for each unit. This time unit can accept both probability
distributions and straight time units (SEC, MIN, HR, DAY, WK). If the process specifies
production for example, the Work Time Per Unit is multiplied by the quantity of ordered
product, to arrive at a total production time for this step.
Important: If you do not specify a time unit, the default is DAY. Note that in the Work
Centers table, if the Capacity Basis is Time, the Work Center Summary output table
Throughput Level is displayed in HOURS.
Example: The Work Time Per Unit at the Lemonade Squeezing step is 6 SEC. The total
production time per unit for 1000 lemons is 6000 seconds or 100 minutes.

Cost Per Unit

Type: Number
Enter the cost for each unit for this process step. Each step in a process can have a
different cost. For example, as an production order goes through each routing step, costs
accumulate until the order is complete. The total cost of the order is then added to the
site production cost statistics.
The Cost Per Unit is reflected in the Total Production Cost in the Network Summary output
tables.

Average Changeover Time

Type: Time
Enter the average fixed amount of time required for each order that goes through this
step. The Average Changeover Time includes time for such tasks as setup and
changeover times. It is not exclusive of the Work Time per Unit; you can have both a
fixed Average Changeover Time and a Work Time per Unit. This field accepts both straight
time (SEC, MIN, HR, DAY, WK) and probability distributions.
Important: If you do not specify a time unit, the default is DAY.
The Work Time Per Order field acts as a setup time for individual orders. For example,
assume that you have a lot size of 2, demand of 5 and a Average Changeover Time Per
Order value of 1 HR. Optimization determines the number of orders as 2.5 (that is, the
total production amount is 2.5 * the lot size). It would therefore incur a total changeover
time of 2.5 HR. The total production cost is:
(Cost Per Unit * Units) + (Setup Cost * # of orders * Average Changeover Time)

Setup Cost
Type: Number
Specify the initial costs for implementing the process step. Setup Costs are applied for
each batch, i.e. the setup costs are calculated based upon the lot size and the number of
units processed. For example, if the order is for 500 and the lot size is 100, then 5 lots
will be produced.

Note: In Optimization, the Setup Cost is applied only if the Average Changeover Time
has a value > 0; that is, no cost is incurred if the changeover is instantaneous. In

72 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Processes

Simulation, the Setup Cost is incurred for each lot, regardless of the value of Work
Time Per Order.

The Setup Cost is reflected in the Total Production Cost in the Network Summary output
tables.

Work Time Per Order

Type: Time
Enter the fixed amount of time required for each order that goes through this step,
regardless of the production quantity. The Work Time per Order includes time for such
tasks as setup and changeover times. It is not exclusive of the Work Time per Unit; you
can have both a fixed Work Time per Order and a Work Time per Unit. This field accepts
both straight time (SEC, MIN, HR, DAY, WK) and probability distributions.
Important: If you do not specify a time unit, the default is DAY.
The Work Time Per Order field acts as a setup time for individual orders. For example,
assume that you have a lot size of 2, demand of 5 and a Work Time Per Order value of 1
HR. You will have 3 orders - 2 orders for 2 units and 1 order for 1 unit. Each of these
three orders incurs the 1 HR of Work Time Per Order added to the total production cost.
Keep in mind that the number of orders calculated is based on each demand order
specified. If you have 5 units of demand on March 14, this would be 3 orders and 7 units
on March 21 would be 4 orders based on the example lot size. The demand is not
summed up over the horizon to calculate the number of orders.
The total production cost is:
(Cost Per Unit * Units) + (Setup Cost * # of orders * Work Time Per Order)

Move Time
Type: Time
Enter the amount of time it takes to move the product from this process step to the next
in case a next process step is specified in the Next Process Step field.
Important: If you do not specify a time unit, the default is DAY.

Lot Size
Type: Number
Enter the lot size for this process step. The lot size is used to break up a production
quantity into smaller amounts. For example, if a production quantity of 1000 starts a
process step with a lot size of 100, the production item will cause 10 items of 100 each to
be produced.
To enforce an integer number of production lots:
 The Process must have a Work Center defined, and
 You must select the “Enforce integer number of production lots” optimization option
(on the Modeling Options tab).
For example, you would need both these conditions to be met if your Lot Size is 100,
Demand is 750, and you expect the production to be 800 (a multiple of 100).

Yield
Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 73

Chapter 1 Standard Tables

Enter the loss factor due to this process step. For example, if 10% of the material that
was input to a cutting production step (making skewed edges straight) is lost due to the
cutting, the yield factor is equal to 0.9: 90% of the material that was inputted is
outputted after this production step. Demand (from a customer/facility or input of the
next work center) determines the net production, that is the amount that needs to be
output of a certain work center. The input needed at a work center (gross production) is
calculated from the demand and the yield value.

Resource
Type: Text
Choose the work resource that will be assigned to this process step.

Minimum Lot Size

Type: Number
Use this field to enforce a minimum batch size in the process. The Minimum Lot Size
enables you to specify the minimum number of units that must be produced at a time. It
prevents a process step from producing if this threshold is not met. In contrast, the Lot
Size field serves as a capacity (breaking quantities into pieces if necessary).

Resource Usage Hours

Type: Number
Specify the number of hours the resource is used for this process step.

Graphic, Graphic Color, Graphic Size

In these fields, choose how you want your processes to appear. Graphic Size is measured
in points.

Note: It will be helpful to be consistent when choosing how your processes appear. For
example, you could choose to represent all manufacturing processes with a red
triangle 10 points in size and all packaging processes with blue squares 8 points in
size.

Work Centers
Name
Type: Text
Enter a unique name for your work center.

Site
Type: Text
Enter the facility where this work center is located.

Status
Type: Special

74 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Centers

The status field defines whether this work center will be included, considered, or excluded
during optimization runs.

Type
Type: Special
This field enables you to specify whether this is an existing work center or a potential
work center. Along with the status, this field will determine which of the fixed startup
cost, fixed operating cost, and closing cost fields will be incurred during the network
optimization run.

Capacity Basis
Type: Text
Choose the unit measure you will use to determine the dimension of shipment capacity in
the Fixed Startup <Cap,Cost> and Fixed Operating <Cap,Cost> fields. Valid choices are:
 Quantity
 Weight
 Cubic
 Time

Note: If the Capacity Basis is Time, the unit of measure in the Fixed Startup and Fixed
Operating graphs for capacity is HOURS. Be careful of the capacity basis that you
set. Typically, you would use "Day" if you are using "Time" as the basis.
Remember that the basis is used to figure out the total aggregate capacity. If the
start and end is set to be 1 year apart (in Model Options), you are running for 365
days. If you then set the basis to "Time" and period to "Day", the cap/cost is in
daily running hours for the work center.

In this case, if you set "8" as the capacity, the total hours available for the work
center for the year at that level is 365 * 8.

This capacity is consumed by work times specified in the Processes Table, enabling you to
model rough cut capacity.
The time per unit is multiplied by the total flow to get the total capacity required for flow.
For example, if the solution has 500 units of P1 getting produced on WC1, and the cycle
time is 5 minutes per unit, the total capacity required = 5 * 500 / 60 hours of capacity.

Capacity Period
Type: Text
Choose the period (Day, Week, Month (30 day), Quarter (91 day), or Year) over which the
cost numbers in the Fixed Operating <Cap,Cost> field is applied. If no Capacity Period is
specified, the default is the model period length.
The Fixed Startup <Cap,Cost> is applied over the model horizon.
If no Capacity Period is specified, the default is the model period length.

Fixed Startup <Cap,Cost>

Type: Number or Function

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 75

Chapter 1 Standard Tables

Enter a function that defines the relationship between startup capacities and startup cost.
The function is specified by a series of coordinates. The first number in the coordinate
indicates shipment capacity. The second number indicates the startup cost.
For example, an entry of <0, 1000000> <500000, 2000000> <750000, 2500000>
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, 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 Costs are always applied to the optimization horizon.
The Fixed Startup Cost is reflected in the Total Fixed Startup Cost in the Network
Summary output tables.

Fixed Operating <Cap,Cost>

Type: Number or Function
Enter a function that defines the relationship between operating capacity and operating
costs. The function is specified by a series of coordinates. The first number in the
coordinate indicates production capacity. The second number indicates operating cost.
For example, an entry of <0,1000000><500000, 2000000> <15000000,INF> indicates
that there is an initial operation cost of $1,000,000 before any product is produced. In
order to get capacity to more than 500,000, the operating cost increases to $2,000,000.
The maximum capacity is 15,000,000 as indicated with a cost of infinite (INF). If the cost
is INF for a certain capacity level, that capacity is considered as a hard constraint.
If you create capacity values that do not start with 0, the result is a conditional minimum
constraint for throughput at the work center. For example, if you enter
<100,175000><250000,INF> for the Fixed Operating value on a work center, if the work
center is used, it must have throughput of at least 100 units.
The Fixed Operating Cost is reflected in the Total Fixed Operating Cost in the Network
Summary output tables.

Closing Cost
Type: Number
Enter the monetary cost of shutting down the operations of this work center. In an
optimization, closing cost will be included if a work center with the type Existing Work
Center is closed.
The Closing Cost is reflected in the Total Closing Cost in the Network Summary output
table.

Apply Fixed <Cap,Cost> To Horizon

Type: Yes/No
Select Yes or No from the drop down menu. When it is set to Yes, the specified Cost and
Capacity structure for the Fixed Operating Costs is applied over the total length of the
optimization. When periods are specified in the Multi-Time Periods Table, and this field is
set to No, the Cost and Capacity structure will be applied to each individual period.

Expansion Only
Type: Yes/No

76 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Centers

Select Yes if this optimization is for expansion only.

Capital Investment Basis

Type: Special
Select the basis to be used for the Capital Investment <Cap,Cost> value(s). Select one
of:
 Quantity
 Weight
 Cubic
 Time

Capital Investment <Cap,Cost>

Type: Pairs
Enter one or more sets of capacity and capital investment pairs in the format:
<capacity1,cost1><capacity2,cost2><capacity3,cost3>
For example, if the capital investment for throughput up to 1000 is 500, and 250 for
throughput up to 5000, you would enter:
<1000,500><5000,250>
You can also use the field guru to input multiple values.

Note: INF is not allowed as a value for Cost. Use the Fixed Operating <Cap,Cost> field if
you want to constrain the capacity.

The Capital Investment Cost is reflected in the Total Capital Investment in the Network
Summary output table.

Book Value
Type: Special
Enter the value of the facility 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
Type: Special
Select the depreciation schedule you want to use:
 5 Year Straight-line
 10 Year Straight-line

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 77

Chapter 1 Standard Tables

Queue Capacity
Type: Number
Enter the maximum number of production orders allowable in the queue leading up to the
work center. If the value is set to INF, there are no limits on how many production items
could be queued up waiting for production. If the Queue Capacity is reached, production
items that are routed to this work center will be blocked, and will not move until queue
capacity is available.

Queue Selection Rule

Type: Special
Choose the way new orders will be lined up in the queue for this work center. For the FIFO
(first in first out) option, orders are queued in the order in which they arrive. In case
there are multiple routes specified for this work center in the Processes Table, the First
Available Resources rule checks which route will have the resources needed available the
soonest and queues the order accordingly (resources used by work centers are specified
on the Processes Table). The Queue Only rule only puts the orders into a queue, but does
not trigger the production of any, it is assumed that this is taken care of through a script
(Scripts Table) when Queue Only is selected.

Planning Capacity
Type: Number
Enter the planning capacity value for this work center. This value is not used by the
simulation logic; rather, it is a model variable which is visible to be used in the model’s
scripts.

Changeover Table
Type: Special
This field is used to associate a work center changeover table with this work center.

Shift Pattern
Type: Special
Enter the shift pattern, such as 3 Shifts/7 Days or 2 Shifts/5 Days, for this work center.

Work Resources
Name
Type: Text
Enter a unique name for your work resource.

Site Name
Type: Text
Specify the site where this resource is used.

78 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Center Changeovers

Units
Type: Number
Enter the number of identical units of this resource available to perform work. It must be
a whole number.

Expansion Only
Type: Yes/No
If set to Yes, then the available number of resources cannot be less than any previous
period.

Unit Fixed Cost

Type: Number
Enter the fixed unit cost for each work resource. This is the fixed cost of a work resource, such
as the general/administrative costs per worker for the horizon of the model.
The Unit Fixed Cost is reflected in the Total Work Resource Cost in the Network Summary
output tables.

Hourly Cost Cap

Type: Text
This is the hourly cost of a work resource. Generally, it is used for the hourly wages of
workers. Specify the <Cap,Cost> structure per hour for this resource.
The Hourly Cost is reflected in the Total Work Resource Cost in the Network Summary
output tables.

Capacity Period
Type: Text
Choose the period (Day, Week, Month (30 day), Quarter (91 day), or Year) over which the
specified Hourly <Cap,Cost> structure applies to for this resource. If no Capacity Period
is specified, the default is the model period length.

Waiting Consumer Queue Basis

Type: Special
Specify the unit by which the consumer queue is reported, either by item, quantity,
weight, cubic, or value.

Work Center Changeovers

Name
Type: Text
Enter a unique name for your work center changeover table.

Changeover Table
Type: Special

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 79

Chapter 1 Standard Tables

Click on the field guru in the field to open the table record editor, where you can enter the
specific changeover values. For each ID, enter:
 Current Product – Select the Product name from the dropdown list.
 Previous Product – Select the Product name from the dropdown list.
 Changeover Time – Enter the time required to changeover the work center from the
Previous Product to the Current Product. The default time unit is DAY.

Current Product
Type: Text
Select the current product in this field.

Previous Product
Type: Text
Select the previous product in this field.

Changeover Time
Type: Number/Distribution
The delay time that will occur when this specific current/previous product combination
occurs at any work center using this table.

Production
Production Site
Type: Text
Enter the Facility Site that will be producing the product.

Product Name
Type: Text
Enter the name of the product to be produced.
A Tip: You can select your Production Site and Product Names from the drop-down list or
enter the first few letters of the product or site and the software will find the first match
from the drop-down list.

Quantity
Type: Number
Enter the quantity of product to be produced. A probability distribution can be specified
by clicking on the field guru button in the cell.

Order Time
Type: Date
Enter the date on which the production should begin.

80 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Production

Note: If you populate both Order Time and Order Time Formula, Supply Chain Guru uses
Order Time Formula when the model is run.

If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Order Time Formula

Type: Text
Enter the number or distribution that defines when the production should begin. If the
value is a number, it will be offset from the start of the model horizon by that number of
days.

Note: If you populate both Order Time and Order Time Formula, Supply Chain Guru uses
Order Time Formula when the model is run.

If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Due Date
Type: Date
Used to specify the date by which a production must be completed. You can alternatively
use the Due Date Formula field to define a number or distribution to define the date for
production completion.

Note: If you populate both Due Date and Due Date Formula, Supply Chain Guru uses
Due Data Formula when the model is run.

If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Due Date Formula

Type: Text
Enter the number or distribution that defines when the production must be completed. If
the value is a number, it will be offset from the start of the model horizon by that number
of days.
Due Date Formula has a Field Guru associated with it.

Note: The default Due Date Formula unit is DAY. If you do not enter a date, the software
assumes the Due Date Formula is measured in days. If Due Date Formula is left
blank, the software assumes the order is due immediately when production
occurs.
If you populate both Due Date and Due Date Formula, Supply Chain Guru uses
Due Data Formula when the model is run.

Due Date examples are in the following table:

If you want the Due Date to occur: Enter

As soon as the production begins 0 or leave blank

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 81

Chapter 1 Standard Tables

1 day after the production begins 1

On a particular day Use the Due Date field

If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Occurrences
Type: Number/Text
Enter how many times this production will occur. Production must occur at least once.
When you enter a number greater than one, production will occur multiple times.

If you want the Occurrence to take place: Enter

1 time 1

10 times 10

As long as the simulation runs INF

Time Between Orders

Type: Number or Distribution
Enter how much time must pass between each recurring production. It is directly
connected with the Occurrences. For example, Time Between Orders can be 24 HR,
meaning that production must recur every 24 hours.

Note: You must enter data in this field if the Occurrences are greater than 1. If you do
not enter Time Between Orders and production recurs, the software will assume
that this production happens once a day.

Time Between Orders examples are in the following table.

If you want: Enter

Recurring daily production 1 DAY or leave blank

Occurrences: INF

Randomly occurring production T(1,3,4) DAY

according to a triangular distribution
Occurrences: INF

Note: If you are defining production by using a pattern, you do not need to enter data in
the Occurrences or InterArrivalTime fields. The pattern specifies this for you.

Process Name
Type: Text
Specify the relevant process used in the production

82 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Production

Pattern
Type: Text
Allows patterns of production to be distributed over periods of time. The pattern
represents a predefined set of occurrences, instead of a single occurrence.

Note: If you are defining production by using the Occurrences and InterArrivalTime, you
do not need to enter data in the Pattern field.

Pattern is directly related to Quantity. The pattern you select will take the total aggregate
quantity stated in the Quantity field and spread it out, as evenly as possible, over the
desired time frame. For example, If Quantity is less than the number of occurrences in
the Pattern, the software adds additional time between the recurring production and the
production. If Quantity is greater than the number of occurrences in the Pattern, the
software evenly distributes the quantity over the entire time amount.

Note: If you specify a pattern, Quantity field must be a number. Distribution functions
are not allowed in conjunction with patterns.

Pattern examples are in the following table.

If the Quantity Is: And Pattern Is: Then:

30 Month to Day 1 unit is produced every day for 30

days.

15 Month to Day 1 unit is produced every 2 days for 30

days resulting in 15 occurrences.

40 Month to Day 2 units are produced each day for 10

days, followed by 1 unit each day for 20
days. The aggregate quantity amount
will be 40 units. The 40 units will be
produced over the course of 30 days.

The following patterns are available:

Results in part of Quantity being Over the

This pattern:
Produced: course of:

Year to Month Once A Month A Year

Year to Week Once A Week A Year

Year to Day Once A Day A Year

Month to Week Once A Week A Month

Month to Day Once A Day A Month

Month to Hour Once Every Hour A Month

Week to Day Once A Day A Week

Week to Hour Once Every Hour A Week

Day to Hour Once Every Hour A Day

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 83

Chapter 1 Standard Tables

Order Number
Type: Number
Enter an order number for your reference. This number is not used in any calculations.

Priority
Type: Number
Specify the Priority by which products are produced. This is useful in differentiating
production based on the relative importance of products.

Unit Weight
Type: Number
Specify the desired weight of production.

Unit Cubic
Type: Number
Specify the desired cubic volume of production.

User Defined Customer Demand Profile

You can use the User-Defined Customer Demand Profile table along with the Demand
table to override statistics and the Demand Class or use it as the primary set of data
without using the Demand table.

Customer Name
Type: Text
Specifies the name of the customer at which demand occurs.

Product Name
Type: Text
Specifies the product demanded at the given customer.

Period Name
Type: Text
Specifies the period at which the demand occurs.

Non-zero Demand Mean

Type: Number
Average demand size during the period at the given site. This does not include
aggregation periods with zero demand.

Non-zero Demand Std Dev

Type: Number

84 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 User Defined Customer Demand Profile

Standard deviation of demand size during the period at the given site. This does not
include aggregation periods with zero demand.

Inter-Demand Interval Mean

Type: Number
Average number of aggregation periods between two adjacent aggregated demand records in a
time series.

Demand Mean
Type: Number
Specifies the mean daily demand during the period at the given customer. The mean is
calculated as per a normal distribution of demand.

Demand Std Dev

Type: Number
Specifies the standard deviation of the demand during the period at the given customer.
The standard deviation is calculated as per a normal distribution of demand.

Demand Class Details

Type: Special
Specifies the classification of demand for the product at the site in a multi-echelon model.

Forecast Mean
Type: Number
Enter the mean for the Customer-Product-Period combination representing a forecast to
be used with Demand Sampling. Demand Sampling uses the Forecast Mean and Forecast
Std Dev from the User Defined Customer Demand Profile, the historical demand mean
interval, and historical demand points from the Demand table, along with the Demand
Sampling horizon and aggregation. It generates a new demand time series with the
forecast mean and forecast standard deviation, and then calculates the five statistics
parameters in the User Defined Customer Demand Profile table based on the new
demand series.

Forecast Std Dev

Type: Number
Enter the standard deviation for the Customer-Product-Period combination representing a
forecast to be used with Demand Sampling. Demand Sampling uses the Forecast Mean
and Forecast Std Dev from the User Defined Customer Demand Profile, the historical
demand mean interval, and historical demand points from the Demand table, along with
the Demand Sampling horizon and aggregation. It generates a new demand time series
with the forecast mean and forecast standard deviation, and then calculates the five
statistics parameters in the User Defined Customer Demand Profile table based on the
new demand series.

Status
Type: Special

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 85

Chapter 1 Standard Tables

The status field defines whether this profile record will be included or excluded during
Demand Analysis and Safety Stock Optimization runs.

User Defined Facility Demand Profile

Use the User-Defined Facility Demand Profile as an override to the calculated statistics
and Demand Class. The use case for the user-defined facility demand is to do overrides at
a single echelon only and has no effect on upstream propagation.

Facility Name
Type: Text
Specifies the name of the site at which demand occurs.

Product Name
Type: Text
Specifies the product demanded at the given site.

Period Name
Type: Text
Specifies the period at which the demand occurs.

Non-zero Demand Mean

Type: Number
Average demand size during the period at the given site. This does not include
aggregation periods with zero demand.

Non-zero Demand Std Dev

Type: Number
Standard deviation of demand size during the period at the given site. This does not
include aggregation periods with zero demand.

Inter-Demand Interval Mean

Type: Number
Average number of aggregation periods between two adjacent aggregated demand records in a
time series.

Demand Mean
Type: Number
Specifies the mean daily demand during the period at the given site. The mean is
calculated as per a normal distribution of demand.

Demand Std Dev

Type: Number
Specifies the standard deviation of the demand during the period at the given site. The
standard deviation is calculated as per a normal distribution of demand.

86 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipments

Demand Class Details

Type: Special
Specifies the classification of demand for the product at the site in a multi-echelon model.

Status
Type: Special
The status field defines whether this profile record will be included or excluded during
Demand Analysis and Safety Stock Optimization runs.

Shipments
Product Name
Type: Text
Enter the name of the product to be shipped.
A Tip: You can select your Source Site, Destination Site and Product Name from the drop-
down list or enter the first few letters of the product or site and the software will find the
first match from the drop-down list.

Source Site
Type: Text
Enter the Site that will be shipping the product.

Destination Site
Type: Text
Enter the Site that will be receiving the product.

Quantity
Type: Number
Enter the quantity of product to be shipped. A probability distribution can be specified by
clicking on the field guru button in the cell.

Name
Type: Text
Enter the Name for the Shipment.
Vehicle Route Optimization: The Name must be populated for the shipment to be
considered in Vehicle Route Optimization. The Shipment Name is used throughout the
VRP process, specifically:
 In the Relationship Constraints Editor
 Populated by the Shipments Builder
 Reported in all Transportation Guru output tables
When shipments are sent to the VRP, they are ordered by Shipment Name to ensure
consistency.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 87

Chapter 1 Standard Tables

Order Time
Type: Date
Enter the date when this shipment will occur. The shipment can occur on a certain date or
after a certain time period. To specify the time period, use Order Time Formula.

Note: If you populate both Order Time and Order Time Formula, Supply Chain Guru uses
Order Time Formula when running Optimization or Simulation.

For Vehicle Route Optimization, this field specifies the start of the delivery time window
for the shipment. The end of the delivery time window is defined using Due Date.
If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Order Time Formula

Type: Number or Distribution
Enter a number or distribution that defines when the shipment will occur. Order Time
Formula has a Field Guru associated with it that allows you to enter probability factors or
dates for shipment time.
If you want to change the Order Time through a scenario, you should use the Order Time
Formula field with numeric values, not the date-based Order Time field.

Due Date
Type: Date
Used to specify the date by which a shipment must be completed.

Note: If you populate both Due Date and Due Date Formula, Supply Chain Guru uses
Due Date Formula when running Optimization or Simulation.

For Vehicle Route Optimization, this field specifies the end of the delivery time window for
the shipment. The start of the delivery time window is defined using Order Time.
If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Due Date Formula

Type: Number or Distribution
Enter the number or distribution that defines when a shipment must be completed.
Due Date Formula has a Field Guru associated with it.

Note: The default Due Date Formula unit is DAY. If you do not enter a date, the software
assumes the Due Date Formula is measured in days. If Due Date Formula is left
blank, the software assumes the order is due immediately when a shipment
occurs.
If you populate both Due Date and Due Date Formula, Supply Chain Guru uses
Due Date Formula when running Optimization or Simulation.

88 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipments

Due Date examples are in the following table.

If you want the Due Date to occur: Enter:

As soon as a production begins 0 or leave blank

1 day after the production begins 1

On a particular day Use the Due Date field

For Vehicle Route Optimization, this field specifies the number of days to add to the start
of the delivery time window to calculate the end of the delivery time window. The start of
the delivery time window is defined using Order Time. For example, if your Order Time is
1/5/2013, a value of 7 in the Due Date Formula field indicates a date of 1/12/2013 (1/5/
2013 + 7 days).
If you want to change the Due Date through a scenario, you should use the Due Date
Formula field with numeric values, not the date-based Due Date field.

Occurrences
Type: Number or Text
Enter how many times this shipment will occur. A shipment must occur at least once.
When you enter a number greater than one, shipments will occur multiple times.

If you want the Occurrence to take place: Enter:

1 time 1

10 times 10

As long as the simulation runs INF

Time Between Orders

Type: Number or Distribution
For Simulation, enter how much time must pass between each recurring order. It is
directly connected with the Occurrences. For example, Time Between Orders can be 24
HR, meaning that shipment must recur every 24 hours.
For Optimization, the Time Between Orders is ignored. The total shipment size based on
Quantity and Occurrences is put into the period for which the shipment is specified based
on the Order Time or Order Time Formula field.

Note: You must enter data in this field if the Occurrences are greater than 1. If you do
not enter Time Between Orders and shipments recurs, the software will assume
that this production happens once a day.

Time Between Orders examples are in the following table.

If you want: Enter

Recurring daily shipment 1 DAY or leave blank

Occurrences: INF

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 89

Chapter 1 Standard Tables

Randomly occurring shipments according to a triangular T(1,3,4) DAY

distribution
Occurrences: INF

Mode
Type: Special
Enter the mode for this shipment.
For Vehicle Route Optimization, shipments with the same Mode value will be pooled
together and routed on equipment with the same Mode as defined in the Asset Availability
table.

Route ID
Type: Text
When creating a Vehicle Route Optimization baseline model, enter the Route ID to which
the shipment should be assigned. The order of the shipments on the route is determined
by the value you enter for Sequence.

Delivery Sequence
Type: Text
When creating a Vehicle Route Optimization baseline model, enter the sequence number
that determines the order of the shipment delivery on the route assigned with Route ID.
Use this field for deliveries.

Pickup Sequence
Type: Text
When creating a Vehicle Route Optimization baseline model, enter the sequence number
that determines the order of the shipment pick up on the route assigned with Route ID.
Use this field for pick ups.

Order Number
Type: Number
Enter the order number for the shipment. This field can be called in a script during
simulation.

Priority
Type: Special
Enter the priority level of the shipment.
Simulation: This field can be called in a script during simulation.
Vehicle Route Optimization: Use this value to set the priority for routing the shipment
(lower numbers have a higher priority). The priority is assessed per pool site.

Unit Price
Type: Number
Enter the price to ship one unit of product in the shipment during shipment. If this field is
left blank, Supply Chain Guru will use the unit price from the Products Table.

90 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipments

For Vehicle Route Optimization, the Unit Price in the Shipments table is not used.

Weight
Type: Number
Enter the weight of one unit of product in this shipment. If this field is left blank during
Simulation, Supply Chain Guru will use the unit weight from the Products Table.
When using Vehicle Route Optimization, the Weight is the weight of the shipment. If this
field is left blank during Vehicle Route Optimization, the associated value from the
Products table is not used.

Cubic
Type: Number
Enter the cubic volume of one unit of product in this shipment. If this field is left blank
during Simulation, Supply Chain Guru will use the unit cubic volume from the Products
Table.
When using Vehicle Route Optimization, the Cubic is the cubic volume of the shipment. If
this field is left blank during Vehicle Route Optimization, the associated value from the
Products table is not used.

Comp2 Quantity
Type: Number
Enter the quantity of product to be shipped in the second compartment of the selected
transportation asset. Shipments that have Comp2 Quantity values populated can be
loaded into the second compartment of the asset during Vehicle Route Optimization.

Note: This field is hidden by default. You can display the field using Column Options.

Comp2 Weight
Type: Number
Enter the weight of product to be shipped in the second compartment of the selected
transportation asset. Shipments that have Comp2 Weight values populated can be loaded
into the second compartment of the asset during Vehicle Route Optimization.

Note: This field is hidden by default. You can display the field using Column Options.

Comp2 Cubic
Type: Number
Enter the cubic volume of product to be shipped in the second compartment of the
selected transportation asset. Shipments that have Comp2 Cubic values populated can be
loaded into the second compartment of the asset during Vehicle Route Optimization.

Note: This field is hidden by default. You can display the field using Column Options.

Cancel if Late
Type: Yes/No

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 91

Chapter 1 Standard Tables

In the drop down menu, select if the shipment will be canceled if it will arrive late (YES)
or if it should still be delivered if it will be late (NO).

Inter Location ID 1
This field identifies the location ID of a possible hub for consolidating outbound
shipments. Shipments can also be consolidated at a warehouse and de-consolidated at
Inter Location ID 1.

Note: This field is hidden by default. You can display the field using Column Options.

Inter Location ID 2
This field identifies the location ID of a second possible hub for consolidating outbound
shipments.

Note: This field is hidden by default. You can display the field using Column Options.

LTL Time

Note: This is the extra time from the last warehouse or hub in the network to the
customer location, if using LTL/small package shipping method. The default unit
for time fields is DAY. This field is hidden by default. You can display the field using
Column Options.

Direct Shipping Cost

Type: Number
Defines the cost to make the shipment using standard direct shipping (often LTL) rates. If
specified, the optimization engine can look to consolidate multiple direct shipments into a
truckload shipment to save money.
Vehicle Route Optimization: This is the direct shipment cost. It is typically the extra cost from
the last warehouse or hub in the network to the customer location, if using an LTL or small package
shipping method, or when using an alternate truckload routing option. When using Standard,
Backhaul or Periodic Optimization, this cost does not affect the solution and is reported in the
Delivered Shipments table. When using Interleaved or Asset Optimization, this cost is used in the
objective function and will influence the solution.

Desired Pickup Date

This field specifies the desired pickup date for the shipment. It acts as a soft constraint,
unlike the shipment windows specified by the Earliest and Latest Pickup and Delivery
dates. In future, this field may be used in conjunction with penalties to impact the solver
behavior.

Note: This field is hidden by default. You can display the field using Column Options.

Desired Delivery Date

This field specifies the desired delivery date for the shipment. It acts as a soft constraint,
unlike the shipment windows specified by the Earliest and Latest Pickup and Delivery

92 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipments

dates. In future, this field may be used in conjunction with penalties to impact the solver
behavior.

Note: This field is hidden by default. You can display the field using Column Options.

Freight Class
This field specifies the freight class. This is the category of freight defined by the National
Motor Freight Traffic Association according to four characteristics: Weight, Storability,
Handling, and Liability. There are 18 freight classes ranging from class 50 (the least
expensive) to class 500 (most expensive).

Max Cost
This is a penalty cost that will be incurred if the shipment is not delivered.

Fixed Service Time

This field defines the fixed service time for the shipment at the non-pool site location.
This is the destination for outbound shipments and the origin for inbound shipments. The
default unit for time fields is DAY.

Earliest Pickup Date

This field determines the earliest pickup date and time for the shipment. If no value is
specified, Vehicle Route Optimization uses the Begin Time Horizon parameter (defaults to
Model Horizon Start Date).

Earliest Pickup Date Formula

Not currently used. This field determines the earliest pickup date and time for the
shipment. If no value is specified, Vehicle Route Optimization uses the Begin Time
Horizon parameter (defaults to Model Horizon Start Date).

Latest Pickup Date

This field determines the latest pickup date and time for the shipment. If no value is
specified, Vehicle Route Optimization uses the End Time Horizon parameter (defaults to
Model Horizon End Date).

Latest Pickup Date Formula

This field determines the latest pickup date and time for the shipment. Enter the number
of days to add to the start of the pickup time window to calculate the end of the pickup
time window. The start of the delivery time window is defined using Earliest Pickup Date.
For example, if your Earliest Pickup Date is 1/5/2013, a value of 7 in the Latest Pickup
Date Formula field indicates a date of 1/12/2013 (1/5/2013 + 7 days).
If no value is specified, Vehicle Route Optimization uses the End Time Horizon parameter
(defaults to Model Horizon End Date).

Status
This field determines whether or not the shipment will be included when you run Vehicle
Route Optimization.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 93

Chapter 1 Standard Tables

Forecasts
Name
Type: Text
Enter a descriptive name for the forecast you are specifying.

Basis
Type: Text
Enter the length of the time periods for which you are forecasting demand or setting the
Reorder Point and Reorder/Order Up to Qty for R,Q-Targets and s,S-Targets inventory
policies. This is one of:
 Period Length – If you have defined periods, this is the length of the defined period. In
a single period model, it is the model horizon.
 Day – This is a single day.
 Week – The first day of the week is based on the model horizon. For example, if your
model horizon starts on 1/1/2015, this is a Thursday, so your forecast week will be
Thursday through Wednesday.
 Month (30 Day) – The first day of the month is based on the model horizon. For
example, if your model horizon starts on 1/7/2015, the 30 day period will start on this
date. An average of 30 days is used, rather than months of varying lengths.
 Quarter (91 Day) – The first day of the quarter is based on the model horizon. For
example, if your model horizon starts on 1/7/2015, the 91 day period will start on this
date.
 Year – This is a year starting on the first day of the model horizon.

Type
Type: Special
Choose whether you are using forecasting or targets. If an "s,S targets" or an "R,Q
targets" inventory policy is being used, then you must select Targets.

Quantities
Type: Number
Enter the anticipated quantities of product needed for each period (forecasting) or the
Reorder Point and Reorder/Order up to Qty (targets). Commas should be used to
separate numbers.

Note: You cannot use scenarios to update the values in the Quantities field.

The number of quantities you enter depends on the period you choose and how long your
simulation will run. The table below provides examples of how many quantities would be
needed for specific simulation lengths and forecast periods (type is set to forecast in
these examples).

If Simulation Forecast Enter At Least This Many

Lasts: Period is: Quantities:

30 Days Day 30

94 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Annual Schedules

30 Days Week 5

1 Year Day 365

1 Year Month 12

1 Year Quarter 4

5 Years Year 5

Note: The DOS Window setting in the Inventory Policies data table also affects how
many forecast quantities you should set. You should enter enough quantities to
cover your simulation duration plus your DOS Window. For example, if your
simulation lasts 30 days, your Forecast Period is Day, and your DOS Window is 7
days, then you should enter 37 Quantities, not 30 as shown above.

Use the name of the forecast specified in this table in the Forecast Name field of the
Inventory Policies table for the product-site combination(s) that this forecast applies to.

Annual Schedules
Name
Type: Text
Select the site to which the schedule applies.

Date
Type: Date
Choose the date on which the change should occur. For example, you can enter the date
of a holiday on which site operations will be down.

State
Type: Special
Choose whether the schedule defines a period of site operations being up or down.

Weekly Schedule
This should be used when the weekly operating schedules at a site varies through the
simulation horizon. The annual schedule allows for Up and Down state changes to be
specified for a particular calendar date, where Scheduled Up signifies if the site is
operational and Scheduled Down signifies the site being not operational.
This allows specific days such as holidays to be programmed. The annual schedule can
also be used to activate a new weekly schedule to allow for seasonal variation.

Shipping Routes
(Simulation Only)

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 95

Chapter 1 Standard Tables

The Shipping Routes table is for use with the following Transportation Policies only in
Simulation: Pooled Inbound, Pooled Outbound, Pooled Periodic Inbound, and Pooled
Periodic Outbound.

Name
Type: Text
Enter a descriptive name for the shipping route that is being defined. The Name will be
the same for all waypoints in one shipping route.

Waypoint Name
Type: Text
Select a site that will be on this shipping route.

Waypoint Number
Type: Number
Enter the number that indicates the order in which the asset that uses this shipping route
will go to this site. Start with 1 for the first site the asset will go to, and increase by one
for each sequential site.

Distance
Type: Number
The software calculates the distance between the two waypoints automatically. Entering a
value in this field overwrites what the software calculates

Time
Type: Time
The software calculates the time it takes to travel between the two waypoints
automatically. Entering a value in this field overwrites what the software calculates.
Additionally, for this field to take effect, you have to specify a nominal value in the
Distance field.

Global Variables
(Simulation Only)

Name
Type: Text
Enter a unique name for this global variable.

Type
Type: Special
Select whether the variable will be an integer variable or a real variable.

Value
Type: Special

96 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Greenhouse Gases

Enter the initial value for the variable.

For variables that have dimensions specified (arrays), you can initialize individual
elements in the array by making the value field a comma separated list of values, such
as: 1,5,6,1,4,1,3,5,6,7,2. For two-dimensional arrays, each row is completely initialized
before moving to the next. Higher dimensional arrays cannot be initialized through the
values field.
For arrays, you can also load data directly into the array from an external MS Excel
spreadsheet, by simply listing a valid path as the value.

Note: The external spreadsheet initialization requires that MS Excel is installed on the PC
where the software is being run. The spreadsheet should only have 1 single
worksheet, and should only consist of numeric values that will be loaded into the
array.

Dimensions
Type: Number
Enter the dimensions of the global variable if you want to create an indexed variable
(array). Leaving this field blank will make this variable a single value variable.

Greenhouse Gases
The greenhouse gases table is responsible for storing the overall carbon constraints for
any supply chain model.

Max Carbon Footprint

Type: Number
Defines the maximum carbon footprint allowed in any model run. This is enforced by
solving the model with this number as a hard constraint on output. This number is
compared to the total CO2 of any model.

Enforce Max Carbon Footprint

Type: Yes/No
Defines whether or not the Max Carbon Footprint value is used as a hard constraint. If
blank or set to No, the constraint is excluded from the mixed integer linear program used
to optimize the model.

Carbon Cost
Type: Number
Represents cost per unit of CO2 in the model. This field is used to model carbon taxation
and other penalties for carbon emissions. This cost is used in both Network Optimization
and Simulation.

Carbon Offset Price

Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 97

Chapter 1 Standard Tables

Cost per unit of carbon offsets that can be purchased. In the real world, this price is the
equivalent to the cost of a carbon credit, or could represent a cost for voluntary carbon
offsetting. This cost is used in both Network Optimization and Simulation.

Optimize Carbon Offset

Type: Yes/No
Defines whether or not the number of carbon offsets needed for purchase should be
included in the objective function of the network design optimization.

Carbon Offset Initial

Type: Number
The initial number of units of carbon offsets included in the model. The number of
additional carbon offsets needed in the model is calculated by subtracting the initial
quantity of carbon offsets from the total number of carbon offsets needed to meet the
necessary requirements of the supply chain network.

Carbon Offset Minimum

Type: Number
The minimum number of carbon offsets that must be purchased.

Carbon Offset Maximum

Type: Number
The maximum number of carbon offsets that can be purchased for the network design.

Service Requirements
(Network Optimization Only)

Customer Name
Type: Text
Enter the Customer Site of the Customer Site - Facility (Source Site) pair to which the
service requirement applies.

Product Name
Type: Text
Enter the name of the product to which the service requirement applies.

Source Site
Type: Text
Enter the Source Site of the Customer Site - Facility (Source Site) pair to which the
service requirement applies. This site should be the originating site of the product that is
demanded at the customer site.

98 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Asset & Inventory Constraints

Note: Service requirements add an implicit constraint that all units on a path must
original from the Source Site on that path. Supply Chain Guru will not use initial
inventory at a site in between the source and destination.

Lead Time Reqt

Type: Number
Enter the amount of time it may take a product to travel through the supply chain from
the Source Site to the Customer Site.

Note: The default Lead Time Reqt unit is DAY. If you do not enter a unit, the software
assumes the Lead Time Reqt is measured in days.

Distance Reqt
Type: Number
The maximum distance between the source site and the facility can be specified.

Asset & Inventory Constraints

(Simulation Only)
This table enables you to limit:
 how much product/how many assets can pass through an object over a time period.
 how much product can be in inventory and how many assets can be at a location at
any point in time.

Site Name
Type: Text
Specify the site where this resource is used.

Constraint Type
Type: Text
Specify the constraint type. This is one of:
 Inventory
 Container
 Vehicle

Constraint Scope
Type: Text
Specify the scope to which the constraint applies. The available selections will be:
 (All)
 Names of defined Products
 Names of defined Transportation Assets for assets that have a Type value of Container
or Vehicle.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 99

Chapter 1 Standard Tables

Constraint Basis
Type: Text
Specify the dimension to be used for the constraint:
 Quantity
 Weight
 Cubic
 Value

Maximum
Type: Number
Enter the maximum value for the Constraint Basis.

Period
Type: Text
Specify the time period to which the constraint applies.

Transportation Paths
(Simulation Only)

Path Name
Type: Text
Enter the name for the transportation path.

Leg Number
Type: Integer
Specify the sequence number of the leg on the transportation path.

Leg Latitude
Type: Number
Enter the latitude value for the leg.

Leg Longitude
Type: Number
Enter the longitude value for the leg.

Leg Distance
Type: Number
Enter the distance of the leg.

Leg Speed
Type: Number

100 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Asset Availability

Enter the speed at which vehicles travel on the leg.

Leg Constraint Scope

Type: Text
Specify the scope to which the constraint applies. The available selections are:
 (All)
 Names of defined Transportation Assets for assets that have a Type value of Container
or Vehicle.

Leg Constraint Basis

Type: Text
Specify the dimension to be used for the constraint:
 Quantity
 Weight
 Cubic
 Value

Leg Constraint Maximum

Type: Number
Enter the maximum value for the Leg Constraint Basis.

Leg Constraint Period

Type: Text
Specify the time period to which the constraint applies.

Asset Availability
(Vehicle Route Optimization Only)
You use the Asset Availability table to define the equipment available at each site. You
must define at least one asset availability record.

Site Name
Type: Text
The location at which the equipment is located.

Asset Name
Type: Text
The equipment type for the availability.

Available Quantity
Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 101

Chapter 1 Standard Tables

The number of vehicles of the specified equipment type available at the location. When
specifying the Asset Availability for a periodic VRP model, the Available Quantity
represents the number of vehicles available per day.

Priority
Type: Number
Use this field to specify the equipment priority. The lower the value, the higher the
priority. If there is no value provided for priority, the default value (0) is used - the
highest priority.

Equipment ID
Type: Text
Use this field to specify a unique ID number for each vehicle (equipment) if required.

Mode
Type: Text
The mode for the equipment. Equipment with the same Mode value will be pooled
together and used to route shipments and demand with the same Mode.

Home Site Name

Type: Text
The location where the equipment is domiciled (garaged).

Note: This field is hidden by default. You can display the field using Column Options.

Start Date/Time
Type: Number
The start date and time of the equipment availability. If no date/time is provided, it is set
to the Begin Time Horizon value in the Vehicle Route Optimization Options. If no time is
provided, it is set to the beginning of the day.

Start Date/Time Formula

Type: Number or Distribution
Not currently supported. Specify a number or distribution that defines the start date and
time of the equipment availability. If no value is provided, it is set to the Begin Time
Horizon value in the Vehicle Route Optimization Options.

Carrier ID
Type: Text
Specifies the particular carrier for which this service is available.

Note: This field is hidden by default. You can display the field using Column Options.

102 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Rate

Dedicated Origin ID
Type: Text
Specifies the particular origin location ID where this service is available.

Dedicated Destination ID
Type: Text
Specifies the particular destination location ID where this service is available.

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Asset
Availability record.

End Date/Time
Type: Number
The end date and time of the equipment availability. If no date/time is provided, it is set
to the End Time Horizon value in the Vehicle Route Optimization Options. If no time is
provided, it is set to the end of the day.

End Date/Time Formula

Type: Number or Distribution
Not currently supported. Specify a number or distribution that defines the end date and
time of the equipment availability as an offset from the Start Date/Time. If no date/time
is provided, the end of the Asset Availability is set to the End Time Horizon value in the
Vehicle Route Optimization Options.

Rate
(Vehicle Route Optimization Only)
Define the detailed rate information used to cost your vehicle routes. You must define at
least one rate.

Note: The Distance Based, Time Based and Stop cost fields in the Rate table accept
either a number or pairs of values. Enter a number for a constant cost. If the cost
varies with the distance, stop or time incurred, enter pairs of values that define
the relationship between the value incurred and cost. The first number in the pair
is the distance, stop or time. The second number is the unit cost per unit. For
example, if you enter <0,1.8><300,1.5) for the Per Distance Cost, the first 300
miles are charged at 1.8 per mile and the distance over 300 miles is charged at
1.5 per mile.

The piecewise costs on the Rate table are evaluated as Incremental Discounts (as
opposed to All Item Discounts). The Piecewise Costs setting in Optimization
Options that supports All Item Discounts applies to Network Optimization only.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 103

Chapter 1 Standard Tables

Rate ID
Type: Text
The identifier of the rate.

Asset Name
Type: Text
Provide the equipment type ID if the rate applies to a specific equipment type.

Origin Location Group

Type: Text
Used to define a set of origin locations.

Destination Location Group

Type: Text
Used to define a set of destination locations.

Unit of Measurement
Type: Text
Defines the unit to which the rate applies:
 Per Load
 In Cubic
 In Weight
 In Quantity
Default: Per Load

Note: This field is hidden by default. You can display the field using Column Options.

Freight Class
Type: Text
The Freight Class to which the rate applies. This field is not applicable to full truckload.
Freight class is the category of freight defined by the National Motor Freight Traffic
Association according to four characteristics: Weight, Storability, Handling, and Liability.
There are 18 freight classes ranging from class 50 (the least expensive) to class 500
(most expensive). LTL carriers use the NMFC tariff to determine their freight charges.
Default: 50

Note: This field is hidden by default. You can display the field using Column Options.

Carrier
Type: Text
The carrier to which the rate applies.

104 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Rate

Note: This field is hidden by default. You can display the field using Column Options.

Charge Type
Type: Text
Defines the type of charge:
 Distance and Time Based
 Distance Based
 Time Based
 Flat Rate
Default: Distance and Time Based

Note: This field is hidden by default. You can display the field using Column Options.

Surcharge Per Distance

Type: Number
Typically used for full truckload, this is a surcharge that will be applied per distance unit.
It is added to the Per Distance Cost.
The actual per distance cost = Per Distance Cost * (1 + Surcharge Percentage) +
Surcharge Per Distance.
Default: 0

Surcharge Percentage
Type: Number
Typically used for full truckload, this is a percentage surcharge that will be applied. 0.02
means 2%. It is added to the Per Distance Cost. The actual per distance cost = Per
Distance Cost * (1 + Surcharge Percentage) + Surcharge Per Distance.
Default: 0

Discount Rate
Type: Number
Used to define a discount percentage that is applied to the total charge.
Default: 0

Fixed Cost
Type: Number
Specifies the fixed charge applied to the route.
Default: 0
Applicable when Charge Type is “Distance and Time Based”, “Distance Based”, “Time
Based” or “Flat Rate”.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 105

Chapter 1 Standard Tables

Per Unit Cost

Type: Number or Pairs
Specifies the cost per unit on the route, as determined by the Unit Cost Basis. Enter a
number for a constant Per Unit Cost. If the Per Unit Cost varies with the number of units,
enter pairs of values that define the relationship between the units and cost. The first
number in the pair is the number of units. The second number is the cost per unit. For
example, if you enter <0,5><300,4>, the first 300 units on the route are charged at 5
per unit and the units over 300 are charged at 4 per unit.

Unit Cost Basis

Type: Text
Specifies the basis on which the Per Unit Cost is applied. This is one of:
 Quantity
 Weight
 Cubic
The default Unit Cost Basis, if no value is selected, is Quantity.

Minimum Cost
Type: Number
Specifies the minimum cost that must be incurred per shipment.

Per Distance Cost

Type: Number or Pairs
Specifies the charge per travel distance unit with loaded equipment. Enter a number for a
constant Per Distance Cost. If the Per Distance Cost varies with the distance traveled,
enter pairs of values that define the relationship between the distance and cost. The first
number in the pair is the distance. The second number is the unit cost per distance. For
example, if you enter <0,1.8><300,1.5>, the first 300 miles are charged at 1.8 per mile
and the distance over 300 miles is charged at 1.5 per mile.
Applicable when Charge Type is “Distance and Time Based” or “Distance Based”.
Default: 0

Per Reposition Distance Cost

Type: Number or Pairs
Specifies the charge per travel distance unit with empty equipment (often a repositioning
movement). Enter a number for a constant Per Reposition Distance Cost. If the Per
Reposition Distance Cost varies with the distance traveled, enter pairs of values that
define the relationship between the distance and cost. The first number in the pair is the
distance. The second number is the unit cost per distance. For example, if you enter
<0,1.8><300,1.5>, the first 300 miles are charged at 1.8 per mile and the distance over
300 miles is charged at 1.5 per mile.
Applicable when Charge Type is “Distance and Time Based” or “Distance Based”.

Note: For inbound Standard VRP and Asset Optimization problems, this cost is currently
being applied to the segment from the last pickup to the delivery at the pool site.

106 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Rate

Default: 0

Per Stop Cost

Type: Number or Pairs
Specifies the charge for each delivery stop. Enter a number for a constant Per Stop Cost.
If the Per Stop Cost varies with the number of stops, enter pairs of values that define the
relationship between the number of stops and cost. The first number in the pair is the
number of stops. The second number is the unit cost per stop. For example, if you enter
"<0,0><1,100>", this means that the first stop is free, and the second stop and later are
$100 per stop.
Applicable when Charge Type is “Distance and Time Based”, “Distance Based”, “Time
Based” or “Flat Rate”.
Default: 0

Fixed Overnight Cost

Type: Number or Pairs
Specifies the charge every time the driver needs to lodge overnight. Enter a number for a
constant Fixed Overnight Cost. If the Fixed Overnight Cost varies with the number of
lodgings, enter pairs of values that define the relationship between the number of
overnights and cost. The first number in the pair is the number of overnights. The second
number is the unit cost per overnight. For example, if you enter "<0,100><2,80>", this
means that the first two overnights are charged at 100, and overnights more than 2 are
80 per lodging.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Drive Time Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of driving. Enter a number for a constant
Drive Time Cost. If the Drive Time Cost varies with the number of drive time hours, enter
pairs of values that define the relationship between the number of drive time hours and
cost. The first number in the pair is the number of drive time hours. The second number
is the unit cost per hour. For example, if you enter "<0,60><8,80>", this means that the
first 8 hours are charged at 60 per hour, and hours more than 8 are 80 per hour.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Service Time Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of on-duty time that is not driving or waiting.
Examples of service time includes loading and unloading. Enter a number for a constant
Service Time Cost. If the Service Time Cost varies with the service time, enter pairs of
values that define the relationship between the number of hours and cost. The first
number in the pair is the number of hours. The second number is the unit cost per hour.
For example, if you enter "<0,60><8,80>", this means that the first 8 hours are charged
at 60 per hour, and hours more than 8 are 80 per hour.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 107

Chapter 1 Standard Tables

Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Wait Time Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of waiting. Enter a number for a constant
Wait Time Cost. If the Wait Time Cost varies with the number of wait time hours, enter
pairs of values that define the relationship between the number of hours and cost. The
first number in the pair is the number of hours. The second number is the unit cost per
hour. For example, if you enter "<0,60><4,80>", this means that the first 4 hours are
charged at 60 per hour, and hours more than 4 are 80 per hour.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Variable Overnight Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of a long break as defined by Min Break Time
Between Shifts in the Transportation Assets table. Enter a number for a constant Variable
Overnight Cost. If the Variable Overnight Cost varies with the number of wait time hours,
enter pairs of values that define the relationship between the number of hours and cost.
The first number in the pair is the number of hours. The second number is the unit cost
per hour. For example, if you enter "<0,80><4,60>", this means that the first 4 hours
are charged at 80 per hour, and hours more than 4 are 60 per hour.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Break Time Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of short breaks as defined by Min Break Time
Within Shift in the Transportation Assets table. Short breaks are calculated if Max Drive Time
Within Shift and Min Break Time Within Shift are both populated. It counts toward duty time.
Enter a number for a constant Break Time Cost. If the Break Time Cost varies with the
number of wait time hours, enter pairs of values that define the relationship between the
number of hours and cost. The first number in the pair is the number of hours. The
second number is the unit cost per hour. For example, if you enter "<0,80><4,60>", this
means that the first 4 hours are charged at 80 per hour, and hours more than 4 are 60
per hour.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Duty Time Cost

Type: Number or Pairs
Specifies the charge per hour (not minute) of on-duty time (including driving, non-drive-
working, waiting, and short breaks). Vehicle Route Optimization will use this field to
calculate the rate if it is specified. It must be a positive number. In that case, Drive Time
Cost, Service Time Cost, Wait Time Cost, and Break Time Cost are ignored. Enter a

108 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Business Hours

number for a constant Duty Time Cost. If the Duty Time Cost varies with the number of
duty time hours, enter pairs of values that define the relationship between the number of
hours and cost. For example, you may want to define a separate rate for overtime hours.
The first number in the pair is the number of hours. The second number is the unit cost
per hour. For example, if you enter "<0,60><12,80>", this means that the first 12 hours
are charged at 60 per hour, and hours more than 12 are 80 per hour.
Applicable when Charge Type is “Distance and Time Based” or “Time Based”.
Default: 0

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Rate record.

Business Hours
(Vehicle Route Optimization Only)
You can optionally define the business hours per day per site using this table.

Site
Type: Text
The name of the site to which the business hours apply.

Sunday Open
Type: Text
The time at which the site opens on Sunday.
Default: 00:00

Sunday Closed
Type: Text
The time at which the site closes on Sunday.
Default: 23:59

Monday Open
Type: Text
The time at which the site opens on Monday.
Default: 00:00

Monday Closed
Type: Text
The time at which the site closes on Monday.
Default: 23:59

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 109

Chapter 1 Standard Tables

Tuesday Open
Type: Text
The time at which the site opens on Tuesday.
Default: 00:00

Tuesday Closed
Type: Text
The time at which the site closes on Tuesday.
Default: 23:59

Wednesday Open
Type: Text
The time at which the site opens on Wednesday.
Default: 00:00

Wednesday Closed
Type: Text
The time at which the site closes on Wednesday.
Default: 23:59

Thursday Open
Type: Text
The time at which the site opens on Thursday.
Default: 00:00

Thursday Closed
Type: Text
The time at which the site closes on Thursday.
Default: 23:59

Friday Open
Type: Text
The time at which the site opens on Friday.
Default: 00:00

Friday Closed
Type: Text
The time at which the site closes on Friday.
Default: 23:59

110 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transit Override

Saturday Open
Type: Text
The time at which the site opens on Saturday.
Default: 00:00

Saturday Closed
Type: Text
The time at which the site closes on Saturday.
Default: 23:59

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Business
Hours record.

Transit Override
(Vehicle Route Optimization Only)
You can optionally define overrides to the calculated travel time or distance or both
between pairs of locations. Additionally, you can define a Cost to override the cost
calculated based on the defined Rate records.

Origin
Type: Text
The identifier of the origin location.

Destination
Type: Text
The identifier of the destination location.

Travel Time
Type: Number
The time, in days, required to travel from the origin to the destination location. This value
overrides the calculated travel time. The default unit for time fields is DAY.
Default: 0

Travel Time Factor

Type: Number
Enter the factor by which the Travel Time should be adjusted for use in calculating times
on routes. In this way, you can adjust the times returned by the Distance Matrix
Calculator as required.
For example, if you set the Travel Time to 0.5 DAY (or 12 hours), and you set the Travel
Time Factor to 1.2, the calculated travel time is .5 DAY x 1.2 = .6 DAY (or 14.4 hours).

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 111

Chapter 1 Standard Tables

Distance
Type: Number
The distance from the origin location to the destination location. This value overrides the
calculated distance. By default, the calculated distance is the straightline distance
multiplied by the Distance Circuity Factor as defined in the Vehicle Route Optimization
Options. The default for this factor is 17%.
Default: 0

Cost
Type: Number
The cost to travel from the origin to the destination location. This value overrides the cost
calculated based on the Rate table.
Default: 0

Asset Name
Type: Text
The specific equipment type to which the override applies.

Is Symmetric
Type: Yes/No
Set this to Yes if travel time, distance, cost from origin to destination are all the same as
from destination to origin.
Default: Yes

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Transit
Override record.

Relationship Constraint
(Vehicle Route Optimization Only)
This table enables you to optionally define pairs of entities that must be combined on a
route and those that cannot be combined on a route. The primary use case for

112 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Relationship Constraint

relationship constraints is to force items to be shipped together or to keep them separate.

The following combinations are supported:

Entity A Entity B Relationship

Shipment Shipment Prevent

Note: This combination is not supported
for Periodic Scheduling and Balancing
(Periodic VRP).

Shipment Transportation Prevent and Force (a Shipment may

Asset request more than one Transportation
Asset)

Product Product Prevent

Note: Your Transportation Policy records
must include Product to use this type of
Relationship Constraint. If you do not
include the Product value, the
Relationship Constraint can be violated.

Product Transportation Prevent and Force (a Product may request

Asset more than one Transportation Asset)
Note: Your Transportation Policy records
must include Product to use this type of
Relationship Constraint. If you do not
include the Product value, the
Relationship Constraint can be violated.

Site Transportation Prevent and Force (a Site may allow more

Asset than one Transportation Asset)

Site Site Prevent

Relationship
Type: Force/Prevent
Set this to Prevent to indicate that Item A must not be combined on a route with Item B.
Set this to Force to indicate that Item A must be combined with Item B on a route.
Default value: Force

Type A
Type: Text
Select the type of entity for the first part of the relationship constraint. This value will be
one of the following:
 Products
 Shipments
 Sites
 Transportation Assets

Note: If the Relationship Constraint includes Products, your Transportation Policy records
must include Product to use this type of Relationship Constraint. If you do not
include the Product value, the Relationship Constraint can be violated.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 113

Chapter 1 Standard Tables

ID Field A
Type: Text
Select the Shipment, Product, Site, or Asset to be considered with Item B for the
Relationship Constraint.

Type B
Type: Text
Select the type of entity for the second part of the relationship constraint. This value will
be one of the following:
 Products
 Shipments
 Sites
 Transportation Assets

Note: If the Relationship Constraint includes Products, your Transportation Policy records
must include Product to use this type of Relationship Constraint. If you do not
include the Product value, the Relationship Constraint can be violated.

ID Field B
Type: Text
Select one or more entities of Type B to be considered with Item A for the Relationship
Constraint.

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Relationship
Constraint record.

Notes
Type: Text
Use this field to include descriptive information for the record.

Relationship Constraint Example:

The following illustration shows two valid relationship constraints.

114 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Periodic VRP Schedule

In the first row, a “Prevent” relationship has been set up for the Transportation Asset
called “StandardTruck” and the group of sites “NJ_MD_DE_Sites”. This relationship
constraint ensures that the StandardTruck asset will not stop at any of the sites in the
group. This could be due to limitations in the size of vehicle that can be accommodated in
the dense cities of the northeastern United States.
In the second row, a “Force” relationship has been set up for the Transportation Asset
called “RefrigeratedTruck” and the Product called “PerishableFood”. This relationship
constraint ensures that the shipments containing the PerishableFood product must be
shipped on a refrigerated truck.

Periodic VRP Schedule

(Vehicle Route Optimization Only)
You use this table to define the schedule, by site (or group of sites), for Periodic VRP
Optimization. In the Periodic VRP Schedule table, you define the frequency of deliveries
over the model horizon and the minimum and maximum number of days between visits.
Additionally, you can force which days in the horizon must be used and which days cannot
be used for visits.

Site Name
Type: Text
This is the site to which the visit schedule applies.

Frequency
Type: Number
Enter the number of visits to the site during the model horizon.

Minimum Days Between

Type: Number
Enter the minimum number of days between visits, if multiple visits occur during the
model horizon.

Maximum Days Between

Type: Number
Enter the maximum number of days between visits, if multiple visits occur during the
model horizon.

Forced Include Day(s)

Type: Text
Enter days on which the visits must occur. The first day of the model horizon is 1. For
example, assume a model horizon of 1/8/2012 to 1/16/2012. 1/8/2012 (a Sunday) is day
1. If you want visits on Monday and Thursday, enter 2|5 (day values separated by the
pipe character).
Forced Exclude Day(s)
Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 115

Chapter 1 Standard Tables

Enter days on which the visits must not occur. The first day of the model horizon is 1. For
example, assume a model horizon of 1/8/2012 to 1/16/2012. 1/8/2012 (a Sunday) is day
1. If you do not want visits on Tuesday and Friday, enter 3|6 (day values separated by the
pipe character).

Status
Type: Include/Exclude
Use this field to determine if Vehicle Route Optimization should consider the Periodic VRP
Schedule record.

116 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Chapter 2

Multi-Time Period Tables

The following are Supply Chain Guru Multi-Time Period tables:

 Periods
 Products Multi-Period
 Sites Multi-Period
 Sourcing Policies Multi-Period
 Inventory Policies Multi-Period
 Transportation Policies Multi-Period
 Transportation Assets Multi-Period
 Processes Multi-Period
 Work Centers Multi-Period
 Work Resources Multi-Period

Multi-Time Period Costs and Constraints

When building costs and constraints into multi-time period models, you can specify
values in both the Standard Tables and in the Multi-Time Period tables. The values can
vary between the tables and across the periods, and optimization uses period-specific
values. When setting costs and constraints in multi-period models, the following rules
apply:

Costs
If you set a cost in a Standard Table, that cost value is used for each period, unless the
cost is also set in the corresponding Multi-Time Period table. When that happens:
 In the period(s) for which the cost is also set in the Multi-Time Period table, that cost
is used and not the one set in the Standard Table.
 In period 1, if a cost is set on the Multi-Time Period table, that cost is used and not
the one set in the Standard Table.
 In all other periods that do not have a cost set on the Multi-Time Period table, the cost
from period 1 is used. This is either the cost set in the Multi-Time Period table for
period 1 or, if that cost is not set, the cost from the Standard Table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 117

Chapter 2 Multi-Time Period Tables

Constraints
Constraints include fields such as Inbound Capacity and Outbound Capacity on the
Inventory Policies table.
 If constraints are set only on the Standard Table, they are applied only to period 1.
 To apply a constraint to periods other than period 1, you must set it explicitly on the
Multi-Time Period table for each period for which it should apply.
The exception to this is the Fixed Operating cost for Sites/Work Centers. The Capacity
Period, Capacity Basis, and Apply to Horizon fields define how these work across
periods. Note that Fixed Operating cost can still be overwritten for specific periods in
the Multi-Time Period tables.

Periods
Period Name
Type: Special
The value for this field is entered automatically entered when you click on the Generate
Periods button. Alternatively, you can click on the field and enter a name for the period.
To change a name that was created using Generate Periods, double-click on the field and
enter a new name.

Period Start Date

Type: Date
Enter the date for the start of the period. The end of the period becomes the day before
the next period’s start date.

Note: The Periods are used throughout the Multi-Time Period Data Table Fields.

Products Multi-Period
Period Name
Type: Special
Select the Period Name in which the product information changes.

Name
Type: Text
Select a unique Name from the drop-down menu to represent the product or Stock
Keeping Unit (SKU) number.

Value
Type: Number
Enter a monetary value for each unit for this Period. Similar to an accounting valuation,
this field is used to calculate the inventory investment and inventory holding costs.
For optimization:

118 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sites Multi-Period

 If a Value is not specified in the Multi-Time Period record, the Value from the Standard
Products table is used.
 If a Value is set for period 1 in the Multi-Time Period table, that Value is used instead
of the value set in the Standard Table.
 In all other periods that do not have a Value set in the Multi-Time Period table, the
Value from period 1 is used. This is either the Value set in the Multi-Time Period table
for period 1 or, if that Value is not set, the Value from the Standard Table.

Price
Type: Number
Enter the revenue generated from the sale of a single unit of this product. The product
price is used to calculate revenue statistics.
For optimization:
 If a Price is not specified in the Multi-Time Period record, the Price from the Standard
Products table is used.
 If a Price is set for period 1 in the Multi-Time Period table, that Price is used instead of
the Price set in the Standard Table.
 In all other periods that do not have a Price set in the Multi-Time Period table, the
Price from period 1 is used. This is either the Price set in the Multi-Time Period table
for period 1 or, if that Price is not set, the Price from the Standard Table.

Lead Time Cost/Day/Unit

Type: Number
Use this field to specify the cost of 1 day of lead time per unit of product. It is used in lead
time optimization. This field accepts positive values.

Max-Lead Time x Flow

Type: Number
Use this field to specify the maximum limit when the lead time is multiplied by the flow. It
is used in lead time optimization.

Sites Multi-Period
Period Name
Type: Special
Select the Time Period in which the site data changes.

Name
Type: Text
Select the name of an existing site within the model.

Fixed Operating <Cap,Cost>

Type: Function/Pair

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 119

Chapter 2 Multi-Time Period Tables

Enter a function that defines the relationship between operating capacity and operating
costs for this specific site during this time period. The function is specified by a series of
coordinates. The first number in the coordinate indicates throughput capacity. The second
number indicates operating cost.
For example, an entry of <0, 1000000> <500000, 2000000> <15000000, INF>
indicates an initial operation cost of $1,000,000 before any product is shipped. To boost
capacity to more than 500,000, the operating cost increases to $2,000,000. The
maximum capacity is 15,000,000 as indicated with a cost of infinite (INF). If the cost is
INF for a certain capacity level, that capacity is considered as a hard constraint.

Closing Cost
Type: Number
Enter the monetary cost of shutting down operations at this site during the specific time
period. In an optimization, closing costs are applied if a site of type Existing Facility is
closed during this period.

Sourcing Policies Multi-Period

Period Name
Type: Special
Select the Time Period in which the Sourcing Policy data changes.

Site
Type: Text
Select the site for which the Sourcing Policy changes.

Product Name
Type: Text
Enter the product for which the Sourcing Policy changes.

Source Name
Type: Text
Choose a site that can fill this replenishment order, or choose a work center that has a
routing record for this product for this time period.

Note: If using the Make souring policy, this field can be left blank, or it can be set to a
work center with a routing record for this product.

Avg Unit Cost

Type: Number
Specifies the average cost per unit for sourcing to be used in the network optimization for
this time period.
As an alternative to a simple constant cost, you can set up a cost schedule. This method
uses quantity break points and different costs with the Guru bracketed format, such as

120 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies Multi-Period

<0,1.50> <5000, 1.25> <10000, 1.00>. Using this example, the sourcing cost per unit
is:
 1.50 for units 0 through to 5,000
 1.25 for units 5,000 through to 10,000
 1.00 for units 10,000 and up.
For an order consisting of 20,000 units, the total cost is:
(5,000-0)*1.50 + (10,000-5,000)*1.25 + (20,000-10,000)*1.00 = 23,750.

Note: Simulation and optimization calculate costs differently. Simulation costs are
calculated on a per-order basis for each individual order, using the Sourcing Cost
value. Optimization costs are calculated using the aggregate flow quantity for the
entire time horizon, using the Avg Unit Cost value. Thus, when using quantity-cost
break points, you use different break points for simulation and optimization.

When setting costs in Multi-Time Period models, for optimization:

 If Avg Unit Cost is not specified in the Multi-Time Period record, the Avg Unit Cost
from the Standard Sourcing Policies table is used.
 If Avg Unit Cost is set for period 1 in the multi-period table, that Avg Unit Cost is used
and not the Avg Unit cost set in the Standard Table.
 For all other periods that do not have an Avg Unit Cost set on the multi-period table,
the Avg Unit Cost from period 1 is used. This is either the Avg Unit Cost set in the
multi-period table for period 1 or, if that Avg Unit Cost is not set, the Avg Unit Cost
from the standard table.

Days Between Productions

Type: Number
The number of days between production occurring at manufacturing sites that have Make
policies. This field is used to calculate the amount of cycle stock that should be held at the
manufacturing sites. This value is equivalent to the number of units produced divided by
the number of production turns that occur during the time period.

Minimum Order Quantity

Type: Number
Denote the minimum order quantity for this source to be used. This value is used when
calculating the inventory for the product at the site.

Inventory Policies Multi-Period

Period Name
Type: Special
Select the Time Period in which the Inventory Policy data changes.

Site
Type: Text
Select the Site for which an Inventory Policy is being changed for this time period.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 121

Chapter 2 Multi-Time Period Tables

Product Name
Type: Text
Select the product for which an Inventory Policy is being changed during this time period.

Inbound Cost
Type: Number or pairs
Enter the new activity cost of handling and moving one unit of this product from the
receiving dock into inventory for this time period. Inbound and outbound costs include
such costs as paper tracking procedures, handling equipment, and personnel.

Note: Inbound Cost does not include Transportation costs.

Outbound Cost
Type: Number or pairs
Enter the new activity cost of removing one unit of this product from inventory to the
shipping dock during this time period. Inbound and outbound costs include such costs as
paper tracking procedures, handling equipment, and personnel.

Note: Outbound Cost does not include Transportation costs.

Inbound Capacity
Type: Number
Enter the maximum quantity of product this site is capable of accepting during this
period. To define a capacity with no maximum, leave this field blank or enter INF
(infinity).

Outbound Capacity
Type: Number
Enter the maximum quantity of product this site is capable of shipping during this period.
You can also leave it blank or enter INF (infinity) to define a capacity with no maximum.

Inv Carrying Cost %

Type: Number
Specifies the cost percentage for holding inventory of specified product at this site during
this period in the optimization run. This percentage and the Product Value are used to
calculate inventory holding costs. For example, if the inventory carrying cost percentage
is 10%, enter "10" in this field. If this value is not specified, the Inv Carrying Cost % in
the Inventory Policies is used if populated; otherwise, the Inv Carrying Cost % in Model
Options is used.

Inv Turns
Type: Number or Pairs
Specifies a piecewise linear function from which the average inventory can be calculated
during optimization.

122 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policies Multi-Period

We define the following relationship between Average Inventory and Throughput:

Average Inventory = m x Throughput
Where m is the inverse of the inventory turns value.

Max Inv Qty

Type: Number
Specifies the maximum number of units of specified product that this site can stock
during this period.

Min Inv Qty

Type: Number
Specifies the minimum number of units of specified product that this site is allowed to
stock during this period.

Scheduled Receipt
Type: Number
Enter the number of units that this site is to receive during this period outside of the
other logic set up in the model.

Safety Stock
Type: Number
Specifies the quantity or Days of Supply (depending on the Safety Stock Basis) to be held
in inventory in the Network optimization. This value can be changed by period in the
Multi-Period Inventory Policies table. This field is an input for Network Optimization. To
calculate this value, use Safety Stock Optimization.

Disposal Cost
Type: Number
Enter the disposal cost that is incurred when the shelf life expires for this by-product at
this site in this period. In multi-period models, if a Disposal Cost value is not defined for
the first period in the Inventory Policies Multi-Time Period table, Supply Chain Guru uses
the Disposal Cost in the Inventory Policies table.
Supply Chain Guru supports disposal cost both for products that expire based on their
shelf life and those by-products that are trash (not expired)
 Expired Products – If the by-product reaches its shelf life before the model ends, it is
an expired product. You can define a disposal cost that is incurred when the shelf life
of a by-product expires within the model horizon. Supply Chain Guru will determine
whether it is cheaper to incur the disposal cost and get rid of the product, or hold it in
inventory based on inventory and production costs.
The Disposal Cost field in the Inventory Policies and Inventory Policies Multi-Period
tables enable you to set a disposal cost per product per site for each time period. You
must define Inventory Policies for products that can expire, even if you are not
applying a Disposal Cost.
For expired products, the cost is reported in the Flow Transportation Cost field on the
Customer Flows Optimization Output table, for a flow with a Customer named "Trash".
The Mode is “EXPIRED PRODUCT”.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 123

Chapter 2 Multi-Time Period Tables

Note: The Disposal Cost fields for product expiration are available as target fields when
creating Input Pipes.

 Trashed Products – A by-product is considered trash if it has not reached its expiration
date (end of shelf life) by the end of the model and if there are no Inventory Policies
defined for the product. If there are Inventory Policies defined, it is assumed that the
by-product should be held in inventory, rather than trashed. In this case, an inventory
holding cost may be incurred.
If a by-product is to be trashed (that is, no Inventory Policies have been defined), you
can define a disposal cost to be incurred for an unexpired by-product, in other words
the cost to dispose of by-products created as part of your Bills of Material. This is
referred to as a “trashing cost” and applies to unused, unexpired by-product. You
specify this using the “Disposal cost per unit of by-product” on the Modeling Options
tab of Optimization Options.
The disposal cost for trashed products is reported in the Flow Transportation Cost field on
the Customer Flows Optimization Output table, for a flow with a Customer named
"Trash". The Mode is “UNUSED PRODUCT”.

Product Value
Type: Number
Data: Enter a monetary value for each unit. The Product Value field is used to calculate
the inventory investment and inventory holding costs. This enables you to vary the
product value at a specific site by time period. It is incorporated in the following formula:
Inventory holding cost = Inventory Quantity * Product value * Holding Cost Percentage *
Length of Time in Inventory
In Network Optimization, the Product Value in the Inventory Policies table overrides the
Product Value in the Products table. In Simulation, the Product Value in the Products table
is always used.

Inv Cost Other

Type: Number
Specifies any additional inventory costs not covered by other categories. Enter the cost
per unit of inventory per period.

Min and Max Safety Stock Qty

Type: Number
Specifies hard constraints on the safety stock for the product-location combination.

Min and Max Service Time

Type: Number
Specifies hard constraints for the service time quoted by the Site to its downstream sites.
This service time is expressed in units of DAY. For these fields, enter the number of days
(do not specify a time unit).

Reorder Point
Type: Number

124 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Policies Multi-Period

Specifies the inventory level at which a request for restocking (additional inventory
provided from a Sourcing Policy) is submitted.

Reorder Qty
Type: Number
Specifies the amount of product requested at the reorder point to refill inventory.

Service Requirement
Type: Number
Specifies the required service level of the product for customer-facing sites. The number
must be input as a fraction - that is, 95% would be input as .95, not 95 in the table. A
Service Requirement value of .50 ensures that no safety stock is held (that is, if the
service definition is Type 1). If no service requirements are specified at any site, the
service requirement will default to 95%. If Service Requirements are not specified
upstream from a site where a Service Requirement is specified, this requirement is
considered for the service level at the upstream sites.

Transportation Policies Multi-Period

Note: If you are using Transportation Policies Multi-Period records with Safety Stock
Optimization, you must have corresponding records in the regular Transportation
Policies table.

Period Name
Type: Special
Select the Time Period in which the Transportation Policy data changes.

Source Site
Type: Text
Choose the source site from which the product is to be transported for this time period.

Destination Site
Type: Text
Select the destination site that receives the product for this time period.

Product Name
Type: Text
Choose the product to be transported for this time period. Transportation Policies can be
product-specific or product-neutral. Specifying a product creates a product-specific
Transportation Policy that only affects transporting this product from Site A to Site B. No
other product uses this policy. Leave the product field empty to define a Transportation
Policy that applies to all the products from one site to another. If a product-specific policy
does not exist for a given product between Site A and Site B, the product-neutral policy is
used.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 125

Chapter 2 Multi-Time Period Tables

Mode
Type: Text
Specify a mode for the shipment.

Avg Cost
Type: Number
Enter the change in the Average Cost during this time period. The Avg Cost field is related
to the Cost Basis field, which is specified on the Standard Transportation Policies table.
The value entered in the Avg Cost field is the transportation cost per Cost Basis unit. For
example, if Cost Basis is Qty, Avg Cost should be the cost to ship 1 unit. If Cost Basis is
Distance, the Avg Cost should be the cost of shipping 1 unit of distance. Avg Cost has an
Average Cost Field Guru associated with it.

Flow Reqt
Type: Number
Enter the amount of this product required for shipment over the transportation lane for
this time period. Flow refers to the amount of product moved by this Transportation Policy
in a given time period. Optimization uses flow requirements as constraints.

Flow Reqt Type

Type: Text
Choose the flow requirement type for this period: conditional minimum, minimum,
maximum, or fixed. This selection defines how the Flow Requirement is used in
optimization. If conditional minimum is specified as the type, a minimum flow is
necessary to use this transportation lane for any shipments. In other words, the flow can
be 0 or higher than the minimum.

Load Cost
Type: Number
Cost per unit to load product during this period.

Unload Cost
Type: Number
Cost per unit to unload product during this period.

Return Trip Cost

Type: Number
Enter the cost of making the return trip back to the source.

Duty Rate
Type: Number
Enter a duty rate to represent the taxes and tariffs that are levied for each shipment on
this lane for this time period. The actual duty cost is calculated by multiplying the duty
rate by the shipment’s total value (product value multiplied by shipment quantity.)

126 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Assets Multi-Period

Days Between Replenishments

Type: Number
Specifies the number of days between receipt of additional product at the destination
site. This field is primarily used in cycle stock optimization.

Minimum Shipment Quantity

Type: Number
In Safety Stock Optimization, the Minimum Replenishment Quantity is the maximum of
the Sourcing Policies Min Order Qty and the Transportation Policies Minimum Shipment
Quantity.

Minimum Service Time

Type: Number
Specifies the constraint for the minimum service time on the lane. This time is in units of
DAY. Enter the number of days (do not specify a time unit).

Maximum Service Time

Type: Number
Specifies the constraint for the maximum service time on the lane. This time is in units of
DAY. Enter the number of days (do not specify a time unit).

Transportation Assets Multi-Period

Period Name
Type: Special
Select the name of the time period for which the changes for this transportation asset are
to occur.

Name
Type: Text
Select the name of the asset which changes during this time period.

Units
Type: Number
Enter the number of units of this asset that are available for use in the network during
this time period. Units must be a whole number; for example, you cannot have half a
truck.

Note: Be sure to specify the Asset being used in the Asset field of the Transportation
Policies data table.

Unit Fixed Cost

Type: Number

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 127

Chapter 2 Multi-Time Period Tables

Enter the total cost of owning or using each unit of this asset during this time period. For
example, this could be the cost of maintaining a vehicle in the fleet, or the administrative
costs for operating it in the period.

Hourly Cost Cap

Type: Function/Pairs
Specify the <Cap,Cost> structure per hour for this asset during this period.

Processes Multi-Period
Period Name
Type: Special
Select the time period in which the changes in the routing occur.

Process Name
Type: Text
Enter a descriptive name for the process you are specifying for this period.

Process Step
Type: Text
Enter a descriptive name for this particular step of the process that you are specifying.

Next Process Step

Type: Text
Choose the next step of the process. When the process is complete, choose None or leave
the Next Process Step field blank.

Work Time Per Unit

Type: Time
Enter the fixed amount of time required for each unit that goes through this step,
regardless of the production quantity. It is not exclusive of the Work Time Per Order as
defined in the Processes table. You can define both a fixed Work Time Per Order and a
Work Time Per Unit. This field accepts either straight time (SEC, MIN, HR, DAY, WK) or
probability distributions.
Important: If you do not specify a time unit, the default is DAY.

Average Changeover Time

Type: Time
Enter the average fixed amount of time required for each order that goes through this
step at this work center during this period. This value includes time for such tasks as
setup and changeover. It is not exclusive of the Work Time per Unit. You can have both a
fixed Average Changeover Time and a Work Time per Unit. This field accepts both straight
time (SEC, MIN, HR, DAY, WK) and probability distributions.
Important: If you do not specify a time unit, the default is DAY.

128 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Centers Multi-Period

The Work Time Per Order field in the Processes table acts as a setup time for individual
orders. For example, assume that you have a lot size of 2, demand of 5 and a Average
Changeover Time Per Order value of 1 HR. Optimization determines the number of orders
as 2.5 (that is, the total production amount is 2.5 * the lot size). It would therefore incur
a total changeover time of 2.5 HR. The total production cost is:
(Cost Per Unit * Units) + (Setup Cost * # of orders * Average Changeover Time).

Resource Usage Hours

Type: Number
Specify the number of hours the resource is used for this process step in this period.

Lot Size
Type: Number
Enter the lot size for this process step in this period. The lot size is used to break up a
production quantity into smaller amounts. For example, if a production quantity of 1000
starts a process step with a lot size of 100, the production item will cause 10 items of 100
each to be produced.

Unit Cost
Type: Number
Enter the cost of production for each unit at this work center during this period. Each step
in a production process can have a different cost. As the production order goes through
each routing step, costs accumulate until the order is complete. The total cost of the
order is then added to the site production cost statistics.

Setup Cost
Type: Number
Specify the initial costs for implementing the Work Center to process a specified product
during this period. Setup Costs are applied for each batch, i.e. the setup costs are
calculated based upon the lot size and the number of units processed.

Yield
Type: Number
Enter the loss factor due to this work center during this period. For example, if 10% of
the material that was input to a cutting production step (making skewed edges straight)
is lost due to the cutting, the yield factor is equal to 0.9: 90% of the material that was
inputted is outputted after this production step.
Demand (from a customer/facility or input of the next work center) determines the net
production, that is the amount that needs to be output of a certain work center. The input
needed at a work center (gross production) is calculated from the demand and the yield
value.

Work Centers Multi-Period

Period Name
Type: Special

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 129

Chapter 2 Multi-Time Period Tables

Select the Period for which the changes occur.

Name
Type: Text
Select the name of the work center which changes during this time period.

Site
Type: Text
Select the Site where this work center is located during this time period.

Fixed Startup <Cap,Cost>

Type: Function/Pairs
Defines the relationship between startup capacities and startup cost. The function is
specified by a series of coordinates. The first number in the coordinate indicates shipment
capacity. The second number indicates the startup cost.
For example, suppose you have an entry like the following:
<0, 1000000> <500000, 2000000> <750000, 2500000>
This entry indicates that before any products can be shipped, an initial expenditure of
$1,000,000 must be invested. To increase capacity to more than 500,000, an initial
expenditure of $2,000,000 is required. For capacity to be greater than 750,000, an initial
expenditure of $2,500,000 is required.
Fixed Startup Costs are always applied to the optimization horizon.

Fixed Operating <Cap,Cost>

Type: Function/Pairs
Defines the relationship between operating capacity and operating costs for this time
period. The function is specified by a series of coordinates. The first number in the
coordinate indicates production capacity. The second number indicates operating cost.
For example, suppose you have an entry like the following:
<0, 1000000><500000, 2000000> <15000000, INF>
This entry indicates that an initial operation cost of $1,000,000 is required before any
product is produced. To increase capacity to more than 500,000, the operating cost must
increase to $2,000,000. The maximum capacity is 15,000,000 as indicated with a cost of
infinite (INF). If the cost is INF for a certain capacity level, that capacity is considered as
a hard constraint.

Closing Cost
Type: Number
Enter the monetary cost of shutting down the operations of this work center in this
period. Closing costs are applied if a work center with the type Existing Work Center is
closed during this period.

130 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Resources Multi-Period

Work Resources Multi-Period

Period Name
Type: Special
Select the time period in which the changes to the work resource will occur.

Site
Type: Text
Specify the site where this resource is used during this period.

Name
Type: Text
Select the name for the work resource which will change during this time period.

Units
Type: Number
Enter the number of identical units of this resource available to perform work during this
time period. It must be a whole number.

Unit Fixed Cost

Type: Number
Enter the fixed unit cost for each work resource during this period. This is the fixed cost of a
work resource, such as the general/administrative costs per worker for the period.

Hourly Cost Cap

Type: Text
Specify the <Cap,Cost> structure per hour for this resource during this period.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 131

Chapter 2 Multi-Time Period Tables

132 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Chapter 3

Constraints Tables

The following are Supply Chain Guru Constraints Tables:

 Flow Constraints
 Flow Count Constraints
 Inventory Constraints
 Inventory Count Constraints
 Production Constraints
 Production Count Constraints
 Site Constraints
 Work Center Constraints
 Greenfield Service Constraints
 Expression Constraints
 Expression Based Costs
 Open/Close Relations
 Sequential Objectives
 Decomposition Sets

Flow Constraints
Expression Name
Type: Text
This is an optional name for the Flow Constraint. You can then use the Flow Constraint in:
 an Expression Constraint by specifying the Expression Name for either the Expression
1 or Expression 2 value. This enables you to combine constraints.
 an Expression Based Cost by using this value in the Expression Name field. This
enables you to defined fixed and variable cost components that are incurred as a
result of the constraint.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 133

Chapter 3 Constraints Tables

Period Name
Type: Special
Select the period which the constraint will apply to. If there are no Periods specified in the
model or when this field is left blank, the constraint will apply to the planning horizon.

Source Site
Type: Text
Select the source site of the transportation lane to which this aggregate flow constraint
applies. When this field is left blank, the constraint applies to all sites that source the
specified destination site with specified product through specified mode: "the constraint is
aggregated over all source sites".

Destination Site
Type: Text
Select the destination site of the transportation lane to which this aggregate flow
constraint applies. When this field is left blank, the constraint applies to all destinations
sites that are sourced from the specified source site with specified product through
specified mode: "the constraint is aggregated over all destination sites".

Product Name
Type: Text
Select the product to which the aggregate flow constraint applies. When this field is left
blank, the constraint applies to all products that are transported over this lane: "the
constraint is aggregated over all products".

Mode
Type: Number
Specify which mode of a certain transportation lane the constraint applies. This field can
also be left blank, in which case the constraint is aggregated over all transportation
modes with the specified Source Site - Destination Site - Product (in case the constraint is
product-specific) combination.
This table lists the possible combinations of using specified or blank source site,
destination site, product name and mode parameter fields in the aggregate flow
constraint:

Flow Reqt
Type: Number
Enter the amount of product required for shipment from source site to destination site.
Its use is determined by three other flow requirement fields listed below; Flow
Requirement Type, Flow Requirement Basis and Flow Requirement Period. Flow refers to
the amount of product moved from source site to destination site in a given time period.

Flow Reqt Type

Type: Text
Choose the flow requirement type. This defines how the Flow Requirement is used.
 Min – At least X units must be produced

134 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Flow Count Constraints

 Max – At most X units may be produced

 Fixed – X units must be produced
 Cond Min – Either produce at least X units or produce none at all

Note: The conditional minimum flow establishes that, in order to use this source site -
destination site combinations for any shipments, a minimum flow is necessary.
Essentially this constraint is similar to saying the flow can be 0 or higher than the
minimum.

 Define – Supply Chain Guru does not use the Flow Reqt to satisfy the constraint.
Instead, the requirement value is specified in the Expression Constraint.

Flow Reqt Basis

Type: Text
Choose the flow requirement basis - Quantity, Weight or Cubic. This defines the units of
measurement for Flow Requirement.

Flow Reqt Period

Type: Text
Choose the period over which the Flow Requirement is to be established - Day, Week,
Month, Quarter, or Year. When this field is left blank the horizon of the optimization will be
used as the Flow Reqt Period.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Flow Count Constraints

Period Name
Type: Special
Select the period which the constraint will apply to. If there are no Periods specified in the
model or when this field is left blank, the constraint will apply to the planning horizon.

Source Site
Type: Text
Select the source site to which this aggregate flow constraint applies.

Destination Site
Type: Text
Select the destination site to which this aggregate flow constraint applies.

Product Name
Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 135

Chapter 3 Constraints Tables

Select the product to which the aggregate flow count constraint applies. When this field is
left blank, the constraint applies to all products that flow between the source and
destination: "the constraint is aggregated over all products".

Mode
Type: Text
Select the mode to which this aggregate flow constraint applies.

Count Value
Type: Number
Enter the number of different products that flow between the source and destination. Its
use is determined by the count type. Count refers to the number of individual product
types (SKUs, for instance) that can flow from source to destination in a given time period.

Count Type
Type: Text
Choose the flow count requirement type - minimum, maximum, or fixed. This defines
how the Count Value is used.

Source Aggregated
Type: Yes/No
If set to Yes, the flow count constraint is applied across all source sites chosen, as
opposed to each individually.

Destination Aggregated
Type: Yes/No
If set to Yes, the flow count constraint is applied across all destination sites chosen, as
opposed to each individually.

Product Aggregated
Type: Yes/No
If set to Yes, the flow count constraint is applied across all products chosen, as opposed
to each individually.

Mode Aggregated
Type: Yes/No
If set to Yes, the flow count constraint is applied across all modes chosen, as opposed to
each individually.

Period Aggregated
Type: Yes/No
If set to Yes, the flow count constraint is applied across all periods chosen, as opposed to
each individually.

136 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Constraints

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Inventory Constraints
Use this table to constrain the pre-build inventory in your model.

Expression Name
Type: Text
This is an optional name for the Inventory Constraint. You can then use the Inventory
Constraint in:
 an Expression Constraint by specifying the Expression Name for either the Expression
1 or Expression 2 value. This enables you to combine constraints.
 an Expression Based Cost by using this value in the Expression Name field. This
enables you to defined fixed and variable cost components that are incurred as a
result of the constraint.

Period Name
Type: Special
Select the period to which the constraint will apply to. If there are no Periods specified in
the model or when this field is left blank, the constraint will apply to the planning horizon.

Site Name
Type: Text
Select the site to which this Aggregate Inventory Constraint will apply to. If this field is
left blank, the constraint applies to all sites that have inventory (the constraint is then
aggregated over all sites)

Product Name
Type: Text
Select the product to which the Aggregate Inventory Constraint applies. When this field is
left blank, the constraint applies to all products that are being kept in inventory at this
particular site(s); (the constraint is aggregated over all products).

Inventory Reqt
Type: Number
Enter the amount of pre-build inventory required. Its use is determined by two other
Inventory requirement fields listed below; Inventory Requirement Type and Inventory
Requirement Basis.

Inventory Reqt Type

Type: Text

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 137

Chapter 3 Constraints Tables

Choose the Inventory Requirement Type - conditional minimum, minimum, maximum, or

fixed. This defines how the Inventory Requirement for pre-build inventory is used:
 Min – At least X amount of Inventory Units must be at that site(s).
 Max – At most X amount of Inventory Units can be at that site(s).
 Fixed – X amount of Inventory Units must be present at that particular site(s) at all
times.
 Cond. Min – Either 0 or at least X amount of Inventory must be present at that
particular site(s).

Note: The conditional minimum Inventory Aggregate Constraint is similar to saying the
Inventory can be 0 or higher than the minimum.

 Define – Supply Chain Guru does not use the Inventory Reqt to satisfy the constraint.
Instead, the requirement value is specified in the Expression Constraint.

Inventory Reqt Basis

Type: Special
Choose the Inventory Requirement Basis for pre-build inventory - Quantity, Weight, Cubic
or DOS (Days of Supply). This defines the units of measurement for the number
populated in the Inventory Requirement field.

Pre-Build Inventory
Type: Include/Exclude
Use this field to determine if the constraint is applied to the Pre-Build Inventory. The
values is one of:
 Include - If selected, the constraint is applied to Pre-Build Inventory.
 Exclude - If selected, the constraint is not applied to Pre-Build Inventory.
The Default is Include.

Note: If Pre-Build Inventory, Safety Stock, Cycle Stock and Turn-Estimated Inventory
are all set to Exclude, the constraint is ignored.

Safety Stock
Type: Include/Exclude
Use this field to determine if the constraint is applied to the Safety Stock. The values is
one of:
 Include - If selected, the constraint is applied to Safety Stock.
 Exclude - If selected, the constraint is not applied to Safety Stock.
The Default is Include.

Note: If Pre-Build Inventory, Safety Stock, Cycle Stock and Turn-Estimated Inventory
are all set to Exclude, the constraint is ignored.

Cycle Stock
Type: Include/Exclude

138 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Count Constraints

Use this field to determine if the constraint is applied to the Cycle Stock. The values is
one of:
 Include - If selected, the constraint is applied to Cycle Stock.
 Exclude - If selected, the constraint is not applied to Cycle Stock.
The Default is Exclude.

Note: If Pre-Build Inventory, Safety Stock, Cycle Stock and Turn-Estimated Inventory
are all set to Exclude, the constraint is ignored.

Turn-Estimated Inventory
Type: Include/Exclude
Use this field to determine if the constraint is applied to the Turn-Estimated Inventory.
The values is one of:
 Include - If selected, the constraint is applied to Turn-Estimated Inventory.
 Exclude - If selected, the constraint is not applied to Turn-Estimated Inventory.
The Default is Exclude.

Note: If Pre-Build Inventory, Safety Stock, Cycle Stock and Turn-Estimated Inventory
are all set to Exclude, the constraint is ignored.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Inventory Count Constraints

Period Name
Type: Special
Select the period which the constraint will apply to. If there are no Periods specified in the
model or when this field is left blank, the constraint will apply to the planning horizon.

Site Name
Type: Text
Select the site to which this aggregate inventory constraint applies.

Product Name
Type: Text
Select the product to which the aggregate inventory count constraint applies. When this
field is left blank, the constraint applies to all products that are held in inventory at this
site: "the constraint is aggregated over all products".

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 139

Chapter 3 Constraints Tables

Count Value
Type: Number
Enter the number of different products held in inventory at the site. Its use is determined
by the count type. Count refers to the number of individual product types (SKUs, for
instance) that can be held at the site in a given time period.

Count Type
Type: Text
Choose the inventory count requirement type - minimum, maximum, or fixed. This
defines how the Count Value is used.

Site Aggregated
Type: Yes/No
If set to Yes, the inventory count constraint is applied across all sites chosen, as opposed
to each individually.

Product Aggregated
Type: Yes/No
If set to Yes, the inventory count constraint is applied across all products chosen, as
opposed to each individually.

Period Aggregated
Type: Yes/No
If set to Yes, the inventory count constraint is applied across all periods chosen, as
opposed to each individually.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Production Constraints
Expression Name
Type: Text
This is an optional name for the Production Constraint. You can then use the Production
Constraint in:
 an Expression Constraint by specifying the Expression Name for either the Expression
1 or Expression 2 value. This enables you to combine constraints.
 an Expression Based Cost by using this value in the Expression Name field. This
enables you to defined fixed and variable cost components that are incurred as a
result of the constraint.

140 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Production Constraints

Period Name
Type: Special
Select the period to which the constraint will apply to. If there are no Periods specified in
the model or when this field is left blank, the constraint will apply to the planning horizon.

Site Name
Type: Text
Select the site to which this Aggregate Production Constraint will apply to. If this field is
left blank, the constraint applies to all sites that produce product (the constraint is then
aggregated over all sites)

Product Name
Type: Text
Select the product to which the Aggregate Production Constraint applies. When this field
is left blank, the constraint applies to all products that are being produced at this
particular site(s); (the constraint is aggregated over all products).

Process Name
Type: Text
Select the process to which the Aggregate Production Constraint applies. When this field
is left blank, the constraint applies to all processes that are being used at this particular
site (the constraint is aggregated over all products).

Production Reqt
Type: Number
Enter the amount of product required to be produced. Its use is determined by three
other production requirement fields listed below: Production Requirement Type,
Production Requirement Basis, and Production Requirement Period.

Production Reqt Type

Type: Special
Enter the type of production constraint placed, based on the production requirement
specified:
 Min – At least X units must be produced
 Max – At most X units may be produced
 Fixed – X units must be produced
 Cond Min – Either produce at least X units or produce none at all
 Define – Supply Chain Guru does not use the Production Reqt to satisfy the constraint.
Instead, the requirement value is specified in the Expression Constraint.

Production Reqt Basis

Type: Special
Enter the basis by which the production constraint is placed:
 Qty - X refers to the quantity of units

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 141

Chapter 3 Constraints Tables

 Weight - X refers to the weight of units

 Cubic - X refers to the cubic volume of units

Production Reqt Period

Type: Special
Enter the time period over which the specified production requirement must be satisfied.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Production Count Constraints

Period Name
Type: Special
Select the period which the constraint will apply to. If there are no Periods specified in the
model or when this field is left blank, the constraint will apply to the planning horizon.

Site Name
Type: Text
Select the site to which this aggregate production constraint applies.

Product Name
Type: Text
Select the product to which the aggregate production count constraint applies. When this
field is left blank, the constraint applies to all products that are made in production at this
site: "the constraint is aggregated over all products".

Count Value
Type: Number
Enter the number of different products put through production at the site. Its use is
determined by the count type. Count refers to the number of individual product types
(SKUs, for instance) that can be made at the site in a given time period.

Count Type
Type: Text
Choose the production count requirement type - minimum, maximum, or fixed. This
defines how the Count Value is used.

Site Aggregated
Type: Yes/No

142 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Site Constraints

If set to Yes, the production count constraint is applied across all sites chosen, as
opposed to each individually.

Product Aggregated
Type: Yes/No
If set to Yes, the production count constraint is applied across all products chosen, as
opposed to each individually.

Period Aggregated
Type: Yes/No
If set to Yes, the production count constraint is applied across all periods chosen, as
opposed to each individually.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Site Constraints
Period Name
Type: Special
This field is not required, however if you are running a multi-period model, it will consider
the entire model horizon if left blank. This field allows you to enter a specific period for
the site requirement. In multi-period models, once a potential site has been opened, it
cannot be closed.

Site Name
Type: Text
Allows you to choose from the available sites or site sets. For the model to be feasible,
included sites must be set to potential or consider.

Note: When creating Site Constraints, use a group that has been defined as a Set. If the
group uses Treat As Individuals, the constraint will not work.

Open Sites Value

Type: Number
Specify the number of sites. This number is used as a constraint based on the Open Sites
Type value.

Open Sites Type

Type: Number
Type: Special
Specify whether the constraint Open Sites Value represents:

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 143

Chapter 3 Constraints Tables

 Min – The minimum number of sites that must be used.

 Max – The maximum number of sites that can be used.
 Fixed – The number of sites that must be used.

Status
Type: Include/Exclude
Specify whether or not to include the specific constraint in the model. See the Scenarios
section for best uses of this field.

Work Center Constraints

Period Name
Type: Text
This field allows you to select a specific period for the work center requirement, a period
group that has Function = Set, or the entire horizon. In multi-period models, once a work
center has been “opened”, it cannot be “closed”. This field is not required; however if you
are running a multi-period model, Supply Chain Guru will consider the entire model
horizon if left blank.

Work Center Name

Type: Text
Select the work center to which the constraint applies. This can be a specific work center,
a work center group, (All) for all work centers, or blank which behaves the same as
selecting (All). Work center groups that have a Function of “Set” will be displayed as
“(Set) <groupname>”.

Site Name
Type: Text
Select the site to which the constraint applies. This can be a specific site, a site group,
(All) for all sites, or blank which behaves the same as selecting (All). Site groups that
have a Function of “Set” will be displayed as “(Set) <groupname>”; those with a Function
of “Treat As Individuals” will be displayed as “(Group) <groupname>”.

Open Work Centers Value

Type: Number
Specify the number of work centers. This number is used as a constraint based on the
Open Work Centers Type value.

Open Work Centers Type

Type: Special
Specify whether the constraint Open Work Centers Value represents:
 Min – The minimum number of work centers that must be used.
 Max – The maximum number of work centers that can be used.
 Fixed – The number of work centers that must be used.

144 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Greenfield Service Constraints

Status
Type: Include/Exclude
Specify the status of the constraint:
 Include – The constraint is included when the model is run.
 Exclude – The constraint is excluded when the model is run.

Greenfield Service Constraints

Constraint Name
Type: Text
This field is the name of the Greenfield service constraint.

Distance
Type: Number
This field specifies the distance range from the DC for customer sites.

Percentage Demand/Customers Served

Type: Number
This field specifies the minimum percentage of demand or customers that must be served
within the distance specified by Distance. For example, if you have 400 customers and
specify a Percentage Demand/Customers Served of 50, the Greenfield Analysis must
serve at least 200 customers within the Distance value.
The Service Constraint Basis on the Greenfield Options tab of Optimization Options
determines whether the constraint is applied to Demand or Customers served.

Status
Type: Include/Exclude
Select one of:
 Include – to include the constraint in the greenfield analysis.
 Exclude – to exclude the constraint from the greenfield analysis.

Expression Constraints
Expression Name
Type: String
This field is the name of the expression constraint.

Coefficient 1
Type: Number
Use this field to apply a multiplier to the expression you enter in Expression 1.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 145

Chapter 3 Constraints Tables

Expression 1
Type: Special
Enter the name of the first expression in the expression constraint record. This will be one
of the following:
 The Expression Name from a Flow Constraint, Inventory Constraint, Production
Constraint
 The Expression Name from an Expression Constraint
 The Cost Name from an Expression Based Cost
You can define Expression 1 or Expression 2 or both, as needed.

Coefficient 2
Type: Number
Use this field to apply a multiplier to the expression you enter in Expression 2.

Expression 2
Type: Special
Enter the name of the second expression in the expression constraint record. This will be
one of the following:
 The Expression Name from a Flow Constraint, Inventory Constraint, Production
Constraint
 The Expression Name from an Expression Constraint
 The Cost Name from an Expression Based Cost
You can define Expression 1 or Expression 2 or both, as needed.

Expression Type
Type: Special
Enter the type of expression constraint:
 Min – The value specified in the Constraint Requirement must be reached.
 Max – The value specified in the Constraint Requirement cannot be exceeded.
 Fixed – The value specified in the Constraint Requirement must be used.
 Cond Min – The value specified in the Constraint Requirement must be reached or
none at all.
 Define – Supply Chain Guru does not use the Constraint Requirement to satisfy the
constraint. This setting can be used when you are nesting Expression Constraints.

Constraint Requirement
Type: Special
For all Expression Types other than Define, enter the value that acts as the constraint;
that is, the minimum, maximum or fixed value.

Status
Type: Include/Exclude
Select one of:

146 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Expression Based Costs

 Include – to include the expression constraint during optimization.

 Exclude – to exclude the expression constraint during optimization.

Expression Based Costs

Cost Name
Type: Text
This field is the name of the expression based cost.

Expression Name
Type: Text
Enter the name of the expression to which the cost applies.

Fixed Cost Component

Type: Number or Pairs
Enter the fixed cost to be applied to the expression. You can define the cost as a single
value, or specify a step cost. For example, if you define the Fixed Cost Component as
<0,5000><250,40000><1000,75000>, if the constraint value is 600, the Fixed Cost will
be 40000.

Variable Cost Component

Type: Number or Pairs
Enter the cost to be applied to the Quantity, Weight or Cubic as defined by the
Expression. You can define the cost as a single value, or specify a step cost. The cost will
be calculated based on the Variable Cost Type you select.

Variable Cost Type

Type: Special
Select one of:
 Linear – A single variable cost is applied for all Quantity, Weight or Cubic as defined by
the Expression. You must enter a single value for the Variable Cost Component when
using Linear as the Variable Cost Type. The <Quantity,Cost> format is not supported
for this cost type.
 Incremental – Piecewise costs will be calculated based on break points. For example,
assume you have set up the Variable Cost Component as <0,1.50> <5000, 1.25>
<10000, 1.00> for a Flow Constraint and the flow is 20,000 units for the referenced
expression. The total cost will be:
(5,000 - 0)*1.50 + (10,000 - 5,000)*1.25 + (20,000 - 10,000)*1.00 = 23,750
 All Item – The cost will be based on the break in which the total occurs. Given the
same example from above, Variable Cost Component as <0,1.50> <5000, 1.25>
<10000, 1.00> for a Flow Constraint and a flow of 20,000 units, the total cost will be:
20,000 * 1.0 = 20,000

Status
Type: Include/Exclude

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 147

Chapter 3 Constraints Tables

Select one of:

 Include – to include the expression based cost during optimization.
 Exclude – to exclude the expression based cost during optimization.

Open/Close Relations
Period Name
Select the period or set of periods to which the constraint will apply. If there are no
Periods specified in the model or when this field is left blank, the constraint will apply to
the planning horizon.

If Type
Select the type of constraint from the following:
 At Least
 At Most
 Equals
 Not Equals

If Value
Enter the numeric value associated with the If Type selection. For example, you may
define a constraint where at least 2 sites are open in a specified period. The If Value
would be 2.

If Site Name
Select the site, site set or (All) sites to which the “If” clause applies.

If Work Center Name

Select the work center, work center set or (All) work centers to which the “If” clause
applies.

If Condition
Select whether the condition of the site or work center in the “If” clause is Open or
Closed.

Then Type
Select the type of constraint from the following:
 At Least
 At Most
 Equals
 Not Equals

148 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Sequential Objectives

Then Value
Enter the numeric value associated with the Then Type selection. For example, you may
define a constraint where if 2 sites are open in a specified period, exactly 1 work center
must be open. The Then Value would be 1

Then Site Name

Select the site, site set or (All) sites to which the “Then” clause applies.

Then Work Center Name

Select the work center, work center set or (All) work centers to which the Then clause
applies.

Then Condition
Select whether the condition of the site or work center in the Then clause is Open or
Closed.

If And Only If
When set to No, if the “If” clause is evaluated as True, the “Then” clause must also be
True. If the “If” clause is False, the “Then” clause can be either True or False.
When set to Yes, if the “If” clause is evaluated as False, the “Then” clause must also be
False.

Status
Use this field to specify whether a record is included or excluded from optimization.

Sequential Objectives
Objective
Select the objective to be used in Sequential Optimization. This represents the objective
function or hard constraint violation that you want to use during solving. The same
objective can be selected more than once, enabling you to group the objective with
various other objectives based on Priority.

Priority
Priority determines an objective group. Each group is solved together. All Objectives with
Priority 1 are grouped together and solve, then all Objectives with Priority 2 are grouped
together and solved next, and so on.

Tolerance
The tolerance specifies the amount of deviation in the objective value when solving the next 
hierarchy.
For example, assume the first Priority objective (Total Transportation Cost) has a
Tolerance of 0.25 and no Tolerance is specified for the second Priority objective (Total
Profit). Supply Chain Guru first minimizes Total Transportation Cost, then maximizes Total
Profit such that the new value of total Transportation Cost does not deviate more than
25% from the value when the first hierarchy was solved.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 149

Chapter 3 Constraints Tables

By default, the tolerance is 1.0e-6.

Weight
This is a weight applied to the objective function. For example, if your model has a Fixed
Operating Cost of 10000 and you specify a Weight of 2 for the Total Fixed Operating Cost
Objective, this will be treated as a cost of 20000. The default Weight is 1.

Site
For constraints that are site-dependent, specify the site(s) to which the objective function
applies. For example, Site Throughput Capacity and Demand are Objectives that can be
constrained at the Site level.

Source
For constraints that are source location-dependent, specify the source sites to which the
objective function applies. For example, Flow is an objective that can be constrained at
the Source level.

Destination
For constraints that are destination location-dependent, specify the destination sites to
which the objective function applies. For example, Flow is an objective that can be
constrained at the Destination level.

Product
For constraints that are product-dependent, specify the products to which the objective
function applies. For example, Flow and Demand are objectives that can be constrained
at the Product level.

Mode
For constraints that are mode-dependent, specify the modes to which the objective
function applies. For example, Flow is an objective that can be constrained at the Mode
level.

Period
For constraints that are period-dependent, specify the period(s) to which the objective
function applies. For example, Work Center Throughput Capacity is an objective that can
be constrained at the Period level.

Asset
For constraints that are asset-dependent, specify the asset(s) to which the objective
function applies.

Process
For constraints that are process-dependent, specify the process(es) to which the
objective function applies. For example, Production is an objective that can be
constrained at the Process level.

150 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Decomposition Sets

Expression
Identify the Expression Name to which the objective function applies.

Type
Identify the constraint type to which the objective function applies (Min, Max, Cond Min,
Fixed).

Other
Use this field to enter Work Center or Bill of Materials (BOM) names for constraints based
on Work Centers or BOMs.

Status
Use this field to specify whether a record is included or excluded from optimization.

Decomposition Sets
Set Name
Enter or select the name of a group that has been defined with a Function of Set.

Status
The status field allows you to specify whether the decomposition set is included or
excluded from optimization. Note that the set is only used when the Decomposition
Method is enabled. If the field is left blank, the set is assumed to be included.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 151

Chapter 3 Constraints Tables

152 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Chapter 4

Optimization Output Tables

The following are Supply Chain Guru Optimization Output Tables:

 Network Summary
 Financial Summary
 Customer Flows
 Interfacility Flows
 Productions
 Customer Summary
 Productions
 Inventory
 Aggregated Demand
 Product Summary
 Production Process Flows
 Aggregated Customer Demand
 Work Resource Summary
 Bill Of Materials Summary
 Work Center Summary
 Network Paths
 Network Paths Summary
 Facility Status Decision History
 Multi-Objective Details
Safety Stock Optimization:
 Aggregated Customer Demand
 Aggregated Customer Facing Facility Demand
 Customer Demand Profile
 Facility Demand Profile
 Inventory Policy Summary
 Inventory Policy Details
Greenfield:

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 153

Chapter 4 Optimization Output Tables

 Greenfield Summary
 Greenfield Service
 Greenfield Facilities
 Greenfield Flows
Vehicle Route Optimization:
 Vehicle Route Optimization Summary
 Assets
 Routes
 Stops
 Invalid Shipments
 Unrouted Shipments
 Segments
 Input Shipments
 Route Breaks
 Delivered Shipments
 PVRP Delivered Shipments
 Asset Summary
Constraints:
 Expression Summary
 Expression Based Cost Summary
 Constraint Summary

Network Summary
Optimization output tables summarize cost, site, network flow, and demand statistics for
your supply chain. The following is an explanation of how each of these metrics are
measured or calculated.
The network summary summarizes total profit, costs, and revenue.

Scenario
The scenario for which the summary data was generated.

Model Run Time

The date and time of the optimization run.

Model Optimization Type

The selected objective of the optimization, and the algorithm selected.

Model Period In Days

The number of days that are optimized according to the model.

154 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Summary

Total Profit
The total profit of the optimization network and inventory structure.
Total profit = total revenues - total cost

Total Cost
The total network costs incurred after optimization.
total cost = total fixed startup cost + total fixed operating cost + total closing cost + total
production cost + total transportation cost + total duty cost + total warehousing cost +
total facility inventory cost + total in transit inventory cost + total sourcing cost + total
transportation asset cost + total work resource cost + total capital investment + (cost of
carbon * amount of CO2 emission)

Total Revenue
The total revenue generated by units shipped to customers.
total revenue = (sum of all product demand met) * (price per product)

Total Fixed Startup Cost

The total cost of setting up potential facilities and work centers in the network.

Total Fixed Operating Cost

The total cost to keep facilities and work centers in the network functional.

Safety Stock Cost

The costs from the Inventory Policy Summary output table. If Safety Stock Optimization
has not been run on this model, the value is blank.

Note: This field is currently not implemented.

Model Name
The name of the model for which optimization was run.

Total Ending Book Value

The sum over the Book Value of all Facilities and Work Centers in the Facility Summary
and Work Center Summary output tables for the last period of the model, for the
specified (sub)-scenario. It is NOT summed over all periods.

Total Closing Cost

The total cost of stopping production at facilities and work centers in the network.

Total Capital Investment

The sum over the Total Capital Investment values in the Facility Summary and Work Center
Summary output tables for the specified (sub)-scenario.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 155

Chapter 4 Optimization Output Tables

Accumulated Depreciation
The sum over the Depreciation values in the Facility Summary and Work Center Summary
output tables for the specified (sub)-scenario.

Total Production Cost

The total cost of producing units in the network.

Total Inbound Warehousing Cost

The total cost of bringing units into facilities, from dock to stock, excluding transportation
costs in the network.

Total Outbound Warehousing Cost

The total cost of moving units out of facilities, from stock to dock, excluding
transportation costs in the network.

Total Transportation Cost

The total cost of transporting units between sites in the network.

Total Duty Cost

The total cost from taxes and tariffs levied on shipments.

Total Warehousing Cost

The total of all warehousing costs.

Total Sourcing Cost

The total cost of sourcing products from facilities.

Total Transportation Asset Cost

The total cost from usage of transportation assets.

Total Work Resource Cost

The total cost from usage of work resources.

Total Expression Based Cost

This is the total cost incurred through the use of Expression Based Costs.

Total Unserved Demand Qty

The total quantity of demand that is unserved.

Gap Percent
The percentage gap between best bound and best solution.

Solution Notes
Currently not in use.

156 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Summary

Total CO2
The total emissions of CO2 in kilograms.

Total Carbon Cost

The total cost attributed to carbon emissions, based on the Carbon Cost from the
Greenhouse Gases table.

Initial Carbon Offsets

The total number of carbon offsets available to the network.

Optimized Carbon Offsets

The number of offsets required by the optimal model.

Optimized Carbon Offset Cost

The cost allocated to purchasing optimal carbon offsets.

Carbon Offset Price

The price of carbon offsets in the model.

Total Cycle Stock

The total amount of cycle stock held in the inventory optimization.

Total Min Inventory

The total safety stock held in the inventory optimization.

Total Pre Build Inventory

The total amount of pre-build inventory held in the inventory optimization.

Total Inv Holding Cost

This is the Total Inventory Holding Cost. It is calculated as:
Total Inventory Holding Cost (Network Summary) = In-Transit Inventory Cost (Customer
Flows) + Total Inventory Holding Cost (Facility Summary)

Note: A “Closed” site is a site that does not allow product to flow in or out. If a site that
is currently holding inventory is closed, the inventory is held for the remaining
periods in the model and will incur any associated holding costs.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 157

Chapter 4 Optimization Output Tables

being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Financial Summary
This table displays financial information including startup, operating and closing costs,
depreciation, and capital investment.
The table includes a record for each period in the scenario, and a record that represents
the total over all periods.

Scenario
The scenario for which the output data was generated.

Period Name
The name of the period to which these financial statistics apply. For the network total, the
period Name is displayed as Total.

Total Profit
The total profit of the optimization network and inventory structure.
total profit = total revenues - total cost

Present Value
The value of the network when the annual Discount Rate (NPV) specified in Model Options
is applied to the non-discounted value. This is calculated as:
1 / (1 + r) ^ (Elapsed Days/Days Per Year)
where:
r = Discount Rate entered in Model Options
Elapsed Days = Number of days from the model Start date to the end of the time
period.
Days Per Year = 365

Total Cost
The total network cost incurred after optimization.
total cost = Total fixed startup cost + total fixed operating cost + total closing cost +
total production cost + total transportation cost + total duty cost + total warehousing
cost + total facility inventory cost + total in transit inventory cost + total sourcing
cost + total transportation asset cost + total work resource cost

Total Revenue
The total revenue generated by units shipped to customers.
total revenue = (sum of all product demand met) * (price per product)

Capital Investment
The sum over the Total Capital Investment values in the Facility Summary and Work
Center Summary output tables for the specified (sub)scenario.

158 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Financial Summary

Depreciation
The sum over the Depreciation values in the Facility Summary and Work Center Summary
output tables for the specified (sub)scenario.

Closing Cost
The total cost of stopping production at facilities in the network.

Fixed Startup Cost

The total cost of setting up facilities in the network.

Fixed Operating Cost

The total cost to keep facilities in the network functional.

Transportation Cost
The total cost incurred in transporting units between sites in the network.

Transportation Asset Cost

The total cost from usage of transportation assets.

Production Cost
The total cost of producing units in the network.

Sourcing Cost
The total cost of sourcing products from facilities.

Warehousing Cost
The total of all warehousing costs.

Duty Cost
The total cost from taxes and tariffs levied on shipments.

Inventory Holding Cost

The Inventory Holding Cost is calculated as:
Inventory Holding Cost (Financial Summary) = In-Transit Inventory Cost (Customer
Flows) + Total Inventory Holding Cost (Facility Summary.

Work Resource Cost

The total cost from work resources.

Carbon Cost
The total cost from carbon emissions.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 159

Chapter 4 Optimization Output Tables

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
Click on the field guru for the field to open a Scenario Item Wizard summary table. This
table lists the scenario and sub-scenario names, in addition to the field that is being
modified and the operator and value of that field.

Customer Flows
This output table summarizes the specifics of all shipments to customers in the network.

Scenario
The scenario for which the summary data was generated.

Source Name
The site which shipped the product.

Customer Name
The customer site which receives the shipment.

Product Name
The name of the product being shipped.

Mode
The lane differentiation parameter defined in Transportation Policies.

Period Name
The period in which this flow occurs.

Demand
The total customer demand for this product over this lane in this period. This is the
demand that the flow is attempting to satisfy. This may represent a substituted product if
product substitution is being used, even though no actual customer demand exists for the
substituted product.

Flow Units
The number of units shipped over this lane in this period.

160 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Customer Flows

Flow Weight
The weight of the units shipped over this lane in this period.
Flow Weight = Flow Units * Product Weight

Flow Cubic
The cubic size of the units shipped over this lane in this period.
Flow Cubic = Flow Units * Product Cubic

Flow Revenue
The revenue generated by the units shipped over this lane in this period. The Price is
from the Products table, but you can override it by specifying a Unit Price in the Demand
table.

Flow Outbound Warehousing Cost

The sum of all costs involved in bringing goods from stock to dock at the source over this
lane in this period. This amount is the product of the number of flow units and the
outbound cost at the sourcing facility. If piecewise costs are used, their values are based
on whether you are using All Item Discounts or the default of Incremental Discounts.

Flow Transportation Cost

The total cost for shipping this product between source and destination sites in the
network over this lane in this period. This amount is the product of the number of flow
units, the average unit cost as specified in the Transportation Policies table, and the
number of units as determined by the Transportation Policy Cost Basis, which is Distance,
Qty, Weight, and so on. It also considers the Min Charge value if defined. If piecewise
costs are used, their values are based on whether you are using All Item Discounts or the
default of Incremental Discounts.

Flow Sourcing Cost

The total cost involved in sourcing this product from the Source Site in this period. This
amount is the number of flow units multiplied by the average unit cost, as specified in the
Sourcing Policies table. If piecewise costs are used, their values are based on whether
you are using All Item Discounts or the default of Incremental Discounts.

Flow Duty Cost

The total costs due to taxes and tariffs levied on shipments over this shipment lane in this
period. This amount is the product of the number of flow units, the duty cost, and the
product value.

In Transit Inventory Holding Cost

The cost from units considered as inventory due to their inaccessibility during
transportation. This amount is calculated by multiplying the In Transit Inventory, the
product Value, and the Inv Carrying Cost % from Model Options, and then dividing the
result by 365. For the Transportation Time used to calculate In Transit Inventory, Supply
Chain Guru uses the minimum of the transport time or the sum of all period lengths (in
Days). It does not go past the end of the model horizon.
In Transit Inventory Holding Cost =

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 161

Chapter 4 Optimization Output Tables

((In Transit Inventory * Product Value * Inventory Carrying Cost %* Period Length) /
365) * minimum of (Model Horizon in days, Service Time in days)
If the Inv Carrying Cost % is populated in Inventory Policies, Supply Chain Guru uses this
value; otherwise it uses the Inventory Carrying Cost % from Model Options.

Service Hours
The time, in hours, required for the product to leave the source and arrive at the
destination.
service hours = load time + transport time + unload time

Service Distance
The distance between the source and destination.

CO2
The carbon emissions in the units of the inputs on the lanes. This value is a product of the
CO2 and CO2 Basis for the lane as specified in Transportation Policies, multiplied by the
number of units flowing on the lane.
For example, if you have set the CO2 Basis to Weight-Distance, then the CO2 here is
expressed as:
(Product Weight * Distance * CO2) * FlowUnits

Output Flow Graphic / Output Graphic Size / Output Flow Graphic Color
Allows you to specify the type of line drawn in the Geo Map to represent the flow.

In Transit Inventory
The amount of product that is inaccessible because it is in transit between two sites.
in transit inventory = (Flow Units) * (minimum of either Transport Time from
Transportation Policies or time remaining in model horizon) / Period Length in days

CO2 Cost
The total cost incurred due to carbon emissions.

Total Cost
The total cost incurred for the customer flow.
Total Cost = Flow Outbound Warehouse Cost + Flow Transportation Cost + Flow
Sourcing Cost + Flow Duty Cost + Intransit Inventory Cost + CO2 Cost

Flow Lead Time Cost

The cost incurred on the customer flow due to lead time.
flow lead time cost = (the product’s Lead Time Cost/Day/Unit) * (Flow Units) *
(Transport Time in days from the Transportation Policies table)

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

162 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Interfacility Flows

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Interfacility Flows
This output table summarizes the specifics of all shipments between facilities in the
network.

Scenario
The scenario for which the summary data was generated.

Source Name
Site where the product originated.

Destination Name
Site to where the product is shipped.

Product Name
The name of the product being shipped.

Mode
The transportation lane that is being used in case of multiple modes.

Period Name
The period in which this flow occurs.

Flow Units
The number of units shipped over this lane in this period.

Flow Weight
The weight of all units shipped over this lane in this period.

Flow Cubic
The cubic size of all units shipped over this lane in this period.

Flow Inbound Warehousing Cost

The sum of all costs involved in bringing goods from dock to stock at the destination. This
amount is the number of flow units multiplied by the inbound cost at the sourcing facility.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 163

Chapter 4 Optimization Output Tables

If piecewise costs are used, their values are based on whether you are using All Item
Discounts or the default of Incremental Discounts.

Flow Outbound Warehousing Cost

The sum of all costs involved in bringing goods from stock to dock at the source over this
lane in this period. This amount is the number of flow units multiplied by the outbound
cost at the sourcing facility. If piecewise costs are used, their values are based on
whether you are using All Item Discounts or the default of Incremental Discounts.

Flow Transportation Cost

The total cost for shipping this product between source and destination sites in the
network over this lane in this period. This amount is the product of the number of flow
units, the average unit cost as specified in the Transportation Policies table, and the
number of units as determined by the Transportation Policy Cost Basis, such as Distance,
Qty, Weight, and so on. It also considers the Min Charge value if defined. If piecewise
costs are used, their values are based on whether you are using All Item Discounts or the
default of Incremental Discounts.

Flow Sourcing Cost

The total cost involved in sourcing this product from the Source Site in this period.
Flow Sourcing Cost = Flow Units * Avg Unit Cost specified in Sourcing Policies table
If piecewise costs are used, their values are based on whether you are using All Item
Discounts or the default of Incremental Discounts.

Flow Duty Cost

The total costs due to taxes and tariffs levied on shipments over this shipment lane in this
period. This amount is the product of the number of flow units, the duty cost, and the
product value.

In Transit Inventory Holding Cost

The total cost involved in products being in transport over this lane in this period.
Total In Transit Inv Holding Cost =
((Total Ending Inventory * Product Value * Inventory Carrying Cost %* Period
Length) / 365) * minimum of (Model Horizon in days, Transportation Policy Time in
days)
For the Transportation Time used to calculate In Transit Inventory, Supply Chain Guru
uses the minimum of the transport time or the sum of all period lengths in Days. It does
not go past the end of the model horizon.
If the Inv Carrying Cost % is populated in Inventory Policies, Supply Chain Guru uses this
value; otherwise it uses the Inventory Carrying Cost % from Model Options.

Service Hours
The time, in hours, required for the product to leave the source and arrive at the
destination. This time includes the load time, the transport time, and the unload time.

Service Distance
The distance between the source and destination.

164 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Interfacility Flows

CO2
The carbon emissions in the units of the inputs on the lanes. This value is the CO2 and
CO2 Basis for the lane as specified in Transportation Policies, multiplied by the number of
units flowing on the lane.
For example, if you have set the CO2 Basis to Weight-Distance, then the CO2 here is
expressed as:
(Product Weight * Distance * CO2) * FlowUnits

Cycle Stock
The cycle stock allocated for the specific interfacility flow.

Replenishment Frequency
The calculated days between replenishments used for inventory optimization. This is
calculated as:
(2 *(Cycle Stock * Period Length))/Flow Units
where the Flow Units are per Source, Destination, Product, Mode, Period combination.

In Transit Inventory
The amount of product that is inaccessible because it is in transit between two sites. The
outbound flow per day is the Flow Units multiplied by the minimum of either the
Transport Time (from Transportation Policies) or the time remaining in the model horizon,
the result of which is divided by the Period Length in days.

CO2 Cost
The total cost incurred due to carbon emissions. The Carbon Cost is available from the
Greenhouse Gases table.

Total Cost
The total cost incurred for the customer flow.
Total Cost = Flow Outbound Warehouse Cost + Flow Transportation Cost + Flow
Sourcing Cost + Flow Duty Cost + Intransit Inventory Cost + CO2 Cost.

Flow Lead Time Cost

The cost incurred on the interfacility flow due to lead time.
Flow Lead Time Cost = (product’s Lead Time Cost/Day/Unit) * Flow Units * (Transport
Time in Days from Transportation Policies table)

Output Flow Graphic / Output Graphic Size / Output Flow Graphic Color
Allows you to specify the type of line drawn in the Geo Map to represent the flow.

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 165

Chapter 4 Optimization Output Tables

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Facility Summary
This output table summarizes throughput and cost per facility.

Scenario
The scenario for which the summary data was generated.

Site Name
The name of the facility.

Site Type
The type of this facility, which is either potential facility or existing facility.

Initial Status
The status of this facility before making the optimization run (either include or consider).

Period Name
The name of the period these facility statistics apply to.

Optimized Status
The status of this facility after optimization.

Throughput Level
The amount of product shipped from a site in this period. If the Fixed Operating Cost is
applied to the horizon, the total throughput output is associated with the first period in
the model, and no throughput is displayed for the remaining periods.

Throughput Basis
The units of measure for throughput level.

Total Cost
The total cost incurred by the facility.
total cost = total fixed startup cost + total fixed operating cost + total closing cost +
total production cost + total sourcing cost + total transportation cost + total
warehousing cost + total duty cost + total inventory holding cost

166 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Facility Summary

Total Fixed Startup Cost

The total one time costs of beginning operations at this site in this period.

Total Fixed Operating Cost

The total cost to keep shipping products from this site during this period.

Total Closing Cost

The total cost for closing this site during this period.

Total Capital Investment

The total capital investment for the facility in the period for the specified (sub)scenario.

Depreciation
The depreciation for the facility in the period for the specified (sub)scenario.

Current Book Value

The book value for the facility in the period for the specified (sub)scenario.

Total Production Cost

The total costs from producing units at this site during this period. This total cost includes
the costs where one or more Make process(es) exist for a product at the facility, such as
the Flow Production Cost and Flow Setup Cost from the Production Process Flows table,
and the costs for Make Sourcing Policies, such as the Interfacility Flows Flow Sourcing
Cost. If piecewise costs are used for Avg Unit Cost in the Sourcing Policies table, their
values are based on whether you are using All Item Discounts or the default of
Incremental Discounts.

Total Sourcing Cost

The total sourcing costs of this site during this period.
total sourcing cost = (flow quantity from Interfacility Flows table) * (average unit cost
in Sourcing Policy)
where the Sourcing Policy average unit cost is for this facility to obtain product from the
source site.

Total Inbound Transportation Cost

The total cost of bringing goods to this site during this period.
total inbound transportation cost = (flow quantity from Interfacility Flows table) *
(average unit cost in Transportation Policies table)

Total Outbound Transportation Cost

The total cost of shipping goods from this site during this period.
total outbound transportation cost = (flow quantity from Interfacility Flows table +
flow quantity from Customer Flows table) * (average unit cost in Transportation
Policies table)

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 167

Chapter 4 Optimization Output Tables

Total Warehousing Cost

The total inbound and outbound warehousing cost for this site during this period.

Total Inbound Warehousing Cost

The total costs involved in bringing goods from dock to stock for this site during this
period.
total inbound warehousing cost = (number of facility’s inbound units from Interfacility
Flows table) * (facility inbound cost)

Total Outbound Warehousing Cost

The total costs involved in bringing goods from stock to dock for this site during this
period.
total outbound warehousing cost = (number of facility’s outbound units from
Interfacility Flows table) * (facility oubound cost)

Total Duty Cost

The total costs due to taxes and tariffs levied on shipments from this site during this
period.
total duty cost = (number of shipped units from the Interfacility Flows table + number
of shipped units from Customer Flows table) * duty costs * product value

Total Inventory Holding Cost

The total costs due to holding inventory during the optimization run at this site during
this period. This is the product of the number of units shipped out of the facility, the
product value, the run time, and the Inv Carrying Cost %, the result of which is divided
by 365.
Total Inventory Holding Cost = Facility Inv Holding Cost + Interfacility Flows In Transit
Inventory Holding Cost

Total CO2 Cost

The total cost incurred from carbon emissions.

Total CO2
The carbon emissions if transportation is involved in the production process. This value is
the product of the lane distances, flow weights, and CO2 settings as defined in the
Transportation Policies table.

Safety Stock Cost

The costs from the Inventory Policy Summary output table. The Safety Stock Cost is
included in the Total Cost value. If a Safety Stock Optimization has not been run on this
model, the value is blank.

Note: This field is currently not implemented.

Throughput Quantity
The throughput at the facility by quantity.

168 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Facility Summary

Throughput Weight
The throughput at the facility by weight.

Throughput Cubic
The throughput at the facility by cubic volume.

Step Capacity
The site's fixed operating capacity step used to accommodate the throughput.

Step Remaining Capacity

The remaining capacity based on the Step Capacity minus the Throughput.

Step Capacity Utilization

The portion of the step capacity used to accommodate the throughput.
For a one-step constraint, assume a Fixed Operating capacity constraint on a site has
been defined as:
<0,175000><250000,INF>
If the throughput is 150,000:
 Step Remaining Capacity is 250,000 – 150,000 = 100,000
 Step Capacity Utilization is 150,000 / 250,000 = 0.60
For a two-step constraint, assume a Fixed Operating capacity constraint has been defined
on a site as:
<0,175000><250000,200000><400000,INF>
This defines two steps:
 0 to 250,000
 250,000 to 400,000, where INF cost results in a hard constraint of 400,000)
If the throughput is 300,000, the capacity is calculated as follows:
 The step size of the second step = 400,000 – 250,000 = 150,000
 The amount of the second step used = 300,000 – 250,000 = 50,000
 The Step Capacity Utilization = 50,000 / 150,000 = 0.33

Total Capacity
The site's total fixed operating capacity, which is the final capacity specified.

Total Remaining Capacity

The remaining capacity.
Total Remaining Capacity = Total Capacity - Throughput

Total Capacity Utilization

The portion of the total capacity used to accommodate the throughput.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 169

Chapter 4 Optimization Output Tables

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Customer Summary
This output table summarizes revenue and flow per customer.

Scenario
The scenario for which the summary data was generated.

Customer Name
The name of the customer site.

Initial Status
The status of this customer site before optimization.

Period Name
The name of the period to which these customer statistics apply.

Optimized Status
The status of this site after making the optimization run for this period. The status is one
of: Served, Unserved, or Partially Served.

Total Revenue
The total revenue generated by units shipped to this customer in this period.

Total Flow Units

The total units shipped to this customer in this period.

Total Flow Weight

The total weight of units shipped to this customer in this period.

Total Flow Cubic

The total cubic of units shipped to this customer in this period.

170 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Productions

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Total Demand
The total demand for all products for this customer.

Unserved Demand
Displays any demand that was not served in the model. If this value is less than the Total
Demand, the Optimization Status is Partially Served.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Productions
This output table summarizes all productions per site-product combination that occur in
the network during the optimization.

Scenario
The scenario for which the summary data was generated.

Site Name
The name of the facility at which production occurs.

Product Name
The name of the product being produced.

Period Name
The name of the period in which this productions occurs.

Gross Production Quantity

The number of end product units produced by this site in this period before applying
Yield. This quantity does not include the Byproduct Production Quantity.

Net Production Quantity

The total number of end product units produced at this site in a period after applying
Yield. This quantity does not include the Byproduct Production Quantity.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 171

Chapter 4 Optimization Output Tables

Byproduct Production Quantity

The total number of byproduct units produced at a site in a period.

Total Production Quantity

The combined total of product and byproduct that is produced.
Total Production Quantity = Net Production Quantity + Byproduct Production Quantity

Production Weight
The weight of the units produced by this site in this period for a product.

Production Cubic
The cubic of the all units produced by this site in this period for a product.

Production Cost
The total cost for producing product at this site in this period. If one or more Make
process(es) exist for a product at the facility, this amount is the sum of the Flow
Production Cost and the Flow Setup Cost. For Make Sourcing Policies, it is the sum of the
flow setup cost and the work center total cost. Keep in mind that if piecewise costs are
used for Avg Unit Cost in the Sourcing Policies table, their values are based on whether
you are using All Item Discounts or the default of Incremental Discounts.

CO2
The carbon emissions in unit mass if transportation is involved in the production process.
CO2 = lane distance * flow weight * CO2 setting in Transportation Policies

CO2 Cost
The total cost incurred due to carbon emissions.

Total Cost
The total cost incurred for the customer flow.
Total Cost = Production Cost + CO2 Cost

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

172 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory

Inventory
This output table summarizes end inventory and associated costs per facility.

Scenario
The scenario for which the summary data was generated.

Site Name
The name of the site that holds inventory.

Product Name
The name of the product stocked at this site.

Period Name
The name of the period to which these inventory statistics apply.

Pre Build Inventory

The amount of inventory held ahead of the demand period to ensure against known
demand seasonality. Production capacity constraints in a period can place limits on
production that prevent demand from being met in peak periods. If production capacity in
earlier model periods is available, and minimum and maximum inventory constraints
permit it, pre-build inventory can be accumulated to meet the demand in a peak period.

Period No
The sequence number for the period. This value is useful when sorting periods
sequentially rather than by name.

Transportation Safety Stock

Displays any safety stock held in transportation. Safety stock can be held as a result of
transportation lead time variability. This amount is separate from the safety stock
quantity at the destination.

Transportation Safety Stock Cost

The cost of any Transportation Safety Stock based on the Inventory Carrying Cost in
Model Options.

Safety Inventory
The buffer stock accumulated to avoid stock outs. Network Optimization determines this
value based on the Safety Stock and Safety Stock Basis fields in Inventory Policies.
 When the basis is Quantity, the Safety Inventory for a given product at a facility is
equal to the Safety Stock defined in the Inventory Policies table.
 When the basis is DOS (Days of Supply), the Safety Stock field represents the days of
supply.
Safety Inventory = (days of supply) * (outflow per day of the product)
The outflow per day is also impacted by the model horizon.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 173

Chapter 4 Optimization Output Tables

Cycle Stock
The stock allocated to meet immediate forecasted demand.

Turn Estimated Inventory

The number of units of inventory expected per inventory turn.
turn estimated inventory = (number of flow units) / (number of turns)

Total Inventory
The total units of product held during the optimization run.

Total Inv Holding Cost

The cost for inventory of the product at the end of the period at this site. This field is only
listed for multi-time period models.
The Total Inv Holding Cost is calculated as:
= Total Ending Inv Holding Cost + Total Intransit Inventory Holding Cost
= [(Total Inventory - Total Intransit Inventory)* Product Value * Inv Carrying Cost %
* Period Length) / 365] + [In-transit inventory * unit cost at source site * carrying
cost % at source site * period length / 365]
If the Inv Carrying Cost % is populated in Inventory Policies, Supply Chain Guru uses this
value; otherwise it uses the Inventory Carrying Cost % from Model Options.

Total Ending Inventory

The total number of units remaining at the end of the model run time.

Total Ending Inv Holding Cost

The total costs due to holding inventory during the optimization run at this site.
The Total Ending Inv Holding Cost is calculated as:
Total Ending Inv Holding Cost = (Total Ending Inventory * Product Value * Inv
Carrying Cost % * Period Length) / 365
If the Inv Carrying Cost % is populated in Inventory Policies, Supply Chain Guru uses this
value; otherwise it uses the Inventory Carrying Cost % from Model Options.

In Transit Inventory
The amount of product that is inaccessible because it is in transit between two sites. This
is the sum of the flow in transit inventory and the production inventory.
 The flow in transit inventory is the Flow Units multiplied by the minimum of either the
Transport Time (from Transportation Policies) or the time remaining in the model
horizon, divided by the Period Length in days.
 The production component is the Production Flow Units multiplied by the minimum of
either the production lead time (Sourcing Policies Production Time) or the time
remaining in the model horizon, divided by 2 x Period Length in days.

Scenario ID
The identifier of the scenario for which the summary data was generated.

174 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Aggregated Customer Demand

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Aggregated Customer Demand

This table shows aggregated demand for customer-product pairs from the Demand table.
If the customer-product pair has demand profile override in User-Defined Customer
Demand Profile in a specific period, demand during that period will not be written to the
Aggregated Customer Demand table.

Scenario
The scenario for which the output data was generated.

Customer Name
The name of the customer site at which the demand occurs.

Product Name
The name of the product demanded at the customer site.

Date
The date on which the demand occurs or the date into which the demand is aggregated.
The aggregation period determines this date.
 Daily Demand – Date that demand occurs.
 Weekly Demand – Date for the Monday of the week in which the demand occurs .
 Monthly Demand – The first day of the month in which the demand occurs.

Aggregated Demand
The non-zero aggregated demand for the specified aggregation period.

Outlier
Identifies whether the aggregated demand is an outlier or not. This field displays “True” if
the aggregated demand is an outlier.

Adjusted Demand
The value that replaces the Outlier if the Replace with Non-Zero Demand Mean option is
selected for outlier handling.

Potential Revenue
The possible revenue based on Aggregated Demand * (Demand) Unit Price.

Scenario ID
The identifier of the scenario for which the summary data was generated.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 175

Chapter 4 Optimization Output Tables

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Aggregated Customer Facing Facility Demand

This table is populated when the Propagation Method is “Demand Quantity” only.
Aggregated Customer Facing Facility Demand shows aggregated demand at customer-
facing sites derived from the propagation of aggregated customer demand.

Scenario
The scenario for which the output data was generated.

Site Name
The name of the customer site at which the demand occurs.

Product Name
The name of the product demanded at the customer site.

Date
The date on which the demand occurs or the date into which the demand is aggregated.
The aggregation period determines this date.
 Daily Demand– Date that demand occurs.
 Weekly Demand – Date for the Monday of the week in which the demand occurs.
 Monthly Demand – The first day of the month in which the demand occurs.

Aggregated Demand
The non-zero aggregated demand for the specified aggregation period.

Outlier
Identifies whether the aggregated demand is an outlier or not.

Adjusted Demand
The value that replaces the Outlier if the Replace with Non-Zero Demand Mean option is
selected for outlier handling.

Potential Revenue
The possible revenue based on Aggregated Demand * (Demand) Unit Price.

Scenario ID
The identifier of the scenario for which the summary data was generated.

176 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Customer Demand Profile

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Customer Demand Profile

The Customer Demand Profile contains statistics and demand classes for demand
reported by scenario-site-product-period.

Scenario
The scenario for which the output data was generated.

Customer Name
The name of the customer site at which the demand occurs.

Product Name
The name of the product demanded at the customer site.

Period Name
The period in which the demand occurs.

Intermittency
Determines how frequently demand happens using the average time between adjacent
demand. One of:
 Non-Intermittent – when the average time between demand is less than the
Intermittency Threshold
 Intermittent – when the average time between demand is at or greater than the
Intermittency Threshold

Variability
Shows how much demand is varying based on Non-Zero Demand Variability. One of:
 Low-Variable – demand is reasonably constant or fluctuating within a small range
 Highly-Variable – demand is significantly different from one demand point to another
This field only applies to Intermittent demand and is blank for Non-Intermittent demand.

Demand Class
Defines demand as one of four main categories. Intermittency and demand variability in
relation to its mean are used to differentiate demand class:
 Smooth – Non-Intermittent demand with low variability compared to its mean.
 Erratic – Non-Intermittent demand with higher variability compared to its mean.
 Slow – Intermittent demand with low variability compared to its mean.
 Lumpy – Intermittent demand with higher variability compared to its mean.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 177

Chapter 4 Optimization Output Tables

Clumpiness
Further defines Low-Variable Slow demand. Clumpiness indicates how close demand
points are to each other. Clumped demand has reasonably constant demand with
variability close to zero. Unit-Sized demand has no variability and demand size is always
1.

Demand Class Details

Demand Class Details indicates the demand class based on Intermittency, Variability,
Demand Class and Clumpiness. This is the class that Safety Stock Optimization uses to
determine Lead-Time Demand Distribution.

Total Demand Qty

Total demand quantity calculated from demand mean and period length. Demand in
incomplete aggregation periods is not included.

Non-zero Demand Mean

Average demand size during the period at the given site. This does not include
aggregation periods with zero demand.

Non-zero Demand Std Dev

Standard deviation of demand size during the period at the given site. This does not
include aggregation periods with zero demand.

Demand Mean
Average demand per aggregation period during the period at the given site.

Demand Std Dev

Standard deviation of the aggregated demand during the period at the given site.

Inter-Demand Interval Mean

Average number of aggregation periods between two adjacent aggregated demand
records in a time series. The beginning and end of the model horizon are included in the
calculation of this mean even if there is no demand at these times.

Non-zero Demand CV2

The squared coefficient for the variation in demand size. This is the demand variability in
relation to its mean. Non-Zero Demand CV2 is derived as:
(Non-Zero Demand Std Dev/Non-Zero Demand Mean)2

Min Non-zero Demand

The minimum aggregated demand for the site-product during the period. This does not
take into account zero demand.

Max Non-zero Demand

The maximum aggregated demand for the site-product during the period.

178 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Facility Demand Profile

Aggregation Period Count

The number of complete aggregation periods (buckets). A complete weekly bucket is
from Monday-Sunday. A complete monthly bucket is from the first to the last day of a
particular calendar month.

Demand Count
The number of aggregation periods with non-zero demand.

Outliers Count
The number of aggregated demand records detected as outliers in the period for the site-
product.

Potential Revenue
The possible revenue based on the Total Demand * Unit Price.

Total Cost
The total product cost based on the Total Demand * Unit Cost.

Total Weight
The total product weight based on the Total Demand * Unit Weight.

Total Cubic
The total product cube based on the Total Demand * Unit Cubic.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Facility Demand Profile

The Facility Demand Profile table contains statistics and the demand class at all facilities
including upstream sites. The profile of customer-facing sites includes both customer
demand and the portion of demand from other facilities. This information is reported by
scenario-site-product-period.

Scenario
The scenario for which the output data was generated.

Site Name
The name of the site at which the demand occurs.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 179

Chapter 4 Optimization Output Tables

Product Name
The name of the product demanded at the site.

Period Name
The period in which the demand occurs.

Intermittency
Determines how frequently demand happens using the average time between adjacent
demand. One of:
 Non-Intermittent – when the average time between demand is less than the
Intermittency Threshold
 Intermittent – when the average time between demand is at or greater than the
Intermittency Threshold

Variability
Shows how much demand is varying based on Non-Zero Demand Variability. One of:
 Low-Variable – demand is reasonably constant or fluctuating within a small range
 Highly-Variable – demand is significantly different from one demand point to another
This field only applies to Intermittent demand and is blank for Non-Intermittent demand.

Demand Class
Defines demand as one of four main categories. Intermittency and demand variability in
relation to its mean are used to differentiate demand class:
 Smooth – Non-Intermittent demand with low variability compared to its mean.
 Erratic – Non-Intermittent demand with higher variability compared to its mean.
 Slow – Intermittent demand with low variability compared to its mean.
 Lumpy – Intermittent demand with higher variability compared to its mean.

Clumpiness
Further defines Low-Variable Slow demand. Clumpiness indicates how close demand
points are to each other. Clumped demand has reasonably constant demand with
variability close to zero. Unit-Sized demand has no variability and demand size is always
1.

Demand Class Details

Demand Class Details indicates the demand class based on Intermittency, Variability,
Demand Class and Clumpiness. This is the class that Safety Stock Optimization uses to
determine Lead-Time Demand Distribution.

Total Demand Qty

Total demand quantity calculated from demand mean and period length. Demand in
incomplete aggregation periods is not included.

180 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Facility Demand Profile

Non-zero Demand Mean

Average demand size during the period at the given site. This does not include
aggregation periods with zero demand.

Non-zero Demand Std Dev

Standard deviation of demand size during the period at the given site. This does not
include aggregation periods with zero demand.

Demand Mean
Average demand per aggregation period during the period at the given site.

Demand Std Dev

Standard deviation of the aggregated demand during the period at the given site.

Inter-Demand Interval Mean

Average number of aggregation periods between two adjacent aggregated demand
records in a time series.

Non-zero Demand CV2

The squared coefficient for the variation in demand size. This is the demand variability in
relation to its mean. Non-Zero Demand CV2 is derived as:
(Non-Zero Demand Std Dev/Non-Zero Demand Mean)2

Aggregation Period Count

The number of complete aggregation periods (buckets). A complete weekly bucket is
from Monday-Sunday. A complete monthly bucket is from the first to the last day of a
particular calendar month.

Potential Revenue
The possible revenue based on the Total Demand * Unit Price.

Total Cost
The total product cost based on the Total Demand * Unit Cost.

Total Weight
The total product weight based on the Total Demand * Unit Weight.

Total Cubic
The total product cube based on the Total Demand * Unit Cubic.

Scenario ID
The identifier of the scenario for which the summary data was generated.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 181

Chapter 4 Optimization Output Tables

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Inventory Policy Summary

The Inventory Policy Summary table outputs the results of Safety Stock Optimization by
site-product.

Scenario
The scenario for which the output data was generated.

Site Name
The name of the site at which the demand occurs.

Product Name
The name of the product demanded at the site.

Period Name
The period to which the safety stock and inventory policy applies.

Target Service Level

The Service Requirement value specified in the Inventory Policies table. Safety Stock
Optimization will optimize the safety stock to satisfy the given target service level. This
field will be left blank when Safety Stock is zero for the site-product. The default Target
Service Level for the customer-facing site is set to 0.95. For additional information, refer
to Service Level Propagation.

Note: If the Target Service Level displays as 1, right-click and select Column Formatting
to adjust the number of Decimal Places.

Service Type
The Service Definition used for the output calculation for the product at the site during
the period. This is usually the same as the Service Definition value in Optimization
Options > Safety Stock Options.

Type 1: The probability of no stock-out during  Event-oriented

Probability based the risk period.  Concerned with whether a
shortage occurs during the risk
period.

182 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policy Summary

Type 2: The percentage of demand fulfilled from  Quantity-based

Quantity based stock on time (Quantity Fill Rate).  Interested in the percentage of
demand satisfied on time.

Type 3: The fraction of time with positive stock  Time based

Time based on hand.  Interested in both the shortage
event and its duration.

CAUTION: Type 2 and Type 3 Service Types need batch size information in order to
calculate. You must provide either the Min Order Qty (Sourcing Policies) or
the Days between Replenishment (Transportation Policies).
Batch-size Q = max (Min Order Qty, DBR * Daily Demand Mean).
If batch size information is not provided, Supply Chain Guru will use the Type
1 service type calculation automatically due to the lack of required
information.

Safety Stock
The optimized amount of safety stock that should be held to account for unknown
variations in demand or lead time.

Excess Safety Stock

This field displays the difference between the Minimum Safety Stock as defined in the
Inventory Policies table and the calculated optimal safety stock. Safety Stock is the
optimized amount of safety stock you must carry to satisfy the target service level.
However, you may want to carry more than the optimized safety stock. In this case, you
can input a Minimum Safety Stock that is greater than the optimal safety stock. When the
Minimum Safety Stock > optimal safety stock, the difference is reported as Excess Safety
Stock.

Total Safety Stock

This field displays the sum of the Safety Stock and Excess Safety Stock.

Safety Stock DOS

The equivalent number of days of supply (DOS) to be held in inventory as safety stock to
account for unknown variations in demand or lead time. Safety Stock DOS is derived as:
Safety Stock/Daily Demand Mean
Daily Demand Mean is calculated as:
(aggregated) Demand Mean/Average number of days in aggregation period)
This value is in DAYS.

Safety Stock Cost

The cost of holding the safety stock.
Safety Stock Cost = Safety Stock * Product Value * Inventory holding cost % * Period
Length/365 days.
The Period Length is affected by the Work Week setting in Safety Stock Options. For
example, if your Period is one year and the Work Week is 7 Days, the Period Length is

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 183

Chapter 4 Optimization Output Tables

365. If the Work Week is 5 Days, the length is 261. You can see the period length in the
Aggregation Period field of the Customer Demand Profile Optimization Output table.

Safety Stock Value

The total product value of the safety stock.
Safety Stock Value = Safety Stock * Product Value

Coverage
The optimized net period of risk (in days) that a site's safety stock will cover. Also known
as the "net replenishment lead time". Coverage is equal to this site's immediate lead
time, plus the service time quoted by its nearest source, minus the service time this site
quotes to its customer or nearest downstream sites. When the site has multiple sources
or destinations, coverage is calculated from the combination of coverage for each source-
site-destination. For more information, refer to Coverage.

Daily Demand Mean

Daily Demand Mean is calculated as:
(aggregated) Demand Mean/Average number of days in aggregation period.

Daily Demand Std Dev

Daily Demand Std Dev is calculated as:
(aggregated) Demand Standard Deviation/Average number of days in aggregation
period.

Demand Class Details

Demand Class Details summarizes the demand class from four different aspects. This is
the class that Safety Stock Optimization uses to determine Lead-Time Demand
Distribution and which inventory policy is recommended.

Recommended Policy
The inventory control policy that is appropriate for demand at the site for the product in
order to maintain the service requirement. See detailed descriptions in Determining the
Inventory Policy.

Policy Parameter 1
The first parameter as determined based on the Recommended Policy. For example, if the
Recommended Policy is (R,Q), Policy Parameter 1 will be the value for the Reorder Point
(R). If the Recommended Policy is (s,S), POlicy Parameter 1 will be the value for the
Report Point (s).
For additional information, refer to Policy Parameters.

Policy Parameter 2
The first parameter as determined based on the Recommended Policy. For example, if the
Recommended Policy is (R,Q), Policy Parameter 2 will be the value for Reorder Qty (Q). if
the Recommended Policy is (R,Q), Policy Parameter 2 will be the value for Reorder Up To
Qty (S).
For additional information, refer to Policy Parameters.

184 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policy Summary

Expected Type 1 Service

The expected Type 1 service level met by the recommended safety stock and inventory
policy. When Service Type = Type 1, the value will be the same as the Target Service
Level for “Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 1 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

Expected Type 2 Service

The expected Type 2 service level met by the recommended safety stock and inventory
policy. When Minimum Order Qty (Q) or Days Between Replenishments or both are not
provided, this field is calculated based on Q = 1. You must provide Minimum Order
Qty (Sourcing Policies) or Days Between Replenishments (Transportation
Policies) if Type 2 is used as a target service level to calculate safety stock. When
Service Type = Type 2, the value will be the same as the Target Service Level for
“Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 2 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

Expected Type 3 Service

The expected Type 3 service level met by the recommended safety stock and inventory
policy. When Minimum Order Qty (Q) or Days Between Replenishments or both are not
provided, this field is calculated based on Q = 1. You must provide Minimum Order
Qty (Sourcing Policies) or Days Between Replenishments (Transportation
Policies) if Type 2 is used as a target service level to calculate safety stock. When
Service Type = Type 2, the value will be the same as the Target Service Level for
“Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 3 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

Lead-Time Demand Dist

The distribution used to represent the demand during risk period (coverage). This is
determined by Demand Class Details and lead time demand parameters. For more
information, refer to Lead Time Outputs.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 185

Chapter 4 Optimization Output Tables

Lead-Time Demand Mean

The average demand during lead-time. This is derived by:
Demand Mean * Coverage
For more information, refer to Lead Time Outputs.

Lead-Time Demand Std Dev

The standard deviation of demand during risk period (coverage). This is defined by:

For more information, refer to Lead Time Outputs.

Avg Backorders
The long-run time weighted average of backorders (shortage). For more information,
refer to Average Backorders.

Avg Inventory
The long-run time-weighted average on-hand inventory levels. For more information,
refer to Average Inventory.

Avg Replenishment Qty

The average size of replenishment orders. This is greater than or equal to Min
Replenishment Qty.
For example, assume the order quantity Q = 4. Depending on the demand, the
replenishment orders will vary. Assume that on day 1, the total replenishment order is 1
* Q = 4 (ordering in multiples of Q). On day 2, the replenishment order is 4 * Q = 16. On
day 3, the replenishment order is 3 * Q = 12. In this case, the Avg Replenishment Qty is
(4+16+12)/3 = 11.

Sourcing Type
Identifies if the site is sourcing the product from a single site or multiple source(s)/
mode(s) during the period. If the site has multiple sources for the product, the
recommended inventory policy for each source is found the in Inventory Policy Details
table.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

186 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policy Details

Inventory Policy Details

The Inventory Policy Details table outputs the results of Safety Stock Optimization by
site-product-source-destination-BOM. When the site-product pair is connected to multiple
sources, modes, or destinations, there will be multiple records for the site-product pair in
this table.

Scenario
The scenario for which the output data was generated.

Source Name
The name of the source from which the site receives products.

Destination Name
The name of the site served by the source site.

Product Name
The name of the product demanded at the customer.

Period Name
The period to which the safety stock and inventory policy applies.

BOM Name
The name of the bill of material (BOM) using the product at the site.

Mode
The transportation mode by which the site receives products from the source.

Min Replenishment Qty

Minimum size of replenishment order based on replenishment frequency or the minimum
order quantity. Min Replenishment Qty is derived as:
Max(Min Order or Shipment Qty, Days Between Replenishment or Days Between
Production × daily demand mean)
Min Replenishment Qty is used in demand propagation, and the safety stock calculation
for service Type 2 and Type 3. For Type 2 and Type 3, cycle time demand information is
required to calculate the safety stock. The Min Replenishment Qty is used to approximate
the cycle time demand.

Service Time
The amount of time the site quotes to its customer or downstream sites for getting their
orders ready to ship. Service times are the decision variables of the optimization model.
The service time customer-facing facilities quote to customers is zero by default, which
means whenever a customer places an order, the customer-facing facilities have enough
stock ready to ship immediately.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 187

Chapter 4 Optimization Output Tables

Immediate Lead Time

The lead time required for the product to get replenished at the destination site from the
nearest upstream source node or production site. Immediate Lead Time is the shortest
time that product can be replenished assuming the nearest upstream site has on-hand
stock.
For lanes, Immediate Lead Time = Source Lead Time + Transport Time + Inventory
Review Period
For Make policies, Immediate Lead Time = Source Lead Time + Production Time +
Inventory Review Period

Max Lead Time

The duration of the longest chain from the site to the furthest upstream node. For end
products with bill of materials, Max Lead Time includes the lead time for components. For
additional information, refer to Max Lead Time.

Recommended Policy
The inventory control policy that is appropriate for demand at the site for the product in
order to maintain the service requirement. See detailed descriptions in Determining the
Inventory Policy.

Policy Parameter 1
The first parameter as determined based on the Recommended Policy. For example, if the
Recommended Policy is (R,Q), Policy Parameter 1 will be the value for the Reorder Point
(R). If the Recommended Policy is (s,S), Policy Parameter 1 will be the value for the
Report Point (s).
For additional information, refer to Policy Parameters.

Policy Parameter 2
The second parameter as determined based on the Recommended Policy. For example, if
the Recommended Policy is (R,Q), Policy Parameter 2 will be the value for Reorder Qty
(Q). if the Recommended Policy is (s,S), Policy Parameter 2 will be the value for Reorder
Up To Qty (S).
For additional information, refer to Policy Parameters.

Expected Type 1 Service

The expected Type 1 service level met by the recommended safety stock and inventory
policy. When Service Type = Type 1, the value will be the same as the Target Service
Level for “Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 1 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

188 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Inventory Policy Details

Expected Type 2 Service

The expected Type 2 service level met by the recommended safety stock and inventory
policy. When Minimum Order Qty (Q) or Days Between Replenishments or both are not
provided, this field is calculated based on Q = 1. You must provide Minimum Order
Qty (Sourcing Policies) or Days Between Replenishments (Transportation
Policies) if Type 2 is used as a target service level to calculate safety stock. When
Service Type = Type 2, the value will be the same as the Target Service Level for
“Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 2 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

Expected Type 3 Service

The expected Type 3 service level met by the recommended safety stock and inventory
policy. When Minimum Order Qty (Q) or Days Between Replenishments or both are not
provided, this field is calculated based on Q = 1. You must provide Minimum Order
Qty (Sourcing Policies) or Days Between Replenishments (Transportation
Policies) if Type 2 is used as a target service level to calculate safety stock. When
Service Type = Type 2, the value will be the same as the Target Service Level for
“Continuous” products, and greater than or equal to the Target Service Level for
“Discrete” products. For example, 9.5 liters of water will satisfy exactly 0.95 service
requirements. However, if water is packed 1 liter per bottle, then it must be rounded up
to 10 bottles to satisfy 0.95 service requirements. Since 10 Liters > 9.5 Liters, the
expected service level will be higher than 0.95.

Note: If the Expected Type 3 Service displays as 1, right-click and select Column
Formatting to adjust the number of Decimal Places.

Coverage
The optimized net period of risk (in days) that the destination site's safety stock will
cover. Also known as the "net replenishment lead time". Coverage is equal to this site's
immediate lead time, plus the service time quoted by its nearest source, minus the
service time this site quotes to its customer or nearest downstream sites. When the site
has multiple sources or destinations, coverage is calculated from the combination of
coverage for each source-site-destination. For more information, refer to Coverage.

Safety Stock
The amount of safety stock that should be held at the destination site to account for
unknown variations in demand or lead-time. This portion of safety stock at the site is
associated with demand and lead-time for the specific source, destination, mode, or BOM.
Please note that the straight sum of all safety stock at the site from the Inventory Policy
Details table may not be equal to the safety stock reported in the Inventory Policy
Summary table due to pooling effects.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 189

Chapter 4 Optimization Output Tables

Excess Safety Stock

This field displays the difference between the Minimum Safety Stock as defined in the
Inventory Policies table and the calculated optimal safety stock. Safety Stock is the
optimized amount of safety stock you must carry to satisfy the target service level.
However, you may want to carry more than the optimized safety stock. In this case, you
can input a Minimum Safety Stock that is greater than the optimal safety stock. When the
Minimum Safety Stock > optimal safety stock, the difference is reported as Excess Safety
Stock.

Total Safety Stock

This field displays the sum of the Safety Stock and Excess Safety Stock.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Aggregated Demand
This output table summarizes demand details per site and product.

Scenario
The scenario for which the summary data was generated.

Site Name
The name of the customer site.

Period No
The number of the period in which this demand occurs.

Product Name
The name of the product being demanded.

Period Name
The name of the period to which these demand statistics apply.

Mode
The specific mode used by the demand.

Total Qty
The total demand at this customer site for this product during this period.

190 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Product Summary

Total Revenue
The total revenue generated due to the demand of this customer for this product during
this period.
total revenue = product demand * unit price

Demand Lead Time

The time interval between when demand occurs and when it is being fulfilled.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Product Summary
Scenario
The scenario for which the summary data was generated.

Product Name
The name of the product.

Period Name
The name of the period.

Total Profit
The total profit generated from the product.
total profit = total revenue - total cost

Total Cost
The total cost of the product.

Total Revenue
The total revenue generated from the product.

Production Cost
The total cost to make the product.

Transportation Cost
The total cost to ship the product between facilities and to a customer.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 191

Chapter 4 Optimization Output Tables

Warehousing Cost
The total inbound and outbound warehousing cost for the product.

Duty Cost
The amount of duty applied to the product.

Sourcing Cost
The total amount of sourcing costs incurred by the product.

Facility Inv Holding Cost

The total cost to hold the product in a facility's inventory.

In Transit Inv Holding Cost

The cost incurred from the amount of Inventory in transit in the model.

Product Max Lead Time x Flow

The maximum limit of the flow multiplied by the lead time.

Product Lead Time x Flow

The actual flow multiplied by the lead time.

Product Remaining Lead Time x Flow

Product Remaining Lead Time x Flow = (Max Lead Time * Flow) - (Lead Time x Flow)

Safety Stock Cost

The costs from the Inventory Policy Summary output table. The Safety Stock Cost is
included in the Total Cost value. If a Safety Stock Optimization has not been run on this
model, the value is blank.

Note: This field is not currently implemented.

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

192 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Production Process Flows

Production Process Flows

This output table summarizes the specifics of all shipments between facilities in the
network.

Scenario
The scenario for which the summary data was generated.

Site Name
The Site at which the production process occurred.

Product Name
The name of the product being shipped.

Process Name
The name of the entire process.

Work Center Name

The name of the work center, if applicable, used by the process.

Process Step Name

The name of this process step.

Next Process Step Name

The process step that occurs after this step.

Period Name
The period in which this flow occurs.

Flow Units
The number of units handled in this process.

Flow Weight
The weight of all units handled in this process.

Flow Cubic
The cubic size of all units handled in this process.

Flow Production Cost

The total cost for running the process setup.
flow production cost = (total number of flow units) * (cost per unit in Processes table)

Flow Setup Cost

The total cost involved in setting up this process.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 193

Chapter 4 Optimization Output Tables

flow setup cost = (total number of flow units * setup cost from Processes table) / lot
size

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Work Center Summary

This output table summarizes throughput and cost per work center.

Scenario
The scenario for which the summary data was generated.

Work Center Name

The name of the Work Center.

Work Center Type

The type of work center, which is either potential facility or existing work center.

Site Name
The site where the work center is located.

Initial Status
The status of this work center before optimization.

Period Name
The name of the period to which these work center statistics apply.

Optimized Status
The status of this work center after optimization.

Throughput Level
The amount of product processed by this work center during this period. If the Fixed
Operating Cost is applied to the horizon, the total throughput output is associated with
the first period in the model, and no throughput is displayed for the remaining periods.

194 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Center Summary

Note: If the Throughput Basis is Time, this value is displayed in HOURS.

Throughput Basis
The units of measure for throughput level, which is determined by the Capacity Basis in
the Work Centers table.

Total Cost
The total cost incurred by the work center.
total cost = total fixed startup cost + total fixed operating cost + total closing cost +
total production cost

Total Fixed Startup Cost

The total one-time costs of beginning operations by this work center in this period.

Total Fixed Operating Cost

The total cost to keep producing products by this work center during this period.

Total Closing Cost

The total cost of closing this work center during this period.

Total Capital Investment

The total capital investment for the facility in the period for the specified (sub)scenario.

Depreciation
The depreciation for the facility in the period for the specified (sub)scenario.

Current Book Value

The book value for the facility in the period for the specified (sub)scenario.

Total Production Cost

The total production costs of this work center during this period. This amount is also
displayed in the Production Process Flows table.

Throughput Quantity
The throughput at the work center by quantity.

Throughput Weight
The throughput at the work center by weight.

Throughput Cubic
The throughput at the work center by cubic volume.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 195

Chapter 4 Optimization Output Tables

Throughput Time
The throughput at the work center based on time.

Step Capacity
The work center's fixed operating capacity step used to accommodate the throughput.

Step Remaining Capacity

The remaining capacity.
Step Remaining Capacity = Step Capacity - Throughput

Step Capacity Utilization

The portion of the step capacity used to accommodate the throughput.
For a one-step constraint, assume a Fixed Operating capacity constraint on a work center
is defined as:
<0,175000><250000,INF>
If the throughput is 150,000:
 Step Remaining Capacity is 250,000 – 150,000 = 100,000
 Step Capacity Utilization is 150,000 / 250,000 = 0.60
For a two-step constraint, assume a Fixed Operating capacity constraint on a work center
is defined as:
<0,175000><250000,200000><400000,INF>
This defines two steps:
 0 to 250,000
 250,000 to 400,000, where INF cost results in a hard constraint of 400,000)
If the throughput is 300,000, the capacity is calculated as follows:
 The step size of the second step = 400,000 – 250,000 = 150,000
 The amount of the second step used = 300,000 – 250,000 = 50,000
 The Step Capacity Utilization = 50,000 / 150,000 = 0.33

Total Capacity
The work center's total fixed operating capacity, which is the final capacity specified.

Total Remaining Capacity

The remaining capacity.
Total Remaining Capacity = Total Capacity - Throughput

Total Capacity Utilization

The portion of the total capacity used to accommodate the throughput.

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

196 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Resource Summary

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Work Resource Summary

The work resource summary table summarizes utilization and cost of work resources, and
also suggests an optimal number of work resources.

Scenario
The scenario for which the summary data was generated.

Name
The name of the work resource.

Max Units
The upper bound, or maximum number, of work resources available in the network.

Site Name
The site where the work resource is based.

Period Name
The name of the period to which these work resource statistics apply.

Optimized Units
The number of work resources required by the optimized model.

Utilization
The proportion of time this work resource is being used, when compared to the total time
the resource is available during this period.

Fixed Cost
The total fixed costs for using this work resource during this period.
Fixed Cost = work resource optimized units * asset fixed cost defined in Work
Resources

Variable Cost
The costs attributed to hourly usage of the work resource. This is calculated by taking the
number of hours and multiplying by the hourly cost capacity (as defined in work
resources).

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 197

Chapter 4 Optimization Output Tables

Variable Cost = Hours x Hourly <Cap,Cost> (as in Work Resources).

Remaining Units
The portion of the Max Units minus Optimized Units.

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Bill Of Materials Summary

This output table summarizes the specifics of the Bills of Materials defined in the network.

Scenario
The scenario for which the summary data was generated.

Site Name
The name of the facility at which the process using the bill of materials occurs.

BOM Name
The name of the bill of materials.

Product Name
The name of the component product that is included in the bill of materials.

Type
Displays how the product is used in the BOM. The value is one of:
 component
 byproduct
 endproduct

Period Name
The name of the period in which the bill of materials applies.

198 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Transportation Asset Summary

Period No
The period sequence number for the period in which the bill of materials applies.

Quantity
The quantity of the product needed to produce the end product.

Weight
The weight of the product needed to produce the end product.

Cubic
The cubic volume of the product needed to produce the end product.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Transportation Asset Summary

The transportation asset summary table summarizes utilization and cost of transportation
assets as well as suggesting an optimal number of assets.

Scenario
The scenario for which the summary data was generated.

Name
The name of the transportation asset.

Max Units
The number of units specified in the Transportation Assets data table.

Period Name
The name of the period to which these transportation asset statistics apply.

Optimized Units
The optimal number of transportation asset units for this period.

Utilization
The proportion of time this asset is being used, when compared to the total time the
asset is available during this period.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 199

Chapter 4 Optimization Output Tables

Fixed Cost
The total fixed costs for using this asset during this period.
Fixed Cost = Optimized Units * Unit Fixed Cost from Transportation Assets
If the fixed cost is applied to the horizon, the number of optimized units is the maximum
Optimized Units value across all periods.

Variable Cost
The total variable costs for using this asset during this period. This amount is calculated
from the Hourly Cap Cost function specified on the Transportation Assets data table and
the total time this asset is used in this period. The cost includes the load cost, unload
cost, and Return Trip Cost from the Transportation Policies table.

Num Trips
The number of times this transportation asset is used during this period. This number is
calculated by dividing the number of flow units by the limiting fill level, which refers to
either the quantity, volume, or cubic fill level that reaches capacity first.

Remaining Units
The number of Transportation Asset units not utilized during optimization.
Remaining Units = Max Units - Optimized Units

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Network Paths
Use Network Paths to review the landed cost of the overall flow of product from
production to customer receipt. These paths can be generated by clicking the arrow
below the Run Optimization button, and then selecting Generate Network Paths.
If your model is a multi-time period model, Network Paths are generated per period.

Scenario
The scenario for which the summary data was generated.

200 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Paths

Source Name
The name of the site from which the network path originates.

Destination Name
The name of the site or customer at which the network path ends.

Product Name
The name of the product that flows between the source and destination.

Mode
The mode on which the product flows.

Flow Units
The number of units that flow on the site-destination-product-mode combination.

Flow Weight
The weight of the flow traveling on this network path.

Flow Cubic
The cubic volume of the flow traveling on this network path.

Flow Inbound Warehousing Cost

The inbound warehousing cost incurred by the network path when entering the
destination site.

Flow Outbound Warehousing Cost

The outbound warehousing cost incurred by the network path by leaving the source site.

Flow Transportation Cost

The transportation cost incurred by the network path.

Flow Production Cost

The production cost incurred at the source site to enable the network path, if any.

Flow Duty Cost

The additional duty cost incurred by the network path.

Intransit Inventory Holding Cost

The inventory cost incurred by the travel time and units of travel.

Service Hours
The time required to traverse the network path.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 201

Chapter 4 Optimization Output Tables

Service Distance
The distance traveled along the network path.

Customer Name
The name of the customer at which the network path ends.

Revenue
The revenue, if any, generated on the network path.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Network Paths Summary

Network Paths Summary displays the overall flow of product from production to customer
receipt. These paths can be generated by clicking the arrow below the Run Optimization
button, and selecting Generate Network Paths.

Scenario
The scenario for which the summary data was generated.

Product Name
The name of the product that flows between the source and destination.

Customer Name
The name of the final recipient of the product flowing through the network.

Demand Qty
The overall demand requested by the customer.

Note: If aggregating all overall demand data, these values are equal for all customer-
product combinations.

Customer Flow Qty

The amount of flow traveling along this total network path. The aggregate of all customer
flow quantities equals the demand quantity of one customer-product record.

202 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Paths Summary

Facility1 (, Facility2, etc.)

The facilities the product travels through to get to the customer. The number of
Facility<x> fields depends on the number of facilities involved in the path from source to
final destination.

Mode1 (, Mode2, etc.)

The mode taken from the facility to the next location, beginning with the final facility-
customer link. The number of Mode<x> fields depends on the number of modes involved
in the path from source to final destination.

Transportation Cost
The transportation cost incurred by products traveling along the total network path.

Warehousing Cost
The warehousing cost incurred by products traveling along the total network path.

Production Cost
The production cost incurred by products originating and traveling along this total
network path.

Sourcing Cost
The other sourcing costs incurred by products traveling along this total network path.

Duty Cost
The total duties incurred by products flowing on this total network path.

Intransit Inventory Holding Cost

The total in-transit inventory costs incurred by products flowing on this total network
path.

Service Distance
The total distance traveled by product along the network path.

Service Hours
The total time taken to traverse the total network path to the customer.

Weight Qty
This is the Customer Flow Quantity multiplied by the Weight from the Product table.

Cubic Qty
This is the Customer Flow Quantity multiplied by the Cubic from the Product table.

Total Cost
The total cost incurred by product reaching the customer along this total network path.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 203

Chapter 4 Optimization Output Tables

Revenue
The revenue generated by product reaching the customer along this total network path.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Facility Status Decision History

This table is populated when you select the Generate Solution History for Sites’ Open/
Close Decisions. This enables you to gain more insight into the solutions found before the
optimal solution was found. Information such as which sites were open or closed in
certain solutions and the associated objective is generated.

Scenario
The scenario for which the summary data was generated.

Integer Solution
The Integer Solution value that was calculated at the time the solution was reported.

Site Name
The name of the site for which status is being reported.

Period Name
The name of the period for which the status information applies.

Period No
The sequence number for the period. This value is useful in sorting periods sequentially
rather than by name.

Objective Value
The Objective Value that had been calculated at the time the solution was reported.

Gap (%)
The Relative Gap (%) at the time the solution was reported. This value is the gap
between the predicted optimal solution and the particular branch-and-bound solution,
relative to the predicted optimal solution.

Solution Time
The elapsed solution time at the point at which the solution was reported.

204 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Greenfield Summary

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Greenfield Summary
One record is generated for each model/scenario that is run with Greenfield Analysis.

Scenario
The scenario for which the summary data was generated.

Total Customers
The total number of Customers in the scenario.

Total Greenfield Facilities

The total number of Greenfield facilities generated for the scenarios.

Total Existing Facilities

The total number of existing facilities used as Greenfield facilities.

Total Cost
The total cost of the scenario. It is based on flow times the distance with an assumed cost
of 1 per distance unit (for example, $1 per mile). This value is the sum of the Flow Times
Distance values from the Greenfield Flows table.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Greenfield Service
This table displays the results of applying Greenfield Service Constraints to the Greenfield
Analysis.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 205

Chapter 4 Optimization Output Tables

Scenario
The scenario for which the summary data was generated.

Service Level
The name of the Greenfield Service Constraint.

Input Service Distance

The service distance requirement defined in the Greenfield Service Constraints record.

Input Service Percentage

The Percentage Customers Served that must be served within the distance requirement
as defined in the Greenfield Service Constraints record.

Total Customers Served

The total number of customers served within this distance constraint.

Total Demand Served

The total amount of demand served within this distance constraint.

Percentage Customers Served

The percentage of customers served, relative to the total number of customers.

Percentage Demand Served

The percentage of demand met relative to the total demand. This value is calculated from
the Greenfield Flows table results, based on the customers and their associated demand
served within the mileage bands defined by the Greenfield Service Constraints.

Constraint Basis
This field displays the basis for the service constraint. The value is one of:
 % Demand Served
 % Customers Served

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

206 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Greenfield Facilities

Greenfield Facilities
This table displays a record for each Greenfield Facility. It includes new greenfield
facilities and existing facilities used in the Greenfield Analysis.

Scenario
The scenario for which the summary data was generated.

Greenfield Facility
The name of the facility used as a Greenfield location. If the location was generated by
the Greenfield algorithm, the name is Greenfield_DC_X_Y_Z, where:
 X is an incremented number for each site created within the (sub-)scenario
 Y is the scenario ID of the Greenfield Facility
 Z is the sub-scenario ID of the Greenfield Facility.
If the location was an Existing Facility, the name of that Site is displayed.

Greenfield Latitude
The optimal latitude used to place a facility to minimize weighted distance (flow x
distance) to customers.

Greenfield Longitude
The optimal longitude used to place a facility to minimize weighted distance (flow x
distance) to customers.

Closest City Latitude

The latitude of the city, based on a search of the GeoData.sgd database, that is closest to
the Greenfield Latitude.

Closest City Longitude

The longitude of the city, based on a search of the GeoData.sgd database, that is closest
to the Greenfield Longitude.

Distance
The total distance between the Calculated Latitude/ Longitude values and the Closest
Latitude/Longitude, based on a straight line + circuity factor calculation.

City
The city found in the GeoData.sgd database search.

State
The state found in the GeoData.sgd database search.

Country
The country found in the GeoData.sgd database search.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 207

Chapter 4 Optimization Output Tables

Output Type
This field displays the location option used to generate the Greenfield Facility. This will be
one of:
 Greenfield Lat/Long
 Closest City

Greenfield Status
The status of the Greenfield Facility based on its use in the Greenfield Flows table:
 Open/Used – If the Greenfield Facility exists in both the Greenfield Facilities table and
Greenfield Flows table.
 Open/Not Used – If the Greenfield Facility does not exist in both the Greenfield
Facilities table and Greenfield Flows table.

Throughput Level
The throughput at the Greenfield Facility, based on its use in the Greenfield Flows table:
 Total sum of Flow Units for the facility – If the Greenfield Facility exists in both the
Greenfield Facilities table and the Greenfield Flows table.
 0 – If the Greenfield Facility does not exist in both Greenfield Facilities table and the
Greenfield Flows table.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Greenfield Flows
This table displays each customer facility and the Greenfield Facility to which it is
assigned.

Scenario
The scenario for which the summary data was generated.

Source Name
The name of the Greenfield Facility.

Customer Name
The name of the customer served by the Greenfield Facility.

208 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Vehicle Route Optimization Summary

Flow Units
The number of units served for the customer by the Greenfield Facility.

Distance
The distance from the Source to the Customer, based on the latitudes and longitudes of
the Source and the Customer and a straight line + circuity factor calculation.

Flow Times Distance

The Flow Units multiplied by the Distance. This value serves as a proxy for cost at $1 per
mile.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the summary data was
generated. Click on the field guru for the field to open a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names, in addition to the field that is
being modified and the operator and value of that field. The summary table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Vehicle Route Optimization Summary

Scenario
The scenario for which the output data was generated.

Model Run Time

The date and time of the optimization run.

Total Transportation System Cost

The total cost of the complete vehicle route optimization solution. This value is
Total Route Cost +Total Fixed Asset Cost + Unrouted Shipment Direct Shipping Cost

Total Route Cost

The total cost of the generated routes.

Total Direct Shipping Cost

The total cost incurred in the solution based on the Direct Shipping Cost from the
Shipments table. This is the sum of all direct shipping costs where shipments were
assigned to Direct routing rather than on routes generated by Vehicle Route Optimization.

Total Fixed Asset Cost

The total fixed asset cost incurred in the solution. This is based on the Unit Fixed Cost as
defined in the Transportation Asset table. The Total Fixed Asset Cost is only incurred when

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 209

Chapter 4 Optimization Output Tables

running the Asset Optimization problem type, or when the Asset Optimization option is
selected for the Interleaved Optimization problem type.

Total Routes
The total number of generated routes.

Total Assets
The total number of unique transportation assets used.

Total Stops
The total number of stops on the generated routes.

Total In Transit Stops

The number of in-transit stops on the generated routes. This count does not include the
initial stop at the pool site nor the final stop at the pool site for round trip routes. It also
does not include stops at a domicile, in the case where the asset is located at a site other
than the pool site.

Total Distance
The total distance travelled on the generated routes.

Total Reposition Distance

The total distance the assets travelled to return to their starting locations in round trip
routes. The equipment is typically empty for this distance.

Total Time
The total time in minutes spent on the generated routes. This is defined as End Date Time
- Start Date Time per route.

Total Input Quantity

The total of all shipment quantities considered for vehicle route optimization.

Total Output Quantity

The total of all shipment quantities carried on the generated routes.

Total Input Weight

The total of all shipment weight considered for vehicle route optimization.

Total Output Weight

The total of all shipment weight carried on the generated routes.

Total Input Cubic

The total of all shipment cubic volume considered for vehicle route optimization.

210 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Vehicle Route Optimization Summary

Total Output Cubic

The total of all shipment cubic volume carried on the generated routes.

Total Segments
The total number of segments on all generated routes. Segments are the lanes between
pairs of stops.

Total Deliveries
The total number of delivered shipments on all generated routes.

Total Unrouted Shipments

The total number of unrouted shipments. Unrouted shipments are those shipments that
are not routed by Vehicle Route Optimization. Shipments are typically unrouted when
they violate a constraint such as equipment capacity or business hours at a location.
Shipments can also be unrouted if the Direct Shipment Cost is less than the cost to route
a shipment. The Direct Shipment Cost is often the cost to deliver the shipment using LTL
or parcel shipping.

Total Invalid Shipments

The total number of invalid shipments. Invalid shipments are those shipments that
cannot be considered for routing by Vehicle Route Optimization. In many cases, the
Origin or Destination in the Shipment record does not have a corresponding Site Name in
the Sites table. This results in an invalid shipment. Conflicting constraints can also cause
a shipment to be considered invalid, such as when there are conflicting Relationship
Constraints defined for the same shipment.

Model Name
The name of the model where vehicle route optimization was run.

Optimization Type
The selected algorithm run on the data. One of the following:
 Standard Optimization
 Backhaul Optimization
 Periodic Optimization
 Asset Optimization
 Interleaved Optimization

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 211

Chapter 4 Optimization Output Tables

Assets
The Assets table provides information about sequence of routes that are assigned to an
asset during the planning horizon by Vehicle Route Optimization.

Scenario
The scenario for which the output data was generated.

Asset ID
The identifier of the asset.

Asset Name
The equipment type that the asset represents.

Equipment ID
The identifier of the equipment, made up of the asset name, pool site and asset ID.

Equipment Availability ID
The identifier of the asset from the Asset Availability table.

Location
The Site Name to which the asset is assigned from the Asset Availability table.

Start Date Time

The date and time at which the asset started its first route.

End Date Time

The date and time at which the asset ended its last route.

Total Asset Route Cost

The total cost calculated for the asset. This includes both route costs and asset fixed
costs.

Horizon Fixed Asset Cost

The total asset-based fixed cost of the asset for the model horizon.

Total Route Cost

The total cost of the routes assigned to the asset.

Total Distance
The total distance traveled by the asset.

Reposition Distance
The total distance the asset travels to return to its starting location for the round trip
routes assigned to the asset. The asset is usually empty for this distance.

212 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Assets

Total Stops
The total number of stops for the routes assigned to the asset. These stops include the
in-transit stops, plus the initial and final stops at the pool site. It also includes stops at a
domicile, if the asset is located at a site other than the pool site.

In Transit Stops
The total number of in-transit stops for the routes assigned to the asset. This count does
not include the initial stop at the pool site, nor the final stop at the pool site for round trip
routes. It also does not include stops at a domicile, if the asset is located at a site other
than the pool site.

Total Weight
The total weight carried on the asset.

Total Cubic
The total cubic volume carried on the asset.

Total Qty
The total quantity carried on the asset.

Total Time
The total time in minutes spent from the start of the first route to the end of the last
route assigned to the asset.
Total Time = End Date Time - Start Date Time

Duty Time
The total duty time (in minutes) for the asset.
Duty Time = Drive Time (driving time) + Service Time (loading/unloading time)

Drive Time
The total driving time expressed in minutes.

Reposition Time
The total operating time, in minutes, with an empty load. This is the time the asset
travels to return to its starting location for the round trip routes assigned to the asset.

Service Time
The time incurred in activities such as loading and unloading shipments. You can define
Fixed Service Time and Variable Service Time on the Transportation Assets table, Fixed
Service Time and Variable Service Time on the Sites table, and Service Time (service
time at the non-pool site location) on the Shipment itself.

Wait Time
The total wait time, in minutes, incurred at locations. For example, wait time can be
incurred when the equipment arrives before opening time at a location.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 213

Chapter 4 Optimization Output Tables

Break Time
The total break time, in minutes, from short breaks within a shift. You must define Min
Break Time Within Shift and Max Drive Time Within Shift in the Transportation Asset table
to incur short breaks within a shift.

Overnight Time
The time incurred due to Min Break Time Between Shifts, which is defined in
Transportation Assets. The shift is defined based on the Max Duty Time Per Shift in
Transportation Assets.

Total Gap Time Between Routes

The total time accumulated through gaps between the end and start of all the routes
assigned to an asset, in minutes.

Max Out Of Route Percent

Used when determining how far apart stops on a route can be, this field displays the
maximum out of route percentage incurred for a route assigned to the asset. The Out of
Route Percent per Route is calculated as:
Out Of Route Percent = (Traveled Distance - Direct Distance) / Direct Distance
where
 Traveled Distance is the sum of the distances between all stops on the route.
 Direct Distance is the distance from the pool site to the furthest customer. This
distance is multiplied by 2 if the route is a round trip.

Avg Out Of Route Percent

Used when determining how far apart stops on a route can be, this field displays the
average of the out of route percentages for the routes assigned to the asset. The Out of
Route Percent per Route is calculated as:
Out Of Route Percent = (Traveled Distance - Direct Distance) / Direct Distance
where
 Traveled Distance is the sum of the distances between all stops on the route.
 Direct Distance is the distance from the pool site to the furthest customer. This
distance is multiplied by 2 if the route is a round trip.

Start Date Time Local

The local time of the first location at the start of the first route assigned to the asset.

End Date Time Local

The local time of the last location at the end of the last route assigned to the asset.

Asset Utilization
The utilization is calculated as:
(Segment Distance * Load on the Segment by Key UoM) / (Total Distance * Asset
Capacity by Key UoM)

214 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Routes

summed for each segment on the asset.

Number of Routes
The number of routes that are assigned to the asset.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Routes
The Routes table provides information about each vehicle route generated by Vehicle
Route Optimization.

Scenario
The scenario for which the output data was generated.

Route ID
The identifier of the route.

Asset Name
The identifier of the asset used on the route.

Pool Site
The shipment pooling origin site for outbound consolidation or destination site for
inbound consolidation. For Outbound Consolidation, this site is the origin of the
shipments, typically a distribution center. For Inbound Consolidation, this site is the
destination of the shipments.

Total Cost
The total cost calculated for the route.

Direct Shipping Cost

The direct shipping cost of all shipments on the route. This value is based on the Direct
Shipping Cost populated on the Shipments table.

Fixed Cost
The Fixed Cost for the route as defined in the Rate table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 215

Chapter 4 Optimization Output Tables

Unit Cost
The Unit Cost for the route as defined by the Per Unit Cost in the Rate table.

Total Stops
The total number of stops on the route. These stops include the in-transit stops, plus the
initial and final stops at the pool site. It also includes stops at a domicile, if the asset is
located at a site other than the pool site.

In Transit Stops
The number of in-transit stops on the route. This count does not include the initial stop at
the pool site, nor the final stop at the pool site for round trip routes. It also does not
include stops at a domicile, if the asset is located at a site other than the pool site.

Total Distance
The total distance traveled on the route.

Reposition Distance
The distance the asset travels to return to its starting location in a round trip route. The
asset is usually empty for this distance.

Multi-Stop Savings
The savings achieved by using a consolidated, or multi-stop, route instead of Direct
routing.

Selected Mode Cost

The cost of the mode as shown in Selected Mode, which is the least cost mode for the
route. You can use this column to determine the total cost of the hybrid transportation
network which includes both consolidated routes and Direct lanes.

Selected Mode
The least expensive mode, either Multi-Stop or Direct.

Total Weight
The total weight carried on the route.

Total Cubic
The total cubic volume carried on the route.

Total Qty
The total quantity carried on the route.

Start Date Time

The date and time at which the route started.

216 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Routes

End Date Time

The date and time at which the route ended.

VRP Number
The problem ID, used when multiple Supply Chain Guru instances are called
simultaneously.

Break Time
The total break time, in minutes, from short breaks within a shift. You must define Min
Break Time Within Shift and Max Drive Time Within Shift in the Transportation Asset table
to incur short breaks within a shift.

Trans Mode ID
The mode ID for the route.

Total Time
The total time in minutes spent on the route.
Total Time = End Date Time - Start Date Time

Duty Time
The total duty time (in minutes) for the route.
Duty Time = Drive Time + Service Time (loading/unloading time)

Drive Time
The total operating time, or driving time, expressed in minutes.

Reposition Time
The total operating time, in minutes, with an empty load.

Wait Time
The total wait time, in minutes, incurred at delivery locations. For example, wait time can
be incurred when the equipment arrives before opening time at a location.

Service Time
The time incurred in activities such as loading and unloading shipments. You can define
Fixed Service Time and Variable Service Time on the Transportation Assets table, Fixed
Service Time and Variable Service Time on the Sites table, and Service Time (service
time at the non-pool site location) on the Shipment itself.

Overnight Time
The time incurred due to Min Break Time Between Shifts, which is defined in
Transportation Assets. The shift is defined based on the Max Duty Time Per Shift in
Transportation Assets.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 217

Chapter 4 Optimization Output Tables

Equipment ID
The unique ID of the specific piece of equipment, if defined.

Carrier ID
The carrier, if defined, assigned to the route.

Start Date Time Local

The local time of the first location at the start of the route.

End Date Time Local

The local time of the last location at the end of the route.

Lock Type
The lock type for the route. By default, routes are not locked, and the Lock Type is 0.
 If the parameter readPreviousResult = TRUE, and the RouteOutput.csv file is in the
OUTPUT0 folder, a Lock Type > 0 indicates this route from the previous result is read
in but locked and therefore not considered by the scheduling algorithm. The route and
its stops, segments, and shipments are posted to the output.
 If Lock Type = 1, all properties of the route are kept unchanged.
 If Lock Type = 2, some properties of the route, such as time and distance, are
recalculated and updated.

Out Of Route Percent

Used when determining how far apart stops on a route can be, this field displays the out
of route percentage on the route.
Out Of Route Percent = (Traveled Distance - Direct Distance) / Direct Distance
where
 Traveled Distance is the sum of the distances between all stops on the route.
 Direct Distance is the distance from the pool site to the furthest customer. This
distance is multiplied by 2 if the route is a round trip.

Max Qty
The maximum quantity that was on the route. On an outbound route, this amount is
typically the total quantity loaded at the origin pool site. On an inbound route, this
amount is typically the total quantity delivered at the destination pool site.

Max Cubic
The maximum cubic volume that was on the route. On an outbound route, this amount is
typically the total cubic loaded at the origin pool site. On an inbound route, this amount is
typically the total cubic delivered at the destination pool site.

Max Weight
The maximum weight that was on the route. On an outbound route, this amount is
typically the total weight loaded at the origin pool site. On an inbound route, this amount
is typically the total weight delivered at the destination pool site.

218 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Routes

Comp2 Quantity
The total quantity carried on the route in the second asset compartment.

Comp2 Weight
The total weight carried on the route in the second asset compartment.

Comp2 Cubic
The total cubic volume carried on the route in the second asset compartment.

Duty Cost
The total duty cost incurred on the route. If you have specified Duty Time Cost on the
Rate table:
Duty Cost = Duty Time Cost * Duty Time
If Duty Time Cost is not specified:
Duty Cost = (Drive Time Cost * Drive Time) + (Service Time Cost * (Fixed Service
Time + Variable Service Time)) + (Wait Time Cost * Wait Time) + (Break Time Cost *
(Min Break Time Within Shift * number of short breaks))

Drive Time Cost

The total in-transit drive time cost incurred on the route.
Drive Time Cost = Drive Time Cost (from Rate table) * Drive Time

Service Time Cost

The total service time cost incurred on the route. The Service Time Cost is calculated as:
Service Time Cost = Service Time Cost (from Rate table) * (Fixed Service Time +
Variable Service Time)

Break Cost
The total cost incurred on the route due to short breaks that occur during a shift. The
Break Cost is calculated as:
Break Time Cost * (Min Break Time Within Shift * number of short breaks)

Overnight Cost
The total cost incurred on the route due to long (overnight) breaks that occur between
shifts. The Overnight Cost is calculated as:
(Variable Overnight Cost * (Min Break Time Between Shifts * number of overnight
breaks)) + (Fixed Overnight Cost * number of overnight breaks)

Wait Cost
The total wait time cost incurred on the route. The Wait Cost is calculated as:
Wait Time Cost * Wait Time

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 219

Chapter 4 Optimization Output Tables

Total Stop Cost

The total cost incurred due to in-transit stops on the route. The Total Stop Cost is
calculated as:
Per Stop Cost * number of In Transit Stops

Total Distance Cost

The total distance cost incurred on the route. The Total Distance Cost is calculated as:
(Per Distance Cost * loaded distance) + (Per Reposition Distance Cost * Reposition
Distance)

Total Per Reposition Distance Cost

The total reposition distance cost incurred on the route. The Total Reposition Distance
Cost is calculated as:
Per Reposition Distance Cost * Reposition Distance

Total Surcharge
The total surcharge cost incurred on the route. The Total Surcharge is calculated as:
(Surcharge Per Distance * distance) + Surcharge Percentage

CO2 Emission
Displays the total CO2 emission incurred on the route. This is the sum of the CO2
emissions calculated for all the segments on the route.

Delivered Stops
This is the number of stops at which deliveries are made. These are the outbound stops.

Delivered Qty
This is the total shipment quantity on the load that is delivered at sites.

Delivered Weight
This is the total shipment weight on the load that is delivered at sites.

Delivered Cubic
This is the total shipment cubic volume on the load that is delivered at sites.

Pickup Stops
This is the number of stops at which pickups are made. These are the inbound stops.

Pickup Qty
This is the total shipment quantity on the load that is picked up at sites.

Pickup Weight
This is the total shipment weight on the load that is picked up at sites.

220 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Stops

Pickup Cubic
This is the total shipment cubic volume on the load that is picked up at sites.

Asset ID
The identifier of the asset (from the Assets table) to which the route is assigned.

Asset Sequence ID
The sequence number of the route on the asset.

Route Utilization
The utilization is calculated as:
(Segment Distance * Load on the Segment by Key UoM) / (Total Distance * Asset
Capacity by Key UoM)
summed for each segment on the route.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Stops
The Stops table provides information about each stop on the routes generated by Vehicle
Route Optimization.

Scenario
The scenario for which the output data was generated.

Stop ID
The identifier of the stop.

Route ID
The identifier of the route (from the Routes table) on which the stop is located.

Sequence ID
The sequence number of the stop on the route.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 221

Chapter 4 Optimization Output Tables

Stop Type
The type of stop. The value will be one of:
 Pickup - Shipments are picked up at this stop.
 Delivery - Shipments are delivered at this stop.
 Equipment Return - The equipment (asset) is returned to its original location.

Site Name
The site name of the stop location.

Arrive Date Time

The date and time at which the asset arrives at the stop.

Delivery Date Time

The date and time at which the shipment(s) are delivered at the stop.

Leave Date Time

The date and time at which the asset leaves at the stop.

Qty
The shipment quantity picked up or delivered at the stop.

Weight
The shipment weight picked up or delivered at the stop.

Cubic
The shipment cubic volume picked up or delivered at the stop.

Pickup Cubic
Displays the cubic volume that is picked up at the stop.

Pickup Weight
Displays the weight that is picked up at the stop.

Pickup Qty
Displays the quantity that is picked up at the stop.

Delivered Cubic
Displays the cubic volume that is delivered at the stop.

Delivered Weight
Displays the weight that is delivered at the stop.

Delivered Qty
Displays the quantity that is delivered at the stop.

222 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Stops

Remaining Cubic
Displays the cubic volume that remains on the asset after shipments have been picked up
or delivered (or both) at the stop.

Remaining Weight
Displays the weight that remains on the asset after shipments have been picked up or
delivered (or both) at the stop.

Remaining Qty
Displays the quantity that remains on the asset after shipments have been picked up or
delivered (or both) at the stop.

Longitude
The longitude of the stop location.

Latitude
The latitude of the stop location.

VRP Number
The problem ID, used in case multiple Supply Chain Guru instances are called at a time.

Arrive Date Time Local

The local date and time at which the asset arrives at the stop.

Delivery Date Time Local

The local date and time at which the shipment(s) are delivered at the stop.

Leave Date Time Local

The local date and time at which the asset leaves at the stop.

Shipment ID
The identifier(s) of shipment(s) picked up or delivered at the stop.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 223

Chapter 4 Optimization Output Tables

Segments
The Segments table provides information about each leg between an origin and
destination on the vehicle routes generated by Vehicle Route Optimization.

Scenario
The scenario for which the output data was generated.

VRP Number
The problem ID, used in case multiple Supply Chain Guru instances are called at a time.

Route ID
The identifier of the route (from the Route table) on which the segment is located.

Start Date Time

The start date and time at the first stop on the segment.

End Date Time

The end date and time at the last stop on the segment.

Distance
The distance from the first stop to the last stop on the segment.

Drive Time
The total time from the first stop to the last stop on the segment (drive time plus any
handling time).

Carry Shipments
The identifiers of the shipments that are carried on the segment.

Start Date Time Local

The start date and time in local time at the first stop on the segment.

End Date Time Local

The end date and time in local time at the last stop on the segment.

Segment ID
The identifier of the segment.

Sequence ID
The sequence number of the segment on the route.

Start Stop ID
The identifier of the first stop on the segment. The identifier is from the Stops table.

224 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Route Breaks

Start Site
This field displays the name of the site represented by the Start Stop ID.

End Stop ID
The identifier of the last stop on the segment. The identifier is from the Stops table.

End Site
This field displays the name of the site represented by the End Stop ID.

CO2 Emission
Displays the CO2 emission incurred on the segment. The emission is calculated as:
((Tare weight of vehicle + weight of shipments onboard) * CO2 factor) * Distance
traveled
The CO2 factor is defined on the Transportation Assets table.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Route Breaks
The Route Breaks table provides information about the various breaks that are taken
during the route. These can be short breaks, such as a break within a driver’s shift, or
longer overnight breaks between shifts.

Scenario
The scenario for which the output data was generated.

Route Break ID
The identifier of the route break.

Break Start Date Time

The date and time at which the break starts.

Break End Date Time

The date and time at which the break ends.

Break Start Date Time Local

The date and time in local time at which the break starts.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 225

Chapter 4 Optimization Output Tables

When determining the local start and end times for those breaks that occur within transit,
the time zone of the Origin of the segment is used.

Break End Date Time Local

The date and time in local time at which the break ends.
When determining the local start and end times for those breaks that occur within transit,
the time zone of the Origin of the segment is used.

Route Event Type

The type of break. This is one of:
 Overnight - These breaks can incur the Overnight Cost that results from a Fixed
Overnight Cost or a Variable Overnight Cost (or both) as defined on the Rate table.
Overnight breaks are based on the Min Break Time Between Shifts value in the
Transportation Assets table.
 Short - These breaks can incur the Break Cost that results from a Break Time Cost
value as defined on the Rate table. Short breaks are defined by the Min Break Time
Within Shift value in the Transportation Assets table. Short breaks are calculated if Max
Drive Time Within Shift and Min Break Time Within Shift are both populated.

Route ID
The identifier of the route (from the Route table) on which the route break occurs.

Stop ID
The identifier of the stop (from the Stops table) at which the route break occurs.

Overnight Cost
For an overnight route break, the cost that is incurred based on the Fixed Overnight Cost
and Variable Overnight Cost defined in the Rate table.

Break Cost
For a short route break, the cost that is incurred based on the Break Time Cost defined in
the Rate table.

Segment ID
The identifier of the segment (from the Segments table) on which the route break occurs.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

226 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Input Shipments

Input Shipments
The Input Shipments table provides information about the shipments that were
considered for vehicle routing by Vehicle Route Optimization.

Scenario
The scenario for which the output data was generated.

Shipment ID
The identifier of the delivered shipment.

Customer ID
The destination site name for the shipment.

Source Site
The source site name for the shipment.

Destination Site
The source site name for the shipment.

Product Name
The name of the product for the shipment.

Priority
Display the shipment’s priority.

Qty
The quantity of the delivered shipment. This may be less than the total quantity of the
original shipment if the shipment was split.

Weight
The weight of the delivered shipment. This may be less than the total weight of the
original shipment if the shipment was split.

Cubic
The cubic volume of the delivered shipment. This may be less than the total cubic volume
of the original shipment if the shipment was split.

Earliest Delivery Date

This field displays the start of the delivery time window for the shipment. This is the
Order Time value from the Shipments (or Demand) table.

Latest Delivery Date

This field displays the end of the delivery time window for the shipment. This is the Due
Date value from the Shipments (or Demand) table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 227

Chapter 4 Optimization Output Tables

Comp2 Quantity
The quantity for this shipment specified for the second asset compartment.

Comp2 Weight
The weight for this shipment specified for the second asset compartment.

Comp2 Cubic
The cubic volume for this shipment specified for the second asset compartment.

Earliest Pickup Date

The start of the pickup time window for the shipment.

Latest Pickup Date

The end of the pickup time window for the shipment.

Order ID
The Order ID for the shipment.

Pool Site
The shipment pooling origin site for outbound consolidation or destination site for
inbound consolidation. For Outbound Consolidation, this is the origin of the shipments,
typically a distribution center. For Inbound Consolidation, this is the destination of the
shipments.

Trans Mode ID
The mode ID for the shipment.

Route ID
The Route ID to which the shipment was assigned in the Shipments table for baseline
modeling. The order of the shipments on the route is determined by the value you enter
for Sequence.

Sequence ID
The sequence number that determines the order of the shipment on the route assigned
with Route ID.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

228 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Unrouted Shipments

Unrouted Shipments
The Unrouted Shipments table lists those shipments that could not be routed by Vehicle
Route Optimization. Shipments are typically unrouted when they violate a constraint such
as equipment capacity or business hours at a location.

Scenario
The scenario for which the output data was generated.

Name
The name of the shipment that was determined to be unrouted.

Product Name
This field displays the Product Name value from the Shipments (or Demand) table.

Source Site
The source site of the invalid shipment.

Destination Site
The destination site of the invalid shipment.

Weight
The weight of the unrouted shipment. This may be less than the total weight of the
original shipment if the shipment was split.

Cubic
The cubic volume of the unrouted shipment. This may be less than the total volume of
the original shipment if the shipment was split.

Qty
The quantity of the unrouted shipment. This may be less than the total quantity of the
original shipment if the shipment was split.

Direct Shipping Cost

The Direct Shipping Cost (if any) applied to the shipment. You enter the Direct Shipping
Cost on the Shipments table.

VRP Number
The problem ID, used in case multiple Supply Chain Guru instances are called at a time.

Comp2 Quantity
The quantity for this shipment specified for the second asset compartment.

Comp2 Weight
The weight for this shipment specified for the second asset compartment.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 229

Chapter 4 Optimization Output Tables

Comp2 Cubic
The cubic volume for this shipment specified for the second asset compartment.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Invalid Shipments
The Invalid Shipments table lists those shipments that cannot be considered for routing
by Vehicle Route Optimization.

Scenario
The scenario for which the output data was generated.

Shipment Name
The name of the shipment that was determined to be invalid.

Product Name
This field displays the Product Name value from the Shipments (or Demand) table.

Qty
This field displays the Quantity value from the Shipments (or Demand) table.

Weight
This field displays the Weight value from the Shipments (or Demand) table.

Cubic
This field displays the Cubic value from the Shipments (or Demand) table.

Reason
The reason the shipment was invalid, if available.

VRP Number
The problem ID, used in case multiple Supply Chain Guru instances are called at a time.

Source Site
The source site of the invalid shipment.

230 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Delivered Shipments

Destination Site
The destination site of the invalid shipment.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Delivered Shipments
The Delivered Shipments table provides information about the shipments that have been
placed on vehicle routes by Vehicle Route Optimization.

Scenario
The scenario for which the output data was generated.

Shipment ID
The identifier of the delivered shipment.

Route ID
The identifier of the route used by the shipment, from the Route table.

Source Site
The source site for the shipment.

Destination Site
The destination site for the shipment.

Pickup Date Time

The date and time at which the shipment was picked up.

Delivery Date Time

The date and time at which the shipment was delivered.

Product Name
The product that is the delivered shipment.

Weight
The weight of the delivered shipment. This may be less than the total weight of the
original shipment, if the shipment was split.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 231

Chapter 4 Optimization Output Tables

Cubic
The cubic volume of the delivered shipment. This may be less than the total cubic volume
of the original shipment, if the shipment was split.

Qty
The quantity of the delivered shipment. This may be less than the total quantity of the
original shipment, if the shipment was split.

Pickup Stop ID
The identifier of the stop (from the Stops table) at which the shipment is picked up.

Delivery Stop ID
The identifier of the stop, from the Stops table, at which the shipment is delivered.

VRP Number
The problem ID, used when multiple Vehicle Route Optimization instances are called
simultaneously.

Pickup Date Time Local

The local date and time at which the shipment was picked up.

Delivery Date Time Local

The local date and time at which the shipment was delivered.

Visit Sequence ID
The identifier of the visit sequence for periodic vehicle routing problems.

Comp2 Quantity
The quantity for this shipment specified for the second asset compartment.

Comp2 Weight
The weight for this shipment specified for the second asset compartment.

Comp2 Cubic
The cubic volume for this shipment specified for the second asset compartment.

Cost To Route
Displays what it cost to add the shipment to the route. Given a route, if Shipment A is
removed, Cost to Route is the difference between the original cost and the cost without
Shipment A. Only the delivery or pickup cost is removed from the total route cost, and
the route is not reconstructed. For detailed information, refer to Cost to Route and
Allocated Cost.

232 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 PVRP Delivered Shipments

Allocated Cost
Displays an allocated cost to route the shipment. For example, assume you have three
stops on a route. This is the cost to remove each one at a time, then allocate the fixed
cost back to the shipment based on Key UoM amount per shipment. For detailed
information, refer to Cost to Route and Allocated Cost.

Direct Shipping Cost

Displays the Direct Shipping Cost (if any) applied to the shipment. You enter the Direct
Shipping Cost on the Shipments table.

Mode Suggestion
Displays one of the following, based on the route cost versus the Direct Shipping Cost:
 Route – The suggested mode is the route generated by the solver. The solver route is
more cost effective than direct shipping.
 Consider Direct Ship – If the cost of the route on which the shipment is allocated is
close to the Direct Shipping Cost to send the shipment, this is the suggested mode.
 Direct Ship – If the Direct Shipping Cost is less than the Cost to Route for the
shipment, Direct Ship is the suggested mode.

Note: Note: This field is hidden by default. You can display the field using Column
Options.

Direct Shipping Confidence %

Displays a measure of the confidence in recommending Direct Ship as the Mode, and
relates to the Mode Suggestion value as shown:
 Route – Value is 0, indicating that Direct Ship should not be the mode.
 Consider Direct Ship – Value between 0 and 1 using the ratio of the Cost to Route /
Direct Shipping Cost.
 Direct Ship – Value is 1, indicating that Direct Ship should be the mode.

Note: Note: This field is hidden by default. You can display the field using Column
Options.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
Click on the field guru for the field to open a Scenario Item Wizard summary table. This
table lists the scenario and sub-scenario names, in addition to the field that is being
modified and the operator and value of that field.

PVRP Delivered Shipments

You can review the shipments that were included in the Periodic Scheduling and Balancing
with the PVRP Delivered Shipments table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 233

Chapter 4 Optimization Output Tables

Scenario
The scenario for which the output data was generated.

Shipment ID
The identifier of the delivered shipment.

PVRP Shipment ID
This field displays a shipment identifier generated by the Vehicle Route Optimization. It is
a concatenation of the Destination Site, the Product Name and the day on which the
shipment occurred.

Route ID
The identifier of the route used by the shipment, from the Route table.

Source Site
The source site for the shipment.

Destination Site
The destination site for the shipment.

Pickup Date Time

The date and time at which the shipment was picked up.

Delivery Date Time

The date and time at which the shipment was delivered.

Product Name
The product that is the delivered shipment.

Weight
The weight of the delivered shipment. This may be less than the total weight of the
original shipment, if the shipment was split.

Cubic
The cubic volume of the delivered shipment. This may be less than the total cubic volume
of the original shipment, if the shipment was split

Qty
The quantity of the delivered shipment. This may be less than the total quantity of the
original shipment, if the shipment was split.

Pickup Stop ID
The identifier of the stop (from the Stops table) at which the shipment is picked up.

234 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 PVRP Delivered Shipments

Delivery Stop ID
The identifier of the stop, from the Stops table, at which the shipment is delivered.

VRP Number
The problem ID, used when multiple Vehicle Route Optimization instances are called
simultaneously.

Pickup Date Time Local

The local date and time at which the shipment was picked up.

Delivery Date Time Local

The local date and time at which the shipment was delivered.

Visit Sequence ID
The identifier of the visit sequence for periodic vehicle routing problems. The sequence ID
is the number of visits concatenated with the day and day index value of each visit day.
For example, you may have a sequence such as:
2_MondayDayIndex1_FridayDayIndex5
indicating 2 visits: one on Monday and the other on Friday.

Comp2 Qty
The quantity for this shipment specified for the second asset compartment.

Comp2 Weight
The weight for this shipment specified for the second asset compartment.

Comp2 Cubic
The cubic volume for this shipment specified for the second asset compartment.

Cost To Route
Displays what it cost to add the shipment to the route. Given a route, if Shipment A is
removed, Cost to Route is the difference between the original cost and the cost without
Shipment A. Only the delivery or pickup cost is removed from the total route cost, and
the route is not reconstructed. For detailed information, refer to Cost to Route and
Allocated Cost.

Allocated Cost
Displays an allocated cost to route the shipment. For example, assume you have three
stops on a route. This is the cost to remove each one at a time, then allocate the fixed
cost back to the shipment based on Key UoM amount per shipment. For detailed
information, refer to Cost to Route and Allocated Cost.

Direct Shipping Cost

Displays the Direct Shipping Cost (if any) applied to the shipment. You enter the Direct
Shipping Cost on the Shipments table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 235

Chapter 4 Optimization Output Tables

Direct Shipping Confidence %

Displays one of the following, based on the route cost versus the Direct Shipping Cost:
 Route – The suggested mode is the route generated by the solver. The solver route is
more cost effective than direct ship.
 Consider Direct Ship – If the cost of the route on which the shipment is allocated is
close to the Direct Shipping Cost to send the shipment, this is the suggested mode.
 Direct Ship – If the Direct Shipping Cost is less than the Cost to Route for the
shipment, Direct Ship is the suggested mode.

Note: Note: This field is hidden by default. You can display the field using Column
Options.

Mode Suggestion
Displays a measure of the confidence in recommending Direct Ship as the Mode, and
relates to the Mode Suggestion value as shown:
 Route – Value is 0, indicating that Direct Ship should not be the mode.
 Consider Direct Ship – Value between 0 and 1 using the ratio of the Cost to Route /
Direct Shipping Cost.
 Direct Ship – Value is 1, indicating that Direct Ship should be the mode.

Note: Note: This field is hidden by default. You can display the field using Column
Options.

ScenarioID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
Click on the field guru for the field to open a Scenario Item Wizard summary table. This
table lists the scenario and sub-scenario names, in addition to the field that is being
modified and the operator and value of that field.

Asset Summary
Scenario
The scenario for which the output data was generated.

Asset Availability ID
The identifier for the asset from the Asset Availability table.

Site Name
The site at which the asset is located (from the Asset Availability table).

236 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Multi-Objective Details

Asset Name
The name of the asset.

Assets Available
The number of assets available based on those defined in the Asset Availability table.

Assets Used
The number of this asset from this site used in the scenario.

ScenarioID
The identifier of the scenario for which the output data was generated.

Sub-ScenarioID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Multi-Objective Details
This table displays information about the various solution points generated when you run
Multi-Objective Optimization.

Scenario
The name of the scenario run to generate a full solution. Default scenario names are
generated, or you can rename the scenario when running the full solution. When
generating pareto points, but not a full solution, the value will not be populated.

Run Time
The date and time at which the multi-objective optimization was started.

Origin Scenario
The model scenario you selected when defining the Pareto Curve for multi-objective
optimization. For example, you can run multi-objective optimization on any of the
scenarios defined in your model, such as Baseline.

Objective1
This is the Objective 1 (Y Axis) value you selected when defining the Pareto Curve for
multi-objective optimization. For example, this may be Total Cost, Facility Set, % Demand
Served, etc.

Objective2
This is the Objective 2 (X Axis) value you selected when defining the Pareto Curve for
multi-objective optimization. For example, this may be Service Distance, Facility Set, %
Demand Served, etc.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 237

Chapter 4 Optimization Output Tables

Objective1 Value
This is the value calculated for Objective 1 when the multi-objective optimization scenario
is run. For example, if Objective 1 is Facility Set, this will be an integer representing the
number of facilities selected for the objective.

Objective2 Value
This is the value calculated for Objective 2 when the multi-objective optimization scenario
is run. For example, if Objective 2 is Total Weighted Transportation Time, this will be a
number representing the total service time X flow.

Total Cost
This is the total cost incurred in the multi-objective optimization scenario.

Total Profit
This is the total profit generated by the multi-objective optimization scenario.

CO2
This is the total CO2 emission incurred in the multi-objective optimization scenario.

Solution Time
This is the date and time at which the specific solution point was generated.

Scenario ID
The identifier of the scenario for which the summary data was generated.

Expression Summary
This table provides details about the constraints, including expression constraints, that
were included in the Optimization.

Scenario
The scenario for which the output data was generated.

Expression Name
The name of the constraint. If the constraint does not have an Expression Name, you see
an Expression Name value such as:
 AGGFLOWCON_<x> – The source constraint is an unnamed Flow Constraint.
 AGGINVCON_<x> – The source constraint is an unnamed Inventory Constraint.
 AGGPRODCON_<x> – The source constraint is an unnamed Production Constraint.
 AGGEDPCONS_<x> – The source constraint is an unnamed Expression Constraint.
where x is an integer used to uniquely identify the constraint.

Expression Basis
The basis for the constraint. This will be one of:

238 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Expression Based Cost Summary

 Quantity
 Weight
 Cubic

Expression Value
The value evaluated for the constraint. For example, if you have a Flow constraint with a
requirement of 500 using a requirement type of Max, if the solution uses a Flow of 400,
the Expression Value will be 400. If you have a Flow constraint using a requirement of
1000 with a requirement type of Min, if the solution uses a Flow of 1200, the Expression
Value will be 1000 (the actual value of the constraint).

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Expression Based Cost Summary

This table provides details about the Expression Based Costs that were included in the
Optimization.

Scenario
The scenario for which the output data was generated.

Cost Name
The name of the Expression Based Cost.

Cost Value
The total cost value of the Expression Based Cost. This includes both the Fixed
Component and Variable Component values.

Expression Name
The Expression to which the cost is applied. This can be a regular constraint or an
Expression Constraint.

Expression Value
The value evaluated for the constraint specified in Expression Name. For example, if you
have a Flow constraint with a requirement of 500 using a requirement type of Max, if the
solution uses a Flow of 400, the Expression Value will be 400. If you have a Flow
constraint with a requirement of 1000 using a requirement type of Min, if the solution
uses a Flow of 1200, the Expression Value will be 1000 (the actual value of the
constraint).

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 239

Chapter 4 Optimization Output Tables

Fixed Component
The cost incurred based on the Fixed Cost Component defined in the Expression Based
Costs record.

Variable Component
The cost incurred based on the Fixed Cost Component defined in the Expression Based
Costs record.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

Constraint Summary
This table provides details about the Constraints (regular constraints and Expression
Constraints) that were included in the Optimization.

Scenario
The scenario for which the output data was generated.

Constraint
This indicates the type of constraint. For example, if you have defined a Flow Constraint,
the value will be Flow. Expression Constraints will be shown as Expression.

Note: If you have entered values for constraining fields the the Inventory Policies table
(such as Max Inv Qty, Min Inv Qty and Safety Stock), these will be reflected as
records in the Constraint Summary table. The Constraint Names will be
MaximumInventory, MinimumInventory and SafetyStock.

Expression
This is the Expression Name entered in the constraints tables. If the constraint does not
have an Expression Name, you see an Expression Name value such as:
 AGGFLOWCON_<x> – The source constraint is an unnamed Flow Constraint.
 AGGINVCON_<x> – The source constraint is an unnamed Inventory Constraint.
 AGGPRODCON_<x> – The source constraint is an unnamed Production Constraint.
 AGGEDPCONS_<x> – The source constraint is an unnamed Expression Constraint.
where x is an integer used to uniquely identify the constraint.

Site
This is the Site Name for Inventory Constraints and Production Constraints

240 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Constraint Summary

Source
This is the Source Site for Flow Constraints.

Destination
This is the Destination Site for Flow Constraints.

Product
This is the Product Name for the constraint (all constraint types).

Mode
This is the Mode for Flow Constraints.

Period
This is the Period Name for the constraint (all constraint types).

Period Number
This is the Period number for the constraint (all constraint types).

Asset
This is the name of the Transportation Asset for any asset-based constraint. For work
center constraints, the Work Center Name is displayed here.

Process
This is the Process Name for any process-based constraints.

Other

Range
When Shelf Life it used, this value represents the age to which the constraint applies.

Constraint Type
This is the requirement type for the constraint. It will be one of:
 Min – The value specified in the Constraint Requirement must be reached.
 Max – The value specified in the Constraint Requirement cannot be exceeded.
 Fixed – The value specified in the Constraint Requirement must be used.
 Cond Min – The value specified in the Constraint Requirement must be reached or
none at all.
 Define – Supply Chain Guru does not use the Constraint Requirement to satisfy the
constraint. This setting can be used when you are nesting Expression Constraints.

Constraint Activity
This is the activity incurred by the constraint. For example, if you have a Flow constraint
with a requirement of 500 using a requirement type of Max, if the solution uses a Flow of

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 241

Chapter 4 Optimization Output Tables

400, the Constraint Activity will be 400. If you have a Flow constraint with a requirement
of 1000 using a requirement type of Min, if the solution uses a Flow of 1200, the
Constraint Activity will be 1000 (the actual value of the constraint).

Constraint Slack
This is the difference between the Constraint Requirement and the Constraint Activity;
that is the amount of the constraint that was not used. For example, if you have a Flow
constraint with a requirement of 500 using a requirement type of Max, if the solution uses
a Flow of 400, the Constraint Activity will be 400 and the Constraint Slack will be 100.

Constraint Requirement
This is the required value that is defined for the constraint.

Diagnostic Excess
For constraints that do not meet a limit, this is the excess capacity that is available.

Diagnostic Deficit
When the model requirements exceed the constraint limit, this is the deficit incurred.

Scenario ID
The identifier of the scenario for which the output data was generated.

Sub-Scenario ID
The identifier of the sub-scenario, if applicable, for which the output data was generated.
When you click on the field guru for the field, you see a Scenario Item Wizard summary
table. This table lists the scenario and sub-scenario names along with the field that is
being modified and the operator and value of that field.

242 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Chapter 5

Simulation Output Tables

The following are Supply Chain Guru Simulation Output Tables:

 Network Summary
 Site Summary
 Asset Summary
 Work Center Summary
 Work Resource Summary
 Site Details
 Customer Details
 Network Flows
 Interfacility Shipment Flows
 Customer Shipment Flows
 Interfacility Order Flows
 Customer Order Flows
 Bill of Materials Summary
 Customer Summary
 Production Summary
 Product Summary
 Process Summary
 Network Paths
 Production Transactions
 Demand Transactions
 Shipment Transactions
 Shipment Mileage Log
 Shipment Handling Log
 Order Report
 Error Log

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 243

Chapter 5 Simulation Output Tables

Network Summary
This table provides a high-level summary of the scenario results for each scenario,
replication and period combination.

Scenario
Displays the scenario for which the simulation output has been generated.

Model Name
Displays the name of the model simulated.

Num Reps
Displays the number of replications run in the simulation.

Period Length Days

Displays the period length in days.

Total Profit
Displays the total profit (Total Revenue - Total Cost) in this period.

Total Cost
Displays the total cost incurred during this period of the simulation. Total cost is the sum
of a number of costs including total fixed operating cost, total fixed startup cost, sourcing
cost, consignment cost, total production cost, total warehousing cost, total transportation
cost, total inventory carrying cost, total CO2 cost, and total CO2 offsets cost.

Total Revenue
Displays the total revenue generated during the simulation by product being shipped to
customers in this period. The revenue is based on the Product Price and the units of
demand served. If the Price is a number, this is multiplied by units of demand served to
calculate revenue.

Total Fixed Operating Cost

Displays the total fixed operating cost incurred during this period of the simulation.

Total Fixed Startup Cost

Displays the total fixed startup cost incurred during this period of the simulation.

Total Inbound Warehousing Cost

Displays the Total Inbound Warehousing Cost incurred during this period of the
simulation. Total Inbound Warehousing Costs are incurred when goods are brought in
from dock to stock, excluding transportation costs. This is based on the Inbound Cost in
the Inventory Policies table.

244 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Summary

Total Outbound Warehousing Cost

Displays the Total Outbound Warehousing Cost incurred during this period of the
simulation. Total Outbound Warehousing Costs are incurred when goods are brought in
from stock to dock, excluding transportation costs. This is based on the Outbound Cost in
the Inventory Policies table.

Total Production Cost

Displays the total cost of production for products in this period. This is based on the
Setup Cost per lot and the Cost Per Unit in the Processes table.

Total Transportation Cost

Displays the cost incurred transporting products between facilities and to customer during
this period.

Total Inventory Carrying Cost

Displays the cost to hold inventory incurred during this period. This is calculated by the
multiplying the total inventory, the product value, the Inv Carrying Cost %, and the
runtime, and dividing the product by 365.

Avg Fill Rate

Displays the Average Fill Rate incurred during the simulation. The average fill rate for a
facility is the weighted average of the number of orders that were fulfilled completely or
partially (by placing orders up the network) to the total number of orders.

Avg Fill Qty Rate

Displays the Average Fill Qty Rate incurred during the simulation. The average fill
quantity rate for a facility is the weighted average of the number of units that were
available at the facility to fulfill orders to the total number of units shipped out.

Total CO2
Displays the total CO2 output of the simulation, as generated by facilities, production,
and transportation during this period.

Total Carbon Offsets

Displays the total number of Carbon Offsets used during the model simulation run.

Total Carbon Offset Cost

Displays the Total Carbon Offset Cost incurred during the simulation based on the number
of carbon offsets and the carbon offset price.

Carbon Offset Price

Displays the price of a single carbon offset in the given model run.

Avg Ready Rate

This is the percentage of no stockout in any given aggregation period; that is the fraction
of time with positive stock on-hand.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 245

Chapter 5 Simulation Output Tables

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Total Demand
Displays the total units of demand for the period.

Lost Demand
Displays the number of demand units that were lost during this period in the simulation
replication. Demand units which cannot be delivered based on values such as Due Date
are reported as lost.

Lost Revenue
Displays the lost revenue due to lost demand units during this period in the simulation
replication.

Total Duty Cost

Displays the additional duty cost incurred during this period. The duty cost is calculated
by multiplying the duty from Transportation Policies by the shipment’s total value. The
total value is the Value from the Product table multiplied by shipment quantity.

Transportation CO2
Displays the total emissions of transportation-related CO2 in unit mass in this period
based on the CO2 and CO2 Basis in Transportation Policies.

Production CO2
Displays the total emissions of production-related CO2 in unit mass in this period based
on the CO2 in Sourcing Policies.

Fixed CO2
Displays the total emissions of site-related CO2 in unit mass in this period based on the
Fixed CO2 <Cap,Cost> in the Sites table.

Avg On Time Rate

Displays the weighted average of the orders that were successfully delivered on time to
the total number of orders received during this period.

Avg On Time Qty Rate

Displays the weighted average of the number of units that were delivered on time to the
total number of orders received during this period.

Rep
Displays the replication number of the scenario that generated the summary data.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

246 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Site Summary

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Site Summary
This table breaks down costs, revenue, inventory, and flow by site. This table contains a
unique record for each site, scenario, replication and period combination.

Scenario
Displays the name of the scenario which generated the site summary data.

Site Name
Displays the name of the site referred to in the report.

Total Cost
Displays the total cost incurred by the site. This figure is calculated by: total fixed
operating cost + total outbound transportation cost + total production cost + total
warehousing cost + total inventory carrying cost at this site +CO2 production cost + CO2
transportation cost + CO2 fixed cost.

Throughput Level
Displays the total shipment out of the site, in product units.

Throughput Basis
Displays the unit measure of the throughput. (i.e. Quantity, Weight or Cubic).

Inventory Carrying Cost

Displays the cost of holding inventory at this site. This is calculated by the multiplying the
total inventory, the product value, the Inv Carrying Cost %, and the runtime, and dividing
the product by 365.

Average Inventory Value

Displays the value of inventory at this site, based on the Value field in the Products table.

Maximum Inventory Value

Displays the highest value that total inventory value at this site ever reached throughout
the simulation run. The value is based on the Value field in the Products table.

Average Inventory Cubic

Displays the time-weighted average inventory cubic fill level at this site.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 247

Chapter 5 Simulation Output Tables

Maximum Inventory Cubic

Displays the highest value that the inventory cubic fill level at this site ever reached
throughout the simulation run.

Inventory Turns
Displays the cost of goods sold divided by average site inventory investment level (units).
This is calculated by the cost of good sold divided by the average inventory.

Total Fixed Operating Cost

Displays the fixed operating cost corresponding to the throughput level at this site.

Total Outbound Transportation Cost

Displays the total cost of shipments out of this site.

Total Production Cost

Displays the sum of production costs for all products at this site. This is calculated by
product quantity times the average unit cost, as specified in the Sourcing Policies at the
MFG site.

Avg On Time Rate

Displays the facility’s weighted average of the orders that were successfully delivered on
time to the total number of orders received.

Avg On Time Qty Rate

Displays the facility’s weighted average of the number of units that were delivered on
time to the total number of orders received.

Avg Fill Rate

Displays the facility’s weighted average of the number of orders that were fulfilled
completely/partially by placing orders up the network to the total number of orders.

Avg Fill Qty Rate

Displays the facility’s weighted average of the number of units that were available at the
facility to fulfill orders to the total number of units shipped out.

Total Inbound Warehousing Cost

Displays the cost of bringing goods from dock to stock, excluding transportation, at this
site. This is calculated by taking the number of units into the facility times the facility
Inbound Cost from the Inventory Policies table.

Total Outbound Warehousing Cost

Displays the cost of bringing goods from stock to dock, excluding transportation, at this
site. This is calculated by taking the units shipped out of the facility times the facility
Outbound Cost from the Inventory Policies table..

248 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Site Summary

Outbound Flow
Displays the number of units shipped out of this site.

Inbound Flow
Displays the number of units shipped into this site.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Avg Ready Rate

This is the percentage of no stockout in any given aggregation period; that is the fraction
of time with positive stock on-hand.

Outbound Weight
Displays the total weight of products shipped out of this site.

Inbound Weight
Displays the total weight of products shipped into the site.

Outbound Cubic
Displays the total cubic volume of products shipped out of this site.

Inbound Cubic
Displays the total volume of products shipped into the site.

COGS (Cost of Goods Sold)

Displays the total cost of all components and products used for shipments at this site. this
is calculated by taking the sum of each product's throughput times its product value.

Total CO2
Displays the total emissions of CO2 in unit mass (fixed + production + transport).

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 249

Chapter 5 Simulation Output Tables

Asset Summary
This table shows details regarding individual transportation assets. This table contains a
unique record for each asset, scenario, replication and period combination.

Scenario
Displays the name of the scenario which generated the asset summary data.

Name
Displays the name of the particular asset in the report.

Available Time
Displays the total time (in days) that all units of this asset are available (but not in use)
during the model run.

Utilized Time
Displays the total time (in days) all asset units were in the process of transporting a
shipment during model run.

Setup Time
Displays the total Setup time (in days) for the particular asset during model run load or
unload shipments (or a return trip). This is calculated by taking the number of flow units
divided by the lot size, and multiplying by the changeover time.

Scheduled Down Time

Displays the total time (in days) scheduled for the asset to be non-operational.

Unscheduled Down Time

Displays the total time (in days) the asset was non-operational that was unplanned.

Average Units Utilized

Displays the time the asset is being used divided by total simulation time in days. This is
calculated by taking the asset utilized time and dividing it by the total model run time.

Maximum Units Utilized

Displays the maximum number of assets in used at any one point in time during the
model run.

Total Utilization
Displays the total utilization percentage for all assets of this type during the model run.
This is calculating by dividing the asset utilized time by the sum of the asset available
time, the asset setup time, and the asset utilized time.
Utilized Time / (Available Time + Setup Time + Utilized Time)

250 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Center Summary

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Work Center Summary

This table shows details regarding work centers. This table contains a unique record for
each work center, scenario, replication and period combination.

Scenario
Displays the name of the scenario which generated the work center summary data.

Site Name
Displays the site where the work center is located.

Name
Displays the name of the work center.

Available Time
Displays the amount of time that the work center was available for production but was
unused (unit is DAY). For example, if the last production occurs on 1/7/2014 and the
model horizon end is 1/10/2014, the available time is 4 days.

Utilized Time
Displays the total time in days that the work center is employed. This is from the Stats.
Start Date/Time as defined in Model Options to the final production time.

Setup Time
Displays the time the work center required to be setup in days, as accounted for in the
Work Centers Changeovers table. This is calculated by taking the number of flow units
divided by the lot size, and multiplying the result by the changeover time.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 251

Chapter 5 Simulation Output Tables

Scheduled Down Time

Displays the time in days scheduled for the asset to be non-operational.

Unscheduled Down Time

Displays the time in days asset was non-operational that was unplanned.

Average Queue Depth

Displays the average number of units waiting to be processed at the work center

Maximum Queue Depth

Displays the maximum number of units waiting at any point of time to be processed at
the work center

Total Utilization
Displays the ratio of the work center utilized time to the total time (start to end of the
model horizon).

Throughput Level
Displays the total shipment out of the work center, in product units.

Throughput Basis
Displays the unit measure of the throughput. (i.e. Quantity, Weight or Cubic).

Total Fixed Operating Cost

Displays the fixed operating cost corresponding to the throughput level at this work
center.

Outbound Flow
Displays the number of units shipped out of this work center.

Outbound Weight
Displays the total weight of products shipped out of this work center.

Outbound Cubic
Displays the total cubic volume of products shipped out of this work center.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

252 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Work Resource Summary

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Work Resource Summary

This table shows details regarding work resources. This table contains a unique record for
each work resource, scenario, replication and period combination.

Scenario
Displays the name of the scenario which generated the work resource summary data.

Site Name
Displays the site where the work resource is located.

Name
Displays the name of the particular work resource in the report.

Available Time
Displays the amount of time that the work resource was available for production but was
unused (unit is DAY).

Utilized Time
Displays the total time in days that the work resource is employed.

Average Units Utilized

Displays the average number of units of the work resource that are used.

Maximum Units Utilized

Displays the maximum number of units of the work resource that are used at any point of
time.

Total Utilization
Displays the ratio of the work resource utilized time to the total available time.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 253

Chapter 5 Simulation Output Tables

Destroyed Time
Displays the total length of time that has been incurred as a result of assets destroyed
due to ambush.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Site Details
This table shows detailed information at the site-product level, including inventory values.
This table contains a unique record for each site, product, scenario, replication and period
combination.

Scenario
Displays the name of the scenario which generated the site-product detail data.

Product Name
Displays the name of the product referred to in the report.

Site Name
Displays the name of the site referred to in the report.

Initial Inventory Units

Displays the inventory of the product at the site at the beginning of the period.

Average Inventory Units

Displays the average inventory for this product at this site during the simulation run.

Ending Inventory Units

Displays the inventory remaining at the site at the end of the simulation run.

Minimum Inventory Units

Displays the lowest value that the inventory for this product at this site ever reached
throughout the simulation run.

254 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Site Details

Maximum Inventory Units

Displays the highest value that the inventory for this product at this site ever reached
throughout the simulation run.

Average Back Order Units

Displays the mean number of back ordered items for this product at this site.

Maximum Back Order Units

Displays the highest number of back ordered items at any point of time for this product at
this site.

Average In Transit Units

Displays the average in-transit inventory level for the entire simulation run.

Maximum In Transit Units

Displays the highest value that the in-transit inventory for this product at this site ever
reached throughout the simulation run.

Average Replenishment Quantity

Displays the average replenishment quantity for Safety Stock.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Average Order Cycle Time

Displays the average of the order cycle times (in DAYS) by this site and for this product.
Order cycle time is the difference between the time the entire order was filled and the
Due Date. If the value is negative, this is a measure of how much more quickly the cycles
are being fulfilled compared to when they are due. If the Due Date is not set, it is treated
as the end of time (also known as year 100000). In this case the order cycle time will be
0.

Maximum Order Cycle Time

Displays the highest cycle time by site and product. If the Due Date is not set, it is
treated as the end of time (also known as year 100000). In this case the order cycle time
will be 0.

On Time Rate
Displays the facility’s ratio of the orders that were successfully delivered on time to the
total number of orders received.

On Time Qty Rate

Displays the facility’s ratio of the number of units that were delivered on time to the total
number of orders received.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 255

Chapter 5 Simulation Output Tables

Cycle Service Level

This is the percentage of no stockouts in a given risk period. The risk period is based on
the demand lead time.

Fill Rate
Displays the ratio of fulfilled orders using current inventory over total orders for the
product at the facility. The Fill Rate does not apply to customer sites.

Fill Qty Rate

Displays the ratio of the number of units of the product that were available at the facility
(current inventory) to fulfill orders to the total number of units shipped out. The Fill Qty
Rate is not populated for customer sites.

Ready Rate
This is the percentage of no stockout in any given aggregation period; that is the fraction
of time with positive stock on-hand.

Ending Orders
Displays the total outstanding upstream orders at the end of the run which have yet to be
filled. For example, a shipment that has not arrived is included in Ending Orders.

Ending Order Qty

Displays the total outstanding upstream order quantity at the end of the run which have
yet to be filled. For example, a shipment that has not arrived is included in Ending Order
Qty.

Total Order Qty

Displays the total number of product units that were ordered from this site during this
period.

Total Shipped Qty

Displays the number of units of this product shipped from this site.

Total Shipped Value

Displays the value of product shipped from this site.

Total Shipped Weight

Displays the weight of this product shipped from this site.

Total Shipped Cubic

Displays the cubic volume of this product shipped from this site.

Ending Back Orders

Displays the number of orders that are currently on back order at the end of simulation;
that is, the number of orders that are unfulfilled. Orders will be on back order if, for
example, a shipment has not arrived.

256 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Customer Details

Ending Back Order Qty

Displays the number of product units that are currently (at the end of the simulation) on
back order; that is, the number of units that are unfulfilled. Ordered units will be on back
order if, for example, a shipment has not arrived.

Total Back Order Qty

Displays the total number of back ordered product units throughout the simulation. These
are the order units that cannot be fulfilled using inventory. It applies only to non-
customer sites.
For example, a distribution center receives 5 orders of 10 units each from the customer.
Throughout the modeling time, this DC has only 10 units of inventory; the Total Back
Order Units at the DC is 40 units.

Total Downstream Demand

Displays the total demand for this product at this site throughout the simulation.

Lost Downstream Demand

Displays the number of demand units that were lost during this simulation replication.

Lost Downstream Demand Revenue

Displays the lost revenue due to lost demand units during this simulation replication.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Customer Details
This table shows detailed information at the customer-product level, including order cycle
time values. This table contains a unique record for each site, product, scenario,
replication and period combination.

Scenario
Displays the name of the scenario which generated the customer-product detail data.

Customer Name
Displays the name of the customer site referred to in the report.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 257

Chapter 5 Simulation Output Tables

Product Name
Displays the specific item detailed in the report.

Average Order Cycle Time

Displays the average of the order cycle times (in DAYS) at this customer site and for this
product. Order cycle time is the difference between the time the entire order was filled
and the Due Date. If the value is negative, this is a measure of how much more quickly
the cycles are being fulfilled compared to when they are due. If the Due Date is not set, it
is treated as the end of time (also known as year 100000). In this case the order cycle
time will be 0.

Maximum Order Cycle Time

Displays the highest cycle time for this customer site and product. If the Due Date is not
set, it is treated as the end of time (also known as year 100000). In this case the order
cycle time will be 0.

On Time Rate
Displays the ratio of the orders that were successfully delivered on time to this customer
site to the total number of orders received.

On Time Qty Rate

Displays the ratio of the number of units that were delivered on time to this customer site
to the total number of orders received.

Ending Orders
Displays the total the number of outstanding orders still in existence at the end of a run
that have yet to be fulfilled. For example, a shipment that has not arrived is included in
Ending Orders.

Ending Order Qty

Displays the total the number of outstanding order quantity still in existence at the end of
a run that have yet to be fulfilled. For example, a shipment that has not arrived is
included in Ending Ordered Qty.

Total Orders
Displays the total number of orders by this customer during this period.

Total Order Qty

Displays the total number of product units that were ordered by this customer during this
period.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

258 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Flows

Total Demand
Displays the total demand for this product at this customer site throughout the
simulation.

Total Revenue
Displays the total revenue generated during the simulation by product being shipped to
this customer. The revenue is the Product Price multiplied by the units of demand served.

Lost Demand
Displays the number of demand units that were lost during this simulation replication.

Lost Revenue
Displays the lost revenue due to lost demand units during this simulation replication.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Network Flows
This table breaks down data regarding the flow of product from source to destination.

Scenario
Displays the name of the scenario which generated the network flow data.

Source Name
Displays where the product is shipped from.

Destination Name
Displays where the product is shipped to.

Product Name
Displays the item that is being shipped.

Mode
Displays the transportation lane that is being used in case of multiple modes.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 259

Chapter 5 Simulation Output Tables

Flow Units
Displays the number of products shipped.

Flow Weight
Displays the total weight of all units shipped.

Flow Cubic
Displays the total cubic volume of all units shipped.

Flow Transportation Cost

Displays the the total cost of shipping the units.

Flow Count
Displays the the number of times shipment occurs along this transportation lane during
the simulation (or equivalently, the number of trips in this lane).

CO2
Displays the CO2 emissions of the flow in unit mass.

Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic
Color
Allows for specific varieties of line to be displayed on the Geo Map by individual flows.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Flow Revenue
Displays the total revenue generated by product being shipped on this network path. The
revenue is the Product Price multiplied by the units of demand served.

Flow Outbound Warehousing Cost

Displays the outbound warehousing cost incurred by the network path by leaving the
source site.

Flow Duty Cost

Displays the additional duty cost incurred by the network path. The duty cost is calculated
by multiplying the duty from Transportation Policies by the shipment’s total value. The
total value is the Value from the Product table multiplied by shipment quantity.

Flow Total Cost

The total cost incurred for the network flow.
Total Cost = Flow Outbound Warehousing Cost + Flow Transportation Cost + Flow
Duty Cost + Flow Intransit Inventory Holding Cost

260 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Interfacility Shipment Flows

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Interfacility Shipment Flows

This table displays the flows between facilities per period for a product on a specific
mode.

Scenario
Displays the name of the scenario which generated the interfacility shipment flows data.

Source Name
Displays where the product is shipped from.

Destination Name
Displays where the product is shipped to.

Product Name
Displays the item that is being shipped.

Mode
Displays the transportation lane that is being used in case of multiple modes.

Flow Units
Displays the number of products shipped.

Flow Weight
Displays the total weight of all units shipped.

Flow Cubic
Displays the total cubic volume of all units shipped.

Flow Revenue
Displays the total revenue generated by product being shipped on this interfacility flow.
The revenue is the Product Price multiplied by the units of demand served.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 261

Chapter 5 Simulation Output Tables

Flow Inbound Warehousing Cost

Displays the inbound warehousing cost incurred by the network path when entering the
destination site. This is based on the Inbound Cost in the Inventory Policies table.

Flow Outbound Warehousing Cost

Displays the outbound warehousing cost incurred by the network path by leaving the
source site. This is based on the Outbound Cost in the Inventory Policies table.

Flow Transportation Cost

Displays the the total cost of shipping the units.

Flow Duty Cost

Displays the additional duty cost incurred by the network path. The duty cost is calculated
by multiplying the duty from Transportation Policies by the shipment’s total value. The
total value is the Value from the Product table multiplied by shipment quantity.

Flow Intransit Inventory Holding Cost

Displays the inventory cost incurred by the travel time and units of travel.

Flow Total Cost

The total cost incurred for the interfacility flow (for each source - destination - product -
mode - period combination):
Total Cost = Flow Inbound Warehousing Cost + Flow Outbound Warehousing Cost +
Flow Transportation Cost + Flow Sourcing Cost + Flow Duty Cost + Flow Intransit
Inventory Holding Cost + CO2 Cost

CO2
Displays the CO2 emissions of the flow in unit mass.

Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic
Color
Allows for specific varieties of line to be displayed on the Geo Map by individual flows.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

262 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Customer Shipment Flows

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Customer Shipment Flows

This table displays the details of flows from source to customer for each product, mode
and period.

Scenario
Displays the name of the scenario which generated the customer shipment flows data.

Source Name
Displays where the product is shipped from.

Customer Name
Displays where the product is shipped to.

Product Name
Displays the item that is being shipped.

Mode
Displays the transportation lane that is being used in case of multiple modes.

Flow Units
Displays the number of products shipped to this customer.

Flow Weight
Displays the total weight of all units shipped to this customer.

Flow Cubic
Displays the total cubic volume of all units shipped to this customer.

Flow Revenue
Displays the total revenue generated by product being shipped on this customer flow. The
revenue is the Product Price multiplied by the units of demand served.

Flow Outbound Warehousing Cost

Displays the outbound warehousing cost incurred by the network path by leaving the
source site.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 263

Chapter 5 Simulation Output Tables

Flow Transportation Cost

Displays the the total cost of shipping the units.

Flow Duty Cost

Displays the additional duty cost incurred by the customer flow. The duty cost is
calculated by multiplying the duty from Transportation Policies by the shipment’s total
value. The total value is the Value from the Product table multiplied by shipment quantity.

Flow Total Cost

The total cost incurred for the customer flow.
Total Cost = Flow Outbound Warehousing Cost + Flow Transportation Cost + Flow
Sourcing Cost + Flow Duty Cost

CO2
Displays the CO2 emissions of the flow in unit mass.

Output Flow Graphic / Output Flow Graphic Size / Output Flow Graphic
Color
Allows for specific varieties of line to be displayed on the Geo Map by individual flows.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Interfacility Order Flows

Use this table to review the order flows between facilities by product and period.

Scenario
Displays the name of the scenario which generated the interfacility order flows data.

264 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Customer Order Flows

Order Source
Displays where the product is shipped from.

Order Destination
Displays where the product is shipped to.

Product Name
Displays the item that is being shipped.

Orders
Displays the number of orders of this product from the source to the site in this period.

Order Qty
Displays the number of units of this product from the source to the site in this period.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Flow Sourcing Cost

Displays the cost incurred in sourcing the product units. This is based on the Sourcing
Cost and Sourcing Order Cost in the Sourcing Policies table.

Flow Consignment Cost

Displays the cost incurred in consigning the product units. This is based on the
Consignment Cost and Consignment Unit Cost in the Inventory Policies table.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Customer Order Flows

Use this table to review the order flows to each customer by source, product and period.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 265

Chapter 5 Simulation Output Tables

Scenario
Displays the name of the scenario which generated the customer order flows data.

Order Source
Displays where the product is shipped from.

Order Destination
Displays where the product is shipped to.

Product Name
Displays the item that is being shipped.

Orders
Displays the number of orders of this product from the source to the customer in this
period.

Order Qty
Displays the number of units of this product from the source to the customer in this
period.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Flow Sourcing Cost

Displays the cost incurred in sourcing the product units. This is based on the Sourcing
Cost and Sourcing Order Cost in the Sourcing Policies table.

Flow Consignment Cost

Displays the cost incurred in consigning the product units. This is based on the
Consignment Cost and Consignment Unit Cost in the Inventory Policies table

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

266 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Bill of Materials Summary

Bill of Materials Summary

Use this table to review Bill of Materials information per Site - BOM - Product - Period.

Scenario
Displays the name of the scenario which generated the bill of materials data.

Site Name
Displays the site at which the product is located.

BOM Name
Displays the name of the Bill of Materials for the specific product.

Product Name
Displays the product that is part of the Bill of Materials.

Type
Displays whether the product is an INPUT to the Bill of Materials or an OUTPUT from the
Bill of Materials.

Quantity
Displays the number of units of this product for the Bill of Materials at this site in the
specific period.

Weight
Displays the weight of this product for the Bill of Materials at this site in the specific
period.

Cubic
Displays the cubic volume of this product for the Bill of Materials at this site in the specific
period.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 267

Chapter 5 Simulation Output Tables

that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Customer Summary
Use this table to review statistics about orders, revenue and inbound flows to each
customer per period.

Scenario
Displays the name of the scenario which generated the customer summary data.

Customer Name
Displays the customer to which the summary applies.

Avg On Time Rate

Displays the weighted average of the orders that were successfully delivered to the
customer on time (before their due date) to the total number of orders received during
this period.

Avg On Time Qty Rate

Displays the weighted average of the number of units that were delivered to the customer
on time (before their due date) to the total number of orders received during this period.

Inbound Flow Units

Displays the total number of units of all products to this customer in this period.

Inbound Flow Weight

Displays the total weight of all products to this customer in this period.

Inbound Flow Cubic

Displays the total cubic volume of all products to this customer in this period.

Total Revenue
Displays the total revenue generated during the simulation by product being shipped to
this customer.

Lost Revenue
Displays the lost revenue due to lost demand units during this simulation replication.

Total Demand
Displays the total number of demand units for all products at this customer in this period.

Lost Demand
Displays the number of demand units that were lost during this simulation replication.

268 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Production Summary

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Production Summary
This table provides information about the production of a product at a site per period.

Scenario
Displays the name of the scenario which generated the production summary data.

Site Name
Displays the location where the product is produced.

Product Name
Displays the item that is being produced.

Production Lots
Displays the number of lots (flow / lot size) for the product at this site in this period.

Production Qty
Displays the number of units of this product produced at this site in this period.

Production Weight
Displays the weight of this product produced at this site in this period.

Production Cubic
Displays the cubic volume of this product produced at this site in this period.

Production Value
Displays the value of the product produced at this site in this period based on the Value in
the Products table.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 269

Chapter 5 Simulation Output Tables

Production Cost
Displays the total cost of production for products in this period. This is based on the
Setup Cost per lot and the Cost Per Unit in the Processes table.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Product Summary
This table provides a summary of information about the products in the simulation run,
including total profit, total cost and other statistics per period.

Scenario
Displays the name of the scenario which generated the product summary data.

Product Name
Displays the name of the product in the simulation model.

Total Profit
Displays the total profit generated from this product in this period, as calculated by the
total revenue for the product minus the total cost for the product.

Total Cost
Displays the total cost incurred by sourcing, producing, storing, and transporting the
product in this period.

Total Revenue
Displays the total revenue generated by delivering the product to customers in this
period. The revenue is the Product Price multiplied by the units of demand served.

270 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Process Summary

Production Cost
Displays the total cost of production for the product in this period. This is based on the
Setup Cost per lot and the Cost Per Unit in the Processes table.

Transportation Cost
Displays the total cost to ship the product between facilities (Interfacility Shipment Flows)
and to customers (Customer Shipment Flows) in this period.

Warehousing Cost
Displays the total inbound and outbound warehousing cost for the product in this period.

Total CO2
Displays the total CO2 incurred producing and transporting this product in this period.

Total Demand
Displays the total units of this product demanded in this period.

Lost Demand
Displays the number of demand units of this product that were lost during this period in
the simulation replication.

Lost Revenue
Displays the lost revenue due to lost demand units of this product in this period during
this simulation replication.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Process Summary
This table provides a summary of the process steps for each site - product - period
combination.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 271

Chapter 5 Simulation Output Tables

Scenario
Displays the name of the scenario which generated the process summary data.

Site Name
Displays where the product is produced.

Product Name
Displays the item that is being produced at this site in this period.

Process Name
Displays the name of the process at this site in this period.

Process Step Name

Displays the process step name for this record.

Input Weight
Displays the weight of this product used at this site for this process step in this period.

Input Cubic
Displays the cubic volume of this product used at this site for this process step in this
period.

Input Quantity
Displays the number of units of the product used at this site for this process step in this
period.

Yield Quantity
Displays the number of units of the product produced at this site for this process step in
this period based on the Yield as defined in the Processes table.

Production Cost
Displays the total cost of production for the product in this period. This is based on the
Setup Cost per lot and the Cost Per Unit in the Processes table.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Rep
Displays the replication number that the data on this row apply to.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

272 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Network Paths

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Network Paths
Network Paths display the flow of product from its initial source to final destination. To
generate Network Paths, click the arrow underneath the Optimization or Simulation run
button and select "Generate Network Paths."

Scenario
Displays the scenario for which the summary data was generated.

Customer Name
Displays the name of the customer to which the network path occurred.

Product Name
Displays the name of the product that flowed between the source and destination.

Demand Qty
Displays the quantity demanded by the customer for the specific product.

Flow Unit Qty

Displays the number of units that flowed on the site-destination-product-mode
combination.

Weight Qty
Displays the weight of the flow traveling on this network path.

Cubic Qty
Displays the cubic volume of the flow traveling on this network path.

Facility1
Displays the first facility upstream from the customer. Additional Facilityn columns are
displayed for facilities upstream on the network path.

Mode1
Displays the mode on which the product flows for the first leg of the network path.
Additional Moden columns are displayed for transportation legs upstream on the network
path where n indicates the leg on the network path.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 273

Chapter 5 Simulation Output Tables

Transportation Cost1
Displays the transportation cost incurred on the first leg of the network path. Additional
Transportation Costn columns are displayed for transportation legs upstream on the
network path where n indicates the leg on the network path.

Facility Fixed Cost1

Displays the fixed cost for the first facility in the network path. Additional Facility Fixed
Costn columns are displayed for facilities upstream on the network path where n indicates
the leg on the network path.

Transportation Cost
Displays the total transportation cost incurred by the network path.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Production Transactions
This table shows all individual production orders that occur during the simulation. Records
are populated in this table if the Production Transactions option is checked on the
Detailed Output tab of Simulation Options.

Scenario
Displays the name of the scenario which generated the production transaction data.

Site Name
Displays the name of the site that produced the product.

Product Name
Displays the product produced at this site.

Quantity
Displays the number of units of product produced in the production order.

Time
Displays the time at which the production order completed.

Work Center Name

Displays the name of the final work center used in producing the product.

274 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Demand Transactions

Production Cost
Displays the cost to complete the specific production order. This is based on the Setup
Cost per lot and the Cost Per Unit in the Processes table.

Production Time
Displays the amount of time in DAYS taken to complete the production order. This is
based on the Production Time and Production Time Per Unit in the Sourcing Policies table.

Internal Order Number

Displays the internally generated order number used to track the production order.

User Defined Order Number

Displays the Order Number field from the Demand or Shipments table. This is an optional
user defined order number that you can populate.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Demand Transactions
This table breaks down data regarding the demand occurring per product per customer
site. Records are populated in this table if the Demand Transactions option is checked on
the Detailed Output tab of Simulation Options.

Scenario
Displays the name of the scenario which generated the demand transaction data.

Site Name
Displays the site (customer) where the demand originates.

Product Name
Displays the product name of the item that is demanded.

Quantity
Displays the number of units demanded by the customer.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 275

Chapter 5 Simulation Output Tables

Time
Displays the time when the demand was generated.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Shipment Transactions
This table shows all the shipments that occur during the simulation. Records are
populated in this table if the Shipment Transactions option is checked on the Detailed
Output tab of Simulation Options.

Scenario
Displays the name of the scenario which generated the shipment transaction data.

Source Name
Displays where the product is shipped from.

Destination Name
Displays where the product is shipped to.

Product Name
Displays the name of the product that is being shipped in this transaction.

Quantity
Displays the number of units of product shipped in the particular transaction

Time
Displays the time when the shipment arrived at the destination.

CO2
Displays the unit mass of CO2 emissions due to the shipment. This is based on the CO2
and CO2 Basis values in the Transportation Policies table.

276 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipment Transactions

Weight
Displays the total weight of items shipped in this transaction.

Cubic
Displays the total volume of items shipped in this transaction.

Mode
Displays the mode used on this transportation lane.

Shipment Number
Displays the unique shipment ID number for this transaction.

Transportation Cost
Displays the cost incurred due to the shipment. This is calculated based on the Cost Basis
and Cost values in Transportation Policies. For example, if Cost Basis = Distance,
Transportation Cost is (Distance * Cost).

Duty
Displays the duty or tariff incurred by the shipment transaction. The duty cost is
calculated by multiplying the duty from Transportation Policies by the shipment’s total
value. The total value is the Value from the Product table multiplied by shipment quantity.

Due Date
Displays the original due date for the shipment to reach its destination.

Transportation Policy
Displays the name of the transportation policy used to conduct the shipment.

Asset Name
Displays the type of asset used to conduct the shipment.

Asset Unit
Displays the specific unit of the asset type that conducted the individual shipment.

Internal Order Number

Displays the unique internally generated order ID number as defined in the original
shipment table.

User Defined Order Number

Displays the Order Number field as defined in the Shipments table.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 277

Chapter 5 Simulation Output Tables

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number that the data on this row applies to.

Shipment Mileage Log

The mileage log is written as shipments depart during the simulation.
Each row of the mileage log contains information about one leg of the trip. Thus for a
simple out and back delivery there would be two rows, one for the outbound delivery and
one for the return trip.
In a pooled delivery model there would potentially be more than two rows corresponding
to a single trip.
Each shipment is assigned a Shipment ID that can be used to group all the legs belonging
to the same shipment. This value can also be used to correlate data with the shipping
item log.

Scenario
Displays the name of the scenario which generated the shipment mileage log data.

Source Site
Displays the name of the Source Site of the shipment.

Destination Site
Displays the name of the destination site of the shipment.

Shipment ID
Displays the unique ID number that is used to group and correlate data relating to the
same shipment.

Departure Date
Displays the date and time of departure from the source location.

Arrival Date
Displays the date and time of arrival at the destination location.

Distance
Displays the distance traveled between the source and destination on this leg of the trip.

278 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Shipment Mileage Log

Asset Name
Displays the name of the asset. This field could be empty if no asset was used.

Asset Unit Number

Displays the unit number of the asset. This field could be empty if no asset was used.

Container ID
Displays the unique ID of the container used to transport the product, if used.

AVERAGE
Displays the time series average value.

SIMPLEAVERAGE
Displays the time series simple average value.

STDDEV
Displays the time series standard deviation value.

MIN
Displays the time series minimum value.

MAX
Displays the time series maximum value.

CURRENT
Displays the time series current value.

TOTAL
Displays the time series total value.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 279

Chapter 5 Simulation Output Tables

Rep
Displays the replication number to which this data corresponds.

Shipment Handling Log

This table displays the handling that occurs, both assets and work resources.

Scenario
Displays the name of the scenario which generated the shipment handling log data.

Site
Displays the site which handled the shipment.

Shipment ID
Displays the unique shipment ID number.

Start Date
Displays the date and time at which the shipment was first handled by the site.

Handling Time
Displays the amount of time the shipment was handled by the site.

Operation
Displays the operation which the site conducted to the shipment.

Asset Name
Displays the asset type that was used in the shipment.

Asset Unit Number

Displays the unique asset ID number of the asset type that was used in the shipment
handling.

Consignment Name
Displays the unique order (or consignment) from which the handling was based.

Quantity
Displays the quantity of units handled by the site.

Work Resource Name

Displays the last work resource to handle the shipment at the site.

Internal Order Number

Displays the order number as defined in the shipment or demand table.

280 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Order Report

User Defined Order Number

Displays the Order Number field as defined in the Shipments table.

AVERAGE
Displays the time series average value.

SIMPLEAVERAGE
Displays the time series simple average value.

STDDEV
Displays the time series standard deviation value.

MIN
Displays the time series minimum value.

MAX
Displays the time series maximum value.

CURRENT
Displays the time series current value.

TOTAL
Displays the time series total value.

Period
Displays the Period number for the summary values. ALL indicates the record for the
complete model horizon.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number to which this data corresponds.

Order Report
This report displays details about each order processed. The information includes the
source and destination sites, product and quantities ordered, filled and back ordered.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 281

Chapter 5 Simulation Output Tables

Records are populated in this table if the Order Transactions option is checked on the
Detailed Output tab of Simulation Options.

Scenario
Displays the name of the scenario which generated the order report data.

Replication Number
Displays the replication number of the scenario that generated the summary data.

Order Processed Date

Displays the date on which the order was processed by the Inventory Policy.

Source Site
Displays the name of the Source Site of the order.

Destination Site
Displays the name of the Destination Site of the order.

Product Name
Displays the name of the Product that was on this order.

Internal Order Number

Displays the unique order number generated by Supply Chain Guru.

User Defined Order Number

Displays the Order Number entered on the Demand or Shipments table.

Original Order Quantity

Displays the quantity specified on the Demand or Shipments table.

Quantity Previously Filled

Displays the quantity filled prior to the current date. If an order is too large to fulfill at
once, it may be filled in a series of separate shipments.

Quantity Filled
Displays the number of product units that were filled at the end of the simulation.

Quantity Backordered
Displays the number of product units that is currently (at the end of the simulation) on
back order; that is, the number of units that are unfulfilled.

Order Created Date

Displays the date on which the order was created based on the Order Time or Order Time
Formula and the Time Between Orders.

282 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

 Error Log

Order Due Date

Displays the original due date for the order to reach its destination.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Error Log
This report displays information about any errors that were reported during the
simulation run.

Scenario
Displays the name of the scenario which generated the error log data.

Error
Displays information about the error that occurred.

Scenario ID
Displays the identifier of the scenario for which the summary data was generated.

Sub-Scenario ID
Displays the identifier of the sub-scenario, if applicable, for which the summary data was
generated. When you click on the field guru for the field, you see a Scenario Item Wizard
summary table. This table lists the scenario and sub-scenario names along with the field
that is being modified and the operator and value of that field. This table can assist in
distinguishing the sub-scenarios both by name and by their internal values.

Rep
Displays the replication number to which this data corresponds.

LLamasoft® Supply Chain Guru™ Data Dictionary 8.2 283

Chapter 5 Simulation Output Tables

284 LLamasoft® Supply Chain Guru™ Data Dictionary 8.2

Index

A I
Aggregate 120 Individuals 120
Assets 127 INF 119, 121, 129
Average Cost 120, 125 Inventory 118, 121
Average Cost Field Guru 125 Inventory carrying cost 121
Average Inventory 121, 247 Inventory Count Constraint 139
Average Site Inventory 247 Inventory holding costs 118, 121
Avg Cost 125 Inventory Policies 121
Avg Unit Cost 120 Inventory Policies Multi-Period 121

C L
CO2 247, 250 Lane 125
Cond Min 140
Conditional Minimum 125 M
Constraints 119, 125, 129, 139, 140, Make 120, 125, 128
142, 143 Modes 125, 259
Cost Basis 125
Costs 118, 119, 120, 121, 125, 127,
128, 129, 131 N
Count Value 139, 142 Network Flows 259
Customer 128 Network Optimization 120
Cycle Stock 121
O
D Optimization 119, 120, 121, 125, 129
Demand 121, 128, 275 Order 119, 120, 125, 128, 129
Demand Transactions 275 Order Number 276
Destination 125 Outbound cost 247
Destination Site 125
Distance 125 P
Distance Traveled 278 Periods 118, 119, 120, 121, 125, 127,
128, 129, 131
F Policies 120, 125
Fixed Cost Fields 119 Price 4, 118
Fixed Operating Costs 247 Processes 128
Fixed Startup Costs 129 Processes Multi-Period 128
Flow 120, 125 Product required 125
Flow Requirement 125 Product Summary 250
Product Value 121, 125
Production Costs 128, 247
H Production Count 142
Horizon 120, 129 Production Transactions 278

Supply Chain Guru Data Dictionary 8.2 285

 Index

Products 118, 119, 120, 121, 125, 128, User-Defined Customer Demand
129 Profile 84
Products Multi-Period 118 User-Defined Facility Demand Profile 86

Q V
Qty 125 Value 4
Quantity 120, 121, 125
W
R Work Center Summary 251
Revenue 118, 247 Work Centers 120, 128, 129, 131
Work Centers Multi-Period 129
S Work Resource Summary 253
Safety Stock 121 Work Resources 131
Schedule 120 Work Resources Multi-Period 131
Set 120, 121
Shipment Handling Log 280
Shipment Mileage Log 278
Shipment Transactions 276
Simulation 120
Site Summary 247
Sites 119, 120, 121, 125, 128, 129, 131
SKU 118
Source Site 125
Sourcing Cost 120
Sourcing Policies 120
Sourcing Policies Multi-Period 120
Startup 129
Step 128
Stock 118, 121

T
Tables 125, 127
Throughput 121, 247
Time 118, 119, 120, 121, 125, 127,
128, 129, 131
Total Fill 244
Total Fill Rate 244
Total Inbound Warehousing 244
Total Inbound Warehousing Costs 244
Total Outbound Warehousing 244
Total Outbound Warehousing Costs 244
Transportation Assets 127, 250
Transportation Assets Multi-Period 127
Transportation Costs 121, 125, 244
Transportation Policies 125, 127
Transportation Policies Multi-Period 125
Types 118, 119, 120, 121, 125, 127,
128, 129, 131

U
Units 118, 120, 121, 125, 127, 128, 131

Supply Chain Guru Data Dictionary 8.2 286

 Index

Supply Chain Guru Data Dictionary 8.2 287

 Index

Supply Chain Guru Data Dictionary 8.2 288

 Index

Supply Chain Guru Data Dictionary 8.2 289

 Index

Supply Chain Guru Data Dictionary 8.2 290

 Index

Supply Chain Guru Data Dictionary 8.2 291

 Index

Supply Chain Guru Data Dictionary 8.2 292